2026-05-04 9:41 PM
Hi everybody.
I'm currently trying to use the N6 Nucleo for a personal application but am having trouble starting the debugger after initially successes. I am using the Nx_TCP_Echo_Server example, and after a couple of successful iterations my debugger stopped working entirely.
I am using the VSCode extension. When I start my debug session with ST-Link GDB server it will connect to the debugger, but an error will follow in the terminal as shown ("target not responding"). After disconnecting and re-initializing the debugger I will get the following error ("error in intializing... please check power"). I get the same issues after power-cycling the board. LED 2 (Red) will then remain off until I power cycle the board after the first error.
Previous issues led me to believe I re-wrote the SWD lines so I connected BOOT0 to 3.3V and used the CubeProgrammer to perform a chip erase. Specifically for the external memory since to my knowledge the N6 doesn't maintain internal memory. After the chip erase and unplugging the BOOT0 jumper I'm still stuck with the same issue.
If I could be offered some guidance to remedy my problem. I still suspect issues with the SWD but I might be overlooking an architectural aspect with the board that could resolve the issue.
2026-05-04 9:48 PM
Here is the initial error for more visibility.
Nx_TCP_Echo_Server/Core/Src/main.c:100
100 MPU_Config();
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...
GdbSession, Lost target connection, Exiting...
Shutting down...
Exit.
cube has exited with code 0