Unable to use debugger in VS Code using nRF Connect

RE: Unable to use debugger in VS Code using nRF Connect

Einar Thorsrud — Wed, 22 Sep 2021 13:29:24 GMT

Hi,

We have only been able to reproduce this issue when having checked the "Enable debug options" box when generating the Build Configuration together with samples that do not use threads. Can you see if this is the case in your setup as well? For instance, you should be able to debug Blinky if you do not select "Enable debug options", and all samples that use threads (like the Basic Thread Example and most complex samples) should work with "Enable debug options" enabled.

Checking "Enable debug options" adds several options to aid in debugging, including options that adds thread info structures to the firmware. This in turn is used by the Zephyr RTOS plugin for JlinkGDBserver. We suspect there is a bug here that causes this issue when no threads are used and will continue to look into that.

In a nutshell: Leave "Enable debug options" unchecked for samples that does not use threads.

Update: A workaround is to be to start debugging by Run -> Start Debugging (or pressing F5) instead of starting by clicking the "Debug Application" icon within the nRF Connect for VS Code plugin.

RE: Unable to use debugger in VS Code using nRF Connect

wbober — Wed, 22 Sep 2021 12:20:02 GMT

Hi AustinE,

We don't know yet what is causing this but some users report similar issue. We will look into this.

Kind regards,
Wojtek

VSC Team

RE: Unable to use debugger in VS Code using nRF Connect

Einar Thorsrud — Wed, 22 Sep 2021 12:11:57 GMT

Hi,

Yes, it seems this is the same issue as in the thread you linked to. We have seen a few instanced of this issue, and the team behind the nRF Connect for VS Code plugin is looking into it. Unfortunately we do not have a explanation or fix at the moment.