Embedded Linux & Yocto

Reproducible Yocto builds with licence compliance and update signing done first, not deferred until expensive.

A Yocto BSP built for reproducibility, licence compliance and signed updates from the start — and handed over so you can build it yourself.

Embedded Linux build and boot chainBuild on the left, boot on the right. Yocto layers produce a signed image; the board comes up through it to the application.Yocto layersrecipes · pinnedApplicationHMI · controlSigned imagerootfs · kernelLinux kerneldrivers · dtbCIreproducible buildU-Boot · BSPsecure bootBoard · SoCours, or yours

Scope

What we do

  • Custom BSP and machine layers for i.MX8M, AM62x, RK3588 and Raspberry Pi CM.
  • U-Boot and kernel configuration, device-tree work, and driver back-ports.
  • Reproducible builds with pinned layers, shared sstate, and a documented build procedure.
  • Secure boot, dm-verity and signed A/B updates wired in before first release.
  • SPDX/BOM output and licence-compliance review for the shipped image.
  • Boot-time reduction: measured, staged, and documented for what worked and what did not.

Typical stack

  • yocto
  • bitbake
  • u-boot
  • kernel
  • device-tree
  • boot-time
  • secure-boot
  • ota-updates
  • imx8m
  • am62x
  • rk3588
  • raspberry-pi-cm

Standards worked to

Applicable standards are agreed at the start of a programme and written into the scope. Certificates we hold are shared on request.

Deeper reading: Embedded Linux & Yocto

Talk to an engineer

Ask about this capability directly — the person who answers has shipped it.

Talk to an engineer