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

From ESS-WIKI
Jump to: navigation, search
 
(62 intermediate revisions by 5 users not shown)
Line 22: Line 22:
  
 
:mx8mq for iMX8M Dual Core<br/>
 
:mx8mq for iMX8M Dual Core<br/>
 +
:mx8mm for iMX8MM<br/>
 
:mx8qm for iMX8QM<br/>
 
:mx8qm for iMX8QM<br/>
 
:mx8qxp for iMX8QXP<br/>
 
:mx8qxp for iMX8QXP<br/>
Line 28: Line 29:
 
<span style="color:purple">'''${IMX8PROC}'''</span>&nbsp;: i.MX8 Processor
 
<span style="color:purple">'''${IMX8PROC}'''</span>&nbsp;: i.MX8 Processor
  
:imx8mq / imx8qm /imx8qxp<br/>
+
:imx8mq / imx8mm / imx8qm /imx8qxp<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
  
 
:rom5720<br/>
 
:rom5720<br/>
 +
:rom5721<br/>
 +
:rom7720<br/>
 +
:rom5620<br/>
 +
:rom3620<br/>
  
 
<span style="color:purple">'''${BOARD_REV}'''</span>&nbsp;: board revision
 
<span style="color:purple">'''${BOARD_REV}'''</span>&nbsp;: board revision
Line 45: Line 50:
 
::<tt>imx8qmrom7720a1 for ROM-7720 A1</tt><br/>
 
::<tt>imx8qmrom7720a1 for ROM-7720 A1</tt><br/>
 
::<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>imx8qxprom3620a1 for ROM-3620 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 61: Line 68:
 
<span style="color:purple">'''${UBOOT}'''</span>&nbsp;:u-boot version(e.g. 2016.03)
 
<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">'''${KERNEL}'''</span>&nbsp;: linux kernel version(e.g. 4.14.98)
  
 
<span style="color:purple">'''${TOOLCHAIN}'''</span>&nbsp;: toolchain installed directory(e.g. /opt/fsl-imx-x11/4.1.15-2.0.0)
 
<span style="color:purple">'''${TOOLCHAIN}'''</span>&nbsp;: toolchain installed directory(e.g. /opt/fsl-imx-x11/4.1.15-2.0.0)
Line 81: Line 88:
 
