nRF Connect SDK 1.6.1 : Automatically confirming of firmware

[Mike Mascari]

Hi. 

We're using the out-of-the-box NCS 1.6.1 SDK / Zephyr / MCU boot process for our application. After upgrading the firmware, either via a dfu-utils flash to slot 1, or performing a DFU OTA (via the default MCU manager's SMP implementation -- CONFIG_MCUMGR_SMP_BT=y), the device successfully boots into the new version of the firmware. But despite us invoking: 

boot_write_img_confirmed();

during the new firmware's execution with a return code of zero, after a power-cycle, MCU is rolling back to the previous version.

Any thoughts on how/why to ensure that the boot image confirmation takes place successfully? We tried moving the code out of our start-up to a time-based call-back, but the firmware was still rolled back. 

[Håkon Alseth]

Hi,

 

the device successfully boots into the new version of the firmware. But despite us invoking: 

boot_write_img_confirmed();

during the new firmware's execution with a return code of zero, after a power-cycle, MCU is rolling back to the previous version.

Do you have the secondary slot located in external memory, or internal flash?

Could you share the log output of the process?

 

Kind regards,

Håkon