Hello all, I am following up on a related issue regarding mcuboots partitioning and image validation. (link to previous MCUBoot QA forum). I have devices out in the field that i would like to update and change the partition formatting to include a settings section in NVM. We previously discovered and confirmed that MCUboot uses SHA to validate an image. How ours got stuck is that the image initially starts as all 0xFF in the settings partition, matching the needed padding for the image validation. When we saved settings it "corrupted" the image, essentially locking the image in slot one due to verification errors. I have thought of a few ways to work around this issue (resetting the settings partition to all 0xFF before dfu, JTAG only), but all current solutions are complex and situational.
Question: Hoping to get insight into the MCUBoot process to understand paths to introduce features that modify partitions without breaking the DFU process. Restraints are that devices cannot come out of the field to be JTAG'd.
