# Current SMI Setup B connected-bench record

Status: active connected-bench inventory; authoritative complete-flash observation proves preserved prior Release `23428a89...54ca`, not imported candidate `d1babfa7...70556`
Type: inventory
Updated: 2026-08-02
Next Action: obtain separate state-changing authorization before any candidate programming; then require complete verify/reset/run and a fresh independent read-only firmware/CID/HPT observation
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

Canonical Truth: E:/dev/high_point/7520553_SMI_FW/README.md

## Identity

- Bench label: Controller B / Setup B
- Controller assembly: `1751219`
- Running hardware variant: `1`
- J-Link serial: `69660123`
- Generic connector endpoint: `srv-rpi00` port `19121` through SSH forwarding
- Mapping method: read `gHardwareVersion` from the running target through the
  serial-bound J-Link endpoint; reconfirm after cabling changes

## Authoritative current identity — 2026-08-02

Owner-authorized Pi observation
`e371bc50-1163-4c70-88ad-2ac1226210df` read the complete 4 MiB code flash
without reset, programming, or target-memory writes. It observed SHA-256
`23428a890890ca40172483a683f2b985c5bfc640650e7b33b977ead15db754ca`,
the preserved prior Release identity, instead of imported candidate SHA-256
`d1babfa7a65610544741c0b329212b0eadfc92b32a8e95b513e2e2ec9ae70556`.

The exact-candidate gate is therefore
`BLOCKED/FIRMWARE_IDENTITY_MISMATCH`. The fail-closed observer did not interpret
mapped RAM after the mismatch, so current protocol status, CID validity,
representative-sector-read state, CID fields, and raw CID are unavailable for
this observation. Historical CID values below remain history and must not be
promoted as the current candidate-run identity.

Evidence:
`work/evidence/controller-b-exact-candidate-readonly-identity-20260802.md`.

## Historical evidenced firmware and target state

### Historical cumulative candidate and recovery baseline

- Source commit:
  `2f4d872495920027651d5b18e893df8484000831`.
- Debug S-record SHA-256:
  `30C98F00E8712BB1C9CF4C9FC144F20A84692C1C416CE09BEF5AF20E2AADF649`.
- Debug ELF SHA-256:
  `F53A6E1C15142936F90A6BF99D55A9B5D31009C465705B0431D7693C23952821`.
- The then-fresh four-MiB internal-flash readback exactly matched that S-record;
  reconstructed/readback SHA-256:
  `6C0DBDB31E30AAD13993CA3D49BA0141BEDCC8FF2E4C38BC33743D9FA7389D4B`.
- Configuration/calibration, option memory, known-good recovery image,
  serial-bound J-Link recovery, reset persistence, and the electronic
  non-heating baseline pass.
- The recovery-only non-heating snapshot passed at configuration generation
  `174`. Normal main-temperature control was then restored and passed another
  reset at committed generation `175` with the original setpoint and
  calibration unchanged. Active heater demand and normal output-bit toggling
  were observed.
- CID remains `035344535330384780976F0085018507`; no SD format,
  initialization, removal, insertion, or replacement occurred.
- Graph cache returned ready with real data after reset.
- Evidence:
  `work/evidence/controller-b-recovery-baseline-20260727.md`.

### Historical 32 KiB buffered USB-publication image

- Debug S-record SHA-256:
  `35B020FDBDF2E02E0ACD96E83A261917A11F5EE48DB24058FB98450F6A956B4F`.
- Programming/verify/reset/run: PASS on J-Link `69660123`.
- CID unchanged at `035344535330384780976F0085018507`.
- Real retained-range export published 1,775 records with zero gaps,
  fallbacks, dropped logs, system errors, or HPT/USB status.
- Timing: `2.22 s` HPT staging, `2.04 s` USB publication through final
  flush/rename, `4.29 s` total; 3 bounded writes.
- Boot cache ready in `2.87 s` total (`2.06 s` traversal).
- No format or initialization occurred. Lane oldest starts remain
  `86 / 86 / 1`; active starts `1109 / 1109 / 1024`; retirements `2 / 1 / 0`.
- Final Graph is active and following newest with current rendering and zero
  viewport lag; newest was `39 s` behind RTC at capture.
- Evidence:
  `work/evidence/hpt-usb-csv-buffer-window-tuning-20260726.md`.

### Prior graph real-event timer image

- Debug S-record SHA-256:
  `D3D3615586FD522A9472504EAB55BC8A6F4955956AAE3229CCD397A0AD1A1EAF`.
- Programming/verify/reset/run: PASS on J-Link `69660123`.
- CID unchanged at `035344535330384780976F0085018507`.
- Cache ready in `2.62 s` total (`1.78 s` traversal), `720` chart records.
- Real `GX_SIGNAL` task-button paths advance on a later persisted record at
  24, 12, 6, 3, and 1 hour zoom; Pan Left hold and Pan Right reattachment pass.
- Owner observed advancement while zooming in and accepted the correction on
  2026-07-26.
- No format or reinitialization occurred; abnormal lane starts remain
  `86 / 86 / 1`.
- Evidence:
  `work/evidence/graph-real-event-refresh-timer-correction-20260726.md`.

### Historical graph-follow review image

- Debug S-record SHA-256:
  `143F1941FCF43BD31A5084CF21E0BC8595880F8E58C2CBA22B98D594759C3124`.
- Programming/verify/reset/run: PASS on J-Link `69660123`.
- CID unchanged at `035344535330384780976F0085018507`.
- Cache ready in `2.60 s` total (`1.75 s` traversal), `720` chart records.
- Active Graph followed new records with zero edge lag at 1, 3, 6, 12, and
  24 hour zoom; pan-away hold and exact Pan Right reattachment passed.
