ST-Link can't connect in VSCode using ST-Link GDB server; but OK in Keil

[Austin_Jia]

[LaurentL]

Hello,

In the debug console text, can you check that the STLINK Firmware is not outdated and needs to be upgraded.

Or check if you see any error message.

Rgds,

Laurent

[Andrew Neil]

Welcome to the forum

Please see How to write your question to maximize your chances to find a solution for best results.

In particular:

• What STM32 device are you using?
• What board?
• What ST-Link?

Note that both a clone STM32 and a clone ST-Link could cause this type of thing - see:

Blue pill (STM32F1) programs OK via Arduino IDE but not Keil. Chip ID:0x2BA01477

How to recognize a genuine ST-LINK/V2 versus a cloned one

[luiscoelho23]

I had a similar problem, solved it with :

"serverPort": 50000 (configuration launch.json)

[Andrew Neil]

---

@Austin_Jia wrote:

---

Could you translate the rest of that message (the bit after "(error138):") to English, please?

[Nate42]

Yes, not sure about the non-english portion of the error but I just had a very similar problem and changing the port fixed it. This not too useful error message is exactly what you will get if the stlink gdb server fails to open the port it wants, which by default is 61234 and 61235. which just happen to be in a range windows will assign at random for a variety of things. 

[Andrew Neil]

---

@Nate42 wrote:

---

It seems that "tried to join a drive to a directory on a joined drive" is a generic thing that GDB says when pretty much anything goes wrong.

I see it when the connection fails because my target is not powered up, and when I've forgotten to connect  the ST-Link.