Yocto Linux BSP Ver.9 User Guide for iMX8 series

Introduction

Getting Started

Conventions

${PREBUILT_IMAGE} : compressed prebuilt image (*.img.gz)

${CONTAINER_NAME} : container name (e.g. imx9LBV90016)

${BSP_TARBALL} : BSP tarball (*.tgz)

${BSP_HOME} : home directory of the BSP

${BDIR} : build directory (e.g. build_x11)

${MX8PROC} : i.MX8 Processor mx8mq for iMX8M Dual Core mx8mm for iMX8MM mx8qm for iMX8QM mx8qxp for iMX8QXP

${IMX8PROC} : i.MX8 Processor imx8mq / imx8mm / imx8qm /imx8qxp

${BOARD} : available target boards list below rom5720 rom5721 rom7720 rom5620 rom3620

${BOARD_REV} : board revision a1

${MC} : machine code combined with **${IMX8PROC}``${BOARD}``${BOARD_REV}**for example, imx8mqrom5720a1 for ROM-5720 A1imx8qmrom7720a1 for ROM-7720 A1imx8qxprom5620a1 for ROM-5620 A1imx8mmrom5721a1 for ROM-5721 A1imx8qxprom3620a1 for ROM-3620 A1You can also use the command below to check supported machines on BSP $ source setup-environment

${MEM_SIZE} : memory size 2G/4G

${SD_DEVICE} : device name of SD card in Linux (e.g. /dev/sdf)

${SDCARD_IMAGE} : sdcard image built by bitbake (*.sdcard.bz2)

${WORKSPACE} : host workspace folders

${UBOOT} :u-boot version(e.g. 2016.03)

${KERNEL} : linux kernel version(e.g. 4.14.98)

${TOOLCHAIN} : 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 ...)

Docker install and setting

If you don't have docker in your system, then you can follow the below steps to install docker and run it first.

To install Docker Engine on your platform

Please refer to Docker Installation Guide for details

To pull ubuntu 18.04 image from Docker Hub

$ docker pull advrisc/u18.04-imx8lbv1

To create container

$ docker run --privileged -it --name ``${CONTAINER_NAME}`` -v ``${WORKSPACE}``:/home/adv/adv-release-bsp -v /dev:/dev advrisc/u18.04-imx8lbv1 /bin/bash

Get BSP

You have two methods to put BSP into container created above

Download_BSP_From_GitHub

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 IoTGateway/BSP/Linux/iMX8/OS_Support_List , Official version "**imx8LBV90029" **is taken as an example :

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

If you want to get latest bsp

repo init -u git://github.com/ADVANTECH-Corp/adv-arm-yocto-bsp.git-b imx-linux-sumo -m imx-4.14.98-2.0.0_ga.xml $ repo sync

If you suffer "server certificate verification failed", you can use the following command to disable SSL verification in git repositories with self-signed certificates. 

export GIT_SSL_NO_VERIFY=1

or

git config --global http.sslverify false

```''''''The unauthenticated git protocol on port 9418 is no longer supported''''''

To Solve The unauthenticated git protocol on port 9418 is no longer supported Error This error May occurs due to latest '''Improving Git protocol security on GitHub '''which was released on '''January 11, 2022 Final brownout.''' Simple solution is Before You Install Just Set url to globally to set url globally Run this command:''' git config –global url.”[https://”.insteadOf https://”.insteadOf] git://''' Now, Your error must be solved.

Copy BSP tarball to Container

If you have BSP tarball (eg. imx8LBV90029_2019-10-23.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 imx8LBV90029_2019-10-23.tgz `/home/adv/adv-release-bsp`
$ sudo chown adv:adv /home/adv/adv-release-bsp/imx8LBV90029_2019-10-23.tgz 

3.Back to container

 docker start `${CONTAINER_NAME}`
$ docker attach `${CONTAINER_NAME}`

4.Unpack BSP tarball

 tar zxvf imx8LBV90029_2019-10-23.tgz

Downloads tarball

Not necessarily step During building 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. You can get Downloads tarball (downloads_imx8-2.5.tgz) from following URL: [downloads_imx8-2.5.tgz], md5 checksum:****4971ce00d3d0cdc48a5f35b584920c07If 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_imx8-2.5.tgz `/home/adv/adv-release-bsp`
$ sudo chown adv:adv /home/adv/adv-release-bsp/downloads_imx8-2.5.tgz 

3.Back to container

 docker start `${CONTAINER_NAME}`
$ docker attach `${CONTAINER_NAME}`

4.Unpack Downloads tarball

 tar zxvf downloads_imx8-2.5.tgz

5.make link to downloads folder

 cd adv-release-bsp
$ ln -s /home/adv/adv-release-bsp/downloads_imx8-2.5 downloads

Introducing BSP

The BSP is based on Yocto Project with Freescale enhanced features for i.MX8, 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.

Naming Rule

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: imx8LBV90010_2019-08-27.tgzwhich , "LB" is acronym of Linux BSP, "V90010" stands for Version 9.0010 .

For example, **Yocto image name: '***5720A1AIM20LIV90010_iMX8M_2019-08-27.img.gz'*which "5720A1" stands for ROM-5720 A1 "LI" is acronym for prebuilt Linux Image

BSP Content

The description of some important folders list below:sources/meta-advantech/ : meta layer by Advantechmeta-fsl-*/ : meta layer by Freescalefsl-setup-release.sh : to create one new build environmentsetup-environment : to continue an exist build environment

Build Instructions

To create one new build environment

Perform the following commands in terminal console $ cd ${"}BSP_HOME{"} MACHINE=`${MC}DISTRO=fsl-imx-xwayland source fsl-setup-release.sh -b `$\{"{"}BDIR\{"}"}

To continue an exist build environment

Perform the following commands in terminal console $ cd ${"}BSP_HOME{"}``` source setup-environment ### To build recovery image for OTA Perform the following command in terminal console $ bitbake initramfs-debug-imageThe initramfs-debug-image`, will be located in recovery partition.

To build sdcard image

To create/continue a build environment Perform the following command in terminal console $ bitbake fsl-image-validation-imxThe file, fsl-image-validation-imx-${MC}.sdcard.bz2, will be located in directory, ./tmp/deploy/images/${MC}, while building process finished successfully.

To build toolchain installer

To create/continue a build environment Perform the following command in terminal console $ bitbake meta-toolchainThe below installer will be located in the directory "./tmp/deploy/sdk". fsl-imx-xwayland-glibc-x86_64-meta-toolchain-aarch64-toolchain-${KERNEL}-sumo.sh

To build bootloader

To create/continue a build environment Perform the following command in terminal console $ bitbake imx-boot

To build linux kernel

To create/continue a build environment If you operate on docker images, please install tmux application before running this command $ sudo apt-get install tmuxType following command to enter tmux $ tmuxPerform the following command in terminal console to show up menuconfig $ bitbake linux-imx -c menuconfigAfter edit menuconfig, type following command to exit tmux windows $ exitto build kernel image $ bitbake linux-imxThe two files, Image & Image-adv-${"}IMX8PROC{"}-${BOARD}-${BOARD_REV}.dtb, will be located in the directory, ./tmp/deploy/images/${MC}.

Creating boot-up on-board flash from prebuilt image

To create one boot-up SD card

Perform the following command in terminal console # gunzip -c **${PREBUILT_IMAGE**} | dd of=${"}SD_DEVICE{"} bs=1M``# sync

Creating boot-up on-board flash from built sdcard image

To create one boot-up SD card

Perform the following commands in terminal console $ pushd ${"}BSP_HOME{"}/${"}BDIR{"}/tmp/deploy/images/${"}MC{"}``` sudo bzcat ${SDCARD_IMAGE} | sudo dd of=${SD_DEVICE} bs=1M$ sync$ popd`## Debug console information

If you want to see debug message from device, you need to prepare for hardware device and software tool.

Preparing for hardware device

The following URL provides information about the debug port slot and the debug port line for each device

Debug Port Information

Preparing for software tool

You need to prepare the debug console tool. For example: "minicom" tool or "putty" tool.
Baud rate: 115200

One step build image

Our machine must be pre-installed docker

Download the following script can quickly build our image.

 wget https://raw.githubusercontent.com/ADVANTECH-Corp/RISC_tools_scripts/master/imx8/adv_imx8_build.sh
$ sudo chmod a+x adv_imx8_build.sh

Build image

 sudo ./adv_imx8_build.sh ${BOARD}
$ sudo ./adv_imx8_build.sh rom5720

Our image will be in workspace folder.

Then refer to Creating_boot-up_on-board_flash_from_built_sdcard_image to build SD card.

# Customization

## Package addition

### To add tcf-agent & openssh-sftp-server
Navigate to the directory where fsl-image-adv.inc located 
`$ cd `/home/adv/adv-release-bsp`/sources/meta-advantech/meta-fsl-imx/recipes-fsl/images`Add following line to fsl-image-adv.inc 
`IMAGE_INSTALL += " tcf-agent openssh-sftp-server "`Continue an exist build environment and build sdcard image
### To add chromium browser
Navigate to the directory where local.conf located 
`$ cd `/home/adv/adv-release-bsp`/`${BDIR}`/conf`

- Method 1(Suggest): Add following one line to local.conf 
```CORE_IMAGE_EXTRA_INSTALL += "chromium-ozone-wayland"
- Method 2: Add following two lines to local.conf 
```IMAGE_INSTALL_append = \
   "${@bb.utils.contains('DISTRO_FEATURES', 'wayland', ' chromium-ozone-wayland libexif', \
       bb.utils.contains('DISTRO_FEATURES',     'x11', ' chromium-x11 libexif', \
                                                        *, d), d)}"*
LICENSE_FLAGS_WHITELIST = \
   "${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 'commercial', \
       bb.utils.contains('DISTRO_FEATURES',     'x11', 'commercial', \
                                                       *, d),"*
Continue an exist build environment and build sdcard image

### To add QtWebEngine
Put the following in `/home/adv/adv-release-bsp`/`${BDIR}`/conf/local.conf `IMAGE_INSTALL_append += "packagegroup-qt5-webengine"`Continue an exist build environment and build sdcard image
## Setting up SDK
Please follow the section,To build toolchain installer, to build one toolchain installer Perform the following command in terminal console 
`$ cd `/home/adv/adv-release-bsp`/`${BDIR}`/tmp/deploy/sdk``$ sudo ./fsl-imx-xwayland-glibc-x86_64-meta-toolchain-aarch64-toolchain-4.14-sumo.sh`Enter new installed directory or just press `Enter` to use default directory. While `Proceed[y/n]?` shows up, please enter the correct one. Waiting for the SDK installed (while the following messages show up completely) 

![RTENOTITLE](img/Setting_up_sdk_3.png)

## Setting up cross compiling environment
SDK has been set up (ref.Setting up SDK) Perform the following command in terminal console 
`$ source `${TOOLCHAIN}`/environment-setup-aarch64-poky-linux`
## Build U-Boot in standalone environment

#### Config u-boot

```make \\$\{IMX8PROC\}_\\$\{BOARD\}\\$\{BOARD_REV\}_\\$\{MEM_SIZE\}_defconfig
eg.

```make imx8mm_rom5721a1_2G_defconfig

#### Build u-boot

```make -j4
## Build imx-boot image by using imx-mkimage

Get imx-boot tarball from our server Here we take rom5721 as an example:

```tar zxvf 5721A1AIM20LIV90118_iMX8MM_imx-boot.tgz 
cd 5721A1AIM20LIV90118_iMX8MM_imx-boot/ 

In this folder , we have two script as below: Copy necessary files to imx-mkimage folder

Make imx-boot image

eg.

./mk_imx-boot.sh **imx8mm**

Replace imx-boot

Perform the following command to transfer to on-board flash

 dd if=flash.bin of=/dev/mmcblk0 bs=1K seek=<offset> conv=fsync

Where offset is: 33 - for i.MAX 8QuadMax A0, i.MAX 8QuadXPlus A0, i.MAX 8M Quad, and i.MAX 8M Mini 32 - for i.MAX 8QuadXPlus B0 and i.MAX 8QuadMax B0

Building & updating kernel/modules/dtb manually

First, set up the cross compiling environment!

You can refer to Setting up cross compiling environment

Copy BSP tarball to Container

Refer to Copy_BSP_tarball_to_Container , copy kernel tarball to ${"}WORKSPACE{"} and back to container

change owner & unpack tarball

 sudo chown adv:adv imx8LBV90029_2019-10-23_linux-imx6.tgz
$ tar zxvf imx8LBV90029_2019-10-23_linux-imx6.tgz

Config kernel

Configure linux kernel

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

Start building linux kernel

 make -j4 Image

When you get error like below

RTENOTITLE run command then rebuild

 unset LDFLAGS

The kernel image file, Image, is located in the directory "./arch/arm64/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 freescale/adv-`${IMX8PROC}`-`${BOARD}`-`${BOARD_REV}`.dtb
eg.
$ make -j4 freescale/adv-imx8mq-rom5720-a1.dtb

The device tree blob, ${IMX6PROC}-${BOARD}-${BOARD_REV}.dtb, is located in the directory "./arch/arm64/boot/dts/freescale/". Note:./build_x11/tmp/work-shared/imx8qxprom5620a1/kernel-source/arch/arm64/boot/dts/freescale/imx8qxp-rom5620-a1.dts

Replace kernel & dts

Replace kernel copy Image to SDcard or emmc Replace dtb file copy dtb file to SDcard or emmc

Improve boot speed

Bootloader

1.bootdelay time We can cancel the bootdelay time by setting bootloader environment value.

env save
reset

2.Disable console Disable debug message output can also improve boot speed

Disable kernel message

env save
reset

Or Disable debug port

(1) Yocto machine setting:

modify the meta-fsl-imx/conf/machine/${"}MC{"}.conf

(2) Uboot parameter setting:

For the imx8mq, imx8mm, imx8mp:

env save
reset

For the imx8qm, imx8qxp:

setenv earlycon disabled
env save
reset

Rootfs TBD
Services

Using systemctl disable remove ,we can remove unnecessary services.

eg.

# System Recovery

This section provides detail procedures of restoring the eMMC image.

If you destroy the onboard flash image by accident, you can recover a system following these steps.

## Recover by SD card

1.Copy 5720A1AIM20LIV90022_iMX8M_flash_tool.tgz package to your desktop.

2.Insert SD card to PC

3.Make a bootable sd card

```# tar zxvf 5720A1AIM20LIV90022_iMX8M_flash_tool.tgz
# cd 5720A1AIM20LIV90022_iMX8M_flash_tool/mk_inand/
# sudo ./mksd-linux.sh /dev/sdg
4.Insert SD card and copy 5720A1AIM20LIV90022_iMX8M_flash_tool to USB disk

5.Insert USB disk and SD card then Boot from SD

6.Enter usb disk folder, make a bootable emmc

```# cd /run/media/sda1/
# cd 5720A1AIM20LIV90022_iMX8M_flash_tool/mk_inand/
# sudo ./mksd-linux.sh /dev/mmcblk0

## Recover by UUU tool

1.Download uuu tool from (https://github.com/ADVANTECH-Corp/uuu/releases/tag/v20200619)

2.burn command

- For Linux 
``` sudo ./uuu
- For Windows 
``` uuu.exe 

2.Create a folder with files as below:

We can download image from official build folder(https://www.dropbox.com/sh/w271m51tuoajvbp/AAD6KM2uu-ONRUXCLKL8y4hia?dl=0)
rootfs.sdcard in 5620A1AIM20LIV90135_iMX8X_flash_tool.tgz
imx-boot in 5620A1AIM20LIV90135_iMX8X_imx-boot.tgz

imx-boot-imx8mqrom5720a1-sd.bin-flash_evk
fsl-image-validation-imx-imx8mqrom5720a1-20190917152605.rootfs.sdcard
Image_dtb.uuu
rootfs.uuu

3.Connect USB OTG cable from PC to device

4.Set SW1 to Recovery mode, then power on

ROM5720/ROM5721/ROM5620: 1,2,3-off, 4-on
ROM7720: 1,2,3,4,5,6-off or 1,2,4,5,6-off, 3-on

5.Perform the following command:

PS.If you want to burn uboot to mmcblk0 instead of mmcblk0boot0, u-boot must be updated to version 20191101,

   a)replace uboot in mmcblk0boot0
       sudo ./uuu -b **emmc** imx-boot-imx8mqrom5720a1-sd.bin-flash_evk
   b)replace uboot in mmcblk0
       sudo ./uuu -b **emmc_adv** imx-boot-imx8mqrom5720a1-sd.bin-flash_evk
2.Burn rootfs image to emmc
   a)replace uboot in mmcblk0boot0
       sudo ./uuu -b **emmc_all** imx-boot-imx8mqrom5720a1-sd.bin-flash_evk fsl-image-validation-imx-imx8mqrom5720a1-20190917152605.rootfs.sdcard
   b)replace uboot in mmcblk0
       sudo ./uuu -b **emmc_all_adv** imx-boot-imx8mqrom5720a1-sd.bin-flash_evk fsl-image-validation-imx-imx8mqrom5720a1-20190917152605.rootfs.sdcard

6.uuu tool will start recovery image to emmc.

