Roadmaps / BeagleBone
Electronics · 16 study weeks · 4 phases
BeagleBone Roadmap Beta
16 study weeks on one board. You start with a BeagleBone Black at power-on and finish with an image that updates itself and survives a power cut. On the way you boot Linux, describe your hardware to the kernel, and move a timing-critical job onto the board's two PRU (programmable real-time unit) cores. At 8 hours a week the core path is 128 hours and takes 16 weeks. At 12 hours a week it takes about 11 weeks, and at 16 hours a week about 8 weeks. You build one product across all four phases, a single-axis step engine, and every phase adds a checkpoint to it. At the end you can say, with measurements, when Linux is enough, when a real-time kernel is enough, and when the job belongs on a PRU or a microcontroller.
This roadmap is in beta and keeps improving over time. If you spot an error, please email your suggestions and corrections to [email protected].
Read first
Phase 1 · Study weeks 1-4
Board, boot chain and a measured baseline
This phase lets you boot, debug and recover the board, and it tells you how badly plain Linux handles timing, so Phase 3 has a number to beat. Start here: Bootlin's Embedded Linux labs for the BeagleBone Black (bootlin.com/doc/training).
- 4 repos
- Milestone checkpoint
- Study week 1AM335x block diagram8 h
- Study week 2Boot chain: ROM, SPL (MLO), U-Boot, kernel and device tree, init8 h
- Study week 3GPIO from user space with libgpiod v2 (v1 tools differ)8 h
- Study week 4Latency measurement: cyclictest, stress-ng, histograms8 h
Phase 2 · Study weeks 5-8
Device tree, drivers and buses
This phase lets you describe real hardware to the kernel instead of poking registers from user space, so your step engine gets safe, supervised I/O. Start here: docs.kernel.org (device tree usage) and Bootlin's kernel and driver labs.
- 2 repos
- Milestone checkpoint
- Study week 5Device tree syntax and the dtc compiler8 h
- Study week 6I2C and SPI8 h
- Study week 7Out-of-tree kernel module8 h
- Study week 8Limit-switch design: debouncing, interrupt against polling, enable and direction lines8 h
Phase 3 · Study weeks 9-12
PRU real-time control
This phase gives the step engine its deterministic core (start here: the PRU Cookbook, docs.beagleboard.io books/pru-cookbook): the board's two PRUs run your timing loop with a 5 ns instruction cycle, independent of Linux.
- 2 repos
- Milestone checkpoint
- Study week 9PRU-ICSS: two 32-bit cores at 200 MHz, 8 KB program RAM and 8 KB data RAM per core, 12 KB shared RAM, registers R30 and R318 h
- Study week 10Linux-to-PRU communication: resource table, RPMsg, shared memory8 h
- Study week 11Exact timing: cycle counting, delaycycles, the PRU cycle counter, a step pulse with fixed-point ramps8 h
- Study week 12PRU1 as the observer: capture the step pin by loopback, timestamp edges, watch the limit switch and a heartbeat8 h
Phase 4 · Study weeks 13-16
Ship it: image, updates and operations
This phase turns a lab setup into a product (start here: the Buildroot manual at buildroot.org/docs.html and the RAUC documentation at rauc.readthedocs.io; modify a known-good setup, do not write one from scratch): a reproducible image, updates that survive a power cut, and the operating practices to run it.
- 3 repos
- Milestone checkpoint
- Study week 13Reproducible image with Buildroot (beaglebonedefconfig, pinned release)8 h
- Study week 14Where U-Boot and the slots live (ADR-5)8 h
- Study week 15Read-only root, watchdog, logging and field diagnostics8 h
- Study week 16Integration test, 24-hour soak, power-cut drills, final report and readout8 h