RE: [NRF91] B0 + MCUBOOT (+ SPM + APP) -> updating MCUBoot over fota results in bootloop

Simon — Wed, 28 Apr 2021 12:48:32 GMT

It seems like this check: https://github.com/nrfconnect/sdk-nrf/blob/v1.5.0/samples/bootloader/src/main.c#L62 evaluates to true, which will make the bootloader check S0 first. The bootloader then finds a valid image in S0 and will boot that.

In your case, either s1_info is set to NULL, which means the magic value was not found, or the firmware version of S0 was greater or equal than the firmware version of S1. Could you add some printk's and figure out what's the case?

I may also be useful to take a look at the file signed_by_mcuboot_and_b0_s1_image_update.bin, e.g. by opening it up in HEX Editor Neo. The fw info struct (which contains the firmware version and the magic value) should be stored inside the signed_by_mcuboot_and_b0_s1_image_update.bin file at the offset specified by CONFIG_FW_INFO_OFFSET (Take a look at <application>\build\mcuboot\zephyr\.config), to see what CONFIG_FW_INFO_OFFSET is equal to.

If anything is unclear, please tell me and I will try to elaborate.

Best regards,

Simon

RE: [NRF91] B0 + MCUBOOT (+ SPM + APP) -> updating MCUBoot over fota results in bootloop

Jelmer — Tue, 27 Apr 2021 17:29:19 GMT

Thanks Simon

RE: [NRF91] B0 + MCUBOOT (+ SPM + APP) -> updating MCUBoot over fota results in bootloop

Simon — Tue, 27 Apr 2021 11:13:57 GMT

Hello Jelmer.

Sorry for the delay on this, I'll look into it the next days.

BR,

Simon