zudo-led-lamp
GitHub repository

Type to search...

to open search from anywhere

Current State and Completion

What the LED lamp's current build path is, which artifacts exist at which revision, what has and has not been ordered, programmed or measured, and the owner actions that remain, in order.

Order handoff reviewed on 2026-11-09, against lamp main 5726c8e6e89b5a03ba149c234cccda2f9afab6c8. Lamp PR #150 and tracker #149 are complete. External zudo-pd PR #234 is now merged; the owner handoff was inspected at 44fd3ba810aad627fd461b90093a3482707b44da on zudo-pd main. This page owns the LED lamp's current status. A software check, CAD result, order plan, received board and bench measurement establish different things; nothing on the current path has been programmed, energized or measured.

Adopted path: zudo-pd P15 r1 with the two existing Board Ls

DimensionRecorded state
Architecturezudo-pd P15 r1 (STUSB4500, 27 × 40 mm, 15 V / 3 A NVM image) feeding the two Board Ls from the 2026-09-19 order. Decided by the owner on 2026-11-03; LED first, then the same P15 design serves zudo-pd PD15
Canonical P15 sourceOwned by zudo-pd: boards/board-p15/board-p15-draft.kicad_pcb (SHA-256 97acc5f4…), NVM boards/board-p15/nvm/stusb4500-15v.bin (SHA-256 76622e14…). Consumer reference: boards/p15-r1-reference.json, checked by python3 scripts/checks/verify-p15-reference.py --pd-repo <zudo-pd checkout> (byte identity only)
Board Lboards/board-l/ as ordered on 2026-09-19, reused unchanged. RS1 = 200 mΩ; MCU believed blank
Historical Board Pboards/board-p/ is the as-ordered 2026-09-19 LED Board P. It is not P15 and not zudo-pd's 20 V Board P r3. Its records #143 and #144 describe those units only
Firmwarefirmware/board-l/target/ links the V72 portable sources for the STM32G031F8P6 with CTRL_FULL_CCR = 2407. Each build writes build/board-l-skeleton.receipt.json (revision, dirty state, toolchain, options, cap, hashes, memory) labelled UNFLASHED BENCH CANDIDATE. Linked is not flashed, option-byte-verified or measured
EnclosurePrototype 03 generator in enclosure/. P15 fit is a CAD result in candidates/p15-r1-enclosure-fit/ (nominal datums; 0.0 mm³ interference)

P15 has no hardware voltage window or eFuse. Requirement rows R2.3, R2.4 and R2.6 stay FAIL and R2.5 UNKNOWN; the owner accepted this as a prototype residual. Per-unit NVM acceptance is the only mitigation, and it is not a pass.

Checks completed in software and CAD, with their limits

CheckResultLimit
P15 consumer referenceMATCH against zudo-pd at the recorded commitByte identity; no electrical or physical claim
Target buildDefault ELF reproducible; header, option and Makefile changes rebuild (make check-incremental); CI job target-buildNot flashed; no option bytes read
Firmware host testsExisting V72 and target host tests pass in CIHost behaviour, not board behaviour
Enclosure CAD fit with P15PASS in an isolated generator runPrint, seating, USB plug engagement and screw fit unmeasured

Order, received, programmed and measured state

ItemOrderedReceivedProgrammedMeasured
P15 r1 × 2NOT ORDERED (plan only)—NOT RUNNOT RUN
Board L × 22026-09-19YesNOT RUN (MCU believed blank)NOT RUN
Enclosure———Not printed with P15

Owner actions, in order

#ActionProcedureEvidence to record
1Complete owner checkout checks, then order 2 × P15 r1 (zudo-pd owns the files)LED prototype-order handoffDownloaded hashes, all polarized placements including D5/D9, stock, assembly eligibility, total cost; eventual order date and number
2Incoming P15 inspection and per-unit NVM acceptance before any Board L connectionzudo-pd P15-NVM-1–7Power-cycle readback hash, 15 V contract on a 20 V-capable source with no load, and VBUS_OUT measured off during the 5 V attach phase (the POWER_ONLY_ABOVE_5V bit position is third-party and an ST draft note marks it reserved)
3Board L identity and unpowered checks, first energizing on a current-limited sourceBefore-programming checklist §0–2Board identity, RS1 four-wire (Kelvin) measured resistance with instrument/date, rail readings
4Option-byte readback, image identity against the receipt, firmware readbackChecklist §3–4; bench sheet OSave receipt and ELF identity; record option-byte readbacks separately. Raw flash-image readback must match artifacts.loadable_image_sha256 over exactly artifacts.loadable_image_bytes at the ELF-confirmed load range (current FLASH origin 0x08000000); see checklist §4 and bench sheet F
5Startup/CTRL measurement, knob calibration, LED current, thermal and NTC correlationChecklist §5–6; bench sheets B, K, C, N, TEach sheet row with the board identity
6Mate an accepted P15 with a passing Board L; record contract, ATT/PDOK and input currentChecklist and P15 procedureContract voltage, ATT/PDOK, input current
7Enclosure print and fit: seated gap, USB engagement, controls, retention, optical appearance, temperatureEnclosure guideMeasured gap, plug seating, photos, temperatures

Before action 4 the owner also chooses the first bench image's open firmware behaviour (noise configuration, gamma, latch and tuning values). The options and a recommendation are in firmware/board-l/target/OPEN-PRODUCT-DECISIONS.md. Keep RS1 = 200 mΩ and CTRL_FULL_CCR = 2407; the 250 mΩ and 3200 alternatives are not selected.

The existing Board Ls are not yet inspected or cleared to mate. Physical holds #34, #35 and #52 remain open. #145 (HUSB238) is an unadopted future alternative.

The prototype-order handoff separates verified source and four-file identity from full historical replay (NOT RUN, original STEP absent). Supplier preview and order-day stock, assembly eligibility and total cost remain unresolved owner actions. Cloud preparation does not mean ordered or qualified. zudo-pd#228 remains the external coordination record; it is not a prerequisite to use the inspected immutable owner handoff.

Revision History

CreatedUpdated