Skip to content

Document advanced BGA breakout fanout - #833

Merged
seveibar merged 6 commits into
mainfrom
agent/document-bga-bus-breakout
Jul 31, 2026
Merged

Document advanced BGA breakout fanout#833
seveibar merged 6 commits into
mainfrom
agent/document-bga-bus-breakout

Conversation

@seveibar

@seveibar seveibar commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Summary

  • replace the lead <breakout /> example with an advanced 100-pin BGA fanout
  • configure bus directions, escape layers, boundary padding, and pour-net plane drops directly on <breakout>
  • route two contiguous 8-bit outer-pin buses toward explicit left/right exits
  • drop center-region GND/VCC balls into mapped inner1/inner2 copper-pour planes
  • move the two bus endpoint chips farther from the BGA
  • remove the unnecessary <autoroutingphase> from the example and prose

Dependencies

Why

The common one-stage breakout case should not require a nested routing phase. The example now presents the intended API directly on <breakout> while showing the usual BGA pattern: clustered signal buses on perimeter balls and power/ground escapes from the center of the array.

Validation

  • compiled and routed the exact extracted preview against the local props/core branches with no <autoroutingphase>
  • verified no autorouting, trace, pad-clearance, or via-clearance errors
  • verified vias terminate on both inner1 and inner2
  • bun run build
  • bun run typecheck
  • git diff --check

@vercel

vercel Bot commented Jul 30, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview Jul 31, 2026 2:33am

Request Review

@seveibar
seveibar marked this pull request as ready for review July 31, 2026 04:10
@seveibar
seveibar merged commit 9f97b70 into main Jul 31, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant