# USB04_32G compliant SYNCHRONIZE CACHE Release qualification — 2026-07-30

Status: complete
Result: passed
Type: evidence
Updated: 2026-08-01
Next Action: none; retain as historical optional-command evidence, not the current production lifecycle
Campaign: 003-complete-bounded-hpt-slow-export-firmware-ticket
Parent: work/wp/completed/wp-implement-usb-command-class-compatibility-fallback-end-to-end.md

## Identity

- Release S-record SHA-256:
  `838645AF04F6718231AE892A7F2EB16EC6710A8354DA270A6601CFEAC8E6ABE9`
- USB label: `USB04_32G`
- USB serial: `071C49DE246A1F97`
- FAT UUID: `E4FE-BA86`
- Controller B SD CID: `035344535330384780976F0085018507`
- Controller A SD CID: `035344535330384780976F0084018559`

## Controller results

Controller B then Controller A each completed a full 8,388,864-byte image
publication on the Release firmware.

On both targets:

- `sync_cache_compatibility_required` remained `0`;
- `sync_cache_compatibility_count` remained at its pre-run value `4`;
- the full image completed physical VBUS-cycle/remount verification;
- `verified_bytes` was `8,388,864`;
- the fresh session reached acceptance mask `15`; and
- live system errors remained zero.

The unchanged compatibility count proves that `USB04_32G` accepted the
SYNCHRONIZE CACHE path rather than selecting the unsupported-command fallback.

Raw evidence:

- `work/evidence/hpt-log-store-circular-mirror/controller-b/usb04-compliant-sync-release-20260730/`
- `work/evidence/hpt-log-store-circular-mirror/controller-a/usb04-compliant-sync-release-20260730/`

## Independent Raspberry Pi verification

After both controller runs:

- `/dev/sdb1` identified as `USB04_32G`, serial `071C49DE246A1F97`;
- `fsck.vfat -vn` reported a clean FAT32 filesystem without repair;
- `7520553_SMI_00_05_00.imx` was exactly 8,388,864 bytes;
- image SHA-256 was
  `4E0E1C3DD651B557FD6B71840C60E6D1DA8493E413D39EFE825C7853F8536CD6`;
- WAV hashes matched the qualified inputs;
- no `.TMP` files were present; and
- the drive was left unmounted on the Pi.
