Automatic Rollback and Recovery
Return to confirmed firmware when the candidate crashes, fails health checks or misses confirmation.
Arduino-compatible frameworks, ESP-IDF/FreeRTOS, PIC/AVR/STM32/RP-class systems; apply exact vendor documentation for the selected MCU.Architecture
Bootloader selects pending slot → firmware self-test → confirm or watchdog/reset → bootloader rollback.
Security and recovery risks
- A network connection alone must not confirm firmware.nProtect rollback metadata against corruption.nDocument recovery when both application slots fail.
Implementation procedure
- Define candidate confirmation criteria.nSet boot-attempt and confirmation limits.nSimulate crash before confirmation.nVerify prior slot boots and records rollback reason.nTest factory/recovery image path.
Starter code / configuration
if (mandatory_self_tests_pass()) confirm_running_image();Verification evidence
| Test | Expected | Evidence |
|---|---|---|
| Nominal boot | Correct version and hardware revision reported | Captured boot log |
| Fault recovery | Defined safe state and reset reason | Fault-injection record |
| Power cycle | No corrupt configuration or unsafe output | Repeated-cycle log |
Required release artifacts
- Versioned firmware binary and SHA-256
- Source revision / build identifier
- Board and hardware-revision compatibility list
- Test report and known limitations
- Recovery image and factory-reset procedure
- Provisioning/calibration schema
- Release approval record
Local browser tools
Firmware production workbench
A/B update exercise
OTA and automatic rollback simulator
Advance one validated stage at a time. A failed boot test returns the device to the previous slot.
- Running confirmed firmware from Slot A.
Release gate
Production-readiness checklist
A downloadable release decision is generated only after every mandatory control is confirmed.