# Project Map: SMI 00-05-01 Transition Floor And Controlled Return

Status: active
Type: project-map
Updated: 2026-09-24
Source Idea: IDEA-0007
Technical Source: IDEA-0006
Requested Endpoint: source completion plus authorized A/B bench qualification; release and publication remain separate
Next Action: Prepare an explicit release-document/evidence and Tool Shed checkpoint commit list, preserving unrelated changes. Qualification is accepted; firmware release remains unauthorized.
Campaign: standalone
Initial Target Control: Controller A

## Current release reconciliation — 2026-09-24

Corrected candidate `00.05.01-b59c33d1c1f4-3f464c236471` is committed, reproducibly built, immutable and locally registered. Controlled images, A/B normal transitions, A warning/Cancel, B HPT2 initialization/logging/CSV/restart retention, accepted DisplayTest return/restart behavior, and A malformed-header refusal are evidenced. CAMP-0028's service-471 target criterion is now evidenced on B. Do not repeat these completed checks.

The owner removed stale-selection testing as a release requirement and closed both the legacy 00-04-11 Success mismatch and DVO intermittent 901 investigations. Preserve their observations without further resolution work or root-cause claims. The accepted transition contract already excludes promised recovery after internal-flash replacement starts; this is a scope limit, not a new qualification deliverable. The owner accepted the existing source/host checks as sufficient for SD-preparation failures and timeouts before flash replacement on September 24. All four qualification gates are satisfied, including that explicit evidence disposition; no target fault-injection pass is invented. Missing historical CID/screen captures remain declared evidence limits, not requests to reconstruct them.

Firmware release is explicitly unauthorized. The cohort remains working and unfrozen; final scoped content checkpoint, release preflight/exact-content CI, publication, and release-outcome reconciliation remain future release work. One candidate commit has two owner registrations (MAP-0009 and CEO IDEA-0007), not two firmware candidates. IDEA-0006 is the technical source for this same outcome. No abandoned work is revived. Detailed prior checkpoints remain in managed revision history and linked evidence.

Current authority: `docs/firmware-update-validation-and-recovery.md` and `work/evidence/smi-current-release-gate-review-20260924.json`.

## Outcome

Deliver a safe SMI 00-05-01 update floor, a direct controlled SMI rollback, and a safe return to revised DisplayTest. Preserve normal DisplayTest FAT32 handoff and explicit SMI HPT2 initialization. Qualify all transitions on both controller assemblies before any release decision.

## Direction and boundaries

1. Use CRC-validated IMX Title family/version identity plus MachineMask, layout, size and payload checks; the external filename is only a discovery label. Ordinary Update Software and service 151 share the current admission and confirmation flow. Valid older SMI is admitted through the ordinary path with target-driven media preparation; do not restore the superseded service-only restriction.
2. Retain verified FAT32; format another readable layout only for an admitted FAT32 target after explicit data-loss consent. Missing, unreadable or busy required media stops admission. Validate/stage the image, recheck CID and representative sector, prepare media, revalidate staged CRCs, then replace flash. The retained branch must not read CID through a closed raw driver.
3. Service 471 remains explicit HPT2 recovery when SMI remains bootable with usable UI. No promise covers recovery after internal-flash replacement starts.
4. DisplayTest 01-01 remains the controlled external return/handoff dependency; its project is read-only here. DisplayTest 01-00 and SMI 00-05-00 are excluded from target qualification. No Full Run merely to supply this transition.
5. CVO/DVO delivery is outside this project. Preserve owner-closed DVO 901 disposition and no specimen-specific production behavior.

## Execution sequence

Qualification is complete with the owner-approved source/host evidence disposition for pre-flash SD-preparation failures/timeouts. Preserve completed tests. Next: prepare the exact release-document/evidence and Tool Shed checkpoint file list, preserve unrelated edits, then perform authorized release controls. Firmware release remains explicitly withheld.

## Readiness gates

