A modular Yocto stack for multi-hardware
First target: TI AM335x-class hardware
The Yocto multi-SoC platform — old and new SoCs alike, kept on the latest Yocto release, layer by layer, and what runs on real hardware today.
JustEmbed's multi-SoC BSP project is built on a shared layer foundation across every target, with a separate vendor BSP layer per SoC. The goal is a board you can build with a single switch wherever that's technically possible — not a one-off Yocto setup per board. That includes older SoCs: instead of staying frozen on whatever Yocto release they launched with, they move forward on the same shared layer set as new boards, on the current Yocto version.
Each new SoC goes through the same test flow before it counts as brought up: serial console, then network boot for fast iteration, and finally boot from the board's own storage. Writes to physical storage stay a manual, confirmed step — never automated.
Why it matters
A board frozen on its launch-day BSP is a board nobody wants to own.
Vendor support for embedded SoCs and carrier boards often ends years before the product built on them does. Once it does, security fixes stop — and every new advisory widens the gap between what's deployed and what's actually safe.
We bring boards that have lost official vendor support onto the same current, actively-maintained Yocto layer set every other target we support runs on — pairing old silicon with a current kernel, u-boot and Yocto release, so it keeps getting security fixes without a hardware redesign.
That discipline is read directly from the engineering repository per platform rather than hand-maintained — from the silicon up to the application runtimes, and the security built into it.
That discipline has a second payoff. A build that is reproducible and verified per release is one where the software bill of materials and CVE record stay accurate as we go, generated alongside the platform rather than reconstructed after the fact.
Software stack
The same shared layer set, built once and reused across every target we support — not a one-off Yocto setup per board.
BSP & boot
Kernel, bootloader, device drivers, secure boot, OTA update, watchdog handling
Graphics & UI
Qt 5, Qt 6, Wayland/Weston, GPU-accelerated rendering
Application runtimes
Python, Node.js, Go, Rust
Security & visibility
eBPF/BTF-CO-RE detection hooks, software inventory, CVE visibility
Supported platforms
TI AM335x — fully supported in our current Yocto solution. More platforms as bring-up completes (NXP i.MX8M Nano next).
Public, citable CVE data for this stack is being generated against our QEMU reference build first; real-hardware numbers follow once NXP i.MX8M Nano bring-up is done. See vulnerability management for how that process works today.