Difference between revisions of "IoTGateway/BSP/Linux/iMX6/Yocto LBVD User Guide"

From ESS-WIKI
Jump to: navigation, search
(Created page with " = Getting Started = == <span style="color:#0070c0">Conventions</span> == <span style="color:purple">'''${PREBUILT_IMAGE}'''</span> : compressed prebuilt image (*.img.g...")
 
 
(4 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
<span style="color:purple">'''${PREBUILT_IMAGE}'''</span>&nbsp;: compressed prebuilt image (*.img.gz)
 
<span style="color:purple">'''${PREBUILT_IMAGE}'''</span>&nbsp;: compressed prebuilt image (*.img.gz)
  
<span style="color:purple">'''${CONTAINER_NAME}'''</span>&nbsp;: container name (e.g. imx8LBVD0027)
+
<span style="color:purple">'''${CONTAINER_NAME}'''</span>&nbsp;: container name (e.g. imx6LBVD0014)
  
 
<span style="color:purple">'''${BSP_TARBALL}'''</span>&nbsp;: BSP tarball (*.tgz)
 
<span style="color:purple">'''${BSP_TARBALL}'''</span>&nbsp;: BSP tarball (*.tgz)
Line 14: Line 14:
 
<span style="color:purple">'''${BDIR}'''</span>&nbsp;: build directory (e.g. build_xwayland)
 
<span style="color:purple">'''${BDIR}'''</span>&nbsp;: build directory (e.g. build_xwayland)
  
<span style="color:purple">'''${MX8PROC}'''</span>&nbsp;: i.MX8 Processor
+
<span style="color:purple">'''${MX6PROC}'''</span>&nbsp;: i.MX6 Processor
  
:mx8mq for iMX8M Dual Core
+
:rsb4411 imx6q
:mx8mm for iMX8MM
 
:mx8mp for iMX8MP
 
:mx8qm for iMX8QM
 
:mx8qxp for iMX8QXP
 
:mx8ulp for iMX8ULP
 
 
:&nbsp;  
 
:&nbsp;  
  
<span style="color:purple">'''${IMX8PROC}'''</span>&nbsp;: i.MX8 Processor
+
<span style="color:purple">'''${IMX6PROC}'''</span>&nbsp;: i.MX8 Processor
  
:imx8mq / imx8mm / imx8qm /imx8qxp /imx8mp /imx8ulp
+
:iimx6q
  
 
<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
+
:rsb4411
:rom5721
 
:rom7720
 
:rom5620
 
:rom3620
 
:rom5722
 
:rsb3720
 
:rom2620
 
:rsb3730
 
  
 
<span style="color:purple">'''${BOARD_REV}'''</span>&nbsp;: board revision
 
<span style="color:purple">'''${BOARD_REV}'''</span>&nbsp;: board revision
Line 49: Line 36:
  
 
:
 
:
::<tt>imx8mqrom5720a1 for ROM-5720 A1</tt>
+
::imx6qrsb4411a1 for RSB-4411&nbsp;A1   
::<tt>imx8qmrom7720a1 for ROM-7720 A1</tt>
 
::<tt>imx8qxprom5620a1 for ROM-5620 A1</tt>
 
::<tt>imx8qxprom3620a1 for ROM-3620 A1</tt>
 
::<tt>imx8mmrom5721a1 for ROM-5721 A1</tt>
 
::<tt>imx8mprom5722a1 for ROM-5722 A1</tt>
 
::<tt>imx8mprsb3720a1 for RSB-3720 A1</tt>
 
::<tt>imx8mprsb3720a2 for RSB-3720 A2</tt>
 
::<tt>imx8ulprom2620a1 for ROM-2620 A1</tt>
 
::<tt>imx8mmrsb3730a2 for RSB-3730 A2</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  
Line 65: Line 43:
 
<span style="color:purple">'''${MEM_SIZE}'''</span>&nbsp;: memory size
 
<span style="color:purple">'''${MEM_SIZE}'''</span>&nbsp;: memory size
  
:1G/2G/4G/6G
+
:1G/2G  
  
 
<span style="color:purple">'''${UC}'''</span>&nbsp;: u-boot config
 
<span style="color:purple">'''${UC}'''</span>&nbsp;: u-boot config
  
:1G/2G/4G/6G/FSPI_1G/FSPI_2G/FSPI_4G/FSPI_6G...
+
:1G/2G  
  
 
<span style="color:purple">'''${SD_DEVICE}'''</span>&nbsp;: device name of SD card in Linux (e.g. /dev/sdf)
 
<span style="color:purple">'''${SD_DEVICE}'''</span>&nbsp;: device name of SD card in Linux (e.g. /dev/sdf)
Line 117: Line 95:
 
: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[http://ess-wiki.advantech.com.tw/view/IoTGateway/BSP/Linux/iMX8/OS_Support_List_4.0_releasehttp://ess-wiki.advantech.com.tw/view/IoTGateway/BSP/Linux/iMX8/OS_Support_List_4.0_release IoTGateway/BSP/Linux/iMX8/OS_Support_List] , Official version "'''imx8LBVD0XXX" '''is taken as an example&nbsp;:  
+
:Refer to[http://ess-wiki.advantech.com.tw/view/IoTGateway/BSP/Linux/iMX8/OS_Support_List_4.0_releasehttp://ess-wiki.advantech.com.tw/view/IoTGateway/BSP/Linux/iMX8/OS_Support_List_4.0_release IoTGateway/BSP/Linux/iMX6/OS_Support_List] , Official version "'''imx6LBVD0XXX" '''is taken as an example&nbsp;:  
 
<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 141: Line 119:
 
=== <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. imx8LBVD0027_2023-10-25.tgz), then you have to copy it into container.  
+
:If you have BSP tarball (eg. imx6LBVD0014_2024-06-22.tgz), then you have to copy it into container.  
  
 
Follow the steps below:
 
Follow the steps below:
Line 151: Line 129:
 
2.Copy BSP tarball to ${WORKSPACE} , and change owner
 
2.Copy BSP tarball to ${WORKSPACE} , and change owner
  
  $ cp imx8LBVD0027_2023-10-25.tgz '''${WORKSPACE}'''
+
  $ cp imx6LBVD0014_2024-06-22.tgz '''${WORKSPACE}'''
  $ sudo chown adv:adv ${WORKSPACE}/imx8LBVD0027_2023-10-25.tgz
+
  $ sudo chown adv:adv ${WORKSPACE}/imx6LBVD0014_2024-06-22.tgz
  
 
3.Back to container
 
3.Back to container
Line 161: Line 139:
 
4.Unpack BSP tarball
 
4.Unpack BSP tarball
  
  $ tar zxvf imx8LBVD0027_2023-10-25.tgz
+
  $ tar zxvf imx6LBVD0014_2024-06-22.tgz
  
 
&nbsp;
 
&nbsp;
Line 201: Line 179:
 
  $ cd adv-release-bsp
 
  $ cd adv-release-bsp
 
  $ ln -s ${WORKSPACE}/downloads_imx8_6.1.22_2.0.0 downloads
 
  $ ln -s ${WORKSPACE}/downloads_imx8_6.1.22_2.0.0 downloads
 +
 +
&nbsp;
  
 
== <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.MX6/iMX8/iMX9, 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,  
  
Line 212: Line 192:
  
 
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.
 
=== <span style="color:#0070c0">Naming Rule</span> ===
 
 
:The tarball/prebuilt image name is consist of the model name followed by "LB" or "LI" plus version number and released date.
 
 
:For example, '''BSP file name: imx8LBVD0027_2023-10-25.tgz'''
 
:which , "LB" is acronym of <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''B'''</span>SP,
 
:"VD0010" stands for <span style="color:#ff0000">'''V'''</span>ersion <font color="#ff0000">'''D'''</font>.<span style="color:#ff0000">'''0027'''</span> <nowiki>
 
</nowiki>
 
 
 
&nbsp;
 
 
:For example, '''Yocto image name: ''''''3720A2AIM36LIVD0027_iMX8MP_6G_2023-10-25.img.gz'''
 
:which "3720A2" stands for <span style="color:#ff0000">'''RSB-3720 A2'''</span>
 
:"LI" is acronym for prebuilt <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''I'''</span>mage
 
:"6G" is DDR size
 
  
 
=== <span style="color:#0070c0">BSP Content</span> ===
 
=== <span style="color:#0070c0">BSP Content</span> ===
Line 329: Line 292:
 
*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  
 
&nbsp;
 
 
== <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/mickledore/imx8/adv_imx8_build.sh https://raw.githubusercontent.com/ADVANTECH-Corp/RISC_tools_scripts/mickledore/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_LBVA_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.
 
 
&nbsp;
 
  
 
= Customization =
 
= Customization =
Line 382: Line 321:
 
==== <span style="color:#0070c0">Config u-boot</span> ====
 
==== <span style="color:#0070c0">Config u-boot</span> ====
  
  make ${IMX8PROC}_${BOARD}${BOARD_REV}_${MEM_SIZE}_defconfig
+
  make ${IMX6PROC}_${BOARD}${BOARD_REV}_${MEM_SIZE}_defconfig
  
 
eg.
 
eg.
  
  make imx8mp_rsb3720a2_6G_defconfig
+
  make mx6qrsb4411a1_1G_defconfig
  
 
==== <span style="color:#0070c0">Build u-boot</span> ====
 
==== <span style="color:#0070c0">Build u-boot</span> ====
  
 
  make -j4
 
  make -j4
 
== <span style="color:#0070c0">Build imx-boot image by using imx-mkimage for imx8</span> ==
 
 
Get imx-boot tarball from our server Here we take rom5721 as an example:
 
 
tar zxvf 3720A2AIM36LIVD0027_iMX8MP_6G_imx-boot.tgz
 
cd 3720A2AIM36LIVD0027_iMX8MP_6G_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-imx '''imx8mp'''
 
./mk_imx-boot.sh '''imx8mp'''
 
 
== <span style="color:#0070c0">Build imx-boot image by using imx-mkimage for imx93</span> ==
 
 
Get imx-boot tarball from our server Here we take rom2820 as an example:
 
 
tar zxvf 3720A2AIM36LIVD0027_iMX8MP_6G_imx-boot.tgz
 
cd 3720A2AIM36LIVD0027_iMX8MP_6G_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-imx '''imx8mp'''
 
./mk_imx-boot.sh '''imx8mp'''
 
  
 
&nbsp;
 
&nbsp;
  
 
==== <span style="color:#0070c0">Replace imx-boot</span> ====
 
==== <span style="color:#0070c0">Replace imx-boot</span> ====
 +
 +
:Perform the following command to transfer to exist boot-up SD card
 +
<pre>$ dd if=u-boot_crc.bin.crc of='''${SD_DEVICE}''' bs=512 seek=2 conv=fsync
 +
$ dd if=u-boot_crc.bin of='''${SD_DEVICE}''' bs=512 seek=3 conv=fsync
 +
</pre>
  
 
:Perform the following command to transfer to on-board flash  
 
:Perform the following command to transfer to on-board flash  
 
+
<pre>$ dd if=u-boot_crc.bin.crc of=/dev/mmcblk0 bs=512 seek=2 conv=fsync
$ dd if=flash.bin of=/dev/mmcblk0 bs=1K seek=<offset> conv=fsync
+
$ dd if=u-boot_crc.bin of=/dev/mmcblk0 bs=512 seek=3 conv=fsync</pre>
 
 
:Where offset is:
 
::33 - for i.MAX 8QuadMax A0, i.Mx 8QuadXPlus A0, i.MX 8M Quad, and i.MX 8M Mini
 
::32 - for iMX 8M PLUS, i.MAX 8QuadXPlus B0/C0, i.Mx 8QuadMax B0 and i.MX 8ulp 
 
  
 
== <span style="color:#0070c0">Building & updating kernel/modules/dtb manually</span> ==
 
== <span style="color:#0070c0">Building & updating kernel/modules/dtb manually</span> ==
Line 454: Line 354:
 
change owner & unpack tarball
 
change owner & unpack tarball
  
  $ sudo chown adv:adv imx8LBVD0027_2023-10-25_linux-imx.tgz
+
  $ sudo chown adv:adv imx6LBVD0014_2024-06-22_linux-imx.tgz
  $ tar zxvf imx8LBVD0027_2023-10-25_linux-imx.tgz
+
  $ tar zxvf imx6LBVD0014_2024-06-22_linux-imx.tgz
  
 
=== <span style="color:#0070c0">Config kernel</span> ===
 
=== <span style="color:#0070c0">Config kernel</span> ===
  
 
:Configure linux kernel  
 
:Configure linux kernel  
 +
<pre>$cd linux-imx6
 +
$make distclean
 +
$make imx_v7_adv_defconfig
 +
$make menuconfig
 +
</pre>
  
$ cd linux-imx
+
If you get error ,when you "make imx_v7_adv_defconfig" , you need to insatall "libncurses*"
$ make distclean
 
$ make imx_v8_adv_defconfig
 
$ make menuconfig
 
  
:Start building linux kernel
+
$apt-get install libncurses*
  
  $ make -j4 Image
+
  $ unset LDFLAGS
  
:When you get error like below
+
=== Build kernel ===
  
[[File:Imx8 error.jpg|RTENOTITLE]]
+
:Start building linux kernel
 
+
<pre>$ make -j4 zImage
:run command then rebuild
+
</pre>
 
 
$ unset LDFLAGS
 
 
 
&nbsp;
 
  
:The kernel image file, Image, is located in the directory "./arch/arm64/boot/".  
+
:The kernel image file, zImage, is located in the directory "./arch/arm/boot/".  
  
 
:Start building kernel modules  
 
:Start building kernel modules  
 
+
<pre>$ make -j4 modules
$ make -j4 modules
+
</pre>
  
 
:Copy all modules to a temporary rootfs directory, "~/temp/rootfs"  
 
:Copy all modules to a temporary rootfs directory, "~/temp/rootfs"  
 
+
<pre>$ make modules_install INSTALL_MOD_PATH=~/temp/rootfs
$ make modules_install INSTALL_MOD_PATH=~/temp/rootfs
+
</pre>
  
 
:Building device tree blob  
 
:Building device tree blob  
 +
<pre>$ make -j4 '''${IMX6PROC}'''-'''${BOARD}'''-'''${BOARD_REV}'''.dtb
 +
</pre>
  
$ make -j4 freescale/<span style="color:#7030a0">'''${IMX8PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD_REV}'''</span>.dtb
+
:The device tree blob, '''${IMX6PROC}'''-'''${BOARD}'''-'''${BOARD_REV}'''.dtb, is located in the directory "./arch/arm/boot/dts/".  
eg.
 
$ make -j4 freescale/imx8mp-rsb3720-a2.dtb
 
 
 
:The device tree blob, <span style="color:#7030a0">'''${IMX8PROC}'''</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/".  
 
  
=== <span style="color:#0070c0">Replace kernel & dts</span> ===
+
=== Replace kernel & dts ===
  
 
:Replace kernel  
 
:Replace kernel  
::copy Image to SDcard or emmc   
+
::copy zImage to SDcard or emmc   
 
:Replace dtb file  
 
:Replace dtb file  
::copy dtb file to SDcard or emmc   
+
::copy dtb file to SDcard or emmc  
 +
::&nbsp;    
  
== <span style="color:#0070c0">Improve boot speed</span> ==
+
Reflash EMMC from Boot SD CARD
  
*Bootloader
+
Download mksd-linux.sh in [https://github.com/ADVANTECH-Corp/RISC_tools_scripts/blob/kirkstone/imx8/mksd-linux.sh https://github.com/ADVANTECH-Corp/RISC_tools_scripts/blob/kirkstone/imx8/mksd-linux.sh]
 
 
1.bootdelay time
 
 
 
:We can cancel the bootdelay time by setting bootloader environment value.
 
 
 
setenv bootdelay 0
 
env save
 
reset
 
 
 
2.Disable console
 
 
 
:Disable debug message output can also improve boot speed
 
 
 
Disable kernel message
 
 
 
setenv mmcargs setenv bootargs ${jh_clk} console=${console} modprobe.blacklist=${modprobe.blacklist} root=${mmcroot} video=HDMI-A-1:${videores} '''quiet'''
 
env save
 
reset
 
 
 
Or
 
 
 
:Disable debug port
 
 
 
setenv console
 
env save
 
reset
 
 
 
*Rootfs
 
 
 
:TBD
 
 
 
*Services
 
 
 
1. Using '''systemctl disable ''' remove ,we can remove unnecessary services.
 
 
 
systemctl disable <services>
 
 
 
eg.
 
 
 
systemctl disable boottimes
 
 
 
&nbsp;
 
 
 
= System Recovery =
 
 
 
This section provides detail procedures of restoring the eMMC image.
 
 
 
For more usage ([https://github.com/NXPmicro/mfgtools/wiki https://github.com/NXPmicro/mfgtools/wiki])
 
 
 
&nbsp;
 
 
 
= Reflash EMMC from Boot SD CARD =
 
 
 
Download mksd-linux.sh in [https://github.com/ADVANTECH-Corp/RISC_tools_scripts/blob/mickledore/imx8/mksd-linux.sh https://github.com/ADVANTECH-Corp/RISC_tools_scripts/blob/mickledore/imx8/mksd-linux.sh]
 
  
 
Download "Product_AIM_Release_version"_flash_tool.tgz
 
Download "Product_AIM_Release_version"_flash_tool.tgz
Line 571: Line 414:
 
Run mksd-linux.sh
 
Run mksd-linux.sh
  
&nbsp;
+
:
 
+
::&nbsp;
= Package List =
 
 
 
= 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 09:10, 12 July 2024

Getting Started

Conventions

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

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

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

${BSP_HOME} : home directory of the BSP

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

${MX6PROC} : i.MX6 Processor

rsb4411 imx6q
 

${IMX6PROC} : i.MX8 Processor

iimx6q

${BOARD} : available target boards list below

rsb4411

${BOARD_REV} : board revision

a1

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

for example,
imx6qrsb4411a1 for RSB-4411 A1
You can also use the command below to check supported machines on BSP
$ source setup-environment

${MEM_SIZE} : memory size

1G/2G

${UC} : u-boot config

1G/2G

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

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

${WORKSPACE} : host workspace folders

${UBOOT} :u-boot version(e.g. v2023.04_6.1.22-2.0.0)

${KERNEL} : linux kernel version(e.g. 6.1.22-2.0.0)

${TOOLCHAIN} : toolchain installed directory(e.g. opt/fsl-imx-wayland/6.1-mickledore/environment)

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 20.04 image from Docker Hub

$ docker pull advrisc/u20.04-imx8lbv1

To create container

$ docker run --privileged -it --name ${CONTAINER_NAME} -v ${WORKSPACE}:/home/adv/adv-release-bsp -v /dev:/dev advrisc/u20.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 toIoTGateway/BSP/Linux/iMX6/OS_Support_List , Official version "imx6LBVD0XXX" 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 imx-linux-mickledore -m adv-6.1.22-2.0.0.xml
$ repo sync
f 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
If you get "The unauthenticated git protocol on port 9418 is no longer supported.", you can try it.
$ git config --global url."https://".insteadOf git://

 

Copy BSP tarball to Container

If you have BSP tarball (eg. imx6LBVD0014_2024-06-22.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 imx6LBVD0014_2024-06-22.tgz ${WORKSPACE}
$ sudo chown adv:adv ${WORKSPACE}/imx6LBVD0014_2024-06-22.tgz

3.Back to container

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

4.Unpack BSP tarball

$ tar zxvf imx6LBVD0014_2024-06-22.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_6.1.22_2.0.0.tar.gz) from following URL:
[downloads_imx8_6.1.22_2.0.0.tar.gz]
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_6.1.22_2.0.0.tar.gz ${WORKSPACE}
$ sudo chown adv:adv ${WORKSPACE}/downloads_imx8_6.1.22_2.0.0.tar.gz 

3.Back to container

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

4.Unpack Downloads tarball

$ tar zxvf downloads_imx8_6.1.22_2.0.0.tar.gz

5.make link to downloads folder

$ cd adv-release-bsp
$ ln -s ${WORKSPACE}/downloads_imx8_6.1.22_2.0.0 downloads

 

Introducing BSP

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

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 imx-setup-release.sh -b ${BDIR}
We can specify u-boot default config like below
$ MACHINE=${MC} UBOOT_CONFIG=${UC} DISTRO=fsl-imx-xwayland source imx-setup-release.sh -b ${BDIR}
You need to read and accept the EULA.
RTENOTITLE

To continue an exist build environment

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

 

To build sdcard image

To create/continue a build environment
Perform the following command in terminal console
$ bitbake imx-image-full
The two files, imx-image-full-${MC}.wic.zst and ...wic.bmap, 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-wayland-glibc-x86_64-meta-toolchain-armv8a-imx8mp-lpddr4-evk-toolchain-${KERNEL}-mickledore.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-${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}
$ zstd -cd ${SDCARD_IMAGE} | sudo dd of=${SD_DEVICE} bs=1M
( or using bmaptool to take less time elapsed)
$ sudo bmaptool copy --bmap ${SDCARD_IMAGE/zst/bmap} ${SDCARD_IMAGE} ${SD_DEVICE}
$ 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

Customization

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-wayland-glibc-x86_64-meta-toolchain-armv8a-imx8mp-lpddr4-evk-toolchain-6.1-mickledore.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)
Download SDK Link (Just Only reference), [downloads_SDK]

 

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 ${IMX6PROC}_${BOARD}${BOARD_REV}_${MEM_SIZE}_defconfig

eg.

make mx6qrsb4411a1_1G_defconfig

Build u-boot

make -j4

 

Replace imx-boot

Perform the following command to transfer to exist boot-up SD card
$ dd if=u-boot_crc.bin.crc of='''${SD_DEVICE}''' bs=512 seek=2 conv=fsync
$ dd if=u-boot_crc.bin of='''${SD_DEVICE}''' bs=512 seek=3 conv=fsync
Perform the following command to transfer to on-board flash
$ dd if=u-boot_crc.bin.crc of=/dev/mmcblk0 bs=512 seek=2 conv=fsync
$ dd if=u-boot_crc.bin of=/dev/mmcblk0 bs=512 seek=3 conv=fsync

Building & updating kernel/modules/dtb manually

The cross compiling environment has been set up. (ref. Setting up cross compiling environment)

Copy BSP tarball to Container

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

change owner & unpack tarball

$ sudo chown adv:adv imx6LBVD0014_2024-06-22_linux-imx.tgz
$ tar zxvf imx6LBVD0014_2024-06-22_linux-imx.tgz

Config kernel

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

If you get error ,when you "make imx_v7_adv_defconfig" , you need to insatall "libncurses*"

$apt-get install libncurses*

$ unset LDFLAGS 

Build kernel

Start building linux kernel
$ make -j4 zImage
The kernel image file, zImage, is located in the directory "./arch/arm/boot/".
Start building kernel modules
$ make -j4 modules
Copy all modules to a temporary rootfs directory, "~/temp/rootfs"
$ make modules_install INSTALL_MOD_PATH=~/temp/rootfs
Building device tree blob
$ make -j4 '''${IMX6PROC}'''-'''${BOARD}'''-'''${BOARD_REV}'''.dtb
The device tree blob, ${IMX6PROC}-${BOARD}-${BOARD_REV}.dtb, is located in the directory "./arch/arm/boot/dts/".

Replace kernel & dts

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

Reflash EMMC from Boot SD CARD

Download mksd-linux.sh in https://github.com/ADVANTECH-Corp/RISC_tools_scripts/blob/kirkstone/imx8/mksd-linux.sh

Download "Product_AIM_Release_version"_flash_tool.tgz

Unzip the "Product_AIM_Release_version"_flash_tool.tgz

Copy the mksd-linux.sh to mk_inand folder.

Run mksd-linux.sh