rtic-examples
nrf-hal
| rtic-examples | nrf-hal | |
|---|---|---|
| 3 | 5 | |
| 130 | 473 | |
| 2.3% | 2.1% | |
| 7.1 | 8.4 | |
| 23 days ago | 22 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.
rtic-examples
- RTIC 在 Blue Pill 上的点灯案例
- Rust newcomers are 70x less likely to create vulnerabilities than C++ newcomers [pdf]
-
Embedded Systems Weekly #113
RTIC Real-Time Interrupt-driven Concurrency It is a Rust concurrency framework for building real-time systems on all Cortex-M devices. If you want to see how it works a repository with examples is public.
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?
noboilerplate - Code for my talks on the No Boilerplate channel
embassy - Modern embedded framework, using Rust and async.
ziglings - Learn the Zig programming language by fixing tiny broken programs.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
zephyr - Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
nrf-softdevice
drogue-device - A distribution of tools and examples for building embedded IoT applications in Rust
riscv-rust-quickstart - A template for building Rust applications for HiFive1 boards
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
microbit - A Rust crate for BBC micro:bit development
CC65-Advanced-Optimizations - How to optimize C code for CC65 compiler
rust-mos - Empowering everyone to build reliable and efficient software.