Open main menu

DAVE Developer's Wiki β

Changes

DESK-MX6-L/Development/Building the Yocto BSP

163 bytes added, 15:07, 1 July 2021
no edit summary
[[File:TBD.png|thumb|center|200px|Work in progress]]
 
<section begin=History/>
{| style="border-collapse:collapse; "
|-
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|1.0.0
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|Oct 2020Jun 2021
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|First DESK release
|}
''desk-mx-l'' provides one (or more) pre-built root file system, that can be used during the evaluation/development/deployment cycle. For instance, the root file system included in the <code>dave-image-devel</code> image is suited for the development phase, since it provides a relatively rich set of packages including tools and libraries used to debug the application code. The pre-built root file systems are located here: <code>/home/dvdk/desk-mx-l/rfs/<kit_name></code>.
Besides the pre-built root file systems, DAVE also provides a rich repository containing pre-built applications and libraries. These packages can be easily installed on the target by using the <code>smartdnf</code> tool. Please refer to [[Advanced_use_of_Yocto_build_system_(''desk-mx-l'')#Using_pre-built_package_archive|this section]] for more details.
To generate the supported root file systems, the build of the Yocto BSP has to be run. The output of this process is an image containing the U-Boot binary file, the Linux kernel image, and the selected root file system image. The following sections describe in detail how to execute this operation.
{{ImportantMessage|text=This process requires a lot of hardware resources in terms of disk storage, RAM, and processing power. For this reason, it also is recommended to consider the use of a physical machine.
For more details on this topic, please refer to the [https://www.nxp.com/webapp/Download?colCode=imx-yocto-L4.14.98_2.0.0_ga NXP documentation on this BSP], i.e. the ''i.MX Yocto Project User's Guide'', which talks about the hosto host setup for the Yocto build system.}}
==== Initialize the build environment ====
Before running the build, the environment must be initialized properly.
''desk[[AXEL_Lite_SOM/DESK-mxMX6-l'' L | DESK-MX6-L]] 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@vagrant:~/desk-mx-l$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo -1 > repo
dvdk@vagrant:~/desk-mx-l$ chmod a+x repo
dvdk@vagrant:~/desk-mx-l$ ./repo init -u git@git.dave.eu:desk-mx-l/desk-mx-l-bsp.git -b sumorefs/tags/desk-mx6-l-1.0.1
dvdk@vagrant:~/desk-mx-l$ ./repo sync
dvdk@vagrant:~/desk-mx-l$ source deskDISTRO=fsl-mximx-lx11 MACHINE=desk-bspmx6 source desk-initsetup-envrelease.sh-b build-x11
</pre>
Once completed the initialization phase, developers can launch the Yocto image build process with the following commands:
<pre class="workstation-terminal">
dvdk@vagrant:~/desk-mx-l/yocto$ DISTRO=fsl-imx-x11 MACHINE=desk-mx6 source desk-setup-release.sh -b build-x11dvdk@vagrant:~/desk-mx-l/yocto/build-x11$ bitbake <targetdesk-image-name>x11
</pre>
Where <code><target-image-name></code> is one of the images listed in [[#Quick reference|here]].
<pre class="workstation-terminal">
dvdk@vagrant:~/desk-mx-l/yocto$ source deskDISTRO=fsl-mximx-lx11 MACHINE=desk-bspmx6 source desk-initsetup-envrelease.shdvdk@vagrant:~/desk-mxb build-l/build$x11
</pre>
<pre class="workstation-terminal">
dvdk@vagrant:~/desk-mx-l/build-x11$ bitbake memtester
</pre>
The resulting packages (the default format is ipk<code>rpm</code>) can be found inside ''build/tmp/deploy/rpm''. ''TBD: nomi dei pacakge pertinenti con il SOC''
<pre class="workstation-terminal">
8,226
edits