Files
pcb/.gitignore
onur 1ea2bc64ac Add the missing TPS2121 status pull-up (R108) and correct the power-mux docs
The power mux's status output had no pull-up, which broke the USB current
budget interlock.

TPS2121 ST is an open-drain output; the datasheet lists RST = 6-20 kOhm under
Recommended Operating Conditions, alongside RILM, so it is an external part.
ST is driven low only while IN2 (the J3 external 5 V header) is sourcing OUT,
and is high impedance whenever IN1 (the J7 USB-C input) is sourcing. U10 gate 2
inverts MUX_ST into EXT_SELECTED, and MAIN_EN = USB_3A_OK OR EXT_SELECTED
enables the 15 A core buck. With MUX_ST floating on USB-C power, a drift low
asserts MAIN_EN no matter what the TUSB320 advertised, so the board would try
to bring up the core rail on a 500 mA port. Every other open-drain net here
already has its pull-up (R7/R8, R30, R33/R34, R98/R104/R105/R106); this one was
missed.

R108 (10 k, VCC3V3_AUX -> MUX_ST) is appended at the end of design_data.py
rather than beside the mux: reference designators are assigned in call order,
so inserting it mid-file would renumber every later resistor and invalidate the
routed board. Placed at (53.0, 101.6), 2.4 mm from the U10 gate it holds up,
on a site checked clear of existing copper, and routed with close_remaining.py.

Also corrects POWER_TREE.md, which credited PR1 for giving the external input
priority. PR1 = GND actually *disables* priority mode; CP2 (tied to VCC3V3_AUX)
is what selects IN2. Since CP2 derives from the mux's own output the behaviour
is two-phase - highest-voltage wins at cold start, IN2 unconditionally once the
aux rail is up - so with both inputs connected there can be one seamless
switchover at startup. Documented, with the numbers: both eFuses UV 3.98 V /
OV 5.80 V, ILIM 2.69 A (USB-C) and 4.04 A (header), mux OV 5.69 V / ILIM 4.5 A.
The two inputs are never summed: both eFuses block reverse current and the mux
bonds exactly one input at a time.

board_routed.kicad_sch/.kicad_sym are now gitignored byte copies of the tracked
schematic; kicad-cli needs them beside the board for --schematic-parity, and
deleting them in the previous commit had silently disabled that check.

Verified: ERC 0/0, DRC 0 violations, 0 unconnected, every net one copper group,
schematic parity unchanged at the 402 pre-existing warnings.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012KaTmCCxCEW4awsmXRNT1d
2026-09-01 12:28:00 +03:00

44 lines
1.3 KiB
Plaintext

# Local tools and Python environments
.tools/
.venv/
venv/
__pycache__/
*.py[cod]
# KiCad local/editor state
*.lck
*.kicad_prl
*-backups/
*.bak
# Local manufacturer documents; links and policy are in references/README.md
references/official/
# Stale/intermediate routed board variants, regenerated by the routing flow.
# board_routed.kicad_pcb is the finished deliverable and IS tracked.
hardware/board_prerouted.*
hardware/board_plane_stitched.*
hardware/board_power_routed.*
hardware/board_power_local.*
# kicad-cli finds the schematic for --schematic-parity by matching the board's
# own basename, so board_routed needs a copy of board.kicad_sch beside it.
# It is a byte copy of the tracked original, so it is not tracked itself:
# cp hardware/board.kicad_sch hardware/board_routed.kicad_sch
# cp hardware/board.kicad_sym hardware/board_routed.kicad_sym
hardware/board_routed.kicad_sch
hardware/board_routed.kicad_sym
# KiCad writes these when it rescues a symbol; the originals are tracked.
hardware/rescue-backup/
# Routing/build workspace. Keep only the current review deliverables.
outputs/*
!outputs/README.md
!outputs/bom.csv
!outputs/jlcpcb_bom.csv
!outputs/erc_final_reset.rpt
!outputs/drc_final_placement.rpt
!outputs/drc_final_routed.rpt
!outputs/board_final_reset_top.png
!outputs/routing_report.txt