Difference between revisions of "DART-6UL Yocto Jethro R1 build"

From Variscite Wiki
 
(26 intermediate revisions by 2 users not shown)
Line 27: Line 27:
 
$ export PATH=~/bin:$PATH
 
$ export PATH=~/bin:$PATH
  
$ mkdir ~/var-dart-6ul-yocto-jethro
+
$ mkdir ~/var-mx6ul-mx7-yocto-jethro
$ cd ~/var-dart-6ul-yocto-jethro
+
$ cd ~/var-mx6ul-mx7-yocto-jethro
$ repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-4.1.15-1.0.0_ga
+
$ repo init -u https://source.codeaurora.org/external/imx/fsl-arm-yocto-bsp.git -b imx-4.1.15-1.0.0_ga
 
$ repo sync
 
$ repo sync
 
</pre>
 
</pre>
Line 35: Line 35:
 
= Download Yocto Jethro i.MX6UL with Meta Variscite DART-6UL support =
 
= Download Yocto Jethro i.MX6UL with Meta Variscite DART-6UL support =
 
<pre>
 
<pre>
$ cd ~/var-dart-6ul-yocto-jethro/sources
+
$ cd ~/var-mx6ul-mx7-yocto-jethro/sources
$ git clone https://github.com/varigit/meta-variscite-mx6ul-mx7/ -b imx_4.1.15_6ul_ga-var01
+
$ git clone https://github.com/varigit/meta-variscite-mx6ul-mx7.git -b imx_4.1.15_ga-var01
 
$ cp meta-variscite-mx6ul-mx7/scripts/var-setup-release.sh ../
 
$ cp meta-variscite-mx6ul-mx7/scripts/var-setup-release.sh ../
 
$ patch -p1 < meta-variscite-mx6ul-mx7/patch/Fix-FSL-multi-patch-append-bugs.patch
 
$ patch -p1 < meta-variscite-mx6ul-mx7/patch/Fix-FSL-multi-patch-append-bugs.patch
Line 42: Line 42:
  
 
= Setup and build Yocto =
 
= Setup and build Yocto =
The following images can be built:
+
The following distros can be used:
 
* fsl-imx-x11 - Only X11 graphics
 
* fsl-imx-x11 - Only X11 graphics
 
* fsl-imx-wayland - Wayland weston graphics
 
* fsl-imx-wayland - Wayland weston graphics
Line 52: Line 52:
  
 
'''Sample build scenarios:'''
 
'''Sample build scenarios:'''
* [[VAR-SOM-MX6 Yocto Jethro R4 Build Yocto release#Build X11 GUI image without Qt content | Build X11 GUI image without Qt content]]
+
* [[#Build X11 GUI image without Qt content|Build X11 GUI image without Qt content]]
* [[VAR-SOM-MX6 Yocto Jethro R4 Build Yocto release#Build opensource QT5 image | Build opensource QT5 image]]
+
* [[#Build Qt5 image without X11|Build Qt5 image without X11]]
 
== Build X11 GUI image without Qt content ==
 
== Build X11 GUI image without Qt content ==
 
<pre>
 
<pre>
$ cd ~/var-dart-6ul-yocto-jethro
+
$ cd ~/var-mx6ul-mx7-yocto-jethro
 
$ MACHINE=imx6ul-var-dart DISTRO=fsl-imx-x11 source var-setup-release.sh -b build_x11
 
$ MACHINE=imx6ul-var-dart DISTRO=fsl-imx-x11 source var-setup-release.sh -b build_x11
 
</pre>
 
</pre>
Line 71: Line 71:
 
</pre>
 
</pre>
  
== Build opensource QT5 image ==
+
== Build Qt5 image without X11 ==
 
<pre>
 
<pre>
$ cd ~/var-dart-6ul-yocto-jethro
+
$ cd ~/var-mx6ul-mx7-yocto-jethro
 
$ MACHINE=imx6ul-var-dart DISTRO=fsl-imx-fb source var-setup-release.sh -b build-fb
 
$ MACHINE=imx6ul-var-dart DISTRO=fsl-imx-fb source var-setup-release.sh -b build-fb
 
</pre>
 
</pre>
Line 85: Line 85:
 
$ bitbake fsl-image-qt5
 
$ bitbake fsl-image-qt5
 
</pre>
 
</pre>
 
== local.conf customization ==
 
 
Edit you local.conf file:
 
<pre>$ gedit conf/local.conf
 
</pre>
 
Modify download directory:
 
 
Change packages download directory. By default it is set to:
 
DL_DIR ?= "${BSPDIR}/downloads/"
 
change it to a global folder like
 
DL_DIR = "/opt/yocto_downloads/".
 
Don't forget to create the folder and make it available without a sudo permissions.
 
  
 
== Build Results ==
 
== Build Results ==
The resulted images are located in tmp/deploy/images/imx6ul-var-dart/.<br/>Looking at tmp/deploy/images/imx6ul-var-dart/ you will find 6 main files that are linked to the actual file<br/>
+
The resulted images are located in tmp/deploy/images/imx6ul-var-dart/
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 106: Line 93:
 
! scope="col" | Image Name<br/>
 
! scope="col" | Image Name<br/>
 
! scope="col" | How to use<br/>
 
! scope="col" | How to use<br/>
|-
 
| fsl-image-gui-imx6ul-var-dart.ext4<br/>
 
| Not in Use<br/>
 
 
|-
 
|-
 
| fsl-image-gui-imx6ul-var-dart.sdcard
 
| fsl-image-gui-imx6ul-var-dart.sdcard
| This image is for SD-Card boot.<br> It can be flashed as-is on an SD-Card and you can boot your system <br> form SD-Card, according to the relevant startup-guide of your product (usually requires to press the boot select button, or toggle a dip-switch).
+
| This image is for SD card boot.<br> It can be flashed as-is on an SD card and you can boot your system <br> form SD card, according to the relevant startup-guide of your product (usually requires to press the boot select button, or toggle a dip-switch).
For detailed information refer to Create a sample SDCARD section below [[DART-6UL Yocto Fido R1 Build Yocto release#Create_a_bootable_SD-Card |Create a bootable SD-Card]].
+
For detailed information refer to Create a sample SD card section below [[#Create_a_bootable_SD_card |Create a bootable SD card]].
 
|-
 
|-
 
| fsl-image-gui-imx6ul-var-dart.tar.bz2
 
| fsl-image-gui-imx6ul-var-dart.tar.bz2
Line 118: Line 102:
 
|-
 
|-
 
| fsl-image-gui-imx6ul-var-dart.ubi
 
| fsl-image-gui-imx6ul-var-dart.ubi
| Use the sdcard created above. Copy the file into it and use the following commands to flash them into nand.<br/>Coping files (mount the sd-card created above first):
+
| Use the SD card created above. Copy the file into it and use the following commands to flash them into NAND.<br/>Coping files (mount the SD card created above first):
 
|-
 
|-
 
| zImage
 
| zImage
Line 124: Line 108:
 
|-
 
|-
 
| SPL-nand
 
| SPL-nand
| SPL built for NAND-Flash. The SPL is pre-u-boot SW component, required for DDR initialization
+
| SPL built for NAND flash. The SPL is a pre-U-Boot SW component, required for DDR initialization
|-
 
| u-boot-nand-2015.10-r0.img
 
| U-Boot built for NAND Flash.
 
 
|-
 
|-
 
| SPL-sd
 
| SPL-sd
| SPL built for SD-Card boot. The SPL is pre-u-boot SW component, required for DDR initialization
+
| SPL built for SD card boot. The SPL is pre-U-Boot SW component, required for DDR initialization
 
|-
 
|-
 
| u-boot.img-sd
 
| u-boot.img-sd
| u-boot built for SD-Card boot, or eMMC boot in case of DART-MX6UL.
+
| U-Boot built for SD card boot, or eMMC boot
 
|-
 
|-
 
| u-boot.img-nand
 
| u-boot.img-nand
| u-boot built for nand boot in case of DART-MX6UL.
+
| U-Boot built for NAND flash boot
 
|-
 
|-
 
! scope="col" | Device Tree Name<br/>
 
! scope="col" | Device Tree Name<br/>
Line 142: Line 123:
 
|-
 
|-
 
| zImage-imx6ul-var-dart-emmc_wifi.dtb
 
| zImage-imx6ul-var-dart-emmc_wifi.dtb
| Boot from internal eMMC with WI-FI enabled. (SDCARD & NAND disabled)
+
| Boot from internal eMMC with WI-FI enabled. (SD card & NAND disabled)
 
|-
 
|-
 
| zImage-imx6ul-var-dart-nand_wifi.dtb
 
| zImage-imx6ul-var-dart-nand_wifi.dtb
| Boot from internal NAND with WI-FI enabled. (SDCARD & eMMC disabled)
+
| Boot from internal NAND with WI-FI enabled. (SD card & eMMC disabled)
 
|-
 
|-
 
| zImage-imx6ul-var-dart-sd_emmc.dtb
 
| zImage-imx6ul-var-dart-sd_emmc.dtb
| SDCARD and eMMC enabled (WIFI & NAND disabled). You can boot from eMMC or SDCARD
+
| SD card and eMMC enabled (WIFI & NAND disabled). You can boot from eMMC or SD card
 
|-
 
|-
 
| zImage-imx6ul-var-dart-sd_nand.dtb
 
| zImage-imx6ul-var-dart-sd_nand.dtb
| SDCARD and NAND enabled (WIFI & eMMC disabled). You can boot from NAND or SDCARD
+
| SD card and NAND enabled (WIFI & eMMC disabled). You can boot from NAND or SD card
 
|-
 
|-
 
|}
 
|}
  
= Create a bootable SD-Card =
+
= Create a bootable SD card =
== SD-Card structure ==
+
== SD card structure ==
[[File:Sdcard_part.png]]
+
The first unallocated 4MB are saved space for U-Boot. it can be replaced with a dd command described in "U-Boot out of tree" section below.<br>
<br>The SD-Card is divided into 3 sections as shown in the picture above.
+
The first partition is a fat16 partition used for the Linux uImage and device tree files. You can copy them as described in the Linux out of tree section.<br>
<br>The first unallocated 4MB are saved space for SPL and u-boot.img. it can be replaced with a dd command described in u-boot out of tree section below.
+
The second partition is an ext4 partition that contains the complete file system and modules.
<br>The second partition is a fat16 partition used for the device tree files and Linux uImage file. You can copy them as described in the Linux out of tree section.
 
<br>The third partition is an ext3 partition that contains the complete file system and modules.
 
  
 +
== Yocto pre-built bootable SD card ==
 +
The Yocto build products contains many files as explained in [[#Build Results|Build Results]] section above including a ".sdcard" file. For example, fsl-image-gui-imx6ul-var-dart.sdcard, depending on your build.<br>
 +
This is a complete image to be flashed directly to an SD card.<br>
 +
Example usage:
  
 
+
<pre>
== Yocto pre-built bootable SD-Card ==
+
$ cd ~/var-mx6ul-mx7-yocto-jethro/build_x11
The Yocto build products contains many files as explained in [[DART-6UL Yocto Jethro Build Yocto release#Build Results | Build Results section]] above including a ".sdcard" file. For example fsl-image-gui-imx6ul-var-dart.sdcard. This is a complete image to be flashed directly to an SD-Card.<br> Example usage:
 
 
 
<pre>$ cd ~/var-dart-6ul-yocto-jethro/build_x11
 
 
$ sudo dd if=tmp/deploy/images/imx6ul-var-dart/fsl-image-gui-imx6ul-var-dart.sdcard of=/dev/sdX bs=1M
 
$ sudo dd if=tmp/deploy/images/imx6ul-var-dart/fsl-image-gui-imx6ul-var-dart.sdcard of=/dev/sdX bs=1M
 
Replace sdX with the right device name.
 
Replace sdX with the right device name.
 
</pre>
 
</pre>
 +
 
Drawbacks of the native .sdcard yocto-built image:
 
Drawbacks of the native .sdcard yocto-built image:
* The second partition size doesn't use the entire SD-Card.
+
* The second partition size doesn't use the entire SD card.
 
* The second partition is not labeled as rootfs.
 
* The second partition is not labeled as rootfs.
 
* The NAND and eMMC flashing scripts are not included.
 
* The NAND and eMMC flashing scripts are not included.
  
== Create an extended SD-Card ==
+
== Create an extended SD card ==
Variscite provides var-create-yocto-sdcard.sh script that makes use of the .sdcard image mentioned above, extends the partitions of the SD-Card to the maximum available space, and copies the NAND-Flash burning scripts and relevant binaries for your convenience.<br> Later, you will be able to follow [http://variwiki.com/index.php?title=DART-6UL_NAND_Flash_Burning DART-6UL NAND Flash Burning] do burn your images to NAND-Flash or eMMC <br>
+
Variscite provides the var-create-yocto-sdcard.sh script which creates our NAND/eMMC recovery SD card - an SD card based on the fsl-image-gui filesystem, which copies the NAND flash burning scripts and relevant binaries for your convenience.<br>
See usage below:
+
Later, you will be able to follow either the more automatic [[DART-6UL Yocto NAND Recovery|DART-6UL Yocto Recovery SD card]] guide or the more manual [[DART-6UL NAND Flash Burning|Flashing the internal storage device]] guide to burn your images to NAND flash or eMMC.<br><br>
<pre>$ cd ~/var-dart-6ul-yocto-jethro/build_x11
 
$ sudo ../sources/meta-variscite-mx6ul-mx7/scripts/var_mk_yocto_sdcard/var-create-yocto-sdcard.sh /dev/sdX
 
Replace sdX with the right device name.
 
</pre>The script assume fsl-image-qt5-minimal build was used. It is very easy to modify it and adopt it to your requirements.
 
  
= Boot board with a bootable SD-Card =
+
Note:<br>
<span style="color:red">Note: Boot from SD-Card eliminates Wifi</span> as the Wifi and SD-Card are using same SDIO interface.<br>
+
This is essentially the same as our pre-built Recovery SD image, with the following main difference:<br>
A typical use-case, is to boot from SD-Card, flash eMMC or NAND-Flash, and re-boot form eMMC/NAND to have Wi-Fi operational.
+
The pre-built image's rootfs partition size is 3700MiB, which is also the default size when using the script, but the script also has an option to set the rootfs partition size to fill the whole free space of the used SD card. Anyway, you can always resize the partition later with an external tool such as gparted.<br>
 +
Naturally, the pre-built image is more straight forward and easier to use, while the script method is easier to customize.<br><br>
  
== Setting board dip-switches ==
+
Usage:<br>
Booting your system requires switching the relevant dip-switch to "Boot from SD-Card". See picture below.<br>
+
* Follow the [[#Setup and build Yocto|Setup and build Yocto]] guide, and bitbake fsl-image-gui.
 +
* Plug-in the SD card to your Linux HOST PC, run dmesg and see which device is added (i.e. /dev/sdX or /dev/mmcblkX)
 +
<pre>
 +
$ sudo MACHINE=imx6ul-var-dart ~/var-mx6ul-mx7-yocto-jethro/sources/meta-variscite-mx6ul-mx7/scripts/var_mk_yocto_sdcard/var-create-yocto-sdcard.sh <options> /dev/sdX
 +
(Replace /dev/sdX with your actual device)
 +
</pre>
 +
<pre>
 +
options:
 +
  -h            Display help message
 +
  -s            Only show partition sizes to be written, without actually write them
 +
  -a            Automatically set the rootfs partition size to fill the SD card
  
 +
If you don't use the '-a' option, a default rootfs size of 3700MiB will be used
 +
</pre>
  
 +
= Boot board with a bootable SD card =
 +
<span style="color:red">Note: Boot from SD card eliminates Wifi</span> as the Wifi and SD card are using same SDIO interface.<br>
 +
A typical use-case, is to boot from SD card, flash eMMC or NAND flash, and re-boot form eMMC/NAND to have Wi-Fi operational.
  
 +
== Setting the Boot DIP switches ==
 +
Booting your system from an SD card requires switching the Boot DIP switches. See picture below.
 
[[File:Boot_switch_6ul1.jpg|thumb|none|upright=2.0]]
 
[[File:Boot_switch_6ul1.jpg|thumb|none|upright=2.0]]
<br>
+
* "00" The current position in the picture will set the system to boot from SD card.
* "00" - Boot from SDCARD - The picture mode
+
* "01" Moving the right switch will set the system to boot from eMMC
* "01" - Boot from eMMC
+
* "10" Moving the left switch will set the system to boot from NAND flash
* "10" - Boot from NAND-Flash
 
 
* "11" is illegal.
 
* "11" is illegal.
Be aware that your SOM has either eMMC or NAND but never both !<br><br>
+
Be aware that your system has eMMC or NAND but never both.
 
 
To boot board with SD-Card, Follow the steps below:<br>
 
 
 
*Power-off the board.
 
*Insert the SD card into the SD/MMC slot of the carrier board (DVK)
 
*Switch the relevant dip-switch to "Boot from SD-Card"
 
*Power-up board
 
*The board will automatically boot into Linux from SD-Card
 
  
 
== Automatic device Tree selection in U-Boot ==
 
== Automatic device Tree selection in U-Boot ==
Upon reset you will see the U-BOOT-SPL printouts. It will print also the SOM configuration:
+
Upon reset you will see the U-Boot SPL printouts. It will print also the SOM configuration:
 
<br>On-SOM storage: SD only, eMMC, NAND.
 
<br>On-SOM storage: SD only, eMMC, NAND.
 
<br>WIFI if chip exits.
 
<br>WIFI if chip exits.
Line 226: Line 212:
 
</pre>
 
</pre>
 
As explained in the above [[DART-6UL Yocto Fido R1 Build Yocto release#Build_Results | Build Results]] table we have 4 optional configurations.
 
As explained in the above [[DART-6UL Yocto Fido R1 Build Yocto release#Build_Results | Build Results]] table we have 4 optional configurations.
<br>We implemented in U-BOOT and automatic device tree selection, so when kernel boots, the u-boot will load the corresponding device tree according to On-SOM configuration.  
+
<br>We implemented in U-Boot and automatic device tree selection, so when kernel boots, the U-Boot will load the corresponding device tree according to On-SOM configuration.  
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 266: Line 252:
 
|}
 
|}
  
<span style="color:red">Note: Boot from SD-Card eliminates Wifi</span> as the Wifi and SD-Card are using same SDIO interface.<br>
+
<span style="color:red">Note: Boot from SD card eliminates Wifi</span> as the Wifi and SD card are using same SDIO interface.<br>
A typical use-case, is to boot from SD-Card, flash eMMC or NAND-Flash, and re-boot form eMMC/NAND to have Wi-Fi operational.
+
A typical use-case, is to boot from SD card, flash eMMC or NAND flash, and re-boot form eMMC/NAND to have Wi-Fi operational.
  
 
== Disable Automatic Device Tree selection ==
 
== Disable Automatic Device Tree selection ==
To disable the automatic device tree selection in u-boot:
+
To disable the automatic device tree selection in U-Boot:
 
<pre>
 
<pre>
 
$ setenv var_auto_fdt_file=N
 
$ setenv var_auto_fdt_file=N
Line 290: Line 276:
 
= Flash images to NAND/eMMC =
 
= Flash images to NAND/eMMC =
  
Please refer to [http://variwiki.com/index.php?title=DART-6UL_NAND_Flash_Burning DART-6UL NAND Flash Burning]
+
Please refer to [https://variwiki.com/index.php?title=DART-6UL_NAND_Flash_Burning DART-6UL NAND Flash Burning]
  
 
= QT5/Embedded runtime =
 
= QT5/Embedded runtime =
Line 320: Line 306:
 
</pre>
 
</pre>
  
= Next steps =
+
= Update Yocto Jethro Meta-Variscite =
In sections 1-6 we explained how to build Yocto for DART-6UL. We explained the results for nand (UBI) and for sd-card.
+
From time to time we will post updates to meta-variscite that will include new features and bug fixes.<br>
At this point you should have a bootable sd-card with UBI images on it. You should be able to boot from the sd-card using the boot select button and flash the nand.
+
Follow the instructions below to update your tree:
Next steps:<br>
+
<pre>
* Build and deploy the compiler and tools.
+
$ cd ~/var-mx6ul-mx7-yocto-jethro/sources/meta-variscite-mx6ul-mx7/
* Fetch u-boot and compile it out of Yocto tools.
 
* Fetch Linux kernel and compile it out of Yocto tools.
 
 
 
= Update Yocto Jethro i.MX6UL Meta Variscite DART-6UL support =
 
From time to time we will post updates to meta-variscite-mx6ul-mx7. This will include improve features and bug fix.
 
You can track the history log in the previous page to see if such an update was posted. In such a case follow the instructions below to update your tree.
 
<pre>$ cd ~/var-dart-6ul-yocto-jethro/sources/meta-variscite-mx6ul-mx7/
 
 
$ git fetch origin
 
$ git fetch origin
 +
$ git checkout imx_4.1.15_ga-var01
 
$ git pull
 
$ git pull
Set your enviroment
+
 
$ cd ~/var-dart-6ul-yocto-jethro
+
Setup your enviroment:
 +
$ cd ~/var-mx6ul-mx7-yocto-jethro
 
$ MACHINE=imx6ul-var-dart DISTRO=fsl-imx-x11 source var-setup-release.sh -b build_x11
 
$ MACHINE=imx6ul-var-dart DISTRO=fsl-imx-x11 source var-setup-release.sh -b build_x11
In order to update the kernel
+
In order to update the kernel and U-Boot:
$ bitbake -c cleanall linux-variscite
+
$ bitbake -c cleanall fsl-image-gui u-boot-variscite linux-variscite cryptodev-module
$ bitbake  -c cleanall u-boot-variscite
+
and build your image:
and build your image
 
 
$ bitbake fsl-image-gui
 
$ bitbake fsl-image-gui
 
</pre>
 
</pre>

Latest revision as of 18:21, 2 December 2020

DART-6UL - Yocto fsl-4.1.15 Yocto Jethro R1 Build

1 Installing required packages

Follow the link below and install all required packages on your machine.

www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html

Please make sure you host PC is running Ubuntu 14.04 and install the following packages:

sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev
sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev
sudo apt-get install python-git xterm sed cvs subversion coreutils texi2html
sudo apt-get install docbook-utils python-pysqlite2 help2man make gcc g++ desktop-file-utils libgl1-mesa-dev
sudo apt-get install libglu1-mesa-dev mercurial automake groff curl lzop asciidoc u-boot-tools mtd-utils

2 Documentation

Documentation are available for Download from FreescaleJethroDocuments

3 Download Yocto Jethro for i.MX6UL Freescale source

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin (this step may not be needed if the bin folder already exists)
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/var-mx6ul-mx7-yocto-jethro
$ cd ~/var-mx6ul-mx7-yocto-jethro
$ repo init -u https://source.codeaurora.org/external/imx/fsl-arm-yocto-bsp.git -b imx-4.1.15-1.0.0_ga
$ repo sync

4 Download Yocto Jethro i.MX6UL with Meta Variscite DART-6UL support

$ cd ~/var-mx6ul-mx7-yocto-jethro/sources
$ git clone https://github.com/varigit/meta-variscite-mx6ul-mx7.git -b imx_4.1.15_ga-var01
$ cp meta-variscite-mx6ul-mx7/scripts/var-setup-release.sh ../
$ patch -p1 < meta-variscite-mx6ul-mx7/patch/Fix-FSL-multi-patch-append-bugs.patch

5 Setup and build Yocto

The following distros can be used:

  • fsl-imx-x11 - Only X11 graphics
  • fsl-imx-wayland - Wayland weston graphics
  • fsl-imx-xwayland - Wayland graphics and X11. X11 applications using EGL are not supported
  • fsl-imx-fb - Frame Buffer graphics - no X11 or Wayland


Note: refer to ftp://customerv:Variscite1@ftp.variscite.com/VAR-SOM-MX6/Software/Linux/Yocto/fsl-yocto-imx-4.1.15_1.0.0-docs/Freescale_Yocto_Project_User's_Guide.pdf
Page 7 for further information.

Sample build scenarios:

5.1 Build X11 GUI image without Qt content

$ cd ~/var-mx6ul-mx7-yocto-jethro
$ MACHINE=imx6ul-var-dart DISTRO=fsl-imx-x11 source var-setup-release.sh -b build_x11

Optional: Direct downloads to /opt/yocto_downloads, make sure directory exists and all permissions are set

$ sudo mkdir /opt/yocto_downloads
$ sudo chmod 777 /opt/yocto_downloads/
$ sed -i 's/DL_DIR ?= "${BSPDIR}\/downloads/DL_DIR = "\/opt\/yocto_downloads/g' conf/local.conf

launch bitbake:

$ bitbake fsl-image-gui

5.2 Build Qt5 image without X11

$ cd ~/var-mx6ul-mx7-yocto-jethro
$ MACHINE=imx6ul-var-dart DISTRO=fsl-imx-fb source var-setup-release.sh -b build-fb

Optional: Direct downloads to /opt/yocto_downloads, make sure directory exists and all permissions are set

sed -i 's/DL_DIR ?= "${BSPDIR}\/downloads/DL_DIR = "\/opt\/yocto_downloads/g' conf/local.conf

launch bitbake:

$ bitbake fsl-image-qt5

5.3 Build Results

The resulted images are located in tmp/deploy/images/imx6ul-var-dart/

Image Name
How to use
fsl-image-gui-imx6ul-var-dart.sdcard This image is for SD card boot.
It can be flashed as-is on an SD card and you can boot your system
form SD card, according to the relevant startup-guide of your product (usually requires to press the boot select button, or toggle a dip-switch).

For detailed information refer to Create a sample SD card section below Create a bootable SD card.

fsl-image-gui-imx6ul-var-dart.tar.bz2 Used to create an NFS root file system on the host. See apendix for setting an NFS server
fsl-image-gui-imx6ul-var-dart.ubi Use the SD card created above. Copy the file into it and use the following commands to flash them into NAND.
Coping files (mount the SD card created above first):
zImage Linux kernel image
SPL-nand SPL built for NAND flash. The SPL is a pre-U-Boot SW component, required for DDR initialization
SPL-sd SPL built for SD card boot. The SPL is pre-U-Boot SW component, required for DDR initialization
u-boot.img-sd U-Boot built for SD card boot, or eMMC boot
u-boot.img-nand U-Boot built for NAND flash boot
Device Tree Name
Boot Device
zImage-imx6ul-var-dart-emmc_wifi.dtb Boot from internal eMMC with WI-FI enabled. (SD card & NAND disabled)
zImage-imx6ul-var-dart-nand_wifi.dtb Boot from internal NAND with WI-FI enabled. (SD card & eMMC disabled)
zImage-imx6ul-var-dart-sd_emmc.dtb SD card and eMMC enabled (WIFI & NAND disabled). You can boot from eMMC or SD card
zImage-imx6ul-var-dart-sd_nand.dtb SD card and NAND enabled (WIFI & eMMC disabled). You can boot from NAND or SD card

6 Create a bootable SD card

6.1 SD card structure

The first unallocated 4MB are saved space for U-Boot. it can be replaced with a dd command described in "U-Boot out of tree" section below.
The first partition is a fat16 partition used for the Linux uImage and device tree files. You can copy them as described in the Linux out of tree section.
The second partition is an ext4 partition that contains the complete file system and modules.

6.2 Yocto pre-built bootable SD card

The Yocto build products contains many files as explained in Build Results section above including a ".sdcard" file. For example, fsl-image-gui-imx6ul-var-dart.sdcard, depending on your build.
This is a complete image to be flashed directly to an SD card.
Example usage:

$ cd ~/var-mx6ul-mx7-yocto-jethro/build_x11
$ sudo dd if=tmp/deploy/images/imx6ul-var-dart/fsl-image-gui-imx6ul-var-dart.sdcard of=/dev/sdX bs=1M
Replace sdX with the right device name.

Drawbacks of the native .sdcard yocto-built image:

  • The second partition size doesn't use the entire SD card.
  • The second partition is not labeled as rootfs.
  • The NAND and eMMC flashing scripts are not included.

6.3 Create an extended SD card

Variscite provides the var-create-yocto-sdcard.sh script which creates our NAND/eMMC recovery SD card - an SD card based on the fsl-image-gui filesystem, which copies the NAND flash burning scripts and relevant binaries for your convenience.
Later, you will be able to follow either the more automatic DART-6UL Yocto Recovery SD card guide or the more manual Flashing the internal storage device guide to burn your images to NAND flash or eMMC.

Note:
This is essentially the same as our pre-built Recovery SD image, with the following main difference:
The pre-built image's rootfs partition size is 3700MiB, which is also the default size when using the script, but the script also has an option to set the rootfs partition size to fill the whole free space of the used SD card. Anyway, you can always resize the partition later with an external tool such as gparted.
Naturally, the pre-built image is more straight forward and easier to use, while the script method is easier to customize.

Usage:

  • Follow the Setup and build Yocto guide, and bitbake fsl-image-gui.
  • Plug-in the SD card to your Linux HOST PC, run dmesg and see which device is added (i.e. /dev/sdX or /dev/mmcblkX)
$ sudo MACHINE=imx6ul-var-dart ~/var-mx6ul-mx7-yocto-jethro/sources/meta-variscite-mx6ul-mx7/scripts/var_mk_yocto_sdcard/var-create-yocto-sdcard.sh <options> /dev/sdX
(Replace /dev/sdX with your actual device)
options:
  -h            Display help message
  -s            Only show partition sizes to be written, without actually write them
  -a            Automatically set the rootfs partition size to fill the SD card

If you don't use the '-a' option, a default rootfs size of 3700MiB will be used

7 Boot board with a bootable SD card

Note: Boot from SD card eliminates Wifi as the Wifi and SD card are using same SDIO interface.
A typical use-case, is to boot from SD card, flash eMMC or NAND flash, and re-boot form eMMC/NAND to have Wi-Fi operational.

7.1 Setting the Boot DIP switches

Booting your system from an SD card requires switching the Boot DIP switches. See picture below.

Boot switch 6ul1.jpg
  • "00" The current position in the picture will set the system to boot from SD card.
  • "01" Moving the right switch will set the system to boot from eMMC
  • "10" Moving the left switch will set the system to boot from NAND flash
  • "11" is illegal.

Be aware that your system has eMMC or NAND but never both.

7.2 Automatic device Tree selection in U-Boot

Upon reset you will see the U-Boot SPL printouts. It will print also the SOM configuration:
On-SOM storage: SD only, eMMC, NAND.
WIFI if chip exits.
For example:

U-Boot SPL 2015.10-00532-g482dc88 (Jan 03 2016 - 10:05:42)
i.MX6UL SOC 
Part number: DART-6U-A01
Assembly: AS11
Date of production: 2015 Dec 31
DART-6UL configuration: eMMC WIFI
Ram size: 512
Boot Device: SD

As explained in the above Build Results table we have 4 optional configurations.
We implemented in U-Boot and automatic device tree selection, so when kernel boots, the U-Boot will load the corresponding device tree according to On-SOM configuration.

Boot From
SOM Internal FLASH
SOM has WIFI/BT
Device Tree selected
SD eMMC Don't Care imx6ul-var-dart-sd_emmc.dtb
SD NAND Don't Care imx6ul-var-dart-sd_nand.dtb
eMMC eMMC Yes imx6ul-var-dart-emmc_wifi.dtb
eMMC eMMC NO imx6ul-var-dart-sd_emmc.dtb
NAND NAND YES imx6ul-var-dart-nand_wifi.dtb
NAND NAND NO imx6ul-var-dart-sd_nand.dtb

Note: Boot from SD card eliminates Wifi as the Wifi and SD card are using same SDIO interface.
A typical use-case, is to boot from SD card, flash eMMC or NAND flash, and re-boot form eMMC/NAND to have Wi-Fi operational.

7.3 Disable Automatic Device Tree selection

To disable the automatic device tree selection in U-Boot:

$ setenv var_auto_fdt_file=N
$ saveenv

Now you can set the device tree to meet your requirments. For example:

$ setenv fdt_file=imx6ul-var-dart-sd_emmc.dtb
$ saveenv

Will select device tree that has SD and eMMC regardless if the SOM has WIFI.

$ setenv fdt_file=imx6ul-var-dart-sd_nand.dtb
$ saveenv

Will select device tree that has SD and NAND regardless if the SOM has WIFI.

Comment:
Make sure you don't set am illegal value like "imx6ul-var-dart-sd_nand.dtb" in a SOM that has eMMC flash.

8 Flash images to NAND/eMMC

Please refer to DART-6UL NAND Flash Burning

9 QT5/Embedded runtime

9.1 Environment Variables

The QT5/Embedded require environment variables to run correctly. DART6Ul support QT Embedded over Linux Frame Buffer. For example /etc/profile.d/tslib.sh can be edited. The following example enable touch, mouse and keyboard:

export TSLIB_TSEVENTTYPE='INPUT'
export TSLIB_TSDEVICE='/dev/input/touchscreen0'
export TSLIB_CALIBFILE='/etc/pointercal'
export TSLIB_CONFFILE='/etc/ts.conf'
export TSLIB_CONSOLEDEVICE='none'
export TSLIB_FBDEVICE='/dev/fb0'
export TSLIB_PLUGINDIR='/usr/lib/ts'

export QT_QPA_PLATFORM=linuxfb:fb=/dev/fb0:size=800x480:mmSize=800x480
export QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS='/dev/input/touchscreen0'
export QT_QPA_GENERIC_PLUGINS='tslib:/dev/input/touchscreen0,evdevmouse:/dev/input/event5,evdevkeyboard:/dev/input/event3'

9.2 Running Application

$ cd /usr/share/qt5/examples/
$ touch/dials/dials --platform linuxfb
$ gui/rasterwindow/rasterwindow --platform linuxfb
$ touch/fingerpaint/fingerpaint  --platform linuxfb
$ widgets/mainwindows/mainwindow/mainwindow --platform linuxfb

10 Update Yocto Jethro Meta-Variscite

From time to time we will post updates to meta-variscite that will include new features and bug fixes.
Follow the instructions below to update your tree:

$ cd ~/var-mx6ul-mx7-yocto-jethro/sources/meta-variscite-mx6ul-mx7/
$ git fetch origin
$ git checkout imx_4.1.15_ga-var01
$ git pull

Setup your enviroment:
$ cd ~/var-mx6ul-mx7-yocto-jethro
$ MACHINE=imx6ul-var-dart DISTRO=fsl-imx-x11 source var-setup-release.sh -b build_x11
In order to update the kernel and U-Boot:
$ bitbake -c cleanall fsl-image-gui u-boot-variscite linux-variscite cryptodev-module
and build your image:
$ bitbake fsl-image-gui

11 Useful Bitbake commands

Bitbake Cheat Sheet

Useful bitbake commands

i.MX Yocto Project: ltib versus bitbake