Encountering "Target is not responding, retrying..." a few seconds after starting the GDB debugger

rrooyen · ‎2024-04-05

I tried an uninstall and reinstall of STM32CubeIDE V1.14 (this version is a project requirement), but there has been no change in the behavior. That target board is a NUCLEO-F413ZH. I have never seen this behavior before on a variety of other NUCLEO boards using STM32CubeIDE V1.8.

Console:

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

Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
-------------------------------------------------------------------
STM32CubeProgrammer v2.15.0
-------------------------------------------------------------------

Log output file: C:\Users\rob\AppData\Local\Temp\STM32CubeProgrammer_a23412.log
ST-LINK SN : 066EFF363445503043033620
ST-LINK FW : V2J43M28
Board : NUCLEO-F413ZH
Voltage : 3.26V
SWD freq : 4000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x463
Revision ID : Rev A
Device name : STM32F413/F423
Flash size : 1.5 MBytes
Device type : MCU
Device CPU : Cortex-M4
BL Version : 0x90

Memory Programming ...
Opening and parsing file: ST-LINK_GDB_server_a23412.srec
File : ST-LINK_GDB_server_a23412.srec
Size : 175.92 KB
Address : 0x08000000

Erasing memory corresponding to segment 0:
Erasing internal memory sector 0
Erasing memory corresponding to segment 1:
Erasing internal memory sectors [4 5]
Download in Progress:

File download complete
Time elapsed during download operation: 00:00:03.549

Verifying ...

Download verified successfully

Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Shutting down...
Exit.

rrooyen · ‎2024-04-07

Update: The generic project that was created for the NUCLEO-F413ZH board with a simply blinky was showing the "Target is not responding, retrying..." debugger issue as well, so I did a full chip erase with the STM32CubeProgrammer and debugged the generic project again, and the problem appears to have gone away!

rrooyen · ‎2024-04-07

Update: I tried a full chip erase and downloaded the application code, but no luck as the "Target is not responding, retrying..." debugger issue is still present.

bowlofpudding · ‎2024-10-13

I had this same problem and would like to share what caused it. I ended up having a small hair short (piece of wire) between TDI and the pin next to it. When the processor set that pin to an output, it made jtag not work anymore. removing the short fixed the issue for me.