UART between MCUs
Two Unos on a crossed software serial link: ground control asks TEMP?, the probe answers with tenths of a degree, every reply checked before it is trusted, and what a baud mismatch looks like.
Open it in the simulatorDesigns that use more than one processor: why to split work, UART links between Unos, an addressed shared bus, SPI with a slave in software, a Raspberry Pi and an Uno together, framed protocols with CRCs and retries, and a rover with a display coprocessor.
0 of 7 done
7 lessons in 4 chapters, about 7 hours on a simulated Arduino Uno R3. Free, in your browser, every step checked by the simulator.
Two Unos on a crossed software serial link: ground control asks TEMP?, the probe answers with tenths of a degree, every reply checked before it is trusted, and what a baud mismatch looks like.
Open it in the simulatorA Raspberry Pi as the SPI master in Python with spidev, the Uno as the software slave, and a resistor divider so 5 V never reaches a 3.3 V pin. Linux for the thinking, a microcontroller for the timing.
Open it in the simulatorEach lesson opens when the one before it is done, and each chapter ends in a project.
What a second processor buys, and the simplest link.
One Uno crunching numbers between looks at a button counts 1 press of 5; a second Uno with nothing else to do counts all 5. What a second processor buys, and what it costs.
0 of 6 steps
Two Unos on a crossed software serial link: ground control asks TEMP?, the probe answers with tenths of a degree, every reply checked before it is trusted, and what a baud mismatch looks like.
0 of 6 steps
An addressed shared bus, SPI, and a Pi with a microcontroller.
One master, two nodes, one return wire: nodes answer through diodes onto a pulled-up line, each only when its address is called. The idea under I2C target mode, built where Mokxi can run it.
0 of 6 steps
SPI between two Unos: a bit-banged master at 10 kHz and a slave written in software on two interrupts, one byte each way per transfer, and the one-transfer lag every SPI slave has.
0 of 6 steps
A Raspberry Pi as the SPI master in Python with spidev, the Uno as the software slave, and a resistor divider so 5 V never reaches a 3.3 V pin. Linux for the thinking, a microcontroller for the timing.
0 of 7 steps
Frames, CRCs, acknowledgments and retries.
Packets instead of lines: a start byte, sequence number, type, length, payload and CRC-8. The receiver ACKs or NAKs, a damaged packet is caught and sent again, and the retry limit decides when to give up.
0 of 7 steps
A rover with a brain and a display coprocessor.
A rover split in two: the brain reads its range sensor, picks CRUISE, SLOW or STOP and drives the motor; a dashboard coprocessor draws its status on an LCD and sends a park command, all in framed, checked packets.
0 of 8 steps
All 7 lessons, in order, each with what it covers. Any of them opens in the editor right away.
Every lesson runs in the simulator with nothing to buy. When you want the real thing, these kits have the parts.
Pick the starter kit you own and run every lesson in its manual with the same parts on the same pins.
See every kitYes. All 7 lessons of Systems of boards are free and run in your browser, with nothing to install and no parts to buy before you start.
No. Every lesson runs on a simulated Arduino Uno R3 with its parts on the canvas, and the simulator checks each step as you go. When you want to build it for real, the same wiring and code work on a real board.
About 7 hours: 7 lessons in 4 chapters, each one a few short steps. Your progress is kept, so you can stop after any lesson and pick up where you left off.
Each chapter ends in a project that puts it together: UART between MCUs and Pi plus microcontroller.
With "Why split work", and each lesson builds on the one before it. New to circuits? Electronics basics is the course that starts from zero.