knaxuslearn · build · ship

Roadmaps / Embedded Linux / Who this is for

Read first

Who this is for

Hours by path (core only; the work version is extra; Checkpoint W also needs a 90-day wait that costs no hours).

You areStart atSkipYour assignmentsYour milestone scopeAim for
Fresher who knows Linux (see the prerequisites; otherwise take Linux Engineer first)Week 0, then Week 1Checkpoint W, the Staff and Principal variants, and the "Staff adds" and "Principal probe" lines in Interview topicsPractice projects 1 and 2 in each phase, checkpoints 1 to 4Core scope: faults 1 to 6, reproducible image, one driver bound to a device tree node, 100 power-cut trials, one CVE drill, ADRs 1 to 52 Sound on every dimension
Senior (5 to 8 years, owns services or firmware)Week 2 (skim Week 1)Week 5 if you already maintain kernel configsAll practice projects, checkpoints 1 to 4Adds a second update tool compared by measurement, a storage-level power-cut method (fault 3b), ADRs 6 and 7, and a fleet key-rotation plan (ADR-6; the Phase 3 practice project does the single-device rotation)3 Proven on every dimension
Staff (10+ years, sets direction across teams)The fast lane (12 hours, below), then Phase 3 and 4Phases 1 and 2 weekly tables (the fast lane's gap test tells you which to read)Checkpoints 3 and 4, Checkpoint W and the platform-policy memoAdds a platform-policy memo with numbers (8 hours, below)3 on all; 4 only through the work version
Principal (15+ years, sets strategy)The milestone section, the fast lane (on a product that already has an A/B update), Phase 4, then Interview topicsThe weekly tables of Phases 1 to 3Checkpoint W on a real product (it replaces the lab run of Checkpoint 4: read Phase 4 and run its drill on that product), plus a compliance review checklist others reuseAdds the checklist (6 hours) and a build-or-buy memo (8 hours), below3 on all; 4 only through the work version
PathPartsHoursWeeks at your pace
FresherWeek 0 (optional, 8), Weeks 1 to 1612816 at 8 hours; 26 at 5; 32 at 4
SeniorSkim Week 1 (4), Weeks 2 to 16 (120), second update tool and storage-level cut (10)13423 at 6 hours; 27 at 5
StaffFast lane (12), Phases 3 and 4 (64), platform-policy memo (8)84 (+16 with no A/B image), plus 24 for Checkpoint W (108)21 at 4 hours (27 with W); 28 at 3 (36 with W)
PrincipalFast lane (12), Phase 4 (32), checklist (6), build-or-buy memo (8)58 (+16 with no A/B image), plus 24 for Checkpoint W (82)20 at 3 hours; 28 with Checkpoint W

The fast lane (12 hours, after your image has built; build time is not counted) is for Staff and Principal readers who ship Linux products but have not measured an update path. Use your own product image if it has an A/B update and a bootloader you can script. If you have none, do Weeks 1 and 2 first with the starter pack in the milestone section (16 hours more; Staff already covers Weeks 9 and 10 in Phase 3); a Principal with no A/B product to test on should take the Staff path. Then do the gap test: for each row of the fault table below, write down what you expect to happen and the evidence you would collect, run it, and mark where you were wrong. Read the Phase 1 and 2 weeks that cover your wrong answers. Hand-in: the gap table (expectation, evidence, result, what you got wrong) and a half-page on which failure classes your product's test method cannot show.

Prerequisites for a fresher. If one is missing, take Linux Engineer first, or do Week 0.

  • You can use a Linux shell, edit files, and read a systemd unit file.
  • You can read and write C at the level of structs, pointers and a Makefile.
  • You can use Git (commit, branch, diff, a submodule or a pinned commit).
  • You know what a partition, a filesystem and a bootloader are.
  • You know these terms or will meet them in Weeks 1 to 4: ADR (architecture decision record: one page with the decision, a rejected option, its cost and the check), sstate (Yocto's cache of build outputs), wic (Yocto's disk-image tool). "Sound" and the other levels are defined under Scoring.
  • You have a Linux build host: native Linux, a Linux VM, or WSL2 on Windows. Yocto does not build natively on macOS, so use a Linux VM there (on Apple silicon the VM runs arm64 natively but QEMU for the x86 tools may be slow). Build inside the VM's own disk, with 200 GB free (two builds with separate caches need 120 to 200 GB; delete the first build's work directory once its manifest is saved) and 16 GB of RAM (check the Yocto Project's build-host requirements page).

This roadmap builds a Linux product from sources with Yocto and updates it in QEMU. For a real board, use BeagleBone Engineer (Buildroot, PRU, hardware) or Embedded Systems Engineer (the wider field). For general Linux operation, use Linux Engineer.