7.If we want to burn separately into emmc

       Step 1: rename Image and dtb 
                 _Image
                 _board.dtb
       Step 2: 
                 sudo ./uuu Image_dtb.uuu
   b)replace rootfs
       Step 1: rename rootfs tarball
                 _rootfs.tar.bz2
       Step 2: 
                 sudo ./uuu rootfs.uuu

8.For more usage (https://github.com/NXPmicro/mfgtools/wiki)

Package List

In BSP, list all packages which will be built in the image

20191025 Package List

Show all recipes (include non-installed packages)

20191025 Package Version List

You can also check ${BDIR}/tmp/deploy/images/${MC}/fsl-image-qt5-validation-imx-${MC}.manifest

It will show the same content with checking by rpm tool on target board.

On target board, list all packages by rpm tool

20191025 RPM on Board List
# Device Tree Source file select

We can setup different dts file on bootloader to enable different devices.

eg.

```setenv fdt_file **adv-imx8mm-rom5721-a1-dsi2dp**.dtb
env save
boot 
## ROM-5721

- Display 

- DSI to LVDS 

- g070vw01 

- adv-imx8mm-rom5721-a1.dtb   
- g150xgel05 

- adv-imx8mm-rom5721-a1-dsi2lvds-g150xgel05.dtb   
- g215hvn01 

- adv-imx8mm-rom5721-a1-dsi2lvds-g215hvn01.dtb     
- DSI to DP 

- adv-imx8mm-rom5721-a1-dsi2dp.dtb   
- DSI to HDMI 

- adv-imx8mm-rom5721-a1-adv7535.dtb   
- DSI 

- auog101uan02 

- adv-imx8mm-rom5721-a1-auog101uan02.dtb       
- M.2 SDIO 

- Adjust CN43~CN48 
- adv-imx8mm-rom5721-a1-m2-sdio.dtb   
- M.2 I2S 

- adv-imx8mm-rom5721-a1-m2-i2s.dtb   
## ROM-5720

- Display 

- DSI to HDMI 

- adv-imx8mq-rom5720-a1-dcss-adv7535-b3.dtb 
- adv-imx8mq-rom5720-a1-lcdif-adv7535.dtb   
- DSI 

- auog101uan02 

- adv-imx8mq-rom5720-a1-dcss-auog101uan02.dtb     
- Dual Display 

- DSI to HDMI + HDMI 

- adv-imx8mq-rom5720-a1-dual-display.dtb       
- M.2 SDIO 

- Adjust CN43~CN48 
- adv-imx8mq-rom5720-a1-m2-sdio.dtb   
- M.2 I2S 

- adv-imx8mq-rom5720-a1-m2-i2s.dtb   
## ROM-5620

- Display 

- LVDS 

- g070vw01 

- adv-imx8mxp-rom5620-a1.dtb   
- g150xgel05 

- adv-imx8qxp-rom5620-a1-lvds-chimei.dtb   
- g215hvn01 

- adv-imx8qxp-rom5620-a1-lvds-dual.dtb     
- LVDS to HDMI 

- adv-imx8qxp-rom5620-a1-hdmi-bridge.dtb   
- DSI to HDMI 

- adv-imx8qxp-rom5620-a1-hdmi-bridge.dtb   
- DSI 

- auog101uan02 

- adv-imx8qxp-rom5620-a1-auog101uan02.dtb       
- M.2 SDIO 

- Adjust CN43~CN48 
- adv-imx8qxp-rom5620-a1-m2-sdio.dtb   
- 2-nd QSPI 

- adv-imx8qxp-rom5620-a1-qspi-b.dtb   
## ROM-3620

- Display 

- LVDS 

- g070vw01 

- adv-imx8mxp-rom3620-a1.dtb   
- g150xgel05 

- adv-imx8qxp-rom3620-a1-lvds-chimei.dtb   
- g215hvn01 

- adv-imx8qxp-rom3620-a1-lvds-dual.dtb     
- DSI to HDMI 

- adv-imx8qxp-rom3620-a1-hdmi-bridge.dtb   
- DSI 

- auog101uan02 

- adv-imx8qxp-rom3620-a1-auog101uan02.dtb       
## ROM-7720

- Display 

- HDMI 

- adv-imx8qm-rom7720-a1.dtb   
- LVDS 

- g070vw01 

- adv-imx8qm-rom7720-a1_lvds0.dtb 
- adv-imx8qm-rom7720-a1_lvds1.dtb   
- g215hvn01 

- adv-imx8qm-rom7720-a1_lvds_dual.dtb     
- HDMI + LVDS 

- HDMI + g070vw01 

- adv-imx8qm-rom7720-a1_hdmi_lvds0.dtb 
- adv-imx8qm-rom7720-a1_hdmi_lvds1.dtb   
- HDMI + g215hvn01 

- adv-imx8qm-rom7720-a1_hdmi_lvds_dual.dtb     
- LVDS to HDMI 

- adv-imx8qm-rom7720-a1-it6263.dtb
- Audio Codec 

- adv-imx8qm-rom7720-a1-sgtl5000.dtb   
# Burn-in Test

When running the burn-in test, the CPU, GPU and VPU are running in turns. It is not recommended to run three at the same time.

## About DB5901 bottom board setting

## The disable pin of PCIE

On DB5901 bottom board, the disable pin is connect to gpio expander(tca9538)

![RTENOTITLE](img/1633679976526.jpg)

![RTENOTITLE](img/1633672222378.jpg)

You should config disable pin follow your bottom board.

If the disable pin is not set correctly, the pcie may not enable.

We remove the disable pin setting by default.

```&pcie0\{pinctrl-names="default";pinctrl-0=<&pinctrl_pcie0>;//disable-gpio = <&tca9538 0 GPIO_ACTIVE_LOW>; <---reset-gpio=<&gpio113GPIO_ACTIVE_LOW>;ext_osc=<1>;status="okay";\};
# How to get the MAC, Serial Number, and Manufacture Date in the QSPI flash

MAC 0:

```READ_DATA=`ddif=/dev/mtdblock0bs=1skip=$((0xd0000))count=62>/dev/null|hexdump-e'16/1"%02x ""\n"'|sed's//:/g'|cut-c1-17`echo$READ_DATA
MAC 1:

```READ_DATA=`ddif=/dev/mtdblock0bs=1skip=$((0xd0400))count=62>/dev/null|hexdump-e'16/1"%02x ""\n"'|sed's//:/g'|cut-c1-17`echo$READ_DATA

Serial Number:

```READ_DATA=ddif=/dev/mtdblock0bs=1skip=$((0xd0006))count=102>/dev/null|cut-c1-10echo$READ_DATA

Manufacture Date:

```READ_DATA=`ddif=/dev/mtdblock0bs=1skip=$((0xd0010))count=142>/dev/null|cut-c1-14`READ_DATA=`echo$READ_DATA|cut-c1-4`-`echo$READ_DATA|cut-c5-6`-`echo$READ_DATA|cut-c7-8`_`echo$READ_DATA|cut-c9-10`-`echo$READ_DATA|cut-c11-12`-`echo$READ_DATA|cut-c13-14`echo$READ_DATA

Introduction​

Getting Started

Conventions​

Docker install and setting​

To install Docker Engine on your platform​

To pull ubuntu 18.04 image from Docker Hub​

To create container​

Get BSP​

Download_BSP_From_GitHub​

Copy BSP tarball to Container​

Downloads tarball​

Introducing BSP​

Naming Rule​

BSP Content​

Build Instructions​

To create one new build environment​

To continue an exist build environment​

To build sdcard image​

To build toolchain installer​

To build bootloader​

To build linux kernel​

Creating boot-up on-board flash from prebuilt image​

To create one boot-up SD card​

Creating boot-up on-board flash from built sdcard image​

To create one boot-up SD card​

Preparing for hardware device​

Preparing for software tool​

One step build image​

Replace imx-boot​

Building & updating kernel/modules/dtb manually​

Copy BSP tarball to Container​

Config kernel​

Replace kernel & dts​

Improve boot speed​

Package List

Introduction

Conventions

Docker install and setting

To install Docker Engine on your platform

To pull ubuntu 18.04 image from Docker Hub

To create container

Get BSP

Download_BSP_From_GitHub

Copy BSP tarball to Container

Downloads tarball

Introducing BSP

Naming Rule

BSP Content

Build Instructions

To create one new build environment

To continue an exist build environment

To build sdcard image

To build toolchain installer

To build bootloader

To build linux kernel

Creating boot-up on-board flash from prebuilt image

To create one boot-up SD card

Creating boot-up on-board flash from built sdcard image

To create one boot-up SD card

Preparing for hardware device

Preparing for software tool

One step build image

Replace imx-boot

Building & updating kernel/modules/dtb manually

Copy BSP tarball to Container

Config kernel

Replace kernel & dts

Improve boot speed