Difference between revisions of "Building the Yocto BSP (XELK)"

From DAVE Developer's Wiki
Jump to: navigation, search
m
(22 intermediate revisions by 4 users not shown)
Line 6: Line 6:
 
{{InfoBoxBottom}}
 
{{InfoBoxBottom}}
  
{{ObsoleteWikiPage|link=DESK-MX6-L/Development/Building_the_Yocto_BSP}}
+
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.
  
{{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.
+
For more information regarding Yocto build system, go to its [[:Category:Yocto|dedicated category page]]
}}
 
== History ==
 
  
{| class="wikitable" border="1"
+
=== Build System prerequisite ===
!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 ==
+
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.
  
{| class="wikitable" border="1"
+
DAVE Embedded System uses a standard Ubuntu 12.04.4 LTS Server 64 bit distribution plus the following additional packages:
|+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"
+
<pre class="workstation-terminal">
|+Build targets
+
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
! Name
+
    build-essential chrpath socat libsdl1.2-dev xterm
! Description
+
</pre>
|-
 
| 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 (U-Boot, 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 ==
 
 
 
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 [http://www.yoctoproject.org/docs/1.8/mega-manual/mega-manual.html#yp-resources 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 ==
+
=== Build AXEL Yocto BSP ===
  
=== Initialize the build environment ===
+
==== 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  
+
AXEL 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">
 
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/axel$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo-1 > repo
+
dvdk@dvdk-vm:~/xelk$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repo
dvdk@dvdk-vm:~/axel$ chmod a+x repo
+
dvdk@dvdk-vm:~/xelk$ 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:~/xelk$ ./repo init -u git@git.dave.eu:dave/axel/axel-bsp.git -b axel-dora
dvdk@dvdk-vm:~/axel$ ./repo sync
+
dvdk@dvdk-vm:~/xelk$ ./repo sync
 +
dvdk@dvdk-vm:~/xelk$ source axel-bsp-init-env.sh -m xelk-l -p package_rpm -b build -e x11
 +
dvdk@dvdk-vm:~/xelk/build$ bitbake axel-fsl-image-x11
 
</pre>
 
</pre>
  
=== Build the Yocto BSP image ===
+
==== Build the Yocto 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:  
+
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
 
* 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)
 
* assuming that the host system has the required resources, extending the hardware capabilities of the default DVDK (eg: adding more cores and disk space)
Line 128: Line 45:
  
 
<pre class="workstation-terminal">
 
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/axel$ DISTRO=fsl-imx-fb MACHINE=imx6qxelk source axel-setup-release.sh -b build-fb
+
dvdk@dvdk-vm:~/xelk$ source axel-bsp-init-env.sh build
dvdk@dvdk-vm:~/axel/build$ bitbake axel-image-qt5
+
dvdk@dvdk-vm:~/xelk/build$ bitbake base-rootfs-image
 
</pre>
 
</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''.
 
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===
+
==== Build additional packages ====
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
 
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">
 
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/axel$ DISTRO=fsl-imx-fb MACHINE=imx6qxelk source axel-setup-release.sh -b build-fb
+
dvdk@dvdk-vm:~/xelk$ source axel-bsp-init-env.sh build
dvdk@dvdk-vm:~/axel/build$
+
dvdk@dvdk-vm:~/xelk/build$
 
</pre>
 
</pre>
  
And then he can run any of the [http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#usingpoky-components-bitbake bitbake] commands.
+
And then can run any of the [[http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#usingpoky-components-bitbake bitbake]] command.
  
 
<pre class="workstation-terminal">
 
<pre class="workstation-terminal">
Line 156: Line 66:
 
</pre>
 
</pre>
  
The resulting packages (the default format is ipk) can be found inside ''build/tmp/deploy/rpm''.
+
The resulting packages (the default format is ipk) can be found inside ''build/tmp/deploy/ipk''.
  
 
<pre class="workstation-terminal">
 
<pre class="workstation-terminal">

Revision as of 11:16, 3 February 2016

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

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 prerequisite[edit | edit source]

Please read the Yocto manual setup section for a list of supported Linux distribution and their configuration.

DAVE Embedded System uses a standard Ubuntu 12.04.4 LTS Server 64 bit distribution plus the following additional packages:

$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
     build-essential chrpath socat libsdl1.2-dev xterm

Build AXEL Yocto BSP[edit | edit source]

Initialize the build environment[edit | edit source]

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

dvdk@dvdk-vm:~/xelk$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repo
dvdk@dvdk-vm:~/xelk$ chmod a+x repo
dvdk@dvdk-vm:~/xelk$ ./repo init -u git@git.dave.eu:dave/axel/axel-bsp.git -b axel-dora
dvdk@dvdk-vm:~/xelk$ ./repo sync
dvdk@dvdk-vm:~/xelk$ source axel-bsp-init-env.sh -m xelk-l -p package_rpm -b build -e x11
dvdk@dvdk-vm:~/xelk/build$ bitbake axel-fsl-image-x11

Build the Yocto 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:~/xelk$ source axel-bsp-init-env.sh build
dvdk@dvdk-vm:~/xelk/build$ bitbake base-rootfs-image

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.

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:~/xelk$ source axel-bsp-init-env.sh build
dvdk@dvdk-vm:~/xelk/build$

And then can run any of the [bitbake] command.

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

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

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