Configure meta-tolomeo for Your Machine¶
This guide covers overriding the ToloMEO TLM_ configuration interface from your own layer and verifying that your
machine configuration is complete.
Prerequisites¶
- An integration project that consumes meta-tolomeo — see Build Your Own BSP Layer.
Override a Configuration Variable¶
The TLM_ variables are weak defaults (?=), so setting a value anywhere with stronger precedence overrides the
class default. Set it in the location that matches its scope:
- Machine configuration — for values tied to the hardware (partition devices, filesystem types, mount points).
- Distribution include — for values shared by every machine in your product line.
local.conf— for a one-off local override during development. It is parsed before the machine configuration, so it cannot override a variable that a storage profile hard-assigns (TLM_DATA_DIR,TLM_CERTS_DIR,TLM_CERTS_FSTYPEand, in the eMMC profile,TLM_CERTS_DEVICE).
For example, to relocate the persistent data directory and the configuration directory, set them in your machine
configuration. Assign TLM_DATA_DIR after the require of the storage profile, which hard-assigns it:
Redirect the OTA Location¶
The OTA paths are coupled: TLM_OTA_FILE, the checkpoint, and the descriptor all derive from TLM_OTA_DIR and
TLM_OTA_FILENAME. Override the directory and filename, not the derived paths, so every consumer moves together:
After overriding, confirm the coupled values resolve consistently:
kas shell kas/tolomeo-qemux86-64_tolomeo-prod_image-prod.yml -c 'bitbake -e swupdate | grep ^TLM_OTA_'
Provide the Required Machine Variables¶
Some recipes declare machine-supplied variables in REQUIRED_VARS. Set them in your machine configuration:
If a required variable is empty, the build stops at parse time with a message naming the recipe and the missing variable:
Check the Machine Configuration¶
A machine configuration is complete for ToloMEO's purposes when:
- It requires a base machine configuration and sets
MACHINEOVERRIDESif it derives from one. - It requires exactly one of
tolomeo-mmc-storage.incortolomeo-mtd-storage.inc. - It requires
u-boot-secure-boot.inc. -
OVERLAYFS_ETC_DEVICEandTLM_CERTS_DEVICEpoint at partitions your image actually creates. - Its WIC or flash layout creates the data and certificate partitions.
- It lives in your
-bsplayer, whoseLAYERDEPENDSnames the vendor BSP it builds on.
See also
- Configuration Classes — the full
TLM_variable reference - Machine Configuration — the machine contract and storage profiles
- Configuration Interface — why the interface is designed this way