Android based FOTA doesn't work with nRF54L15 (2.9.0)

RE: Android based FOTA doesn't work with nRF54L15 (2.9.0)

LHZ — Thu, 06 Mar 2025 14:16:09 GMT

Hi Einar,

Thank you for the reply. The reason of time-out makes sense. I will hold and wait for the new app release.

Just curious, the same setting works on nRF52840DK while 54l15 fails. Is that due to the smaller size of 52840's memory?

Thanks

RE: Android based FOTA doesn't work with nRF54L15 (2.9.0)

Einar Thorsrud — Thu, 06 Mar 2025 07:10:37 GMT

Hi,

I see. Errror 147 is a Timeout error that was introduced in Android 15. The likely reason you are getting it is that when you select "test and confirm", the Android app will first issue a test command, and the nRF will reboot at MCUboot will swap in the new image. This takes some time, and if it takes longer than the configured wait time in the app, it will fail when attempting to re-connect to do a confirm. We will increase the default esitmated swap time in the Anroid app to improve this in the future.

RE: Android based FOTA doesn't work with nRF54L15 (2.9.0)

LHZ — Wed, 05 Mar 2025 19:59:47 GMT

Thank you for the infomation.

I am still confused about the symptons: iOS works and 52840 works, but Android and 54L15 combo doesn't work.

I will skip the FOTA and hop to our next feature. I will pay a revisit later in case something gets changed in new releases.

Thank you

RE: Android based FOTA doesn't work with nRF54L15 (2.9.0)

Einar Thorsrud — Mon, 03 Mar 2025 14:43:39 GMT

Did you specify in the app that you wanted to confirm? If not, it is expected that it does not happen.

[quote user="LHZ"]I can try boot_write_img_confirmed() for prototyping, but please advise if that is also a proper way for a production release. [/quote]

Yes, you can do this in production as well. For most applications, it makes sense to do it. In some special cases, applications may want to do some self-check before confirming and perform a reset if it fails (in order to revert back to the old firmware), but this is not typically done.

RE: Android based FOTA doesn't work with nRF54L15 (2.9.0)

LHZ — Mon, 03 Mar 2025 14:29:05 GMT

Hello Einar,

Thank you for the reply!

Yes, I am using the latest Nordic "Device Manager" and "nRF Connect" to do the FOTA. Both app failed with the same way. I didn't use any customized app.

I used a fresh LBS example from 2.9.0. I followed the exercise example from Nordic Academy and didn't change any extra.

I reported more details with output log in this thread:

The state status is Unknown(147) after FOTA DFU on 54L15

I can try boot_write_img_confirmed() for prototyping, but please advise if that is also a proper way for a production release.

Thank you very much!

RE: Android based FOTA doesn't work with nRF54L15 (2.9.0)

Einar Thorsrud — Mon, 03 Mar 2025 12:31:41 GMT

Hi Haizhou,

Are you using a custom app on the Android device or one of our Android apps? If so, which and how to you use it?

You write that the new firmware is used once, but after a reset the old firmware is used again. This indicate that the test flag is set, and not the confirm flag. With test, the new image is booted once, and unless the firmware confirms itself, it is reverted after the next boot. With confirm, the new image is used permanently.

PS: If you want the firmware to confirm itself, that can be done using boot_write_img_confirmed()

Br,

Einar