Changes

This {{ImportantMessage|text=As the XELK kit is a quickstart guide to build based on Yocto BSP for Axel SOMs, to rebuild the binaries implementation of the MVM follows the approach described [[Managed_Virtual_Machine_(uMVM)#Yocto-bootbased_Linux_distribution|here]]. As such, linux kernel, root file systemthe reading of [[Managed_Virtual_Machine_(MVM) provided with XELK releases#Yocto-based_Linux_distribution|this section]] is highly recommended.}}== History ==

Since the {| class="wikitable" border="1"!Version!Date!XELK version!Notes|-|1.0.0|Nov 2013|[[Axel_Embedded_Linux_Kit_(XELK)#XELK 1.0.0 | XELK 1.0.0]]||-|1.2.0|May 2014|[[Axel_Embedded_Linux_Kit_(XELK)#XELK 1.2.0 | XELK 1.2.0]]||-|{{oldid|3262|2.0.0}}|Nov 2014|[[Axel_Embedded_Linux_Kit_(XELK)#XELK 2.0.0 | XELK 2.0.0]]||-|{{oldid|3456|2.1.0}}|May 2015|[[Axel_Embedded_Linux_Kit_(XELK)#XELK 2.1.0 | XELK 2.1.0]]||-|{{oldid|4442|2.2.0}}|Feb 2016|[[Axel_Embedded_Linux_Kit_(XELK)#XELK 2.2.0 | XELK 2.2.0]]||-|{{oldid|7089|2.3.1}}|Oct 2016|[[Axel_Embedded_Linux_Kit_(XELK)#XELK 2.3.1 | XELK 2.3.1]]||-|{{oldid|7353|3.0.1}}|Nov 2017|[[Axel_Embedded_Linux_Kit_(XELK)#XELK 3.0.1 | XELK 3.0.1]]||-|4.0.0|Aug 2019|[[Axel_Embedded_Linux_Kit_(XELK)#XELK 4.0.0 | XELK virtual machine is already configured to match all the requirements for using the 4.0.0]]||-|} == Quick reference == {| class="wikitable" border="1"|+Repository Information|-! Repository| BSP Manifest| Yocto build 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|-|} {| class="wikitable" border="1"|+Build targets! Name! Description|-| axel-image-qt5| QT5 based root file system with eglfs backend|-| axel-image-java| QT5 based root file system, developers who wants with QtWebEngine and Java (OpenJDK 8)|} ==Introduction==This is a quickstart guide to quickly build a Yocto image can directly go BSP for Axel SOMs, to section 4.4.3rebuild the binaries (U-Boot, Linux kernel, root file system) provided with XELK releases.

=== Build System prerequisite =prerequisites == Please read the [http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#getting-setup Yocto manual setup section] for a list of supported Linux distribution and their configuration.

DAVE Embedded System uses XELK MVM is already configured to build this Yocto version/configuration, however, users typically don't use a standard Ubuntu 12VirtualBox VM for Yocto builds for performance reasons.04.4 LTS Server 64 bit distribution plus the following additional packages:

<pre class="workstationYou can refer to [http://www.yoctoproject.org/docs/1.8/mega-terminal">$ sudo aptmanual/mega-get install gawk wget gitmanual.html#yp-core diffstat unzip texinfo gcc-multilib \ resources Yocto manual setup section] for a list of supported Linux distribution and their configuration to create your own build-essential chrpath socat libsdl1environment on your favorite distribution.2-dev xterm</pre>

=== Build Axel the XELK Yocto BSP ===

==== Initialize the build environment ====

Bora XELK Yocto BSP uses [https://code.google.com/p/git-repo/ git-repo] tool to fetch all the required git repositories to build

dvdk@dvdk-vm:~/belkaxel$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repodvdk@dvdk-vm:~/belkaxel$ chmod a+x repodvdk@dvdk-vm:~/belkaxel$ ./repo init -u git@git.dave.eu:dave/axel/axel-bsp.git -b axel-mortydvdk@dvdk-vm:~/belkaxel$ ./repo syncdvdk@dvdk-vm:~/belk$ source axel-bsp-init-env.sh builddvdk@dvdk-vm:~/belk/build$ bitbake base-rootfs-image

==== Build the Yocto BSP image ====

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:

dvdk@dvdk-vm:~/belkaxel$ DISTRO=fsl-imx-fb MACHINE=imx6qxelk source axel-bspsetup-init-envrelease.sh -b build-fbdvdk@dvdk-vm:~/belkaxel/build$ bitbake baseaxel-rootfsimage-imageqt5

===Generating the SDKs===After creating an image as described above, the corresponding SDK can be generated by issuing the following command:<pre class="workstation-terminal">bitbake <target-image-name> -c populate-sdk</pre>Again, replace <code><target-image-name></code> with one of the images listed in [[#Quick reference|here]]. === Build additional packages ====

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

dvdk@dvdk-vm:~/xelkaxel$ DISTRO=fsl-imx-fb MACHINE=imx6qxelk source boraaxel-bspsetup-init-envrelease.sh -b build-fbdvdk@dvdk-vm:~/xelkaxel/build$

And then he can run any of the [[http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#usingpoky-components-bitbake bitbake]] commandcommands.

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