- G-APPROVED-IMAGES: PASS. Controlled corrected SMI and DisplayTest images are bound to verified hashes, package checks and exact target readbacks. No duplicate corrected service-150 export is required.
- G-SMI-CANDIDATE: PASS for committed source, canonical reproduced builds, immutable candidate and local registration. Candidate `00.05.01-b59c33d1c1f4-3f464c236471` is current; final release content/cohort freeze is distinct and not performed.
- G-DISPLAYTEST-RETURN: PASS for bounded A/B return, FAT32 handoff and accepted restart. B post-restart remote CID is explicitly unavailable because its probe is missing; operator OK/OK and earlier exact return/CID evidence are retained.
- G-DUAL-CONTROLLER-TRANSITION: normal A/B transitions/storage, A Cancel and malformed-header refusal pass. The owner accepted existing source/host checks as sufficient for pre-flash SD-preparation failures/timeouts; this gate is PASS with that explicit evidence disposition. Stale-selection refusal is not required; legacy 00-04-11 and DVO incidents are owner-closed. Recovery after internal-flash replacement begins is already outside the promise. Historical capture limits are retained.

All four stable IDs remain. The overall owner outcome stays open for final release preparation and the unreleased delivery obligation; no release approval is inferred.

## Controller A qualification image inventory

Current controlled SMI IMX: `7520553_SMI_00_05_01.imx`, SHA-256 `4E4321E5BDA3942BF70ED9304B935DF33DC40E5FA1E9B8A4AEF60DCA6ED3B97A`. Controlled DisplayTest 01-01 IMX: SHA-256 `E11CEB483BA478F6A3D98F75DBF303EA09800165463EFE17880D5CDB2ACD78AB`. Legacy SMI 00-04-11 specimen: SHA-256 `1A83853002168B373FE756FF090F4364E9D82039D247E12678E842643C6AB274`.

IMX2/IMX3 retained images were verified; obsolete test images were removed under owner direction. The temporary malformed-header image was removed from IMX3 after its successful refusal test. Earlier candidate hashes remain historical evidence with documented change-impact applicability, not current image identities.

## Current limits

No fresh baseline is claimed beyond the linked captures. B post-DisplayTest-restart CID is unavailable because its probe is missing. Legacy 00-04-11 has no trustworthy mapped CID capture; exact historical warning transcription was not retained. These are explicit evidence limits. No full SD-family/physical-card qualification, interrupted-internal-flash recovery, or CVO/DVO delivery is claimed. Previously abandoned programmes stay abandoned. Firmware release is not authorized.

## 2026-09-22 target designation

Controller A remains the initial target control and Controller B follows for the dual-controller gate. A read-only four-MiB Controller A DVO rollback capture was retained before programming. After a fresh serial-bound inventory, Controller A was programmed with the manifest-bound SMI 00-05-01 Release candidate. No SD card was moved and no power operation or SD write occurred during this program step.

## 2026-09-22 rollback boundary review

The source review found that the USB updater could time out while the SD worker still had a pending or active FAT32 preparation, falsely reporting failure before a later card format. The updater now waits for the SD owner's terminal result once preparation is requested. The final read-only USB media flush remains telemetry rather than an image-admission gate after full payload and staged QSPI CRC verification. The canonical Release rebuild, 16 update cases, and 19 review checks pass. This does not prove SD-worker liveness or target fault behavior; the Controller A fault matrix remains open.

The separate DisplayTest project's newer Controller B record includes a five-minute export with newly written and read SMI `00-04-11` FAT32 records. Post-restart retention was not checked. That pairing evidence does not qualify the SMI `00-05-01` A/B transition.

## 2026-09-21 source checkpoint

