Problems with "Enable debug options"

Hi,

I am facing a problem with the selection "Enable debug options" when creating a build configuration. I use nRF connect SDK 1.9.1 with VSCode. I create an application from sample aws_iot. Then I make two different build configurations, one with "Enable debug options" checked, and one with the option unchecked. The one that has debug option enabled is not possible to debug (it may work once, but all other debug sessions do not work). But the one that doesn't have the option enabled works fine to debug.

How come there is a difference?

What does "Enable debug options" provide?

Best regards,
Lars

Parents
  • 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 Dejans, Lars. 

    I also have exactly the same symptoms as Lars, with the Enable debug options checked the debug is non-functional, (AKA useless). 

    I am using 

    SDK 2.1.0

    nrf Debug 

    asset_tracker_v2 with aws_iot enabled. 

    turning off the debug option in build allows me to start / restart / stop with the debug toolbar, but the breakpoints are all over the place, probably because the build is optimised? 

    Any suggestions as to resolution on this would be appreciated. 

    Regards

    Marshall

Reply
  • Hi Dejans, Lars. 

    I also have exactly the same symptoms as Lars, with the Enable debug options checked the debug is non-functional, (AKA useless). 

    I am using 

    SDK 2.1.0

    nrf Debug 

    asset_tracker_v2 with aws_iot enabled. 

    turning off the debug option in build allows me to start / restart / stop with the debug toolbar, but the breakpoints are all over the place, probably because the build is optimised? 

    Any suggestions as to resolution on this would be appreciated. 

    Regards

    Marshall

Children
Related