Manufacturing Self-Test
Run deterministic fixture tests and produce a per-device pass/fail record before packing.
Arduino-compatible frameworks, ESP-IDF/FreeRTOS, PIC/AVR/STM32/RP-class systems; apply exact vendor documentation for the selected MCU.Architecture
Fixture command → board test mode → rail/GPIO/bus/radio checks → signed/controlled result record.
Security and recovery risks
- A pass requires measured limits, not only completion.nTest fixtures need maintenance/calibration.nPrevent production units from entering unsafe unrestricted test mode.
Implementation procedure
- Enter test mode through controlled interface.nVerify identity and firmware version.nTest rails, memory, GPIO and required buses.nRun bounded sensor/radio tests with known fixtures.nFail closed and record measured values.
Starter code / configuration
SELFTEST: identity, rails, flash, RAM, GPIO, I2C, radio, current, resultVerification 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.