wg
cortex-m
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.
wg
-
Embedded Rust Education: 2023 Reflections & 2024 Visions
Inspired by James Munns's call, and as 2023 is coming to an end, I figure it's a good opportunity to reflect and look forward to 2024. It's been a bit over 1.5 years since I embarked on my embedded Rust journey and it's been nothing less than exciting since. So here it goes.
-
In search of Rust projects to contribute
Because you are an embedded guy. There is the https://github.com/rust-embedded/wg working-group. Rust on embedded is really on a got track forward. There are many chips/vendors that are supported both in no std / std rust world, but still there is a lot of niche things where you can actively help to be the first to get it run in Rust.
-
Rust – Are We Game Yet?
To specifically answer your question, here:
* <http://www.areweembeddedyet.com/>
It currently redirects to:
* <https://rust-embedded.org>
Which doesn't really contain anything other than a link to <https://github.com/rust-embedded>.
(via <https://github.com/rust-embedded/wg/issues/15>)
-
Google announce secure Rust-based OS for embedded system
Then the Rust Embedded workgroup provides: - Direction on how to using generics and zero-sized types to achieve functional safety - svd2rust, which provides safe abstractions to peripheral access from SVD files and achieves this functional safety - The embedded HAL spec, which makes porting to different vendors/hardware easy - Peripheral access controllers and HALs for various vendors & hardware
-
What are your guys' thoughts on Rust?
The Rust Embedded Devices Working Group curates a list of useful embedded Rust resources, including Peripheral Access Crates (autogenerated from SVD files), embedded-hal Implementation Crates (hand-written libraries implementing the traits (interfaces) specified by the embedded-hal), and Board Support Crates.
-
Question about Rust's binary size
You should also look at https://github.com/rust-embedded/wg/issues/41 and https://github.com/rust-lang/rust/pull/55011#issuecomment-429336055.
-
Things you can’t do in Rust (and what to do instead)
Here's an interesting discussion, consolidated here. My view is you should use a restricted scope atomic (as best as can be supported) and interact with that through a handler struct. I.e. no global state.
- Semantic Versioning Will Not Save You
- Is there a embedded community/website where it is modern?
-
Would it be possible to run Rust on the new Raspberry Pi Pico?
Most of the issues are explained in EWG RFC 419. The TL;DR is that some resources need to implement Send to be usable from interrupts, but they must not be sent across cores.
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?
What are some alternatives?
rust-semverver - Automatic checking for semantic versioning in library crates
cortex-m-rt - Minimal startup / runtime for Cortex-M microcontrollers
pico-examples
stm32-rs - Embedded Rust device crates for STM32 microcontrollers
flip-link - Adds zero-cost stack overflow protection to your embedded programs
rtic - Real-Time Interrupt-driven Concurrency (RTIC) framework for ARM Cortex-M microcontrollers
erdtree - A modern, cross-platform, multi-threaded, and general purpose filesystem and disk-usage utility that is aware of .gitignore and hidden file rules.
wyhash-rs - wyhash fast portable non-cryptographic hashing algorithm and random number generator in Rust
not-yet-awesome-embedded-rust - A collection of items that are not yet awesome in Embedded Rust
TX-2-simulator - Simulator for the pioneering TX-2 computer
stm32-hal - This library provides access to STM32 peripherals in Rust.