Debugging from VSCode with nRF Connect Extension

RE: Debugging from VSCode with nRF Connect Extension

Einar Thorsrud — Fri, 06 May 2022 10:22:23 GMT

I see, that is the latest. I have not been able to reproduce myself and have not found any other reports of this. Are there other factors that are need to reproduce this? Also, which Linux distribution (and version of it) are you using?

For now, enabling debug options in the project configuration file or just adding "-DCONFIG_DEBUG_OPTIMIZATIONS=y" as an extra CMake argument when you make a build configuration in VS Code should be a good workaround.

RE: Debugging from VSCode with nRF Connect Extension

diogodias — Thu, 05 May 2022 14:09:17 GMT

2022.4.219

RE: Debugging from VSCode with nRF Connect Extension

Einar Thorsrud — Thu, 05 May 2022 14:08:11 GMT

I see. Which version is nRF Connect for VS Code?

RE: Debugging from VSCode with nRF Connect Extension

diogodias — Thu, 05 May 2022 14:03:30 GMT

No problem.
Nothing happens, it just gets stuck in "Debugger requested to halt target..." and the debugger doesn't start.

My vscode version is 1.66.2 and nRF Connect Exntension Pack is v2021.9.1.

RE: Debugging from VSCode with nRF Connect Extension

Einar Thorsrud — Thu, 05 May 2022 13:57:46 GMT

Ah, sorry. I misread your question. No, you should be able to debug with the checkbox checked. I do not see anything obviously wrogn when browsing through the log in your original post. What happens when you try to debug with the "Enable debug options" box checked? And which VS Code version and version of the nRF plugins do you use?

RE: Debugging from VSCode with nRF Connect Extension

diogodias — Thu, 05 May 2022 13:52:13 GMT

Hi,

Thank you for your response.

Yes, I'm aware of code optimization and that it makes debug harder. With the CONFIG_DEBUG_OPTIMIZATIONS=y I was able to properly debug and my "problem" is solved. However, just out of curiosity, do you know why I cant debug the board if I check the "Enable debug options" in the build configuration? As you can see in the code that I posted, I get stuck in "Debugger requested to halt target...".

RE: Debugging from VSCode with nRF Connect Extension

Einar Thorsrud — Thu, 05 May 2022 11:02:11 GMT

Hi,

It is a general concept that compilers will do code optimization if configured to do so, and for release builds you typically always enable optimization. This can of course on speed, code size, etc. This changes the machine code so that it does not exactly map the C code, so it makes debugging harder. Therefor you often want to disable optimization when you debug. The "Enable debug options" in nRF Connect for VS Code causes optimization to be disabled, and also sets a few other options to further aid debugging VS code. If you want to permanently disable optimization you can do that, for instance by adding CONFIG_DEBUG_OPTIMIZATIONS=y to your prj.conf. See this post for more.