CONFIG_BOOT_SWAP_USING_MOVE mcuboot operation

[m0sf3tz]

Hi,

Much like the poster below, I have ran into some issues during FOTA when my flash usage gets VERY CLOSE TO 100% (Much less than a page left), disabling some features in my FW (getting close to 80% flash usage) I can do FOTA just fine, so It seems like the problem is w/ my flash usage.

https://devzone.nordicsemi.com/f/nordic-q-a/78984/big-primary-image-prevents-fota

In the above thread, it was mentioned that the last page needs to be persevered for FOTA, does this mean the final page in the FLASH or final page per image?

furthermore, can the difference between

CONFIG_BOOT_SWAP_USING_MOVE and CONFIG_BOOT_SWAP_USING_SCRATCH be explained?

I will be running some continues integration for FOTA, from the documentation that I read, CONFIG_BOOT_SWAP_USING_SCRATCH hammers the swap block with write/erase cycles - but I can't find any details on CONFIG_BOOT_SWAP_USING_MOVE. Is there some numbers for how many times FOTA can be ran before the blocks wear out using CONFIG_BOOT_SWAP_USING_MOVE?

[m0sf3tz]

For what it's worth - I had no issues with CONFIG_BOOT_UPGRADE_ONLY=y, even with a very large flash footprint.

[Alexandre Desgagne]

I'm not able to set some option inside of my prj.conf such as CONFIG_BOOT_UPGRADE_ONLY. When I'm trying to set these configurations, I'm getting a warning like this:  warning: attempt to assign the value 'y' to the undefined symbol BOOT_UPGRADE_ONLY.

Do you have an idea of why I'm not able to set these?

Thanks,

Alexandre

[Amanda Hsieh]

Hi, 

You should use a mcuboot.conf under child_image to include that config. 

Please back to your case to continue the discussion. Thanks.  

-Amanda