Seitenleiste


Access to information is restricted depending on your login. Request login-information through our contact form.

service:linux:yocto:zeus:zeus

Yocto Zeus

We do not have a Keith&Koep specific Zeus Yocto recipe.
In short we describe on how to build the generic NXP Yocto recipe and patch this with Keith & Koep U-Boot and Linux 5.4, Trizeps VIII (-/Mini/Nano)-Kernel.

Yocto Images

Yocto Project Setup

This is only a quick-reference on how to setup and build a Yocto image.
For details please view the Linux and NXP i.MX8M documentation. Especially the „i.MX_Yocto_Project_User's_Guide“.

$ mkdir <project-dir>
$ cd <project-dir>
$ repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b <Branch> -m <Manifest-File>
$ repo sync

Example

$ mkdir imx-yocto-bsp
$ cd imx-yocto-bsp
$ repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-zeus -m imx-5.4.24-2.1.0.xml
$ repo sync

When this process is completed, the source code is checked out into the directory imx-yocto-bsp/sources.
You can perform repo synchronization, with the command repo sync, periodically to update to the latest code.

Distribution Remarks
fsl-imx-wayland Wayland weston graphics.
fsl-imx-xwayland Wayland graphics and X11. X11 applications using EGL are not supported.
fsl-imx-fb Frame Buffer graphics - no X11 or Wayland. Frame Buffer is not supported on i.MX 8.
Machine Remarks
imx8mmevk NXP i.MX 8M Mini Eval-Kit. Use for Trizeps VIII Mini, Myon II, SBCSOM
$ DISTRO=<Distribution> MACHINE=<Machine> source fsl-setup-release.sh -b <build-dir>

Example

$ DISTRO=fsl-imx-wayland MACHINE=imx8mmevk source fsl-setup-release.sh -b build-wayland

Image Build

After the setup of the build-environment, you can start to run bitbake to build the image.

$ bitbake <project-image>
Project-Image Target Provided by layer
core-image-minimal A small image that only allows a device to boot. Poky
core-image-base A console-only image that fully supports the target device hardware. Poky
core-image-sato An image with Sato, a mobile environment and visual style for mobile devices. The image supports a Sato theme and uses Pimlico applications. It contains a terminal, an editor and a file manager. Poky
imx-image-core An i.MX image with i.MX test applications to be used for Wayland backends. This image is used by our daily core testing. meta-imx/meta-sdk
fsl-image-machine-test An FSL Community i.MX core image with console environment - no GUI interface. meta-freescale-distro
imx-image-multimedia Builds an i.MX image with a GUI without any Qt content. meta-imx/meta-sdk
imx-image-full Builds an opensource Qt 5 image with Machine Learning features. These images are only supported for i.MX SoCwith hardware graphics. They are not supported on the i.MX 6UltraLite, i.MX 6UltraLiteLite, i.MX 6SLL, and i.MX 7Dual. meta-imx/meta-sdk

After reboot or opening a new terminal window, you can restart the build environment with:

$ source setup-environment <build-dir>

Example

$ source setup-environment ./build-wayland
$ bitbake imx-image-multimedia

After a build is complete, the image can be found at <build-dir>/tmp/deploy/images.
The image_name will be <Project-Image>-<Machine>.sdcard.bz2; i.e. imx-image-multimedia-imx8mmevk.sdcard.bz2.

Deploy Image

How to deploy the image depends on wether you have a module with eMMC oder uSD-card-slot.
For a module with eMMC you will use the NXP Universal Update Utility (UUU) to update the files while the module is in USB Serial Download Mode.
For a module with uSD-Slot you can either use NXP Universal Update Utility (UUU) or deploy the image directly to the uSD-card using an uSD-card-reader with your PC.

Flash Image to SD card

Identify the uSD-card plugged to your PC; i.e. by using „lsblk | grep disk“

$ bunzip2 -dk -f <image_name>.sdcard.bz2
$ sudo dd if=<image_name>.sdcard of=/dev/sd<disk> bs=1M conv=fsync

Flash Image to eMMC

Put the module into USB Serial Download Mode and run:

$ sudo ./uuu -b emmc_all <bootloader> <image_name>.sdcard

Patch Image with Keith & Koep Linux Bootloader and Kernel

Bootloader

Linux-Kernel

Select Device-Tree

After flashing the image you will need to select the correct device-tree for your device.

This can be done in two ways:
1. Through the bootloader-console (115k2, 8N1):

u-boot=> env set fdt_file kuk-trizeps8mini-pconxs-edt7.dtb
u-boot=> env save

You can get a list of installed *.dtb files by calling „fatls mmc 0“.

2. Rename the wished device-tree file (.dtb) to the default fdt_file setting:

Module Default fdt_file setting
Trizeps VIII kuk-trizeps8.dtb
Trizeps VIII Mini kuk-trizeps8mini.dtb
Myon II kuk-trizeps8mini.dtb

(Myon II and Trizeps VIII Mini use the same bootloader )

Cookies helfen bei der Bereitstellung von Inhalten. Durch die Nutzung dieser Seiten erklären Sie sich damit einverstanden, dass Cookies auf Ihrem Rechner gespeichert werden. Weitere Information
service/linux/yocto/zeus/zeus.txt · Zuletzt geändert: 2021/09/02 17:25 von