View source for IoTGateway/BSP/Linux/iMX6/Yocto LBV8 User Guide

{{DISPLAYTITLE:Yocto Linux BSP Ver.8 User Guide for iMX6 series}} <!--
{| align="right"
 | <span class="fck_mw_magic" _fck_mw_customtag="true" _fck_mw_tagname="TOC" _fck_mw_tagtype="c">_</span>
 |}
-->

= Getting Started =

== <span style="color:#0070c0">Conventions</span> ==

<span style="color:purple">'''${PREBUILT_IMAGE}'''</span>&nbsp;: compressed prebuilt image (*.img.gz)

<span style="color:purple">'''${CONTAINER_NAME}'''</span>&nbsp;: container name (e.g. imx6LBV8040)

<span style="color:purple">'''${BSP_TARBALL}'''</span>&nbsp;: BSP tarball (*.tgz)

<span style="color:purple">'''${BSP_HOME}'''</span>&nbsp;: home directory of the BSP

<span style="color:purple">'''${BDIR}'''</span>&nbsp;: build directory (e.g. build_x11)

<span style="color:purple">'''${MX6PROC}'''</span>&nbsp;: i.MX6 Processor

:mx6q for iMX6 Quad Core / Dual Core
:mx6dl for iMX6 Dual Lite / Solo

<span style="color:purple">'''${IMX6PROC}'''</span>&nbsp;: i.MX6 Processor

:imx6q / imx6dl

<span style="color:purple">'''${BOARD}'''</span>&nbsp;: available target boards list below

:rom5420/ / rom7421 / ubc220 / rom3420 / rom7420 / rsb4410 / rsb4411 / rsb6410 / ubcds31 / wise3310

<span style="color:purple">'''${BOARD_REV}'''</span>&nbsp;: board revision

:a1 / a2 / b1

<span style="color:purple">'''${MC}'''</span>&nbsp;: machine code combined with <span style="color:purple">'''${IMX6PROC}${BOARD}${BOARD_REV}'''</span>

:for example,

::<tt>imx6dlrom5420b1 for ROM-5420-Solo B1</tt>
::<tt>imx6dlrom7421a1 for ROM-7421-Solo A1</tt>
::<tt>imx6dlubc220a1 for UBC-220-Dual-Light A1</tt>
::<tt>imx6qprom7421a1 for ROM-7421-Dual/Quad-Plus A1</tt>
::<tt>imx6qrom3420a1 for ROM-3420-Dual/Quad A1</tt>
::<tt>imx6qrom5420a1 for ROM-5420-Dual/Quad A1</tt>
::<tt>imx6qrom5420b1 for ROM-5420-Dual/Quad B1</tt>
::<tt>imx6qrom7420a1 for ROM-7420-Dual/Quad A1</tt>
::<tt>imx6qrsb4410a1 for RSB-4410-Dual A1</tt>
::<tt>imx6qrsb4410a2 for RSB-4410-Dual A2</tt><tt></tt><br/><tt></tt>
::<tt>imx6qrsb4411a1 for RSB-4411-Dual/Quad A1</tt><tt></tt><br/>
::<tt>imx6qrsb6410a1 for RSB-6410-Dual/Quad A1</tt>
::<tt>imx6qrsb6410a2 for RSB-6410-Dual/Quad A2</tt><tt></tt>
::<tt>imx6qubcds31a1 for UBC-DS31-Dual A1</tt>
::<tt>imx6qwise3310a1 for WISE-3310-Dual A1</tt>

<span style="color:purple">'''${MEM_SIZE}'''</span>&nbsp;: memory size

:1G / 2G / 512M

<span style="color:purple">'''${SD_DEVICE}'''</span>&nbsp;: device name of SD card in Linux (e.g. /dev/sdf)

<span style="color:purple">'''${SDCARD_IMAGE}'''</span>&nbsp;: sdcard image built by bitbake (*.sdcard)

<span style="color:purple">'''${WORKSPACE}'''</span>&nbsp;:&nbsp;host workspace folders

<span style="color:purple">'''${UBOOT}'''</span>&nbsp;:u-boot version(e.g. 2016.03)

