Device-tree-overlays to build Torizon 7.5.0

Technical Support
, , ,
1

I would like updateing my custom build of Torizon OS from 7.2.0 to 7.5.0 for Verdin iMX8M-Plus.

I see here that BSP 7.5.0 is based on
Kernel: Downstream Toradex v6.6.119 based on NXP BSP L6.6.52_2.2.2

As usual, to customize TorizonOS with TCB I need to clone both the device tree and linux repos (see here).

And so, the usual question is: which is the branch to be used for 7.5.0?

Is this toradex_6.6-2.2.x-imx ? Or toradex_6.6-2.1.x-imx like in the link I posted above?

As far as I remember I’ve already asked in the past, but I suggest to show this info clearly somewhere, together with the info of every TorizonOS release.

Thanks

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Based on the community discussions and information available, for Torizon OS 7.2.0 the branch to use is toradex_6.6-2.2.x-imx for downstream NXP based modules (1).

The documentation shows that for custom Torizon OS builds using TorizonCore Builder, you need to clone both repositories using the same branch (2). The community discussions confirm that toradex_6.6-2.1.x-imx was available in the linux-toradex.git repository but initially wasn’t available in the device-tree-overlays repository, and later became available (2).

For your upgrade from Torizon OS 7.2.0 to 7.5.0, you should use the toradex_6.6-2.2.x-imx branch for both repositories:

  • git://git.toradex.com/linux-toradex.git
  • git://git.toradex.com/device-tree-overlays.git

TorizonCore Builder Configuration

When using TorizonCore Builder, your tcbuild.yaml file should reference the device tree files from the cloned repositories (3). The structure would be similar to:

customization:
  device-tree:
    include-dirs:
    # Folder that contains common kernel header files like gpio.h
      - linux/include
    # Folder containing overlays included by verdin-imx8mp_panel-cap-touch-7inch-dsi_overlay.dts
      - device-trees/overlays
    # Top-level device tree source file that will be used.
    # This file's name includes the name of the target SoC and carrier board.
    # Note that we are including a a device tree source file (dts) and not a dtsi file.
    custom: linux/arch/arm64/boot/dts/freescale/imx8mp-verdin-wifi-dahlia.dts
    overlays:
      add:
      # Overlay to be applied
        - device-trees/overlays/verdin-imx8mp_panel-cap-touch-7inch-dsi_overlay.dts

(3)

I understand your suggestion about making branch information more visible in the release documentation. The community has raised similar concerns about making the device tree branch information more accessible alongside BSP release information (1).

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.

3

Hi @vix!

Thanks for the feedback!

I already talked with the responsible team, and they will fix the information ASAP. Also, a way to show this information clearly will be discussed.

Besides that, the answer given by the Toradex AI is correct. You should use the toradex_6.6-2.2.x-imx for both the Linux kernel and device trees repository.

Best regards.