Difference between revisions of "iMX8M Industrial Yocto Image Building"

From Voipac Wiki
Jump to navigation Jump to search
 
(23 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
<div style="float:right">__TOC__</div>
 
<div style="float:right">__TOC__</div>
  
This Wiki page guides thorugh the process of downloading the Yocto Project source files for release 3.1 (dunfell), preparing and building images for the iMX8M Industrial Development Kit.
+
This Wiki page guides through the process of downloading the Yocto Project source files for release 3.1 (dunfell), their synchronization and building images for the iMX8M Industrial Development Kit.
  
Before images can be built, [[iMX8M Industrial Yocto Prerequisities|neccesary steps need to be performed]] to setup the host machine.
+
Before images can be built, [[iMX8M Industrial Yocto Prerequisites|necessary steps need to be performed]] to setup the host machine.
  
  
Line 34: Line 34:
 
# Copy manifests helper function
 
# Copy manifests helper function
 
copy_manifests() {
 
copy_manifests() {
rm -rf .repo
+
rm -rf .repo
mkdir -p .repo/manifests
+
mkdir -p .repo/manifests
cp scripts/voipac.xml .repo/manifests/
+
cp scripts/voipac.xml .repo/manifests/
 
}
 
}
  
Line 44: Line 44:
 
         repo init -u "$(pwd)"/.repo/repo -b default -m voipac.xml
 
         repo init -u "$(pwd)"/.repo/repo -b default -m voipac.xml
 
fi
 
fi
       
+
     
 
repo sync --optimized-fetch
 
repo sync --optimized-fetch
  
Line 52: Line 52:
  
  
The script automatically updates the latest meta layers. These layers include manifest files discribing where all the sources are located. Afterwards all the directories are synchronized.
+
This script automatically updates the latest meta layers. These layers include manifest files describing where all the sources are located. Afterwards all the directories are synchronized.
  
The second to last command defines the machine for which the last command ''bitbake'' compiles and builds output binaries. Besides specifiyng the setup for iMX8M Industrial Development Kit by '''MACHINE''' string, '''DISTRO''' provides several building options selecting graphical interface:
+
The second to last '' source'' command defines the machine for which the last command ''bitbake'' compiles and builds output binaries. Besides describing the specifics for iMX8M Industrial Development Kit, '''DISTRO''' provides several graphical interface options:
* '''fsl-imx-wayland''': Wayland weston graphics
+
* '''fsl-imx-wayland''': Wayland/Weston graphics
 
* '''fsl-imx-xwayland''': Wayland graphics and X11
 
* '''fsl-imx-xwayland''': Wayland graphics and X11
 
* '''fsl-imx-fb''': framebuffer graphics (no Wayland or X11)
 
* '''fsl-imx-fb''': framebuffer graphics (no Wayland or X11)
  
The script can be run to fetch and build the Yocto images by simply calling the file:
+
 
 +
The script can be run to fetch and build the Yocto images by simply calling its filename:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
./build_image.sh
 
./build_image.sh
 
</syntaxhighlight>
 
</syntaxhighlight>
  
'''''Note:''''' Make sure that synchronization finished with no errors showcasing it by the following massage:
+
'''''Note:''''' Make sure that the synchronization finished without errors displaying the successful fetching with the following massage:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
repo sync has finished successfully.
 
repo sync has finished successfully.
 
</syntaxhighlight>
 
</syntaxhighlight>
  
'''''Note:''''' The first successful build can take several hours (depending on multiple factors affecting the host machine like CPU, internet bandwidth, alocated disk space, etc.).
+
'''''Note:''''' The first successful build can take several hours (depending on multiple factors affecting the host machine like CPU, internet bandwidth, allocated disk space, etc.).
  
 
== Locating output files ==
 
== Locating output files ==
After the complyiling process completed, the freshly built oputput files are located in directory:
+
After the compiling process was completed, the freshly built output files are located in the directory:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
cd ~/voipac-yocto/yocto-imx8m-voipac/build-voipac/tmp/deploy/images
 
cd ~/voipac-yocto/yocto-imx8m-voipac/build-voipac/tmp/deploy/images
 
</syntaxhighlight>
 
</syntaxhighlight>
  
The files which need to be flashed into the development kit are located in this directory. To make them more accesible, the files can be copied and unpacked:
+
This directory also include binaries to be flashed into the development kit. To make them more accessible, the files can be copied and unpacked:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
cp -prv imx-boot ~/
 
cp -prv imx-boot ~/
Line 83: Line 84:
 
gzip -d ~/voipac-image-imx8mq-voipac.wic.gz
 
gzip -d ~/voipac-image-imx8mq-voipac.wic.gz
 
</syntaxhighlight>
 
</syntaxhighlight>
 +
'''''Note:''''' The number string (e.g. ''20230512212054'') in the filename differs between every build as it displays the timestamp of the compilation.
  
At this point everything was prepared to flash the binaries. Follow the [[iMX8M Industrial Flashing Procedure|flashing procedure]] instructions how to start the development kit with these compiled bianries.
+
== Flashing the binaries ==
 +
At this point everything was prepared to flash the binaries. Follow the [[iMX8M Industrial Flashing Procedure|flashing procedure]] instructions to start the development kit with the compiled images.

Latest revision as of 19:27, 11 December 2023

This Wiki page guides through the process of downloading the Yocto Project source files for release 3.1 (dunfell), their synchronization and building images for the iMX8M Industrial Development Kit.

Before images can be built, necessary steps need to be performed to setup the host machine.


All the source files for this customized Yocto Project, together with the recent changes made, can be inspected and downloaded at the Voipac GitHub repository.

Cloning the project

Create a new directory for the project environment:

mkdir ~/voipac-yocto
cd ~/voipac-yocto

Clone the iMX8M Industrial Yocto Project into the host machine:

git clone https://github.com/voipac/yocto-imx8m-voipac.git

Building the image

Voipac provides quick and simple-to-use option how to build an image by using prepared script:

#!/bin/bash

set -e

# Copy manifests helper function
copy_manifests() {
rm -rf .repo
mkdir -p .repo/manifests
cp scripts/voipac.xml .repo/manifests/
}

# Fetch the latest meta layers
if ! diff -q .repo/manifests/voipac.xml scripts/voipac.xml >/dev/null 2>&1; then
        copy_manifests
        repo init -u "$(pwd)"/.repo/repo -b default -m voipac.xml
fi
       
repo sync --optimized-fetch

MACHINE=imx8mq-voipac DISTRO=fslc-xwayland source ./setup-environment build-voipac
bitbake -f voipac-image


This script automatically updates the latest meta layers. These layers include manifest files describing where all the sources are located. Afterwards all the directories are synchronized.

The second to last source command defines the machine for which the last command bitbake compiles and builds output binaries. Besides describing the specifics for iMX8M Industrial Development Kit, DISTRO provides several graphical interface options:

  • fsl-imx-wayland: Wayland/Weston graphics
  • fsl-imx-xwayland: Wayland graphics and X11
  • fsl-imx-fb: framebuffer graphics (no Wayland or X11)


The script can be run to fetch and build the Yocto images by simply calling its filename:

./build_image.sh

Note: Make sure that the synchronization finished without errors displaying the successful fetching with the following massage:

repo sync has finished successfully.

Note: The first successful build can take several hours (depending on multiple factors affecting the host machine like CPU, internet bandwidth, allocated disk space, etc.).

Locating output files

After the compiling process was completed, the freshly built output files are located in the directory:

cd ~/voipac-yocto/yocto-imx8m-voipac/build-voipac/tmp/deploy/images

This directory also include binaries to be flashed into the development kit. To make them more accessible, the files can be copied and unpacked:

cp -prv imx-boot ~/
cp -prv voipac-image-imx8mq-voipac-20230512212054.rootfs.wic.gz ~/voipac-image-imx8mq-voipac.wic.gz
gzip -d ~/voipac-image-imx8mq-voipac.wic.gz

Note: The number string (e.g. 20230512212054) in the filename differs between every build as it displays the timestamp of the compilation.

Flashing the binaries

At this point everything was prepared to flash the binaries. Follow the flashing procedure instructions to start the development kit with the compiled images.