After upgrading mcuboot, the device crashes upon power-up

[Carter]

hi,

  After upgrading mcuboot from NCS 2.6.1 to NCS 2.9.0, the upgrade file is downloaded, and the device restarts and runs normally. The mcuboot version number and active slot are updated as expected. However, when the device is powered off and then powered on again, it fails to work properly, almost as if it has crashed. What could be the cause of this issue?

In NCS 2.6.1, the default value of CONFIG_PM_PARTITION_SIZE_MCUBOOT is 0xc000, while in NCS 2.9.0, the default value is 0xbe00. A bug related to the MCUboot partition size was fixed on October 24, 2024. Could this bug have affected the upgrade failure?

Link:Fix MCUboot partition sizes

[Sigurd Hellesvik]

Hi,

In NCS 2.6.1, the default value of CONFIG_PM_PARTITION_SIZE_MCUBOOT is 0xc000, while in NCS 2.9.0, the default value is 0xbe00. A bug related to the MCUboot partition size was fixed on October 24, 2024. Could this bug have affected the upgrade failure?

Generally, you need to follow the Static partitioning requirement. Im not 100% sure since it is just the headers in this case.

But try to copy build/partitions.yml into pm_static.yml and then build the project for v2.9.0. Does DFU work then?

Regards,
Sigurd Hellesvik

[Carter]

I tried copying build/partitions.yml into pm_static.yml.After upgrading mcuboot from NCS 2.6.1 to NCS 2.9.0, the upgrade file is downloaded, and the device restarts and runs normally. The mcuboot version number and active slot are updated as expected. However, when the device is powered off and then powered on again, it fails to work properly, almost as if it has crashed. 

[Sigurd Hellesvik]

Do you have logs from NSIB?

[Carter]

How to view the logs of NSIB?

[Sigurd Hellesvik]

When I add NSIB and MCUboot to hello world, it looks like this:

A: NSIB logs

B: MCUboot logs

C: Application logs

So for the DK, it logs by default at least

[Carter]

Can you provide the example you added?