Custom STM32H743 port fails to boot when certain pins have peripherals attached #17106
Unanswered
charlierefvem
asked this question in
STM32 / Pyboard
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working with a colleague to trim down the NUCLEO_H743ZI2 port to barebones for a custom PCB I've designed. We have modified the firmware to use appropriate pins for USB VCP and to get the clock working with an 8MHz crystal. The board can boot fine, the REPL works, and we've tested some of the features of the PCB, such as a few LEDs and a couple motor drivers that are on board. All of that works fine until we hook up some of the external peripherals. Either of the two issues cause boot failure (no USB device mounting, no REPL, and previously flashed code does not run either).
I'm hoping to get some help troubleshooting why having these pins connected externally might cause the Micropython firmware to fail to boot properly. My hunch is that something in the startup/boot process depends on one or more of the utilized pins in a manner that we do not understand.
I have confirmed with moderate confidence that the issue is not hardware or power related as I can run C code just fine with all of these peripherals connected and enabled.
Beta Was this translation helpful? Give feedback.
All reactions