Changes

{{ImportantMessage|text=As the XELK kit is based on Yocto, the implementation of the MVM follows the approach described [[Managed_Virtual_Machine_(MVM)#Yocto-based_Linux_distribution|here]]. As such, the reading of [[Managed_Virtual_Machine_(MVM)#Yocto-based_Linux_distribution|this section]] is highly recommended.}}== History == {| 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 4.0.0]]||-|} == Quick reference == {| class="wikitable" border="1"|+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|-|} {| 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 with QtWebEngine and Java (OpenJDK 8)|} ==Introduction==This is a quickstart guide to build Yocto BSP for Axel SOMs, to rebuild the binaries (uU-bootBoot, linux Linux kernel, root file system) provided with XELK releases.

=== Build System prerequisite =prerequisites ==

Please read the [http:XELK MVM is already configured to build this Yocto version//www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#getting-setup configuration, however, users typically don't use a VirtualBox VM for Yocto manual setup section] builds for a list of supported Linux distribution and their configurationperformance reasons.

DAVE Embedded System uses a standard Ubuntu 12You can refer to [http://www.yoctoproject.org/docs/1.048/mega-manual/mega-manual.4 LTS Server 64 bit html#yp-resources Yocto manual setup section] for a list of supported Linux distribution plus and their configuration to create your own build environment on your favorite distribution. == Build the following additional packagesXELK Yocto BSP == === Initialize the build environment === 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:~/axel$ sudo aptcurl http://commondatastorage.googleapis.com/git-get install gawk wget repo-downloads/repo > repodvdk@dvdk-vm:~/axel$ chmod a+x repodvdk@dvdk-vm:~/axel$ ./repo init -u git@git.dave.eu:axel/axel-bsp.git-core diffstat unzip texinfo gccb axel-multilib \morty builddvdk@dvdk-essential chrpath socat libsdl1vm:~/axel$ .2-dev xterm/repo sync

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

Bora Yocto BSP uses [https:Please note that even the basic root file system requires a few hours to build on a mid//codehi 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.googleMoreover, building inside the DVDK adds some overhead, since the performances of a virtual machine are reduced if compared to the physical hardware.com/p/git-repo/ git-repo] tool Thus, it's recommended to fetch all check the hardware capabilities of the host system and, when building with Yocto is required git repositories , 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:~/belkaxel$ curl http://commondatastorage.googleapis.com/gitDISTRO=fsl-repoimx-downloads/repo > repodvdk@dvdkfb MACHINE=imx6qxelk source axel-vm:~/belk$ chmod a+x repodvdk@dvdk-vm:~/belk$ ./repo init setup-u git@gitrelease.dave.eu:dave/axel/axel-bsp.git sh -b axeldvdk@dvdkbuild-vm:~/belk$ ./repo syncfbdvdk@dvdk-vm:~/belk$ source axel-bsp-init-env.sh builddvdk@dvdk-vm:~/belk/build$ bitbake baseaxel-rootfsimage-imageqt5

Please note that even the basic The resulting files (kernel, devicetree and u-boot binaries, plus .tar.gz 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 will then be available inside ''build/tmp/deploy/images/axel''.

The resulting files (kernel===Generating the SDKs===After creating an image as described above, devicetree and uthe corresponding SDK can be generated by issuing the following command:<pre class="workstation-terminal">bitbake <target-image-name> -boot binariesc populate-sdk</pre>Again, plus .tar.gz root file system) will then be available inside ''build/tmp/deployreplace <code><target-image-name></code> with one of the images/axel''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''.