Building the Yocto BSP (BELK/BXELK)

Info Box Applies to Bora Applies to BORA Xpress

As the structure of the BELK/BXELK is based on several tools, it is strongly recommended the reading of this document first to get an overview.

As the XUELK kit is based on Yocto, the implementation of the MVM follows the approach described here. As such, the reading of this section is highly recommended.

The instructions described by this document apply to the following kits: BELK 4.0.0 or newer BXELK 2.0.0 or newer.

Introduction

As known, in addition to a bootloader and the o.s. kernel, an embedded Linux system needs a root file system to operate. The root file system must contain everything needed to support the Linux system (applications, settings, data, etc.). The root file system is the file system that is contained on the same partition on which the root directory is located. The Linux kernel, at the end of its startup stage, mounts the root file system on the configured root device and finally launches the /sbin/init, the first user space process and "father" of all the other processes. For more information on the Linux filesystem, please refer to http://www.thegeekstuff.com/2010/09/linux-file-system-structure/.

BELK/BXELK provides one (or more) pre-built root file system, that can be used during the evaluation/development/deployment cycle. For instance, the root file system included in the bora-image-devel image is suited for the development phase, since it provides a relatively rich set of packages including tools and libraries used to debug the application code. The pre-built root file systems are located here: /home/dvdk/<target_name>/rfs/<kit_name>.

Besides the pre-built root file systems, BELK/BXELK also provides a rich repository containing pre-built applications and libraries. These packages can be easily installed on the target by using the smart tool. Please refer to this section for more details.

To generate the supported root file systems, the build of the Yocto BSP has to be run. The output of this process is an image containing the U-Boot binary file, the Linux kernel image, and the selected root file system image. The following sections describe in detail how to execute this operation.

For more general information regarding the Yocto build system, please refer the dedicated category page.

How to build the Yocto BSP images including the U-Boot binary file, the Linux kernel image, and the target root file system image

The following procedure requires the access to the DAVE Embedded Systems' git repositories. The access to such repositories is granted to development kit's owners only. Please refer to this page for detailed instructions on how to get it.

The procedure described here makes use of a huge number of pre-built software modules which are included in the MVM. Technically speaking, the developer can run a Yocto-based full build process to (re)generate from scratch all these modules. However, this process requires a lot of hardware resources in terms of disk storage, RAM, and processing power. For this reason, it is discouraged to use the MVM to perform such a build. Using a physical machine is recommended instead. For more details on this topic, please refer to this document which talks about the advanced use of the Yocto build system.

Prerequisites

BELK/BXELK MVM is already configured to build this Yocto version/configuration, therefore no additional packages have to be installed by the user in order to run the Yocto BSP build process.

Initialize the build environment

Before running the build, the environment must be initialized properly.

BELK/BXELK Yocto BSP uses git-repo tool to fetch all the required git repositories. To install it, please use the following commands:

dvdk@dvdk-vm:~/lynx$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repo
dvdk@dvdk-vm:~/lynx$ chmod a+x repo
dvdk@dvdk-vm:~/lynx$ ./repo init -u git@git.dave.eu:lynx/lynx-bsp.git -b lynx-fido
dvdk@dvdk-vm:~/lynx$ ./repo sync

Run the build

Please note that even the basic root file system requires a few hours to build on a mid/hi range desktop (4-6 cores, 8-12 GiB RAM) also depending on your Internet connection speed (all sources are fetched from the network). Nearly 20GiB of disk space is required for the build. Moreover, building inside the DVDK adds some overhead, since the performances of a virtual machine are reduced if compared to the physical hardware. Thus, it's recommended to check the hardware capabilities of the host system and, when building with Yocto is required, developers should consider the following options:

• migrating the build system to a physical machine
• assuming that the host system has the required resources, extending the hardware capabilities of the default DVDK (eg: adding more cores and disk space)

Once completed the initialization phase, developers can launch the Yocto image build process with the following commands:

dvdk@dvdk-vm:~/lynx$ DISTRO=fsl-imx-fb MACHINE=sbc-lynx source lynx-setup-release.sh -b build-fb -e fb
dvdk@dvdk-vm:~/lynx/build$ bitbake lynx-image-networking

The resulting files (kernel, devicetree and u-boot binaries, plus .tar.gz root file system) will then be available inside build/tmp/deploy/images/sbc-lynx.

In addition to the typical images, the XUELK provides the following too:

• lynx-image-networking-sbc-lynx-xeno
  • With respect to the lynx-image-networking image, this includes additional libraries required to run the Linux kernel featuring the Xenomai real-time extension. For more details about it, please refer to https://xenomai.org/.

Build additional packages

To build additional packages the user must first enter the directory where the lynx-setup-release.sh is placed and source it

dvdk@dvdk-vm:~/lynx$ DISTRO=fsl-imx-fb MACHINE=sbc-lynx source lynx-setup-release.sh -b build-fb -e fb
dvdk@dvdk-vm:~/lynx/build$

And then can run any of the bitbake command.

dvdk@dvdk-vm:~/lynx/build$ bitbake memtester

The resulting packages (the default format is ipk) can be found inside build/tmp/deploy/rpm.

