Generate Tezi image


I’ve been trying for a few days to generate automatically a Tezi image compatible with the installer without any success.

I followed, the tutorial on your website : Build a Reference Image with Yocto Project/OpenEmbedded | Toradex Developer Center and I had the image generated.

However, when I want to add it to my project the image isn’t generated.

I’m working with Yocto Kirkstone

My conf/local.conf is :

# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at
# local.conf.sample.extended which contains other examples of configuration which
# can be placed in this file but new users likely won't need any of them
# initially.
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.
IMAGE_INSTALL:append = " zabbix openssh usbutils bash libgpiod libgpiod-tools rfid-reader-config whiptail ntpd-start openvpn mercury cronie rfid-reader"
IMAGE_CLASSES:append = " image_type_tezi"
INHERIT += "toradex-sanity"
# Machine Selection
# You need to select a specific machine to target the build with. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#MACHINE ?= "qemuarm"
#MACHINE ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
# There are also the following hardware board target machines included for 
# demonstration purposes:
#MACHINE ?= "beaglebone-yocto"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "edgerouter"
# This sets the default machine to be qemux86-64 if no other machine is selected:
MACHINE ??= "raspberrypi4-64"

PREFERRED_VERSION_cargo = "1.63.0"

# Where to place downloads
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
# The default is a downloads directory under TOPDIR which is the build directory.
#DL_DIR ?= "${TOPDIR}/downloads"

# Where to place shared-state files
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
# The default is a sstate-cache directory under TOPDIR.
#SSTATE_DIR ?= "/yocto/sstate-cache"

# Where to place the build output
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
# The default is a tmp directory under TOPDIR.
#TMPDIR = "${TOPDIR}/tmp"

# Default policy config
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing 
# these defaults.
DISTRO ?= "poky"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream 
# source control systems. This is just mentioned here as an example, its not
# useful to most new users.
# DISTRO ?= "poky-bleeding"

# Package Management configuration
# This variable lists which packaging formats to enable. Multiple package backends
# can be enabled at once and the first item listed in the variable will be used
# to generate the root filesystems.
# Options are:
#  - 'package_deb' for debian style deb files
#  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
#  - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to rpm:
PACKAGE_CLASSES ?= "package_rpm"
#PACKAGE_CLASSES ?= "package_deb"

# SDK target architecture
# This variable specifies the architecture to build SDK items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host).
# Supported values are i686, x86_64, aarch64
#SDKMACHINE ?= "i686"

# Extra image configuration defaults
# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
# images. Some of these options are added to certain image types automatically. The
# variable can contain the following options:
#  "dbg-pkgs"       - add -dbg packages for all installed packages
#                     (adds symbol information for debugging/profiling)
#  "src-pkgs"       - add -src packages for all installed packages
#                     (adds source code for debugging)
#  "dev-pkgs"       - add -dev packages for all installed packages
#                     (useful if you want to develop against libs in the image)
#  "ptest-pkgs"     - add -ptest packages for all ptest-enabled packages
#                     (useful if you want to run the package test suites)
#  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
#  "tools-debug"    - add debugging tools (gdb, strace)
#  "eclipse-debug"  - add Eclipse remote debugging support
#  "tools-profile"  - add profiling tools (oprofile, lttng, valgrind)
#  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
#  "debug-tweaks"   - make an image suitable for development
#                     e.g. ssh root access has a blank password
# There are other application targets that can be used here too, see
# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
# We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"

# Additional image features
# The following is a list of additional classes to use when building images which
# enable extra features. Some available options which can be included in this variable
# are:
#   - 'buildstats' collect build statistics
USER_CLASSES ?= "buildstats"

# Runtime testing of images
# The build system can test booting virtual machine images under qemu (an emulator)
# after any root filesystems are created and run tests against those images. It can also
# run tests against any SDK that are built. To enable this uncomment these lines.
# See classes/test{image,sdk}.bbclass for further details.
#IMAGE_CLASSES += "testimage testsdk"
#TESTIMAGE_AUTO:qemuall = "1"

# Interactive shell configuration
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):

# Disk Space Monitoring during the build
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less than 100MB or 1K inodes, perform a hard halt
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necessary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
    STOPTASKS,${DL_DIR},1G,100K \
    STOPTASKS,/tmp,100M,100K \
    HALT,${TMPDIR},100M,1K \
    HALT,${DL_DIR},100M,1K \
    HALT,${SSTATE_DIR},100M,1K \

# Shared-state files from other locations
# As mentioned above, shared state files are prebuilt cache data objects which can be
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
# This can be a filesystem directory, or a remote url such as https or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#file://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \
#file://.* file:///some/local/dir/sstate/PATH"

# Yocto Project SState Mirror
# The Yocto Project has prebuilt artefacts available for its releases, you can enable
# use of these by uncommenting the following lines. This will mean the build uses
# the network to check for artefacts at the start of builds, which does slow it down
# equally, it will also speed up the builds by not having to build things if they are
# present in the cache. It assumes you can download something faster than you can build it
# which will depend on your network.
# Note: For this to work you also need hash-equivalence passthrough to the matching server
#SSTATE_MIRRORS ?= "file://.*;downloadfilename=PATH"

