Skip to main content
Associate III
March 28, 2025
Solved

My USB-C Nucelo boards cannot detect ST-Link

  • March 28, 2025
  • 13 replies
  • 1322 views

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.

This topic has been closed for replies.
Best answer by kag_embedded

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.

13 replies

Chris21
Associate II
March 28, 2025

Are you using the correct USB connector? 

Labeled USB STLK.

.
Associate III
March 28, 2025

I have tried both USBC ports. One port, the LEDs do not light up. The other USBC port, near the header pins with the ST-LINK pins which are shorted together, blink through what appears to be a boot up sequence and then LED3 blinks at a regular pulse rate.

What should I try next?

Thank you.

Chris21
Associate II
March 28, 2025

Not sure, my NUCLEO-H503RB worked immediately. 

"the header pins with the ST-LINK pins which are shorted together"?

Which pins are those?  JP1 should not have a jumper.

.
Associate III
March 28, 2025

JP5, SW_STLK pins are shorted to +5v.

Chris21
Associate II
March 28, 2025

5V_STLK shorted to +5V is the normal use case, board powered from ST-LINK USB connector.

.
Associate III
March 28, 2025

Would using JP1 to reset the STLNK be worth a try? If yes, do I just short it out and then remove the short?

Chris21
Associate II
March 28, 2025

"do I just short it out and then remove the short?"  

That will reset the ST-LINK MCU, I don't expect it will solve your problem, though.

.
TDK
March 28, 2025

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.

"If you feel a post has answered your question, please click ""Accept as Solution""."
Associate III
March 28, 2025

I receive the same error message while trying to use STM32CubeProgrammer. Here is a screenshot of my board plugged in.

 

kag_embedded_0-1743191431659.png

 

eProgrammer. 

Associate III
March 28, 2025

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.

kag_embeddedAuthorBest answer
Associate III
March 28, 2025

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.