MCUBoot rolling back to previous image after uploading new app binary, unless confirm only is choosen.

[waatff]

Hi! I'm developing using nrf52840DK and have an issue with DFU. When I'm uploading new app image and choose test and confirm, image is uploaded but after resetting DK, MCUBoot rolls back to previous image. When uploading an image the confirm only option is choosen, everything works fine and MCUBoot uses new image even after resetting, am I doing something wrong or should I add any "confirm image" callback manually in the code?

[Menon]

Hello,

Could you share the SDK version you are trying with? Do you have any logs to confirm that the  MCUBoot rolls back to previous image, or how do you test that the old image is active after an update? 

am I doing something wrong or should I add any "confirm image" callback manually in the code?

You don't need to add anything inside the code but this might be an issue with the new images (sometimes broken) and that's the reason mcuboot is rolling back to old image. By giving the tag "confirm" the option to revert is not given to mcuboot. See the section Boot swap types

Kind Regards,

Abhijith

[waatff]

I'm currently using ncs v2.3.0. I test it by changing the device name in prj.conf. When I'm trying to upload new image via nrf connect for mobile, choosing test and confirm, the app gets stuck at 'validating' while in the same time the device automatically reboots with new image. Device's name changes accordingly to new image config, but then after manually rebooting device, mcuboot has swap type revert and goes back to an old image, which can be tested by looking at device's name. Changes between old and new image are really simple, like disabling passkey.