-
Notifications
You must be signed in to change notification settings - Fork 141
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
Adding support for Nordic nRF52833 #148
Conversation
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.
Great! We're approaching #[cfg]
-hell though, maybe we should rethink how we handle different chips...
Is there a good pattern for solving |
I could imagine using a build.rs script to set various |
When you're talking about cfg-hell you mean from a developer perspective, right? Because from a user perspective I like it quite much :) |
With regards to cfg-hell. I experimented a bit with adding a build.rs that generated features from the features defined in Cargo.toml. I am on the fence on if the result is better or not. Maybe open a issue for cfg opportunity for improvement?
build.rs
|
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.
PR looks good to me, thanks!
This PR adds support for the Nordic nRF52833. This chip is similar to the nRF52840 with less flash and memory, no CryptoCell, some radio differences and probably som other smaller differences.
I have tested using clocks, gpio, timer and uarte in a RTFM program running on a Nordic nRF52833-DK.