You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present, the jump out of the revert tests happens when an erase or write is about to happen, however when developing the swap using offset algorithm, it was noticed (on a real board) that if the device was reset after the final sector erase but before the function returned to the loader.c file, upon reboot MCUboot failed to read the image headers and boot failed. Therefore, it would also be good to have a mirrored fail with revert setup whereby the requested write/erase is allowed then the simulated reboot occurs, which would allow for tested these sorts of edge cases
The text was updated successfully, but these errors were encountered:
At present, the jump out of the revert tests happens when an erase or write is about to happen, however when developing the swap using offset algorithm, it was noticed (on a real board) that if the device was reset after the final sector erase but before the function returned to the loader.c file, upon reboot MCUboot failed to read the image headers and boot failed. Therefore, it would also be good to have a mirrored fail with revert setup whereby the requested write/erase is allowed then the simulated reboot occurs, which would allow for tested these sorts of edge cases
The text was updated successfully, but these errors were encountered: