nRF5340 multi-image DFU not getting reverted when it should

[ronbo999]

Hi. I'm testing the multi-image DFU in nRF Connect SDK 1.7.0. I'm seeing an issue with the firmware images not getting reverted when it should.

Here's what I'm doing:

1) I built an example project that does not call the boot_write_img_confirmed() or the boot_write_image_multi().

2) Flashed the app core firmware to the mcuboot_secondary partition located in the external flash.

3) Flashed the net core firmware to the mcuboot_secondary_1 partition located in the external flash.

4) Hit the reset button.

5) Verified that both the app core and the net core are updated.

6) Hit the reset button.

7) mcuboot doesn't revert the app core and the network core firmware to the previous versions.

*** Booting Zephyr OS (1.16) build v2.6.99-ncs1  ***
I: Starting bootloader
I: Swap type: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS (1.16) build v2.6.99-ncs1  ***
Done flashing the app firmware to mcuboot_secondary partition (128868 bytes)
Done flashing the network firmware to mcuboot_secondary partition (161976 bytes)
Starting Nordic UART service example 1.2
*** Booting Zephyr OS (1.16) build v2.6.99-ncs1  ***
I: Starting bootloader
I: Swap type: test
I: Swap type: test
I: Image upgrade secondary slot -> primary slot
I: Erasing the primary slot
I: Copying the secondary slot to the primary slot: 0x1f768 bytes
I: Image upgrade secondary slot -> primary slot
I: Erasing the primary slot
I: Copying the secondary slot to the primary slot: 0x278bc bytes
I: Turned on network core
I: Turned off network core
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS (1.15) build v2.6.99-ncs1  ***
Starting Nordic UART service example 1.2
*** Booting Zephyr OS (1.16) build v2.6.99-ncs1  ***
I: Starting bootloader
I: Swap type: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS (1.15) build v2.6.99-ncs1  ***
Starting Nordic UART service example 1.2

[ronbo999]

3.5) Call the following functions to request an upgrade.

boot_request_upgrade_multi(0, BOOT_UPGRADE_TEST); /* mcuboot_secondary */
boot_request_upgrade_multi(1, BOOT_UPGRADE_TEST); /* mcuboot_secondary_1 */

[Sigurd]

Hi,

I believe this is expected, as CONFIG_BOOT_UPGRADE_ONLY is set. (this also sets MCUBOOT_OVERWRITE_ONLY).

See this link: http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf5340.html?highlight=config_boot_upgrade_only#simultaneous-multi-image-dfu

[ronbo999]

Hi,

I checked to see if the MCUBOOT_OVERWRITE_ONLY is set and I don't see it being set in the autoconf.h file of the application and mcuboot.

[Sigurd]

But I assume you have CONFIG_BOOT_UPGRADE_ONLY. (MCUBOOT_OVERWRITE_ONLY is not a Kconfig).

[ronbo999]

Yes. I have the CONFIG_BOOT_UPGRADE_ONLY set to "y" in mcuboot.conf file.