BOM Table: Every Component from the Design Files
Open the BOM tab and see every component on the ZEReader board — parsed directly from KiCad schematics, no CSV export needed:
- MCU: Raspberry Pi Pico 2 (module approach)
- Battery charger: BQ24090DGQ
- USB-C connector: GCT USB4105-GF-A
- SD card: Hirose DM3AT-SF-PEJM5
- Display connector: Hirose FH12-24S
Switch between Compact, Full, Manufacturing, and Sourcing views. Filter by value, footprint, or part number.
Diff: See Design Decisions, Not File Changes
Pick any two commits to see what changed at the component level. For ZEReader, the diffs reveal real design decisions:
- USB-C connector changed 3 times — first for compliance (CC pulldown resistors added), then for manufacturing (footprint violated DFM rules), then for availability (part went out of stock). Each swap is a single line in BOMblame's diff. In a KiCad XML diff, it's buried in hundreds of lines.
- Post-prototype value tuning — resistors and capacitors in the e-Paper driver circuit adjusted after real-world testing. The diff shows exactly which values changed and by how much.
Blame: Why This Part?
Every component in ZEReader traces back to a specific commit and author. "Why is this resistor 2.7k instead of 2.2k?" One click on the blame column: it was changed in the post-testing refinement commit, June 2025. Deliberate, tested, documented — without anyone writing documentation.
Design State: Is It Ready?
The Design State bar tells you at a glance:
- Are all components mounted on the PCB?
- Are footprints assigned to everything?
- Is sourcing data complete?
For a bachelor's thesis project evolving into a hobby initiative, this is the quickest way to assess "how done is this revision?"
Try It Yourself
Browse the BOM. Compare the first commit to the latest. Check which USB-C connector survived. That's BOMblame — making hardware history navigable.
Open ZEReader →