dvdk@dvdk-vm:~/lynx/build$ ls -l tmp/deploy/rpm/cortexa7hf_vfp_neon/memtester*
-rw-r--r-- 1 dvdk dvdk  9967 Sep  7 05:43 tmp/deploy/rpm/cortexa7hf_vfp_neon/memtester-4.1.3-r0.cortexa7hf_vfp_neon.rpm
-rw-r--r-- 1 dvdk dvdk 25544 Sep  7 05:43 tmp/deploy/rpm/cortexa7hf_vfp_neon/memtester-dbg-4.1.3-r0.cortexa7hf_vfp_neon.rpm
-rw-r--r-- 1 dvdk dvdk  2884 Sep  7 05:42 tmp/deploy/rpm/cortexa7hf_vfp_neon/memtester-dev-4.1.3-r0.cortexa7hf_vfp_neon.rpm
-rw-r--r-- 1 dvdk dvdk  5611 Sep  7 05:44 tmp/deploy/rpm/cortexa7hf_vfp_neon/memtester-doc-4.1.3-r0.cortexa7hf_vfp_neon.rpm

The generic procedure to generate the Yocto BSP image is the following:

dvdk@dvdk-vm:~/belk$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repo
dvdk@dvdk-vm:~/belk$ chmod a+x repo
dvdk@dvdk-vm:~/belk$ ./repo init -u git@git.dave.eu:bora/bora-bsp.git -b bora-morty
dvdk@dvdk-vm:~/belk$ ./repo sync
dvdk@dvdk-vm:~/belk$ source bora-bsp-init-env.sh
dvdk@dvdk-vm:~/belk/build$ bitbake <target-image-name>

bora-image bora-image-devel bora-image-networking

The components listed in the table above can be kept in sync and up to date with DAVE Embedded Systems' repositories. Once the git account has been enabled, the developer can:

• clone the repository with the git clone <git_remote_repository> command
• synchronize a source tree entering the repository directory and launching the git fetch origin command.

Please note that git fetch doesn't merge the commits on the current branch. To do that, the developer should run the git merge command or replace the fetch-merge process with a single git pull command. Please note that the recommended method is the fetch-merge process. For further information on Git, please refer to the official Git Documentation (http://git-scm.com/documentation).

Technically speaking, the developer can run a Yocto-based full build process to (re)generate all the pre-built objects included in the MVM. However, this process requires a lot of hardware resources in terms of disk storage, RAM, and processing power. For this reason, it is discouraged to use the MVM to perform such build. Using a physical machine is recommended instead. For more details on this, please refer to this page.

The following table lists the pre-built root file systems included in the MVM.

Kit version BELK BXELK	Image name	Build commands	Path
4.0.0 2.0.0	bora-image	dvdk@dvdk-vm:~/belk$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repo dvdk@dvdk-vm:~/belk$ chmod a+x repo dvdk@dvdk-vm:~/belk$ ./repo init -u git@git.dave.eu:bora/bora-bsp.git -b bora-morty dvdk@dvdk-vm:~/belk$ ./repo sync dvdk@dvdk-vm:~/belk$ source bora-bsp-init-env.sh dvdk@dvdk-vm:~/belk/build$ bitbake bora-image	/home/dvdk/bora/rfs/belk-4.0.0
	bora-image-devel	dvdk@dvdk-vm:~/belk$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repo dvdk@dvdk-vm:~/belk$ chmod a+x repo dvdk@dvdk-vm:~/belk$ ./repo init -u git@git.dave.eu:bora/bora-bsp.git -b bora-morty dvdk@dvdk-vm:~/belk$ ./repo sync dvdk@dvdk-vm:~/belk$ source bora-bsp-init-env.sh dvdk@dvdk-vm:~/belk/build$ bitbake bora-image-devel	/home/dvdk/bora/rfs/belk-4.0.0
	bora-image-networking	dvdk@dvdk-vm:~/belk$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repo dvdk@dvdk-vm:~/belk$ chmod a+x repo dvdk@dvdk-vm:~/belk$ ./repo init -u git@git.dave.eu:bora/bora-bsp.git -b bora-morty dvdk@dvdk-vm:~/belk$ ./repo sync dvdk@dvdk-vm:~/belk$ source bora-bsp-init-env.sh dvdk@dvdk-vm:~/belk/build$ bitbake bora-image-networking	/home/dvdk/bora/rfs/belk-4.0.0

The following table lists the pre-built Yocto SDKs included in the MVM. These SDKs are associated with the root file system images mentioned above.

Kit version BELK BXELK	SDK name	Build commands	Path
4.0.0 2.0.0	bora-image	bitbake bora-image -c populate-sdk	/home/dvdk/bora/sdk/belk-4.0.0/sysroots/cortexa9hf-neon-xilinx-linux-gnueabi
	bora-image-devel	bitbake bora-image-devel -c populate-sdk	/home/dvdk/bora/sdk/belk-4.0.0/sysroots/cortexa9hf-neon-xilinx-linux-gnueabi
	bora-image-networking	bitbake bora-image-networking -c populate-sdk	/home/dvdk/bora/sdk/belk-4.0.0/sysroots/cortexa9hf-neon-xilinx-linux-gnueabi

About C/C++ application development and debugging, please refer to this page.