Skip to content

Yocto integration


Kynetics maintains meta-updatefactory, a layer designed to facilitate the integration of Update Factory in embedded Linux OSes built using the Yocto project. The layer provides an easy way to add support for:

This section provides guidance to set up and configure meta-updatefactory to build OS images for the following supported boards:

  1. Raspberry Pi (RPi 4B)
  2. Boundary Devices (Nitrogen6x, Nitrogen8M)
  3. Toradex (Apalis iMX6)
  4. Variscite (VAR-SOM-MX7)

The layer makes it easy to expand support to other boards.

Required layers

Here you will find references to set up a host machine with all the required Yocto layers to build an embedded Linux OS with Update Factory support.

Poky (basic layer)

See the Yocto Quick Start documentation to setup a host machine to build an embedded Linux OS with the poky layer.

Hardware layers

All supported hardware vendors provide a Yocto BSP and guidance on how to build it. Have a look at the following links for more information:

  1. Raspberry Pi BSP
  2. Boundary Devices BSP
  3. Toradex BSP
  4. Variscite BSP

meta-swupdate layer

meta-updatefactory depends on meta-swupdate. Refer to the "Building with Yocto" section in SWUpdate's documentation to customize SWUpdate configuration.

meta-updatefactory integration

Once all the required layers are in place clone meta-updatefactory alongside the other layers:

git clone -b <branch>
and add it to the bblayers.conf:
${BSPDIR}/sources/meta-swupdate \
${BSPDIR}/sources/meta-updatefactory \

Add the following snippet in the OS image recipe:

require <relative-path-to>/recipes-images/images/


If you are building for Raspberry Pi, you have to enable the U-Boot support by setting RPI_USE_U_BOOT = "1" in the local.conf

Partitioning scheme

It is possible to provide a custom .wks file (see the Yocto reference manual for the wks syntax) in your Yocto layer. The partitioning scheme requirements for meta-updatefactory are the following:

  1. a recovery partition that holds a minimal "recovery OS" to install the updates in single copy mode
  2. an updates partition that holds the .swu update files that will be installed by SWUpdate.

Variables in /etc/swupdate/swupdate.env allow customizing names and directories, if needed:


We recommend using the provided .wks files to begin with:

  • For all supported boards except the Raspberry Pi: uf-boot-root-recovery-updates.wks
  • For the Raspberry Pi: uf-rpi-boot-root-recovery-updates.wks

If using the above .wks files you can customize the boot, root and updates partition sizes with the following bitbake variables: