drogue-device
nrf-hal
| drogue-device | nrf-hal | |
|---|---|---|
| 2 | 5 | |
| 188 | 530 | |
| 0.0% | 2.3% | |
| 3.0 | 8.0 | |
| over 1 year ago | about 1 month ago | |
| Rust | Rust | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
drogue-device
- I rewrote my Rust keyboard firmware in Zig: consistency, mastery, and fun
-
Async actor framework for embedded Rust
https://github.com/drogue-iot/drogue-device/blob/972e1806c25752d66f60b2a6755124ee8148f522/src/actor.rs#L411
nrf-hal
-
Rust newcomers are 70x less likely to create vulnerabilities than C++ newcomers [pdf]
You should try again. I think that code is verbose because of the borrowing and because you're trying to do a one-liner. I use the nrf-hal library with the nrf52840, and the code reads pretty nicely. Here's an example:
https://github.com/nrf-rs/nrf-hal/blob/master/examples/blink...
-
Any good examples of using embedded Rust with an existing embedded C codebase?
Reading nrf-hal source, unfortunately new does re-configure the UARTE, and there is not a new_unchecked. The solution I can think of is to duplicate the write code with nrf52833_hal::pac::UARTE0. The Uarte type does not contain any metadata, it exists purely to guard the init of UARTE.
- Rust on the MOS 6502: Beyond Fibonacci
-
First steps with Embedded Rust: Selecting a board
Really good. Check out the examples in the nrf-hal repo. Also, if you don't mind forking out for some extra components the Knurling sessions by Ferrous Systems are ace.
-
I rewrote my Rust keyboard firmware in Zig: consistency, mastery, and fun
The embedded HAL crates do this with extensive use of macros, for example: https://github.com/nrf-rs/nrf-hal/blob/aae17943efc24baffe30b...
This solution makes sense given the constraints of Rust, but there's quite a cost in terms of compiler time and cognitive overhead to understand what is going on.
(Aside: I didn't use the HAL in my Rust firmware, that's a higher layer of abstraction; I only used the PAC crates.)
What are some alternatives?
quad - Firmware, hardware and documentation for my autonomous quad copter project
embassy - Modern embedded framework, using Rust and async.
rusty-password - Get the password of the Wi-Fi network you're connected to
ziglings - Learn the Zig programming language by fixing tiny broken programs.
chirpstack - ChirpStack open-source LoRaWAN Network Server
microbit - A Rust crate for BBC micro:bit development