EMBEDDED RUST IN THE AGE OF AI
Learn embedded Rust that works today.
Today’s crates. Checked Exercises. Sim or your own board.
Free account with the newsletter. No password. No card.
SOUND FAMILIAR?
Learning Struggles
Stale Tutorials That Don’t Compile
AI Hallucinating API
It Compiles, but Nothing Happens
Embassy, RTIC, std, no-std?
Too Many Crate Choices
Pasting Code You Don’t Understand
It’s not you.
Embedded Rust moves fast, most of what’s online doesn’t keep up, and AI learns from stale code at times. You don’t need more answers. You need ground that holds.
LEARNING IN THE AGE OF AI
AI writes code. You still have to know if it’s right.
On a laptop, wrong code typically crashes with a message. On a microcontroller, sometimes it compiles, flashes, and sits there. The AI can’t see your board. You can, if you know what you’re looking at.
01
Grounded in the hardware
Embedded Foundations starts at the chip: registers, clocks, pins, buses. The part AI glosses over is the part you’ll debug.
02
Checked, not trusted
Every exercise is checked by ter, a companion CLI. It builds your code, runs it, and tests what it does, not only that it compiles.
03
AI on your terms
Hints point back to the lesson. Want a model’s help? ter hint --llm gives your own model the lesson, your run, and your files, so its answer fits your code and this crate version.
ALWAYS CURRENT
Learn it once. We keep it current.
Embedded Rust crates can change frequently. Your course changes with it.
✓
Every course shows the crate version it teaches and when it was last updated.
✓
Whenever a course changes, we compile every lesson’s complete program against its pinned crates.
✓
New and Updated marks, plus a note in your bell, tell you what changed.
HOW IT WORKS
Read it. Write it. Prove it.
1
Read a short lesson
One idea at a time, with diagrams and the real code.
2
Write it in your editor
VS Code, Zed, Neovim, anything. Your machine, your toolchain.
3
Check it
ter run in your terminal, or Run on the lesson page with ter serve. Pass the checks, move on.
No board? Simulate it.
Every exercise runs in a simulator of your choice.
Got a µFerris board? Run it for real.
µFerris is the TER companion board. You can run your code on it or share it with a friend: ter serve --share, they ter connect.
THE PLATFORM
Everything around the lesson, built in.
A path to follow, checks you can trust, and tools that keep you moving.
Guided paths
Start at the chip. Always know the next step.
Completion certificates
One for every path you finish.
Growing catalog
New courses as the ecosystem moves.
Dated courses
Every course shows its crate version and when it was last updated.
Simulation enabled
No board? Every exercise runs in a simulator of your choice.
Course checking
ter builds, runs and tests what your code does.
Local build and compile
Your editor, your toolchain, your machine.
Skill Maps and mastery
See what you can do, what you’ve mastered and what’s next.
Goal setting
Set a pace and keep it.
Roadmap voting
Suggest and vote on the next courses and features.
BETA
Hardware sharing
Share your board with a friend: ter serve --share.
COMING SOON
Multi-MCU support
STM32, Raspberry Pi Pico & nRF, after ESP32.
COMING SOON
What’s next on the platform.
Already on the roadmap. Vote to move them up.
Interactive courses
Write and run code right on the lesson page.
Teams support
Seats and shared progress for teams learning together.
Multi-simulator support
Pick the simulator that fits each exercise.
FREE AND RUSTACEAN+
Start free. Go all in when you’re ready.
Free with the newsletter
Try selected lessons
Suggest features and vote on the roadmap
The twice-monthly newsletter
Rustacean+
Every course and path
Every exercise checked by ter
Certificates, Skill Map and goals
FAQ
Questions
Why not just ask an AI?
Ask it. Then you need to know whether its answer fits your chip, your crate version and your board. That’s what you learn here, and ter hint --llm lets your model help with the lesson in front of it.
Do I need a board?
No. Every exercise runs in a Wokwi simulation with your own free account. With an ESP32-C3, the same exercise runs on real hardware.
How much Rust do I need?
The basics: variables, functions, structs, enums, match, and a first pass at ownership and borrowing. If you've worked through the first half of The Rust Programming Language book, roughly chapters 1 to 10, you're ready. The embedded side of Rust, like why a pin moves into its driver or how async works on a microcontroller, is explained in the lessons where you first meet it.
Is this actually current?
Each course shows its crate version and when it was last updated. Whenever a course changes, every complete program is compiled against those crates.
Which editor and OS?
Any editor. Linux, macOS or Windows; the setup course walks through each.
I’m already a subscriber. Do I have an account?
Yes. Sign in with the email you subscribed with and we’ll send you a link.
Stop guessing which code is current.
Start with the chip. End up knowing what the code does.
