nrf54l10: FOTA issue

[payalD]

Hello Team,

I am currently using the nRF54L15 DK with NCS version 2.9.0 for development and compiling code for the nRF54L10 board.

I am trying to implement FOTA updates over BLE. To facilitate this, I have added the following lines to my configuration files:

1. In `sysbuild.conf`: `SB_CONFIG_BOOTLOADER_MCUBOOT=y`

2. In `prj.conf`: `CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y`

After compiling the code, the `dfu_application.zip` file is generated, which I am using for the FOTA process through the nRF Connect Device Manager app, as instructed in nRF Connect SDK Intermediate.

I have successfully flashed the v1 application onto the board and am attempting to perform a FOTA using the v2 `dfu_application.zip`. The FOTA process completes successfully, and the application appears to switch to the v2 image. However, upon resetting the board, it reverts back to the v1 image.

Could you please help me identify if I missed any settings or configurations and resolve the issue?

Thank you!

[Amanda Hsieh]

Hi, 

If an image is tagged as “confirm”, MCUboot will swap it into the primary slot permanently.
If an image is tagged as “test”, MCUboot will swap it into the primary slot for one reset cycle. Unless the image is then confirmed while running, MCUboot will swap back the old application to the primary slot on its next reset. We will try out both modes in the exercises.

After clicking “Select file” to choose zephyr_signed.bin, and pressing to “Start” on the nRF Connect Device Manager app, choose the “Test & Confirm” option to first tag the image with “test”, and after the swap, the app will reconnect to the chip and confirm the image before it reverts. 

Regards,
Amanda H.