2025-05-02 5:45 AM - edited 2025-05-02 6:19 AM
I have a Nucleo WB55RG board with in built ST-Link.
I programmed it with a blinky LED & a UART message "Hi there!\n" via the CubeIDE on a different PC & it all works fine. TeraTerm has no problem selecting the ST-Link device connected to the PC
Now running it on a new PC I keep getting "No ST-Link Detected" when trying to download from Cube
TeraTerm cant find any COM ports when the board is plugged in but can find Arduino devices communicating via serial with no problem when they are plugged in.
The device doesn't even show up in the Device Manager.
I have installed ST-Link drivers & have successfully programmed other Nucleo boards with this PC in the past.
When the board is plugged in the com LED next to the ST USB flashes red & LED5 is on-red
I have uninstalled & reinstalled the latest ST-Link version but nothing.
I'm on USB cable number 3 so I doubt that a ddgy cable is th eissue unless I'm unlucky enough to have 3 failed cables.
Solved! Go to Solution.
2025-05-02 8:34 AM - edited 2025-05-02 8:35 AM
Turns out I was in fact very unlucky & did have 3 faulty USB cables!!
Fixed now with new USB micro B cable
2025-05-02 6:13 AM
I assume you have the NUCLEO-WB55RG in front of you?
I'll leave the information on ST-LINK to other users, but you can find all the documents including the layout in GERBER format in the file 'MB1355 Manufacturing files' at the tab CAD Resources.
Regards
/Peter
2025-05-02 6:18 AM - edited 2025-05-02 7:04 AM
Thanks Peter, yes I have it in front of me.
2025-05-02 8:34 AM - edited 2025-05-02 8:35 AM
Turns out I was in fact very unlucky & did have 3 faulty USB cables!!
Fixed now with new USB micro B cable
2025-05-02 1:14 PM
Well, not just you as it turns out. I have just had the exact same problem with a new STM32MP157D dev board. I tried three cables and could get no response from the board so concluded the board must be faulty even though it gave all the signs of working properly. Eventually found another USB cable and that brought everything to life. Maybe there is something a bit sensitive about the connectors on the boards. I have lots of other dev boards and never had this problem with any of them.