# Setup A controller baseline and candidate load

Status: superseded by corrected evaluator candidate; original load and first-run baseline retained
Type: evidence
Updated: 2026-07-14
Next Action: use `work/evidence/evaluator-correction-build-and-load-20260714.md` for the corrected candidate and rerun
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/maps/map-smi-firmware-stabilization-and-qualification.md

## Connection and pre-load baseline

- Probe: SEGGER J-Link V9.60, serial `69664082`, J-Flash license.
- Target: Renesas `R7FS7G27H`, Cortex-M4, SWD at 4 MHz.
- Target voltage: 3.308 V.
- The read-only J-Link attach found the CPU already running. No halt, reset,
  breakpoint, register write, or output forcing was performed during baseline
  capture.
- Installed image contained runtime filename `7520553_SMI_00_04_12.imx` and
  closely matched the repository baseline rather than the new evaluator build.

## Recovery images

| File | Bytes | SHA-256 |
| --- | ---: | --- |
| `program-flash-jlink-69664082-20260714.bin` | 3,145,728 | `AD72B96C3AC4EB0F1AE67EB8A7DBFFDE2FC46F0BEA0544DAAC5DBEF63DEFB5E2` |
| `veeprom-jlink-69664082-20260714.bin` | 4,096 | `89BB6593360B7BE5B0EC4E1EF34D3CD6AEC3E5BA5271C9B1DE19232E0CADCE7D` |
| `option-memory-jlink-69664082-20260714.bin` | 48 | `80A76A18ACF8CB64FEC3A659FFC4BAB4A87CD9A6FDE4DAB2161A8751D136C9D2` |

Both 2 KiB VEEPROM blocks were byte-identical before programming. Their raw
identity fields were configuration version 1, update count 1, serial word
`0xA050D0F0`, machine type 1, model 3, and Part ID `SLM622`.

## Candidate programming and verification

- Programmed with `smi.jflash`, whose internal data-flash bank is disabled.
- Candidate: Release `7520553_SMI_FW.srec`, SHA-256
  `ADE296F71313D3D3DADCBDBB94AFD9A80988484B3AFA7EE0E1398B52A26276DE`.
- J-Flash automation returned success, restarted the application, and exited.
- A post-load read matched every one of the 2,825,780 candidate program bytes;
  mismatch count was zero.
- Captured option-setting bytes matched every candidate option record and were
  unchanged from the baseline.
- Pre/post VEEPROM images were byte-identical with the same SHA-256. The load
  therefore preserved configuration/calibration data.

## Live candidate status

Read without halting the running CPU:

- `gPowerOnStatus = 0xC00000FF` (boot complete).
- `gMainSystemErrors = 0`.
- Semantic status: findings 0, changed 0, controls inhibited 0,
  commissioning required 0.
- Model 3, Part ID `SLM622`.
- Main temperature operation/control enabled; setpoint approximately 37.0 C.
- Main PID: loop 300 seconds, P 350.0, I 0.75, D 5000.0.
- Actual temperature approximately 36.56 C.
- Heater-demand snapshots were nonzero (167/1000 and 146/1000 ticks),
  consistent with active regulation.
- SD state 2 (`READY`), last status 0, format-marker status 0.
- Evaluator state 0 (`IDLE`); no destructive evaluator action has started.

## Remaining gate

The controller has an internally mounted, ready SD card, even though the PC USB
reader remains empty. Its physical identity cannot be inferred through the
current firmware. The operator must identify whether the installed card is the
SanDisk EDGE failure reference or SanDisk Industrial working reference before
the run is labeled. Service code 472 must then present the mandatory data-loss
warning and receive the operator's on-screen confirmation; this gate was not
bypassed through J-Link.

Operator identification update: the installed card is the known-working
SanDisk Industrial 8 GB microSDHC U1/Class 10 reference. A subsequent live read
still showed SD READY, clean semantic/system status, and evaluator IDLE. The
destructive service-code confirmation has not yet been received.

Supersession update: run 06670 exposed an undersized FileX media-check workspace,
not media corruption. The corrected Release SREC
`F5D026FC039BF6755B68B17AC9BF40A03AFC872EC2EE563A8E27FD70B1C7CB05`
was loaded and verified on 2026-07-14; see
`work/evidence/evaluator-correction-build-and-load-20260714.md`.
