Diagnostic Export and Service Bundle
Export useful health evidence while removing credentials, personal data and raw cryptographic material.
Arduino-compatible frameworks, ESP-IDF/FreeRTOS, PIC/AVR/STM32/RP-class systems; apply exact vendor documentation for the selected MCU.Architecture
Reset/events/metrics/config summary → allowlist/redaction → bounded JSON bundle → user-approved export.
Security and recovery risks
- Never dump arbitrary memory or complete configuration.nMake export user/service initiated and visible.nSign or checksum bundles when authenticity matters.
Implementation procedure
- Define a strict export allowlist.nInclude version, hardware, reset history and self-test results.nRedact tokens, passwords, keys and exact private locations.nLimit history size and validate JSON.nTest export after faults and factory reset.
Starter code / configuration
{"schema":1,"version":"1.2.0","hardware":"A1","reset_reason":"watchdog","secrets":"REDACTED"}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.