Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For a SKR Mini E3 V3.0 make UART 5 available on PD2 and PD3 #26825

Merged
merged 2 commits into from
Apr 7, 2024

Conversation

ellensp
Copy link
Contributor

@ellensp ellensp commented Feb 27, 2024

Description

A discord user tommat6117 wanted to connect octoprint via serial to their SKR Mini E3 V3.0 (not via USB)
I'm guessing that they have a BTT TFT so the TFT serial port and the serial port on EXP1 are not available, leaving no documented options.

At first they wanted software serial on any of the IO pins (PD0,PD2,PD3,PD4,PD5)
I pointed out that software serial was a bad idea, and Marlin doesn't support software serial ports for standard gcode serial ports.

After a little digging I noticed that hardware UART 5 can be configured to be on PD2 (RX) and PD3 (TX)

The current build environment sets up UART 5 pins as PD2 (RX) and PC12 (TX), PC12 being the POWER_LOSS_PIN on the PWR-DET plug.

Updated the build environment STM32G0B1RE_btt
with -DPIN_SERIAL5_RX=PD_2 -DPIN_SERIAL5_TX=PD_3

So now any user can use UART 5 on PD2, PD3 easily

Requirements

A desire to use UART 5

Benefits

UART 5 works "out of the box"

Related Issues

https://discord.com/channels/461605380783472640/491165528295997450/1211624259332612126

@sjasonsmith sjasonsmith changed the title For a SKR Mini E3 V3.0 make UART 5 avalable on PD2 and PD3 For a SKR Mini E3 V3.0 make UART 5 available on PD2 and PD3 Apr 7, 2024
@sjasonsmith sjasonsmith merged commit 351a1a1 into MarlinFirmware:bugfix-2.1.x Apr 7, 2024
61 checks passed
@ellensp ellensp deleted the move-uart-5-pins branch April 7, 2024 06:33
RPGFabi pushed a commit to RPGFabi/Marlin that referenced this pull request Jun 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants