Changes

Jump to: navigation, search

Building the Yocto BSP (XELK)

1,555 bytes added, 12:27, 30 August 2019
no edit summary
{{InfoBoxBottom}}
===Introduction===
{{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.
For more information regarding Yocto build system, go to its [[:Category:Yocto|dedicated category page]]
=== Build System 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 ====
AXEL XELK Yocto BSP uses [https://code.google.com/p/git-repo/ git-repo] tool to fetch all the required git repositories to build
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/xelkaxel$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repodvdk@dvdk-vm:~/xelkaxel$ chmod a+x repodvdk@dvdk-vm:~/xelkaxel$ ./repo init -u git@git.dave.eu:dave/axel/axel-bsp.git -b axel-doramortydvdk@dvdk-vm:~/xelkaxel$ ./repo syncdvdk@dvdk-vm:~/xelk$ source axel-bsp-init-env.sh -m xelk-l -p package_rpm -b build -e x11dvdk@dvdk-vm:~/xelk/build$ bitbake axel-fsl-image-x11
</pre>
==== 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:
* 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)
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/xelkaxel$ DISTRO=fsl-imx-fb MACHINE=imx6qxelk source axel-bspsetup-init-envrelease.sh -b build-fbdvdk@dvdk-vm:~/xelkaxel/build$ bitbake baseaxel-rootfsimage-imageqt5
</pre>
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===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 axel-bsp-init-env.sh is placed and source it
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/xelkaxel$ DISTRO=fsl-imx-fb MACHINE=imx6qxelk source axel-bspsetup-init-envrelease.sh -b build-fbdvdk@dvdk-vm:~/xelkaxel/build$
</pre>
And then he can run any of the [[http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#usingpoky-components-bitbake bitbake]] commandcommands.
<pre class="workstation-terminal">
</pre>
The resulting packages (the default format is ipk) can be found inside ''build/tmp/deploy/ipkrpm''.
<pre class="workstation-terminal">
8,154
edits

Navigation menu