Building the Yocto BSP (XELK)

From DAVE Developer's Wiki
(Redirected from Yocto BSP (XELK))
Jump to: navigation, search
Info Box
Axel-04.png Applies to Axel Ultra
Axel-lite 02.png Applies to Axel Lite
Axel-02.png Applies to AXEL ESATTA
Yocto-logo.png Applies to Yocto


200px-Emblem-important.svg.png As the XELK 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. 200px-Emblem-important.svg.png

History[edit | edit source]

Version Date XELK version Notes
1.0.0 Nov 2013 XELK 1.0.0
1.2.0 May 2014 XELK 1.2.0

2.0.0

Nov 2014 XELK 2.0.0

2.1.0

May 2015 XELK 2.1.0

2.2.0

Feb 2016 XELK 2.2.0

2.3.1

Oct 2016 XELK 2.3.1

3.0.1

Nov 2017 XELK 3.0.1
4.0.0 Aug 2019 XELK 4.0.0

Quick reference[edit | edit source]

Repository Information
Repository BSP Manifest Yocto BSP Layer
URL git@git.dave.eu:axel/axel-bsp.git git@git.dave.eu:axel/meta-axel.git
stable branch axel-morty axel-morty
stable tag xelk-4.0.0 xelk-4.0.0
Build targets
Name Description
axel-image-qt5 QT5 based root file system with eglfs backend
axel-image-java QT5 based root file system with QtWebEngine and Java (OpenJDK 8)

Introduction[edit | edit source]

This is a quickstart guide to build Yocto BSP for Axel SOMs, to rebuild the binaries (U-Boot, Linux kernel, root file system) provided with XELK releases.

For more information regarding Yocto build system, go to its dedicated category page

Build System prerequisites[edit | edit source]

XELK MVM is already configured to build this Yocto version/configuration, however, users typically don't use a VirtualBox VM for Yocto builds for performance reasons.

You can refer to Yocto manual setup section for a list of supported Linux distribution and their configuration to create your own build environment on your favorite distribution.

Build the XELK Yocto BSP[edit | edit source]

Initialize the build environment[edit | edit source]

XELK Yocto BSP uses git-repo tool to fetch all the required git repositories to build

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

Build the Yocto BSP image[edit | edit source]

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:~/axel$ DISTRO=fsl-imx-fb MACHINE=imx6qxelk source axel-setup-release.sh -b build-fb
dvdk@dvdk-vm:~/axel/build$ bitbake axel-image-qt5

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

Generating the SDKs[edit | edit source]

After creating an image as described above, the corresponding SDK can be generated by issuing the following command:

bitbake <target-image-name> -c populate-sdk

Again, replace <target-image-name> with one of the images listed in here.

Build additional packages[edit | edit source]

To build additional packages the user must first enter the directory where the axel-bsp-init-env.sh is placed and source it

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

And then he can run any of the bitbake commands.

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

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

dvdk@dvdk-vm:~/xelk/build$ ls -l tmp/deploy/ipk/armv7a-vfp-neon/memtester*
-rw-r--r-- 2 dvdk dvdk  7102 Aug 26 16:33 tmp/deploy/ipk/armv7a-vfp-neon/memtester_4.1.3-r0_armv7a-vfp-neon.ipk
-rw-r--r-- 2 dvdk dvdk 21720 Aug 26 16:33 tmp/deploy/ipk/armv7a-vfp-neon/memtester-dbg_4.1.3-r0_armv7a-vfp-neon.ipk
-rw-r--r-- 2 dvdk dvdk   792 Aug 26 16:33 tmp/deploy/ipk/armv7a-vfp-neon/memtester-dev_4.1.3-r0_armv7a-vfp-neon.ipk
-rw-r--r-- 2 dvdk dvdk  2748 Aug 26 16:33 tmp/deploy/ipk/armv7a-vfp-neon/memtester-doc_4.1.3-r0_armv7a-vfp-neon.ipk