Add custom dts with torizoncore builder

Technical Support
, , , ,
4

Thank you for providing the detailed information. Based on your tdx-info output, you’re running Torizon OS 7.5.0-build.30 on a Verdin iMX8M Plus with a Mallow Board.

Understanding the Issue

The U-Boot variables you’re seeing (fdt_board=dev and fdtfile=imx8mp-verdin-wifi-dev.dtb) are still pointing to the development board configuration instead of your custom Mallow board device tree. This happens because U-Boot’s environment variables are set during the bootloader phase and may not automatically update when you specify a custom device tree in TorizonCore Builder(1).

Device Tree Customization Process

When using TorizonCore Builder to customize device trees for Torizon OS, the process involves four main steps(2):

  1. Choose the base Device Tree Source(2)
  2. Customize it according to your particular hardware(2)
  3. Compile the Device Tree Source(2)
  4. Deploy the Device Tree to your custom OS image(2)

TorizonCore Builder Configuration

Your tcbuilder.yaml configuration appears correct for specifying a custom device tree(3). The custom: field under device-tree: should properly set your custom DTS file(3).

However, for Torizon OS 7, device tree customization should work as TorizonCore Builder takes a source file and compiles it, which shouldn’t be specific to OS version, assuming you cloned the correct kernel sources for 7.X(4).

Recommended Solutions

1. Verify Device Tree Deployment

Check if your custom device tree was properly deployed by examining the boot partition:

ls /boot/

2. Build Process Verification

When using the build command with TorizonCore Builder, it should compile and deploy the device tree in a single step along with all other customizations described in the tcbuild.yaml file(3).

3. Manual Deployment for Testing

For evaluation purposes, you can also test device tree overlays using TorizonCore Builder commands(5):

torizoncore-builder dto deploy --remote-host <ip-addr> --remote-username torizon --remote-password torizon --force --reboot <overlay-file>

Next Steps

  1. Verify that your custom device tree file path is correct in the tcbuilder.yaml
  2. Ensure you’re using the appropriate branch for Torizon OS 7.X kernel sources
  3. Check the generated image to confirm the custom device tree was properly included
  4. Consider testing with device tree overlays first to isolate the issue

The U-Boot variables may need to be updated separately, or the custom device tree deployment process may need verification to ensure it’s properly overriding the default 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.