5f159f518e75ff14277558467b93ba2e0f6c2099dcabaa7291246017957d658e
AutoPhi BGA Library - AUTOPHI_BGA256 (v1)
Publicly online since 2010 · U.S. patent applications since 2012 · inventions offered since 2014. The work of Christopher Gabriel Brown, independently documented.
Downloads immediately on checkout — the CD GDSII Generator (AES-256 encrypted). Open with 7-Zip, WinRAR, or macOS Archive Utility using password CRIONE99KEY. Founder Access Pass credit (code FAP99CREDIT) applies at checkout.
AutoPhi BGA Library — AUTOPHI_BGA256 (v1)
Every board project that wants to land a 256-ball BGA needs three things in agreement: the footprint that says where the pads go, the symbol that says what the pins do, and the pinmap that says which pin is which. When those three drift apart, you get a board that doesn't route, a chip that doesn't fit, or a power rail that lands on a signal pin.
This library exists so they don't drift apart. One source of truth. Every board project pulls from here.
One library. Every board project pulls from it. No ad-hoc BGA data anywhere.
The 40-autophi-bga project is the dedicated source-of-truth for AutoPhi BGA component definitions — footprints (libs/footprints), symbols (libs/symbols), pinmaps (pinmaps), and the repeatable scripts (scripts) that generate and validate them. Board projects (for example 35-autophi-quantum-pcie5 and 39-autophi-pcie5) consume from this library; they do not define BGA data ad hoc. AUTOPHI_BGA256 (v1) is the 256-ball production seed in this library — 20 mm × 20 mm package, 1.0 mm pitch.
What This Is
AUTOPHI_BGA256 (v1) is the first-version released entry of the AutoPhi BGA library at the 256-ball size class. The release is a coherent set of three artifacts that all reference the same canonical pin grid:
- Footprint —
libs/footprints/AutoPhi.pretty/BGA-256_20x20mm_P1.0mm.kicad_mod. KiCad-format mechanical footprint, 20 mm package, 1.0 mm pitch, 256 balls. Seeded from the upstream 39-autophi-pcie5 board project and lifted into this library as the canonical source. - Pinmap —
pinmaps/AUTOPHI_BGA256_pinmap_template.csv. CSV pinmap derived directly from the footprint pads, so the rows correspond ball-for-ball to the mechanical footprint. Every pin has a row entry. - Symbol — KiCad symbol library (
libs/symbols/AutoPhi_BGA.kicad_sym) generated from the pinmap byscripts/generate_bga_symbol_from_pinmap.py. References the footprint asAutoPhi:BGA-256_20x20mm_P1.0mm.
The three artifacts are not assembled by hand; they are derived from each other through scripted generation. That is the library's correctness guarantee — there is no path by which the symbol references a pin that is not in the pinmap, or the pinmap references a ball that is not in the footprint.
Library Inventory — What's in the Folder
| Path | Contents |
|---|---|
libs/footprints/ | BGA mechanical footprints, KiCad .kicad_mod. Includes BGA-256 (20 mm, 1.0 mm pitch) and the larger BGA-1536 (95 mm × 90 mm, 2.0 mm pitch). |
libs/symbols/ | KiCad symbol libraries (.kicad_sym) generated from the pinmap. Includes AutoPhi_BGA.kicad_sym and AutoPhi_BGA1536_working.kicad_sym. |
pinmaps/ | CSV pinmap definitions. Per-package template + working pinmaps. |
scripts/ | Repeatable Python and PowerShell generation, seeding, validation, and reporting scripts. |
docs/ | Library governance docs: BGA_CATALOG.md, CANONICAL_DIMENSIONS_MATRIX.md, LIBRARY_GOVERNANCE.md, POWER_POLICY.md, RELEASE_V1.md, BOARD_SERIES_STATUS.md, PINMAP_SEEDING_LOG.md. |
exports/ | Build outputs — e.g., magento_import_series_draft.csv, the consolidated Magento draft for the BGA library plus the 34 board rows. |
output/, sources/ | Working build artifacts and upstream source captures. |
Profile-Based Generation — Reproducible, Not Ad-Hoc
The library carries a profile-switching mechanism in its geometry-seeding scripts. Profile defaults are supported for v19_default, zetta_ref, and smd15_ref. A profile selects a dimension and default set; only the fields that need to differ from the profile are explicitly overridden at generation time.
That means a buyer who has the library can generate a new BGA footprint at a different ball count, package size, or pitch without writing a footprint by hand:
python scripts/generate_bga_footprint_grid.py \
--out libs/footprints/AutoPhi.pretty/BGA-1536_95x90mm_P2.0mm.kicad_mod \
--name "BGA-1536_95x90mm_P2.0mm" \
--profile v19_defaultAnd a new pinmap CSV is derived directly from the footprint, then a new KiCad symbol is regenerated from the pinmap — the same chain that produced AUTOPHI_BGA256 (v1) produces every subsequent variant. No drift.
Mechanical Envelope
Current mechanical-planning envelope for BGA interchange across the AutoPhi board series is up to 95 mm, based on the latest board mechanical-clearance updates. The 20 mm AUTOPHI_BGA256 sits well inside that envelope; the 95 mm × 90 mm AUTOPHI_BGA1536 sits at the envelope's edge by design and is the test case for the largest package the series can carry.
Validation Pipeline
The library carries a validation script (scripts/validate_bga_library.py) that takes pinmap + symbol + footprint + KiCad reference triples as input and confirms they are consistent. Running it against AUTOPHI_BGA256 (v1) is part of the release-acceptance gate. The same validator runs against the BGA-1536 entry. Output is a structured pass/fail report.
USPTO Patent Status
The BGA library underpins board projects covered by the AutoPhi patent portfolio — principally USPTO 18/370,908 (AutoPhi quantum-battery and propulsion IC) and the umbrella USPTO 19/540,453 (Integrated Technology Portfolio) — through the board projects that consume it (Projects 35, 39). The library itself is engineering source-of-truth content rather than a separately-claimed invention; its patent value is its role as the canonical foundation for the board-project filings that depend on it.
How it's made
AUTOPHI_BGA256 (v1) is built by running the library's own generation scripts in the canonical sequence: (1) the BGA mechanical footprint is seeded from the upstream 39-autophi-pcie5 board project; (2) scripts/generate_bga_pinmap_template.py derives a pinmap CSV directly from the footprint's pads; (3) scripts/normalize_pinmap_placeholders.py normalises noisy placeholders into a clean working pinmap; (4) scripts/seed_ab_domains.py seeds provisional canonical voltage and signal domains; (5) scripts/promote_provisional_signals.py promotes the provisional names to stable canonical names; (6) scripts/finalize_power_rails.py finalises voltage-domain placeholders; (7) scripts/generate_bga_symbol_from_pinmap.py generates the KiCad symbol library from the working pinmap; (8) scripts/validate_bga_library.py confirms pinmap + symbol + footprint alignment.
The whole pipeline is reproducible end-to-end via scripts/rebuild_provisional_seed.ps1. A buyer can re-derive the v1 release from the source pinmap on their own workstation; the script's output is deterministic.
Why I made it
I had two board projects in the AutoPhi portfolio that needed the same 256-ball BGA — project 35 (autophi-quantum-pcie5) and project 39 (autophi-pcie5) — plus a third project (this library, project 40) that needed to be the canonical source so neither board could drift independently. The earlier convention of defining BGA data inside each board project produced exactly the kind of drift this library exists to prevent: footprints that disagreed with symbols, pinmaps with stale placeholders, no validator that would catch any of it.
The library's purpose is to be the version-controlled, generation-script-backed, validator-checked source-of-truth so that every board project in the portfolio (current and future) consumes from one place. AUTOPHI_BGA256 (v1) is the first stable release the board projects can depend on. Subsequent versions will be released through the same pipeline.
What it can do
An acquirer who licenses AUTOPHI_BGA256 (v1) takes possession of:
- The KiCad mechanical footprint
BGA-256_20x20mm_P1.0mm.kicad_mod, ready to drop into any KiCad board project. - The CSV pinmap template
AUTOPHI_BGA256_pinmap_template.csv, derived directly from the footprint pads. - The KiCad symbol library generated from the pinmap, referencing the footprint by canonical name.
- The full set of generation, validation, seeding, and reporting scripts (
scripts/) that built the v1 release. - The library governance documents (
docs/) explaining the canonical-dimensions matrix, power policy, library governance, and v1 release notes.
What the library is not: it is not a finished board layout. It is the BGA-component foundation a board layout consumes. A board project that uses the library still does its own routing, placement, and mechanical decisions; the library guarantees that the BGA component the board references is internally consistent and validator-clean.
Why it's a fact
Every claim above can be checked against the source record:
- The footprint file
BGA-256_20x20mm_P1.0mm.kicad_mod, the pinmap CSV, and the KiCad symbol library all exist on disk underD:\special\40-autophi-bga256\. They can be opened in KiCad and inspected. - The generation, seeding, normalisation, promotion, finalisation, symbol-generation, and validation scripts under
scripts/are reproducible Python and PowerShell. A buyer can re-run the rebuild pipeline (scripts/rebuild_provisional_seed.ps1) and confirm that the v1 outputs match the released artifacts. - The validator (
scripts/validate_bga_library.py) emits a structured pass/fail report; running it against AUTOPHI_BGA256 (v1) is the release-acceptance gate, and its output can be re-generated. - The companion BGA-1536 entry exists in the same library (
BGA-1536_95x90mm_P2.0mm.kicad_mod, plus pinmaps and a working symbol). Its presence demonstrates that the same generation pipeline scales to the 1536-ball size class. - The board projects that consume the library — Projects 35 (autophi-quantum-pcie5) and 39 (autophi-pcie5) — exist as separate folders in
D:\special\; their dependence on this library is documented in the library'sdocs/BOARD_SERIES_STATUS.md.
ISBN Anchoring — Note
BGA library content is engineering source rather than text-anchored prior art, so the library itself does not carry an ISBN. The board projects that consume the library (35-autophi-quantum-pcie5, 39-autophi-pcie5) and the broader AutoPhi documentary record may carry ISBN-13 anchors associated with specific filings; cross-references can be supplied on request.
License Terms — What's Granted, What Isn't
The acquisition grants the buyer permission to make, build, and copy the deliverable. It does not transfer the underlying intellectual property:
- Granted with the acquisition: permission to use the canonical BGA-256 footprint, pinmap, and KiCad symbol in the buyer's own board projects; permission to build boards consuming the library; permission to make copies of the library for the buyer's engineering and team-distribution use; permission to run the generation, validation, and reporting scripts against the buyer's pinmaps.
- Not transferred with the acquisition: the AutoPhi quantum-battery / EM propulsion IC patents (USPTO 18/370,908 and the Integrated Technology Portfolio umbrella 19/540,453) that the consuming board projects fall under, the inventor's broader BGA library work, trademarks, copyrights, or any rights to license or assign the IP onward. The intellectual property remains held by Christopher Gabriel Brown.
- The buyer's permission is to use the library, not to own the rights behind the library.
This framing applies uniformly across the inventor's portfolio. Buyers seeking IP assignment rather than make/build/copy permission should contact the inventor directly — that is a separate negotiation outside the standard storefront acquisition.
The library is the standardisation. Standardisation is leverage.
A buyer who acquires this library acquires the right not to re-debate the canonical 256-ball BGA across every board project in their pipeline. The footprint, pinmap, and symbol agree. The scripts make sure they keep agreeing. That is the library's commercial value.
One canonical 256-ball BGA, validator-clean, scripted-to-rebuild.
The AUTOPHI_BGA256 (v1) acquisition delivers the KiCad mechanical footprint, the CSV pinmap derived from the footprint, the generated KiCad symbol library, the full generation and validation script set, and the library governance docs that explain how the release was assembled. Reproducible end-to-end from a single PowerShell script.
The library is the engineering source-of-truth for AutoPhi BGA component definitions. Board projects consume from it, including the in-portfolio AutoPhi V19 QSFP28 Optical BGA256 KiCad design package (Project 39) and the AutoPhi Quantum PCIe 5.0 board (Project 35). Validator-clean. v1 release.
Price: see store listing
Engineering source-of-truth. Patent coverage flows through the consuming board projects under USPTO 18/370,908 and umbrella 19/540,453. Contact via the store.
