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

Wrong pin on MCU definition of Bigtreetech SKR2 #576

Closed
1 task done
Andi3D-tech opened this issue Apr 6, 2024 · 4 comments
Closed
1 task done

Wrong pin on MCU definition of Bigtreetech SKR2 #576

Andi3D-tech opened this issue Apr 6, 2024 · 4 comments
Labels
bug Something isn't working triage This is a new issue to be sorted (automatic label)

Comments

@Andi3D-tech
Copy link

Klippain branch

  • I confirm using the main branch

Version

v4.3.1-10-g1d9a2b53

Describe the bug and expected behavior

I wanted to connect the Bigtreetech Mini12864 to my BTT SKR2 via EXP1 and EXP2.

Unfortunately the display remained black.

Neopixel and reset button worked. Also the beeper.

After a long search I found the error:

Under config/mcu_definitions/main there is the BTT_SKR_2.cfg

# EXP1 header
 EXP1_1=PC5 , EXP1_2=PB0 ,
 EXP1_3=PB1 , EXP1_4=PB9 ,
 EXP1_5=PE10 , EXP1_6=PE11 , # Key in the socket on this side
 EXP1_7=PE12 , EXP1_8=PE13 ,
 EXP1_9=<GND> , EXP1_10=<5V> ,

EXP1_4=PB9 should be changed to EXP1_4=PE9.

The pin PB9 points to the I2C header.

Thanks!!!

Additional information and klippy.log

No response

@Andi3D-tech Andi3D-tech added bug Something isn't working triage This is a new issue to be sorted (automatic label) labels Apr 6, 2024
@tsk-2222
Copy link
Contributor

tsk-2222 commented Apr 9, 2024

Yup. It's a typo. Thanks for the eyeballs.

#578

Copy link

📌 This issue has been marked as stale because it has not had activity in the past 30 days.
To keep it open, please respond to this message or add new information. Otherwise, this will be closed in 14 days.
Thank you for your contributions!

@github-actions github-actions bot added the stale Issue that appear to be inactive, mark for potenial closing if stale for longer time label May 10, 2024
Copy link

This issue was closed due to inactivity for 14 days. Feel free to reopen it if you think it was an error or if you have new information or progress to share

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 24, 2024
@Frix-x Frix-x reopened this May 24, 2024
@github-actions github-actions bot removed the stale Issue that appear to be inactive, mark for potenial closing if stale for longer time label May 25, 2024
@Surion79
Copy link
Collaborator

completed by merged PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage This is a new issue to be sorted (automatic label)
Projects
None yet
Development

No branches or pull requests

4 participants