Good afternoon.
We're using nrf Connect for mobile to perform DFU over BLE to an nrf5340-based module with firmware built using the nrf connect 1.6.1 SDK and its associated MCU boot loader. We've enabled this in our app using: CONFIG_MCUMGR_SMP_BT=y and advertising as connectable. We can deploy firmware without an issue. What we'd like to do is also push firmware that executes without confirmation and then reboots into the original firmware. If we use dfu-utils over a USB interface, we can do this by simply not invoking the boot_write_img_confirmed() function in the pushed firmware. But when we use nrf Connect for mobile, it appears that it is writing the firmware with "test and confirm" set automatically, so our "transient" firmware becomes the primary firmware loaded. Is there something we should be doing in nrf Connect for mobile settings (iOS), a change to the firmware packaging (currently a .bin), or a change to mcu code (not ideal) that would allow us to push firmware for execution and automatic rollback?
Thank you!
