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

From ESS-WIKI
Jump to: navigation, search
(Get BSP)
 
(2 intermediate revisions by the same user not shown)
Line 85: Line 85:
 
:<code>$ docker run --privileged -it --name '''${CONTAINER_NAME}''' -v '''${WORKSPACE}''':/home/adv/adv-release-bsp -v /dev:/dev advrisc/u20.04-imx8lbv1 /bin/bash</code>  
 
:<code>$ docker run --privileged -it --name '''${CONTAINER_NAME}''' -v '''${WORKSPACE}''':/home/adv/adv-release-bsp -v /dev:/dev advrisc/u20.04-imx8lbv1 /bin/bash</code>  
  
 +
&nbsp;
  
 
== <span style="color:#0070c0">Get BSP</span> ==
 
== <span style="color:#0070c0">Get BSP</span> ==
Line 202: Line 203:
 
=== <span style="color:#0070c0">BSP Content</span> ===
 
=== <span style="color:#0070c0">BSP Content</span> ===
 
<div style="margin-left:0.499cm; margin-right:0cm">The description of some important folders list below:</div> <div style="margin-left:1.499cm; margin-right:0cm">'''sources/'''</div> <div style="margin-left:1.998cm; margin-right:0cm">'''meta-advantech/'''&nbsp;: meta layer by Advantech</div> <div style="margin-left:1.998cm; margin-right:0cm">'''meta-fsl-*/'''&nbsp;: meta layer by Freescale</div> <div style="margin-left:1.499cm; margin-right:0cm">'''fsl-setup-release.sh'''&nbsp;: to create one new build environment</div> <div style="margin-left:1.499cm; margin-right:0cm">'''setup-environment'''&nbsp;: to continue an exist build environment</div>  
 
<div style="margin-left:0.499cm; margin-right:0cm">The description of some important folders list below:</div> <div style="margin-left:1.499cm; margin-right:0cm">'''sources/'''</div> <div style="margin-left:1.998cm; margin-right:0cm">'''meta-advantech/'''&nbsp;: meta layer by Advantech</div> <div style="margin-left:1.998cm; margin-right:0cm">'''meta-fsl-*/'''&nbsp;: meta layer by Freescale</div> <div style="margin-left:1.499cm; margin-right:0cm">'''fsl-setup-release.sh'''&nbsp;: to create one new build environment</div> <div style="margin-left:1.499cm; margin-right:0cm">'''setup-environment'''&nbsp;: to continue an exist build environment</div>  
 +
 
== <span style="color:#0070c0">Build Instructions</span> ==
 
== <span style="color:#0070c0">Build Instructions</span> ==
  
Line 209: Line 211:
 
::<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 imx-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 imx-setup-release.sh -b <span style="color:#7030a0">'''${BDIR}'''</span></code>   
 +
 +
:Example the machine is 4411 dual lite 2G
 +
::<code>MACHINE=imx6dlrsb4411a2 DISTRO=fsl-imx-xwayland source imx-setup-release.sh -b build_x11</code> 
 
:We can specify u-boot default config like below  
 
:We can specify u-boot default config like below  
 
::<code>$ MACHINE=<span style="color:#7030a0">'''${MC}'''</span> </code> <code>UBOOT_CONFIG=<span style="color:#7030a0">'''${UC}'''</span> </code> <code>DISTRO=fsl-imx-xwayland </code><code>source imx-setup-release.sh -b <span style="color:#7030a0">'''${BDIR}'''</span></code>   
 
::<code>$ MACHINE=<span style="color:#7030a0">'''${MC}'''</span> </code> <code>UBOOT_CONFIG=<span style="color:#7030a0">'''${UC}'''</span> </code> <code>DISTRO=fsl-imx-xwayland </code><code>source imx-setup-release.sh -b <span style="color:#7030a0">'''${BDIR}'''</span></code>   
 +
 +
:Example the machine is 4411 dual lite 2G
 +
::<code>MACHINE=imx6dlrsb4411a2 UBOOT_CONFIG=2G DISTRO=fsl-imx-xwayland source imx-setup-release.sh -b build_x11</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]]  
Line 263: Line 271:
 
::
 
::
 
:::<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">'''${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> ==

Latest revision as of 04:19, 16 December 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

If your platform is imx6dlrsb4411a2, please repo init the imx6LBVD0027.xml tag.

$ repo init -u git://github.com/ADVANTECH-Corp/adv-arm-yocto-bsp.git -b imx-linux-mickledore -m imx6LBVD0027.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
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}
Example the machine is 4411 dual lite 2G
MACHINE=imx6dlrsb4411a2 DISTRO=fsl-imx-xwayland source imx-setup-release.sh -b build_x11
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}
Example the machine is 4411 dual lite 2G
MACHINE=imx6dlrsb4411a2 UBOOT_CONFIG=2G DISTRO=fsl-imx-xwayland source imx-setup-release.sh -b build_x11
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