Serial Numbers and Hardware Revisions
Maintain stable device identity and explicit compatibility across board changes.
Arduino-compatible frameworks, ESP-IDF/FreeRTOS, PIC/AVR/STM32/RP-class systems; apply exact vendor documentation for the selected MCU.Architecture
Immutable manufacturing identity + readable label/QR + firmware compatibility manifest.
Security and recovery risks
- Serial numbers are identifiers, not authentication secrets.nNever silently reuse a retired serial.nKeep compatibility logic explicit and tested.
Implementation procedure
- Define product, serial and check-digit policy.nDefine hardware revision change rules.nStore identity in protected manufacturing data.nPrint and verify human/machine-readable labels.nReject incompatible firmware before writing.
Starter code / configuration
product=TCS-NODE; serial=TCSP-000001; hardware=A1Verification 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.