Incorrect MCXA2xx Metadata for FlexCAN + Gates#109
Merged
Conversation
bjackson312006
changed the title
felipebalbi
approved these changes
Jul 1, 2026
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.
This PR fixes two issues in
data/metadata/MCXA2xx.jsonrelating to FlexCAN metadata:P2_0toP2_1. This is consistent with the chip's datasheet (ALT11 - CAN1_TXDis listed forP2_1on page 120). This also fixed a pin collision (since CAN0_RXD also listed asP2_0, which would be impossible). Note: This issue also seems to be present forLPUART0, sinceP2_0is listed for both TXD and RXD (see around line 6895 indata/metadata/MCXA2xx.json), but I didn't change that since it's out of scope for this PR.This PR also adds gates in
mcxa2xx.jsonandmcxa5xx.json.After making those changes, I regenerated the PAC.