Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
Device Tree and Overlay Setup for Torizon OS 6.8.3+build.37 - Colibri iMX8X
TorizonCore Builder Automated Approach
The most straightforward method is to use TorizonCore Builder’s automated repository cloning, which will select the correct branch based on your image metadata(1).
First, unpack your Torizon OS 6.8.3+build.37 image:
$ torizoncore-builder images unpack torizon-core-docker-colibri-imx8x-Tezi_6.8.3+build.37.tar
(2)
Then use the automated checkout command:
$ torizoncore-builder dt checkout
(2)
This command automatically selects the appropriate branch based on the metadata from your unpacked image(1).
Manual Git Commands for Colibri iMX8X
For manual cloning, you’ll need both the Linux kernel repository and the device tree overlays repository. Based on the Colibri iMX8X being an i.MX 8/8X module, use these commands(3):
$ git clone -b toradex_6.6-2.2.x-imx git://git.toradex.com/linux-toradex.git linux
$ git clone -b toradex_6.6-2.2.x-imx git://git.toradex.com/device-tree-overlays.git device-trees
(3)
Finding Available Device Trees
To locate the available device trees for your Colibri iMX8X module, use these commands:
For Colibri iMX8QuadXPlus versions:
$ find linux -name "*imx8qxp-colibri*.dts"
(3)
For Colibri iMX8DualX versions:
$ find linux -name "*imx8dx-colibri*.dts"
(3)
Checking Compatible Overlays
Once you have the repositories cloned, you can check which overlays are compatible with your specific device tree. For example, if using the imx8qxp-colibri-aster.dts device tree:
$ torizoncore-builder dto list --device-tree ./linux/arch/arm64/boot/dts/freescale/imx8qxp-colibri-aster.dts
(2)
Repository Structure
The device-trees repository contains(2):
dts-arm32 - source files for 32-bit architecture modules
dts-arm64 - source files for 64-bit architecture modules
overlays - device tree overlay source files
Important Notes
- The automated
dt checkout approach is recommended as it ensures branch compatibility with your specific image version(1)
- Make sure to copy the full path of the device tree file when using the
dto list command, as device trees for different modules may be in different paths(3)
- You can use the
--depth 1 option when cloning to only clone the latest commit if you want to speed up the process(3)
Best regards,
Toradex AI Assistant.
Did you like my answer?

If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.