knaxuslearn · build · ship

Roadmaps / BeagleBone / Phase 4

Phase 4 of 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.

Topics every week

  1. Week 138 h
    • Reproducible image with Buildroot (beaglebone_defconfig, pinned release)
    • overlay and PRU firmware in the image
    • an RT kernel in the image (the Beagle am33x-rt-v6.12 tree, or mainline 7.1 or later with PREEMPT_RT)
    • boot time and size

    Hand inA clean-checkout build that boots your supervisor, passes the RPMsg echo from Phase 3 (or pins the Beagle kernel if the Buildroot kernel does not), with boot time and image size

  2. Week 148 h
    • Where U-Boot and the slots live (ADR-5)
    • A/B updates with RAUC: slots, U-Boot integration, signed verity bundles, health checks and rollback

    Hand inAn update that replaces rootfs and PRU firmware and rolls back on a seeded failure

  3. Week 158 h
    • Read-only root, watchdog, logging and field diagnostics
    • a threat model for a device with no secure boot
    • Staff and above add supply and end-of-life planning and the PocketBeagle 2 comparison

    Hand inA one-page threat model (Staff and above: and a cost and supply memo)

  4. Week 168 h
    • Integration test, 24-hour soak, power-cut drills, final report and readout

    Hand inCheckpoint 4, with your predicted and measured soak result

Practice projects

  1. Reproducible build. Build the image twice, on two machines or in a fresh container on one. Done when both root filesystems have identical file lists and checksums (list any timestamp differences) and the build log lists every pinned version.
  2. Power-cut drill. Cut power through the relay 20 times: at scripted points (during download, install, the bootloader variable write and the first boot of the new slot) and at random points. Done when the board always boots a valid slot and the script records which slot each time.
  3. Field diagnostics. Add a command that collects logs, the slot state and PRU state into one file. Done when a colleague finds a seeded fault using only that file.

Optional: build the same image with Yocto (the comparison for ADR-4) using the bootlin yocto-kiss setup and compare build time, size and effort. Optional: measure the update time of the verity bundle against a plain full-image copy.

GitHub repos to study

RepoWhat to readWeek
buildroot/buildroot (Nov 2026)configs/beaglebone_defconfig and board/beagleboard/beaglebone: which kernel and bootloader it pins13
bootlin/yocto-kiss (Oct 2026)A minimal Yocto setup with a BeagleBone Black machine (dogbonedark)13
rauc/rauc (Nov 2026)docs/ on the verity bundle format, slots and bootloader integration14

Milestone checkpoint

Ship the step engine (Checkpoint 4). Build the image from a clean checkout, add A/B updates, a health check and a watchdog, then soak it for 24 hours with a looped job file. Done when the Checkpoint 4 row passes. Evidence: the build log, the update and power-cut logs, the soak report, the threat model, ADR-4 (build system and update tool) and ADR-5 (where U-Boot and the slots live), plus, for Senior and above, ADR-6 (security posture) and ADR-7 (exit plan from the AM335x), and a ten-minute readout. For ADR-5 note that the ROM tries the eMMC before the microSD unless the boot button is held, so an unattended drill cannot rely on the button: put U-Boot on the eMMC and the slots on eMMC or microSD, and back up the eMMC image first.

Pin a Buildroot release in ADR-4: the long-term 2025.02.x series (supported to March 2028), or 2026.11.x once released and after you check its beaglebone_defconfig kernel. The 2026.08.x stable series ends in December 2026. Use the verity bundle format. RAUC 1.15.2 (27 Mar 2026) fixed CVE-2026-34155, an issue with the older plain format on payloads over 2 GiB. Your kernel needs loop devices, SquashFS and dm-verity.

Check yourself

Answer each question in your head first, then open it to check.

  1. Why does an A/B scheme still need a health check and a rollback rule?
    A slot can boot and still be broken. The health check decides when the new slot is good, and the rule says what happens if it never is.
  2. What can you do about security on a board whose chip has no secure boot?
    Sign updates, keep the attack surface small, lock down services and accounts, and say plainly in the threat model what the chip cannot prove.
  3. What does a read-only root filesystem protect against, and where does state go?
    It protects against wear and corrupted writes during power loss. State goes to a separate writable partition with its own recovery rules.
  4. When would you choose Yocto over Buildroot, and the reverse?
    Choose Yocto for many products, layers from several vendors and long-term support (Yocto 6.0 "Wrynose" is an LTS release supported until at least April 2030). Choose Buildroot for one small product, fast builds and simple configuration.
  5. What do you write in an end-of-life plan for a product built on one chip?
    The chip's published status, last-time-buy triggers, a tested port target (for example PocketBeagle 2, which has PRUs but a different firmware and memory map), the software that does not move, and the owner of the decision.