ota error:The image does not have a valid mcu header

[666]

Hi all,

nrf54l15dk,v3.0.1,peripheral_uart demo and no changes have been made.

Then add the following content to prj.conf

sysbuild.conf

mcuboot.conf

Finally, use the OTA file under build to upgrade

Looking forward to your reply！

[Priyanka]

Hi,

Could you take a look at the following and check if it helps?

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/device_guides/nrf54l/fota_update.html#fota_over_bluetooth_low_energy 

https://devzone.nordicsemi.com/f/nordic-q-a/118439/nrf54l15-fota-2-8-0-sdk-clarification?ReplyFilter=Answers&ReplySortBy=Answers&ReplySortOrder=Descending 

Regards,

Priyanka

[666]

HI

According to the configuration in my question，I can run normally in 2.8.0, but according to the same configuration , the situation shown in the picture will appear in v3.0.1. From the information you provided, I don't see any difference between the two versions. Do you have any suggestions？

Looking forward to your reply！

[666]

In autoconf.h, the same configuration is v3.0.1 on the left and v2.8.0 on the right; It can be found that the same configuration can be compiled with different key configurations. I don't know if this will have an impact. Moreover, v3.0.1 also defaults to enabling SB_CONFIG_SUPPORT_BOOT_ENCRYPTION. When I set it to n, it will compile and report an error. Changing it to SB_CONFIG_BOOT_SIGNATURE_TYPE_RSA=y will also cause OTA to fail. Do you have any suggestions？

[Isobel Hermann]

Hi

Do not change the signature type unless:

The boot ROM / secure boot configuration is compatible.

Currently deployed devices are updated synchronously (usually not possible for OTA unless the bootloader is updatable).

Or you can add some more knowledge...

[Isobel Hermann]

If OTA worked in v2.8.0, use that as a base config for v3.0.1 and migrate carefully, only changing what’s required by the new SDK Poor Bunny.