Accept a serial PASS only when a complete result record belongs to the expected unit, qualified boot instance, current test request and test identity. Clearing a buffer or reopening a port does not create that relationship. Stale output can arrive after either action, and a plain success string carries no evidence about which run produced…
When a hardware-test worker disappears, move its board into recovery quarantine before assigning it again. Establish that the old owner can no longer issue commands, reconcile any operation already in flight and verify the required hardware state. Process death, reservation expiry and safe physical cleanup are separate facts. This design uses upstream labgrid 24.0.2 as…
If a hardware test fails only when another device starts, treat the shared supply and wiring as test resources that can couple otherwise independent jobs. Compare each device alone with controlled concurrent and staggered activity, while observing voltage at the affected load. A supply’s front-panel reading or nominal current rating does not establish that both…
A second-run pass is a new observation, not a replacement for the first failure. Keep both attempts, identify what changed between them and require an explicit disposition of the conflicting evidence. Repeatedly pressing “run” until a green result appears creates an undocumented selection rule rather than a qualified acceptance process. This article defines an original…
After a programmer disconnects, revoke the previous connection’s permission to write. Re-establish the physical unit, selected adapter, approved artifact and programming recipe, then reconcile the interrupted operation before considering a retry. USB reconnection or a familiar filename is not enough evidence to repeat a flash command. The concrete interface reference is upstream OpenOCD 0.12.0. An…
A completed, error-free verification with reconciled section and byte coverage establishes a specific image-to-memory comparison through the selected access path. A success return or banner alone is insufficient, including in the pinned OpenOCD version below. It does not establish that the board selects that image at reset, executes it correctly or meets a product requirement….
Classify a suspected pogo-pin failure by tracing the complete fixture contact path and changing one controlled factor at a time. A pass after reseating shows that the outcome depends on the changed condition; it does not establish that the product was good, that the pin was bad or that the original failure may be discarded….
A production “golden unit” is useful when it has a controlled measurement history, a defined set of representative functions and an independent way to question its own stability. A single passing reference board cannot prove that the station is accurate, and a single failing reference board cannot identify whether the station or the reference changed….
Preserve calibration as a unit-bound service artifact, not as an anonymous file copied from the nearest working board. Before storage replacement, establish which physical unit and calibrated assembly produced the data. Before any later import, independently identify the destination and compare that identity with the protected export record. This guide defines a read-only export and…
Check the limits stored in the existing littlefs superblock before reducing firmware’s name, file or attribute limits. An image can be incompatible with a smaller build even when every current filename and file happens to be short. The stored capability contract matters independently of today’s contents. This guide is pinned to littlefs v2.11.2. It qualifies…