VSCode Extension v3.9.0 Breaks Debugger

[hbrewer8893]

Device: NUCLEO-N657X0-Q Board

Environment: STM32CubeIDE for Visual Studio Code Extension (v3.9.0)

Description & Symptoms: The debugger loses a connection with the board with “Target not responding” and “Unable to read memory” errors.  Reverting to version v3.8.0 of the extension and all of its dependencies resolves the issue.

Steps to Reproduce:

1. Set a breakpoint on the first line of the FSBL Reset_Handler
2. Run the debugger
3. Step past the following line in the Reset_Handler: mov sp, r0

Expected Behavior: Debugger is able to continue stepping through the code

Actual Behavior: The device stops responding and is unable to reconnect until unplugging and plugging back in

Other Notes: When running the debugger without a breakpoint set, the program runs normally.  As soon as a breakpoint is set, it loses the connection.

[bsgursta]

Coincidentally I just had this issue myself and somebody on another forum was able to guide me with the same solution.

I was able to narrow down the problematic extension to be the STM32 Debug Core by updating every other extension apart from that one while keeping debugging capabilities. I specifically tested this with the Nx_TCP_Echo_Server example with my STM32N6 Nucleo.