EMB-120 · Embedded Linux & BSP · Practitioner

Buildroot in Practice — full syllabus

The lighter alternative to Yocto: when Buildroot is the right call and how to use it well.

Duration3 full days in person · 6 half-days online
Cohortmax 14 in person · 20 online
Pricefrom SAR 7,880 in person · local pricing per city
Delivery35% principles · 20% guided investigation · 45% engineering studio

Who this course is for

Engineers choosing or running Buildroot for smaller products — who need an honest picture of what it does well, and the discipline to keep a Buildroot-based product maintainable.

Prerequisites

Course outline

Day 1 — The Buildroot model

  • How Buildroot differs from Yocto: no binary packages, no sstate, one tree
  • Kconfig configuration and defconfigs
  • The build flow: toolchain, packages, rootfs, images
  • BR2_EXTERNAL trees for keeping your work out of the fork
  • Build artefacts: where per-package directories and output live

Day 2 — Packages and toolchains

  • The package infrastructures: generic, autotools, cmake, meson
  • Writing a package .mk and Config.in for your own software
  • Patching packages and keeping the patch stack reviewable
  • Toolchain choices: internal build, external toolchain, SDK generation
  • Legal-info output and what it gives you for free

Day 3 — Rootfs assembly and honest comparison

  • Filesystem overlays and permission/device tables
  • Post-build and post-image scripts: where product policy lives
  • Users, init system selection and skeleton customisation
  • Rebuild cost reality: full vs incremental and the make pitfalls
  • Buildroot vs Yocto for real projects: team size, update strategy, compliance and lifecycle

Hands-on labs

  1. Lab: Build a defconfig for a QEMU target and boot the result; then rebuild it for the lab board's architecture
  2. Lab: Add a new package with generic-package, patch it, and prove the patch applied in the per-package build directory
  3. Lab: Assemble a product rootfs with an overlay, a permission table and a post-build script; verify the result on the target
  4. Lab: Generate an SDK and build a userspace application against it outside the Buildroot tree
  5. Lab: Time a clean build vs an incremental change, then measure the same change in an equivalent Yocto build and write up the comparison

Capstone project

Produce equivalent minimal images for the same target in Buildroot and (with provided scaffolding) Yocto: same packages, same init behaviour, same custom application — then deliver both images, the provenance and legal-info output for each, measured rebuild timings and a one-page decision record stating which system you would ship and why.

What you leave with

Upcoming dates

DatesWhereSeatsEarly birdRegular
11 Oct – 13 Oct 20263 full days RiyadhIn person · KAFD Conference Centre 3 of 14 —SAR 7,880
18 Oct – 20 Oct 20263 full days Kuwait CityIn person · Al Hamra Tower 8 of 14 —KWD 650
18 Oct – 20 Oct 20263 full days MuscatIn person · Knowledge Oasis Muscat 3 of 14 —OMR 810
25 Oct – 1 Nov 20266 half-days Gulf bandLive online · 09:00–13:00 GMT+3 15 of 20 —US$1,500
26 Oct – 28 Oct 20263 full days OttawaIn person · Kanata North Tech Park 8 of 14 —CAD 2,860
2 Nov – 4 Nov 20263 full days TorontoIn person · MaRS Discovery District 3 of 14 —CAD 2,860
2 Nov – 4 Nov 20263 full days LondonIn person · Shoreditch Works 8 of 14 —GBP 1,640
2 Nov – 9 Nov 20266 half-days Europe bandLive online · 09:00–13:00 CET 4 of 20 —US$1,500
2 Nov – 9 Nov 20266 half-days Americas bandLive online · 13:00–17:00 ET 9 of 20 —US$1,500
9 Nov – 11 Nov 20263 full days BerlinIn person · Factory Görlitzer Park 3 of 14 EUR 1,740until 10 OctEUR 1,930

Book a seat, or bring this course to your team

Seats can be reserved online; private delivery runs on-site or live online, adapted to your stack.

Course page & booking

Questions about fit or prerequisites? Email hello@kernelsystems.academy. To save this syllabus, print this page to PDF from your browser.