:Please refer to [https://docs.docker.com/engine/installation/ Docker Installation Guide] for details
 
: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 16.04 image from Docker Hub]&nbsp;</span> ===
+
=== <span style="color:#0070c0">To pull [https://hub.docker.com/r/advrisc/u18.04-imx8lbv1 ubuntu 18.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 111: Line 118:
 
  $ 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-sumo -m imx-4.14.98-2.0.0_ga.xml</span>  
 
  $ repo sync
 
  $ 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.<br/>
 +
 +
$ export GIT_SSL_NO_VERIFY=1
 +
 +
or
 +
 +
$ git config --global http.sslverify false
 +
 +
 +
<pre>''''''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.</pre>
  
 
=== <span style="color:#0070c0">Copy BSP tarball to Container</span> ===
 
=== <span style="color:#0070c0">Copy BSP tarball to Container</span> ===
Line 144: Line 164:
 
:You can get Downloads tarball (downloads_imx8-2.5.tgz) from following URL:<br/>
 
:You can get Downloads tarball (downloads_imx8-2.5.tgz) from following URL:<br/>
  
:[https://www.dropbox.com/s/912uqbtqdb4512k/downloads_imx8-2.5.tgz?dl=0 [1]]<br/>
+
:[https://www.dropbox.com/s/912uqbtqdb4512k/downloads_imx8-2.5.tgz?dl=0 [downloads_imx8-2.5.tgz]], <span style="color:#FF0000">'''md5 checksum:'''</span> <span style="color:#FF0000">'''4971ce00d3d0cdc48a5f35b584920c07'''</span><br/>
  
 
:If you get downloads tarball, you can copy to your '''${WORKSPACE}'''
 
:If you get downloads tarball, you can copy to your '''${WORKSPACE}'''
Line 191: Line 211:
 
: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>
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
  
  
Line 200: Line 238:
  
 
=== <span style="color:#0070c0">BSP Content</span> ===
 
=== <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<br/></div><div style="margin-left:1.499cm; margin-right:0cm">'''fsl-setup-release.sh'''&nbsp;: to create one new build environment<br/></div><div style="margin-left:1.499cm; margin-right:0cm">'''setup-environment'''&nbsp;: to continue an exist build environment</div>
+
<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<br/></div><div style="margin-left:1.499cm; margin-right:0cm">'''fsl-setup-release.sh'''&nbsp;: to create one new build environment<br/></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">Build Instructions</span> ==
  
Line 217: Line 254:
 
::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span></code>
 
::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span></code>
 
::<code>$ source setup-environment <span style="color:#7030a0">'''${BDIR}'''</span></code>
 
::<code>$ source setup-environment <span style="color:#7030a0">'''${BDIR}'''</span></code>
 +
 +
=== <span style="color:#0070c0">To build recovery image for OTA</span> ===
 +
 +
:Perform the following command in terminal console
 +
::<code>$ bitbake initramfs-debug-image</code><br/>
 +
:The <code>initramfs-debug-image</code>, will be located in recovery partition.<br/>
  
 
=== <span style="color:#0070c0">To build sdcard image</span> ===
 
=== <span style="color:#0070c0">To build sdcard image</span> ===
Line 222: Line 265:
 
:To create/continue a build environment<br/>
 
:To create/continue a build environment<br/>
 
:Perform the following command in terminal console
 
:Perform the following command in terminal console
::<code>$ bitbake fsl-image-qt5-validation-imx</code><br/>
+
::<code>$ bitbake fsl-image-validation-imx</code><br/>
:The file, <code>fsl-image-qt5-validation-imx</code>-<span style="color:#7030a0">'''${MC}'''</span>.sdcard.bz2, will be located in directory, ./tmp/deploy/images/<span style="color:#7030a0">'''${MC}'''</span>, while building process finished successfully.<br/>
+
:The file, <code>fsl-image-validation-imx</code>-<span style="color:#7030a0">'''${MC}'''</span>.sdcard.bz2, will be located in directory, ./tmp/deploy/images/<span style="color:#7030a0">'''${MC}'''</span>, while building process finished successfully.<br/>
  
 
=== <span style="color:#0070c0">To build toolchain installer</span> ===
 
=== <span style="color:#0070c0">To build toolchain installer</span> ===
Line 234: Line 277:
  
 
=== <span style="color:#0070c0">To build bootloader</span> ===
 
=== <span style="color:#0070c0">To build bootloader</span> ===
 
 
  
 
:To create/continue a build environment<br/>
 
:To create/continue a build environment<br/>
Line 244: Line 285:
  
 
=== <span style="color:#0070c0">To build linux kernel</span> ===
 
=== <span style="color:#0070c0">To build linux kernel</span> ===
 
 
  
 
:To create/continue a build environment<br/>
 
:To create/continue a build environment<br/>
Line 274: Line 313:
 
:Perform the following commands in terminal console
 
: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><br/>
 
::<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><br/>
::<code>$ bunzip -dk -f <span style="color:#7030a0">'''${SDCARD_IMAGE}'''</span> | of=<span style="color:#7030a0">'''${SD_DEVICE}'''</span> bs=1M</code><br/>
+
::<code>$ sudo bzcat <span style="color:#7030a0">'''${SDCARD_IMAGE}'''</span> | sudo dd of=<span style="color:#7030a0">'''${SD_DEVICE}'''</span> bs=1M</code><br/>
 
::<code>$ sync</code>
 
::<code>$ sync</code>
::<code>$ popd</code>
+
::<code>$ popd</code><br/>
  
 
== <span style="color:#0070c0">Debug console information</span> ==
 
== <span style="color:#0070c0">Debug console information</span> ==
Line 292: Line 331:
 
*You need to prepare the debug console tool. For example: "minicom" tool or "putty" tool.
 
*You need to prepare the debug console tool. For example: "minicom" tool or "putty" tool.
 
*Baud rate: 115200
 
*Baud rate: 115200
 +
 +
== <span style="color:#0070c0">One step build image</span> ==
 +
 +
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 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 [http://ess-wiki.advantech.com.tw/view/IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#Creating_boot-up_on-board_flash_from_built_sdcard_image Creating_boot-up_on-board_flash_from_built_sdcard_image] to build SD card.
  
 
= Customization =
 
= Customization =
Line 309: Line 368:
 
:Navigate to the directory where local.conf located
 
: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>
 
::<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
+
 
 +
*Method 1(Suggest): Add following one line&nbsp;to local.conf
 +
 
 +
CORE_IMAGE_EXTRA_INSTALL += "chromium-ozone-wayland"
 +
 
 +
*Method 2: Add following two lines to local.conf
  
 
  IMAGE_INSTALL_append = \
 
  IMAGE_INSTALL_append = \
Line 319: Line 383:
 
         bb.utils.contains('DISTRO_FEATURES',    'x11', 'commercial', \
 
         bb.utils.contains('DISTRO_FEATURES',    'x11', 'commercial', \
 
                                                         '', d),"''
 
                                                         '', d),"''
 +
 +
:[[IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#To_continue_an_exist_build_environment|Continue an exist build environment]] and [[IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#To_build_sdcard_image|build sdcard image]]<br/>
 +
 +
 +
 +
=== <span style="color:#0070c0">To add QtWebEngine</span> ===
 +
 +
:Put the following in <span style="color:#7030a0">'''${BSP_HOME}'''</span>/<span style="color:#7030a0">'''${BDIR'''</span>'''<span style="color:#7030a0">}</span>'''/conf/local.conf
 +
 +
::<code>IMAGE_INSTALL_append += "packagegroup-qt5-webengine"</code>
  
 
:[[IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#To_continue_an_exist_build_environment|Continue an exist build environment]] and [[IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#To_build_sdcard_image|build sdcard image]]<br/>
 
:[[IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#To_continue_an_exist_build_environment|Continue an exist build environment]] and [[IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#To_build_sdcard_image|build sdcard image]]<br/>
Line 339: Line 413:
 
::<code>$ source <span style="color:#7030a0">'''${TOOLCHAIN}'''</span>/environment-setup-aarch64-poky-linux</code>
 
::<code>$ source <span style="color:#7030a0">'''${TOOLCHAIN}'''</span>/environment-setup-aarch64-poky-linux</code>
  
== <span style="color:#0070c0">Updating bootloader</span> ==
+
== <span style="color:#0070c0">Build U-Boot in standalone environment</span> ==
 
 
=== <span style="color:#0070c0">ROM-5720</span> ===
 
  
==== <span style="color:#0070c0">Build bootloader</span> ====
+
==== <span style="color:#0070c0">Config u-boot</span> ====
  
:If you already have a exist build environment
+
make ${IMX8PROC}_${BOARD}${BOARD_REV}_${MEM_SIZE}_defconfig
:Refer to [[IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#To_continue_an_exist_build_environment|IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#To_continue_an_exist_build_environment]]
 
  
Perform the following commands:
+
eg.
  
  bitbake u-boot-imx -c compile -f && bitbake imx-boot -c compile -f && bitbake imx-boot -c deploy -f
+
  make imx8mm_rom5721a1_2G_defconfig
  
You will get new bootloader
+
==== <span style="color:#0070c0">Build u-boot</span> ====
  
  tmp/deploy/images/imx8mqrom5720a1/imx-boot-imx8mqrom5720a1-sd.bin-flash_evk
+
  make -j4
  
==== <span style="color:#0070c0">Replace u-boot</span> ====
+
== <span style="color:#0070c0">Build imx-boot image by using imx-mkimage</span> ==
:eg. SD card
 
dd if=imx-boot-imx8mqrom5720a1-sd.bin-flash_evk of=/dev/mmcblk1 bs=1k seek=33 conv=fsync
 
  
=== <span style="color:#0070c0">ROM-7720</span> ===
+
Get imx-boot tarball from our server Here we take rom5721 as an example:
  
==== <span style="color:#0070c0">Build bootloader</span> ====
+
tar zxvf 5721A1AIM20LIV90118_iMX8MM_imx-boot.tgz
 +
cd 5721A1AIM20LIV90118_iMX8MM_imx-boot/  
  
:1. download the following files:
+
In this folder , we have two script as below: Copy necessary files to imx-mkimage folder
::(1) arm cross toolchain: [https://launchpad.net/gcc-arm-embedded/4.9/4.9-2015-q3-update gcc-arm-none-eabi-4_9-2015q3-20150921-linux.tar.bz2]
 
:::(Ref. [[Media:sc_fw_port.pdf|sc_fw_port.pdf]] in the imx-scfw-porting-kit)
 
::(2) imx-atf(Yocto - imx-atf_2.0.bb): [[Media:bl31.zip|bl31.bin]]
 
::(3) firmware-imx(Yocto - firmware-imx_8.1.bb): [[Media:mx8qm-ahab-container.zip|mx8qm-ahab-container.img]]
 
::(4) imx-sc-firmware(Yocto - imx-sc-firmware_1.2.bb): [[Media:scfw_tcm.zip|scfw_tcm.bin]]
 
:::(Ref. [[Media:sc_fw_port.pdf|sc_fw_port.pdf]] in the imx-scfw-porting-kit)
 
  
:2. decompress the toolchain:
+
./cp_uboot.sh ${uboot path} ${IMX8PROC}
  
$ tar xvf gcc-arm-none-eabi-4_9-2015q3-20150921-linux.tar.bz2 -C ~
+
Make imx-boot image
  
:3. export toolchain:
+
./mk_imx-boot.sh ${IMX8PROC}
  
$ export TOOLS=~
+
eg.
  
:4. download imx-mkimage:
+
./cp_uboot.sh ../uboot-imx6 '''imx8m'''
 +
./mk_imx-boot.sh '''imx8mm'''
  
$ git clone [https://source.codeaurora.org/external/imx/imx-mkimage.git https://source.codeaurora.org/external/imx/imx-mkimage.git] -b imx_4.14.98_2.0.0_ga
+
==== <span style="color:#0070c0">Replace imx-boot</span> ====
$ cd ~/imx-mkimage
 
 
 
:5. copy the bl31.bin, mx8qm-ahab-container.img, scfw_tcm.bin and u-boot.bin to the iMX8QM/
 
 
 
:6. build the flash.bin:
 
 
 
$ make clean
 
$ make SOC=iMX8QM flash
 
 
 
==== <span style="color:#0070c0">Replace u-boot</span> ====
 
 
 
:Perform the following command to transfer to exist boot-up SD card
 
 
 
$ dd if=flash.bin of='''${SD_DEVICE}''' bs=1K seek=<offset> conv=fsync
 
  
 
:Perform the following command to transfer to on-board flash
 
:Perform the following command to transfer to on-board flash
Line 403: Line 454:
  
 
:Where offset is:
 
:Where offset is:
::33 - for i.MAX 8QuadMax A0, i.MAX 8QuadXPlus A0, i.MAX 8M Quad, and i.MAX 8M Mini
+
::33 - for i.MAX 8QuadMax A0, i.MAX 8QuadXPlus A0, i.MAX 8M Quad, and i.MAX 8M Mini<br/>
 
::32 - for i.MAX 8QuadXPlus B0 and i.MAX 8QuadMax B0<br/>
 
::32 - for i.MAX 8QuadXPlus B0 and i.MAX 8QuadMax B0<br/>
  
 
== <span style="color:#0070c0">Building & updating kernel/modules/dtb manually</span> ==
 
== <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]])
+
First, set up the cross compiling environment!
 +
 
 +
You can refer to '''[[#Setting_up_cross_compiling_environment|Setting up cross compiling environment]]'''
  
 
=== <span style="color:#0070c0">Copy BSP tarball to Container</span> ===
 
=== <span style="color:#0070c0">Copy BSP tarball to Container</span> ===
Line 433: Line 486:
  
 
:When you get error like below
 
:When you get error like below
[[File:imx8_error.jpg]]
+
 
 +
[[File:Imx8 error.jpg|RTENOTITLE]]
 +
 
 
:run command then rebuild
 
:run command then rebuild
 +
 
  $ unset LDFLAGS  
 
  $ unset LDFLAGS  
 +
  
  
Line 455: Line 512:
  
 
: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/arm64/boot/dts/freescale/".
 
: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/arm64/boot/dts/freescale/".
 +
:Note:<!--StartFragment --><font size="2" face="Microsoft JhengHei UI" color="#000000">./build_x11/tmp/work-shared/imx8qxprom5620a1/kernel-source/arch/arm64/boot/dts/freescale/imx8qxp-rom5620-a1.dts</font><!--EndFragment -->
  
 
=== <span style="color:#0070c0">Replace kernel & dts</span> ===
 
=== <span style="color:#0070c0">Replace kernel & dts</span> ===
Line 481: Line 539:
 
Disable kernel message
 
Disable kernel message
  
  setenv mmcargs setenv bootargs console=${console},${baudrate} ${smp} root=${mmcroot} ${bootargs} '''quiet'''
+
  setenv mmcargs setenv bootargs ${jh_clk} console=${console} modprobe.blacklist=${modprobe.blacklist} root=${mmcroot} video=HDMI-A-1:${videores} '''quiet'''
 
  env save
 
  env save
 
  reset
 
  reset
Line 489: Line 547:
 
:Disable debug port
 
:Disable debug port
  
setenv console
+
(1) Yocto machine setting:
env save
 
reset
 
  
*Rootfs
+
modify the meta-fsl-imx/conf/machine/${MC}.conf
 +
<pre>SERIAL_CONSOLES = ";"
 +
</pre>
  
1.Use smaller rootfs
+
(2) Uboot parameter&nbsp;setting:
  
:We can speed up boot times by using a smaller rootfs instead of fsl-image-qt5 image
+
*For the imx8mq, imx8mm,&nbsp;imx8mp:
 +
<pre>setenv console disabled
 +
env save
 +
reset
 +
</pre>
  
eg. core-image-full-cmdline, core-image-minimal
+
*For the imx8qm, imx8qxp:
 +
<pre>setenv console disabled
 +
setenv earlycon disabled
 +
env save
 +
reset</pre>
  
bitbake core-image-full-cmdline
+
*Rootfs
  
It's a console-only image with more full-featured Linux system functionality installed.
+
:TBD
  
And replace the original fsl-image-qt5 rootfs.
+
*Services
  
*Services
+
1. Using '''systemctl disable ''' remove ,we can remove unnecessary services.
 +
 
 +
systemctl disable <services>
  
1. Using '''update-rc.d''' remove ,we can remove unnecessary services.
+
eg.
  
  update-rc.d -f <basename> remove
+
  systemctl disable boottimes
  
 
= System Recovery =
 
= System Recovery =
Line 519: Line 587:
 
If you destroy the onboard flash image by accident, you can recover a system following these steps.
 
If you destroy the onboard flash image by accident, you can recover a system following these steps.
  
*Recovery by SD card
+
== Recover by SD card ==
  
 
1.Copy 5720A1AIM20LIV90022_iMX8M_flash_tool.tgz package to your desktop.
 
1.Copy 5720A1AIM20LIV90022_iMX8M_flash_tool.tgz package to your desktop.
Line 536: Line 604:
  
 
6.Enter usb disk folder, make a bootable emmc
 
6.Enter usb disk folder, make a bootable emmc
 +
 
  # cd /run/media/sda1/
 
  # cd /run/media/sda1/
 
  # cd 5720A1AIM20LIV90022_iMX8M_flash_tool/mk_inand/
 
  # cd 5720A1AIM20LIV90022_iMX8M_flash_tool/mk_inand/
Line 541: Line 610:
  
  
*Recovery by UUU tool
 
  
1.Download uuu tool from ([https://github.com/NXPmicro/mfgtools/releases/tag/uuu_1.2.135 https://github.com/NXPmicro/mfgtools/releases/tag/uuu_1.2.135])
+
== Recover by UUU tool ==
 +
 
 +
1.Download uuu tool from ([https://github.com/ADVANTECH-Corp/uuu/releases/tag/v20200619 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:
 
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 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
  
 
  1.uuu
 
  1.uuu
 
  2.imx-boot-imx8mqrom5720a1-sd.bin-flash_evk
 
  2.imx-boot-imx8mqrom5720a1-sd.bin-flash_evk
  3.fsl-image-validation-imx-imx8mqrom5720a1-20190917152605.rootfs.sdcard  
+
  3.fsl-image-validation-imx-imx8mqrom5720a1-20190917152605.rootfs.sdcard
 +
4.Image_dtb.uuu
 +
5.rootfs.uuu
 +
 
 +
3.Connect '''USB OTG''' cable from PC to device
  
3.Connect otg cable from PC to device
+
4.Set '''SW1 '''to Recovery mode, then power on
  
4.Set the correct boot mode(1,2,3-off 4-on), 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:
 
5.Perform the following command:
  
  sudo ./uuu -b emmc_all imx-boot-imx8mqrom5720a1-sd.bin-flash_evk fsl-image-validation-imx-imx8mqrom5720a1-20190917152605.rootfs.sdcard
+
'''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.
 
6.uuu tool will start recovery image to emmc.
  
7.For more usage ([https://github.com/NXPmicro/mfgtools/wiki https://github.com/NXPmicro/mfgtools/wiki])
+
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 https://github.com/NXPmicro/mfgtools/wiki])
  
 
= Package List =
 
= Package List =
Line 567: Line 681:
 
'''In BSP''', list all packages which will be built in the image
 
'''In BSP''', list all packages which will be built in the image
  
  bitbake -g '''fsl-image-qt5''' && cat pn-depends.dot | grep -v -e '-native' | grep -v digraph | grep -v -e '-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
| awk '{print $1}' | sort | uniq
 
  
File:[[:File:BSP_package1.docx|Package List]]
+
:[[:File:20191025.txt|20191025 Package List]]
  
 
Show all recipes (include non-installed packages)
 
Show all recipes (include non-installed packages)
Line 576: Line 689:
 
  bitbake -s
 
  bitbake -s
  
File:[[:File:BSP_package2.docx|Package Version List]]
+
:[[:File:package_version_20191025.txt|20191025 Package Version List]]
  
You can also check <span style="color:purple">'''${BDIR}'''</span>/tmp/deploy/images/<span style="color:purple">'''${MC}'''</span>/fsl-image-qt5-<span style="color:purple">'''${MC}'''</span>.manifest
+
You can also check <span style="color:purple">'''${BDIR}'''</span>/tmp/deploy/images/<span style="color:purple">'''${MC}'''</span>/fsl-image-qt5-validation-imx-<span style="color:purple">'''${MC}'''</span>.manifest
  
 
It will show the same content with checking by rpm tool on target board.
 
It will show the same content with checking by rpm tool on target board.
Line 586: Line 699:
 
  rpm -qa --root / --dbpath /var/lib/rpm | sort
 
  rpm -qa --root / --dbpath /var/lib/rpm | sort
  
File:[[:File:Onboard_package.docx|Package List]]
+
:[[:File:rpm_board_20191025.txt|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<span data-cke-bookmark="1" style="display: none">&nbsp;</span>
 +
*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)
 +
 
 +
[[File:1633679976526.jpg|RTENOTITLE]] [[File:1633672222378.jpg|RTENOTITLE]]
 +
 
 +
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.
 +
 
 +
 
 +
<syntaxhighlight lang="c">
 +
&pcie0{
 +
        pinctrl-names = "default";
 +
        pinctrl-0 = <&pinctrl_pcie0>;
 +
        //disable-gpio = <&tca9538 0 GPIO_ACTIVE_LOW>; <---
 +
        reset-gpio = <&gpio1 13 GPIO_ACTIVE_LOW>;
 +
        ext_osc = <1>;
 +
        status = "okay";
 +
};
 +
</syntaxhighlight>

Latest revision as of 02:51, 13 April 2022


Contents

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 A1
imx8qmrom7720a1 for ROM-7720 A1
imx8qxprom5620a1 for ROM-5620 A1
imx8mmrom5721a1 for ROM-5721 A1
imx8qxprom3620a1 for ROM-3620 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 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"
$ 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 ${WORKSPACE}
$ sudo chown adv:adv ${WORKSPACE}/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: 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 recovery image for OTA

Perform the following command in terminal console
$ bitbake initramfs-debug-image
The 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-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

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

(1) Yocto machine setting:

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

SERIAL_CONSOLES = ";"

(2) Uboot parameter setting:

  • For the imx8mq, imx8mm, imx8mp:
setenv console disabled
env save
reset
  • For the imx8qm, imx8qxp:
setenv console disabled
setenv earlycon disabled
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.

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:

1.uuu
2.imx-boot-imx8mqrom5720a1-sd.bin-flash_evk
3.fsl-image-validation-imx-imx8mqrom5720a1-20190917152605.rootfs.sdcard
4.Image_dtb.uuu
5.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,

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

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 = <&gpio1 13 GPIO_ACTIVE_LOW>;
        ext_osc = <1>;
        status = "okay";
};