# USB 32 KiB matrix Round 1 controller result: USB01_2G and USB05_4G

Status: complete
Result: complete; controller workflow passed and subsequent independent Pi validation passed
Type: evidence
Updated: 2026-08-01
Next Action: none; retain as historical round evidence for the completed matrix
Campaign: 003-complete-bounded-hpt-slow-export-firmware-ticket

Project Map: work/maps/map-smi-firmware-stabilization-and-qualification.md
Workpackage: work/wp/completed/wp-restore-broad-usb-compatibility-baseline.md
Checklist: work/checklists/checklist-stage-1b-four-drive-usb-compatibility-baseline.md
Precheck: work/evidence/usb-32k-round1-precheck-usb01-usb05-20260731.md

## Candidate and allocation

- Deployed firmware source commit:
  `8fa1479b6b942f72f18ff4ed2cb1a5c73ddc2501`.
- Release ELF SHA-256:
  `6A2D8F79D72387311C83599663B192FCF764F53AB3E0926E3B917F3746B426CA`.
- Release S-record SHA-256:
  `82A277EEBBED0CC4FBDDCC848ACEFD43E706849803673C4920E7851FC2ACABB5`.
- Controller A, assembly `1751136`, hardware variant `0`, J-Link
  `69664082`: `USB01_2G`.
- Controller B, assembly `1751219`, hardware variant `1`, J-Link
  `69660123`: `USB05_4G`.

The raw helper artifacts record repository HEAD `c8ee134a...` because that is
the evidence-script/planning state at capture time. The candidate-bound tools
verified the explicit frozen ELF and S-record above; no firmware was rebuilt
or substituted.

## Controller and SD entry gates

Both drives mounted on first insertion and remained attached throughout the
workflow. The initial, pre-export guarded, trigger-specific, and final
captures showed:

- USB mounted `1`, host attached `1`, FileX handoff status `0`, acceptance
  mask `15`, application session state `2` / status `0`, pending instance `0`,
  and a valid FileX media pointer;
- media generation `2` on Controller A and `1` on Controller B;
- system errors `0` and USB application errors `0`;
- HPT media state/status `5/0`, CID valid, and no replacement request;
- no VBUS command or power cycle.

Required SD identities at the guarded export release were:

| Controller | Protocol status | CID valid | Representative sector | Identity |
| --- | ---: | ---: | ---: | --- |
| A | `6` | `1` | `1` | SanDisk/WD; MID `0x03`; OEM `SD`; product `SS08G`; revision `8.0`; serial `2540634244`; manufactured `2024-05`; raw CID `035344535330384780976F0084018559` |
| B | `6` | `1` | `1` | SanDisk/WD; MID `0x03`; OEM `SD`; product `SS08G`; revision `8.0`; serial `2540634245`; manufactured `2024-05`; raw CID `035344535330384780976F0085018507` |

The general HPT identity helper's separate read-only last-operation field
reported representative-sector status `0` after chart-cache capture on each
controller. This did not authorize the export. The initial USB capture, the
immediate guarded USB recheck, the trigger-specific SD detection block, and
the final USB capture all reported representative-sector validity `1`; the
request was released only from the guarded trigger capture with value `1`.

## Common customer workflow

Both controllers accepted the same operations without retry:

- enumerate `W00.WAV` and `W01.WAV`;
- load the WAV data and exercise sound 1 playback;
- publish a new PID capture;
- replace `7520553_SMI_00_05_00.imx`;
- publish a full retained-range HPT CSV.

Image-publication metrics were:

| Drive / controller | Bytes | Calls | Maximum write | Write | Close | Flush | Rename | Total | Result |
| --- | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | --- |
| `USB01_2G` / A | 8,388,864 | 8,193 | 1,024 | 407.70 s | 0.01 s | 0.52 s | 0.03 s | 421.59 s | published, status `0` |
| `USB05_4G` / B | 8,388,864 | 8,193 | 1,024 | 225.74 s | 0.00 s | 1.32 s | 0.02 s | 239.20 s | published, status `0` |

The image path is intentionally unchanged at its established 1 KiB FileX
writes. The candidate changes only the HPT export write cap.

## Full-range 32 KiB HPT discriminator

The exports used each controller's complete retained range available at the
guarded capture, ensuring the test exceeded one 32 KiB write:

| Drive / file | Requested range | Selected / health | Bytes / calls / maximum | Timing | Result |
| --- | --- | --- | --- | --- | --- |
| `USB01_2G` / `K1A_USB01.csv` | `301739760..302283900` | 8,787; 8,787 healthy, 0 degraded, 0 gaps | 441,542 / 14 / 32,768 | scan 11.22 s; write 1.06 s; close 0.01 s; USB 2.47 s; total 13.71 s | state/reason `4/0`; complete/published `1/1`; USB status `0`; phase `14` |
| `USB05_4G` / `K1B_USB05.csv` | `301741860..302283780` | 8,792; 8,711 healthy, 81 historically degraded, 0 gaps | 441,912 / 14 / 32,768 | scan 11.15 s; write 1.83 s; close 0.00 s; USB 3.26 s; total 14.42 s | state/reason `4/0`; complete/published `1/1`; USB status `0`; phase `14` |

Controller B's 81 degraded records are an existing HPT source-data
classification, not a USB failure. The export included them as designed and
reported no snapshot or requested-range gaps, no first USB failure, and no
publication error.

## Evidence and disposition

Raw controller-specific captures remain in the ignored local evidence tree:

- `work/evidence/hpt-log-store-circular-mirror/controller-a/usb-32k-round1-usb01-20260731/`
- `work/evidence/hpt-log-store-circular-mirror/controller-b/usb-32k-round1-usb05-20260731/`

Round 1 passes the complete controller-side production workflow on both
hardware variants without VBUS, controller power, reseat, retry, optional
SCSI, or specimen-specific mitigation. Promotion is not implied. Independent
no-repair Pi validation of both filesystems and every expected artifact was
required before Round 1 could be marked PASS.

The subsequent independent Pi gate passed FAT consistency, equal FAT copies,
kernel state, exact CSV sizes and continuous sequences, COMPLETE markers,
PID/WAV content, identical internally CRC-valid recovery images, absence of
temporary artifacts, and final unmounted state. Round 1 is PASS end to end.
See `work/evidence/usb-32k-round1-pi-usb01-usb05-20260731.md`.
