Building Images¶
Setup Build Directory¶
We provide a script, karo-setup-release.sh, that simplifies the setup for our machines. To use the script, the name
of the specific machine to be built for needs to be specified as well as the desired distro. The script sets up a
directory and the configuration files for the specified machine and distro. It also adds our layers to the bblayers.conf
file.
There are different configurations you can choose from.
Ka-Ro DISTRO configurations
|
Description |
|---|---|
karo-minimal |
Ka-Ro Linux Distro with minimal read-only rootfs |
karo-wayland |
Ka-Ro Linux Distro with wayland backend |
karo-xwayland |
Ka-Ro Linux Distro with xwayland backend |
karo-x11 |
Ka-Ro Linux Distro with X11 support |
Possible
MACHINEconfigurations:
NXP modules can only be built with the karo-nxp-bsp, STM and Renesas modules only with the karo-bsp.
|
|
|---|---|
|
|
|
|
Use this command to setup your build directory (specify the distro you want to use, the machine, and the build directory):
General Example:
DISTRO=<distro> MACHINE=<machine> source karo-setup-release.sh -b <build-dir>
When the script has run, your current directory changes to the <build-dir> you chose before.
Specific Example:
DISTRO=karo-minimal MACHINE=<machine> source karo-setup-release.sh -b build-<machine>
Returning to existing build:
You can return to an already setup build directory by running:
source setup-environment <build-dir>
Configuration¶
To enable different features for your build you can modify the conf/local.conf file inside your <build-dir>.
Baseboard (optional)¶
Machine |
Supported Baseboards |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To set the KARO_BASEBOARD variable, modify your conf/local.conf:
KARO_BASEBOARD = "baseboard"
Machine Features¶
Machine Feature |
Description |
Default? |
|---|---|---|
emmc |
eMMC storage support |
Automatically selected via $MACHINE if supported |
nand |
NAND storage support |
Automatically selected via $MACHINE if supported |
lcd |
LCD interface support |
Automatically selected via $MACHINE if supported |
lvds |
LVDS interface support |
Automatically selected via $MACHINE if supported |
dsi83 |
SN65DSI83 mipi-lvds bridge support |
Automatically selected via $MACHINE if supported |
To expand the MACHINE_FEATURES variable to your needs, modify your conf/local.conf:
MACHINE_FEATURES:append = " item1 item2 ..."
Distro Features¶
Distro Feature |
Description |
Default? |
|---|---|---|
systemd |
Changes init-system to systemd, e.g. neccessary when using Debian |
No |
ipv6 |
IPV6 support |
No |
wifi |
WiFi support |
No |
bluetooth |
Bluetooth support |
No |
To expand the DISTRO_FEATURES variable to your needs, modify your conf/local.conf:
DISTRO_FEATURES:append = " item1 item2 ..."
Build the Image¶
Build the image with the following command inside your <build-dir>:
bitbake <image>
Here are the different images that can be build:
Image |
Description |
DISTRO |
Provided by layer |
|---|---|---|---|
karo-image-minimal |
Image with minimal read-only rootfs |
karo-minimal |
meta-karo-distro |
karo-image-weston |
Image with basic weston desktop, graphics accelerated |
karo-(x)wayland |
meta-karo-distro |
karo-image-qt6 |
Image with basic weston desktop and QT6. To use it wit QT-Creator see QT Guide |
karo-(x)wayland |
meta-karo-distro |
karo-image-x11 |
Image with X11 support |
karo-x11 |
meta-karo-distro |
karo-image-ml |
Image including and supporting imx Machine-Learning demos See Machine Learning Guide |
karo-(x)wayland |
meta-karo-distro |
karo-image-basler |
Image with Basler Camera support on weston desktop Also including imx Machine-Learning demos See Machine Learning Guide |
karo-xwayland |
meta-karo-distro |
To build the SDK of a certain image run inside your <build-dir>:
bitbake <image> -c populate_sdk
Tip
The SDK can e.g. be used for VS Code Cross-Compilation.
Image Deployment¶
After a build is complete, the results reside in the <build-dir>/tmp/deploy/images/<machine>/<image> sub-directory. An image is, for the most part, specific to the machine set in the environment setup. Each image build usually creates U-Boot, kernel, and an image based on the machine and distro configuration files.
i.MX¶
To continue programming your board with these images, simply cd into the above mentioned <image> folder inside deploy folder and run:
uuu -v
For further information about uuu see UUU - Universal Update Utility.
STM32MP¶
To continue with these images see Flashing STM32MP modules.
RZ/G2L¶
To continue with these images see Flashing RZ/G2L modules.