Message-ID: <2004896306.5215.1711642522175.JavaMail.root@dns3> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5214_882009700.1711642522175" ------=_Part_5214_882009700.1711642522175 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
On this page:
Eric Lee= p>
version 1.0a, 4/10/2019
This document describes how Embedian builds a customized version of NXP= =E2=80=99s i.MX8M official Yocto Rocko BSP release for Embedian's = SMARC-iMX8M product platform. The approach is to pull from Embedi= an's public facing GIT repository and build that using bitbake. The reason = why we use this approach is that it allows co-development. The build o= utput is comprised of binary images, feed packages, and an SDK for SMARC-iMX8M specific development.
Freescale makes their i.MX series official bsp build scripts available v= ia the following GIT repository:
=20 =20
=20 =20
It is this repository that actually p=
ulls in the fsl-bsp-relea=
se project to perform the Li=
nux BSP builds for Freescale's i.MX8M ARM Cortext-A53 chips.
We recommend you use SSH= keys to establish a secure connection between your computer and Embedian G= itlab server. The steps below will walk you through generating an SSH key a= nd then adding the public key to our Gitlab account.
First, we need to check for existing ssh keys on your computer. Open up&= nbsp;Git Bash and run:
$ cd ~/.ssh $ ls # Lists the files in your .ssh directory=20
Check the directory list=
ing to see if you have a file named either id_rsa.pub
&nbs=
p;or id_dsa.pub
. If you don't have either of those files =
go to step 2. Otherwise, you already have an existing=
keypair, and you can skip to step 3.
To generate a new SSH ke= y, enter the code below. We want the default settings so when asked to ente= r a file in which to save the key, just press enter.
$ ssh-keygen -t rsa -C "your_email@example.com" # Creates a new ssh key, using the provided email as a label # Generating public/private rsa key pair. # Enter file in which to save the key (/c/Users/you/.ssh/id_rsa): [Press en= ter] $ ssh-add id_rsa=20
Now you need to enter a = passphrase.
Enter passphrase (empty for no passphrase): [Type a passphrase] Enter same passphrase again: [Type passphrase again]=20
Which should give you so= mething like this:
Your identification has been saved in /c/Users/you/.ssh/id_rsa. Your public key has been saved in /c/Users/you/.ssh/id_rsa.pub. The key fingerprint is: 01:0f:f4:3b:ca:85:d6:17:a1:7d:f0:68:9d:f0:a2:db your_email@example.com=20
Copy the key to your cli= pboard.
$ cat ~/.ssh/id_rsa.pub ssh-rsa AAAAB3NzaC1yc2EAAABDAQABAAABAQDQUEnh8uGpfxaZVU6+uE4bsDrs/tEE5/BPW7j= MAxak 6qgOh6nUrQGBWS+VxMM2un3KzwvLRJSj8G4TnTK2CSmlBvR+X8ZeXNTyAdaDxULs/StVhH+QRtF= EGy4o iMIzvIlTyORY89jzhIsgZzwr01nqoSeWWASd+59JWtFjVy0nwVNVtbek7NfuIGGAPaijO5Wnshr= 2uChB Pk8ScGjQ3z4VqNXP6CWhCXTqIk7EQl7yX2GKd6FgEFrzae+5Jf63Xm8g6abbE3ytCrMT/jYy5OO= j2XSg 6jlxSFnKcONAcfMTWkTXeG/OgeGeG5kZdtqryRtOlGmOeuQe1dd3I+Zz3JyT your_email@exa= mple.c om=20
Go to Embedian Git Server. At Profile Setting --> SSH Keys --> Add SSH Key
Paste your public key and press "Add Key" and your are done.
The supplied meta-smarcimx8m-rocto Yocto compliant layer has the following organization:= span>
=20 =20
Notes on meta-smarcimx8m-rocko
conf/machine/*
This folder contains the machine definiti=
ons for the smarcimx8m2g/
recipes-bsp/u-boot/*
This folder contains recipes used to buil= d DAS U-boot for smarcimx8m2= g/smarcimx8m2gind/smarcimx8m4g p= latform.
recipes-bsp/imx-atf/*
This folder contains ARM Trusted firmware= for smarcimx8m2g/smar= cimx8m2gind/smarcimx8m4g platform.
recipes-bsp/imx-mkimage/*<=
/code>
This folder contains imx-mkimage tool for= smarcimx8m2g/smarcimx8m2gin= d/smarcimx8m4g platform.
recipes-core/busybox/*
This folder remove telnetd from bysybox f= or smarcimx8m2g/smarcimx8m2gind/smarcimx8m4g= span> platform.
recipes-kernel/linux/*
Contains the recipes needed to build the&= nbsp;smarcimx8m2g/smarcimx8= m2gind/smarcimx8m4g Linux kernels.
recipes-security/optee-imx=
/*
This folder contains Trusted Execution Environment for smarcimx8m2g/smarcimx8m2gind/smarcimx8= m4g platform.
To build the latest Freescale i.MX8M fsl-bsp-release, you first need an Ub= untu 16.04 LTS installation. Since bitbake does not accept building images = using root privileges, please do not login as a = root user when performing the instructions in this section.
Once you have Ubuntu 16.04 LTS running, install the additional required su= pport packages using the following console command:
=20 =20If you are using a 64-bit Linux, then= you'd also need to install 32-bit support libraries, needed by the pre-bui= lt Linaro toolchain and other binary tools.
=20 =20 =20 =20
To get the BSP you need to have 'repo' installed and use it as:
Install the 'repo' utility:
=20 =20=20 =20
Choose &q=
uot;y" to accept EULA.
This script wil= l create and bring you to ~/smarc-imx8m-rocko-release/imx8m-bui= ld-qt5wayland directory.
=20 =20
Once it done, you can find all required images under ~/smarc-imx8m-rocko-release/<build dir=
ectory>/tmp/deploy/images/<machine name>/
You may want to build programs that aren=E2=80=99t installed into a root= file system so you can make them available via a feed site (described belo= w.) To do this you can build the package directly and then build the packag= e named package-index&nbs= p;to add the new package to the feed site.
The following example builds the minicom program and makes it available on the feed site:
=20 =20~/smarc-imx8m-rocto-release=
/<build directory>/tmp/deploy
.
deploy/images/<machine name>/*
deploy/images/<machine name>/imx-boot-<machine name>-sd=
.bin-flash_evk
&n=
bsp;
deploy/images/<machine name>/imx-boot-<machine name>-sd=
.bin-flash_evk_no_hdmi
deploy/images/<machine name>/Image
deploy/images/<machine name>/<device tee file>=
code>
Select= ing display configuration is a matter of selecting an appropriate DTB file = under deploy/images/<machine name>/<device tee file>=
All available DTB files are listed in= the table below.
DTB File Name | Description |
---|---|
=
fsl-smarcimx8mq.dtb |
Device tree b= lob for no display configuration. |
=
fsl-smarcimx8mq-hdmi.dtb |
Device tree b= lob for HDMI display configuration (DCSS). |
=
fsl-smarcimx8mq-hdmi-4k.dtb |
Device tree b= lob for HDMI 4k display configuration (DCSS). |
=
fsl-smarcimx8mq-lcdif-lvds.dtb |
Device tree b= lob for LCDIF LVDS display configuration. |
=
fsl-smarcimx8mq-dcss-lvds.dtb |
Device tree b= lob for DCSS LVDS display configuration. |
=
fsl-smarcimx8mq-dual-display.dtb |
Device tree b= lob for dual LVDS+HDMI display configuration. |
deploy/images/<machine name>/fsl-image-validation-imx-<machine name>.*
deploy/images/<machine name>/fsl-image-qt5-validation-=
imx-<machine name>.*
deploy/rpm/*
This folder contains all the p= ackages used to construct the root file system images. They are in rpm format (similar format to Fedora package= s) and can be dynamically installed on the target platform via a properly &= nbsp;constructed feed= file. Here is an examp= le of the feed file (named imx8m_qt5wayland_update.repo) that is used internally at Embedian to install upgrades onto a = ;imx8msmarc QT5 platform directl= y on framebuffer without reflashing the file system:
=20 =20deploy/licenses/*
For these instruction, we are assuming: DISK=3D/dev/mmcblk0, "lsblk= " is very useful for determining the device id.
=20 =20Erase SD card:
=20 =20Create Partition Layout: Leave 2MB offset for boot file.
With util-linux v2.26, sfdisk was rewritten and is now based on = libfdisk.
=20 =20Create Partitions:
=20 =20 =20Format Partitions:
=20 =20Mount Partitions:
On some systems, these partitions may be auto-mounted...
=20 =20imx-b=
oot-<machine name>-sd.bin-flash_evk
or imx-boot-<machine name>-sd.bin-flash_e=
vk_no_hdmi)Boot file is factory default flash= ed at on-module eMMC flash.
If on-module eMMC Flash is empty<= /strong>
In some cases, when eMMC flash is erased = or the u-boot is under development, we need a way to boot from SD card firs= t. Users need to shunt cross the TEST# pin to ground. In this way,&nb= sp;SMARC-iMX8M will always boot up from SD card.
Fuse flash.bin to the SD card.
= =20 =20If on-module eMMC Flash is not em= pty
The <boot file> = is pre-installed in on-module eMMC flash at factory default. SMARC-iMX8M is= designed to always boot up from on-module eMMC flash and to load Image, de= vice tree blob and root file systems based on the setting of BOOT_= SEL. If users need to fuse your own flash.bin or perform u-boot upgrad= e. This section will instruct you how to do that.
Copy <boot file> to the second part= ition home directory of your SD card and boot into SD card. Go to home dire= ctory and you should see flash.bin file.
=20 =20Fuse <boot file> to the on-module e= MMC flash. (The eMMC flash is emulated as /dev/mmcblk0 in SMARC-iMX8M)
= =20 =20 =20 =20Create "uEnv.txt" boot script: ($ vim uEnv.txt)
=20 =20Copy uEnv.txt to the boot partition:
=20 =20Copy Image to the boot partition:
=20 =20All available DTB files are listed in= the table below.
DTB File Name | Description |
---|---|
=
fsl-smarcimx8mq.dtb |
Device tree b= lob for no display configuration. |
=
fsl-smarcimx8mq-hdmi.dtb |
Device tree b= lob for HDMI display configuration (DCSS). |
=
fsl-smarcimx8mq-hdmi-4k.dtb |
Device tree b= lob for HDMI 4k display configuration (DCSS). |
=
fsl-smarcimx8mq-lcdif-lvds.dtb |
Device tree b= lob for LCDIF LVDS display configuration. |
=
fsl-smarcimx8mq-dcss-lvds.dtb |
Device tree b= lob for DCSS LVDS display configuration. |
=
fsl-smarcimx8mq-dual-display.dtb |
Device tree b= lob for dual LVDS+HDMI display configuration. |
Yocto Built Rootfs:
=20 =20 =20Remove SD card:
=20 =20The following procedure can be used o= n a Embedian SMARC-iMX8M device to download and utilize = the feed file show above to install the tcpdump&n= bsp;Ethernet packet analyzer program:
=20 =20
In order to package your application and include it in the root filesyst= em image, you must write a BitBake recipe for it.
When starting from scratch, it is easiest to learn by example from exist= ing recipes.
For software that uses autotools (./configure; make; make install), writ= ing recipes can be very simple:
DESCRIPTION =3D
"Hello World Recipe using autotools"=
code>
HOMEPAGE =3D
"http://www.embedian.com/"
SECTION =3D
"console/utils"
PRIORITY =3D
"optional"
LICENSE =3D
"GPL"
PR =3D
"r0"
SRC_URI =3D
"=
git://git@git.embedian.com/developer/helloworld-autotools.git;protocol=3Dss=
h;tag=3Dv1.0"
S =3D
"${WORKDIR}/git"
inherit autotools
|
SRC_URI
sp=
ecifies the location to download the source from. It can take the form of a=
ny standard URL using http://, ftp://, etc. It can also fetch from SCM syst=
ems, such as git in the example above.
PR
is the =
package revision variable. Any time a recipe is updated that should require=
the package to be rebuilt, this variable should be incremented.
inherit autotools
brings in support for the package to be built using autotools, and =
thus no other instructions on how to compile and install the software are n=
eeded unless something needs to be customized.
S
is the s=
ource directory variable. This specifies where the source code will exist a=
fter it is fetched from SRC_URI and unpacked. The default value is ${WORKDIR}/${PN}-${PV}
, where PN
&n=
bsp;is the package name and PV
is the package version. Both PN
and PV
are set by default using the =
filename of the recipe, where the filename has the format PN_PV.bb
.
This example shows a simple case of building a helloworld.c file directl= y using the default compiler (gcc). Since it isn=E2=80=99t using autotools = or make, we have to tell BitBake how to build it explicitly.
DESCRIPTION =3D
"HelloWorld"
SECTION =3D
"examples"
LICENSE =3D
"GPL"
SRC_URI =3D
"file://helloworld.c"
S =3D
"${WORKDIR}"
do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} helloworld.c -o hellow=
orld
}
do_install() {
install -d ${D}${bindir}
install -m 0755 helloworld ${D}${bindir}
}
|
In this case, SRC_URI
specifies a file that must exist locally with the recipe. =
Since there is no code to download and unpack, we set S
to WORKDIR
since that is where he=
lloworld.c will be copied to before it is built.
WORKDIR
is=
located at ${OETREE}/<=
build directory>/tmp/work/aarch64-poky-linux/<package name and versio=
n>
for most packages. If the package is machine-speci=
fic (rather than generic for the aarxh64 architecture), it may be located i=
n the aarch64-mx8mq-poky-linux subdirectory depending on your hardware=
(this applies to kernel packages, images, etc).
do_compile
 =
;defines how to compile the source. In this case, we just call gcc directly=
. If it isn=E2=80=99t defined, make
in the source directory by default.
do_install
 =
;defines how to install the application. This example runs install
to create a bin =
directory where the application will be copied to and then copies the appli=
cation there with permissions set to 755.
D
is the d=
estination directory where the application is installed to before it is pac=
kaged.
${bindir}
=
is the directory where most binary applications are installed, typically&nb=
sp;/usr/bin
.
For a more in-depth explanation of BitBake recipes, syntax, and variable= s, see the Recipe Ch= apter of the OpenEmbedded User Manual.
Setting up eMMC usually is the last step at development stage after the = development work is done at your SD card or NFS environments. From software= point of view, eMMC is nothing but a non-removable SD card on board. For&n= bsp;SMARC-iMX8M, the SD card is always emulated as /dev/mmcblk1 an= d on-module eMMC is always emulated as /dev/mmcblk0. Setting up eMMC now is= nothing but changing the device descriptor.
This section gives a step-by-step procedure to setup eMMC flash. Users c= an write a shell script your own at production to simplify the steps.
First, we need to backup the final firmware from your SD card or NFS.
Insert SD card into your Linux PC. For these instructions, we are assumi= ng: DISK=3D/dev/mmcblk0, "lsblk" is very useful for determining t= he device id.
For these instruction, we are assuming: DISK=3D/dev/mmcblk0, "lsblk= " is very useful for determining the device id.
=20 =20Mount Partitions:
On some systems, these partitions may be auto-mounted...
=20 =20
Copy Image to rootfs pa= rtition:
=20 =20Copy uEnv.txt to rootfs= partition:
Copy and paste the following contents to /media/rootfs/home/root ($ sudo= vim /media/rootfs/home/root/uEnv.txt)
=20 =20Copy device tree blob t= o rootfs partition:
=20 =20Copy real rootfs to roo= tfs partition:
=20 =20Remove SD card:
=20 =20Insert this SD card into your SMARC-iMX8M device.
Now it will be almost the same as you did when setup your SD card, but t= he eMMC device descriptor is /dev/mmcblk0 now. Booting up the device.
=20 =20Erase eMMC:
=20 =20Create Partition Layout:
=20 =20Format Partitions:
=20 =20Mount Partitions:
=20 =20Copy uEnv.txt/Image/*.dtb to the boot partition
=20 =20
Unmount eMMC:
=20 =20
Switch your Boot Select to eMMC and you will be able to boot up from eMM= C now.
For playing video, we can use three solutions to support it. <= /span>
a) # gplay-1.0 <video file>
b) # gst-launch-1.0 playbin uri=3Dfile://<video absolute path>
c) ( i ) if video container on .mp4 format
# gst-launch-1.0 fil= esrc location=3D<file name.mp4> typefind=3Dtrue ! video/quicktime ! q= tdemux ! queue max-size-time=3D0 ! vpudec ! queue max-size-time=3D0 ! kmssi= nk force-hantrope=3Dtrue sync=3Dfalse &
( ii ) if video container on .ts format
# gst-launch-1.0 filesrc location=3D&l= t;file name.ts> typefind=3Dtrue ! video/mpegts ! tsdemux ! queue max-siz= e-time=3D0 ! vpudec ! queue max-size-time=3D0 ! waylandsink
Last updated 2019-04-10