-
Notifications
You must be signed in to change notification settings - Fork 94
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
Request for Feedback: embedded-platform #412
Comments
I like the idea. It is to a BSP, what embedded-hal is to an SPI peripheral driver. |
@thejpster okay, I will continue working on it for a while longer then and see where it ends up! (possibly adding support for more boards etc) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently started down a rabbit hole of creating my own abstraction over
embedded-hal
that makes it easy to mix and match various dev boards. My initial use-case has been to do experiments with Adafruit Feather boards, where I want to plug two devices together and expect the code to "just work" without having to figure out the specific pin/peripheral mappings between them. On the other hand, I didn't want to go all in and rewrite all crates in existence; instead, I wanted to rely on existing-hal
and driver crates as much as possible.As a result, I created https://github.com/dflemstr/embedded-platform (see docs at https://docs.rs/embedded-platform, in particular the example Feather spec). I realize that the scope of that library is huge and hence I would like to get feedback on the approach. I'm happy to share control of the repository in case others think this is a good idea, or yank the crate if not :)
Since I'm not super familiar with this WG, I don't know which exact process to follow here. Please give me input on what to do!
A teaser example:
Quoting the README:
The text was updated successfully, but these errors were encountered: