devwiki_user
120
edits
Changes
Updates for DESK-MX8-L 4.0.0 release
|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"|16/02/2022
|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-MX8M-L release
|-
| style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000" |{{oldid|17543|17543}}
| style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000" |24/02/2023
| style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000" |DESK-MX8M-L-2.0.0 release
|-
! style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000" |{{oldid|17543|17543}}
! style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000" |2425/0207/2023! style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000" |DESK-MX8M-L-24.0.0 release
|-
|}
<section end=History/>
|-
! stable branch
| desk-mx8m-l-24.x.x| desk-mx8m-l-24.x.x
|-
! stable tag
| desk-mx8m-l-24.0.0| desk-mx8m-l-24.0.0
|}
| This image include tools for development/debugging
|-
| desk-image-qt5qt6| This image include a Qt5 Qt6 graphic backend on framebuffer
|}
For more information on the Linux filesystem, please refer to http://www.thegeekstuff.com/2010/09/linux-file-system-structure/.
[[DESK-MX8M-L | DESK-MX8M-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>desk-mx8m-l-24.x.x-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/<target_name>/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>apt-get</code> tool. Please refer to [[DESK-MX8-AN-0001:_Package_Management_with_apt-get | this application note]] for more details.
===How to build the Yocto BSP images including the U-Boot binary file, the Linux kernel image, and the target root file system image===
{{ImportantMessage|text=The following procedure requires the access to the DAVE Embedded Systems' git repositories. The access to such repositories is granted to development kit's owners only. Please refer to [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|this page]] for detailed instructions on how to get it.}}
{{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/webappdocs/en/supporting-information/Download?colCode=L5.415.70_271_2.32.0_LINUX_DOCS .zip 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-MX8M-L | DESK-MX8M-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:~$ mkdir -p ~/desk-mx-l/yocto
dvdk@vagrant:~$ cd ~/desk-mx-l/yocto
dvdk@vagrant:~/desk-mx-l/yocto$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo-1 > repo
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 29945 100 29945 0 0 583k 64816 0 --:--:-- --:--:-- --:--:-- 596k64676
dvdk@vagrant:~/desk-mx-l/yocto$ chmod a+x repo
</pre>
then, fetch the Yocto repositories with the proper branch:
<preclass="workstation-terminal">dvdk@vagrant:~/desk-mx-l/yocto$ ./repo init -u git@git.dave.eu:desk-mx-l/desk-mx-l-bsp.git -b refs/tags/desk-mx8m-l-24.0.0dvdk@vagrant:~/desk-mx-l/yocto$ ./repo sync -c
</pre>
In case of <code>ca-certificates</code> failures, which may appears during https access to some repo:
<pre class="workstation-terminal">
Fetching projects: 11% (2/17) meta-freescale-3rdpartyfatal: unable to access 'https://source.codeaurora.org/external/imxsupport/meta-nxp-demo-experience/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-
certificates.crt CRLfile: none
a possible solution is to disable the SSL verification setting:
==== Initialize DISTRO and MACHINE ====
Select the Weston backend(you will be asked to accept the EULA): <preclass="workstation-terminal">
dvdk@vagrant:~/desk-mx-l/yocto$ DISTRO=fsl-imx-wayland MACHINE=desk-mx8mp source desk-setup-release.sh -b build-wayland
...
Do you accept the EULA you just read? (y/n) y
EULA has been accepted.
Welcome to Freescale Community BSP
...
dvdk@vagrant:~/desk-mx-l/yocto/build-wayland$
==== Running 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. The process may be slowed down significantly 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, to consider the following options:
* Migrating the build system to a physical machine
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/build-wayland$ bitbake dave-image-devel
Where <code>dave-image-devel</code> is one of the images listed in [[#Quick reference|here]].
Once the build process is completed, the resulting files (the U-Boot binaries, the Linux kernel image, the device tree blob, the .tar.gz compressed root file system image, etc.) will be available in <code>build/tmp/deploy/images/desk-mx8m-l-2.x.x<machine_name></code>.
====Generating the SDKs====
After creating an image as described in the previous version, the corresponding SDK can be generated by issuing the following command:
<preclass="workstation-terminal">
bitbake dave-image-devel -c populate-sdk
</pre>