The SMI source version is now 00-05-01. The ordinary update path parses family and two consistent numeric version spellings from the CRC-checked Title, checks the 00-05-01 personality floor and DisplayTest 01-01 return floor, and refuses malformed, unknown, or older identities before the first install QSPI erase. It does not use the USB filename as identity. A distinct controlled direct-rollback path accepts any valid SMI image. A pre-00-05-00 image is fully staged before the SD owner rechecks CID and representative sector, prepares FAT32 in place, and lets USB recheck the staged CRCs before internal-flash replacement. The managed Release rebuild and subsequent incremental build pass; the existing 16-case firmware-update negative corpus and 19 code-review checks pass. This was a source-only checkpoint; later sections supersede its target-evidence status. No controller programming or SD operation occurred at this checkpoint.

## 2026-09-22 source review

The legacy service branch now checks read-only SD preparation eligibility before the first QSPI erase, then checks again after staging when it requests the SD owner operation. The SD worker keeps FAT32 media unavailable to HPT logging until the older firmware takes over. Service-code consent text states that data loss is conditional on a pre-00-05-00 image. The managed Release rebuild and final incremental build pass; the existing 16-case update corpus and 15 review checks pass. The checked-in 00-05-00 IMX header has the expected controlled Title, format-1 layout, and four-MiB main/audio payloads. There is still no target evidence for the DisplayTest return, FAT32 failure/recovery boundary, or A/B transitions; no controller or card action occurred.

Read-only review of the separate DisplayTest 01-01 source found no personality version floor in `src/DisplayTestUpdateAdmission.h`, a 01-01 fixture-to-fixture minimum, and FAT32 handoff before personality installation. Its project record reports Controller B FAT32 handoff and installation of SMI 00-04-11, after a power cycle following an initially unresponsive install tap; old SMI logging remains unproven. The earlier reciprocal-floor requirement conflicted with that media-state design and is superseded above. This does not satisfy the SMI A/B return or rollback gates, and the SMI bench pause remains in force.

## 2026-09-22 resumed implementation checkpoint

The focused review now restricts SMI, CVO, and DVO Titles to product IDs 7520553, 7520555, and 7520721 respectively. A pending direct-rollback SD request cancels atomically if the SD thread does not accept it within 30 seconds; once accepted, USB waits for the terminal result because FAT32 erasure may be underway. Nineteen identity-policy cases, nine rollback-contract checks, the existing 16 update cases, and 19 review checks pass. Fresh managed Debug and Release rebuilds pass. This was a pre-target checkpoint; later sections supersede its candidate status.

## 2026-09-22 immutable candidate and bench-boundary checkpoint

Commit `77495a3715ffeb3d3a4928a82d6f2e949e7e5362` contains the reviewed SMI 00-05-01 source and deterministic Debug and Release outputs. Fresh clean-commit rebuilds reproduced the tracked outputs. Immutable candidate `00.05.01-77495a3715ff-5a30dd9eacda` validates against HEAD; its manifest SHA-256 is `B948EDFC72444042D38E692607A234D9C671B1D1D0BE98C229142095ED57160B`, Debug S-record SHA-256 is `51315325E3B37F91B6A8B204741480F3DC6ED621CC76594FBB0E987D1075047A`, and Release S-record SHA-256 is `5A30DD9EACDA99AD7BC86CA70D536FA331B78A4015325891DE920EA8421B00B3`. This closes the host-side candidate freeze portion of G-SMI-CANDIDATE; target behavior remains open.

Live hub inventory confirmed Controller A probe `69664082` at port `19120` and Controller B probe `69660123` at port `19121`. The Controller A pre-program DVO four-MiB rollback capture has SHA-256 `8DC55368026649523FC751B09A6C99F47FD015251D1B0A6BE7F6CBC9DE44DAD6`. Pre-program CID is unavailable because DVO has no service-467/equivalent mapped state; the installed card was not moved. Manifest-bound programming of the Release candidate passed with serial `69664082` and VTref 3.272 V. The post-program four-MiB readback SHA-256 is `CFC9ECC6ABCCDDA5633FFF6AB8A6595ECAC21F6AC951ED35F0D51407BB8CE407` and exactly matches the expanded S-record. After startup settled, target state reported protocol detection `4` (FAT32 / needs initialization), CID valid `1`, representative-sector read valid `1`, and raw CID `05000C61736466672200001C8901A34F`. Owner-supplied photographs confirm successful SMI boot, working touch navigation, firmware `00-05-01`, assembly `1751136`, and the expected FAT32 / HPT media 2.0 initialization warning while temperature control remained active. No initialization was accepted. The owner confirmed that SMI 00-05-00 was never deployed on a production controller and does not require target qualification. It is excluded from the bridge path. A deterministic host builder now packages the exact SMI 00-05-01 Release S-record with the audio payload from released SMI 00-04-11, allowing the ordinary Settings > Update Firmware path to establish the correct SMI main and QSPI payloads directly.

