Meaning
Redundancy mechanisms in embedded microcontrollers execute a reversion to a previously known functional state when a newly applied update fails to boot correctly. This action of firmware fallback prevents permanent system lockup or loss of remote connectivity during over-the-air updates. It relies on a multi-stage bootloader that maintains at least two separate execution images in non-volatile storage.
The mechanism remains inactive unless a watchdog timer expires or a hardware check fails.
Recovery Trigger
The system begins the transition when the primary application partition contains corrupted files or encounters a continuous crash loop. During a typical startup sequence, the hardware initializes a hardware-based watchdog timer that must be cleared by the application within a designated window. If the new software hangs or crashes before clearing the timer, the board resets and the bootloader selects the older, verified version.
Such action ensures that the device remains accessible for subsequent updates even after a critical failure.
Image Verification
The bootloader compares checksums or digital signatures of the active partition to confirm the integrity of the binary file. If the verification fails, firmware fallback is initiated immediately to run the working backup partition. The backup resides in a protected sector of flash memory that cannot be overwritten by routine update processes.
Rollback Limit
The recovery mechanism assumes that the older software version remains compatible with the current hardware configuration. If a hardware revision has broken backward compatibility, the fallback routine cannot restore full functionality.