Hardware And Firmware

Hardware And Firmware docs cover embedded generation, HAL/RTOS/BSP integration,

secure boot, HIL campaigns, mission IO, space assurance, and physical evidence

intake.

Current Boundary

0x0 has emulator and virtual hardware evidence, secure-boot manifest checks,

dry-run flashing evidence, virtual probes, certification bundles, and physical

evidence intake. The repository default inventory does not claim an attached

physical board.

Secure Boot

Secure boot evidence must identify:

• target id;
• board id;
• serial;
• firmware hash;
• root key id;
• verification status.

HIL Campaigns

HIL campaigns must cover reset, power, bus, storage, timing, and watchdog

faults before a target can be claimed as physical-ready.

Operator Evidence

Physical target claims require flashing receipt, monitor trace, recovery trace,

HIL evidence, and operator signoff. External certification approval remains an

external authority decision.