-
Notifications
You must be signed in to change notification settings - Fork 4
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
Support new PAC (0.5) #7
Conversation
Hi, thanks for the PR! Thanks! |
Thanks for taking a look!
I don't think so. The reason for this change is updates of the SVD tooling (in this PR and this PR and probably others). From what I can tell, the older version of the tooling did not differentiate between setting a bit, and clearing a bit by writing one (both were done with |
Hi, You can use raw bit manipulation instead of the interface. :) |
Sure, that would be possible :) It sort of defeats the purpose of using the PAC though. Do you see any harm in dropping support for the older PAC versions? Of course it's up to you, if you think raw bit-fiddling is the way to go, I'll make that change :) My goal is simply to have a rp2040-monotonic version that works with the latest rp2040-hal (which depends on the 0.5 pac). |
Desperate times, desperate measures. We go with manual bit fixing. |
Use `bit(true)` instead of `set_bit`, since `set_bit` was renamed to `clear_bit_by_one` for write-clear registers.
385a26d
to
d4342ab
Compare
It turned out to be as easy as |
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.
Thanks for fixing!
One small change, needed to work with the latest PAC.
I haven't checked yet if this is backwards compatible though, so the
>= 0.2.0
part of the dependency may not be correct anymore.