Linux 5.10, Trizeps VIII (-/Mini/Plus)
https://git.seco.com/seco-ne/kernel/linux-imx-kuk
Linux 5.10.9 based on Android 11.0.0_2.0.0 | ssh://git@git.seco.com:seco-ne/kernel/linux-imx-kuk.git | kuk_lf-5.10.y_android-compilable |
Previous Versions
Branch/Tag | Comment |
---|---|
|
|
Kernel Binaries
Date | Changelog | Download |
---|---|---|
28.02.2022 |
|
How to Build Linux Kernel for Trizeps VIII & Trizeps VIII Mini
This is only a quick-reference on how to build a Linux Kernel including Seco specific changes.
For details please view the Linux and NXP i.MX8M documentation.
Get the source code of linux-imx from git repository:
$ git clone https://git.seco.com/seco-ne/kernel/linux-imx-kuk.git -b kuk_lf-5.10.y_android-compilable
Setup Cross-Build environment (View Software-Development-Kit on how to install.):
$ . /opt/fsl-imx-wayland/5.10-hardknott/environment-setup-cortexa53-crypto-poky-linux
$ export ARCH=arm64
Build Linux-Kernel from source code:
~/linux-imx$ make kuk_defconfig
~/linux-imx$ make
This will generate linux kernel ('Image') and device-tree binary ('*.dtb') files.
After you generated the kernel, you might want to build the kernel-modules:
Note: When the kernel boots it loads kernel-modules from the root-filesystem at '/lib/modules/<kernel-build-number>' (i.e. /lib/modules/5.10.9).
Note: if kernel stops compiling missing bio.h : –> apt install libssl-dev
Update Kernel
Updating the kernel involves to copy 'Image' and the kernel-module directory to the device.
If the kernel-build-version did not change, copy of the kernel-module directory can be omitted.
Update using USB and bootloader
Enter the bootloader command console and run:
This will configure the USB-OTG port to emulate a USB-Mass-Storage device.
Example:
After calling 'ums 0 mmc 0' a new device 'sdf' appears in the list of mounted devices.
Copy the kernel-'Image' and device-tree binary files to the first partition.
Copy the kernel-modules-directory to the second partition that contains the root-filesystem.
Hints on using the Kernel
Device Tree
The Linux-kernel will use a Device-Tree-Binary file (.dtb) to determine how the Trizeps module is used in a system (i.e. which drivers to load). The device-tree files can be found at:
When building the Linux-kernel .dts source-files are converted to .dtb binary files.
DeviceTree (dtb) | Module | Description |
---|---|---|
Trizeps VIII Mini in i-PAN T7 V1 panel | ||
Trizeps VIII Mini in i-PAN T7 V2 panel | ||
Trizeps VIII Mini in pConXS V1 with capacitive touch EDT 7inch display | ||
Trizeps VIII Mini in pConXS V2 with capacitive touch EDT 7inch display | ||
Trizeps VIII Mini in pConXS V3 with ATM0700 7inch display | ||
Trizeps VIII Mini in pConXS V3 with AM19201080 10inch display | ||
SBCSOM with ATM0700 7inch display | ||
SBCSOM with HDMI display |
When you open the u-boot command prompt and output the environment, you can determine which device-tree is used:
To change this you can call:
'env save' will store this setting for subsequent boots.
Root-Filesystem
To have a full running Linux-system you will need:
Bootloader ( U-Boot, Trizeps VIII Mini ), which loads the Device-Tree and Linux-Kernel.
Linux Kernel
Root-Filesystem, which contains applications, configuration files etc.
There are different approaches on how to create a root-filesystem.
Basicly its a linux-distribution like Debian, where the system is put together by packages or like Yocto, where recipes define what needs to be built and put inside the file-system: