2025-03-28 10:22 AM
I just received a NUCLEO-H503RB dev board, and while attempting to use the GPIO_IOToggle example program to test out the board, I could not run the debugger due to the error "ST-Link not detected." I went back to my NUCLEO-H7S3L8 board, it now receives the same error. A few days ago, I was able to program it.
I was able to detect the ST-Link with my NUCLEO-F446RE board.
Do I need to reinstall ST-Link or is there a way to force a firmware update on my two NUCLEO USBC dev kits?
Thank you.
Solved! Go to Solution.
2025-03-28 12:44 PM
Look in Device Manager to see if anything shows up when the board is inserted. Could also be a bad port or bad cable.
Might need to reboot and reinstall, but seems unlikely if other boards show up fine.
2025-03-28 12:51 PM
I receive the same error message while trying to use STM32CubeProgrammer. Here is a screenshot of my board plugged in.
eProgrammer.
2025-03-28 1:27 PM
I am able to access my NUCLEO-H503RB board on my MAC computer.
On my PC, I see the boards for my non-USBC STM dev boards in Device Manager, but I do not see them for my USBC boards.
My work computer is Windows 10. Do I need to update the Windows 10 ST-Link driver?
I am looking around for a new cable to try.
2025-03-28 1:34 PM
Trying a 3rd cable was the key. It is quite touchy on the USBC cable.
With the 3rd cable, it shows up on my Device Manager and I can connect to it via STM32cubeIDE.
I am considering this issue resolved. Thank you for your help.