MicroPython
H743ZI No Response with Micropython #15656
-
|
Hello, I am trying to compile the NUCLEO-H743ZI2 micropython firmware for a custom made board in which many of the pins have been moved to optimal locations for my use case. I cannot seem to get the device to be discoverable via USB after flashing the firmware. I changed the pins.csv file to match my pinout and the config files as well. I have been wandering through the C files trying to figure out if I am missing something that is causing this to happen. Is there any pointers from more experienced developers that could possibly help me get looking in the correct locations for this? I have tried changing many of the configurations to see if anything changes and so far no luck. Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 4 replies
-
|
The USB pins on a stm often can't be changed, is the USB port still on the same pins? Has the main crystal / oscillator speed and type been changed compared to the nucleo? Can you use the boot0 pin to get the board onto DFU mode and does that come up on USB? (Assuming this mode works the same on this stm chip) There's any number of things that can cause embedded firmware to stop starting up correctly on a new custom board, often a debugger where you can step through the code is the fastest way to see what does and doesn't work. |
Beta Was this translation helpful? Give feedback.
-
|
@andrewleech |
Beta Was this translation helpful? Give feedback.
-
|
I am curious if the standard clock settings are the issue with the mpconfigboard.h file used. Using PLL3 in C code for the USB setup does not work but using the HSI48 setting makes it work. I am just not sure entirely what options I am able to add to the file in order to try this. |
Beta Was this translation helpful? Give feedback.
-
|
Do you have an actual nucleo you can run the official build on to ensure that works for you? I assume the clock settings in the config files are correct for that board but I don't have one myself to double check it does work. |
Beta Was this translation helpful? Give feedback.
-
|
I did have one but the stlink on it seems to be having issues communicating with my laptop and the stm has been locked up so I have another board coming tomorrow. I will update on if it works on that board when I get it. |
Beta Was this translation helpful? Give feedback.
-
|
I froze a simple script to toggle a gpio on and off and after scoping the pin it seems that the code did not run. This leads me to believe that micropython is not actually running on the board after being flashed, just unsure as to why. I will test on the nucleo board again once it comes in this morning. |
Beta Was this translation helpful? Give feedback.
-
|
Have you tested USB connection? just boot the MCU on on bootloader mode and connect the usb to PC and you must see a new device popup, if the DFU driver installs then must be a clock issue, you can configure the clocks using stmcube ide and copy the settings to mpy source code |
Beta Was this translation helpful? Give feedback.
-
|
The issue ended up being clock related. On the nucleo board, the STM32 H7 is getting an 8MHz clock signal from the ST-Link STM32 F7 integrated on the board. This was an oversight when creating the custom board, but was remedied by placing an 8MHz oscillator on our board. Everything seems to be running fine now. Thanks for your help everyone. |
Beta Was this translation helpful? Give feedback.
-
|
Ah yes I'd forgotten that many nucleo boards do that to save a few cents from the BOM. It can be a real trap when using them as a reference, thanks for letting us all know your findings. Great outcome either way and good luck with your board! |
Beta Was this translation helpful? Give feedback.
-
|
@andrewleech our words right before we're "surely they wouldn't have not populated their oscillator to save a couple of cents..." guess we were mistaken! On the flip side the documentation doesn't really do the board justice especially since the ZI2 documentation is from the ZI board which had a different ST-Link setup. Only took us a whole week to figure out! |
Beta Was this translation helpful? Give feedback.
-
Ah, the number of times I've said this over the years working with embedded stuff ... 😅 |
Beta Was this translation helpful? Give feedback.
The issue ended up being clock related. On the nucleo board, the STM32 H7 is getting an 8MHz clock signal from the ST-Link STM32 F7 integrated on the board. This was an oversight when creating the custom board, but was remedied by placing an 8MHz oscillator on our board. Everything seems to be running fine now. Thanks for your help everyone.