knaxuslearn · build · ship

Roadmaps / Embedded Linux / Setup and lab safety

Read first

Setup and lab safety

Kit. A laptop with 16 GB of RAM, 8 or more cores and 200 GB of free disk is the minimum; a second machine or a cloud build host is optional. QEMU runs the arm64 image: on an x86 host that is emulation and slow, so the plan measures ratios and trial counts, not absolute speed. No board, no cost. If you have a board, note the differences (kernel config, device tree and bootloader) and do not skip the QEMU runs, which are where the trials happen.

What QEMU cannot show. It has no real flash: no eMMC or NAND erase blocks, no torn or reordered writes, no wear, no boot ROM and no hardware watchdog. Killing the QEMU process keeps every write the guest already handed to the host, so a kill tests your update ordering and boot logic, not storage atomicity. Say this in ADR-3, and in ADR-7 (Senior) list the failure classes you did not exercise.

Links. Yocto docs: docs.yoctoproject.org. kas: kas.readthedocs.io. RAUC: rauc.readthedocs.io. Bootlin training: bootlin.com/training. CRA reporting: digital-strategy.ec.europa.eu/en/policies/cra-reporting.

Versions. Yocto Project 6.0 "Wrynose" (a long-term release, supported to April 2030), machine qemuarm64, U-Boot as the bootloader, systemd as init, RAUC for updates through the meta-rauc and meta-rauc-community layers. Pin every layer to a commit and record it. Everything runs from the command line.

Safety. Builds download source code: use a dedicated user and directory, and never run bitbake as root. Keep signing keys for exercises in a throwaway directory and never reuse a real key. Do not point the update lab at a device you cannot reflash. Test updates only on your own QEMU instances. Treat any CVE data feed as untrusted input.