Difference between revisions of "IoTGateway/BSP/Linux/iMX8/Yocto LBVA User Guide"

From ESS-WIKI
Jump to: navigation, search
(Created page with "{{DISPLAYTITLE:Yocto Linux BSP Ver.9 User Guide for iMX8 series}} <!-- {| align="right" | <span class="fck_mw_magic" _fck_mw_customtag="true" _fck_mw_tagname="TOC" _fck_mw_ta...")
 
Line 1: Line 1:
−
{{DISPLAYTITLE:Yocto Linux BSP Ver.9 User Guide for iMX8 series}} <!--
+
{{DISPLAYTITLE:Yocto Linux BSP Ver.A User Guide for iMX8 series}} <!--
 
{| align="right"
 
{| align="right"
 
  | <span class="fck_mw_magic" _fck_mw_customtag="true" _fck_mw_tagname="TOC" _fck_mw_tagtype="c">_</span>
 
  | <span class="fck_mw_magic" _fck_mw_customtag="true" _fck_mw_tagname="TOC" _fck_mw_tagtype="c">_</span>
Line 11: Line 11:
 
<span style="color:purple">'''${PREBUILT_IMAGE}'''</span>&nbsp;: compressed prebuilt image (*.img.gz)
 
<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. imx9LBV90016)
+
<span style="color:purple">'''${CONTAINER_NAME}'''</span>&nbsp;: container name (e.g. imx8LBVA0016)
  
 
<span style="color:purple">'''${BSP_TARBALL}'''</span>&nbsp;: BSP tarball (*.tgz)
 
<span style="color:purple">'''${BSP_TARBALL}'''</span>&nbsp;: BSP tarball (*.tgz)
Line 23: Line 23:
 
:mx8mq for iMX8M Dual Core<br/>
 
:mx8mq for iMX8M Dual Core<br/>
 
:mx8mm for iMX8MM<br/>
 
:mx8mm for iMX8MM<br/>
 +
:mx8mp for iMX8MP<br/>
 
:mx8qm for iMX8QM<br/>
 
:mx8qm for iMX8QM<br/>
 
:mx8qxp for iMX8QXP<br/>
 
:mx8qxp for iMX8QXP<br/>
Line 29: Line 30:
 
<span style="color:purple">'''${IMX8PROC}'''</span>&nbsp;: i.MX8 Processor
 
<span style="color:purple">'''${IMX8PROC}'''</span>&nbsp;: i.MX8 Processor
  
−
:imx8mq / imx8mm / imx8qm /imx8qxp<br/>
+
:imx8mq / imx8mm / imx8qm /imx8qxp /imx8mp<br/>
  
 
<span style="color:purple">'''${BOARD}'''</span>&nbsp;: available target boards list below
 
<span style="color:purple">'''${BOARD}'''</span>&nbsp;: available target boards list below
Line 37: Line 38:
 
:rom7720<br/>
 
:rom7720<br/>
 
:rom5620<br/>
 
:rom5620<br/>
 +
:rsb3720<br/>
  
 
<span style="color:purple">'''${BOARD_REV}'''</span>&nbsp;: board revision
 
<span style="color:purple">'''${BOARD_REV}'''</span>&nbsp;: board revision
Line 50: Line 52:
 
::<tt>imx8qxprom5620a1 for ROM-5620 A1</tt><br/>
 
::<tt>imx8qxprom5620a1 for ROM-5620 A1</tt><br/>
 
::<tt>imx8mmrom5721a1 for ROM-5721 A1</tt><br/>
 
::<tt>imx8mmrom5721a1 for ROM-5721 A1</tt><br/>
 +
::<tt>imx8mmrsb3720a1 for RSB-3720 A1</tt><br/>
  
 
:You can also use the command below to check supported machines on BSP
 
:You can also use the command below to check supported machines on BSP
Line 88: Line 91:
 
=== <span style="color:#0070c0">To pull [https://hub.docker.com/r/advrisc/u12.04-imx6lbv3/ ubuntu 16.04 image from Docker Hub]&nbsp;</span> ===
 
=== <span style="color:#0070c0">To pull [https://hub.docker.com/r/advrisc/u12.04-imx6lbv3/ ubuntu 16.04 image from Docker Hub]&nbsp;</span> ===
  
−
:<code>$ docker pull advrisc/u16.04-imx8lbv1</code><br/>
+
:<code>$ docker pull advrisc/u18.04-imx8lbv1</code><br/>
  
 
=== <span style="color:#0070c0">To create container</span> ===
 
=== <span style="color:#0070c0">To create container</span> ===
  
−
:<code>$ docker run --privileged -it --name '''${CONTAINER_NAME}'''&nbsp;-v '''${WORKSPACE}''':/home/adv/adv-release-bsp -v /dev:/dev&nbsp;advrisc/u16.04-imx8lbv1 /bin/bash</code><br/>
+
:<code>$ docker run --privileged -it --name '''${CONTAINER_NAME}'''&nbsp;-v '''${WORKSPACE}''':/home/adv/adv-release-bsp -v /dev:/dev&nbsp;advrisc/u18.04-imx8lbv1 /bin/bash</code><br/>
  
 
== <span style="color:#0070c0">Get BSP</span> ==
 
== <span style="color:#0070c0">Get BSP</span> ==
Line 104: Line 107:
 
:For this example, a directory called '''adv-release-bsp''' is created for the project.
 
:For this example, a directory called '''adv-release-bsp''' is created for the project.
  
−
:Refer to&nbsp;[[IoTGateway/BSP/Linux/iMX8/OS_Support_List|IoTGateway/BSP/Linux/iMX8/OS_Support_List]] , Official version "'''imx8LBV90029"&nbsp;'''is taken as&nbsp;an example&nbsp;:<br/>
+
:Refer to&nbsp;[[IoTGateway/BSP/Linux/iMX8/OS_Support_List|IoTGateway/BSP/Linux/iMX8/OS_Support_List]] , Official version "'''imx8LBVA0029"&nbsp;'''is taken as&nbsp;an example&nbsp;:<br/>
 
<pre>$ git config --global user.name "Your Name"
 
<pre>$ git config --global user.name "Your Name"
 
$ git config --global user.email you@example.com
 
$ git config --global user.email you@example.com
 
$ sudo chown adv:adv adv-release-bsp
 
$ sudo chown adv:adv adv-release-bsp
 
$ cd 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 init -u git://github.com/ADVANTECH-Corp/adv-arm-yocto-bsp.git -b refs/tags/imx8LBVA0029 -m imx8LBVA0029.xml  
 
$ repo sync</pre>
 
$ repo sync</pre>
  
 
:If you want to get latest bsp
 
: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]  <span>-b imx-linux-sumo -m imx-4.14.98-2.0.0_ga.xml</span>  
+
  $ repo init -u [git://github.com/ADVANTECH-Corp/adv-arm-yocto-bsp.git git://github.com/ADVANTECH-Corp/adv-arm-yocto-bsp.git]  <span>-b imx-linux-zeus -m </span>imx-5.4.24-2.1.0.xml<span></span>  
 
  $ repo sync
 
  $ repo sync
  
 
=== <span style="color:#0070c0">Copy BSP tarball to Container</span> ===
 
=== <span style="color:#0070c0">Copy BSP tarball to Container</span> ===
  
−
:If you have BSP tarball (eg. imx8LBV90029_2019-10-23.tgz), then you have to copy it into container.<br/>
+
:If you have BSP tarball (eg. imx8LBVA0029_2019-10-23.tgz), then you have to copy it into container.<br/>
  
 
Follow the steps below:
 
Follow the steps below:
Line 129: Line 132:
 
2.Copy BSP tarball to ${WORKSPACE} , and change owner
 
2.Copy BSP tarball to ${WORKSPACE} , and change owner
  
−
  $ cp imx8LBV90029_2019-10-23.tgz '''${WORKSPACE}'''
+
  $ cp imx8LBVA0029_2020-10-23.tgz '''${WORKSPACE}'''
−
  $ sudo chown adv:adv ${WORKSPACE}/imx8LBV90029_2019-10-23.tgz&nbsp;
+
  $ sudo chown adv:adv ${WORKSPACE}/imx8LBVA0029_2020-10-23.tgz&nbsp;
  
 
3.Back to container
 
3.Back to container
Line 139: Line 142:
 
4.Unpack BSP tarball
 
4.Unpack BSP tarball
  
−
  $ tar zxvf imx8LBV90029_2019-10-23.tgz
+
  $ tar zxvf imx8LBVA0029_2020-10-23.tgz
  
 
== <span style="color:#0070c0">Downloads tarball</span> ==
 
== <span style="color:#0070c0">Downloads tarball</span> ==
Line 196: Line 199:
 
:which , "LB" is acronym of <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''B'''</span>SP,<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;"V90010" stands for <span style="color:#ff0000">'''V'''</span>ersion <font color="#ff0000">'''9'''</font>.<span style="color:#ff0000">'''0010'''</span><nowiki>.</nowiki>
 
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"V90010" stands for <span style="color:#ff0000">'''V'''</span>ersion <font color="#ff0000">'''9'''</font>.<span style="color:#ff0000">'''0010'''</span><nowiki>.</nowiki>
 +
 +
 +
 +
  
  

Revision as of 07:42, 14 August 2020


Contents

Getting Started

Conventions

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

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

${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
mx8mp for iMX8MP
mx8qm for iMX8QM
mx8qxp for iMX8QXP

${IMX8PROC} : i.MX8 Processor

imx8mq / imx8mm / imx8qm /imx8qxp /imx8mp

${BOARD} : available target boards list below

rom5720
rom5721
rom7720
rom5620
rsb3720

${BOARD_REV} : board revision

a1

${MC} : machine code combined with ${IMX8PROC}${BOARD}${BOARD_REV}

for example,
imx8mqrom5720a1 for ROM-5720 A1
imx8qmrom7720a1 for ROM-7720 A1
imx8qxprom5620a1 for ROM-5620 A1
imx8mmrom5721a1 for ROM-5721 A1
imx8mmrsb3720a1 for RSB-3720 A1
You 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 16.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 "imx8LBVA0029" is taken as an example :
$ git config --global user.name "Your Name"
$ 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/imx8LBVA0029 -m imx8LBVA0029.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-zeus -m imx-5.4.24-2.1.0.xml 
$ repo sync

Copy BSP tarball to Container

If you have BSP tarball (eg. imx8LBVA0029_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 imx8LBVA0029_2020-10-23.tgz ${WORKSPACE}
$ sudo chown adv:adv ${WORKSPACE}/imx8LBVA0029_2020-10-23.tgz 

3.Back to container 

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

4.Unpack BSP tarball 

$ tar zxvf imx8LBVA0029_2020-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: 4971ce00d3d0cdc48a5f35b584920c07
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_imx8-2.5.tgz ${WORKSPACE}
$ sudo chown adv:adv ${WORKSPACE}/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 ${WORKSPACE}/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.tgz
which , "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 Advantech
meta-fsl-*/ : meta layer by Freescale
fsl-setup-release.sh : to create one new build environment
setup-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}
You need to read and accept the EULA.
RTENOTITLE

To continue an exist build environment

Perform the following commands in terminal console
$ cd ${BSP_HOME}
$ source setup-environment ${BDIR}

To build sdcard image

To create/continue a build environment
Perform the following command in terminal console
$ bitbake fsl-image-validation-imx
The 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-toolchain
The 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 tmux
Type following command to enter tmux
$ tmux
Perform the following command in terminal console to show up menuconfig
$ bitbake linux-imx -c menuconfig
After edit menuconfig, type following command to exit tmux windows
$ exit
to build kernel image
$ bitbake linux-imx
The 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. 

workspace/${BDIR}/tmp/deploy/images/${MC}

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 ${BSP_HOME}/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 ${BSP_HOME}/${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 ${BSP_HOME}/${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 ${BSP_HOME}/${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

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 

./cp_uboot.sh ${uboot path} ${IMX8PROC}

Make imx-boot image 

./mk_imx-boot.sh ${IMX8PROC}

eg. 

./cp_uboot.sh ../uboot-imx6 imx8m
./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

The cross compiling environment has been set up. (ref. 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/".

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.
setenv bootdelay 0
env save
reset

2.Disable console

Disable debug message output can also improve boot speed

Disable kernel message 

setenv mmcargs setenv bootargs ${jh_clk} console=${console} modprobe.blacklist=${modprobe.blacklist} root=${mmcroot} video=HDMI-A-1:${videores} quiet
env save
reset

Or

Disable debug port
setenv console
env save
reset
  • Rootfs
TBD
  • Services

1. Using systemctl disable remove ,we can remove unnecessary services. 

systemctl disable <services>

eg. 

systemctl disable boottimes

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.

  • Recovery 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


  • Recovery 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: 

1.uuu
2.imx-boot-imx8mqrom5720a1-sd.bin-flash_evk
3.fsl-image-validation-imx-imx8mqrom5720a1-20190917152605.rootfs.sdcard
4._initramfs.cpio.gz.uboot
5.Image_dtb.uuu
6.rootfs.uuu

3.Connect otg cable from PC to device

4.Set the correct boot mode(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), then power 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, 

1.Burn uboot to emmc
   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 

   a)replace Image and dtb
       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 

bitbake -g fsl-image-qt5-validation-imx && cat recipe-depends.dot | grep -v -e '-native' | grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq
20191025 Package List

Show all recipes (include non-installed packages) 

bitbake -s
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 

rpm -qa --root / --dbpath /var/lib/rpm | sort
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

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

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-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.

Retrieved from "https://ess-wiki.advantech.com.tw/wiki/index.php?title=IoTGateway/BSP/Linux/iMX8/Yocto_LBVA_User_Guide&oldid=19214"