Architecture¶
meta-tolomeo splits the platform into layers by concern, so an integrator replaces the machine and keeps the distribution and the application stack.
Each Layer Owns One Concern¶
Each layer can evolve independently of the others. The sections below name the concern of each layer in the repository.
meta-tolomeo-app¶
The ToloMEO application stack: the ToloMEO Edge agent, NATS, tlm-services, Glances, the image-devel, image-prod and
image-test-prod images, and the packagegroup-tlm-* package groups. It is separate from the distribution layer so image
composition can change without touching distribution policy.
meta-tolomeo-bsp¶
The machine includes every BSP requires: the eMMC and NAND storage profiles, u-boot-secure-boot.inc and the U-Boot FIT
signature fragment. It contributes no machines.
meta-tolomeo-containers¶
Docker image recipes (Glances, InfluxDB) and the container_provisioner class, which archives a container image into the
root filesystem.
meta-tolomeo-distro¶
The distribution base tolomeo.inc and the custom classes: artifact collection, CycloneDX SBOM and VEX generation, the
SWUpdate configuration and delta classes, and the tolomeo_* configuration classes. It also holds the recipes that
implement the update infrastructure: the SWUpdate bbappend, the OTA monitor and the system-update-postboot service. It
centralizes the cross-cutting concerns (SBOM generation, update infrastructure, integrity checking) so hardware and
application layers do not repeat them.
meta-tolomeo-nxp¶
The NXP i.MX secure-boot support: the xhab, sigtool and kernel_fitimage_mcore classes, the U-Boot HAB and AHAB
configuration, the NXP signer and imx-mkimage recipes, and the device-tree hardware revision for SWUpdate. It has no
machine configurations; machines come from your BSP.
meta-tolomeo-offline¶
The opt-in offline capabilities: tlm-bridge, a local NATS server, PostgreSQL with TimescaleDB, and the
packagegroup-tlm-system-offline package group. kas/offline.yml enables it.
meta-tolomeo-qemu¶
The QEMU machines for x86-64, AArch64 and ARM, the tolomeo-prod and tolomeo-devel reference distributions, the
imgen-* update-package recipes, and the disk-provisioning scripts. The machines provide a functionally equivalent
virtual target, so the distribution and the application stack can be developed and tested without hardware.
meta-tolomeo Stops at the Machine¶
meta-tolomeo provides the distribution and the ToloMEO application stack, including the services that give the device access to ToloMEO Cloud features. The BSP is responsible for the machine. This boundary determines which files an integration project writes and which it only references.
| meta-tolomeo provides | The BSP is responsible for |
|---|---|
tolomeo.inc — the distribution base |
A distribution include and one distro configuration per flavor deriving from it |
| CVE check, CycloneDX/VEX, SWUpdate, secure boot and hardening classes and includes | The DISTRO_FEATURES selection the product needs |
tolomeo-image-common.inc, packagegroup-tlm-*, ToloMEO Cloud service recipes |
An image include and image recipes deriving from them |
| A kas fragment per layer, declaring repositories, config blocks and passthrough variables | kas/base.yml, kas/common.yml, the target files and kas-ci/ |
| Storage and secure-boot machine includes, plus a reference machine to build against | Machine configurations, board recipes and WIC (.wks) partition layouts |
meta-tolomeo-distro ships only conf/distro/include/. The reference distributions tolomeo-devel and tolomeo-prod
live in meta-tolomeo-qemu; a BSP derives its own distributions from tolomeo.inc instead of inheriting them.
QEMU Machines Replace Hardware During Development¶
meta-tolomeo-nxp adds NXP i.MX support to a machine from your BSP, so the i.MX row below carries no machine name. The
three QEMU machines are provided for development and testing.
| Platform | Machine | Use Case |
|---|---|---|
| NXP i.MX | (BSP-specific) | Production hardware deployment |
| QEMU x86-64 | tolomeo-qemux86-64 |
Development and testing |
| QEMU AArch64 | tolomeo-qemuarm64 |
Development and testing |
| QEMU ARM | tolomeo-qemuarm |
Development and testing |
Build Targets Follow the Machine, Distro and Image¶
The kas configuration files for the QEMU x86-64 machine follow one naming convention:
| Configuration | Machine | Distribution | Image | Purpose |
|---|---|---|---|---|
tolomeo-qemux86-64_tolomeo-prod_image-prod.yml |
x86-64 QEMU | tolomeo-prod |
image-prod |
Production image |
tolomeo-qemux86-64_tolomeo-devel_image-devel.yml |
x86-64 QEMU | tolomeo-devel |
image-devel |
Development image |
tolomeo-qemux86-64_tolomeo-prod_image-test-prod.yml |
x86-64 QEMU | tolomeo-prod |
image-test-prod |
Security validation |
tolomeo-qemux86-64_imgen-update-full.yml |
x86-64 QEMU | tolomeo-prod |
imgen-update-full |
SWUpdate full package |
tolomeo-qemux86-64_imgen-update-delta.yml |
x86-64 QEMU | tolomeo-prod |
imgen-update-delta |
SWUpdate delta package |
See also
- kas Configuration — the build configuration files
- Machine Configuration — the machine contract
- Build Your Own BSP Layer — apply the layer structure