## 2026-09-22 FAT32-safe candidate and direct updater checkpoint

Commit `22a3205bae1372b485f2c484de238e2c9cbae0db` retains an already-readable FAT32 card during service rollback after CID and representative-sector verification; only an HPT2-to-FAT32 conversion invokes formatting. Managed Debug and Release rebuilds pass. Nineteen identity-policy cases, ten rollback-contract checks, sixteen update-validation cases, fifteen review checks, the image-builder CRC round trip, and candidate tamper tests pass.

Immutable candidate `00.05.01-22a3205bae13-da6887348e38` validates against HEAD. Its manifest SHA-256 is `E45CA23CF3F4A321192555B9CFC3E84BFA23F86B000A468CAC5C379348A81FA8`; Release S-record SHA-256 is `DA6887348E38F986F53C17D29BEC6CB04D5ABFF1ECFED2BF67D972E99E657AA0`. Deterministic IMX `7520553_SMI_00_05_01.imx` is 8,388,864 bytes with SHA-256 `6F47AF091C9B73CCE8DD8DC58D4D7F3A270D6E21DB8659D28F1C30B6F4EB80D7`, header CRC `4A7B4205`, main CRC `F5B332CF`, and audio CRC `758FE2DE`. The main payload is the exact candidate Release S-record expanded to four MiB; the audio source is released SMI 00-04-11, SHA-256 `1A83853002168B373FE756FF090F4364E9D82039D247E12678E842643C6AB274`. Controller A was scheduled to consume this image through Settings > Update Firmware under the policy at that checkpoint. The later target-media requirement and staging result supersede this forward-looking statement.

## 2026-09-22 Controller A staging result and requirements detour

Controller A listed and accepted the exact `7520553_SMI_00_05_01.imx` through Settings > Update Firmware and returned to the main screen. Read-only evidence proves exact QSPI staging: main SHA-256 `7F49E615FF971D1C63E44CF94B8DCD9BF919DA7846E052408189997A58B78B8E` and audio SHA-256 `CEDDB5F1BC3F40EDD449E2228B3DB1EB75289C9B60DCD415276DCC31FAC8DCE2`. Internal flash remained exactly the prior candidate at SHA-256 `CFC9ECC6ABCCDDA5633FFF6AB8A6595ECAC21F6AC951ED35F0D51407BB8CE407`; at this checkpoint the final flash-transition cause was unresolved. The FAT32 card remained uninitialized with CID `05000C61736466672200001C8901A34F`, identity valid, and representative-sector read valid. Configuration remained operational and quiescent. The 2026-09-23 reconciliation below closes that defect diagnosis.

