nrf-hal
discovery
Our great sponsors
| nrf-hal | discovery | |
|---|---|---|
| 5 | 5 | |
| 469 | 1,400 | |
| 3.8% | 2.0% | |
| 6.8 | 5.7 | |
| 10 days ago | 10 days 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.
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.)
discovery
-
I'm following the Embedded Discovery book with a micro:bit V2. The code compiles and is flashed fine on the MCU but rust-analyzer in VS Code doesn't recognize the crates I'm using which is quite annoying (no intellisense). How to fix this please? Thank you
You're right that was it, I also found a similar answer here
-
First steps with Embedded Rust: Selecting a board
> currently being rewritten Some things are still missing
-
Embedded Rust: Is memory.x really required?
Discovery Source-code: https://github.com/rust-embedded/discovery
-
New Rust Learner Requesting Help Using The
The library internally refers to something called "f3", which is not found in Cargo.toml: https://github.com/rust-embedded/discovery/blob/master/src/08-leds-again/auxiliary/src/lib.rs (It seems it's pulling it from the internal dependencies of its dependencies)
What are some alternatives?
embassy - Modern embedded framework, using Rust and async.
microbit - A Rust crate for BBC micro:bit development
ziglings - Learn the Zig programming language by fixing tiny broken programs.
nrf-softdevice
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
atsamd - Target atsamd microcontrollers using Rust
zephyr - Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
avr-hal - embedded-hal abstractions for AVR microcontrollers
riscv-rust-quickstart - A template for building Rust applications for HiFive1 boards
drogue-device - A distribution of tools and examples for building embedded IoT applications in Rust