cortex-m
embedded-alloc
| cortex-m | embedded-alloc | |
|---|---|---|
| 6 | 3 | |
| 758 | 268 | |
| 2.6% | 3.0% | |
| 7.6 | 6.8 | |
| 4 days ago | 2 months 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.
cortex-m
-
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
I do not have as strong of feelings as your parent, but:
1. A lot of the APIs make use of the typestate pattern, which is nice, but also very verbose, and might turn many people off.
2. The generated API documentation for the lower level crates relies on you knowing the feel for how it generates the various APIs. It can take some time to get used to, especially if you're used to the better documentation of the broader ecosystem.
3. A bunch of the ecosystem crates assume the "I am running one program in ring0" kind of thing, and not "I have an RTOS" sort of case. See the discussion in https://github.com/rust-embedded/cortex-m/issues/233 for example.
- Advisory: Miscompilation in cortex-m-rt 0.7.1 and 0.7.2
-
Any frameworks in Rust for developing on SiFive / ST / NXP boards?
For cortex-m support, check out the cortex-m crate
-
Getting panic when running Rust-Embedded code to set GPIO mode
See https://github.com/rust-embedded/cortex-m/tree/master/panic-semihosting
-
A GPIO Driver in Rust
I don't think so. Once a function is compiled, it basically becomes a black box with a type signature so unless sleeping in a function affects its signature, that information is erased. If you pass in some kind of a sleep token that has to be used to sleep, then yeah I think you could enforce it by only being able to get that token in a non-atomic context and making it leak proof.
The Cortex-M crate does something similar, but for proving that you are in an atomic context. Another function that expects a CriticalSection type is then assured that it's running without interrupts enabled.
https://github.com/rust-embedded/cortex-m/blob/master/src/in...
- Would it be possible to run Rust on the new Raspberry Pi Pico?
embedded-alloc
-
Embedded Rust on BBC Micro Bit: unlocking Vec and HashMap
Luckily, the embedded-alloc crate provides us with one (there is a complete example in the associated Github repository). We also need the cortex-m crate to handle critical sections. Add them to the project's dependencies like so:
- Help with alloc_cortex_m build
- Alternative for Vec for variable size arrays in no_std environment?
What are some alternatives?
cortex-m-rt - Minimal startup / runtime for Cortex-M microcontrollers
cortex-m-quickstart - Template to develop bare metal applications for Cortex-M microcontrollers
stm32-rs - Embedded Rust device crates for STM32 microcontrollers
staticvec - Implements a fixed-capacity stack-allocated Vec alternative backed by an array, using const generics.
rtic - Real-Time Interrupt-driven Concurrency (RTIC) framework for ARM Cortex-M microcontrollers
rfcs - RFCs for changes to Rust
wyhash-rs - wyhash fast portable non-cryptographic hashing algorithm and random number generator in Rust
tock - A secure embedded operating system for microcontrollers
pico-examples
app-boilerplate-rust - Rust boilerplate application for Ledger Nano S/S+/X
stm32-hal - This library provides access to STM32 peripherals in Rust.
zero-copy-pads - Padding/aligning values without heap allocation