Open main menu

DAVE Developer's Wiki β

Changes

no edit summary
!colspan="4" style="width:100%; text-align:left"; border-bottom:solid 2px #ededed"|History
|-
!style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#73B2C7; padding:5px; color:white"|ID#
!style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#73B2C7; padding:5px; color:white"|Issue Date
!style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#73B2C7; padding:5px; color:white"|Notes
|-
|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"|{{oldid|16113|16113}}|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"|162022/02/202216}}
|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:#ededededf8fb; 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" |242023/02/202324}}| style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededededf8fb; 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:#ededededf8fb; padding:5px; color:#000000" |{{oldid|1754319807|175432023/08/22}}| 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" |DESK-MX8M-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:#ededed; padding:5px; color:#000000" |252024/0704/202302! 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-4.01.0 release
|-
|}
|-
! Repository
| BSP Manifest
| Yocto BSP Layer
|-
! URL
| git@git.dave.eu:desk-mx-l/desk-mx-l-bsp.git
| git@git.dave.eu:desk-mx-l/meta-desk-mx.git
|-
! stable branch
| desk-mx8m-l-4.x.x
| desk-mx8m-l-4.x.x
|-
! stable tag
| desk-mx8m-l-4.0.0| desk-mx8m-l-4.01.0
|}
[[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-4.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-MX8MX8M-AN-0001:_Package_Management_with_apt-get | this application note]] 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.
For more general information regarding the Yocto build system, please refer the [[:Category:Yocto|dedicated category page]].
===How to build the Yocto BSP images including the U-Boot binary file, the Linux kernel image, and the target root file system imagewith KAS===
{{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.}}
==== Initialize the build environment ====
Before running Check that 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 following packages are install it, please use the following commands:
<pre class="workstation-terminal">
dvdk@vagrant:~$ mkdir sudo apt-p ~/deskget update && sudo apt install gawk wget git diffstat unzip texinfo gcc build-mxessential chrpath socat cpio python3 python3-l/yoctodvdk@vagrant:~$ cd ~/deskpip python3-mxpexpect xz-l/yoctodvdk@vagrant:~/deskutils debianutils iputils-mxping python3-l/yocto$ curl http://commondatastorage.googleapis.com/gitpython3-repo-downloads/repo-1 > repo % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed100 29945 100 29945 0 0 64816 0 --:--:-- --:--:-- --:jinja2 libegl1-mesa libsdl1.2-:dev pylint3 xterm python3-subunit mesa- 64676dvdk@vagrant:~/deskcommon-mxdev zstd liblz4-l/yocto$ chmod a+x repotool
</pre>
thenBefore running the build, fetch the Yocto repositories with the proper branch:KAS environment must be initialized properly.
<pre class="workstation-terminal">
dvdk@vagrant:~$ virtualenv -p /usr/bin/python3 venvcreated virtual environment CPython3.8.10.final.0-64 in 351ms creator CPython3Posix(dest=/home/dooraim/venv, clear=False, no_vcs_ignore=False, global=False) seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/dooraim/.local/share/virtualenv) added seed packages: pip==24.0, setuptools==69.1.1, wheel==0.42.0 activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivatordvdk@vagrant:~$ source venv/bin/deskactivate(venv) dvdk@vagrant:~$ pip3 install kas==4.2Collecting kas==4.2 Downloading kas-4.2.tar.gz (39 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... doneCollecting PyYAML<7,>=3.0 (from kas==4.2) Using cached PyYAML-6.0.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.1 kB)Collecting distro<2,>=1.0.0 (from kas==4.2) Downloading distro-1.9.0-py3-none-any.whl.metadata (6.8 kB)Collecting jsonschema<5,>=2.5.0 (from kas==4.2) Using cached jsonschema-4.21.1-py3-none-any.whl.metadata (7.8 kB)Collecting kconfiglib<15,>=14.1.0 (from kas==4.2) Downloading kconfiglib-14.1.0-py2.py3-none-any.whl.metadata (39 kB)Collecting attrs>=22.2.0 (from jsonschema<5,>=2.5.0->kas==4.2) Using cached attrs-23.2.0-py3-none-any.whl.metadata (9.5 kB)Collecting importlib-resources>=1.4.0 (from jsonschema<5,>=2.5.0->kas==4.2) Downloading importlib_resources-6.4.0-py3-none-any.whl.metadata (3.9 kB)Collecting jsonschema-specifications>=2023.03.6 (from jsonschema<5,>=2.5.0->kas==4.2) Using cached jsonschema_specifications-2023.12.1-py3-none-any.whl.metadata (3.0 kB)Collecting pkgutil-resolve-name>=1.3.10 (from jsonschema<5,>=2.5.0->kas==4.2) Using cached pkgutil_resolve_name-1.3.10-py3-none-any.whl.metadata (624 bytes)Collecting referencing>=0.28.4 (from jsonschema<5,>=2.5.0->kas==4.2) Downloading referencing-0.34.0-py3-none-any.whl.metadata (2.8 kB)Collecting rpds-py>=0.7.1 (from jsonschema<5,>=2.5.0->kas==4.2) Using cached rpds_py-0.18.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (4.1 kB)Collecting zipp>=3.1.0 (from importlib-resources>=1.4.0->jsonschema<5,>=2.5.0-mx>kas==4.2) Downloading zipp-l3.18.1-py3-none-any.whl.metadata (3.5 kB)Downloading distro-1.9.0-py3-none-any.whl (20 kB)Using cached jsonschema-4.21.1-py3-none-any.whl (85 kB)Downloading kconfiglib-14.1.0-py2.py3-none-any.whl (145 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 145.9/yocto$ 145.9 kB 12.2 MB/repo init s eta 0:00:00Using cached PyYAML-6.0.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (736 kB)Using cached attrs-23.2.0-py3-none-any.whl (60 kB)Downloading importlib_resources-6.4.0-py3-none-any.whl (38 kB)Using cached jsonschema_specifications-2023.12.1-py3-none-any.whl (18 kB)Using cached pkgutil_resolve_name-1.3.10-py3-none-any.whl (4.7 kB)Downloading referencing-0.34.0-py3-none-any.whl (26 kB)Using cached rpds_py-0.18.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.1 MB)Downloading zipp-3.18.1-py3-none-u git@gitany.whl (8.2 kB)Building wheels for collected packages: kas Building wheel for kas (pyproject.toml) ..dave.eudone Created wheel for kas:deskfilename=kas-4.2-py3-mxnone-lany.whl size=57786 sha256=919ab9cedc442039708d8846f9fb02e8b43d823cb54d8785737bf46361c594a6 Stored in directory: /home/deskdooraim/.cache/pip/wheels/5f/47/a7/e9a292a85a88f96c6b3d834d5e9aceb6927ae2e2b89b123ecbSuccessfully built kasInstalling collected packages: zipp, rpds-py, PyYAML, pkgutil-resolve-name, kconfiglib, distro, attrs, referencing, importlib-mxresources, jsonschema-lspecifications, jsonschema, kasSuccessfully installed PyYAML-bsp6.0.git 1 attrs-b refs/tags/desk23.2.0 distro-1.9.0 importlib-resources-6.4.0 jsonschema-4.21.1 jsonschema-mx8mspecifications-l2023.12.1 kas-4.2 kconfiglib-14.1.0 pkgutil-resolve-name-1.3.10 referencing-0.34.0 rpds-py-0.18.0zipp-3.18.1(venv) dvdk@vagrant:~/desk-mx-l/yocto$ ./repo sync -c
</pre>
In case of then, fetch the <code>cameta-certificatesdesk-mx</code> failures, which may appears during https access to some reporepositories with the proper branch:
<pre class="workstation-terminal">
Fetching projects: 11% (2/17venv) meta-freescale-3rdpartyfatal: unable to access 'httpsdvdk@vagrant:~//source.codeaurora.org/external/imxsupport/metadesk-nxpmx-demo-experiencel/': server certificate verification failedyocto$ git clone git@git. CAfile: /etc/ssl/certs/ca- certificatesdave.crt CRLfile: none fatal: unable to access 'httpseu://git.openembedded.org/metadesk-python2/': server certificate verification failed. CAfile: /etc/ssl/certs/camx-certificates.crt CRLfile: none fatal: unable to access 'https://source.codeaurora.org/external/imxsupportl/meta-nxp-demodesk-experience/': server certificate verification failedmx. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none fatal: unable to access 'https://git.openembedded.org/meta-python2/': server certificate verification failed. CAfile: b refs/etctags/ssl/certs/ca-certificates.crt CRLfile: none error: Cannot fetch metadesk-nxpmx8m-demol-experience from https://source4.codeaurora1.org/external/imxsupport/meta-nxp-demo-experience0
</pre>
==== Running the build ==== Please note that even the basic root file system requires a few hours to build on a possible solution 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 disable 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* Assuming that the host system has the required resources, extending the hardware capabilities of the default MVM (e.g. adding more cores and disk space). Once completed the initialization phase, developers can launch the Yocto image build with KAS, with the SSL verification settingfollowing commands* for build <code>dave-image-devel</code> image with <code>DESK-MX8MM-L</code> machine
<pre class="workstation-terminal">
(venv) dvdk@vagrant:~/desk-mx-l/yocto$ export GIT_SSL_NO_VERIFY=1kas build desk-mx8mm-l_devel.yml
</pre>
==== Initialize DISTRO and MACHINE ====Select the Weston backend (you will be asked to accept the EULA):* for build <code>dave-image-devel</code> image with <code>DESK-MX8MM-L</code> machine with support of <code>MULTILIB-LIB32</code>
<pre class="workstation-terminal">
(venv) dvdk@vagrant:~/desk-mx-l/yocto$ DISTRO=fsl-imx-wayland MACHINE=desk-mx8mp source kas build desk-setupmx8mm-releasel_devel_multilib.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$yml
</pre>
==== Running the * for build ==== Please note that even the basic root file system requires a few hours to build on a mid<code>dave-image-devel</hi range desktop (4code> image with <code>DESK-6 cores, 8MX8MP-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 L</code> 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* Assuming that the host system has the required resources, extending the hardware capabilities of the default MVM (e.g. 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">
(venv) dvdk@vagrant:~/desk-mx-l/yocto/$ kas builddesk-wayland$ bitbake dave-imagemx8mp-devell_devel.yml
</pre>
 
Where <code>dave-image-devel</code> is one of the images listed in [[#Quick reference|here]].
====Generating the SDKs====
After creating an image as described in the previous version, In way to get the corresponding SDK can be generated by issuing for QT6, perform the following command: * for <code>DESK-MX8MM-L</code> machine <pre class="workstation-terminal">(venv) dvdk@vagrant:~/desk-mx-l/yocto$ KAS_TASK="populate_sdk" kas build desk-mx8mm-l_qt6.yml</pre> * for <code>DESK-MX8MP-L</code> machine
<pre class="workstation-terminal">
bitbake dave(venv) dvdk@vagrant:~/desk-imagemx-devel l/yocto$ KAS_TASK="populate_sdk" kas build desk-c populatemx8mp-sdkl_qt6.yml
</pre>
Again, replace <code>dave-image-devel</code> with one of the images listed in [[#Quick reference|here]].
====Generating the Toolchain====
Toolchain can be created by the following command:
 
* for <code>DESK-MX8MM-L</code> machine
<pre class="workstation-terminal">
bitbake (venv) dvdk@vagrant:~/desk-mx-l/yocto$ KAS_TARGET="meta-toolchain" kas build desk-mx8mm-l_devel.yml
</pre>
* for <code>DESK-MX8MM-L</code> machine with support of <code>MULTILIB-LIB32</code>  <pre class="workstation-terminal">(venv) dvdk@vagrant:~/desk-mx-l/yocto$ KAS_TARGET=== Building additional packages ===="meta-toolchain" kas build desk-mx8mm-l_devel_multilib.yml</pre>
To build additional packages the user must select the ''DISTRO'' and source the * for <code>deskDESK-setupMX8MP-release.shL</code> scriptmachine
<pre class="workstation-terminal">
(venv) dvdk@vagrant:~/desk-mx-l/yocto$ DISTROKAS_TARGET=fsl"meta-imx-wayland MACHINE=toolchain" kas build desk-mx8mp source desk-setup-releasel_devel.sh -b build-waylanddvdk@vagrant:~/desk-mx-l/yocto/build-wayland$yml
</pre>
And then can run any of ==== Building additional packages ==== To build additional packages, for example <code>memtester</code> the user need to perform the [http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#usingpoky-components-bitbake bitbake] following command.
<pre class="workstation-terminal">
(venv) dvdk@vagrant:~/desk-mx-l/yocto/$ KAS_TARGET="memtester" kas builddesk-wayland$ bitbake memtestermx8mm-l_devel.yml
</pre>
The resulting packages (the default format is rpmdeb) can be found inside <code>build/tmp/deploy/rpmdeb</code>. 
----
[[Category:ORCA]] [[Category:MITO 8M Mini]]
dave_user
423
edits