NRF5340 Seems to flash, but fails to debug using VSC

RE: NRF5340 Seems to flash, but fails to debug using VSC

TommyKirscher — Fri, 06 Jan 2023 21:06:56 GMT

I swapped out the J-link that I was using. Turns out that was the issue. I am now able to properly debug my board.

RE: NRF5340 Seems to flash, but fails to debug using VSC

TommyKirscher — Fri, 06 Jan 2023 16:25:46 GMT

Hi Dejan,

Is there a way of adding --recover to my west flash command using VSC?

I added "args": "--recover" to my launch.json, but it doesn't seem to accept "args". The only location that I found "west flash" was in build.ninja, and adding --recover to that line did not seem to change anything.

Thank you

RE: NRF5340 Seems to flash, but fails to debug using VSC

dejans — Fri, 06 Jan 2023 11:34:20 GMT

Hi,

Problems with debugging might be caused by enabled readback protection. Option --recover of either "west flash" or "nrfjprog" should be used to disable readback protection. I tested on empty_app_core sample and without --recover I have seen "Unable to step out: Cannot find the caller frame (from exec-finish --thread 1)" message. Adding CONFIG_DEBUG_OPTIMIZATIONS and CONFIG_DEBUG_THREAD_INFO did not change anything. Note that I included "Enable Debug options" when creating build configuration.

Best regards,
Dejan

RE: NRF5340 Seems to flash, but fails to debug using VSC

TommyKirscher — Fri, 06 Jan 2023 01:46:19 GMT

I actually just got it to work in a very janky way. Seems somewhat reliably reproduceable. I can begin debugging if I do the following:

Get the debugger to launch and leave it open
Reboot the kit
While the debugger is still on, launch the debugger again
VSC will ask if it can erase flash memory, say yes. If you don't get the prompt, it doesn't seem to work
Press play on the debugger. Step through won't work, but pausing again will stop the program and show your cursor in the program.

Still a pretty painful process, and I don't think that break points work with this method.