Allow RP2040 crystal traces to be routed - #96
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Thank you for your contribution! 🎉 PR Rating: ⭐⭐ Track your contributions and see the leaderboard at: tscircuit Contribution Tracker |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
The RP2040 crystal endpoints are about 16.23 mm apart, while the default 10 mm trace budget can cause those connections to be skipped.
Scope
This PR does not change package build scripts, add a
preparelifecycle, or add a build-specific TypeScript configuration.Validation
bun test tests/test.test.tsx— 18 passed, 142 assertionsbun run build:libbunx tsc --noEmitbun run formatgit diff --check