Zephyr MCUBoot Application Debug - deadbeef everywhere

RE: Zephyr MCUBoot Application Debug - deadbeef everywhere

denis — Wed, 27 Oct 2021 01:25:54 GMT

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

RE: Zephyr MCUBoot Application Debug - deadbeef everywhere

Carl Richard — Fri, 12 Mar 2021 13:23:08 GMT

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

Best regards,
Carl Richard

RE: Zephyr MCUBoot Application Debug - deadbeef everywhere

denis — Mon, 08 Mar 2021 16:29:05 GMT

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

RE: Zephyr MCUBoot Application Debug - deadbeef everywhere

Carl Richard — Mon, 08 Mar 2021 10:24:19 GMT

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

RE: Zephyr MCUBoot Application Debug - deadbeef everywhere

Carl Richard — Wed, 03 Mar 2021 13:01:41 GMT

Hi again!

Did some more research/testing on this and figured out that my suggestion most likely won't work. The issues you are seeing are due to SECURE_BOOT being enabled (not the MCUBoot bootloader) as the immutable bootloader rejects the debugging image flashed from SES due to the format being different (.elf vs .hex). I have yet to figure out how to solve this, but the check must be disabled (temporarily) at least. Will update you when I know more.

Edit: while SECURE_BOOT is indeed the culprit the issue is not the image validation.

Best regards,
Carl Richard

RE: Zephyr MCUBoot Application Debug - deadbeef everywhere

Carl Richard — Wed, 03 Mar 2021 10:34:14 GMT

Hi, Denis!

Thanks for reaching out. Could you try to reopen the project with a "Clean Build Directory" in Segger Embedded Studio and see if that helps?

Best regards,
Carl Richard