Factory Reset and Recovery
Return user configuration to a defined state without accidentally destroying required manufacturing identity.
Arduino-compatible frameworks, ESP-IDF/FreeRTOS, PIC/AVR/STM32/RP-class systems; apply exact vendor documentation for the selected MCU.Architecture
Authenticated reset request → safe outputs → selective erase → integrity check → provisioning/recovery state.
Security and recovery risks
- Do not erase serial/calibration automatically unless policy requires it.nPrevent remote unauthenticated reset.nDocument ownership transfer separately.
Implementation procedure
- Classify user, service, calibration and manufacturing data.nRequire physical presence or authenticated command.nStop outputs and network sessions safely.nErase only documented partitions/keys.nTest interrupted reset and repeated reset.
Starter code / configuration
factory_reset(PRESERVE_SERIAL | PRESERVE_HW_REV | PRESERVE_CALIBRATION);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.