The owner then required target-driven FAT32 preparation and a gray disabled main chart whenever logging is unavailable. The SMI implementation now shares FAT32 preparation across ordinary DisplayTest return and legacy-SMI service rollback, retains verified FAT32 without formatting, formats another readable classified layout after explicit consent, and refuses missing or unreadable media before QSPI erase. The chart uses live queue/media/store readiness and refuses stale clicks. Twenty-four identity/media cases, thirteen FAT32 transaction checks, sixteen update validation cases, the chart availability contract, nineteen review checks, seventeen warning checks, both managed builds, and related USB/FileX checks pass. Commit `10dbb91519384cc9144b94e8a79057c8f47c0630` was rebuilt cleanly and reproduced Debug S-record SHA-256 `69C28A9B4D51F6AA8BD0F70E6D4360B4D2EC56F401B20C6C82327475414EC8EF` and Release S-record SHA-256 `4E7DFB2F7333202C71A736DF6692512030DB43508A1CCD0C556E7E8C1EB6B326`. Immutable candidate `00.05.01-10dbb9151938-4e7dfb2f7333` validates with manifest SHA-256 `6F753689C56EFACE054C802FF782FFCC193BFAE2D7F5E948F0BE20F44FA86586`. The prior frozen candidate is superseded. Bench work remains paused and no controller programming or SD formatting occurred during this detour or freeze.

## 2026-09-23 operator UI acceptance and final SMI image

Controller A was direct-programmed with accepted candidate `00.05.01-1bf8afe6aeba-6476100e5ae5`; a complete four-MiB readback matched the expanded Release S-record at SHA-256 `40560E9D046293BE345676BC97CD09E88E29D543DBEB02AD3B764EBF029D4E87`. The owner accepted the fitted startup warning, reason-specific disabled-chart message, return-to-home behavior, operator service 467 access, and the remaining service 471 warning flow. The owner unintentionally completed service 471 during that review. Immediate read-only state showed ready media, valid unchanged CID `05000C61736466672200001C8901A34F`, a successful representative-sector read, and no terminal initialization error.

After UI acceptance, Controller A service 150 generated the final `7520553_SMI_00_05_01.imx` on `IMX2`. Read-only host validation reports 8,388,864 bytes, SHA-256 `AF8132D13837F6030CD73689E77833AA563C0C878C19126448E869DFEB337332`, valid header/main/audio CRCs, and an exact main-payload match to the accepted Release candidate. The source media was unmounted cleanly. This closes the SMI controlled-image portion of G-APPROVED-IMAGES. The separate DisplayTest workspace currently has no controlled `01-01` IMX, so that gate and the remaining Controller A transition matrix items remain open. No further controller programming or SD operation is authorized by this checkpoint.

## 2026-09-23 Tool Shed reconciliation to actual work

The earlier internal-flash handoff failure is resolved. Commit `76471306` added watchdog refresh during bounded flash erase/program waits; commit `ab0755e7` cleared stale FCU command-lock state and disabled ROM cache before the RAM-resident updater handoff. A controlled self update completed with terminal diagnostic error `0`, and the full internal-flash readback exactly matched its candidate at SHA-256 `6B27C922C40908BB6221819841F8A7F264E09C3E5D3399ABB0F18993BD01A86F`.

The current accepted candidate is `00.05.01-1bf8afe6aeba-6476100e5ae5`, from commit `1bf8afe6aebab3df4a8c71cb626e405ace3322f8`, manifest SHA-256 `A4BDA8EEE4C5D78C45F7CC943616FAAE2285B00DD76F4F3E02363D5067AD1D60`, and Release S-record SHA-256 `6476100E5AE5B5ED5EA38F5BBFDFC8AE6BC44513200678406F2711B0B91C1D9D`. Controller A's full readback exactly matches the expanded Release image at SHA-256 `40560E9D046293BE345676BC97CD09E88E29D543DBEB02AD3B764EBF029D4E87`. The owner's UI acceptance and the final controller-generated SMI image close the source, UI, Controller A exact-image, and SMI image-control portions of the work.

Open work is now limited to the exact controlled DisplayTest 01-01 IMX and the still-paused A/B forward, return, refusal, controlled rollback, fault, logging, retention, and export evidence needed by the readiness gates. The separate DisplayTest lane has source and bench evidence for safe startup, FAT32 handoff, and touch, but this project cannot close G-DISPLAYTEST-RETURN without the controlled 01-01 image and required SMI transition evidence. MAP-0009 remains active; no release, ECO, or rollout decision is implied.
