Modify Tezi for Custom Board with Verdin-AM62-Solo

ImHei · January 21, 2026, 1:52pm

Hello,

I am working on a custom board with verdin-am62 with a lvds display interface. My custom yocto image based on minimal reference image is working fine. We are using TEZI (7.3.0) to update our image.

Is it possible to modify Tezi (device tree) that LVDS-Display is working while updating to see update progress? How?

Also Tezi is activating GPIOs (SODIMM 58,60,62,64) which should not be activated on our hardware. How can I disable that in Tezi?

Another question: Is it also possible to activate LVDS display in uboot for minimal reference image (u-boot-toradex-ti in yocto bsp 7.3.0)? I would like to activate bootscreen in uboot.

Thanks for your help!!

Regards

Immanuel

ToradexAI · January 21, 2026, 1:53pm

Hi, I’m the Toradex AI Assistant.

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

Hello Immanuel,

I can help you with device tree customization for your Verdin AM62 LVDS display setup. Let me address your questions:

LVDS Display Configuration

The Verdin AM62 supports native LVDS video output through the Open LVDS Display Interface (OLDI) on the SoC (1). According to the datasheet, the LVDS interface provides 8 data lanes split into 2 channels, with single channel supporting resolutions up to 1920x1080p at 60fps (1).

For your LVDS display configuration, you can reference the device tree structure shown in the documentation. The basic approach involves (2):

Define the LVDS panel node with proper timing parameters
Configure the display subsystem (DSS)
Set up the OLDI output connections

Device Tree Customization Process

To customize device trees for your hardware, you’ll need to (3):

Choose the base device tree that matches your hardware platform
Create your custom device tree by copying and modifying the base
Compile the device tree using the Device Tree Compiler

The compilation process involves using the make command (3):

$ make DTC_FLAGS="-@" freescale/<custom-device-tree>.dtb

(3)

GPIO Configuration

To disable unwanted GPIO activation, you can modify the device tree to set the status property to "disabled" for the specific GPIO nodes (2). This approach prevents pins from being configured during boot.

Platform Information Needed

To provide more specific guidance for your TEZI and U-Boot customization questions, could you provide your complete platform details using the tdx-info command? You can find information about this command at: Getting Device Information with Tdx-Info | Toradex Developer Center

This will help me give you precise instructions for:

TEZI device tree modifications
U-Boot LVDS configuration
GPIO control in the bootloader

The customization approach will depend on your exact OS version and hardware configuration.

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.

ImHei · January 26, 2026, 6:50am

Hello ToradexAI,

here the output of tdx-info Command:

root@verdin-am62-15479297:~# tdx-info

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           6.6.94-7.3.0-devel #1 SMP PREEMPT Thu Jul  3 08:47:26 UTC 2025
Kernel command line:      root=PARTUUID=1770490d-02 ro rootwait console=tty1 console=ttyS2,115200 fsck.mode=skip fsck.repair=no
Distro name:              NAME="TDX Wayland with XWayland"
Distro version:           VERSION_ID=7.3.0-devel-20260115091437-build.0
Distro variant:           -
Hostname:                 verdin-am62-15479297
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin AM62 on Dahlia Board
Toradex version:          0071 V1.2A
Serial number:            15479297
Processor arch:           aarch64
------------------------------------------------------------

I know how to modify device-tree overlays for LVDS or GPIOs. It is working on my custom image.

But how to use that Device Tree Overlay in TEZI-Image?

Immanuel

ToradexAI · January 26, 2026, 6:51am

Hello Immanuel,

Thank you for providing the platform details. I can see you’re running BSP 7.3.0 on a Verdin AM62 with Dahlia Board. Now I can provide specific guidance for your TEZI customization needs.

Modifying TEZI for LVDS Display

To modify the Toradex Easy Installer (TEZI) to support your LVDS display, you’ll need to customize the TEZI image itself. The process involves modifying the device tree used by TEZI (1).

Available LVDS Overlays for Verdin AM62

For your Verdin AM62, there are several pre-built LVDS overlays available (2):

verdin-am62_panel-cap-touch-10inch-lvds_overlay.dtbo - for native LVDS with Capacitive Touch Display 10.1" LVDS (with Mallow Carrier Board)
verdin-am62_dsi-to-lvds_panel-cap-touch-10inch-lvds_overlay.dtbo - for DSI to LVDS with Capacitive Touch Display 10.1" LVDS using DSI to LVDS Adapter

TEZI Image Modification Process

The documentation indicates that you can modify TEZI images to include custom device tree configurations (1). The process involves:

Extract the TEZI image components
Modify the device tree or add overlays
Repackage the TEZI image

Deploy to Toradex Easy Installer Image

For deploying custom device trees to a TEZI-compatible image, you can follow this process (3):

Start from an existing TEZI image - Download your current TEZI image
Extract the components:

$ mkdir bootfs rootfs
$ tar xvf <Machine>_<image>-Tezi_version+build.<build-number>.tar
$ tar xvf <Machine>_<image>-Tezi_version+build.<build-number>/<image>-<machine>.rootfs.bootfs.tar.xz -C bootfs
$ tar xvf <Machine>_<image>-Tezi_version+build.<build-number>/<image>-<machine>.rootfs.tar.xz -C rootfs

(3)

Copy your custom device trees into the bootfs:

$ cp <linux-directory>/arch/<architecture>/boot/dts/<soc-vendor>/*.dtb bootfs/

(3)

Repackage the image:

$ tar -C bootfs -cJvf <Machine>_<image>-Tezi_version+build.<build-number>/<image>-<machine>.rootfs.bootfs.tar.xz .
$ tar -C rootfs -cJvf <Machine>_<image>-Tezi_version+build.<build-number>/<image>-<machine>.rootfs.tar.xz .

(3)

GPIO Control in TEZI

To disable the unwanted GPIO activation (SODIMM 58, 60, 62, 64) in TEZI, you’ll need to modify the device tree used by the TEZI bootloader. This involves creating a custom overlay that sets these pins to disabled state or configures them appropriately for your hardware.

U-Boot LVDS Configuration

For U-Boot bootscreen support with LVDS on your Verdin AM62, you would need to modify the U-Boot device tree configuration. This is typically done by customizing the U-Boot build in your Yocto environment.

The specific implementation details would depend on your exact display specifications and timing requirements, similar to how you’ve already configured your custom image.

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.