# Controller A temporary endurance campaign (legacy setup-b path)

Status: reclassified as controller-A evidence; EDGE FAT finding unresolved
Type: evidence
Updated: 2026-07-16
Next Action: preserve/disposition the EDGE card's 4 KiB lost allocation chain
Campaign Reason: Historical record from campaign 009-complete-clean-contract-bound-a-b-qualification; retained independently after campaign closure and requires no separate owner-queue execution.
Campaign: standalone
Parent: work/wp/active/wp-sd-card-accelerated-endurance-evaluator-and-media-qualification.md

## Classification correction

This campaign ran on Setup A/controller `1751219`. It was originally placed in
`setup-b` because the working assumption was that only one controller existed
and “Setup B” denoted a temporary campaign state. The owner later clarified
that Setup B is a separate physical controller, asset `1751136`, and directed
full completion of A before switching. This legacy path is retained to avoid
moving immutable evidence, but none of its contents provide controller-B
coverage. Controller `1751136` remains untested.

## Electronic baseline

- Controller/probe: R7FS7G27H via J-Link V9.60 serial `69664082` at 3.308 V.
- Firmware: integrated 00.04.12 candidate.
- Debug S-record SHA-256:
  `70CA38269672AAA433F567FCCDA39B36FBE430410B58E72F61156AEF00B88EBC`.
- Startup: complete (`0xC00000FF`).
- Configuration: operational 1, no findings/events, generation 6, SMI7.

| Capture | Bytes | SHA-256 |
| --- | ---: | --- |
| `program-flash-jlink-69664082-20260716-campaign-baseline.bin` | 3,145,728 | `D412034EF082A72B284D13B4E3D47C75773BE3FAA930FD66A67C27A2539866B0` |
| `veeprom-jlink-69664082-20260716-campaign-baseline.bin` | 4,096 | `C0AD6BF06D7CA041F36D09A7CBF4205F40E5C762AA736A582AECD080C4B48EFE` |
| `option-memory-jlink-69664082-20260716-campaign-baseline.bin` | 48 | `80A76A18ACF8CB64FEC3A659FFC4BAB4A87CD9A6FDE4DAB2161A8751D136C9D2` |
| `status-ram-jlink-69664082-20260716-campaign-baseline.bin` | 9,216 | `59246ED241FDD030402D2DD9410D5E92ADDC3FE925BA622D6ECCF1098B7B1AFB` |

The program, VEEPROM, and option-memory hashes match the final restored Setup A
baseline. No firmware, configuration, SD media, or power state was changed by
this capture.

## EDGE card pre-erase state

The operator replaced the Industrial card with the slow/failure-prone SanDisk
EDGE 8 GB card. Read-only target capture showed:

- SD state READY, last status 0, one open attempt, and zero I/O/mirror failures.
- Three completed records and zero dropped records at capture.
- 512-byte sectors, `0x00ECC000` total sectors (~7.95 GB).
- 64 sectors per cluster (32 KiB allocation unit).
- FileX, SDMMC, and service-state binary captures are retained under the Setup B
  evidence directory with SHA-256 hashes in the generated file records.

The controller cannot create a host-level forensic card image through the
current read-only J-Link procedure. Remove and image/list the card on a host
before evaluator format if it remains readable.

## Owner destructive-media authorization

On 2026-07-16, the owner explicitly stated that the existing EDGE-card contents
do not need to be preserved and directed the campaign to proceed. Host imaging
and pre-erase file preservation are therefore waived. The authorization covers
permanent erase/format and the approved 31-day accelerated evaluator profile on
this installed slow/failure-prone EDGE card. The firmware's two-stage service-
code 472 warning/confirmation remains the required per-run start path.

## EDGE accelerated run 67569

The operator started service-code 472 run 67569 on the installed EDGE card.
The evaluator reached terminal state PASS after writing 44,640/44,640 records,
then verifying 118,080 mirror records across 1,968 files. First-failure status,
last status, and non-correcting media-check errors were all zero. Elapsed time
was 1,685.57 seconds and maximum observed write time was 108 ThreadX ticks.

Controller RAM, FileX, SDMMC, and service-state captures and their hashes are
recorded in `work/evidence/setup-b/sd-evaluator/67569/manifest.md`. This is a
controller-side result only until the powered-off card is host-mounted and the
A/B namespace, `EV67569.RESULT` JSON, and filesystem are independently checked.

Host analysis subsequently passed both 744-file mirrors, all 44,640 logical
records, exact A/B comparison, and corrected result JSON with zero analyzer
errors. A separate non-repairing CHKDSK scan reported one 4,096-byte lost
allocation chain while also warning it could not lock the in-use volume. The
volume dirty bit is clear. No repair was performed; preserve the card and see
`work/evidence/setup-b/sd-evaluator/67569/host-filesystem-check-20260716.md`.

## Campaign closeout and Setup A restoration

The operator removed and preserved the EDGE card without repair, installed the
Industrial card, and powered the controller. The post-campaign VEEPROM was
captured before restoration. The exact Setup A image was then loaded, verified,
and rebooted. Final program, VEEPROM, and option-memory hashes exactly match the
preserved baseline; startup, configuration, and SD service are healthy. See
`work/evidence/setup-a/post-setup-b-restoration-20260716.md`.
