I am using the Nx_TCP_Echo_Server example with the N6Nucleo, and after a couple of successful iterations my debugger stopped working entirely.
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"). A pop-up lists "can't read memory", but as I mention later the CubeProgrammer works fine.
After disconnecting and re-initializing the debugger I will get the following error ("error in intializing... please check power") and this persists until I power-cycle the board. LED 2 (Red) will then remain off until I power cycle the board after the first error.
I assumed I re-wrote the SWD lines so I used CubeProgrammer to perform a chip erase on the external flash memory and I can see it's empty. After the chip erase and unplugging the BOOT0 jumper I'm still stuck with the same issue.
If anyone could offer some advice to fix the issue. I assume it's related to some part of memory not being erased,but with the external memory the solution isn't clear.
EDIT: I was able to fix the issue by using the STMCubeIDE to run the example.
EDIT 2: It looks like a recent VSCode STM32 update came out in the last 1 or 2 since posting broke the debugging, at least for the N6 Nucleo that I was using. The solution I found was to roll back the specific STM32 Debug Core Extension alongside the CMake Support Extension. I'm not sure about the viability of having everything updated except those 2 extensions but I'll keep at it till something else breaks.