Roadmaps / Embedded Linux
Electronics · 16 study weeks · 4 phases
Embedded Linux Roadmap Beta
16 study weeks on one product image, built with Yocto and run in QEMU, so you need no board. You build a Linux image you can reproduce, configure its kernel and device tree, update it safely in the field, and plan fixes for a ten-year promise that outlasts your upstream's support dates. 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, fleet-gw, a gateway image for 5,000 remote sites, and every phase adds a checkpoint to it. At the end you can say, with numbers, why an update survives a power cut, which known vulnerabilities your image ships, and what you must do within hours when one is exploited.
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
Reproducible builds and your own layer
This phase gives you an image you can rebuild exactly, so every later change has a baseline. Read the Yocto Project overview and the BitBake user manual sections on tasks and the shared state cache (sstate) as you go.
- 3 repos
- Milestone checkpoint
- Study week 1Yocto concepts: layers, recipes, images, machines, the BitBake task graph, the sstate cache8 h
- Study week 2Your own layer: an image recipe, a recipe and systemd unit for gwd, devtool for changing a recipe8 h
- Study week 3Pinning and reproducibility: commit pins, source mirrors, what makes a build differ between runs (timestamps, build paths, wic UUIDs), buildhistory and diffoscope8 h
- Study week 4Read-only root (and a plan for /var and volatile paths), a data partition and the wic image layout8 h
Phase 2 · Study weeks 5-8
Kernel, device tree and a driver
This phase lets you describe hardware to the kernel and write a driver that binds to it, so you can read a vendor's patches without fear. Read the kernel documentation on device tree usage and the Bootlin kernel training slides as you go.
- 2 repos
- Milestone checkpoint
- Study week 5The kernel in Yocto: linux-yocto, config fragments, menuconfig and diffconfig, what to turn off and what that breaks8 h
- Study week 6Device tree: nodes, compatible, properties, dtc8 h
- Study week 7A platform driver (first 2 hours: build the Bootlin hello module): ofmatchtable, probe and remove, reading a property, an out-of-tree module recipe8 h
- Study week 8Boot with U-Boot: environment, boot script, kernel command line, boot time breakdown8 h
Phase 3 · Study weeks 9-12
Safe updates and boot
This phase makes fleet-gw survive a bad update and a power cut, and gives you the numbers to say so. Read the RAUC documentation on slots, bundles and the bootloader interface, and the U-Boot documentation on the environment.
- 5 repos
- Milestone checkpoint
- Study week 9Slot layout: A/B root, shared data partition, boot order, the U-Boot environment (redundant copies), size budgets8 h
- Study week 10RAUC: bundles, signing, verity format, rauc install8 h
- Study week 11Power-cut testing: the harness, trigger and random cuts, counting outcomes, the rule-of-three bound per stage8 h
- Study week 12Choosing an update tool on paper (RAUC, SWUpdate, Mender: model, signing, rollback, operating cost8 h
Phase 4 · Study weeks 13-16
Ship it: SBOM, vulnerabilities and the support promise
This phase turns an image into a product you can support for ten years and report on. Read the Yocto Project security manual on vulnerabilities, the sbom-cve-check documentation, and the European Commission's pages on the Cyber Resilience Act.
- 3 repos
- Milestone checkpoint
- Study week 13SBOMs: what SPDX 3 holds and does not8 h
- Study week 14CVEs in Yocto 6.0: sbom-cve-check (it replaced cve-check), statuses and reasons, kernel CVEs in bulk (the kernel reports very many8 h
- Study week 15The support promise: Cyber Resilience Act timeline, vulnerability reporting, support period, key and certificate lifecycle, staged rollout8 h
- Study week 16The drill: a seeded vulnerable library, rebuild, signed bundle, staged rollout to five instances, a halted rollout, an advisory8 h