Debugging MCUboot in SES

[RAS_ID]

Hi

My requirement is to upgrade the application firmware on the nRF52840-DK from another processor using SPI interface, and I am trying to understand the code to plug-in SPI interface. For that, I need to debug the code and perform step by step operation and someone help me to explain the functions called. I am really interested to understand the following.

1. How to debug the MCUboot code?

2. boot_console_init()

3. boot_serial_start()

4. bs_upload() and cbor_   functions

5. boot_go() and do_boot()

6. sequence of these functions because I am not understanding it completely.

Thanks,

Ram

[Simon]

Debugging/inspecting code can be done through a debugger tool, or through logging. For this case I think to the easiest and most convenient approach is to just add some logging inside the mentioned functions.

Logging

• Add #include <sys/printk.h> at the top of the file (e.g. boot_serial.c) and use printk("This will get logged in a Terminal");. E.g. add printk("Inside boot_serial_start()\n") in boot_serial_start()
  • You could also use BOOT_LOG_INF("This will get logged");
• Then you should open a serial terminal (open several terminals, since the nRF9160 DK exposes several COM ports) to display the messages, e.g. use Termite with these settings

Debuging options:

• Ozone: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/tools/nordic_segger.html#segger-ozone
• SES: 3.2 Debugging
• GDB

Best regards,

Simon

[RAS_ID]

Thanks!