# SMI integrated implementation and build evidence

Status: captured
Type: evidence
Updated: 2026-07-14
Next Action: inventory the connected setup and insert an approved reference card, then execute the hardware checklists
Campaign Reason: Historical record from campaign 010-qualify-firmware-negative-and-recovery-behavior; retained independently after campaign closure and requires no separate owner-queue execution.
Campaign: standalone
Parent: work/maps/map-smi-firmware-stabilization-and-qualification.md

## Implemented candidate

- Startup semantic validation runs after redundant VEEPROM CRC/version block
  selection. Invalid commissioning identity and unsafe controller profiles are
  inhibited without silently enabling hardware or erasing identity/calibration.
- Retained semantic findings are visible through service code 473.
- Destructive service code 472 uses two-stage confirmation. The final screen
  states `ALL DATA ON THE SD CARD WILL BE PERMANENTLY LOST`; Cancel does not
  request format or evaluator start.
- The SD-thread evaluator writes 44,640 production-shaped records into 744 files
  per mirror, checks 1/2/7/31-day checkpoints, performs exact readback,
  byte-for-byte A/B comparison, non-correcting FileX media checks, fail/stop
  latching, and JSON result output.
- Production log queue and existing SD requests retain priority; evaluator work
  yields after every bounded slice.

## Automated checks

All passed on 2026-07-14:

- `script/check-config-semantic.ps1`: 11/11 checks.
- `script/check-sd-evaluator.ps1`: 14/14 checks.
- `script/test-sd-evaluator-model.ps1`: 10/10 host model checks.
- `script/check-sd-safety.ps1`: 10/10 checks.
- `git diff --check`: no whitespace errors (line-ending conversion notices only).

## Isolated clean builds

Both builds used `script/headless-e2-build.ps1`, a fresh staged project, and a
fresh e2 studio workspace. Packaging validation passed.

| Artifact | Bytes | SHA-256 |
| --- | ---: | --- |
| Debug `7520553_SMI_FW.elf` | 14,731,184 | `F109969578502548B08139D0E40A6519C9815F0F9CDDF0C438C6F4D043BB22FA` |
| Debug `7520553_SMI_FW.srec` | 8,477,466 | `E3AC4EC59CA76184040B6BA63BE88BFAE8759712EC20F538B7AEF243700DA90A` |
| Release `7520553_SMI_FW.elf` | 11,069,696 | `23DB5050C077A9F9AA907A85320468490F02472E21A54C8FBB4BB7C9E758304D` |
| Release `7520553_SMI_FW.srec` | 8,477,466 | `ADE296F71313D3D3DADCBDBB94AFD9A80988484B3AFA7EE0E1398B52A26276DE` |

Versioned `00_04_12` artifacts were generated and matched their corresponding
stable artifacts during packaging.

## Physical interface audit

- J-Link driver is connected and healthy: USB serial `69664082`.
- No J-Link or e2 studio process was active after the builds.
- USB disk 1 reports `Generic Mass-Storage`, `RAW`, `No Media`, size `0`.
- Drive D reports no filesystem and zero bytes.

No target was reset/programmed and no SD card was formatted or written during
this execution. Physical qualification is blocked until the connected setup is
inventoried/recoverable and an explicitly selected reference card is present.
Power-cut/removal tests retain their separate authority and safety gates.

## Remaining release evidence

Software implementation and build gates are complete. These are not substitutes
for representative-target proof. Still required: semantic fault injection,
no-card/removal/full-card cases, old-code EDGE/Industrial discrimination,
candidate repeated runs, restart and approved power-cut cases, host filesystem
inspection, concurrent-load observation, and real-time soak.
