2025-04-23 9:13 AM
Hi, I am having several days problems with connecting ST-Link to gdb server to debug. I am using ST-Link V3, V2 (genuine ones).
Everything was working fine until I connected Copy of a ST-Link debugger (I didn't know it is copy, it has original logo on the top, but I took off the cover and there was not original STM32F1 MCU, just some knock off). So I tried to update this Fake ST-Link debugger and I didn't succeed, and I tried to update it also via STM32Programmer and also through ST-Link update button in VS Code. After all of this I think it messed up my GDB server directory on my mac but I deleted all ST software and installed again but still without change. It prints GDB server failed or USB error... Than I have read that ST stopped supporting those fake debuggers so I than connected my two original V2 debuggers, but without change. I even bought new original ST-Link V3MINIE and still the same, now it prints this :
2025-04-23 12:15 PM - edited 2025-04-23 12:16 PM
If you open STM32CubeProgrammer, does it detect the ST-Link chip? If not, what information or error message is displayed?
Try power cycling the computer and the programmer. Try different ports and different USB cables.
2025-04-23 12:23 PM
https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693
In particular: https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/tac-p/698105/highlight/true#M956