DEBUGGER NOT WORKING: STLINK/V2

neelimas · ‎2023-10-11

Hi Team,

Recently i was using stm32 stlinkv2 in the STM32F411CEU6. They debugger was workig fine . After flashing 10-20 times , the debugger stopped working and throwig up the error:

Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
InitWhile : Enabled

Target no device found

Error in initializing ST-LINK device.
Reason: No device found on target.

and a pop up notification stating as follows :
__Error in final launch sequence:

Failed to execute MI command:
target remote localhost:61234

Error message from debugger back end:
localhost:61234: Connection timed out.
Failed to execute MI command:
target remote localhost:61234

Error message from debugger back end:
localhost:61234: Connection timed out.
localhost:61234: Connection timed out.__

I kindly request a solution for the debugger issue that iam facing. Pleaese refer to the attachments below. i tried firmware upgradtion in STM32CubeProgrammer. The IDE , iam using STM32CubeIDE.

Thanks and Regards
Neelima S

TDK · ‎2023-10-11

"Voltage: 0.02V" suggests the target chip doesn't have power.

If you feel a post has answered your question, please click "Accept as Solution".

neelimas · ‎2023-10-11

Hi Team ,

This error was corrected using the STM32 ST-Link UTILITY. When the USB cable is first plugged in, hold down the reset button, and immediately select Target->Erase Chip upon release. Once the chip is erased, the bootloader will be able to utilize the USB connection correctly and you will be able to use the USB port to program.

After this, I did a Mass Erase (Full chip erase)in the STM32CubeProgrammer. STLINK got connected in STM32CubeProgrammer. But while flashing the code to the STM32 MCU, We are getting the error:"Target not responding, retrying".

Kindly provide a solution. Waiting for reply

Thanks and Regards

Neelima S