Add dts overlay custom with torizon core builder

Technical Support
, ,
4

When a new TorizonCore version is released, you need to update both the base image and the corresponding linux-toradex repository branch to maintain compatibility(1).

Update Process

1. Download the New TorizonCore Image

First, download the new TorizonCore image and unpack it(1):

$ torizoncore-builder images unpack torizon-core-docker-verdin-imx8mp-Tezi_NEW_VERSION.tar

(1)

Alternatively, you can use the automatic download command(1):

$ torizoncore-builder images download --remote-host 192.168.1.117 --remote-username torizon --remote-password torizon

(1)

2. Update the linux-toradex Repository

The key is understanding that different TorizonCore versions correspond to different kernel branches(2). For example:

  • TorizonCore 6.x uses kernel 5.15 with branch toradex_5.15-2.2.x-imx(2)
  • TorizonCore 7.x uses kernel 6.6 with branch toradex_6.6-2.2.x-imx(2)

To update your existing linux-toradex repository(1):

$ cd linux-toradex
$ git fetch origin
$ git checkout toradex_6.6-2.2.x-imx  # Use the appropriate branch for your TorizonCore version
$ git pull origin toradex_6.6-2.2.x-imx

(1)

3. Update Device Tree Overlays Repository

Similarly, update the device-tree-overlays repository(1):

$ cd device-trees
$ git fetch origin
$ git checkout toradex_6.6-2.2.x-imx  # Match the same branch as linux-toradex
$ git pull origin toradex_6.6-2.2.x-imx

(1)

Branch Selection Guidelines

For i.MX 8/8X/8M Mini/8M Plus modules, clone or update to the appropriate branch(1):

$ 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

(1)

Version Compatibility Check

The community discussions indicate that branch availability may vary(3). As noted in the community forum, toradex_6.6-2.2.x-imx is the current branch for TorizonCore 7(3).

Important Notes

  • Always ensure both repositories use the same branch version to maintain compatibility(1)
  • The TorizonCore version numbers (6.x, 7.x) don’t directly correspond to kernel version numbers (5.15, 6.6)(2)
  • You can use --depth 1 option when cloning to reduce download time(1)

After updating the repositories, rebuild your custom image using the same torizoncore-builder build command with your existing tcbuild.yaml configuration.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.