-
Notifications
You must be signed in to change notification settings - Fork 79
Add Attiny417/817/1617/3217 support #184
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
Hi, thanks a lot for your contribution! Just a heads-up, I am holding off merging new chips right now until #157 is merged, which quite significantly changes the way the register definitions are generated. I will ping you once this change has landed so you can rebase your changes ontop of it. |
Here's the notification: #157 was merged 🎉 Please rebase your work ontop of the new code-generation. You should be able to make out the new structure in |
Simple: That's what semantic versioning is for. I'll bump the version appropriately to release such breaking changes. No need to hold back improvements, especially as we are still in 0 versioning land :D In more serious terms: I am not afraid of releasing breaking changes for |
There we go! That should work :) |
Famous last words... edit: Fixed |
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.
Hi, thanks a lot for the contribution! I'll have to ask you to rebase on main
once again due to some merge conflicts...
This patch adds support for the Attiny417, 817, 1617 and 3217.
These are all tinyAVR 1-series devices.
I added a lot of SVD patches for all tinyAVR devices in the common definition and one specific patch for the
TCD
timers that seem to be available only for the 1-series chips.The patches add a lot of fixes and make things more ergonomically usable by properly turning things into arrays, adding proper enum values or fixing access (RW, RO, WO etc.) issues. They should all be fine, but might break other people's code. I am not sure what your policy is on something like this.