1.2. Building the SDK¶

1.2.2.1. Prerequisites (One-time setup)¶

Host Setup - Ubuntu (Recommended)

The recommended Linux distribution is Ubuntu 16.04 or Ubuntu 18.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 16.04 and 18.04, please run the following:

$ sudo apt-get install git build-essential python diffstat texinfo gawk chrpath dos2unix wget unzip socat doxygen libc6:i386 libncurses5:i386 libstdc++6:i386 libz1:i386

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.

Host Setup - CentOS

The build also requires that bash is configured as the default system shell. The following steps will configure Ubuntu to use bash instead of the default dash.

$ sudo dpkg-reconfigure dash
(Select "no" when prompted)

The following host packages are required for CentOS. Install the packages using the command below:

$ yum install gawk make wget tar bzip2 gzip python unzip perl patch diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath socat SDL-devel xterm doxygen glibc-devel.i686 glibc-devel libstdc++-devel.i686 libgcc.i686 libstdc++-devel dos2unix

Perl’s Thread::Queue module needs to be installed also. Download and install perl-Thread-Queue-3.02-2.el7.noarch.rpm from https://www.rpmfind.net/linux/rpm2html/search.php?query=perl-Thread-Queue.

Proxy Setup

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

Cross-Compile Toolchain

Run the following commands to install the ARM Toolchain.

$ wget https://developer.arm.com/-/media/Files/downloads/gnu-a/8.3-2019.03/binrel/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz
$ tar -Jxvf gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz -C $HOME
$ wget https://developer.arm.com/-/media/Files/downloads/gnu-a/8.3-2019.03/binrel/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz
$ tar -Jxvf gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz -C $HOME

1.2.2.2. Build Steps¶

Please refer to here for the layer configuration for a particular release of Processor SDK Linux. The final command below will build the arago-base-tisdk-image, which is the minimal Processor SDK filesystem. See Build Options for a list of additional targets.

$ git clone git://arago-project.org/git/projects/oe-layersetup.git tisdk
$ cd tisdk
$ ./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-<version>-config.txt
$ cd build
$ . conf/setenv
$ export TOOLCHAIN_PATH_ARMV7=$HOME/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf
$ export TOOLCHAIN_PATH_ARMV8=$HOME/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu
$ MACHINE=am57xx-evm bitbake arago-base-tisdk-image

1.2.3.1. Layer Configuration¶

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

1.2.3.2. Build Options¶

Images

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 arago-tmp-[toolchain]/deploy directory.

Platforms

The following platforms are supported in Processor SDK. These are the <machine> in the command:

MACHINE=<machine> bitbake <target>

RT Support

Processor SDK Linux supports RT Linux Kernel for the following machines/EVMs. Use the command below to make the RT builds:

MACHINE=<machine> ARAGO_RT_ENABLE=1 bitbake <target>

1.2.3.3. Using the snapshot of the source packages in Processor SDK release¶

Using the snapshot of the arago source packages can avoid fetch errors during the build when external URLs become unavailable. To use the snapshot of sources distributed with a given Processor SDK release, you must download a script from the SDK download page and then execute it on your host to fetch all the packages from TI servers. For example, see am57xx-evm-linux-sdk-arago-src-<version>.tar.xz file in AM57xx-Linux-SDK-Download-page. Once this package is downloaded, there are just a few extra steps in the build process to fetch all the corresponding packages. The extra steps are shown in red below:

$ git clone git://arago-project.org/git/projects/oe-layersetup.git tisdk
$ cd tisdk
$ ./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-<version>-config.txt
$ mkdir downloads
$ cd downloads
$ # Assuming src file downloaded to $HOME/Downloads
$ tar xvf $HOME/Downloads/<target-board>-linux-sdk-arago-src-##.##.##.##.tar.xz
$ <target-board>-linux-sdk-arago-src-##.##.##.##/get_build_sources.sh <target-board>-linux-sdk-arago-src-##.##.##.##/source_pkg_list.txt
$ cd ..</span>
$ cd build
$ . conf/setenv
$ export TOOLCHAIN_PATH_ARMV7=$HOME/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf
$ export TOOLCHAIN_PATH_ARMV8=$HOME/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu
$ MACHINE=<target-board> bitbake arago-core-tisdk-bundle

1.2.3.4. 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 opencl recipe and all the dependencies it defines.

MACHINE=am57xx-evm bitbake opencl

After the bitbake command above is successfully done, arago-tmp-[toolchain]/work/am57xx_evm-linux-gnueabi/opencl 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.

Forced Re-compilation

When needed, source code under the work directory (e.g., arago-tmp-[toolchain]/work/am57xx_evm-linux-gnueabi/opencl/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=am57xx-evm bitbake opencl --force -c compile

MACHINE=am57xx-evm bitbake opencl

Installing Package

To install a modified and rebuilt package, copy the new IPKs from the deploy-ipks folder (e.g., arago-tmp-[toolchain]/work/am57xx_evm-linux-gnueabi/opencl/[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

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.