-
Notifications
You must be signed in to change notification settings - Fork 171
initial stm32u3 support #685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
You're right, I went back and looked at the other files, and they are like this. |
stm32-data-gen/src/interrupts.rs
Outdated
| ("TIM", &["BRK", "UP", "TRG", "COM", "CC"]), | ||
| ( | ||
| "TIM", | ||
| &["BRK_TERR_IERR", "BRK", "UP", "TRG", "TRG_COM_DIR_IDX", "COM", "CC"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BRK_TERR_IERR, TRG_COM_DIR_IDX don't look like signal names. They're most likely a combination of multiple signals, where the signals are actually BRK, TERR, IERR, etc.
No idea what these are (TERR, IERR, DIR, IDX). Maybe they're something new in U3? If so we should ideally make it so they only appear in the U3 generated JSONs and not other families.
If you want to just those signals for now that's fine too, they can be added later when someone needs them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're correct about them being a combination of signals. They are identical to the U5. Should I rename the interrupt name similar to how other typos are fixed in the process function?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Dirbaio I backed out that original code and now rename the divergent interrupt names. Let me know if this should be generalized or if this targeted rename is fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!!
Yeah the rename is fine, the codebase is already full of similar renames 😅
No description provided.