Problems with "Enable debug options"

Hi,

I have replicated the scenario you described myself using aws_iot sample with VS Code and NCS v1.9.1. I did not observe any issue, no matter if "Enable debug options" was checked or unchecked, .

Best regards,
Dejan

Hi Dejan,

Strange. I have staerted over, and the first time I debug the build configuration that has "Enable debug options" checked, it works fine. But all other debug sessions don't. I have attached three files with the printouts from "Debug console". One file is how it looks in the build configuration that doesn't have "Enable debug options" checked. The other two has the option checked. The one where debugging is working is the first debug session, the other one is how it looks for all other debug sessions. Is it possible to find any interesting information from this?

Has any other of your team tested to see if you can repeat this?

What does "Enable debug options" provide?

Best regards,
Lars

Hi,

As can be seen in debugging application, ENABLE_DEBUG_OPTIONS sets the following in the prj.conf
CONFIG_DEBUG_OPTIMIZATIONS=y
CONFIG_DEBUG_THREAD_INFO=y

Best regards,
Dejan

Hi,

Could you please update nRF Command Line Tools to the version 10.16.0 (and J-Link v7.66a)?

Best regards,
Dejan

Hi,

Now I have updated to version 10.16.0 of command line tools. I have tested quite a lot of times to debug, and it's a bit hard to figure out what is really happening. The behaviour is at least somewhat new.

Every other time that I debug, the board is disconnected, and then reconnected. Then debugging doesn't work. I attach the printouts from the debug console. In the window "Disassembly" it says "Disassembly not available". This behaviour is also present when "Enable debug options" is not checked.

The other times, when the board doesn't disconnect and reconnect, I have seen that either debugging works, or it doesn't. When debugging works, it will likely do that every other time (interwined with the disconnection behaviour) for a long period. And when debugging doesn't work, it will likely do that every other time for a long period.

Best regards,
Lars

Hi,

Now I have updated to version 10.16.0 of command line tools. I have tested quite a lot of times to debug, and it's a bit hard to figure out what is really happening. The behaviour is at least somewhat new.

Every other time that I debug, the board is disconnected, and then reconnected. Then debugging doesn't work. I attach the printouts from the debug console. In the window "Disassembly" it says "Disassembly not available". This behaviour is also present when "Enable debug options" is not checked.

The other times, when the board doesn't disconnect and reconnect, I have seen that either debugging works, or it doesn't. When debugging works, it will likely do that every other time (interwined with the disconnection behaviour) for a long period. And when debugging doesn't work, it will likely do that every other time for a long period.

Best regards,
Lars

Hi,

Could you try building unmodified NCS aws_iot sample directly (without making application from sample)?

Best regards,
Dejan

Hi,

Do you mean that I should select "Add an excisting application" so the build catalogues are created where the original example is placed? Doing that makes no difference, I get the exact same behaviour as I explained above.

Best regards,
Lars

Hi,

If you need debugger, you could try to use Ozone debugger instead of VS Code one.

Best regards,
Dejan

Hi,

Do you have debugging repeatedly working for aws_iot?

I got the feeling that you wrote something in a previous post, that you have reported this issue internally. Have you erased that part?

Are you not able to fix debugging in VS Code for aws_iot?

Best regards,
Lars

Hi,

I am just suggesting you to use Ozone as a debugger if you have an issue with VS Code debugger, but you do not have to use it if you do not want to do that.

Best regards,
Dejan