<span style="color:purple">'''${KERNEL}'''</span>&nbsp;: linux kernel version(e.g. 4.1.15)

<span style="color:purple">'''${TOOLCHAIN}'''</span>&nbsp;: toolchain installed directory(e.g. /opt/fsl-imx-x11/4.1.15-2.0.0)

debug console / serial console

:serial terminal program (e.g. minicom, putty, teraterm ...) that serial port is configured to 115200 8N1

terminal console

:terminal program (e.g. gnome-terminal, xfce4-terminal ...)

== <font color="#0070c0">Docker install and setting</font> ==

<span style="font-size:larger;">'''<span style="color:#0070c0">If you don't have docker in your system, then you can follow the below &nbsp;steps to install docker and run it first.</span>'''</span>

=== <span style="color:#0070c0">To install Docker Engine on your platform</span> ===

:Please refer to [https://docs.docker.com/engine/installation/ Docker Installation Guide] for details

=== <span style="color:#0070c0">To pull [https://hub.docker.com/r/advrisc/u12.04-imx6lbv3/ ubuntu 12.04 image from Docker Hub]&nbsp;</span> ===

:<code>$ docker pull advrisc/u12.04-imx6lbv3</code><br/>
:<code>$ docker run --name imx6LBV8200&nbsp;&nbsp;-it advrisc/u12.04-imx6lbv3 /bin/bash</code><br/>

=== To copy BSP from local filesystem to the container ===

:<code>$ docker cp '''${BSP_PACK}''' imx6LBV8200:/home/adv/&nbsp;</code>

=== <span style="color:#0070c0">To&nbsp;create&nbsp;container</span> ===

:<code>$ docker run --privileged -it --name '''${CONTAINER_NAME}'''&nbsp;-v '''${WORKSPACE}''':/home/adv/adv-release-bsp -v /dev:/dev&nbsp;advrisc/u12.04-imx6lbv3 /bin/bash</code><br/>

== <span style="color:#0070c0">Get BSP</span> ==

:You have two methods to put BSP into container created above

=== <span style="color:#0070c0">Download BSP From GitHub</span> ===

:The following example shows how to download the Advantech Yocto BSP from GitHub.

:For this example, a directory called '''adv-release-bsp''' is created for the project.

:Refer to&nbsp;[[IoTGateway/BSP/Linux/iMX6/OS_Support_List_new|IoTGateway/BSP/Linux/iMX6/OS Support List new]] , Official version "'''imx6LBV8040"&nbsp;'''is taken as&nbsp;an example&nbsp;:

 $ git config --global user.name "Your Name"
 $ git config --global user.email you@example.com
 $ mkdir adv-release-bsp
 $ sudo chown adv:adv adv-release-bsp
 $ cd adv-release-bsp
 $ repo init -u [git://github.com/ADVANTECH-Corp/adv-arm-yocto-bsp.git git://github.com/ADVANTECH-Corp/adv-arm-yocto-bsp.git] -b refs/tags/'''imx6LBV8040''' -m '''imx6LBV8040'''.xml
 $ repo sync

:If you want to get latest bsp

 $ repo init -u [git://github.com/ADVANTECH-Corp/adv-arm-yocto-bsp.git git://github.com/ADVANTECH-Corp/adv-arm-yocto-bsp.git] -b imx-4.1-krogoth
 $ repo sync

=== <span style="color:#0070c0">Copy BSP tarball to Container</span> ===

:If you have BSP tarball (eg. imx6LBV8040_2017-01-16.tgz), then you have to copy it into container.

Follow the steps below:

1.Exit container and back to local machine

 $ exit

2.Copy BSP tarball to ${WORKSPACE} , and change owner

 $ cp imx6LBV8040_2017-01-16.tgz '''${WORKSPACE}'''
 $ sudo chown adv:adv ${WORKSPACE}/imx6LBV8040_2017-01-16.tgz&nbsp;

3.Back to container

 $ docker start '''${CONTAINER_NAME}'''
 $ docker attach '''${CONTAINER_NAME}'''

4.Unpack BSP tarball

 $ tar zxvf imx6LBV8040_2017-01-16.tgz

== <span style="color:#0070c0">Downloads tarball</span> ==

:Not necessarily step

:During building &nbsp;Yocto image , it will generate downloads folder which includes all packages we need , but it usually can't fetch normally,

so we keep this downloads folder. Then we can reduce some fetch failed issue.

:If you get downloads tarball , you can copy to your '''${WORKSPACE}'''

Follow the steps below:

1.Exit container and back to local machine

 $ exit

2.Copy Downloads tarball to ${WORKSPACE} , and change owner

 $ cp downloads-2.1.tar.gz '''${WORKSPACE}'''
 $ sudo chown adv:adv ${WORKSPACE}/downloads-2.1.tar.gz&nbsp;

3.Back to container

 $ docker start '''${CONTAINER_NAME}'''
 $ docker attach '''${CONTAINER_NAME}'''

4.Unpack Downloads tarball

 $ tar zxvf downloads-2.1.tar.gz

5.make link to downloads folder

 $ cd adv-release-bsp
 $ ln -s ${WORKSPACE}/downloads_2.1 downloads

== <span style="color:#0070c0">Introducing BSP</span> ==

:The BSP is based on Yocto Project with Freescale enhanced features for i.MX6, plus specific target board features from Advantech Inc..
:The Advantech Yocto Project BSP Release directory contains a "sources" directory, which contains the recipes used to build,

one or more build directories, and a set of scripts used to set up the environment.

:The recipes used to build the project come from both the community and Advantech. The Yocto Project layers are downloaded

to the sources directory. This sets up the recipes that are used to build the project.

=== <span style="color:#0070c0">Naming Rule</span> ===

:The tarball/prebuilt image name is consist of the model name followed by "LB" or "LI" plus version number and released date.

:For example, '''BSP file name: imx6LBV8040_2017-01-16.tgz'''<br/>
:which , "LB" is acronym of <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''B'''</span>SP,<br/>
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"V8040" stands for <span style="color:#ff0000">'''V'''</span>ersion <font color="#ff0000">'''8'''</font>.<span style="color:#ff0000">'''040'''</span><nowiki>.</nowiki>






:For example, '''Yocto image name: 7421A1LIV8040_DualPlus_2017-01-16.img.gz'''<br/>
:which "7421A1" stands for <span style="color:#ff0000">'''ROM-7421 A1'''</span><br/>
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "LI" is acronym for prebuilt <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''I'''</span>mage,<br/>
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "DualPlus" means this image is fit for Dual Plus Core/Quad Plus Core.

:For example, '''Yocto image name: 3420A1LIV8050_DualQuad_2017-01-17.img.gz'''<br/>
:which "3420A1" stands for <span style="color:#ff0000">'''ROM-3420 A1'''</span><br/>
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "LI" is acronym for prebuilt <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''I'''</span>mage,<br/>
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "DualQuad" means this image is fit for Dual Core/Quad Core.

:For example, '''Yocto image name: U220A1LIV8080_DualLiteSolo_2017-02-08.img.gz'''<br/>
:which "U220A1" stands for <span style="color:#ff0000">'''UBC-220 A1'''</span><br/>
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "LI" is acronym for prebuilt <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''I'''</span>mage,<br/>
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "DualLiteSolo" means this image is fit for Dual Lite Core/Solo Core.

=== <span style="color:#0070c0">BSP Content</span> ===
<div style="margin-left:0.499cm; margin-right:0cm">The description of some important folders list below:</div><div style="margin-left:1.499cm; margin-right:0cm">'''sources/'''</div><div style="margin-left:1.998cm; margin-right:0cm">'''meta-advantech/'''&nbsp;: meta layer by Advantech</div><div style="margin-left:1.998cm; margin-right:0cm">'''meta-fsl-*/'''&nbsp;: meta layer by Freescale</div><div style="margin-left:1.499cm; margin-right:0cm">'''fsl-setup-release.sh'''&nbsp;: to create one new build environment</div><div style="margin-left:1.499cm; margin-right:0cm">'''setup-environment'''&nbsp;: to continue an exist build environment</div>
== <span style="color:#0070c0">Build Instructions</span> ==

=== <span style="color:#0070c0">To create one new build environment</span> ===

:Perform the following commands in terminal console
::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span></code>
::<code>$ MACHINE=<span style="color:#7030a0">'''${MC}'''</span> source fsl-setup-release.sh -b <span style="color:#7030a0">'''${BDIR}'''</span> -e x11</code>
:You need to read and accept the EULA.
:[[File:Accept EULA.png|RTENOTITLE]]

=== <span style="color:#0070c0">To continue an exist build environment</span> ===

:Perform the following commands in terminal console
::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span></code>
::<code>$ source setup-environment <span style="color:#7030a0">'''${BDIR}'''</span></code>

=== <span style="color:#0070c0">To build sdcard image</span> ===

:To create/continue a build environment
:Perform the following command in terminal console
::<code>$ bitbake fsl-image-qt5</code>
:The file, fsl-image-qt5-<span style="color:#7030a0">'''${MC}'''</span>.sdcard, will be located in directory, ./tmp/deploy/images/<span style="color:#7030a0">'''${MC}'''</span>, while building process finished successfully.

=== <span style="color:#0070c0">To build toolchain installer</span> ===

:To create/continue a build environment
:Perform the following command in terminal console
::<code>$ bitbake meta-toolchain-qt5</code><br/>
:The below installer will be located in the directory "./tmp/deploy/sdk".
::<tt>fsl-imx-x11-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-<span style="color:#7030a0">'''${KERNEL}'''</span>-1.1.0.sh</tt><br/>

=== <span style="color:#0070c0">To build u-boot</span> ===

:To create/continue a build environment
:Perform the following command in terminal console
::<code>$ bitbake u-boot-imx</code>
:The two files, u-boot_crc.bin & u-boot_crc.bin.crc, will be located in the directory, ./tmp/deploy/images/<span style="color:#7030a0">'''${MC}'''</span>.

=== <span style="color:#0070c0">To build linux kernel</span> ===

:To create/continue a build environment
:Perform the following command in terminal console
::to show up menuconfig
:::<code>$ bitbake linux-imx -c menuconfig</code>
::::＊ If you operate on docker images, please install tmux application before running this command.
:::::<code>$ sudo apt-get install tmux</code>
::to do build
:::<code>$ bitbake linux-imx</code>
:The two files, zImage & zImage-<span style="color:#7030a0">'''${IMX6PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD'''</span>'''<span style="color:#7030a0">_REV</span><span style="color:#7030a0">}</span>'''.dtb, will be located in the directory, ./tmp/deploy/images/<span style="color:#7030a0">'''${MC}'''</span>.

== <span style="color:#0070c0">Creating boot-up on-board flash from prebuilt image</span> ==

=== <span style="color:#0070c0">To create one boot-up SD card</span> ===

:Perform the following command in terminal console
::<code>$ gunzip -c '''<span style="color:#7030a0">${PREBUILT_IMAGE</span>''' | dd of=<span style="color:#7030a0">'''${SD_DEVICE}'''</span> bs=1M</code>
::<code># sync</code>

=== <span style="color:#0070c0">To transfer whole system to on-board flash</span> ===

:Boot up from SD card
:Perform the following commands in debug console
::<code># cd /mk_inand</code>
::<code># ./mksd-linux.sh /dev/mmcblk0</code>
:press y followed by Enter, if following message shows up:
::[[File:All data will be destroyed.png|RTENOTITLE]]
:While "[Done]" shows up means the transferring is finished.

== <span style="color:#0070c0">Creating boot-up on-board flash from built sdcard image</span> ==

=== <span style="color:#0070c0">To create one boot-up SD card</span> ===

:Perform the following commands in terminal console
::<code>$ pushd <span style="color:#7030a0">'''${BSP_HOME}'''</span>/<span style="color:#7030a0">'''${BDIR}'''</span>/tmp/deploy/images/<span style="color:#7030a0">'''${MC}'''</span></code>
::<code>$ dd if=<span style="color:#7030a0">'''${SDCARD_IMAGE}'''</span> of=<span style="color:#7030a0">'''${SD_DEVICE}'''</span> bs=1M</code>
::<code>$ sync</code>
::<code>$ popd</code>

=== <span style="color:#0070c0">To transfer whole system to on-board flash</span> ===

:Boot up from SD card
:Insert USB stick that contains <span style="color:#7030a0">'''${SDCARD_IMAGE}'''</span>, USB stick will be auto mounted to /run/media/sda1.
:Perform the following commands in debug console
::<code># umount /dev/mmcblk0p?</code>
::<code># cd /run/media/sda1</code>
::<code># dd if=<span style="color:#7030a0">'''${SDCARD_IMAGE}'''</span> of=/dev/mmcblk0 bs=4M conv=fsync</code>
::<code># P2START=$(fdisk -lu | grep mmcblk0p2 | awk '{print $2}')</code>
::<code># echo -e "d\n2\nn\np\n2\n<span style="color:#7030a0">'''${P2START}'''</span>\n\nw\n" | fdisk -u /dev/mmcblk0</code>
::<code># umount /dev/mmcblk0p2</code>
::<code># e2fsck -f -y /dev/mmcblk0p2</code>
::<code># resize2fs /dev/mmcblk0p2</code>
::<code># poweroff</code>

= Customization =

== <span style="color:#0070c0">Package addition</span> ==

=== <span style="color:#0070c0">To add tcf-agent & openssh-sftp-server</span> ===

:Navigate to the directory where fsl-image-adv.inc located
::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span>/sources/meta-advantech/recipes-fsl/images</code>
:Add following line to fsl-image-adv.inc
::<code>IMAGE_INSTALL += " tcf-agent openssh-sftp-server "</code>
:[[IoTGateway/BSP/Linux/iMX6/Yocto_LBV5_User_Guide#To_continue_an_exist_build_environment|Continue an exist build environment]] and [[IoTGateway/BSP/Linux/iMX6/Yocto_LBV5_User_Guide#To_build_sdcard_image|build sdcard image]]

=== <span style="color:#0070c0">To add chromium browser</span> ===

:Navigate to the directory where local.conf located
::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span>/<span style="color:#7030a0">'''${BDIR'''</span>'''<span style="color:#7030a0">}</span>'''/conf</code>
:Add following two lines to local.conf
::<code>CORE_IMAGE_EXTRA_INSTALL += "chromium"</code>
::<code>LICENSE_FLAGS_WHITELIST="commercial"</code>
:[[#To_continue_an_exist_build_environment|Continue an exist build environment]] and [[#To_build_sdcard_image|build sdcard image]]

== <span style="color:#0070c0">Setting up SDK</span> ==

:Please follow the section,[[IoTGateway/BSP/Linux/iMX6/Yocto_LBV5_User_Guide#To_build_toolchain_installer|<span style="color:#FF0000;">To build toolchain installer</span>]], to build one toolchain installer
:Perform the following command in terminal console
::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span>/<span style="color:#7030a0">'''${BDIR}'''</span>/tmp/deploy/sdk</code>
::<code>$ sudo ./fsl-imx-x11-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-<span style="color:#7030a0">'''${KERNEL}'''</span>-1.1.0.sh</code><br/>
:Enter new installed directory or just press <code>Enter</code> to use default directory.
:While <code>Proceed[y/n]?</code> shows up, please enter the correct one.
:Waiting for the SDK installed (while the following messages show up completely)
::[[File:Setting up sdk 3.png|RTENOTITLE]]

== <span style="color:#0070c0">Setting up cross compiling environment</span> ==

:SDK has been set up (ref.<span style="color:#FF0000;"></span>[[#Setting_up_SDK|<span style="color:#FF0000;">Setting up SDK</span>]])
:Perform the following command in terminal console
::<code>$ source <span style="color:#7030a0">'''${TOOLCHAIN}'''</span>/environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi</code>

== <span style="color:#0070c0">Building & updating u-boot manually</span> ==

:The cross compiling environment has been set up. (ref. [[#Setting_up_cross_compiling_environment|Setting up cross compiling environment]])

=== <span style="color:#0070c0">Copy BSP tarball to Container</span> ===

Refer to [http://ess-wiki.advantech.com.tw/view/IoTGateway/BSP/Linux/iMX6/Yocto_LBV8_User_Guide#Copy_BSP_tarball_to_Container <span style="color:#FF0000;">Copy_BSP_tarball_to_Container</span>] , copy u-boot tarball to ${WORKSPACE} and back to container change owner & unpack tarball

 $ sudo chown adv:adv imx6LBV8210_2017-02-20_uboot-imx6.tgz
 $ tar zxvf imx6LBV8210_2017-02-20_uboot-imx6.tgz

=== <span style="color:#0070c0">Config u-boot</span> ===

 $make '''${MX6PROC}${BOARD}${BOARD_REV}'''_'''${MEM_SIZE}'''_defconfig

eg.

 $make mx6qrsb4411a1_1G_defconfig

=== <span style="color:#0070c0">Build u-boot</span> ===

 $make -j4

=== <span style="color:#0070c0">Replace u-boot</span> ===

:Perform the following command to transfer to exist boot-up SD card

 $ dd if=u-boot_crc.bin.crc of='''${SD_DEVICE}''' bs=512 seek=2 conv=fsync
 $ dd if=u-boot_crc.bin.crc of=<span style='''${SD_DEVICE}''' bs=512 seek=2 conv=fsync

:Perform the following command to transfer to on-board flash

 $ dd if=u-boot_crc.bin.crc of=/dev/mmcblk0 bs=512 seek=2 conv=fsync
 $ dd if=u-boot-crc.bin of=/dev/mmcblk0 bs=512 seek=3 conv=fsync

== <span style="color:#0070c0">Building & updating kernel/modules/dtb manually</span> ==

:The cross compiling environment has been set up. (ref. [[#Setting_up_cross_compiling_environment|Setting up cross compiling environment]])

=== <span style="color:#0070c0">Copy BSP tarball to Container</span> ===

Refer to [http://ess-wiki.advantech.com.tw/view/IoTGateway/BSP/Linux/iMX6/Yocto_LBV8_User_Guide#Copy_BSP_tarball_to_Container Copy_BSP_tarball_to_Container] , copy kernel tarball to ${WORKSPACE} and back to container

change owner & unpack tarball

 $ sudo chown adv:adv imx6LBV8210_2017-02-20_linux-imx6.tgz
 $ tar zxvf imx6LBV8210_2017-02-20_linux-imx6.tgz

=== <span style="color:#0070c0">Config kernel</span> ===

:Configure linux kernel

 $cd linux-imx6
 $make distclean
 $make imx_v7_adv_defconfig
 $make menuconfig

=== <span style="color:#0070c0">Build kernel</span> ===

:Start building linux kernel

 $ make -j4 zImage LOADADDR=0x10008000

:The kernel image file, zImage, is located in the directory "./arch/arm/boot/".

:Start building kernel modules

 $ make -j4 modules

:Copy all modules to a temporary rootfs directory, "~/temp/rootfs"

 $ make modules_install INSTALL_MOD_PATH=~/temp/rootfs

:Building device tree blob

 $ make -j4 <span style="color:#7030a0">'''${IMX6PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD_REV}'''</span>.dtb

:The device tree blob, <span style="color:#7030a0">'''${IMX6PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD_REV}'''</span>.dtb, is located in the directory "./arch/arm/boot/dts/".

=== <span style="color:#0070c0">Replace kernel & dts</span> ===

:Replace kernel
::copy zImage to SDcard or emmc
:Replace dtb file
::copy dtb file to SDcard or emmc

= System Recovery =

Please refer to [[#Creating_boot-up_on-board_flash_from_prebuilt_image|Creating boot-up on-board flash from prebuilt image]] / [[#Creating_boot-up_on-board_flash_from_built_sdcard_image|sdcard image]] to create a boot-up SD card and transfer whole system to on-board flash.