# Ticket: Report SD card CID identity with service code 467



Status: complete; owner verified the complete compact service-467 display on Controller A
Type: ticket
Updated: 2026-09-23
Next Action: none; retained as history; any new execution requires a new explicit owner instruction
Parent: work/wp/active/wp-triple-mirrored-circular-hpt-log-store.md
Canonical Truth: docs/sd-card-operation-and-recovery.md

## Problem

The Renesas SDHI driver requests the SD card's 128-bit CID during startup but
does not preserve or expose it after initialization. The application therefore
cannot report the installed card's manufacturer ID, OEM/application ID, product
name, product revision, serial number, or manufacturing date. This limits
commodity-card inventory, batch comparison, replacement tracking, and
counterfeit investigation.

## Expected Behavior

Capture the CID response during the existing read-only SD initialization
sequence, decode it without changing card contents or filesystem/raw-media
ownership, and expose the identity through engineering service code 467. The
screen must work for FAT32 and raw-HPT cards and clearly distinguish unavailable
or invalid identity data.

## Acceptance Criteria

- [x] The SDMMC driver preserves the complete raw 16-byte CID response before
      later commands overwrite the response registers.
- [x] Application status reports CID validity, manufacturer ID,
      two-character OEM/application ID, five-character product name,
      major/minor product revision, 32-bit serial number, and manufacturing
      month/year.
- [x] CID collection is read-only and independent of FAT32 versus raw-HPT media.
- [x] Service code 467 presents every requested field and the raw CID in a
      bounded screen with a normal back action at `OPERATOR_ACCESS`; it must
      not require factory/service elevation or a confirmation gate.
- [x] The display resolves the approved 37-code public SD MID table, keeps
      uncertain attributions explicit, and falls back to `Unknown` while
      retaining the raw MID.
- [x] Missing-card or unavailable-CID state is explicit and does not display
      stale identity from a previously installed card.
- [x] Host/static tests cover field decoding, bounded strings, service routing,
      read-only capture placement, and unavailable-state behavior.
- [x] Debug firmware builds cleanly and Controller A is programmed with the
      exact verified image.
- [x] Post-load Controller A health is nominal and service 467 is ready for
      owner visual review.
- [x] Owner confirms that every service-467 field is simultaneously visible
      in the compact layout.

## Implementation Result

- Owner review found that the original 36-pixel message font clipped the
  revision, serial number, manufacturing date, and raw CID below the content
  area. Service 467 now selects the existing 24-pixel bold font; ordinary
  message screens explicitly restore the 36-pixel default. Two decorative
  blank rows were also removed, reducing the complete valid-CID report to ten
  lines with vertical margin.
- On 2026-07-24 the owner reran service 467 on Controller A and confirmed that
  the final `Raw CID` field is visible, completing the visual acceptance gate.
- The protocol-status extension supersedes the earlier review image. The
  current programmed Debug S-record SHA-256 is
  `24BFA31E189F5504EE5602F2326012E9ADC02341FF501E9879D334AC60F5C66E`.
- Stable/versioned ELF SHA-256:
  `1ED9058F98511A0C701A7E8E30A6DA480B4364E306FE0B3C6C0477C771070122`.
- Service 467 now precedes the CID fields with the installed/read-error/needs-
  initialization/ready classification and explicit CID/sector-read evidence.
- Earlier identity-only Debug/versioned S-record SHA-256:
  `A6C90CBA094EB36624EC83F07C6342B2B9C55FD8FAAF0ABF9B3838B02D3101F6`.
- Controller A / J-Link `69664082` programmed and verified through
  `jong@srv-rpi00.local`; target voltage was 3.283 V and the CPU was resumed.
- Post-load RAM reported hardware version `0`, no main-system error,
  SD driver status `0`, raw-HPT-ready state `6`, and a valid CID.
- Decoded installed card: manufacturer `0x03`, OEM `SD`, product `SS08G`,
  revision `8.0`, serial `0x976F0084`, manufactured `2024-05`.
- Service 467 now displays `SanDisk/WD (MID 0x03)` for the installed card.
  Its curated public lookup covers 37 SD MIDs and labels uncertain or unknown
  attributions explicitly.
- Static/regression gates passed: CID `25/25`, SD safety `20/20`, and HPT
  commissioning `82/82`.
- The qualified GCC 10.3 Debug compile and link passed at 2,869,924 bytes text
  and 28,462,852 bytes BSS.

## Verification

- Run the CID/service static fixture.
- Run the established SD/HPT regression fixtures.
- Run a clean Debug build and record ELF/SREC hashes.
- Program and verify Controller A through the hostname-only J-Link hub.
- Read back firmware identity, CID status, SD state, and system-error globals.
- Owner enters service code 467 and reviews the displayed identity.

## Scope Boundary

This ticket does not use CID as an authenticity guarantee, alter the HPT media
format, persist identity onto the SD card, select approved vendors, or perform
any destructive media operation.

## Owner-directed reconciliation — 2026-09-23

Reconcile stale active lifecycle to the previously documented completed disposition; no new test or broader acceptance claim.

Authorization: Owner instruction in this conversation on 2026-09-23 to close/abandon the named work and mitigate older active records.

Previous header retained for evidence interpretation:

> Status: complete; owner verified the complete compact service-467 display on Controller A
> Next Action: none

Earlier observations, unchecked historical criteria, and procedures below/above remain history. This administrative disposition does not qualify a new firmware candidate, physical card, thermal system, ECO, or release. Current 00.05.01 obligations in IDEA-0006, IDEA-0007, MAP-0009, and CAMP-0028 remain unchanged.
