“ST-Link Debugging Issue: Launch Debugging Failed on STM32 Blue Pill”

[srinathr]

Hello Everyone,
I am attempting to debug code on the STM32 Blue Pill board. The project compiles successfully, but when I start a debug session, it fails with the message “Launch debugging failed,” along with additional error details shown below. I would appreciate any guidance on resolving this issue.
Note: I am using an ST-Link V2 programmer (A2020 version).
Wiring is done correctly checked multiple time.
I had doubts about the Debugger configurations. Are there any other settings must be modifiable, or any other ways are

there?

" Error in final launch sequence:

Failed to start GDB server

Failed to start GDB server

Error in initializing ST-LINK device.

Reason: (18) Could not verify ST device! Abort connection."

[mƎALLEm]

Hello @srinathr and welcome to the ST community,

Unfortunately, BluePill boards most probably contain a conterfeit STM32 product.

You may also using a cloned STLINK..

I suggest you to use a ST board with a genuine STM32 chip on it. 

Example: NUCLEO-F103RB

And we will happy to help you.

[Andrew Neil]

Review the many threads here on Blue (and other coloured) Pills.

As @mƎALLEm said, they most likely contain a fake STM32 and, therefore, are not guaranteed to work with genuine ST tools.

Using a fake or clone ST-Link only compounds the issue.

 

https://community.st.com/t5/others-hardware-and-software/stm32programmer-is-not-connecting-with-blue-pill-device/m-p/874331/highlight/true#M33309

[Karl Yamashita]

More than likely the ST-LinkV2 can't detect voltage from the Bluepill.  Does the Bluepill LED turn on when you plug in the USB cable?

Show how you made your connections between the debugger and the Bluepill.