1.2. Building the SDK with Yocto

1.2.1. Introduction

This page provides the steps to build the Processor SDK and individual components from source. The Processor SDK build is based on the Arago Project which provides a set of layers for OpenEmbedded and the Yocto Project targeting TI platforms.

This page will provide the basic steps required to recreate the Processor SDK along with a reference of Processor SDK specific configurations, build targets, and target devices. Also, tips and suggestions are provided along with links for more in-depth information.

1.2.2. Steps to Run Yocto Builds inside Container

TI provides a Ubuntu 22.04 based docker image with all the packages that are required to start a Yocto Build.

The Docker Image is hosted on ghcr.io/texasinstruments.

Refer Steps to Run Yocto builds inside a Container for a comprehensive guide.

Follow Processor SDK Build Reference for Layer Configuration and Build Options.


Before starting the container, ensure that you have completed all the Pre-Requisites as mentioned here.

1.2.3. Steps to Run Yocto Builds on Host Prerequisites (One-time setup)

The recommended Linux distribution is Ubuntu 22.04.

The following build host packages are required for Ubuntu. The following command will install the required tools on the Ubuntu Linux distribution.

For Ubuntu 22.04, please run the following:

$ sudo apt-get update
$ # Install packages required for builds
$ sudo apt-get -f -y install \
    git build-essential diffstat texinfo gawk chrpath socat doxygen \
    dos2unix python3 bison flex libssl-dev u-boot-tools mono-devel \
    mono-complete curl python3-distutils repo pseudo python3-sphinx \
    g++-multilib libc6-dev-i386 jq git-lfs pigz zstd liblz4-tool \
    cpio file zstd lz4

By default Ubuntu uses “dash” as the default shell for /bin/sh. You must reconfigure to use bash by running the following command:

sudo dpkg-reconfigure dash

Be sure to select “No” when you are asked to use dash as the default system shell.

Large Swap File

Building large packages, especially several at a time, requires a lot of working memory for a computer. For computers with 32 GB of RAM or more, this should not be a problem. For computers with less RAM, a swap file of ~16GB may be needed to build large packages. Creating a large swap file, or resizing a small swap file to be larger will help avoid build errors for large packages.

Proxy Setup

If working behind a proxy, please see Working Behind a Network Proxy. Build Steps

Please refer to here for the layer configuration (oeconfig-file) for a particular release of Processor SDK Linux AM69. The MACHINE can be set to j784s4-evm, for example.

Processor SDK Linux AM69 uses the ‘oe-layersetup’ tool to configure the meta layers. If you do not have the Linux SDK package installed:

git clone https://git.ti.com/git/arago-project/oe-layersetup.git yocto-build
cd yocto-build

The Linux SDK package also has the above tool cloned at the top level. If you have it installed:

cd <SDK INSTALL DIR>/yocto-build

Then run following commands to setup a yocto build for a specific release version and build the ‘tisdk-default-image’ target.

./oe-layertool-setup.sh -f configs/processor-sdk-linux/processor-sdk-linux-<version>.txt
cd build
. conf/setenv
MACHINE=<machine> bitbake -k tisdk-default-image

Your newly built wic image will be generated in deploy-ti directory. Use Linux SD Card Creation Guide to flash this image on the SD-Card.


The tisdk-default-image now includes Chromium by default, which may increase the build time. If you prefer not to build Chromium, you can remove the meta-browser layer from the oeconfig-file before running oe-layertool-setup.sh. However, if you are building the tisdk-default-image specifically to try out the TI Apps Launcher out-of-the-box (OOB), it is not recommended to remove the meta-browser layer. The TI Apps Launcher relies on Chromium and removing the layer may impact its functionality. Keep the meta-browser layer intact for the best OOB experience.


The build will use ~250GB of hard disk space for building the tisdk-default-image.


If your computer is frequently crashing while running the bitbake command, edit the ‘./conf/local.conf’ file and set the variables: BB_NUMBER_THREADS and PARALLEL_MAKE to cap the number of threads bitbake can create at a time. By default bitbake tries to automatically figure out and set the maximum values for these variables, on your system, which may lead to errors.


While building images via Yocto, if you are facing locale.Error: unsupported locale setting error, it means your system is trying to use a locale setting which was not there. Run the following commands which will setup the locale and try building your target image again.

export LC_ALL="en_US.UTF-8"
export LC_CTYPE="en_US.UTF-8"
export LC_NUMERIC="en_US.UTF-8"
export LANG=en_US.UTF-8
export LANGUAGE=en_US.UTF-8
ulimit -n 4096

1.2.4. Processor SDK Build Reference

The following sections provide information for configuration, build options, and supported platforms of the Processor SDK. Layer Configuration

Please refer to here for the layer configuration for a particular release of Processor SDK Linux. Build Options


In addition to individual components packages, the following table provides a list of build targets supported. These are the <target> used in the command:

MACHINE=<machine> bitbake <target>

The “Build Output” is given relative to the deploy-ti directory.


Build Output




Full SDK



Target Filesystem



Minimal Target Filesytem



Minimal Target Filesytem with docker enabled



Linux glibc toolchain



K3R5 baremetal toolchain


Please refer to here for the yocto build platforms supported in Processor SDK Linux AM69. These are the <machine> used in the command:

MACHINE=<machine> bitbake <target>


Supported EVMs


J784S4 EVM, AM69 SK

RT Support

Run the command below, before the bitbake build command, to setup a yocto build with RT Linux Kernel:

echo "ARAGO_RT_ENABLE = \"1\"" >> conf/local.conf

This will tell the Arago yocto setup to pick up RT-Linux Kernel when building any images that depend on the Kernel. Alternatively, one can directly build the RT Kernel using below:

MACHINE=<machine> bitbake linux-ti-staging-rt Recipes

Recipe Basics

One or more recipes can be specified for the <target> for greater granularity of recipe development and debug. Specifying a recipe name, minus the version (if the version is appended to the name), will build the recipe and all its dependencies.

For example, the command below builds only the jailhouse recipe and all the dependencies it defines.

MACHINE=<machine> bitbake jailhouse

After the bitbake command above is successfully done, arago-tmp-[toolchain]/work/<machine>-linux/jailhouse directory will be available including the original source code under the git folder, independent shared objects (.so files) under packages-split folder, and IPKs under deploy-ipks folder.


Please note that the output of a recipe can be in another folder under “arago-tmp-[toolchain]/work” directory, depending on the defines of the recipe.

Forced Re-compilation

When needed, source code under the work directory (e.g., arago-tmp-[toolchain]/work/<machine>-linux/jailhouse/git) can be modified. After the modification is done, run the following commands to force recompilation with the new code and rebuilding of the recipe, e.g.,

MACHINE=<machine> bitbake jailhouse --force -c compile

MACHINE=<machine> bitbake jailhouse

Installing Package

To install a modified and rebuilt package, copy the new IPKs from the deploy-ipks folder (e.g., arago-tmp-[toolchain]/work/<machine>-linux/jailhouse/[version]/deploy-ipks) to the target system and then run the following command to install the IPKs:

opkg install [package_ipk].ipk

Cleaning a Built Recipe

A built recipe can be cleaned using:

MACHINE=<machine> bitbake <target> -c cleansstate


MACHINE=<machine> bitbake <target> -c cleanall

The cleansstate task will clean recipe’s work directory and remove the recipe’s output from the dependency tree used by other recipe’s during compilation.

1.2.5. See also

General information on Yocto, OpenEmbedded and Arago projects can be found at: