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

From ESS-WIKI
Jump to: navigation, search
(Created page with " {{DISPLAYTITLE:Yocto Linux BSP Ver.C User Guide for iMX8 series -Yocto 4.0}} <!-- {| align="right" | <span class="fck_mw_magic" _fck_mw_customtag="true" _fck_mw_tagname="TOC...")
 
(Build U-Boot in standalone environment)
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
  
{{DISPLAYTITLE:Yocto Linux BSP Ver.C User Guide for iMX8 series -Yocto 4.0}} <!--
+
{{DISPLAYTITLE:Yocto Linux BSP Ver.C User Guide for iMX6 series -Yocto 4.0}} <!--
 
{| align="right"
 
{| align="right"
 
  | <span class="fck_mw_magic" _fck_mw_customtag="true" _fck_mw_tagname="TOC" _fck_mw_tagtype="c">_</span>
 
  | <span class="fck_mw_magic" _fck_mw_customtag="true" _fck_mw_tagname="TOC" _fck_mw_tagtype="c">_</span>
Line 103: Line 103:
 
: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 &nbsp;IoTGateway/BSP/Linux/iMX8/OS_Support_List] , Official version "'''imx8LBVC0XXX"&nbsp;'''is taken as&nbsp;an example&nbsp;:  
+
:Refer to[http://ess-wiki.advantech.com.tw/view/AIM-Linux/BSP/NXP/Linux_Yocto_OS_Release_note/Yocto4.0/Internal &nbsp;IoTGateway/BSP/Linux/iMX6/OS_Support_List] , Official version "'''imx6LBVC0XXX"&nbsp;'''is taken as&nbsp;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 129: Line 129:
  
 
&nbsp;
 
&nbsp;
 
=== <span style="color:#0070c0">Copy BSP tarball to Container</span> ===
 
 
:If you have BSP tarball (eg. imx8LBVB0029_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 imx8LBVB0029_2021-10-23.tgz '''${WORKSPACE}'''
 
$ sudo chown adv:adv ${WORKSPACE}/imx8LBVB0029_2021-10-23.tgz&nbsp;
 
 
3.Back to container
 
 
$ docker start '''${CONTAINER_NAME}'''
 
$ docker attach '''${CONTAINER_NAME}'''
 
 
4.Unpack BSP tarball
 
 
$ tar zxvf imx8LBVB0029_2021-10-23.tgz
 
 
== <span style="color:#0070c0">Downloads tarball</span> ==
 
 
:Not necessarily step
 
  
 
:During building &nbsp;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 &nbsp;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_5.15.52_2.1.0.tar.gz) from following URL:  
+
:You can get Downloads tarball (downloads_imx6_5.15.52_2.1.0.tar.gz) from following URL:  
  
:[https://www.dropbox.com/s/2rgwquwitvt6ihw/downloads_imx8_5.15.52_2.1.0.tar.gz?dl=0 [downloads_imx8_5.15.52_2.1.0.tar.gz]]  
+
:[https://www.dropbox.com/s/2rgwquwitvt6ihw/downloads_imx8_5.15.52_2.1.0.tar.gz?dl=0 [downloads_imx6_5.15.52_2.1.0.tar.gz]]  
  
 
:If you get downloads tarball, you can copy to your '''${WORKSPACE}'''  
 
:If you get downloads tarball, you can copy to your '''${WORKSPACE}'''  
Line 174: Line 146:
 
2.Copy Downloads tarball to ${WORKSPACE} , and change owner
 
2.Copy Downloads tarball to ${WORKSPACE} , and change owner
  
  $ cp downloads_imx8_5.15.52_2.1.0.tar.gzz '''${WORKSPACE}'''
+
  $ cp downloads_imx6_5.15.52_2.1.0.tar.gz '''${WORKSPACE}'''
  $ sudo chown adv:adv ${WORKSPACE}/downloads_imx8_5.15.52_2.1.0.tar.gz&nbsp;
+
  $ sudo chown adv:adv ${WORKSPACE}/downloads_imx6_5.15.52_2.1.0.tar.gz&nbsp;
  
 
3.Back to container
 
3.Back to container
Line 184: Line 156:
 
4.Unpack Downloads tarball
 
4.Unpack Downloads tarball
  
  $ tar zxvf downloads_imx8_5.15.52_2.1.0.tar.gzz
+
  $ tar zxvf downloads_imx6_5.15.52_2.1.0.tar.gz
  
 
5.make link to downloads folder
 
5.make link to downloads folder
  
 
  $ cd adv-release-bsp
 
  $ cd adv-release-bsp
  $ ln -s ${WORKSPACE}/downloads_imx8_5.15.52_2.1.0 downloads
+
  $ ln -s ${WORKSPACE}/downloads_imx6_5.15.52_2.1.0 downloads
  
 
== <span style="color:#0070c0">Introducing BSP</span> ==
 
== <span style="color:#0070c0">Introducing BSP</span> ==
Line 201: Line 173:
  
 
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: imx8LBVC0010_2019-08-27.tgz'''
 
:which , "LB" is acronym of <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''B'''</span>SP,
 
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"VC0010" stands for <span style="color:#ff0000">'''V'''</span>ersion <font color="#ff0000">'''C'''</font>.<span style="color:#ff0000">'''0010'''</span> <nowiki>.
 
</nowiki>
 
 
 
&nbsp;
 
 
:For example, '''Yocto image name: ''''''5720A1AIM20LIVC0010_iMX8M_2G_2020-08-27.img.gz'''
 
:which "5720A1" stands for <span style="color:#ff0000">'''ROM-5720 A1'''</span>
 
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "LI" is acronym for prebuilt <span style="color:#ff0000">'''L'''</span>inux <span style="color:#ff0000">'''I'''</span>mage
 
:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "2G" is DDR size
 
  
 
=== <span style="color:#0070c0">BSP Content</span> ===
 
=== <span style="color:#0070c0">BSP Content</span> ===
Line 246: Line 201:
 
:Perform the following command in terminal console  
 
:Perform the following command in terminal console  
 
::<code>$ bitbake imx-image-full</code>   
 
::<code>$ bitbake imx-image-full</code>   
:The file, imx-image-full-<span style="color:#7030a0">'''${MC}'''</span>.wic.bz2, will be located in directory, ./tmp/deploy/images/<span style="color:#7030a0">'''${MC}'''</span>, while building process finished successfully.  
+
:The file, imx-image-full-<span style="color:#7030a0">'''${MC}'''</span>.wic.zst, 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> ===
Line 254: Line 209:
 
::<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>-zeus.sh</tt>   
+
::<tt>fsl-imx-xwayland-glibc-x86_64-imx-image-full-cortexa9t2hf-neon-imx6qsabresd-toolchain-5.15-kirkstone</tt>   
  
 
=== <span style="color:#0070c0">To build bootloader</span> ===
 
=== <span style="color:#0070c0">To build bootloader</span> ===
Line 282: Line 237:
 
::
 
::
 
:::<code>$ bitbake linux-imx</code>     
 
:::<code>$ bitbake linux-imx</code>     
:The two files, Image & Image-<span style="color:#7030a0">'''${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>.  
+
:The two files, Image & Image-<span style="color:#7030a0">'''${IMX6PROC}'''</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 316: Line 271:
 
*You need to prepare the debug console tool. For example: "minicom" tool or "putty" tool.  
 
*You need to prepare the debug console tool. For example: "minicom" tool or "putty" tool.  
 
*Baud rate: 115200  
 
*Baud rate: 115200  
 
== <span style="color:#0070c0">One step build image</span> ==
 
 
Our machine must be pre-installed docker
 
 
Download the following script can quickly build our image.
 
 
$ wget [https://raw.githubusercontent.com/ADVANTECH-Corp/RISC_tools_scripts/hardknott/imx8/adv_imx8_build.sh https://raw.githubusercontent.com/ADVANTECH-Corp/RISC_tools_scripts/hardknott/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 346: Line 279:
 
: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-wayland-glibc-x86_64-meta-toolchain-armv8a-imx8mp-lpddr4-evk-toolchain-5.15-kirkstone.sh</code>   
+
::<code>$ sudo ./</code><tt>fsl-imx-xwayland-glibc-x86_64-imx-image-full-cortexa9t2hf-neon-imx6qsabresd-toolchain-5.15-kirkstone</tt>   
 
: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.  
Line 361: Line 294:
 
: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-cortexa9t2hf-neon-poky-linux-gnueabi</code>   
  
 
== <span style="color:#0070c0">Build U-Boot in standalone environment</span> ==
 
== <span style="color:#0070c0">Build U-Boot in standalone environment</span> ==
Line 367: Line 300:
 
==== <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 imx8mm_rom5721a1_2G_defconfig
+
  make mx6qrom7420a1_1G_defconfig
  
 
==== <span style="color:#0070c0">Build u-boot</span> ====
 
==== <span style="color:#0070c0">Build u-boot</span> ====
Line 377: Line 310:
 
  make -j4
 
  make -j4
  
== <span style="color:#0070c0">Build imx-boot image by using imx-mkimage</span> ==
+
== &nbsp; ==
 
 
Get imx-boot tarball from our server Here we take rom5721 as an example:
 
 
 
tar zxvf 5721A1AIM20LIVA0118_iMX8MM_imx-boot.tgz
 
cd 5721A1AIM20LIVA0118_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-imx '''imx8m'''
 
./mk_imx-boot.sh '''imx8mm'''
 
 
 
==== <span style="color:#0070c0">Replace imx-boot</span> ====
 
 
 
: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.Mx 8QuadXPlus A0, i.MX 8M Quad, and i.MX 8M Mini
 
::32 - for iMX 8M PLUS, i.MAX 8QuadXPlus B0/C0 and i.Mx 8QuadMax B0 
 
  
 
== <span style="color:#0070c0">Building & updating kernel/modules/dtb manually</span> ==
 
== <span style="color:#0070c0">Building & updating kernel/modules/dtb manually</span> ==
Line 415: Line 320:
 
Refer to [http://ess-wiki.advantech.com.tw/view/IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#Copy_BSP_tarball_to_Container Copy_BSP_tarball_to_Container] , <span style="color:#FF0000">copy kernel tarball </span>to ${WORKSPACE} and back to container
 
Refer to [http://ess-wiki.advantech.com.tw/view/IoTGateway/BSP/Linux/iMX8/Yocto_LBV9_User_Guide#Copy_BSP_tarball_to_Container Copy_BSP_tarball_to_Container] , <span style="color:#FF0000">copy kernel tarball </span>to ${WORKSPACE} and back to container
  
change owner & unpack tarball
+
Download kernel source from Github
 +
 
 +
$ git clone [https://github.com/ADVANTECH-Corp/linux-imx.git https://github.com/ADVANTECH-Corp/linux-imx.git] -b adv_5.15.52_2.1.0
  
$ sudo chown adv:adv imx8LBVC0029_2019-10-23_linux-imx.tgz
 
$ tar zxvf imx8LBVC0029_2019-10-23_linux-imx.tgz
 
  
 
=== <span style="color:#0070c0">Config kernel</span> ===
 
=== <span style="color:#0070c0">Config kernel</span> ===
Line 426: Line 331:
 
  $ cd linux-imx
 
  $ cd linux-imx
 
  $ make distclean
 
  $ make distclean
  $ make imx_v8_adv_defconfig
+
  $ make imx_v7_adv_defconfig
 
  $ make menuconfig
 
  $ make menuconfig
  
Line 443: Line 348:
 
&nbsp;
 
&nbsp;
  
:The kernel image file, Image, is located in the directory "./arch/arm64/boot/".  
+
:The kernel image file, Image, is located in the directory "./arch/arm/boot/".  
  
 
:Start building kernel modules  
 
:Start building kernel modules  
Line 455: Line 360:
 
:Building device tree blob  
 
:Building device tree blob  
  
  $ make -j4 freescale/<span style="color:#7030a0">'''${IMX8PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD_REV}'''</span>.dtb
+
  $ make -j4 <span style="color:#7030a0">'''${IMX6PROC}'''</span>-<span style="color:#7030a0">'''${BOARD}'''</span>-<span style="color:#7030a0">'''${BOARD_REV}'''</span>.dtb
 
  eg.
 
  eg.
  $ make -j4 freescale/imx8mq-rom5721-a1.dtb
+
  $ make -j4 imx6q-rom7420-a1.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/".  
+
: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/arm/boot/dts/".
  
 
=== <span style="color:#0070c0">Replace kernel & dts</span> ===
 
=== <span style="color:#0070c0">Replace kernel & dts</span> ===
Line 467: Line 372:
 
: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> ==
 
 
*Bootloader
 
 
1.bootdelay time
 
 
:We can cancel the bootdelay time by setting bootloader environment value.
 
 
setenv bootdelay 0
 
env save
 
reset
 
 
2.Disable console
 
 
:Disable debug message output can also improve boot speed
 
 
Disable kernel message
 
 
setenv mmcargs setenv bootargs ${jh_clk} console=${console} modprobe.blacklist=${modprobe.blacklist} root=${mmcroot} video=HDMI-A-1:${videores} '''quiet'''
 
env save
 
reset
 
 
Or
 
 
:Disable debug port
 
 
setenv console
 
env save
 
reset
 
 
*Rootfs
 
 
:TBD
 
 
*Services
 
 
1. Using '''systemctl disable ''' remove ,we can remove unnecessary services.
 
 
systemctl disable <services>
 
 
eg.
 
 
systemctl disable boottimes
 
 
&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 =
 
= Reflash EMMC from Boot SD CARD =
Line 533: Line 384:
  
 
Run mksd-linux.sh
 
Run mksd-linux.sh
 
&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>
 
 
&nbsp;
 

Latest revision as of 07:26, 24 April 2024


Getting Started

Conventions

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

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

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

${BSP_HOME} : home directory of the BSP

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

${MX6PROC} : i.MX6 Processor

mx6q for iMX6 Dual Quad Core
 

${IMX6PROC} : i.MX6 Processor

imx6q

${BOARD} : available target boards list below

rom7420
rsb4411

${BOARD_REV} : board revision

a1

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

for example,
imx6qrom7420a1 for ROM-7420 A1
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/4G/FSPI_1G/FSPI_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. v2022.04_5.15.52_2.1.0)

${KERNEL} : linux kernel version(e.g. 5.15.52_2.1.0)

${TOOLCHAIN} : toolchain installed directory(e.g. opt/fsl-imx-wayland/5-15-kirkstone/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 to IoTGateway/BSP/Linux/iMX6/OS_Support_List , Official version "imx6LBVC0XXX" 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-kirkstone -m adv-5.15.52-2.1.0.xml 
$ repo sync
After repo sync and finished. Please modify the "meta-freescale/recipes-bsp/u-boot/u-boot-imx-common_2022.04.inc"
Please Reference the commit https://github.com/Freescale/meta-freescale/commit/f851708484206263aecee032288d27c948745ce8

U-boot-imx-common.png

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
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://

 

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_imx6_5.15.52_2.1.0.tar.gz) from following URL:
[downloads_imx6_5.15.52_2.1.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_imx6_5.15.52_2.1.0.tar.gz ${WORKSPACE}
$ sudo chown adv:adv ${WORKSPACE}/downloads_imx6_5.15.52_2.1.0.tar.gz 

3.Back to container

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

4.Unpack Downloads tarball

$ tar zxvf downloads_imx6_5.15.52_2.1.0.tar.gz

5.make link to downloads folder

$ cd adv-release-bsp
$ ln -s ${WORKSPACE}/downloads_imx6_5.15.52_2.1.0 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.

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 file, imx-image-full-${MC}.wic.zst, 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-imx-image-full-cortexa9t2hf-neon-imx6qsabresd-toolchain-5.15-kirkstone

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-${IMX6PROC}-${BOARD}-${BOARD_REV}.dtb, will be located in the directory, ./tmp/deploy/images/${MC}.

Creating boot-up on-board flash from prebuilt image

To create one boot-up SD card

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

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

To create one boot-up SD card

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

Debug console information

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

Preparing for hardware device

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

Debug Port Information

Preparing for software tool

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

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-xwayland-glibc-x86_64-imx-image-full-cortexa9t2hf-neon-imx6qsabresd-toolchain-5.15-kirkstone
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-cortexa9t2hf-neon-poky-linux-gnueabi

Build U-Boot in standalone environment

Config u-boot

make ${IMX6PROC}_${BOARD}${BOARD_REV}_${MEM_SIZE}_defconfig

eg.

make mx6qrom7420a1_1G_defconfig

Build u-boot

make -j4

 

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

Download kernel source from Github

$ git clone https://github.com/ADVANTECH-Corp/linux-imx.git -b adv_5.15.52_2.1.0


Config kernel

Configure linux kernel
$ cd linux-imx
$ make distclean
$ make imx_v7_adv_defconfig
$ make menuconfig
Start building linux kernel
$ make -j4 Image
When you get error like below

RTENOTITLE

run command then rebuild
$ unset LDFLAGS 

 

The kernel image file, Image, is located in the directory "./arch/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
eg.
$ make -j4 imx6q-rom7420-a1.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 Image 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