# Qemu configuration
# By default native qemu will build with a builtin VNC server where graphical output can be
# seen. The line below enables the SDL UI frontend too.
PACKAGECONFIG:append:pn-qemu-system-native = " sdl"
# By default libsdl2-native will be built, if you want to use your host's libSDL instead of 
# the minimal libsdl built by libsdl2-native then uncomment the ASSUME_PROVIDED line below.
#ASSUME_PROVIDED += "libsdl2-native"

# You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
# a handy set of menus for controlling the emulator.
#PACKAGECONFIG:append:pn-qemu-system-native = " gtk+"

# Hash Equivalence
# Enable support for automatically running a local hash equivalence server and
# instruct bitbake to use a hash equivalence aware signature generator. Hash
# equivalence improves reuse of sstate by detecting when a given sstate
# artifact can be reused as equivalent, even if the current task hash doesn't
# match the one that generated the artifact.
# A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format
#BB_HASHSERVE = "auto"

# Memory Resident Bitbake
# Bitbake's server component can stay in memory after the UI for the current command
# has completed. This means subsequent commands can run faster since there is no need
# for bitbake to reload cache files and so on. Number is in seconds, after which the
# server will shut down.

# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.

To generate my image I do :

MACHINE=colibri-imx6ull-emmc bitbake core-image-minimal

And the content of my deploy directory is the following :

(yocto) ➜  build-rpi ls -l tmp/deploy/images/colibri-imx6ull-emmc
total 50036
lrwxrwxrwx 2 bort bort       40 oct 21 09:52 boot.scr-colibri-imx6ull-emmc -> boot.scr-colibri-imx6ull-emmc-2020.07-r0
-rw-r--r-- 2 bort bort     3653 oct 21 09:52 boot.scr-colibri-imx6ull-emmc-2020.07-r0
-rw-r--r-- 2 bort bort     2775 nov  2 11:25 core-image-minimal-colibri-imx6ull-emmc-20221102152445.rootfs.manifest
-rw-r--r-- 2 bort bort 10276856 nov  2 11:26 core-image-minimal-colibri-imx6ull-emmc-20221102152445.rootfs.tar.xz
-rw-r--r-- 2 bort bort     3153 nov  2 11:25 core-image-minimal-colibri-imx6ull-emmc-20221102152445.rootfs.wic.bmap
-rw-r--r-- 2 bort bort 25312840 nov  2 11:25 core-image-minimal-colibri-imx6ull-emmc-20221102152445.rootfs.wic.gz
-rw-r--r-- 2 bort bort   516962 nov  2 11:25 core-image-minimal-colibri-imx6ull-emmc-20221102152445.testdata.json
lrwxrwxrwx 2 bort bort       70 nov  2 11:25 core-image-minimal-colibri-imx6ull-emmc.manifest -> core-image-minimal-colibri-imx6ull-emmc-20221102152445.rootfs.manifest
lrwxrwxrwx 2 bort bort       68 nov  2 11:26 core-image-minimal-colibri-imx6ull-emmc.tar.xz -> core-image-minimal-colibri-imx6ull-emmc-20221102152445.rootfs.tar.xz
lrwxrwxrwx 2 bort bort       68 nov  2 11:25 core-image-minimal-colibri-imx6ull-emmc.testdata.json -> core-image-minimal-colibri-imx6ull-emmc-20221102152445.testdata.json
lrwxrwxrwx 2 bort bort       70 nov  2 11:25 core-image-minimal-colibri-imx6ull-emmc.wic.bmap -> core-image-minimal-colibri-imx6ull-emmc-20221102152445.rootfs.wic.bmap
lrwxrwxrwx 2 bort bort       68 nov  2 11:25 core-image-minimal-colibri-imx6ull-emmc.wic.gz -> core-image-minimal-colibri-imx6ull-emmc-20221102152445.rootfs.wic.gz
-rw-r--r-- 2 bort bort     4539 nov  2 11:25 core-image-minimal.env
drwxr-xr-x 2 bort bort     4096 oct 26 16:45 devicetree
-rw-r--r-- 2 bort bort    46502 oct 26 17:04 imx6ull-colibri-emmc-eval-v3--6.0.0+git0+4fe89d07dc-r0-colibri-imx6ull-emmc-20221026204351.dtb
lrwxrwxrwx 2 bort bort       94 oct 26 17:04 imx6ull-colibri-emmc-eval-v3-colibri-imx6ull-emmc.dtb -> imx6ull-colibri-emmc-eval-v3--6.0.0+git0+4fe89d07dc-r0-colibri-imx6ull-emmc-20221026204351.dtb
lrwxrwxrwx 2 bort bort       94 oct 26 17:04 imx6ull-colibri-emmc-eval-v3.dtb -> imx6ull-colibri-emmc-eval-v3--6.0.0+git0+4fe89d07dc-r0-colibri-imx6ull-emmc-20221026204351.dtb
lrwxrwxrwx 2 bort bort       75 oct 26 17:04 kernel-config -> kernel-config--6.0.0+git0+4fe89d07dc-r0-colibri-imx6ull-emmc-20221026204351
-rw-r--r-- 2 bort bort   184716 oct 26 16:45 kernel-config--6.0.0+git0+4fe89d07dc-r0-colibri-imx6ull-emmc-20221026204351
-rw-r--r-- 2 bort bort    69050 oct 21 16:29 LA_OPT_NXP_SW.html
-rw-r--r-- 2 bort bort   378880 oct 21 16:29 marketing.tar
-rw-r--r-- 2 bort bort  2340009 oct 26 17:04 modules--6.0.0+git0+4fe89d07dc-r0-colibri-imx6ull-emmc-20221026204351.tgz
lrwxrwxrwx 2 bort bort       73 oct 26 17:04 modules-colibri-imx6ull-emmc.tgz -> modules--6.0.0+git0+4fe89d07dc-r0-colibri-imx6ull-emmc-20221026204351.tgz
drwxr-xr-x 2 bort bort     4096 oct 26 16:45 overlays
-rw-r--r-- 2 bort bort       14 oct 26 16:45 overlays.txt
-rw-r--r-- 2 bort bort      183 oct 21 16:29
-rw-r--r-- 2 bort bort     2434 oct 21 16:29 toradexlinux.png
-rw-r--r-- 2 bort bort   502784 oct 26 17:01 u-boot-colibri-imx6ull-emmc-2022.07-r0.imx
lrwxrwxrwx 2 bort bort       42 oct 26 17:01 u-boot-colibri-imx6ull-emmc.imx -> u-boot-colibri-imx6ull-emmc-2022.07-r0.imx
lrwxrwxrwx 2 bort bort       42 oct 26 17:01 u-boot.imx -> u-boot-colibri-imx6ull-emmc-2022.07-r0.imx
lrwxrwxrwx 2 bort bort       50 oct 26 17:01 u-boot-initial-env -> u-boot-initial-env-colibri-imx6ull-emmc-2022.07-r0
lrwxrwxrwx 2 bort bort       50 oct 26 17:01 u-boot-initial-env-colibri-imx6ull-emmc -> u-boot-initial-env-colibri-imx6ull-emmc-2022.07-r0
-rw-r--r-- 2 bort bort     5272 oct 26 17:01 u-boot-initial-env-colibri-imx6ull-emmc-2022.07-r0
-rw-r--r-- 2 bort bort       18 oct 21 16:29
lrwxrwxrwx 2 bort bort       72 oct 26 17:04 zImage -> zImage--6.0.0+git0+4fe89d07dc-r0-colibri-imx6ull-emmc-20221026204351.bin
-rw-r--r-- 2 bort bort 11493104 oct 26 17:04 zImage--6.0.0+git0+4fe89d07dc-r0-colibri-imx6ull-emmc-20221026204351.bin
lrwxrwxrwx 2 bort bort       72 oct 26 17:04 zImage-colibri-imx6ull-emmc.bin -> zImage--6.0.0+git0+4fe89d07dc-r0-colibri-imx6ull-emmc-20221026204351.bin

I hope you can help,

Dear @tbornon ,
Do you have any additional information (e.g. logs, error messages … ) that can help us to better understand your issue?

Best regards,

Sadly no, when I start the image generation, the process works fine (expect that I don’t get the tezi image tar file nor the image.json file).
Maybe there is a special log file which can be useful to you? If so tell me and I’ll send it


Hello @tbornon
On closer inspection it seems that you are starting with a generic Yocto image, not with one of our reference images.
Have you followed the tutorial entirely or only a part? It seems that this point is missing.

Best regards,

Hi @josep.tx

You are right, I started from a configuration I used to generate images and thought I would just have to add toradex related meta layers and I would be good to go.

Even tough I read you link, I missed the part you mentionned. Thanks for pointing it out

While thinkering around yestarday, I also ended up finding a solution to make it work. I just added the following lines to my conf/local.conf file :

# Indicate that we want to generate the Tezi image
IMAGE_FSTYPES = "teziimg"

# At the end, load configuration related to the board
include conf/machine/include/${MACHINE}.inc

I’ll try to see if I can get it to work with your solution too.

Thanks for you help

Hi @tbornon !

Searching for teziimg in Toradex layers we can see that the modules’ .conf files already setup the IMAGE_FSTYPES to teziimg. E.g.:

oe-workdir/tdxref-bsp-5/layers $ rg teziimg
80:IMAGE_FSTYPES += "teziimg"

So, I find it strange that you need to add IMAGE_FSTYPES = "teziimg" to your local.conf since the MACHINE=verdin-imx8mm variable will anyway bring the teziimg to your build.

Best regards,

1 Like

Hi @henrique.tx

You are absolutely right, the IMAGE_FSTYPES isn’t necessary.
I added it when I was trying to troubleshot my issue. When I did it, I saw that it was trying to generate the teziimg but failed and I added the include at that point.

I just tried to remove the IMAGE_FSTYPES and only keep the include and it works flawlessly


1 Like