debugging MCUboot

[Jason]

NCS3.1.1, NRF52840, Windows, VScode

I have been trying to add MCUboot to my product, without success.

I believe there are known issues related to debugging when MCUboot is enabled. 

I believe I need to flash the merged.hex, then use "attach" to debug, and I need to specify "flash breakpoints" = false, and I need to supply the path to my elf file. But when I try to edit the vscode launch.json, I cannot see a way to make the configuration with these 3 things. 

There is no way to specify the elf file if I specify "attach"

Is there any info on how to proceed?

[Jason]

I want to step into my "usb_savedata_init()" function 

It;s the same if I remove my code and just put in a while loop with k_msleep

[Jason]

I finally got RTT viewer to work and it looks like I have an exception before it even gets to main. This is the first time I've managed to get anything from the logging. And I've noticed that I now get a stack trace in the debugger. If I connect with RTT with "force go on connect" and then if I use the debugger pause button then I can see where it gets stuck. But I have no way of stepping through the code prior to the crash. 

[Hung Bui]

Hi Jason, 
My understanding is that you want to debug your application, not MCUBoot it self, correct ? 
If it's the case I don't see why it wouldn't work. 

Dfu_target is our library to support DFU, it doesn't belong to MCUBoot. DFU_target run in the application, not in MCUBoot. 

Have you build your application with -Og ? 



I did a quick test here and can debug an application (attached) with MCUBoot included. 



Please check if you can debug this application (NCS v3.1.0)
 8688.peripheral_lbs_smp.zip