Difference between revisions of "IoTGateway/BSP/Linux/iMX8/Yocto LBV9 User Guide"
Darren.huang (talk | contribs) (→How to get the MAC, Serial Number, and Manufacture Date in the QSPI flash) |
|||
(36 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
+ | |||
{{DISPLAYTITLE:Yocto Linux BSP Ver.9 User Guide for iMX8 series}} <!-- | {{DISPLAYTITLE:Yocto Linux BSP Ver.9 User Guide for iMX8 series}} <!-- | ||
{| align="right" | {| align="right" | ||
Line 21: | Line 22: | ||
<span style="color:purple">'''${MX8PROC}'''</span> : i.MX8 Processor | <span style="color:purple">'''${MX8PROC}'''</span> : i.MX8 Processor | ||
− | :mx8mq for iMX8M Dual Core | + | :mx8mq for iMX8M Dual Core |
− | :mx8mm for iMX8MM | + | :mx8mm for iMX8MM |
− | :mx8qm for iMX8QM | + | :mx8qm for iMX8QM |
− | :mx8qxp for iMX8QXP | + | :mx8qxp for iMX8QXP |
− | : | + | : |
<span style="color:purple">'''${IMX8PROC}'''</span> : i.MX8 Processor | <span style="color:purple">'''${IMX8PROC}'''</span> : i.MX8 Processor | ||
− | :imx8mq / imx8mm / imx8qm /imx8qxp | + | :imx8mq / imx8mm / imx8qm /imx8qxp |
<span style="color:purple">'''${BOARD}'''</span> : available target boards list below | <span style="color:purple">'''${BOARD}'''</span> : available target boards list below | ||
− | :rom5720 | + | :rom5720 |
− | :rom5721 | + | :rom5721 |
− | :rom7720 | + | :rom7720 |
− | :rom5620 | + | :rom5620 |
+ | :rom3620 | ||
<span style="color:purple">'''${BOARD_REV}'''</span> : board revision | <span style="color:purple">'''${BOARD_REV}'''</span> : board revision | ||
− | :a1 | + | :a1 |
<span style="color:purple">'''${MC}'''</span> : machine code combined with <span style="color:purple">'''${IMX8PROC}${BOARD}${BOARD_REV}'''</span> | <span style="color:purple">'''${MC}'''</span> : machine code combined with <span style="color:purple">'''${IMX8PROC}${BOARD}${BOARD_REV}'''</span> | ||
− | :for example, | + | :for example, |
− | ::<tt>imx8mqrom5720a1 for ROM-5720 A1</tt | + | : |
− | ::<tt>imx8qmrom7720a1 for ROM-7720 A1</tt | + | ::<tt>imx8mqrom5720a1 for ROM-5720 A1</tt> |
− | ::<tt>imx8qxprom5620a1 for ROM-5620 A1</tt | + | ::<tt>imx8qmrom7720a1 for ROM-7720 A1</tt> |
− | ::<tt>imx8mmrom5721a1 for ROM-5721 A1</tt>< | + | ::<tt>imx8qxprom5620a1 for ROM-5620 A1</tt> |
+ | ::<tt>imx8mmrom5721a1 for ROM-5721 A1</tt> | ||
+ | ::<tt>imx8qxprom3620a1 for ROM-3620 A1</tt> | ||
− | :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 |
− | ::<code>$ source setup-environment</code> | + | ::<code>$ source setup-environment</code> |
<span style="color:purple">'''${MEM_SIZE}'''</span> : memory size | <span style="color:purple">'''${MEM_SIZE}'''</span> : memory size | ||
− | : 2G/4G | + | : 2G/4G |
<span style="color:purple">'''${SD_DEVICE}'''</span> : device name of SD card in Linux (e.g. /dev/sdf) | <span style="color:purple">'''${SD_DEVICE}'''</span> : device name of SD card in Linux (e.g. /dev/sdf) | ||
Line 66: | Line 70: | ||
<span style="color:purple">'''${UBOOT}'''</span> :u-boot version(e.g. 2016.03) | <span style="color:purple">'''${UBOOT}'''</span> :u-boot version(e.g. 2016.03) | ||
− | <span style="color:purple">'''${KERNEL}'''</span> : linux kernel version(e.g. 4. | + | <span style="color:purple">'''${KERNEL}'''</span> : linux kernel version(e.g. 4.14.98) |
<span style="color:purple">'''${TOOLCHAIN}'''</span> : toolchain installed directory(e.g. /opt/fsl-imx-x11/4.1.15-2.0.0) | <span style="color:purple">'''${TOOLCHAIN}'''</span> : toolchain installed directory(e.g. /opt/fsl-imx-x11/4.1.15-2.0.0) | ||
Line 72: | Line 76: | ||
debug console / serial console | debug console / serial console | ||
− | :serial terminal program (e.g. minicom, putty, teraterm ...) that serial port is configured to 115200 8N1 | + | :serial terminal program (e.g. minicom, putty, teraterm ...) that serial port is configured to 115200 8N1 |
terminal console | terminal console | ||
− | :terminal program (e.g. gnome-terminal, xfce4-terminal ...) | + | :terminal program (e.g. gnome-terminal, xfce4-terminal ...) |
== <font color="#0070c0">Docker install and setting</font> == | == <font color="#0070c0">Docker install and setting</font> == | ||
Line 84: | Line 88: | ||
=== <span style="color:#0070c0">To install Docker Engine on your platform</span> === | === <span style="color:#0070c0">To install Docker Engine on your platform</span> === | ||
− | :Please refer to [https://docs.docker.com/engine/installation/ Docker Installation Guide] for details | + | :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/ | + | === <span style="color:#0070c0">To pull [https://hub.docker.com/r/advrisc/u18.04-imx8lbv1 ubuntu 18.04 image from Docker Hub] </span> === |
− | :<code>$ docker pull advrisc/ | + | :<code>$ docker pull advrisc/u18.04-imx8lbv1</code> |
=== <span style="color:#0070c0">To create container</span> === | === <span style="color:#0070c0">To create container</span> === | ||
− | :<code>$ docker run --privileged -it --name '''${CONTAINER_NAME}''' -v '''${WORKSPACE}''':/home/adv/adv-release-bsp -v /dev:/dev advrisc/ | + | :<code>$ docker run --privileged -it --name '''${CONTAINER_NAME}''' -v '''${WORKSPACE}''':/home/adv/adv-release-bsp -v /dev:/dev advrisc/u18.04-imx8lbv1 /bin/bash</code> |
== <span style="color:#0070c0">Get BSP</span> == | == <span style="color:#0070c0">Get BSP</span> == | ||
− | :You have two methods to put BSP into container created above | + | :You have two methods to put BSP into container created above |
=== Download_BSP_From_GitHub === | === Download_BSP_From_GitHub === | ||
− | :The following example shows how to download the Advantech Yocto 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. | + | :For this example, a directory called '''adv-release-bsp''' is created for the project. |
− | :Refer to [[IoTGateway/BSP/Linux/iMX8/OS_Support_List|IoTGateway/BSP/Linux/iMX8/OS_Support_List]] , Official version "'''imx8LBV90029" '''is taken as an example : | + | :Refer to [[IoTGateway/BSP/Linux/iMX8/OS_Support_List|IoTGateway/BSP/Linux/iMX8/OS_Support_List]] , Official version "'''imx8LBV90029" '''is taken as an example : |
<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 | ||
Line 112: | Line 116: | ||
$ 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-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. | ||
+ | |||
+ | $ 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> === | ||
− | :If you have BSP tarball (eg. imx8LBV90029_2019-10-23.tgz), then you have to copy it into container. | + | :If you have BSP tarball (eg. imx8LBV90029_2019-10-23.tgz), then you have to copy it into container. |
Follow the steps below: | Follow the steps below: | ||
Line 143: | Line 160: | ||
== <span style="color:#0070c0">Downloads tarball</span> == | == <span style="color:#0070c0">Downloads tarball</span> == | ||
− | :Not necessarily step | + | :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. | + | :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: | + | :You can get Downloads tarball (downloads_imx8-2.5.tgz) from following URL: |
− | :[https://www.dropbox.com/s/912uqbtqdb4512k/downloads_imx8-2.5.tgz?dl=0 [ | + | :[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> |
− | :If you get downloads tarball, you can copy to your '''${WORKSPACE}''' | + | :If you get downloads tarball, you can copy to your '''${WORKSPACE}''' |
Follow the steps below: | Follow the steps below: | ||
Line 180: | Line 197: | ||
== <span style="color:#0070c0">Introducing BSP</span> == | == <span style="color:#0070c0">Introducing BSP</span> == | ||
− | :The BSP is based on Yocto Project with Freescale enhanced features for i.MX8, plus specific target board features from Advantech Inc.. | + | :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, | + | :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. | 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 | + | :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. | to the sources directory. This sets up the recipes that are used to build the project. | ||
Line 191: | Line 208: | ||
=== <span style="color:#0070c0">Naming Rule</span> === | === <span style="color:#0070c0">Naming Rule</span> === | ||
− | :The tarball/prebuilt image name is consist of the model name followed by "LB" or "LI" plus version number and released date. | + | :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''' | + | :For example, '''BSP file name: imx8LBV90010_2019-08-27.tgz''' |
− | :which , "LB" is acronym of <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''B'''</span>SP, | + | :which , "LB" is acronym of <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''B'''</span>SP, |
− | : "V90010" stands for <span style="color:#ff0000">'''V'''</span>ersion <font color="#ff0000">'''9'''</font>.<span style="color:#ff0000">'''0010'''</span><nowiki>.</nowiki> | + | : "V90010" stands for <span style="color:#ff0000">'''V'''</span>ersion <font color="#ff0000">'''9'''</font>.<span style="color:#ff0000">'''0010'''</span> <nowiki>.</nowiki> |
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
− | :For example, '''Yocto image name: ''''''5720A1AIM20LIV90010_iMX8M_2019-08-27.img.gz''' | + | :For example, '''Yocto image name: ''''''5720A1AIM20LIV90010_iMX8M_2019-08-27.img.gz''' |
− | :which "5720A1" stands for <span style="color:#ff0000">'''ROM-5720 A1'''</span | + | :which "5720A1" stands for <span style="color:#ff0000">'''ROM-5720 A1'''</span> |
− | : "LI" is acronym for prebuilt <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''I'''</span>mage | + | : "LI" is acronym for prebuilt <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''I'''</span>mage |
− | |||
+ | | ||
=== <span style="color:#0070c0">BSP Content</span> === | === <span style="color:#0070c0">BSP Content</span> === | ||
− | <div style="margin-left:0.499cm; | + | <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/''' : meta layer by Advantech</div> <div style="margin-left:1.998cm; margin-right:0cm">'''meta-fsl-*/''' : meta layer by Freescale</div> <div style="margin-left:1.499cm; margin-right:0cm">'''fsl-setup-release.sh''' : to create one new build environment</div> <div style="margin-left:1.499cm; margin-right:0cm">'''setup-environment''' : to continue an exist build environment</div> |
== <span style="color:#0070c0">Build Instructions</span> == | == <span style="color:#0070c0">Build Instructions</span> == | ||
=== <span style="color:#0070c0">To create one new build environment</span> === | === <span style="color:#0070c0">To create one new build environment</span> === | ||
− | :Perform the following commands in terminal console | + | :Perform the following commands in terminal console |
− | ::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span></code> | + | ::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span></code> |
− | ::<code>$ MACHINE=<span style="color:#7030a0">'''${MC}'''</span> </code> <code>DISTRO=fsl-imx-xwayland </code><code>source fsl-setup-release.sh -b <span style="color:#7030a0">'''${BDIR}'''</span> </code> | + | ::<code>$ MACHINE=<span style="color:#7030a0">'''${MC}'''</span> </code> <code>DISTRO=fsl-imx-xwayland </code><code>source fsl-setup-release.sh -b <span style="color:#7030a0">'''${BDIR}'''</span></code> |
− | :You need to read and accept the EULA. | + | :You need to read and accept the EULA. |
− | :[[File:Accept EULA.png|RTENOTITLE]] | + | :[[File:Accept EULA.png|RTENOTITLE]] |
=== <span style="color:#0070c0">To continue an exist build environment</span> === | === <span style="color:#0070c0">To continue an exist build environment</span> === | ||
− | :Perform the following commands in terminal console | + | :Perform the following commands in terminal console |
− | ::<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> | ||
+ | :The <code>initramfs-debug-image</code>, will be located in recovery partition. | ||
=== <span style="color:#0070c0">To build sdcard image</span> === | === <span style="color:#0070c0">To build sdcard image</span> === | ||
− | :To create/continue a build environment | + | :To create/continue a build environment |
− | :Perform the following command in terminal console | + | :Perform the following command in terminal console |
− | ::<code>$ bitbake fsl-image-validation-imx</code> | + | ::<code>$ bitbake fsl-image-validation-imx</code> |
− | :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. | + | :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. |
=== <span style="color:#0070c0">To build toolchain installer</span> === | === <span style="color:#0070c0">To build toolchain installer</span> === | ||
− | :To create/continue a build environment | + | :To create/continue a build environment |
− | :Perform the following command in terminal console | + | :Perform the following command in terminal console |
− | ::<code>$ bitbake meta-toolchain</code> | + | ::<code>$ bitbake meta-toolchain</code> |
− | :The below installer will be located in the directory "./tmp/deploy/sdk". | + | :The below installer will be located in the directory "./tmp/deploy/sdk". |
− | ::<tt>fsl-imx-xwayland-glibc-x86_64-meta-toolchain-aarch64-toolchain-<span style="color:#7030a0">'''${KERNEL}'''</span>-sumo.sh</tt> | + | ::<tt>fsl-imx-xwayland-glibc-x86_64-meta-toolchain-aarch64-toolchain-<span style="color:#7030a0">'''${KERNEL}'''</span>-sumo.sh</tt> |
=== <span style="color:#0070c0">To build bootloader</span> === | === <span style="color:#0070c0">To build bootloader</span> === | ||
− | :To create/continue a build environment | + | :To create/continue a build environment |
− | :Perform the following command in terminal console | + | :Perform the following command in terminal console |
− | ::<code>$ bitbake imx-boot</code> | + | ::<code>$ bitbake imx-boot</code> |
− | |||
+ | | ||
=== <span style="color:#0070c0">To build linux kernel</span> === | === <span style="color:#0070c0">To build linux kernel</span> === | ||
− | :To create/continue a build environment | + | :To create/continue a build environment |
− | :If you operate on docker images, please install tmux application before running this command | + | :If you operate on docker images, please install tmux application before running this command |
− | :::<code>$ sudo apt-get install tmux</code> | + | :: |
− | :Type following command to enter tmux | + | :::<code>$ sudo apt-get install tmux</code> |
− | :::<code>$ tmux</code> | + | :Type following command to enter tmux |
− | :Perform the following command in terminal console to show up menuconfig | + | :: |
− | :::<code>$ bitbake linux-imx -c menuconfig</code> | + | :::<code>$ tmux</code> |
− | :After edit menuconfig, type following command to exit tmux windows | + | :Perform the following command in terminal console to show up menuconfig |
− | :::<code>$ exit</code> | + | :: |
− | :to build kernel image | + | :::<code>$ bitbake linux-imx -c menuconfig</code> |
− | :::<code>$ bitbake linux-imx</code> | + | :After edit menuconfig, type following command to exit tmux windows |
− | :The two files, Image & Image-<span style="color:#7030a0">'''adv-${IMX8PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD'''</span>'''<span style="color:#7030a0">_REV</span><span style="color:#7030a0">}</span>'''.dtb, will be located in the directory, ./tmp/deploy/images/<span style="color:#7030a0">'''${MC}'''</span>. | + | :: |
+ | :::<code>$ exit</code> | ||
+ | :to build kernel image | ||
+ | :: | ||
+ | :::<code>$ bitbake linux-imx</code> | ||
+ | :The two files, Image & Image-<span style="color:#7030a0">'''adv-${IMX8PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD'''</span>'''<span style="color:#7030a0">_REV</span><span style="color:#7030a0">}</span>'''.dtb, will be located in the directory, ./tmp/deploy/images/<span style="color:#7030a0">'''${MC}'''</span>. | ||
== <span style="color:#0070c0">Creating boot-up on-board flash from prebuilt image</span> == | == <span style="color:#0070c0">Creating boot-up on-board flash from prebuilt image</span> == | ||
Line 274: | Line 312: | ||
=== <span style="color:#0070c0">To create one boot-up SD card</span> === | === <span style="color:#0070c0">To create one boot-up SD card</span> === | ||
− | :Perform the following command in terminal console | + | :Perform the following command in terminal console |
− | ::<code># gunzip -c '''<span style="color:#7030a0">${PREBUILT_IMAGE</span>'''} | dd of=<span style="color:#7030a0">'''${SD_DEVICE}'''</span> bs=1M</code | + | ::<code># gunzip -c '''<span style="color:#7030a0">${PREBUILT_IMAGE</span>'''} | dd of=<span style="color:#7030a0">'''${SD_DEVICE}'''</span> bs=1M</code> |
− | ::<code># sync</code> | + | ::<code># sync</code> |
== <span style="color:#0070c0">Creating boot-up on-board flash from built sdcard image</span> == | == <span style="color:#0070c0">Creating boot-up on-board flash from built sdcard image</span> == | ||
Line 282: | Line 320: | ||
=== <span style="color:#0070c0">To create one boot-up SD card</span> === | === <span style="color:#0070c0">To create one boot-up SD card</span> === | ||
− | :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 | + | ::<code>$ pushd <span style="color:#7030a0">'''${BSP_HOME}'''</span>/<span style="color:#7030a0">'''${BDIR}'''</span>/tmp/deploy/images/<span style="color:#7030a0">'''${MC}'''</span></code> |
− | ::<code>$ | + | ::<code>$ sudo bzcat <span style="color:#7030a0">'''${SDCARD_IMAGE}'''</span> | sudo dd of=<span style="color:#7030a0">'''${SD_DEVICE}'''</span> bs=1M</code> |
− | ::<code>$ sync</code> | + | ::<code>$ sync</code> |
− | ::<code>$ popd</code> | + | ::<code>$ popd</code> |
== <span style="color:#0070c0">Debug console information</span> == | == <span style="color:#0070c0">Debug console information</span> == | ||
Line 294: | Line 332: | ||
=== <span style="color:#0070c0">Preparing for hardware device</span> === | === <span style="color:#0070c0">Preparing for hardware device</span> === | ||
− | *The following URL provides information about the debug port slot and the debug port line for each device | + | *The following URL provides information about the debug port slot and the debug port line for each device |
[[Debug_Port_Information#i.MX6|Debug Port Information]] | [[Debug_Port_Information#i.MX6|Debug Port Information]] | ||
Line 300: | Line 338: | ||
=== <span style="color:#0070c0">Preparing for software tool</span> === | === <span style="color:#0070c0">Preparing for software tool</span> === | ||
− | *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> == | == <span style="color:#0070c0">One step build image</span> == | ||
Line 310: | Line 348: | ||
$ 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] | $ 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 | Build image | ||
− | $ sudo ./ | + | $ sudo ./adv_imx8_build.sh ${BOARD} |
− | $ sudo ./ | + | $ sudo ./adv_imx8_build.sh rom5720 |
Our image will be in workspace folder. | Our image will be in workspace folder. | ||
Line 328: | Line 367: | ||
=== <span style="color:#0070c0">To add tcf-agent & openssh-sftp-server</span> === | === <span style="color:#0070c0">To add tcf-agent & openssh-sftp-server</span> === | ||
− | :Navigate to the directory where fsl-image-adv.inc located | + | :Navigate to the directory where fsl-image-adv.inc located |
− | ::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span>/sources/meta-advantech/meta-fsl-imx/recipes-fsl/images</code> | + | ::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span>/sources/meta-advantech/meta-fsl-imx/recipes-fsl/images</code> |
− | :Add following line to fsl-image-adv.inc | + | :Add following line to fsl-image-adv.inc |
− | ::<code>IMAGE_INSTALL += " tcf-agent openssh-sftp-server "</code> | + | ::<code>IMAGE_INSTALL += " tcf-agent openssh-sftp-server "</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]] | + | :[[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]] |
=== <span style="color:#0070c0">To add chromium browser</span> === | === <span style="color:#0070c0">To add chromium browser</span> === | ||
− | :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> |
− | *Method 1(Suggest): Add following one line to local.conf | + | *Method 1(Suggest): Add following one line to local.conf |
CORE_IMAGE_EXTRA_INSTALL += "chromium-ozone-wayland" | CORE_IMAGE_EXTRA_INSTALL += "chromium-ozone-wayland" | ||
− | *Method 2: Add following two lines to local.conf | + | *Method 2: Add following two lines to local.conf |
IMAGE_INSTALL_append = \ | IMAGE_INSTALL_append = \ | ||
Line 354: | Line 393: | ||
'', 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]]< | + | :[[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]] |
+ | |||
+ | | ||
+ | |||
+ | === <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]] | ||
== <span style="color:#0070c0">Setting up SDK</span> == | == <span style="color:#0070c0">Setting up SDK</span> == | ||
− | :Please follow the section,[[IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#To_build_toolchain_installer|<span style="color:#FF0000">To build toolchain installer</span>]], to build one toolchain installer | + | :Please follow the section,[[IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#To_build_toolchain_installer|<span style="color:#FF0000">To build toolchain installer</span>]], to build one toolchain installer |
− | :Perform the following command in terminal console | + | :Perform the following command in terminal console |
− | ::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span>/<span style="color:#7030a0">'''${BDIR}'''</span>/tmp/deploy/sdk</code> | + | ::<code>$ cd <span style="color:#7030a0">'''${BSP_HOME}'''</span>/<span style="color:#7030a0">'''${BDIR}'''</span>/tmp/deploy/sdk</code> |
− | ::<code>$ sudo ./fsl-imx-xwayland-glibc-x86_64-meta-toolchain-aarch64-toolchain-4.14-sumo.sh</code> | + | ::<code>$ sudo ./fsl-imx-xwayland-glibc-x86_64-meta-toolchain-aarch64-toolchain-4.14-sumo.sh</code> |
− | :Enter new installed directory or just press <code>Enter</code> to use default directory. | + | :Enter new installed directory or just press <code>Enter</code> to use default directory. |
− | :While <code>Proceed[y/n]?</code> shows up, please enter the correct one. | + | :While <code>Proceed[y/n]?</code> shows up, please enter the correct one. |
− | :Waiting for the SDK installed (while the following messages show up completely) | + | :Waiting for the SDK installed (while the following messages show up completely) |
− | ::[[File:Setting up sdk 3.png|RTENOTITLE]] | + | ::[[File:Setting up sdk 3.png|RTENOTITLE]] |
== <span style="color:#0070c0">Setting up cross compiling environment</span> == | == <span style="color:#0070c0">Setting up cross compiling environment</span> == | ||
− | :SDK has been set up (ref.[[#Setting_up_SDK|<span style="color:#FF0000">Setting up SDK</span>]]) | + | :SDK has been set up (ref.[[#Setting_up_SDK|<span style="color:#FF0000">Setting up SDK</span>]]) |
− | :Perform the following command in terminal console | + | :Perform the following command in terminal console |
− | ::<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">Build U-Boot in standalone environment</span> == | == <span style="color:#0070c0">Build U-Boot in standalone environment</span> == | ||
Line 409: | Line 459: | ||
==== <span style="color:#0070c0">Replace imx-boot</span> ==== | ==== <span style="color:#0070c0">Replace imx-boot</span> ==== | ||
− | :Perform the following command to transfer to on-board flash | + | :Perform the following command to transfer to on-board flash |
$ dd if=flash.bin of=/dev/mmcblk0 bs=1K seek=<offset> conv=fsync | $ dd if=flash.bin of=/dev/mmcblk0 bs=1K seek=<offset> conv=fsync | ||
− | :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 |
− | ::32 - for i.MAX 8QuadXPlus B0 and i.MAX 8QuadMax B0 | + | ::32 - for i.MAX 8QuadXPlus B0 and i.MAX 8QuadMax B0 |
== <span style="color:#0070c0">Building & updating kernel/modules/dtb manually</span> == | == <span style="color:#0070c0">Building & updating kernel/modules/dtb manually</span> == | ||
− | + | 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 432: | Line 484: | ||
=== <span style="color:#0070c0">Config kernel</span> === | === <span style="color:#0070c0">Config kernel</span> === | ||
− | :Configure linux kernel | + | :Configure linux kernel |
$ cd linux-imx6 | $ cd linux-imx6 | ||
Line 439: | Line 491: | ||
$ make menuconfig | $ make menuconfig | ||
− | :Start building linux kernel | + | :Start building linux kernel |
$ make -j4 Image | $ make -j4 Image | ||
− | :When you get error like below | + | :When you get error like below |
[[File:Imx8 error.jpg|RTENOTITLE]] | [[File:Imx8 error.jpg|RTENOTITLE]] | ||
− | :run command then rebuild | + | :run command then rebuild |
$ unset LDFLAGS | $ unset LDFLAGS | ||
+ | | ||
+ | :The kernel image file, Image, is located in the directory "./arch/arm64/boot/". | ||
− | + | :Start building kernel modules | |
− | |||
− | :Start building kernel modules | ||
$ make -j4 modules | $ make -j4 modules | ||
− | :Copy all modules to a temporary rootfs directory, "~/temp/rootfs" | + | :Copy all modules to a temporary rootfs directory, "~/temp/rootfs" |
$ make modules_install INSTALL_MOD_PATH=~/temp/rootfs | $ make modules_install INSTALL_MOD_PATH=~/temp/rootfs | ||
− | :Building device tree blob | + | :Building device tree blob |
$ make -j4 freescale/adv-<span style="color:#7030a0">'''${IMX8PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD_REV}'''</span>.dtb | $ make -j4 freescale/adv-<span style="color:#7030a0">'''${IMX8PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD_REV}'''</span>.dtb | ||
Line 469: | Line 521: | ||
$ make -j4 freescale/adv-imx8mq-rom5720-a1.dtb | $ make -j4 freescale/adv-imx8mq-rom5720-a1.dtb | ||
− | :The device tree blob, <span style="color:#7030a0">'''${IMX6PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD_REV}'''</span>.dtb, is located in the directory "./arch/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 color="#000000" face="Microsoft JhengHei UI" size="2">./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> === | ||
− | :Replace kernel | + | :Replace kernel |
− | ::copy Image to SDcard or emmc | + | ::copy Image to SDcard or emmc |
− | :Replace dtb file | + | :Replace dtb file |
− | ::copy dtb file to SDcard or emmc | + | ::copy dtb file to SDcard or emmc |
== <span style="color:#0070c0">Improve boot speed</span> == | == <span style="color:#0070c0">Improve boot speed</span> == | ||
− | *Bootloader | + | *Bootloader |
1.bootdelay time | 1.bootdelay time | ||
− | :We can cancel the bootdelay time by setting bootloader environment value. | + | :We can cancel the bootdelay time by setting bootloader environment value. |
setenv bootdelay 0 | setenv bootdelay 0 | ||
Line 492: | Line 545: | ||
2.Disable console | 2.Disable console | ||
− | :Disable debug message output can also improve boot speed | + | :Disable debug message output can also improve boot speed |
Disable kernel message | Disable kernel message | ||
Line 502: | Line 555: | ||
Or | Or | ||
− | :Disable debug port | + | :Disable debug port |
+ | |||
+ | (1) Yocto machine setting: | ||
+ | |||
+ | modify the meta-fsl-imx/conf/machine/${MC}.conf | ||
+ | <pre>SERIAL_CONSOLES = ";" | ||
+ | </pre> | ||
+ | |||
+ | (2) Uboot parameter setting: | ||
+ | |||
+ | *For the imx8mq, imx8mm, imx8mp: | ||
+ | <pre>setenv console disabled | ||
+ | env save | ||
+ | reset | ||
+ | </pre> | ||
− | + | *For the imx8qm, imx8qxp: | |
− | + | <pre>setenv console disabled | |
− | + | setenv earlycon disabled | |
+ | env save | ||
+ | reset</pre> | ||
− | *Rootfs | + | *Rootfs |
− | :TBD | + | :TBD |
− | *Services | + | *Services |
1. Using '''systemctl disable ''' remove ,we can remove unnecessary services. | 1. Using '''systemctl disable ''' remove ,we can remove unnecessary services. | ||
Line 528: | Line 597: | ||
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. | ||
− | + | == 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 550: | Line 619: | ||
# sudo ./mksd-linux.sh /dev/mmcblk0 | # sudo ./mksd-linux.sh /dev/mmcblk0 | ||
+ | | ||
+ | == 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 | ||
− | + | 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: | 5.Perform the following command: | ||
Line 583: | Line 671: | ||
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 591: | Line 693: | ||
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 | 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 | ||
− | :[[:File:20191025.txt|20191025 Package List]] | + | :[[:File:20191025.txt|20191025 Package List]] |
Show all recipes (include non-installed packages) | Show all recipes (include non-installed packages) | ||
Line 597: | Line 699: | ||
bitbake -s | bitbake -s | ||
− | :[[:File:package_version_20191025.txt|20191025 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-validation-imx-<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 | ||
Line 607: | Line 709: | ||
rpm -qa --root / --dbpath /var/lib/rpm | sort | rpm -qa --root / --dbpath /var/lib/rpm | sort | ||
− | :[[:File:rpm_board_20191025.txt|20191025 RPM on Board List]] | + | :[[:File:rpm_board_20191025.txt|20191025 RPM on Board List]] |
= Device Tree Source file select = | = Device Tree Source file select = | ||
Line 621: | Line 723: | ||
== ROM-5721 == | == ROM-5721 == | ||
− | *Display | + | *Display |
− | **DSI to LVDS | + | **DSI to LVDS |
− | ***g070vw01 | + | ***g070vw01 |
− | ****adv-imx8mm-rom5721-a1.dtb | + | ****adv-imx8mm-rom5721-a1.dtb |
− | ***g150xgel05 | + | ***g150xgel05 |
− | ****adv-imx8mm-rom5721-a1-dsi2lvds-g150xgel05.dtb | + | ****adv-imx8mm-rom5721-a1-dsi2lvds-g150xgel05.dtb |
− | ***g215hvn01 | + | ***g215hvn01 |
− | ****adv-imx8mm-rom5721-a1-dsi2lvds-g215hvn01.dtb | + | ****adv-imx8mm-rom5721-a1-dsi2lvds-g215hvn01.dtb |
− | **DSI to DP | + | **DSI to DP |
− | ***adv-imx8mm-rom5721-a1-dsi2dp.dtb | + | ***adv-imx8mm-rom5721-a1-dsi2dp.dtb |
− | **DSI to HDMI | + | **DSI to HDMI |
− | ***adv-imx8mm-rom5721-a1-adv7535.dtb | + | ***adv-imx8mm-rom5721-a1-adv7535.dtb |
− | **DSI | + | **DSI |
− | ***auog101uan02 | + | ***auog101uan02 |
− | ****adv-imx8mm-rom5721-a1-auog101uan02.dtb | + | ****adv-imx8mm-rom5721-a1-auog101uan02.dtb |
− | *M.2 SDIO | + | *M.2 SDIO |
− | **Adjust CN43~CN48 | + | **Adjust CN43~CN48 |
− | **adv-imx8mm-rom5721-a1-m2-sdio.dtb | + | **adv-imx8mm-rom5721-a1-m2-sdio.dtb |
+ | *M.2 I2S | ||
+ | **adv-imx8mm-rom5721-a1-m2-i2s.dtb | ||
== ROM-5720 == | == ROM-5720 == | ||
− | *Display | + | *Display |
− | **DSI to HDMI | + | **DSI to HDMI |
− | ***adv-imx8mq-rom5720-a1-dcss-adv7535-b3.dtb | + | ***adv-imx8mq-rom5720-a1-dcss-adv7535-b3.dtb |
− | ***adv-imx8mq-rom5720-a1-lcdif-adv7535.dtb | + | ***adv-imx8mq-rom5720-a1-lcdif-adv7535.dtb |
− | **DSI | + | **DSI |
− | ***auog101uan02 | + | ***auog101uan02 |
− | ****adv-imx8mq-rom5720-a1-dcss-auog101uan02.dtb | + | ****adv-imx8mq-rom5720-a1-dcss-auog101uan02.dtb |
− | **Dual Display | + | **Dual Display |
− | ***DSI to HDMI + HDMI | + | ***DSI to HDMI + HDMI |
− | ****adv-imx8mq-rom5720-a1-dual-display.dtb | + | ****adv-imx8mq-rom5720-a1-dual-display.dtb |
− | *M.2 SDIO | + | *M.2 SDIO |
− | **Adjust CN43~CN48 | + | **Adjust CN43~CN48 |
− | **adv-imx8mq-rom5720-a1-m2-sdio.dtb | + | **adv-imx8mq-rom5720-a1-m2-sdio.dtb |
+ | *M.2 I2S | ||
+ | **adv-imx8mq-rom5720-a1-m2-i2s.dtb | ||
== ROM-5620 == | == ROM-5620 == | ||
− | *Display | + | *Display |
− | **LVDS | + | **LVDS |
− | ***g070vw01 | + | ***g070vw01 |
− | ****adv-imx8mxp-rom5620-a1.dtb | + | ****adv-imx8mxp-rom5620-a1.dtb |
− | ***g150xgel05 | + | ***g150xgel05 |
− | ****adv-imx8qxp-rom5620-a1-lvds-chimei.dtb | + | ****adv-imx8qxp-rom5620-a1-lvds-chimei.dtb |
− | ***g215hvn01 | + | ***g215hvn01 |
− | ****adv-imx8qxp-rom5620-a1-lvds-dual.dtb | + | ****adv-imx8qxp-rom5620-a1-lvds-dual.dtb |
− | **LVDS to HDMI | + | **LVDS to HDMI |
− | ***adv-imx8qxp-rom5620-a1-hdmi-bridge.dtb | + | ***adv-imx8qxp-rom5620-a1-hdmi-bridge.dtb |
− | **DSI to HDMI | + | **DSI to HDMI |
− | ***adv-imx8qxp-rom5620-a1-hdmi-bridge.dtb | + | ***adv-imx8qxp-rom5620-a1-hdmi-bridge.dtb |
− | **DSI | + | **DSI |
− | ***auog101uan02 | + | ***auog101uan02 |
− | ****adv-imx8qxp-rom5620-a1-auog101uan02.dtb | + | ****adv-imx8qxp-rom5620-a1-auog101uan02.dtb |
− | *M.2 SDIO | + | *M.2 SDIO |
− | **Adjust CN43~CN48 | + | **Adjust CN43~CN48 |
− | **adv-imx8qxp-rom5620-a1-m2-sdio.dtb | + | **adv-imx8qxp-rom5620-a1-m2-sdio.dtb |
− | *2-nd QSPI | + | *2-nd QSPI |
− | **adv-imx8qxp-rom5620-a1-qspi-b.dtb | + | **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 == | == ROM-7720 == | ||
− | *Display | + | *Display |
− | **HDMI | + | **HDMI |
− | ***adv-imx8qm-rom7720-a1.dtb | + | ***adv-imx8qm-rom7720-a1.dtb |
− | **LVDS | + | **LVDS |
− | ***g070vw01 | + | ***g070vw01 |
− | ****adv-imx8qm-rom7720-a1_lvds0.dtb | + | ****adv-imx8qm-rom7720-a1_lvds0.dtb |
− | ****adv-imx8qm-rom7720-a1_lvds1.dtb | + | ****adv-imx8qm-rom7720-a1_lvds1.dtb |
− | ***g215hvn01 | + | ***g215hvn01 |
− | ****adv-imx8qm-rom7720-a1_lvds_dual.dtb | + | ****adv-imx8qm-rom7720-a1_lvds_dual.dtb |
− | **HDMI + LVDS | + | **HDMI + LVDS |
− | ***HDMI + g070vw01 | + | ***HDMI + g070vw01 |
− | ****adv-imx8qm-rom7720-a1_hdmi_lvds0.dtb | + | ****adv-imx8qm-rom7720-a1_hdmi_lvds0.dtb |
− | ****adv-imx8qm-rom7720-a1_hdmi_lvds1.dtb | + | ****adv-imx8qm-rom7720-a1_hdmi_lvds1.dtb |
− | ***HDMI + g215hvn01 | + | ***HDMI + g215hvn01 |
− | ****adv-imx8qm-rom7720-a1_hdmi_lvds_dual.dtb | + | ****adv-imx8qm-rom7720-a1_hdmi_lvds_dual.dtb |
− | **LVDS to HDMI | + | **LVDS to HDMI |
− | ***adv-imx8qm-rom7720-a1-it6263.dtb<span | + | ***adv-imx8qm-rom7720-a1-it6263.dtb<span style="display: none"> </span> |
− | *Audio Codec | + | *Audio Codec |
− | **adv-imx8qm-rom7720-a1-sgtl5000.dtb | + | **adv-imx8qm-rom7720-a1-sgtl5000.dtb |
= Burn-in Test = | = 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. | 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> | ||
+ | |||
+ | = How to get the MAC, Serial Number, and Manufacture Date in the QSPI flash= | ||
+ | |||
+ | MAC 0: | ||
+ | <syntaxhighlight lang="c"> | ||
+ | READ_DATA=`dd if=/dev/mtdblock0 bs=1 skip=$((0xd0000)) count=6 2> /dev/null | hexdump -e '16/1 "%02x " "\n"' | sed 's/ /:/g' | cut -c 1-17` | ||
+ | echo $READ_DATA | ||
+ | </syntaxhighlight> | ||
+ | |||
+ | MAC 1: | ||
+ | <syntaxhighlight lang="c"> | ||
+ | READ_DATA=`dd if=/dev/mtdblock0 bs=1 skip=$((0xd0400)) count=6 2> /dev/null | hexdump -e '16/1 "%02x " "\n"' | sed 's/ /:/g' | cut -c 1-17` | ||
+ | echo $READ_DATA | ||
+ | </syntaxhighlight> | ||
+ | |||
+ | Serial Number: | ||
+ | <syntaxhighlight lang="c"> | ||
+ | READ_DATA=`dd if=/dev/mtdblock0 bs=1 skip=$((0xd0006)) count=10 2> /dev/null | cut -c 1-10` | ||
+ | echo $READ_DATA | ||
+ | </syntaxhighlight> | ||
+ | |||
+ | Manufacture Date: | ||
+ | <syntaxhighlight lang="c"> | ||
+ | READ_DATA=`dd if=/dev/mtdblock0 bs=1 skip=$((0xd0010)) count=14 2> /dev/null | cut -c 1-14` | ||
+ | READ_DATA=`echo $READ_DATA | cut -c 1-4`-`echo $READ_DATA | cut -c 5-6`-`echo $READ_DATA | cut -c 7-8`_`echo $READ_DATA | cut -c 9-10`-`echo $READ_DATA | cut -c 11-12`-`echo $READ_DATA | cut -c 13-14` | ||
+ | echo $READ_DATA | ||
+ | </syntaxhighlight> |
Latest revision as of 10:45, 31 May 2023
Contents
- 1 Getting Started
- 2 Customization
- 3 System Recovery
- 4 Package List
- 5 Device Tree Source file select
- 6 Burn-in Test
- 7 About DB5901 bottom board setting
- 8 How to get the MAC, Serial Number, and Manufacture Date in the QSPI flash
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
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.
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
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),"
To add QtWebEngine
- Put the following in ${BSP_HOME}/${BDIR}/conf/local.conf
-
IMAGE_INSTALL_append += "packagegroup-qt5-webengine"
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)
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
- 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:
- 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
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
Show all recipes (include non-installed packages)
bitbake -s
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
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
- g070vw01
- 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
- auog101uan02
- DSI to LVDS
- 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
- auog101uan02
- Dual Display
- DSI to HDMI + HDMI
- adv-imx8mq-rom5720-a1-dual-display.dtb
- DSI to HDMI + HDMI
- DSI to HDMI
- 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
- g070vw01
- 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
- auog101uan02
- LVDS
- 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
- g070vw01
- DSI to HDMI
- adv-imx8qxp-rom3620-a1-hdmi-bridge.dtb
- DSI
- auog101uan02
- adv-imx8qxp-rom3620-a1-auog101uan02.dtb
- auog101uan02
- LVDS
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
- g070vw01
- 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
- HDMI + g070vw01
- LVDS to HDMI
- adv-imx8qm-rom7720-a1-it6263.dtb
- HDMI
- 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)
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";
};
How to get the MAC, Serial Number, and Manufacture Date in the QSPI flash
MAC 0:
READ_DATA=`dd if=/dev/mtdblock0 bs=1 skip=$((0xd0000)) count=6 2> /dev/null | hexdump -e '16/1 "%02x " "\n"' | sed 's/ /:/g' | cut -c 1-17`
echo $READ_DATA
MAC 1:
READ_DATA=`dd if=/dev/mtdblock0 bs=1 skip=$((0xd0400)) count=6 2> /dev/null | hexdump -e '16/1 "%02x " "\n"' | sed 's/ /:/g' | cut -c 1-17`
echo $READ_DATA
Serial Number:
READ_DATA=`dd if=/dev/mtdblock0 bs=1 skip=$((0xd0006)) count=10 2> /dev/null | cut -c 1-10`
echo $READ_DATA
Manufacture Date:
READ_DATA=`dd if=/dev/mtdblock0 bs=1 skip=$((0xd0010)) count=14 2> /dev/null | cut -c 1-14`
READ_DATA=`echo $READ_DATA | cut -c 1-4`-`echo $READ_DATA | cut -c 5-6`-`echo $READ_DATA | cut -c 7-8`_`echo $READ_DATA | cut -c 9-10`-`echo $READ_DATA | cut -c 11-12`-`echo $READ_DATA | cut -c 13-14`
echo $READ_DATA