Zephyr MCUBoot Application Debug - deadbeef everywhere

[denis]

I have an Zephyr application on the nRF5340 that I've been working on.  I can debug fine in SES without a boot loader.  However, when I add MCUBoot into the mix then everything loads and starts from SES, but if I break then the addresses, registers, etc, all look incorrect and show "deadbeef".  If I set a breakpoint on a line in my application it is never hit.  Is there some trick to setting up SES properly so I can debug in the presence of MCUBoot?

This is what I have in my prj.conf with this issue occurs:

CONFIG_SECURE_BOOT=y

CONFIG_BOOTLOADER_MCUBOOT=y

[Carl Richard]

To follow up on the edit of my last comment: The issue stems from the readback protection of the nRF5340, which is enabled by secure boot. SES is unfortunately not designed to handle this, but a coworker suggests that you could use GDB for debugging instead. Apologies for the inconvenience.

Best regards,
Carl Richard

[denis]

Is there a way to build secure boot for debug - without readback protection?

[Carl Richard]

I got back from the developers that there isn't any trivial way to do this. Apologies for the inconvenience.

Best regards,
Carl Richard

[denis]

I'm using VSCode now for development.  So closing this issue.