Bureaucrats, dave_user, Administrators
743
edits
Changes
update stable tag to xuelk-2.0.2
{{Applies To Yocto}}
{{InfoBoxBottom}}
{{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 ==
!Notes
|-
|{{oldid|6403|1.0.0}}
|December 2016
|[[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)#XUELK_1.1.0|XUELK 1.1.0]]
|
|-
|{{oldid|7093|1.2.0}}
|May 2017
|[[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)#XUELK_1.2.0|XUELK 1.2.0]]
|
|-
|-
|2.0.0
|Sep 2017
|[[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)#XUELK_2.0.0|XUELK 2.0.0]]
|
|-
|-
! stable branch
| lynx-fidokrogoth| lynx-fidokrogoth
|-
! stable tag
| xuelk-12.10.02| xuelk-12.10.02|-
|}
| lynx-image-networking
| based on lynx-image-devel plus networking tools
|-
| lynx-image-core
| minimal working image with SSH
|-
| lynx-image-gui
| based on lynx-image-core with additional tools to support the graphical environment
|}
==Introduction==
This is a quickstart guide to build Yocto BSP for Axel ULite SOM and SBC Lynx, to rebuild the binaries (u-boot, linux kernel, root file system) provided with XUELK releases.
For more information regarding Yocto build system, go to its [[:Category:Yocto|dedicated category page]]
== Build System prerequisite prerequisites ==
XUELK 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 XUELK Yocto BSP ==
=== Initialize the build environment ===
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-fidokrogoth
dvdk@dvdk-vm:~/lynx$ ./repo sync
</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:~/lynx$ DISTRO=fsl-imx-fb MACHINE=sbc-lynx source lynx-setup-release.sh -b build-fb -e fbdvdk@dvdk-vm:~/lynx/build$ bitbake lynx-image-guinetworking
</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''.
===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 ===
<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 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">
