Embedded devices Working Group
Coordination repository of the embedded devices Working Group (WG)
This repository issue tracker is used by the embedded WG to coordinate efforts towards making Rust
a great choice for embedded development.
Want to get started with embedded development with Rust? Check out our
embedded Rust book and the rest of our bookshelf.
Want to stay up-to-date with community progress? Check out our newsletter.
Join the discussion on Matrix! #rust-embedded:matrix.org
Vision
What is it that we really want? At a broad level:
- To improve the absolute quality (functionality, safety, performance) of embedded software in the
wild.
- To improve the productivity of embedded software development teams, by reducing the tangible and
intangible costs of achieving a level of quality.
- To improve the experience for programmers developing for embedded systems.
- To make embedded systems programming more accessible for people that are not already embedded
systems developers.
What we do
At a high level we have two main tasks:
We work with the community to improve the embedded ecosystem.
-
We maintain and develop core crates in the embedded ecosystem ensuring that the development
roadmap aligns with the needs of its users. You can find all the crates we maintain in the
Organization section.
-
We develop and curate resources about embedded Rust development. Check our
bookshelf!
-
We maintain and moderate the venues the embedded community uses to discuss. That includes this
coordination repository and our Matrix room.
And, we serve as a bridge between the Rust teams and the embedded community.
How you can help
Everyone can contribute to the embedded WG efforts! There are several ways to help out:
- Let us know where the gaps are. If you think the language, the compiler, the tooling, the
documentation or the crate ecosystem is lacking some feature, information or library to build
embedded software let us know and we'll bring it up to the Rust teams or organize the community to
build the crates or tools to fill the gaps.
- Participate in RFC (Request For Comments) threads. We are always looking into ways to
improve. This may involve things from changing how we run the WG to landing major breaking changes
in core crates. To ensure we are actually making things better we need your input! That's why
all these changes are preceded by an "RFC", a discussion thread (which may or may not be backed by
a proper RFC document) where we evaluate the pros and cons of a proposal and explore alternatives.
Only after there's consensus on accepting the proposal is the proposal made effective.
- Help wanted!. There's always lots to do but the WG members only have so much free time. You can
help us fixing bugs, implementing features, writing tests, trying out examples and tutorials,
writing documentation, fixing typos, etc. We'll mentor you through these tasks and review your
work. In some cases you may not even need previous embedded experience or access embedded hardware
to help us out so don't let that discourage you from checking out our help wanted issues.
-
Join our weekly meetings on Matrix. We use these meetings as a faster, synchronous alternative to the
RFC threads on GitHub. The agenda is posted in the matrix channel in advance
to the meeting. Everyone is free to join the meeting and share their thoughts. You can also
nominate an existing GH thread for discussion if you think it would benefit from a more
synchronous discussion.
The usual meeting time is Tuesdays, 8pm CET/CEST.
-
We have several teams focused on different areas: tooling, Cortex-M crates, etc. and each team
maintains several projects (crates, docs and / or tools) that live under the rust-embedded
organization. You can collaborate with the maintenance and development of these projects by
becoming a project collaborator (consult with the team that owns the project) or by joining the
team.
Organization
The WG is composed of several teams whose functions are defined in RFC
#136. The embedded WG develops and maintains a large set
of projects under the rust-embedded organization. This section lists all the
teams and all the projects owned by the WG.
The core team
The functions of the core team are:
- Representing the WG in meetings with other Rust teams.
- Communicating the needs of the embedded Rust community (e.g. language features,
core API
stabilization) to the Rust teams.
- Giving the casting vote on intra-WG decisions where no voting majority can be achieved.
- Driving and moderating the weekly meetings.
Members
The Arm team
The Arm team develops and maintains the crates related to Arm microprocessors
and microcontrollers, including Cortex-A, Cortex-R, and Cortex-M.
Members
- @adamgreig
- @bartmassey
- @berkus
- @jonathanpallant
- @nchong-at-aws
- @newAM
- @raw-bin
- @robamu
- @thalesfragoso
- @therealprof
- @ithinuel
- @davidtwco (representing
@rust-lang/arm-maintainers)
Projects
Projects maintained by this team.
aarch64-cpuarm-dccaarch32-cpu (was cortex-ar)aarch32-rtcortex-m-rtcortex-m-semihostingcortex-mitmpanic-dccpanic-itmpanic-semihostingrust-raspberrypi-OS-tutorials
The embedded Linux team
The embedded Linux team develops and maintains the core of the embedded Linux crate ecosystem.
Members
- @eldruin
- @nastevens
- @ryankurte
- @sirhcel
- @jannic
Projects
Projects maintained by the embedded Linux team
gpio-cdevgpio-utilsi2cdevlinux-embedded-halmeta-rust-binspidevsysfs-gpiosysfs-pwm
The HAL team
The HAL team develops and maintains crates containing shared traits and related
code that enables the development of hardware abstraction layers and drivers
which can interoperate across all embedded Rust devices on all architectures.
Members
- @therealprof
- @ryankurte
- @eldruin
- @dirbaio
- @MabezDev
- @ithinuel
Projects
Projects maintained by the HAL team.
embedded-dmaembedded-halnbcritical-section
The infrastructure team
The infrastructure team manages our domains, DNS records, e-mail aliases, etc.
Members
Projects
Projects maintained by this team
rust-embedded-provisioning
The libs team
The libs team manages library code that is not architecture-specific.
Members
- @dirbaio
- @newAM
- @reitermarkus
- @zeenix
- @sgued
Projects
Projects maintained by this team
embedded-allocheaplessqemu-exitvolatile-register
The MSP430 team
The MS430 team develops and maintains the core of the MSP430 crate ecosystem.
Members
Projects
Projects maintained by this team
msp430-quickstartmsp430-rtmsp430
The RISC-V team
The RISC-V team develops and maintains the core of the RISC-V crate ecosystem.
Members
- @almindor
- @dkhayes117
- @romancardenas
- @MabezDev
- @jessebraham
- @rmsyn
Projects
Projects maintained by this team
riscv-rust-quickstartriscv-pacriscv-rtriscv-semihostingriscv
The resources team
The resources team develops, maintains and curates documentation, books, our
social media accounts and websites, and similar resources on embedded Rust.
Members
- @adamgreig
- @bartmassey
- @eldruin
- @hdoordt
- @jamesmunns
- @therealprof
Projects
Projects maintained by the resources team
- Awesome embedded Rust
- The Discovery book
- The embedded Rust book
- The embedonomicon
- @rustembedded twitter
The tools team
The tools team maintains and develops software for embedded development
which typically runs on your development machine rather than the
embedded targets themselves.
Members
- @adamgreig
- @burrbull
- @Emilgardis
- @ryankurte
- @therealprof
- @ithinuel
Projects
Projects maintained by the tools team
cargo-binutilsitmsvd-parsersvd2rust
The triage team
The triage team is charge of keeping PR queues moving; they ensure no PR is left unattended.
Members
- @mathk
- @jessebraham
- @jannic
Hibernating and Alumni
The following alumni have put themselves into the hibernation state, due to being absent or busy for an extended amount of time. See ops/hibernating.md.
- @andre-richter
- @awygle
- @bradjc
- @danc86
- @Disasm
- @dvc94ch
- @dylanmckay
- @hannobraun
- @hargoniX
- @japaric
- @jcsoo
- @korken89
- @laanwj
- @paoloteti
- @parched
- @pftbest
- @sekineh
- @v-thakkar
- @wizofe
- @posborne
- @thejpster
- @YuhanLiin
Contact
Each team can be privately contacted via the following e-mail addresses:
You can usually find the members of the embedded WG on the Rust Embedded Matrix room
(#rust-embedded:matrix.org).
Our Matrix room is logged by on the bridged IRC channel, and you can find the logs at: https://libera.irclog.whitequark.org/rust-embedded/
Other projects
These are other projects you may be interested in but that (currently) are not owned by the WG.
- AVR fork of Rust
- Xtensa fork of Rust (for Espressif chips)
Ongoing community efforts
Device specific communities
Several device specific communities exist that are not part of the working group.
These communities maintain crates for peripheral access, hardware abstraction,
examples, and more that are specific to a particular family of devices.
The list below is not exhaustive and will be updated as device support increases.
- nrf-rs: Nordic nRF series of microcontrollers
- stm32-rs: STM32 microcontrollers
- lpc-rs: NXP LPC microcontrollers
- imxrt-rs: NXP i.MX RT microcontrollers
- esp-rs: Espressif Systems microcontrollers
- rp-rs: Raspberry Pi microcontrollers including the RP2040
embedded-hal
embedded-hal is a project that aims to build a standard set of traits (interfaces) for I/O
functionality common in embedded devices: Serial, I2C, etc. with the goal of serving as a base for
building reusable driver crates, crates to interface with external components like sensors.
There are plenty of traits that still need to be designed, in particular ones that involve async
I/O. Join the discussion and help us design the missing traits so that they'll fulfill your needs.
Awesome embedded Rust
The community is building a curated list of crates useful for embedded development. In this list
you'll find driver crates, board support crates and general purpose no-std crates. Help us improve
this list by adding your crate via PR or by tackling any of our help wanted issues.
Embedded category in the user forum
As an experiment the Rust lang user forum has gained a new embedded category.
This is meant as a friendly exchange for anyone interested in embedded topics with Rust.
So if you want to discuss ideas, problems or solutions please feel free to chime in on existing topics or create a new one!
RFCs
When the team deems it necessary the RFC process may be used to make decisions or to design
processes, user interfaces, APIs, etc.
Learn more about the Rust's RFC process (which is the same as our own) here.
To create an RFC, simply:
- clone this repo to your own personal one
- copy
0000-template.md to text/0000-my-feature.md (where "my-feature" is
descriptive. Don't assign an RFC number yet)
- fill in the details of your RFC in that file
- Open an pull request with this repository
/wg