Personal tools

Difference between revisions of "1-1-1-1-2-1-10"

From ICOP tech wiki

Jump to: navigation, search
(Created page with " <div id="column-content"> <div id="content"> <a id="top"></a> <h1 id="firstHeading" class="firstHeading">Yocto NAND Flash Burning</h1> <div id="bodyConten...")
 
 
Line 1: Line 1:
<div id="column-content">
+
<!-- Set release according to "release" parameter in URL and use MORTY_BETA_DART-6UL as default
<div id="content">
+
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!--
<a id="top"></a>
+
--> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_MORTY_BETA_DART-6UL}}}} <!--
<h1 id="firstHeading" class="firstHeading">Yocto NAND Flash Burning</h1>
+
--> {{PageHeader|Installing Yocto to the SOM's internal storage}} {{DocImage|category1={{#var:HARDWARE_NAME}}|category2=Yocto}} __toc__
<div id="bodyContent">
+
= Introduction =
<h3 id="siteSub">From Variscite Wiki</h3>
+
All SOMs can either boot from an SD card or from their internal storage.<br>
<div id="contentSub"></div>
 
<div id="jump-to-nav">Jump to: <a href="#column-one">navigation</a>, <a href="#searchInput">search</a></div> <!-- start content -->
 
<div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr"><p><br />                                                                                       
 
<span style="font-size:16pt;">Installing Yocto to the SOM's internal storage</span>
 
</p>
 
<hr /> <div id="toc" class="toc"><div id="toctitle"><h2>Contents</h2></div>
 
<ul>
 
<li class="toclevel-1 tocsection-1"><a href="#Introduction"><span class="tocnumber">1</span> <span class="toctext">Introduction</span></a></li>
 
<li class="toclevel-1 tocsection-2"><a href="#eMMC_structure"><span class="tocnumber">2</span> <span class="toctext">eMMC structure</span></a></li>
 
<li class="toclevel-1 tocsection-3"><a href="#Installing_the_Yocto_binaries"><span class="tocnumber">3</span> <span class="toctext">Installing the Yocto binaries</span></a>
 
<ul>
 
<li class="toclevel-2 tocsection-4"><a href="#Images_locations"><span class="tocnumber">3.1</span> <span class="toctext">Images locations</span></a>
 
<ul>
 
<li class="toclevel-3"><a href="#Prepare_the_images_for_flashing_to_eMMC"><span class="tocnumber">3.1.1</span> <span class="toctext">Prepare the images for flashing to eMMC</span></a></li>
 
</ul>
 
</li>
 
<li class="toclevel-2 tocsection-7"><a href="#Flashing_scripts"><span class="tocnumber">3.2</span> <span class="toctext">Flashing scripts</span></a></li>
 
<li class="toclevel-2 tocsection-9"><a href="#Manual_step-by-step_flashing_to_eMMC"><span class="tocnumber">3.3</span> <span class="toctext">Manual step-by-step flashing to eMMC</span></a></li>
 
</ul>
 
</li>
 
<li class="toclevel-1 tocsection-10"><a href="#Summary"><span class="tocnumber">4</span> <span class="toctext">Summary</span></a></li>
 
</ul>
 
</div>
 
 
 
<h1><span class="mw-headline" id="Introduction"><span class="mw-headline-number">1</span> Introduction</span></h1>
 
<p>All SOMs can either boot from an SD card or from their internal storage.<br>
 
 
<br>
 
<br>
 
The SOM's internal storage:<br>
 
The SOM's internal storage:<br>
The Variscite DART-MX8M-MINI comes with eMMC, which holds U-Boot, the kernel image and the ext4 root file system.<br>
+
{{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX6 |
</p><p><br />
+
* '''VAR-SOM-MX6 and VAR-SOM-SOLO/DUAL''' SOMs use the on-SOM NAND flash to boot.<br>
</p>
+
The file system can reside either on the NAND flash or the eMMC.<br>
<h1><span class="mw-headline" id="eMMC_structure"><span class="mw-headline-number">2</span> eMMC structure</span></h1>
+
When the file system resides on the NAND flash, a UBIFS file system is used.<br>
<p>0-8 MiB &#160;&#160;&#160;&#160;&#160;: Non-partitioned space, saved for U-Boot.<br>
+
When the file system resides on the eMMC, an ext4 file system is used.<br>
 +
Regardless of the file system type and location, U-Boot will always boot from the NAND flash.<br>
 +
By default, the kernel image and device tree blob are also written to the NAND flash (again, regardless of the file system type and location).
 +
* '''VAR-DART-MX6''' has only an on-SOM eMMC which can be used to boot from and to hold the filesystem.
 +
|
 +
{{#ifeq: {{#var:SOC_SERIES}} | imx8 |
 +
The Variscite {{#var:HARDWARE_NAME}} comes with eMMC, which holds U-Boot, the kernel image and the ext4 root file system.<br>
 +
|
 +
The Variscite {{#var:HARDWARE_NAME}} has either an on-SOM NAND flash or eMMC, and either of them can be used to boot from and to hold the file system.<br>
 +
For NAND flash we use a UBI file system and for eMMC we use ext4.
 +
}}
 +
}}
 +
 
 +
{{#ifeq: {{#var:SOC_SERIES}} | imx8 |
 +
|
 +
= NAND flash structure =
 +
{{#ifeq: {{#var:MACHINE_NAME}} | var-som-mx6 |* '''VAR-SOM-MX6 and VAR-SOM-SOLO/DUAL'''
 +
These are the defined MTD partitions on the NAND flash:<br>
 +
0x000000000000-0x000000200000 : "spl"<br>
 +
0x000000200000-0x000000400000 : "bootloader"<br>
 +
0x000000400000-0x000000c00000 : "kernel"'''<br>
 +
0x000000c00000-End &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : "rootfs"
 +
|
 +
0x000000000000-0x000000200000 : "spl"<br>
 +
0x000000200000-0x000000400000 : "u-boot"<br>
 +
0x000000400000-0x000000600000 : "u-boot_env"<br>
 +
0x000000600000-0x000000e00000 : "kernel"<br>
 +
0x000000e00000-End &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : "rootfs"<br>}}
 +
}}
 +
 
 +
= eMMC structure =
 +
{{#ifeq: {{#var:SOC_SERIES}} | imx8 |
 +
0-8 MiB &nbsp;&nbsp;&nbsp;&nbsp; : Non-partitioned space, saved for U-Boot.<br>
 
8 MiB-End: "rootfs" - An ext4 partition containing the root file system (including Linux image and the device tree blobs under /boot).
 
8 MiB-End: "rootfs" - An ext4 partition containing the root file system (including Linux image and the device tree blobs under /boot).
</p><p><br />
+
|
</p>
+
{{#ifeq: {{#var:MACHINE_NAME}} | var-som-mx6 |* '''VAR-SOM-MX6 and VAR-SOM-SOLO/DUAL'''
<h1><span class="mw-headline" id="Installing_the_Yocto_binaries"><span class="mw-headline-number">3</span> Installing the Yocto binaries</span></h1>
+
0 MiB-End: "rootfs" - An ext4 partition containing the root file system (including the kernel modules).
<p>If you followed the <a href="/index.php?title=Yocto_Build_Release#Create_an_extended_SD_card" title="Yocto Build Release">Create an extended SD card</a> steps, the <a href="#Images_locations">Yocto binaries</a> and the <a href="#Flashing_scripts">flashing scripts</a> will be included in your SD card. <br>
+
* '''VAR-DART-MX6'''|}}
 +
0-4 MiB &nbsp;&nbsp;&nbsp;&nbsp; : Non-partitioned space, saved for U-Boot.<br>
 +
4-12 MiB &nbsp;&nbsp; : {{#var:EMMC_FAT_PARTITION_NAME}} - A FAT16 partition containing the Linux image and the device tree blob/s.<br>
 +
12 MiB-End: "rootfs" - An ext4 partition containing the root file system (including the kernel modules).}}
 +
 
 +
{{#ifeq: {{#var:SOC_SERIES}} | imx8 |
 +
|
 +
= Yocto Built binaries for NAND flash / eMMC =
 +
 
 +
The resulting images are located at tmp/deploy/images/{{#var:MACHINE_NAME}}.<br>
 +
{{#lst:Yocto_Build_Release|YOCTO_BUILD_RESULTS}}
 +
{{#lst:Yocto_Platform_Customization|{{#var:YOCTO_BUILD_RESULTS_SECTION}}}}
 +
}}
 +
 
 +
= Installing the Yocto binaries =
 +
If you followed the [[Yocto_Build_Release#Create an extended SD card |Create an extended SD card]] steps, the [[#Images locations|Yocto binaries]] and the [[#Flashing scripts|flashing scripts]] will be included in your SD card. <br>
 
The flashing scripts are easy-to-use example scripts for flashing images into NAND flash / eMMC.<br>
 
The flashing scripts are easy-to-use example scripts for flashing images into NAND flash / eMMC.<br>
There is also a section below describing how to <a href="#Manual_step-by-step_flashing_to_NAND_flash_.2F_eMMC">flash the images manually</a>.
+
There is also a section below describing how to [[#Manual step-by-step flashing to NAND flash / eMMC|flash the images manually]].
</p>
+
 
<h2><span class="mw-headline" id="Images_locations"><span class="mw-headline-number">3.1</span> Images locations</span></h2>
+
== Images locations ==
<p>Following is the directory structure on your SD card, which elaborates the files' location that the below installation scripts are expecting:
+
Following is the directory structure on your SD card, which elaborates the files' location that the below installation scripts are expecting:
</p>
+
{{#lst:Yocto_Platform_Customization|{{#var:SD_TREE_SECTION}}}}
<pre>
 
/opt/images/
 
└── Yocto
 
    ├── imx-boot-sd.bin
 
    └── rootfs.tar.gz
 
  
</pre>
+
{{#ifeq: {{#var:SOC_SERIES}} | imx8 |
<p><br />
+
=== Prepare the images for flashing to eMMC ===
</p>
+
|
<h3><span class="mw-headline" id="Prepare_the_images_for_flashing_to_eMMC"><span class="mw-headline-number">3.1.1</span> Prepare the images for flashing to eMMC</span></h3>
+
=== Prepare the images for NAND flash / eMMC flashing ===
<p>Plug the bootable SD card into your host machine and mount the rootfs partition - here we assume it is mounted on /media/rootfs.<br>
+
}}
 +
Plug the bootable SD card into your host machine and mount the rootfs partition - here we assume it is mounted on /media/rootfs.<br>
 
Copy all the mentioned yocto-built binaries to the SD card:
 
Copy all the mentioned yocto-built binaries to the SD card:
 
<br>
 
<br>
</p>
+
* <span style="color:red">Note:</span> If you followed the [[Yocto_Build_Release#Create an extended SD card |Create an extended SD card]] steps, the [[#Flashing scripts|flashing scripts]] and all relevant binaries are already included in your SD card, and the below commands are redundant!<br>
<ul>
+
 
<li> <span style="color:red">Note:</span> If you followed the <a href="/index.php?title=Yocto_Build_Release#Create_an_extended_SD_card" title="Yocto Build Release">Create an extended SD card</a> steps, the <a href="#Flashing_scripts">flashing scripts</a> and all relevant binaries are already included in your SD card, and the below commands are redundant!<br>
+
Setup:
</li>
+
$ export YOCTO_IMGS_PATH={{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_X11}}/tmp/deploy/images/{{#var:MACHINE_NAME}}
</ul>
+
$ export P2_MOUNT_DIR=/media/rootfs/
<p>Setup:
+
$ sudo mkdir -p ${P2_MOUNT_DIR}/opt/images/Yocto/
</p>
+
 
<pre>$ export YOCTO_IMGS_PATH=~/var-fsl-yocto//tmp/deploy/images/imx8mm-var-dart
+
{{#ifeq: {{#var:SOC_SERIES}} | imx8 ||
$ export P2_MOUNT_DIR=/media/rootfs/
 
$ sudo mkdir -p ${P2_MOUNT_DIR}/opt/images/Yocto/
 
</pre>
 
<p>{{#ifeq: imx8 | imx8 ||
 
 
Linux:
 
Linux:
</p>
+
$ sudo cp ${YOCTO_IMGS_PATH}/{{#var:KERNEL_IMAGE}} ${P2_MOUNT_DIR}/opt/images/Yocto/
<pre>$ sudo cp ${YOCTO_IMGS_PATH}/Image.gz ${P2_MOUNT_DIR}/opt/images/Yocto/
+
 
 +
Device Tree:
 +
$ for f in ${YOCTO_IMGS_PATH}/*.dtb; do if <nowiki>[[ -L $f ]] && [[</nowiki> $f != *{{#var:MACHINE_NAME}}.dtb <nowiki>]]</nowiki>; then sudo cp $f ${P2_MOUNT_DIR}/opt/images/Yocto/; fi done
 +
$ sudo rename 's/{{#var:KERNEL_IMAGE}}-imx/imx/' ${P2_MOUNT_DIR}/opt/images/Yocto/*.dtb
 +
 
 +
 
 +
{{#ifeq: {{#var:SOC_SERIES}} | imx8 ||
 +
NAND images:
 +
{{#ifeq: {{#var:SPL_SD_IMAGE_NAME}} | N/A ||SPL:
 +
$ sudo cp ${YOCTO_IMGS_PATH}/{{#var:SPL_NAND_IMAGE_NAME}} ${P2_MOUNT_DIR}/opt/images/Yocto/
 +
}}
 +
 +
U-Boot:
 +
$ sudo cp ${YOCTO_IMGS_PATH}/{{#var:U-BOOT_NAND_IMAGE_NAME}} ${P2_MOUNT_DIR}/opt/images/Yocto/
 +
 +
File System:
 +
$ sudo cp ${YOCTO_IMGS_PATH}/fsl-image-gui-{{#var:MACHINE_NAME}}.ubi ${P2_MOUNT_DIR}/opt/images/Yocto/rootfs.ubi
 +
}}
 +
eMMC images:
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|*'''VAR-SOM-MX6 and VAR-SOM-SOLO/DUAL'''
 +
File System:
 +
$ sudo cp ${YOCTO_IMGS_PATH}/fsl-image-gui-{{#var:MACHINE_NAME}}.tar.gz ${P2_MOUNT_DIR}/opt/images/Yocto/rootfs.tar.gz
 +
|}} <!--
 +
 
 +
-->{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|*'''DART-MX6'''|}}
 +
{{#ifeq: {{#var:SPL_SD_IMAGE_NAME}} | N/A ||SPL:
 +
$ sudo cp ${YOCTO_IMGS_PATH}/{{#var:SPL_SD_IMAGE_NAME}} ${P2_MOUNT_DIR}/opt/images/Yocto/
 +
|}}
 +
 
 +
{{#ifeq: {{#var:SOC_SERIES}} | imx8 |
 +
<br>
 +
U-Boot:
 +
$ sudo cp ${YOCTO_IMGS_PATH}/imx-boot-{{#var:MACHINE_NAME}}-sd.bin ${P2_MOUNT_DIR}/opt/images/Yocto/{{#var:U-BOOT_SD_IMAGE_NAME}}
 +
 +
File System:
 +
$ sudo cp ${YOCTO_IMGS_PATH}/fsl-image-gui-{{#var:MACHINE_NAME}}.tar.gz ${P2_MOUNT_DIR}/opt/images/Yocto/rootfs.tar.gz
 +
|
 +
<br>
 +
U-Boot:
 +
$ sudo cp ${YOCTO_IMGS_PATH}/{{#var:U-BOOT_SD_IMAGE_NAME}} ${P2_MOUNT_DIR}/opt/images/Yocto/
 +
 +
File System:
 +
$ sudo cp ${YOCTO_IMGS_PATH}/fsl-image-gui-{{#var:MACHINE_NAME}}.tar.gz ${P2_MOUNT_DIR}/opt/images/Yocto/rootfs.tar.gz
 +
}}
 +
 
 +
== Flashing scripts ==
 +
The flashing scripts are located on the SD card at /usr/bin/:
 +
 
 +
{{#ifeq: {{#var:SOC_SERIES}} | imx8 |
 +
install_yocto.sh - Flash Yocto into eMMC (Run and follow usage instructions)
 +
|
 +
install_yocto.sh - Flash Yocto into NAND flash or eMMC (Run and follow usage instructions)
 +
}}
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|
 +
(install_yocto_emmc.sh - This script is being called by install_yocto.sh when choosing to install the rootfs to eMMC - it should not be called directly!)
 +
|}}
 +
 
 +
{{#ifeq: {{#var:SOC_SERIES}} | imx8 |
 +
|
 +
== Manual step-by-step flashing to NAND flash ==
 +
 
 +
Use the prepared SD card to boot the board and run the following:
 +
<br>
 +
<pre>
 +
$ cd /opt/images/Yocto
 
</pre>
 
</pre>
<p>Device Tree:
 
</p>
 
<pre>$ for f in ${YOCTO_IMGS_PATH}/*.dtb; do if [[ -L $f ]] &amp;&amp; [[ $f&#160;!= *imx8mm-var-dart.dtb ]]; then sudo cp $f ${P2_MOUNT_DIR}/opt/images/Yocto/; fi done
 
$ sudo rename 's/Image.gz-imx/imx/' ${P2_MOUNT_DIR}/opt/images/Yocto/*.dtb
 
</pre>
 
<p><br />
 
</p><p>eMMC images:
 
</p><p><br />
 
</p><p><br>
 
</p>
 
<pre>U-Boot:
 
$ sudo cp ${YOCTO_IMGS_PATH}/imx-boot-imx8mm-var-dart-sd.bin ${P2_MOUNT_DIR}/opt/images/Yocto/imx-boot-sd.bin
 
  
File System:
+
{{#ifeq: {{#var:SPL_NAND_IMAGE_NAME}} | N/A |Flash U-Boot:| Flash SPL & U-Boot:}}
$ sudo cp ${YOCTO_IMGS_PATH}/fsl-image-gui-imx8mm-var-dart.tar.gz ${P2_MOUNT_DIR}/opt/images/Yocto/rootfs.tar.gz
+
 
</pre>
+
$ flash_erase /dev/mtd0 0 0
<h2><span class="mw-headline" id="Flashing_scripts"><span class="mw-headline-number">3.2</span> Flashing scripts</span></h2>
+
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|
<p>The flashing scripts are located on the SD card at /usr/bin/:
+
$ kobs-ng init -x {{#var:SPL_NAND_IMAGE_NAME}} --search_exponent=1 -v
</p>
+
$ flash_erase /dev/mtd1 0 0
<pre>install_yocto.sh - Flash Yocto into eMMC (Run and follow usage instructions)
+
$ nandwrite -p /dev/mtd1 {{#var:U-BOOT_NAND_IMAGE_NAME}}
 +
|
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|DART-6UL|
 +
$ kobs-ng init -x {{#var:SPL_NAND_IMAGE_NAME}} --search_exponent=1 -v
 +
$ flash_erase /dev/mtd1 0 0
 +
$ nandwrite -p /dev/mtd1 {{#var:U-BOOT_NAND_IMAGE_NAME}}
 +
$ flash_erase /dev/mtd2 0 0
 +
|}}
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX7|
 +
{{#ifeq: {{#var:SPL_NAND_IMAGE_NAME}} | N/A |
 +
$ kobs-ng init -x {{#var:U-BOOT_NAND_IMAGE_NAME}} --search_exponent=1 -v
 +
|
 +
$ kobs-ng init -x {{#var:SPL_NAND_IMAGE_NAME}} --search_exponent=1 -v
 +
$ flash_erase /dev/mtd1 0 0
 +
$ nandwrite -p /dev/mtd1 {{#var:U-BOOT_NAND_IMAGE_NAME}}
 +
}}
 +
$ flash_erase /dev/mtd2 0 0
 +
|}}
 +
}}
 +
 
 +
Flash the Linux Kernel image & Device Tree:<br>
 +
You need to use the right .dtb file for you hardware setup. See the [[#Yocto Built binaries for NAND flash / eMMC | table]] above for a complete description.
 +
 
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|
 +
$ flash_erase /dev/mtd2 0 0
 +
$ nandwrite -p /dev/mtd2 {{#var:KERNEL_IMAGE}}
 +
$ nandwrite -p /dev/mtd1 -s 0x1e0000 <DEVICE_TREE_FILE>
 +
|
 +
$ flash_erase /dev/mtd3 0 0
 +
$ nandwrite -p /dev/mtd3 {{#var:KERNEL_IMAGE}}
 +
$ nandwrite -p /dev/mtd3 -s 0x7e0000 <DEVICE_TREE_FILE>
 +
}}
 +
 
 +
Flash the (UBI) File System to NAND flash:
 +
 
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|
 +
$ ubiformat /dev/mtd3 -f rootfs.ubi
 +
|
 +
$ ubiformat /dev/mtd4 -f rootfs.ubi
 +
}}
 +
}}
 +
 
 +
== Manual step-by-step flashing to eMMC ==
  
</pre>
+
Flashing the eMMC requires several steps including partitioning, file system formatting and image extraction.<br>
<p><br />
 
</p>
 
<h2><span class="mw-headline" id="Manual_step-by-step_flashing_to_eMMC"><span class="mw-headline-number">3.3</span> Manual step-by-step flashing to eMMC</span></h2>
 
<p>Flashing the eMMC requires several steps including partitioning, file system formatting and image extraction.<br>
 
 
We recommend to use our provided scripts to perform this task.<br><br>
 
We recommend to use our provided scripts to perform this task.<br><br>
 
Use the prepared SD card to boot the board and run the following:
 
Use the prepared SD card to boot the board and run the following:
</p>
+
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|
<pre>$ export node=/dev/mmcblk2  
+
* '''DART-MX6'''
$ cd /opt/images/Yocto
+
$ export node=/dev/mmcblk2
</pre>
+
$ cd /opt/images/Yocto
<p>Make sure the eMMC is not mounted:
+
* '''VAR-SOM-MX6 and VAR-SOM-SOLO/DUAL'''
</p>
+
}}
<pre>$ umount ${node}p*
+
$ export node=/dev/{{#var:EMMC_ROOTFS_DEV}}
</pre>
+
$ cd /opt/images/Yocto
<p>Delete current data on eMMC:
+
 
</p>
+
Make sure the eMMC is not mounted:
<pre>$ for((i=1; i&lt;=16; i++)); do [ -e ${node}p${i} ] &amp;&amp; dd if=/dev/zero of=${node}p${i} bs=1M count=1 conv=fsync; done
+
$ umount ${node}p*
$ dd if=/dev/zero of=${node} bs=1M count=8 conv=fsync
+
 
</pre>
+
{{#ifeq: {{#var:SOC_SERIES}} | imx8 |
<p>Create a partition table:
+
Delete current data on eMMC:
</p>
+
$ for((i=1; i<=16; i++)); do [ -e ${node}p${i} ] && dd if=/dev/zero of=${node}p${i} bs=1M count=1 conv=fsync; done
<pre>$ (echo n; echo p; echo 1; echo 16384; echo; echo p; echo w) | fdisk -u $node
+
$ dd if=/dev/zero of=${node} bs=1M count=8 conv=fsync
$ sync
+
 
</pre>
+
Create a partition table:
<p>Format the partitions:
+
$ (echo n; echo p; echo 1; echo 16384; echo; echo p; echo w) <nowiki>|</nowiki> fdisk -u $node
</p>
+
$ sync
<pre>$ mkfs.ext4 ${node}p1 -L rootfs
+
 
$ sync
+
Format the partitions:
</pre>
+
$ mkfs.ext4 ${node}p1 -L rootfs
<p>Flash U-Boot:
+
$ sync
</p>
+
 
<pre>$ dd if=imx-boot-sd.bin of=${node} bs=1K seek=33 conv=fsync
+
Flash U-Boot:
</pre>
+
$ dd if={{#var:U-BOOT_SD_IMAGE_NAME}} of=${node} bs=1K seek={{#var:U-BOOT_OFFSET}} conv=fsync
<p>Extract the rootfs archive:
+
 
</p>
+
Extract the rootfs archive:
<pre>$ mkdir /run/media/mmcblk2p1
+
$ mkdir /run/media/{{#var:EMMC_ROOTFS_DEV}}{{#var:EMMC_ROOTFS_PARTITION_NUM}}
$ mount ${node}p1 /run/media/mmcblk2p1
+
$ mount ${node}{{#var:EMMC_ROOTFS_PARTITION_NUM}} /run/media/{{#var:EMMC_ROOTFS_DEV}}{{#var:EMMC_ROOTFS_PARTITION_NUM}}
$ tar xvpf rootfs.tar.gz -C /run/media/mmcblk2p1
+
$ tar xvpf rootfs.tar.gz -C /run/media/{{#var:EMMC_ROOTFS_DEV}}{{#var:EMMC_ROOTFS_PARTITION_NUM}}
 +
{{#ifeq: {{#var:HARDWARE_NAME}} | DART-MX8M |$ (cd /run/media/{{#var:EMMC_ROOTFS_DEV}}{{#var:EMMC_ROOTFS_PARTITION_NUM}}/boot; ln -fs {{#var:DEFAULT_DTB_EMMC}} {{#var:DEFAULT_DTB}})|}}
 +
$ sync
 +
$ umount /run/media/{{#var:EMMC_ROOTFS_DEV}}{{#var:EMMC_ROOTFS_PARTITION_NUM}}
 +
|
 +
Delete current data on eMMC:
 +
$ dd if=/dev/zero of=${node}p1 bs=1024 count=1024
 +
$ dd if=/dev/zero of=${node}p2 bs=1024 count=1024
 +
$ dd if=/dev/zero of=${node}p3 bs=1024 count=1024
 +
$ dd if=/dev/zero of=${node}p4 bs=1024 count=1024
 +
$ dd if=/dev/zero of=${node}p5 bs=1024 count=1024
 +
$ dd if=/dev/zero of=${node}p6 bs=1024 count=1024
 +
$ dd if=/dev/zero of=${node}p7 bs=1024 count=1024
 +
$ sync
 +
$ (echo d; echo 1; echo d; echo 2; echo d; echo 3; echo d; echo w) <nowiki>|</nowiki> fdisk ${node}
 +
$ sync
 +
$ dd if=/dev/zero of=${node} bs=1M count=4
 +
$ sync
 +
 
 +
Create a partition table:
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|
 +
* '''VAR-SOM-MX6 and  VAR-SOM-SOLO/DUAL'''
 +
$ (echo n; echo p; echo 1; echo; echo; echo p; echo w) <nowiki>|</nowiki> fdisk -u ${node}
 +
$ sync
 +
* '''DART-MX6'''
 +
}}
 +
$(echo n; echo p; echo 1; echo 8192; echo 24575; echo t; echo c; \
 +
  echo n; echo p; echo 2; echo 24576; echo; \
 +
  echo p; echo w) <nowiki>|</nowiki> fdisk -u ${node}
 +
$ sync
 +
 
 +
Format the partitions:
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|
 +
* '''VAR-SOM-MX6 and  VAR-SOM-SOLO/DUAL'''
 +
$ mkfs.ext4 ${node}p1 -L rootfs
 +
* '''DART-MX6'''
 +
}}
 +
$ mkfs.vfat ${node}p1 -n {{#var:EMMC_FAT_PARTITION_NAME}}
 +
$ mkfs.ext4 ${node}p2 -L rootfs
 +
 
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX7|
 +
{{#ifeq: {{#var:SPL_SD_IMAGE_NAME}} | N/A |
 +
Flash U-Boot to eMMC:
 +
$ dd if={{#var:U-BOOT_SD_IMAGE_NAME}} of=${node} bs=1K seek=1; sync
 +
|
 +
Flash SPL and U-Boot to eMMC:
 +
$ dd if={{#var:SPL_SD_IMAGE_NAME}} of=${node} bs=1K seek=1; sync
 +
$ dd if={{#var:U-BOOT_SD_IMAGE_NAME}} of=${node} bs=1K seek=69; sync
 +
}}
 +
}}
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|DART-6UL|
 +
Flash SPL and U-Boot to eMMC:
 +
$ dd if={{#var:SPL_SD_IMAGE_NAME}} of=${node} bs=1K seek=1; sync
 +
$ dd if={{#var:U-BOOT_SD_IMAGE_NAME}} of=${node} bs=1K seek=69; sync
 +
}}
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|
 +
Flash SPL and U-Boot to eMMC:
 +
* '''DART-MX6 only'''
 +
$ dd if={{#var:SPL_SD_IMAGE_NAME}} of=${node} bs=1K seek=1; sync
 +
$ dd if={{#var:U-BOOT_SD_IMAGE_NAME}} of=${node} bs=1K seek=69; sync
 +
}}
 +
 
 +
Copy the Linux kernel image and the device tree blobs to the BOOT partition:
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|
 +
* '''DART-MX6 only'''
 +
}}
 +
$ mkdir /run/media/{{#var:EMMC_ROOTFS_DEV}}p1
 +
$ mount -t vfat ${node}p1 /run/media/{{#var:EMMC_ROOTFS_DEV}}p1/
 +
$ cp *emmc*.dtb /run/media/{{#var:EMMC_ROOTFS_DEV}}p1/
 +
$ cp {{#var:KERNEL_IMAGE}} /run/media/{{#var:EMMC_ROOTFS_DEV}}p1/
 +
$ sync
 +
$ umount /run/media/{{#var:EMMC_ROOTFS_DEV}}p1
 +
 +
Extract the rootfs archive:
 +
$ mkdir /run/media/{{#var:EMMC_ROOTFS_DEV}}{{#var:EMMC_ROOTFS_PARTITION_NUM}}
 +
$ mount ${node}{{#var:EMMC_ROOTFS_PARTITION_NUM}} /run/media/{{#var:EMMC_ROOTFS_DEV}}{{#var:EMMC_ROOTFS_PARTITION_NUM}}
 +
$ tar xvpf rootfs.tar.gz -C /run/media/{{#var:EMMC_ROOTFS_DEV}}{{#var:EMMC_ROOTFS_PARTITION_NUM}}
 +
$ sync
 +
$ umount /run/media/{{#var:EMMC_ROOTFS_DEV}}{{#var:EMMC_ROOTFS_PARTITION_NUM}}
 +
}}
 +
 
 +
{{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX6|
 +
Set the U-Boot env. variable "rootfs_device" to "emmc" by one of the following two methods:
 +
* '''VAR-SOM-MX6 and  VAR-SOM-SOLO/DUAL only'''
 +
$ fw_setenv rootfs_device emmc
 +
(A "Warning: Bad CRC, using default environment" message is expected, since this is the first write of the U-Boot environment to the NAND flash)
 +
 +
or:
 +
Reboot and stop at the U-Boot command line, and enter the following:
 +
=> setenv rootfs_device emmc
 +
=> saveenv
 +
|}}
  
$ sync
+
= Summary =
$ umount /run/media/mmcblk2p1
+
We described the results of a Yocto build, how to copy it to a bootable SD card and how to flash it to NAND and eMMC.<br>
</pre>
 
<p><br />
 
</p>
 
<h1><span class="mw-headline" id="Summary"><span class="mw-headline-number">4</span> Summary</span></h1>
 
<p>We described the results of a Yocto build, how to copy it to a bootable SD card and how to flash it to NAND and eMMC.<br>
 
 
With our extended SD card and our recovery SD card we provide an installation script located at /usr/bin/install_yocto.sh. It is much safer to use it instead of flashing the system manually.<br>
 
With our extended SD card and our recovery SD card we provide an installation script located at /usr/bin/install_yocto.sh. It is much safer to use it instead of flashing the system manually.<br>
</p>
 

Latest revision as of 15:06, 10 March 2020

Installing Yocto to the SOM's internal storage


Introduction

All SOMs can either boot from an SD card or from their internal storage.

The SOM's internal storage:
The Variscite DART-6UL has either an on-SOM NAND flash or eMMC, and either of them can be used to boot from and to hold the file system.
For NAND flash we use a UBI file system and for eMMC we use ext4.

NAND flash structure

0x000000000000-0x000000200000 : "spl"
0x000000200000-0x000000400000 : "u-boot"
0x000000400000-0x000000600000 : "u-boot_env"
0x000000600000-0x000000e00000 : "kernel"
0x000000e00000-End                       : "rootfs"

eMMC structure

0-4 MiB      : Non-partitioned space, saved for U-Boot.
4-12 MiB    : BOOT-VAR6UL - A FAT16 partition containing the Linux image and the device tree blob/s.
12 MiB-End: "rootfs" - An ext4 partition containing the root file system (including the kernel modules).

Yocto Built binaries for NAND flash / eMMC

The resulting images are located at 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 that can then be used to boot your system,
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 the Create a bootable SD card section below.
fsl-image-gui-imx6ul-var-dart.tar.gz Tarball with rootfs files.
Can be used to create an NFS root file system on the host.
See the Yocto Setup TFTP/NFS section for more info.
Also used to create our extended SD card.
See the Create a bootable SD card section below.
fsl-image-gui-imx6ul-var-dart.ubi A complete UBI image containing a UBIFS volume, for writing to NAND flash.
zImage Linux kernel image, same binary for SD card/eMMC or NAND flash.
SPL-sd SPL built for SD card boot or eMMC boot.
SPL-nand SPL built for NAND flash.
u-boot.img-sd U-Boot built for SD card boot or eMMC boot.
u-boot.img-nand U-Boot built for NAND flash.
File Name Description
zImage-imx6ul-var-dart-emmc_wifi.dtb Device tree blob for DART-6UL with eMMC & WI-FI enabled. (SD card & NAND disabled)
zImage-imx6ul-var-dart-nand_wifi.dtb Device tree blob for DART-6UL with NAND flash & WI-FI enabled. (SD card & eMMC disabled)
zImage-imx6ul-var-dart-sd_emmc.dtb Device tree blob for DART-6UL with SD card & eMMC enabled (WIFI & NAND disabled)
zImage-imx6ul-var-dart-sd_nand.dtb Device tree blob for DART-6UL with SD card & NAND flash enabled (WIFI & eMMC disabled)
zImage-imx6ull-var-dart-emmc_wifi.dtb Device tree blob for DART-6ULL with eMMC & WI-FI enabled. (SD card & NAND disabled)
zImage-imx6ull-var-dart-nand_wifi.dtb Device tree blob for DART-6ULL with NAND flash & WI-FI enabled. (SD card & eMMC disabled)
zImage-imx6ull-var-dart-sd_emmc.dtb Device tree blob for DART-6ULL with SD card & eMMC enabled (WIFI & NAND disabled)
zImage-imx6ull-var-dart-sd_nand.dtb Device tree blob for DART-6ULL with SD card & NAND flash enabled (WIFI & eMMC disabled)

Installing the Yocto binaries

If you followed the Create an extended SD card steps, the Yocto binaries and the flashing scripts will be included in your SD card.
The flashing scripts are easy-to-use example scripts for flashing images into NAND flash / eMMC.
There is also a section below describing how to flash the images manually.

Images locations

Following is the directory structure on your SD card, which elaborates the files' location that the below installation scripts are expecting:

/opt/images/
└── Yocto
    ├── imx6ul-var-dart-emmc_wifi.dtb
    ├── imx6ul-var-dart-nand_wifi.dtb
    ├── imx6ul-var-dart-sd_emmc.dtb
    ├── imx6ul-var-dart-sd_nand.dtb
    ├── imx6ull-var-dart-emmc_wifi.dtb
    ├── imx6ull-var-dart-nand_wifi.dtb
    ├── imx6ull-var-dart-sd_emmc.dtb
    ├── imx6ull-var-dart-sd_nand.dtb
    ├── rootfs.tar.gz
    ├── rootfs.ubi
    ├── SPL-nand
    ├── SPL-sd
    ├── u-boot.img-nand
    ├── u-boot.img-sd
    └── zImage


Prepare the images for NAND flash / eMMC flashing

Plug the bootable SD card into your host machine and mount the rootfs partition - here we assume it is mounted on /media/rootfs.
Copy all the mentioned yocto-built binaries to the SD card:

Setup:

$ export YOCTO_IMGS_PATH=~/var-fslc-yocto/build_x11/tmp/deploy/images/imx6ul-var-dart
$ export P2_MOUNT_DIR=/media/rootfs/
$ sudo mkdir -p ${P2_MOUNT_DIR}/opt/images/Yocto/

{{#ifeq: | imx8 || Linux:

$ sudo cp ${YOCTO_IMGS_PATH}/zImage ${P2_MOUNT_DIR}/opt/images/Yocto/

Device Tree:

$ for f in ${YOCTO_IMGS_PATH}/*.dtb; do if [[ -L $f ]] && [[ $f != *imx6ul-var-dart.dtb ]]; then sudo cp $f ${P2_MOUNT_DIR}/opt/images/Yocto/; fi done
$ sudo rename 's/zImage-imx/imx/' ${P2_MOUNT_DIR}/opt/images/Yocto/*.dtb


NAND images:

SPL:
$ sudo cp ${YOCTO_IMGS_PATH}/SPL-nand ${P2_MOUNT_DIR}/opt/images/Yocto/

U-Boot:
$ sudo cp ${YOCTO_IMGS_PATH}/u-boot.img-nand ${P2_MOUNT_DIR}/opt/images/Yocto/

File System:
$ sudo cp ${YOCTO_IMGS_PATH}/fsl-image-gui-imx6ul-var-dart.ubi ${P2_MOUNT_DIR}/opt/images/Yocto/rootfs.ubi

eMMC images:

SPL:
$ sudo cp ${YOCTO_IMGS_PATH}/SPL-sd ${P2_MOUNT_DIR}/opt/images/Yocto/


U-Boot: 
$ sudo cp ${YOCTO_IMGS_PATH}/u-boot.img-sd ${P2_MOUNT_DIR}/opt/images/Yocto/

File System:
$ sudo cp ${YOCTO_IMGS_PATH}/fsl-image-gui-imx6ul-var-dart.tar.gz ${P2_MOUNT_DIR}/opt/images/Yocto/rootfs.tar.gz

Flashing scripts

The flashing scripts are located on the SD card at /usr/bin/:

install_yocto.sh	- Flash Yocto into NAND flash or eMMC (Run and follow usage instructions)

Manual step-by-step flashing to NAND flash

Use the prepared SD card to boot the board and run the following:

$ cd /opt/images/Yocto

Flash SPL & U-Boot:

$ flash_erase /dev/mtd0 0 0
$ kobs-ng init -x SPL-nand --search_exponent=1 -v
$ flash_erase /dev/mtd1 0 0
$ nandwrite -p /dev/mtd1 u-boot.img-nand
$ flash_erase /dev/mtd2 0 0

Flash the Linux Kernel image & Device Tree:
You need to use the right .dtb file for you hardware setup. See the table above for a complete description.

$ flash_erase /dev/mtd3 0 0
$ nandwrite -p /dev/mtd3 zImage
$ nandwrite -p /dev/mtd3 -s 0x7e0000 <DEVICE_TREE_FILE>

Flash the (UBI) File System to NAND flash:

$ ubiformat /dev/mtd4 -f rootfs.ubi

Manual step-by-step flashing to eMMC

Flashing the eMMC requires several steps including partitioning, file system formatting and image extraction.
We recommend to use our provided scripts to perform this task.

Use the prepared SD card to boot the board and run the following:

$ export node=/dev/mmcblk1 
$ cd /opt/images/Yocto

Make sure the eMMC is not mounted:

$ umount ${node}p*

Delete current data on eMMC:

$ dd if=/dev/zero of=${node}p1 bs=1024 count=1024
$ dd if=/dev/zero of=${node}p2 bs=1024 count=1024
$ dd if=/dev/zero of=${node}p3 bs=1024 count=1024
$ dd if=/dev/zero of=${node}p4 bs=1024 count=1024
$ dd if=/dev/zero of=${node}p5 bs=1024 count=1024
$ dd if=/dev/zero of=${node}p6 bs=1024 count=1024
$ dd if=/dev/zero of=${node}p7 bs=1024 count=1024
$ sync
$ (echo d; echo 1; echo d; echo 2; echo d; echo 3; echo d; echo w) | fdisk ${node}
$ sync
$ dd if=/dev/zero of=${node} bs=1M count=4
$ sync

Create a partition table:

$(echo n; echo p; echo 1; echo 8192; echo 24575; echo t; echo c; \
  echo n; echo p; echo 2; echo 24576; echo; \
  echo p; echo w) | fdisk -u ${node}
$ sync

Format the partitions:

$ mkfs.vfat ${node}p1 -n BOOT-VAR6UL
$ mkfs.ext4 ${node}p2 -L rootfs


Flash SPL and U-Boot to eMMC:

$ dd if=SPL-sd of=${node} bs=1K seek=1; sync
$ dd if=u-boot.img-sd of=${node} bs=1K seek=69; sync


Copy the Linux kernel image and the device tree blobs to the BOOT partition:

$ mkdir /run/media/mmcblk1p1
$ mount -t vfat ${node}p1	/run/media/mmcblk1p1/
$ cp *emmc*.dtb			/run/media/mmcblk1p1/
$ cp zImage			/run/media/mmcblk1p1/
$ sync
$ umount /run/media/mmcblk1p1

Extract the rootfs archive:

$ mkdir /run/media/mmcblk1p2
$ mount ${node}p2 /run/media/mmcblk1p2
$ tar xvpf rootfs.tar.gz -C /run/media/mmcblk1p2
$ sync
$ umount /run/media/mmcblk1p2


Summary

We described the results of a Yocto build, how to copy it to a bootable SD card and how to flash it to NAND and eMMC.
With our extended SD card and our recovery SD card we provide an installation script located at /usr/bin/install_yocto.sh. It is much safer to use it instead of flashing the system manually.