Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→How to build the Yocto BSP images including the U-Boot binary file, the Linux kernel image, and the target root file system image
===Prerequisites===
BELK/BXELK MVM is already configured to build this Yocto version/configuration, therefore no additional packages have to be installed by the user in order to run the Yocto BSP build process.
=== Initialize the build environment ===
Before running the build, the environment must be initialized properly.
BELK/BXELK Yocto BSP uses [https://code.google.com/p/git-repo/ git-repo] tool to fetch all the required git repositories. To install it, please use the following commands:
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/lynx$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repo
dvdk@dvdk-vm:~/lynx$ chmod a+x repo
dvdk@dvdk-vm:~/lynx$ ./repo init -u git@git.dave.eu:lynx/lynx-bsp.git -b lynx-fido
dvdk@dvdk-vm:~/lynx$ ./repo sync
</pre>
=== Run the build ===
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:
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/lynx$ DISTRO=fsl-imx-fb MACHINE=sbc-lynx source lynx-setup-release.sh -b build-fb -e fb
dvdk@dvdk-vm:~/lynx/build$ bitbake lynx-image-networking
</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/sbc-lynx''.
In addition to the typical images, the XUELK provides the following too:
*<code>lynx-image-networking-sbc-lynx-xeno</code>
**With respect to the <code>lynx-image-networking</code> image, this includes additional libraries required to run the Linux kernel featuring the Xenomai real-time extension. For more details about it, please refer to https://xenomai.org/.
=== Build additional packages ===
To build additional packages the user must first enter the directory where the <code>lynx-setup-release.sh</code> is placed and source it
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/lynx$ DISTRO=fsl-imx-fb MACHINE=sbc-lynx source lynx-setup-release.sh -b build-fb -e fb
dvdk@dvdk-vm:~/lynx/build$
</pre>
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">
dvdk@dvdk-vm:~/lynx/build$ bitbake memtester
</pre>
The resulting packages (the default format is ipk) can be found inside ''build/tmp/deploy/rpm''.
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/lynx/build$ ls -l tmp/deploy/rpm/cortexa7hf_vfp_neon/memtester*
-rw-r--r-- 1 dvdk dvdk 9967 Sep 7 05:43 tmp/deploy/rpm/cortexa7hf_vfp_neon/memtester-4.1.3-r0.cortexa7hf_vfp_neon.rpm
-rw-r--r-- 1 dvdk dvdk 25544 Sep 7 05:43 tmp/deploy/rpm/cortexa7hf_vfp_neon/memtester-dbg-4.1.3-r0.cortexa7hf_vfp_neon.rpm
-rw-r--r-- 1 dvdk dvdk 2884 Sep 7 05:42 tmp/deploy/rpm/cortexa7hf_vfp_neon/memtester-dev-4.1.3-r0.cortexa7hf_vfp_neon.rpm
-rw-r--r-- 1 dvdk dvdk 5611 Sep 7 05:44 tmp/deploy/rpm/cortexa7hf_vfp_neon/memtester-doc-4.1.3-r0.cortexa7hf_vfp_neon.rpm
</pre>