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，

What is the solution? Have you tested it？

[666]

in V3.0.1 ,adding SB_CONFIG_BOOT_SIGNATURE_TYPE_RSA=y（or SB_CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y） to  sysbuild.conf resulted in normal running. 

Is there any restriction on v3.0.1 in OTA？

[Priyanka]

Hi,

I am checking internally whether there are any differences in the versions for OTA. Please expect a slight delay as it's the summer holidays here and we are slightly short staffed at the moment.

Could you try with the v2.9.0? Also, please note that in newer SDK (from v3.x.x) one needs to use Sysbuild, so maybe you had CONFIG_BOOT_SIGNATURE_TYPE_RSA in mcuboot.conf before and now in v3.0.1 since there is Sysbuild, SB_CONFIG_BOOT_SIGNATURE_TYPE_RSA is what helps. 

Please do verify these in the meantime.

-Priyanka