The DVDK used for the [[ORCA SOM | ORCA]] and [[MITO 8M Mini SOM | MITO 8M Mini]] SOMs is the same used for the [[DESK-MX6-L | DESK-MX6-L]] development environment.Here below you can find the simple instructions for installing the ''rc2'' release for [[DESK-MX8M-L | DESK-MX8M-L]] BSP using this Virtual Machine. ==== Installing the ''meta-toolchain'' SDK ====* open a Desktop Linux Terminal* download the proper SDK from the mirror server <code>fsl-imx-wayland-glibc-x86_64-meta-toolchain-aarch64-desk-mx8mp-toolchain-5.4-zeus.sh</code><pre class="workstation-terminal">dvdk@vagrant:~/desk-mx-l/sdk$ wget http://mirror.dave.eu/desk-mx-l/desk-mx8m-l-2.0.0-rc2/fsl-imx-wayland-glibc-x86_64-meta-toolchain-aarch64-desk-mx8mp-toolchain-5.4-zeus.sh--2022-02-14 16:09:59-- http://mirror.dave.eu/desk-mx-l/desk-mx8m-l-2.0.0-rc2/fsl-imx-wayland-glibc-x86_64-meta-toolchain-aarch64-desk-mx8mp-toolchain-5.4-zeus.shResolving mirror.dave.eu (mirror.dave.eu)... 79.143.179.155Connecting to mirror.dave.eu (mirror.dave.eu)|79.143.179.155|:80... connected.HTTP request sent, awaiting response... 200 OKLength: 445468102 (425M) [text/x-sh]Saving to: ‘fsl-imx-wayland-glibc-x86_64-meta-toolchain-aarch64-desk-mx8mp-toolchain-5.4-zeus.sh’ fsl-imx-wayland-glibc-x86_64-meta-toolchain-aar 100%[=======================================================================================================>] 424.83M 639KB/s in 8m 54s  2022-02-14 16:18:54 (815 KB/s) - ‘fsl-imx-wayland-glibc-x86_64-meta-toolchain-aarch64-desk-mx8mp-toolchain-5.4-zeus.sh’ saved [445468102/445468102] dvdk@vagrant:~/desk-mx-l/sdk$ </pre>* the ''sdk'' recommended installation directory is <code>desk-mx-l/sdk</code>* directory listing before installing the new SDK<pre class="workstation-terminal">dvdk@vagrant:~/desk-mx-l/sdk$ pwd/home/dvdk/desk-mx-l/sdkdvdk@vagrant:~/desk-mx-l/sdk$ ls -latotal 16drwxr-xr-x 4 dvdk dvdk 4096 Apr 9 2021 .drwxr-xr-x 6 dvdk dvdk 4096 Apr 9 2021 ..drwxr-xr-x 3 root root 4096 Apr 9 2021 desk-mx6-l-1.0.0drwxr-xr-x 3 root root 4096 Apr 9 2021 desk-mx6-l-1.0.0-toolchainlrwxrwxrwx 1 root root 41 Apr 9 2021 latest_desk-mx6-l -> /home/dvdk/desk-mx-l/sdk/desk-mx6-l-1.0.0lrwxrwxrwx 1 root root 51 Apr 9 2021 latest_desk-mx6-l-toolchain -> /home/dvdk/desk-mx-l/sdk/desk-mx6-l-1.0.0-toolchaindvdk@vagrant:~/desk-mx-l/sdk$ </pre>* SDK installation<pre class="workstation-terminal">dvdk@vagrant:~/desk-mx-l/sdk$ chmod 755 fsl-imx-wayland-glibc-x86_64-meta-toolchain-aarch64-desk-mx8mp-toolchain-5.4-zeus.shdvdk@vagrant:~/desk-mx-l/sdk$ ./fsl-imx-wayland-glibc-x86_64-meta-toolchain-aarch64-desk-mx8mp-toolchain-5.4-zeus.shNXP i.MX Release Distro SDK installer version 5.4-zeus======================================================Enter target directory for SDK (default: /opt/fsl-imx-wayland/5.4-zeus): /home/dvdk/desk-mx-l/sdk/desk-mx8m-l-2.0.0-rc2-toolchainYou are about to install the SDK to "/home/dvdk/desk-mx-l/sdk/desk-mx8m-l-2.0.0-rc2-toolchain". Proceed [Y/n]? YExtracting SDK.................................................................................................................doneSDK has been successfully set up and is ready to be used.Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g. $ . /home/dvdk/desk-mx-l/sdk/desk-mx8m-l-2.0.0-rc2-toolchain/environment-setup-aarch64-poky-linuxdvdk@vagrant:~/desk-mx-l/sdk$ </pre>* create a symbolic link to the SDK directory ''latest'' version ln -s /home/dvdk/desk-mx-l/sdk/desk-mx8m-l-2.0.0-rc2-toolchain latest_desk-mx8-l-toolchain* create the environment script for enabling the toolchain (during the development phase) and make it executable<pre class="workstation-terminal">dvdk@vagrant:~/desk-mx-l$ {> echo \# DESK-MX8M-L development environment for u-boot/kernel development> echo > echo source /home/dvdk/desk-mx-l/sdk/latest_desk-mx8-l-toolchain/environment-setup-aarch64-poky-linux> } | tee > /home/dvdk/desk-mx-l/desk-mx8m-l-2.0.0-rc2_env.shdvdk@vagrant:~/desk-mx-l$ chmod 755 desk-mx8m-l-2.0.0-rc2_env.shdvdk@vagrant:~/desk-mx-l$ </pre>* once installed, if required for freeing some space, the SKD file can be removed:  rm fsl-imx-wayland-glibc-x86_64-meta-toolchain-aarch64-desk-mx8mp-toolchain-5.4-zeus.sh ==== Installing the ''application'' SDK ====The previously installed SDK is used for building u-boot and kernel sources. For building userspace application another SDK has to be used: the <code>fsl-imx-wayland-glibc-x86_64-desk-image-qt5-aarch64-desk-mx8mp-toolchain-5.4-zeus.sh</code> script has been created by DAVE's Yocto building when the <code>desk-image-qt5-desk-mx8mp.tar.bz2</code> root file system has been created: it contains the SDK headers and libraries for building the Qt5 application too. The same previously described operations can be followed for installing this SDK in the same directory. At the end, both SDK are installed and present into the rfs:<pre class="workstation-terminal">dvdk@vagrant:~/desk-mx-l/sdk$ ls -latotal 435052drwxr-xr-x 5 dvdk dvdk 4096 Feb 14 16:38 ./drwxr-xr-x 6 dvdk dvdk 4096 Feb 14 16:36 ../drwxr-xr-x 3 root root 4096 Apr 9 2021 desk-mx6-l-1.0.0drwxr-xr-x 3 root root 4096 Apr 9 2021 desk-mx6-l-1.0.0-toolchaindrwxr-xr-x 3 dvdk dvdk 4096 Feb 14 16:30 desk-mx8m-l-2.0.0-rc2drwxr-xr-x 3 dvdk dvdk 4096 Feb 14 16:30 desk-mx8m-l-2.0.0-rc2-toolchainlrwxrwxrwx 1 root root 41 Apr 9 2021 latest_desk-mx6-l -> /home/dvdk/desk-mx-l/sdk/desk-mx6-l-1.0.0lrwxrwxrwx 1 root root 51 Apr 9 2021 latest_desk-mx6-l-toolchain -> /home/dvdk/desk-mx-l/sdk/desk-mx6-l-1.0.0-toolchainlrwxrwxrwx 1 dvdk dvdk 57 Feb 14 16:38 latest_desk-mx8-l -> /home/dvdk/desk-mx-l/sdk/desk-mx8m-l-2.0.0-rc2lrwxrwxrwx 1 dvdk dvdk 57 Feb 14 16:38 latest_desk-mx8-l-toolchain -> /home/dvdk/desk-mx-l/sdk/desk-mx8m-l-2.0.0-rc2-toolchaindvdk@vagrant:~/desk-mx-l/sdk$ </pre> ==== Using the SDK ====Anytime it is required to compile u-boot or kernel sources, it is enough to enabling it using the script:  source /home/dvdk/desk-mx-l/desk-mx8m-l-2.0.0-rc2_env.sh ==== MITO 8M Mini SDK ====[[MITO 8M Mini SOM| MITO 8M Mini]] has the same 4-cores Cortex-A53 architecture: even if Yocto builds two SDK, it is possible to install and use the previously described/used SDK file for both SOM modules/architectures.