This repository contains manifest files for the SECO Northern Europe BSP. It is the entry point for the BSP development together with the supplement tooling. See below for details.
The projects of the SECO Northern Europe GitLab group contain the source code and metadata to build Yocto images and packages for SECO Northern Europe devices based on the NXP i.MX6, i.MX6ULL and i.MX8M processors.
The Google repo tool workflow is used for the project setup.
The build system is based on the Yocto project, further information and documentation can be found at http://docs.yoctoproject.org/. The Yocto project uses so called 'layers' containing the metadata to build all needed packages, while the package sources are downloaded during the build.
The SECO Northern Europe Yocto is based on following layers:
For the imx6 based platforms (SAN*) GPU and VPU drivers the etnaviv driver is
used, included in the mainline open-source layers.
This SECO Northern Europe specific part comes as two parts layers:
meta-seconorth-machine:
seco-ne/yocto/layers/meta-seconorth-machine
This part is intended to hold all recipes needed to build the Board Support Package (BSP) for SECO Northern Europe boards.
meta-seconorth-distro:
seco-ne/yocto/layers/meta-seconorth-distro
This part is intended to hold recipes that make up the SECO Northern Europe distribution including the base image: seconorth-image.
meta-seconorth-nogplv3:
seco-ne/yocto/layers/meta-seconorth-nogplv3
This layer can be used to create an image for SECO North devices without GPLv3 software.
The manifest repository seco-ne/yocto/manifest contains the so called manifest (default.xml) for the repo tool. The manifest file contains a list of all layers and there specific revisions needed to build the image for SECO Northern Europe devices, the repo tool itself reads this manifest and handles the clone and directory setup for you.
There are some requirements to the host system.
Tested distribution is currently Ubuntu 20.04.2 LTS. An installation-Image can be found here: https://releases.ubuntu.com/20.04/ubuntu-20.04.2.0-desktop-amd64.iso
This should work as virtual machine (Virtual box ...) or bare-metal installation.
Needed tools are listed in the yocto documentation.
Execute the following commands to install them:
sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev pylint3 xterm python3-subunit mesa-common-dev zstd liblz4-tool
The release builds are executed on docker images based on crops/poky:ubuntu-20.04.
The seconorth container images can be found in the SECO gitlab container registry
Additionl development tools that may be useful:
sudo apt install git minicom gdb-multiarch crossbuild-essential-armhf meld gedit nano cscope quilt qtcreator
If available the tool can also be installed from the distributions package manager. This directly downloads the latest version from google. See https://gerrit.googlesource.com/git-repo/.
mkdir ~/bin # once
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo # once
chmod a+x ~/bin/repo # once
echo "export PATH=${PATH}:~/bin" >> ~/.bashrc # once
source ~/.bashrc
git config --global user.name "Forename Name" # use your name instead
git config --global user.email "my.name@example.com" # use your email instead
This section describes steps to create a local build dir and how to use repo to download all needed
files. After that the build directory gets setup for one specific machine
(imx6guf, imx6ullguf or imx8mguf) and distribution (guf-wayland) and a standard image is built.
mkdir -p ~/projects/yocto-seco-ne
cd ~/projects/yocto-seco-ne
repo init -u https://git.seco.com/seco-ne/yocto/manifest.git -b kirkstone
repo sync --no-clone-bundle
The repo tool stores its meta data in a hidden subdirectory called .repo.
The manifest file is stored at .repo/manifests/default.xml and is used
for the sync command which actually downloads the sources.
The selected branch is kirkstone.
After the download the resulting directory structure should look like this:
yocto-seco-ne$ tree -L 2 -a
.
├── .conf
│ ├── bblayers_imx6.conf
│ ├── bblayers_imx8.conf
│ ├── bblayers_imx8_dual-espresso.conf
│ ├── .git -> ../.repo/projects/.conf.git
│ ├── git-describe.inc
│ ├── .gitignore
│ ├── .gitlab-ci
│ ├── .gitlab-ci.yml
│ ├── .gitmodules
│ ├── LICENSE.txt
│ └── setup-environment
├── .repo
│ ├── copy-link-files.json
│ ├── manifests
│ ├── manifests.git
│ ├── manifest.xml
│ ├── project.list
│ ├── project-objects
│ ├── projects
│ ├── repo
│ └── .repo_fetchtimes.json
├── setup-environment -> .conf/setup-environment
└── sources
├── meta-freescale
├── meta-freescale-distro
├── meta-guf-distro
├── meta-guf-machine
├── meta-openembedded
├── meta-python2
├── meta-qt5
├── meta-seconorth-nogplv3
└── poky
To get the build environment ready run the environment needs to be set up.
For SECO i.MX8M platforms TANARO and Trizeps VIII Mini:
MACHINE=seco-mx8mm DISTRO=seconorth-wayland source ./setup-environment build
For SECO i.MX8MP platform Trizeps VIII Plus:
MACHINE=seco-mx8mp DISTRO=seconorth-wayland source ./setup-environment build
For the i.MX6Q/DL platforms SANTARO, SANTINO, SANTINO-LT, SANTOKA and other SAN* platforms if supported:
MACHINE=seco-mx6 DISTRO=seconorth-wayland source ./setup-environment build
Then build the default SECO Northern Europe image
bitbake seconorth-image
After the image was built the files are located under
build/tmp/deploy/images/seco-[mx8mp|mx8mm|...]/. The files needed are
installation file fng_install.sh and the root file system
seco-image6guf.tar.gz. These files can be used in a Flash-N-Go System
installation process.
See the Flash-N-Go System manual for more information.
It should not be necessary to have a SECO GitLab account to build the standard images. The public access should be sufficient to do that.
However, for customer specific layers and configurations, that are not publicly accessible, a SECO GiLab account is necessary. Contact a SECO Software expert or the Technical Support to get access.
You need too generate a key-pair and register this with your SECO GitLab account, see the gitlab docs.
ssh-keygen -t ed25519 -C "my.name@example.com" # use your email instead
cat ~/.ssh/id_ed25529.pub
Copy and add the key content to your GitLab Profile User Settings -> SSH keys)