circuits/board.py re-implements every block (power tree, RP2350 core, audio chain, RTC, MIDI-DNP, interconnects, SIG/CLIP-DNP, speaker-DNP) with shared net objects and SKiDL auto-assigned reference designators -> one coherent board.net for PCB layout. 167 components, unique refs U1-U18 / K1-K3 / J1-J5. ERC 0 errors; netlist 0 errors. Remaining ERC warnings are all benign unconnected-pin notes on intentionally-spare pins (relay NO contacts, 4 unused ULN2003 channels, spare GPIOs, 2 unused 74LVC14 inverters, RTC CLKOUT, TPS65131 BSW) and OC<->GPIO notes (comparator/opto outputs read by the MCU). MCLK-less: PCM5102A SCK tied to GND (internal PLL). This is the complete schematic deliverable: board.net + BOM.csv ready for layout. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| circuits | ||
| sim | ||
| Containerfile | ||
| README.md | ||
| run.sh | ||
PM_K-1 EDA environment
A reproducible container with the tools to design, check, and simulate the core board — so the work doesn't depend on whatever happens to be installed on a given machine, now or in 50 years.
What's inside
- KiCad 9 — schematic capture + PCB layout, and a CLI (
kicad-cli) that can run ERC (Electrical Rules Check) and DRC, and export netlists/PDF/Gerbers. - ngspice — SPICE simulator for validating the analog audio circuits before we commit copper (op-amp stages, filters, input loading, etc.).
- python3 — scripting, BOM munging, optional code-defined-schematic helpers.
Why a container?
The system KiCad here is 7.0, whose CLI can't run ERC (that arrived in KiCad 8). Rather than fight the host, we pin a known toolchain. Anyone — including future-you — rebuilds the exact environment with one command.
Use it
cd hardware/eda
./run.sh # interactive shell, lands in hardware/kicad/
./run.sh kicad-cli version # confirm KiCad 9
./run.sh kicad-cli sch erc pm_k1_core.kicad_sch # run ERC on the schematic
./run.sh ngspice -b ../eda/sim/input_loading.cir # run a simulation (cwd is kicad/)
run.sh builds the image on first use, then mounts the whole repo at /work (so KiCad sees
hardware/). Use RUNTIME=docker ./run.sh … to use Docker instead of Podman.
Layout
eda/
Containerfile # the pinned toolchain (KiCad 9 + ngspice + python)
run.sh # build-if-needed + run with the repo mounted
sim/ # ngspice decks (SPICE simulations of the analog circuits)