Update on Rust in Zephyr
summary
An RFC for Rust-on-Zephyr exists and the implementation shows concrete pieces: a keyboard firmware of about 5900 lines of Rust with ~2600 lines of Zephyr-support glue and ~500 lines of C, plus ~1300 lines of application logic, demonstrating it runs. Cargo is integrated into West/CMake so builds invoke cargo/cmake integration during West build. Kconfig values become Rust cfgs and consts, device tree becomes device-tree as Rust modules, system-call (C) wrappers and logging remain prototype but functional.
AI-written summary · about
chapters (7)
- 0:00Rust in Zephyr intro
- 4:36Rust progress and goals
- 15:32Kconfig for Rust apps
- 22:22Device tree in Rust
- 30:34Kernel objects in Rust
- 33:07Logging challenges
- 36:25Q&A: Rust in userspace
related talks
42mUpdate on Rust in Zephyr
41mWhy Rust and Zephyr Are a Good Fit
41mRust Meets Zephyr: Building Safer Embedded Applications
45mCrabs Flying Kites: Writing a Zephyr Application in Rust- 45mCrabs Flying Kites: Writing a Zephyr Application in Rust
36mUsing Zephyr with Non-C Languages- 41mRust Meets Zephyr: Building Safer Embedded Applications
26mIntroducing Rust into a Legacy Embedded System