From Zero to A/B: Swimming Upstream with Yocto, Barebox and RAUC
summary
Claims mainline Linux is practical for many SoCs and demonstrates a concrete path: build a Yocto-based BSP for an i.MX8M, integrate barebox as bootloader, and enable RAUC for atomic redundant A/B updates using two full rootfs partitions. Implementation uses upstream ATF but keeps vendor DDR blobs, adds a barebox state device tree node, a RAUC bundle with generated keys, and a simple Yocto machine layer. Demo boots and updates reliably; caveats include small vendor blobs and a couple of recipe forks.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:10Downstream BSP Use
- 2:56How To Update?
- 4:05Knowledge Loss
- 5:13Technical Debt
- 7:17"Soft" Vendor Lock-In
- 9:39What if we had a clean slate?
- 13:17Summary: Swim Upstream!
- 14:47How can this look like?
- 16:20System Architecture
- 19:18Barebox State from Userspace
- 19:40What We Need
- 20:03Initial Yocto Setup
- 20:52Yocto Board Support Layer
- 21:09Machine Configuration
- 22:35Machine: Boot Firmware
- 23:50Machine: Barebox
- 25:31Machine: Device Tree
- 25:56Machine: Kernel
- 26:40Image with A/B partitioning
- 26:52Distro with RAUC support
- 27:54Distro: RAUC bundle
- 29:18RAUC: system.conf
related talks
33mUsing Open Source Software to Build an Industrial-grade Embedded Linux Platform...
49mEmbedded Linux BOF
40mConfiguring and Building a Heterogenous System Using the Yocto Project
39mBoF: The Yocto Project and OpenEmbedded
36mLessons Learned: Migrating a Production Platform to Yocto
29mBehind the Curtains of Making Real Consumer Devices using Debian
41mCase Study: Switching from Asymmetric to Symmetric Software Updates
36mEmbedded Development Made Easy: A Guide to FOSS Platforms and Maxing product value