2022-01-29 02:06 PM
The example project shown below builds and downloads successfully and halts at main(). The ST-LINK appears to connect and start successfully. It is when I click on run that the ST-LINK server says "Target is not responding, retrying..."
I changed absolutely nothing in the source code or header files. This is happening if I attempt to run and debug immediately after importing the default project.
The ST-LINK debugger works with other projects.
Shown below is the precise example project I am using:
This is the debugger view, with the program halted at main(), right before I click run:
Below is the console output after launching the debugger and halting at main():
STMicroelectronics ST-LINK GDB server. Version 5.9.1
Copyright (c) 2021, STMicroelectronics. All rights reserved.
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
-------------------------------------------------------------------
STM32CubeProgrammer v2.8.0
-------------------------------------------------------------------
ST-Link Server is running on port : 7184
ST-LINK SN : 0034002F3756501520303658
ST-LINK FW : V3J8M3
Board : NUCLEO-WL55JC
Voltage : 3.27V
SWD freq : 12000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x497
Revision ID : Rev Z
Device name : STM32WLxx
Flash size : 256 KBytes
Device type : MCU
Device CPU : Cortex-M4
BL Version : 0xc3
Memory Programming ...
Opening and parsing file: ST-LINK_GDB_server_a20912.srec
File : ST-LINK_GDB_server_a20912.srec
Size : 74112 Bytes
Address : 0x08000000
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 36]
Download in Progress:
File download complete
Time elapsed during download operation: 00:00:02.278
Verifying ...
Download verified successfully
And this is the output immediately after I click run:
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...
Error! Failed to read target status
Debugger connection lost.
Shutting down...
Here is my CubeMX configuration. I've tried serial wire, JTAG, and disabled:
I know that the M0+ core should be the core that most efficiently processes the LoRaWAN stack, but I've run this project before on the M4 core successfully, but am not sure what has changed since then, as I don't have that project anymore.
What am I missing?
Thank you to anyone that can help. I'd appreciate some guidance from the ST's FE's or Application Engineers, if that is possible.
Edit: Here are my debug configurations as well
Solved! Go to Solution.
2022-02-02 08:02 AM
Most probably you have to enable DEBUG MODE. Go to sys_conf.h and set DEBUGGER_ENABLED to 1. At this point you should be good to go.
2022-02-02 08:02 AM
Most probably you have to enable DEBUG MODE. Go to sys_conf.h and set DEBUGGER_ENABLED to 1. At this point you should be good to go.
2022-02-10 06:18 AM
I have exactly the same issue
2022-02-10 06:27 AM
The solution was partly answered by LMain.1 (thank you), and partly in the readme.txt included in the project:
2022-02-10 06:30 AM
Thanks! Where can I locate the sys_conf.h?
2022-02-10 06:37 AM
2022-02-10 06:47 AM
Thanks! Solved!
2023-11-22 12:29 AM
Thanks, had the same issue. But if I want to run the program without the debugger, to save battery, how do I proceed?