- B was not formatted or reinitialized; lane starts remain `86/86/1`.
- Evidence: `work/evidence/graph-follow-newest-correction-20260726.md`.

### Prior warning-truth review image

- Debug S-record SHA-256:
  `944BEA28BFD6DE5604A5BE1B03F4F5690CA84213B2BD923940ED27D193844501`
- Programming/verify/reset/run: PASS on J-Link `69660123`.
- Fresh CID/read/HPT baseline: PASS; raw CID unchanged at
  `035344535330384780976F0085018507`.
- Exact setpoint exercise: `23.900045 C` to `24.000046 C` and back to the
  original bits; both saves recovered from first-attempt
  `SSP_ERR_CMD_LOCKED` on attempt 2, warning transaction remained zero, and
  RAM plus both VEEPROM blocks match.
- Graph cache: ready with real data; `1,445` scanned, `1,440` selected;
  `1.64 s` traversal and `2.51 s` total; `274` read commands, `8,368` blocks,
  zero bulk fallbacks.
- Preserved abnormal state: lane oldest sequences `86/86/1`, active sequences
  `1109/1109/1024`, active records `337/337/422`, with no format or
  reinitialization.
- Evidence:
  `work/evidence/operator-warning-truth-and-target-proof-20260726.md`.

### Prior retained-start review image

- Debug S-record SHA-256:
  `91D05B3593D58DD525FFA2EDA74E165D25967652EBE3D0B885CC8368F180CCB5`
- Programming/verify/reset/run: PASS on J-Link `69660123`
- Fresh CID/read/HPT baseline: PASS; raw CID unchanged at
  `035344535330384780976F0085018507`
- Graph cache: ready, complete, retained data present, `720/720`, zero system
  errors
- Bulk-16 timing: `1012` scanned, `1007` selected; traversal
  `114 ticks / 1.14 s`; total `198 ticks / 1.98 s`; `181` read commands,
  `5,764` blocks, maximum `32` blocks/command, `65` refills, zero fallbacks
- Published retained customer bound: sequence `2`, timestamp `301741860`
  (`2026-07-25 09:11 UTC`)
- Preserved abnormal state after normal logging: active records
  `930/930/1015`, first sequences `86/86/1`, retired segments `2/1/0`
- Identity-capture dropped-log count: `0`
- Adjusted-start USB export: PASS; 1,024 records, zero gaps, COMPLETE
  publication, filename starts at retained `20260725t0911`, and HPT staging
  measured `2.84 s`
- Evidence:
  `work/evidence/hpt-export-start-adjustment-20260726.md`
- Performance plan:
  `work/wp/completed/wp-optimize-hpt-triple-mirror-read-performance.md`

### Previous frozen-candidate qualification

- Firmware implementation commit:
  `391c7b4d053ee146b823c505987897d3f88c0022`
- Artifact freeze commit:
  `c0901312e0fe850d8a0b2452eb20d88c86ce07bd`
- Debug S-record SHA-256:
  `D386F03460E225B683D5146FFC7AD949CCFEF71A3EC8169C944EFA82B5992F9F`
- Programming/verify/reset: PASS on J-Link `69660123`
- Card protocol status, CID validity, and representative-sector read: PASS
- Raw CID: `035344535330384780976F0085018507`
- Guarded HPT initialization and three predecessor cold-start/reopen/CID
  witnesses: PASS
- Full-address read-only scrub: PASS; all `15,523,840` sectors accounted for,
  zero failures, retry recoveries, identity mismatches, or HPT errors
- Integrated HPT/chart/logging gate: PASS; zero system errors, raw HPT open,
  representative read good, and bounded chart rebuild completed `720/720`
- Evidence:
  `work/evidence/post-freeze-integrated-qualification-20260725.md`

Controller B cycle 3 is already terminal-success evidence and must not be
repeated. The owner reported PASS on 2026-07-25 for visual
wording/placement/legibility, touchscreen navigation, and alarm audio.
Degraded-media, interruption, endurance, and multi-sample work remains
separately scoped and is not implied by this pass.

## Service 474 snapshot

- Final state: 3 (Stopped), intentionally stopped
- Run: `35709`
- Elapsed seconds/completed records: `5240` / `5240`
- Dropped/mirror/I/O/latched failures: all zero
- Reset count: `0`
- Live and persisted records matched after programming/debug qualification

## Open inventory and authority fields

- Installed SD: owner-identified SanDisk EDGE 8 GB; controller-reported
  SanDisk/WD `SS08G`, serial `0x976F0085` / `2540634245`, manufacture
  `2024-05`, raw CID `035344535330384780976F0085018507`
- Automated power: G-PWR-B fully passed with three current-firmware reset
  witnesses and matching baseline/post-reboot CID identity; see
  `work/evidence/hpt-log-store-circular-mirror/controller-b/g-pwr-full-20260725/qualification-result.md`
- Configuration and calibration backup/hash: complete; pre-change VEEPROM,
  RAM configuration, and option-memory hashes are recorded in
  `work/evidence/controller-b-recovery-baseline-20260727.md`
- Known-good recovery image/hash: complete; exact S-record/ELF and matching
  four-MiB internal-flash hashes are recorded in the same evidence
- Electronic recovery-only non-heating snapshot: complete and proven across
  reset at generation `174`; normal control subsequently restored at generation
  `175` for full-function qualification
- Independent physical protection and emergency disconnect: confirm for each
  later energized or destructive run; not inferred from this electronic
  baseline
- Destructive media, power-cut, or long-duration authority: operation-specific;
  do not inherit authority from the historical campaign record

Historical Setup B evidence through 2026-07-16 used controller `1751136` and is
retained in `smi-setup-b.md`. It must not be relabeled as coverage for this
current connected controller.
