Old Firmware Comes Back After FOTA and Second Reboothttps://devzone.nordicsemi.com/f/nordic-q-a/117314/old-firmware-comes-back-after-fota-and-second-rebootToolchain v2.70, SDK v2.7.0, VS Code, Windows I&#39;m applying an application firmware update by calling fota_download_start_with_image_type with DFU_TARGET_IMAGE_TYPE_MCUBOOT, and then rebooting at a convenient time once the download has reported as completeden-USTelligent Community 13Mon, 16 Dec 2024 00:16:02 GMTRE: Old Firmware Comes Back After FOTA and Second Reboothttps://devzone.nordicsemi.com/thread/515004?ContentTypeID=1Mon, 16 Dec 2024 00:16:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:17ff9e03-7e90-40fe-a85b-3f713396bc9aMike Granby<p>I can get a similar effect with the Segger: Perform a FOTA from say 1.2 to 1.3, and then program the device with dev code using from Visual Studio Code. Upon restarting, it comes up not with the dev code, but with 1.2 again. And then I have to program it once more to get the dev code to stick. It&#39;s as if the old image is still then and is being applied on reboot.</p><div style="clear:both;"></div>