Build device treee ovlerlays for Torizon OS 7.6.1

Technical Support
, , ,
1

Hi.

I’m trying to build a device tree overlay for the verdin-imx8mm on a Mallow board, running under Torizon OS 7.6.1., to add a Reverdi 15.6" DSI touch display. I followed the documentation but I don’t have any success until now.
If I understand the documentation correct, the Torizon Linux branch is toradex_6.6-2.2.x-imx but this is the same as for Torizon OS 6.8.8. However, there is a tag for v7.1. which I have also tied. But independent which branch I use to build the overlay, I get an the following error message from bootloader.
Might be, I have overseen something or I’m doing wrong an other thing.

Applying Overlay: verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dtbo
4276 bytes read in 3 ms (1.4 MiB/s)
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_BADMAGIC

On Torizon OS 6.8.8, the overlay was working.

My tdx-info:

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           6.6.138-7.6.1 #1-Torizon SMP PREEMPT Fri May  8 12:46:27 UTC 2026
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/7bd6a132d63a000c53050
Distro name:              NAME="Torizon OS"
Distro version:           VERSION_ID=7.6.1-build.38
Distro variant:           VARIANT="Docker"
Hostname:                 verdin-imx8mm-xxx
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin iMX8M Mini WB on Verdin Development Board
Toradex version:          0068 V1.1A
Serial number:            xxx
Processor arch:           aarch64
------------------------------------------------------------

I have found a branch (toradex_ti-linux-6.6.y) with the right yocto version ( 6.6.138) but building the overlay currently fails.

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.

I can help you troubleshoot the device tree overlay build issue for your Verdin iMX8M Mini running Torizon OS 7.6.1. The FDT_ERR_NOTFOUND and FDT_ERR_BADMAGIC errors typically indicate a mismatch between the overlay and the base device tree.

Correct Branch Selection

For Torizon OS 7.6.1 on Verdin iMX8M Mini, you should use the following branches(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

The toradex_ti-linux-6.6.y branch is specifically for TI AM62 SoMs, not for iMX8M Mini(1).

Key Points to Check

  1. Base Device Tree Selection: Ensure you’re using the correct base device tree for your Mallow Carrier Board. For Verdin iMX8M Mini on Mallow, you should check which .dts file matches your configuration(1):
$ find linux -name "*imx8mm-verdin*.dts"

  1. Overlay Compatibility: The overlay must target nodes that exist in your base device tree. The FDT_ERR_NOTFOUND error suggests the overlay is trying to modify a node that doesn’t exist in the base tree(1).

  2. Include Directories: When building with TorizonCore Builder, ensure you specify the include directories(1):

customization:
  device-tree:
    include-dirs:
      - device-trees/include/
    custom: linux/arch/arm64/boot/dts/freescale/<your-base-device-tree>.dts
    overlays:
      add:
        - device-trees/overlays/verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dts

Recommended Troubleshooting Steps

  1. Verify your overlay source references nodes that exist in the Verdin iMX8M Mini device tree
  2. Check if the overlay worked on 6.8.8 with a different base device tree configuration
  3. Compare the device tree structure between 6.8.8 and 7.6.1 to identify any node path changes
  4. Ensure the overlay is being compiled with the same kernel headers as your running kernel (6.6.138)

Could you share the content of your verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dts file? This would help identify if there’s a specific node reference causing the issue.

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

Here is the overlay verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dts:

// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
/*
 * Copyright 2023 Toradex
 */

// Verdin with connected Capacitive Touch Display 10.1" DSI.

/dts-v1/;
/plugin/;

/ {
	compatible = "toradex,verdin-imx8mm";
};

#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/gpio/gpio.h>
#include "display-rvt156xxx-bg_overlay.dtsi"
#include "verdin-imx8mm_backlight-dsi_overlay.dtsi"

&gpu {
	status = "okay";
};

/* Verdin I2C_2_DSI */
&i2c2 {
	#address-cells = <1>;
	#size-cells = <0>;
	status = "okay";

	bridge@2c {
		compatible = "ti,sn65dsi83";
		reg = <0x2c>;
		/* IRQ not connected */
		/* Verdin GPIO_10_DSI (SODIMM 21) */
		enable-gpios = <&gpio3 3 GPIO_ACTIVE_HIGH>;
		pinctrl-names = "default";
		pinctrl-0 = <&pinctrl_gpio_10_dsi>;
		status = "okay";

		ports {
			#address-cells = <1>;
			#size-cells = <0>;

			port@0 {
				reg = <0>;

				dsi_lvds_bridge_in: endpoint {
					data-lanes = <1 2 3 4>;
					remote-endpoint = <&mipi_dsi_bridge1_out>;
				};
			};

			port@2 {
				reg = <2>;

				dsi_lvds_bridge_out: endpoint {
					remote-endpoint = <&panel_in_rvt101hvdwc00>;
				};
			};
		};
	};

	touch@41 {
		compatible = "ilitek,ili2132";
		reg = <0x41>;
		/* Verdin DSI_1_INT# (TOUCH_INT#, SODIMM 17) */
		interrupt-parent = <&gpio3>;
		interrupts = <15 IRQ_TYPE_EDGE_RISING>;
		pinctrl-names = "default";
		pinctrl-0 = <&pinctrl_gpio_9_dsi>, <&pinctrl_i2s_2_bclk_touch_reset>;
		/* Verdin I2S_2_BCLK (TOUCH_RESET#, SODIMM 42) */
		reset-gpios = <&gpio3 23 GPIO_ACTIVE_LOW>;
		status = "okay";
	};
};

&lcdif {
	status = "okay";
};

&mipi_dsi {
	#address-cells = <1>;
	#size-cells = <0>;
	status = "okay";

	port@1 {
		mipi_dsi_bridge1_out: endpoint {
			attach-bridge;
			remote-endpoint = <&dsi_lvds_bridge_in>;
		};
	};
};

&panel_rvt101hvdwc00b {
	backlight = <&backlight_verdin_dsi>;

	port {
		panel_in_rvt101hvdwc00: endpoint {
			remote-endpoint = <&dsi_lvds_bridge_out>;
		};
	};
};

And here is the display-rvt156xxx-bg_overlay.dtsi:

// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
/*
 * Copyright 2023 Toradex
 */

// RVT156XXX-B DSI display (15.6 inch) with a resolution of 1920x1080 pixel (by Bernd Gasse).

&panel_lvds {
	compatible = "panel-lvds";
	backlight = <&backlight>;
	data-mapping = "vesa-24";
	height-mm = <193>;
	width-mm = <344>;
	status = "okay";

	/*
	 * These timings are hand-optimized and more stable then teorethical
	 * In particular HBP+HS should be 88 (display datasheet)
	 * Likely an higher value is needed due to dsi to lvds pipeline.
	 */
	panel-timing {
		clock-frequency = <135000000>;
		hactive = <1920>;
		hsync-len = <8>;
		hfront-porch = <140>;
		hback-porch = <140>;

		vactive = <1080>;
		vsync-len = <2>;
		vfront-porch = <32>;
		vback-porch = <12>;

		de-active = <1>;
		hsync-active = <1>;
		vsync-active = <1>;
	};

	port {
		panel_in_lvds_riv: endpoint {
			remote-endpoint = <&lvds_out_panel_riv>;
		};
	};
};
4

I can see the issue with your overlay. The problem is that your overlay references nodes and labels that don’t exist in the base device tree for Verdin iMX8M Mini.

Root Cause Analysis

Your overlay has several critical issues:

  1. Incorrect panel label reference: Your display-rvt156xxx-bg_overlay.dtsi references &panel_lvds and your main overlay references &panel_rvt101hvdwc00b, but these labels don’t exist in the Verdin iMX8M Mini device tree(1).

  2. Missing backlight reference: The .dtsi file references &backlight, which is undefined.

  3. Inconsistent endpoint naming: Your overlay creates panel_in_rvt101hvdwc00 but the .dtsi creates panel_in_lvds_riv with a remote endpoint to &lvds_out_panel_riv which doesn’t exist.

Solution

You need to restructure your overlay to properly define the panel node rather than trying to modify non-existent labels. Here’s the corrected approach:

Corrected verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dts:

// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
/*
 * Copyright 2023 Toradex
 */

/dts-v1/;
/plugin/;

#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/gpio/gpio.h>

/ {
	compatible = "toradex,verdin-imx8mm";
};

&{/} {
	panel_lvds: panel-lvds {
		compatible = "panel-lvds";
		backlight = <&backlight_dsi>;
		data-mapping = "vesa-24";
		height-mm = <193>;
		width-mm = <344>;
		status = "okay";

		panel-timing {
			clock-frequency = <135000000>;
			hactive = <1920>;
			hsync-len = <8>;
			hfront-porch = <140>;
			hback-porch = <140>;

			vactive = <1080>;
			vsync-len = <2>;
			vfront-porch = <32>;
			vback-porch = <12>;

			de-active = <1>;
			hsync-active = <1>;
			vsync-active = <1>;
		};

		port {
			panel_in_lvds: endpoint {
				remote-endpoint = <&dsi_lvds_bridge_out>;
			};
		};
	};

	backlight_dsi: backlight-dsi {
		compatible = "pwm-backlight";
		pinctrl-names = "default";
		pinctrl-0 = <&pinctrl_gpio_8_dsi>;
		/* Verdin GPIO_8_DSI (SODIMM 16) */
		enable-gpios = <&gpio3 1 GPIO_ACTIVE_HIGH>;
		/* Verdin PWM_3_DSI */
		pwms = <&pwm1 0 6666667 0>;
		brightness-levels = <0 45 63 88 119 158 203 255>;
		default-brightness-level = <4>;
		status = "okay";
	};
};

&gpu {
	status = "okay";
};

/* Verdin I2C_2_DSI */
&i2c2 {
	#address-cells = <1>;
	#size-cells = <0>;
	status = "okay";

	bridge@2c {
		compatible = "ti,sn65dsi83";
		reg = <0x2c>;
		/* Verdin GPIO_10_DSI (SODIMM 21) */
		enable-gpios = <&gpio3 3 GPIO_ACTIVE_HIGH>;
		pinctrl-names = "default";
		pinctrl-0 = <&pinctrl_gpio_10_dsi>;
		status = "okay";

		ports {
			#address-cells = <1>;
			#size-cells = <0>;

			port@0 {
				reg = <0>;

				dsi_lvds_bridge_in: endpoint {
					data-lanes = <1 2 3 4>;
					remote-endpoint = <&mipi_dsi_bridge_out>;
				};
			};

			port@2 {
				reg = <2>;

				dsi_lvds_bridge_out: endpoint {
					remote-endpoint = <&panel_in_lvds>;
				};
			};
		};
	};

	touch@41 {
		compatible = "ilitek,ili2132";
		reg = <0x41>;
		/* Verdin DSI_1_INT# (TOUCH_INT#, SODIMM 17) */
		interrupt-parent = <&gpio3>;
		interrupts = <15 IRQ_TYPE_EDGE_RISING>;
		pinctrl-names = "default";
		pinctrl-0 = <&pinctrl_gpio_9_dsi>, <&pinctrl_i2s_2_bclk_touch_reset>;
		/* Verdin I2S_2_BCLK (TOUCH_RESET#, SODIMM 42) */
		reset-gpios = <&gpio3 23 GPIO_ACTIVE_LOW>;
		status = "okay";
	};
};

&lcdif {
	status = "okay";
};

&mipi_dsi {
	#address-cells = <1>;
	#size-cells = <0>;
	status = "okay";

	port@1 {
		mipi_dsi_bridge_out: endpoint {
			attach-bridge;
			remote-endpoint = <&dsi_lvds_bridge_in>;
		};
	};
};

&pwm1 {
	status = "okay";
};

Key Changes Made

  1. Defined panel in root node: Used &{/} to add the panel definition to the root of the device tree(1)
  2. Defined backlight: Created the backlight node that was missing
  3. Fixed endpoint references: Made all endpoint connections consistent and pointing to actually defined labels
  4. Removed separate .dtsi file: Integrated everything into one overlay to avoid reference issues
  5. Added pwm1 enablement: Required for the backlight functionality

Building and Deploying

With the corrected overlay, build using TorizonCore Builder with the toradex_6.6-2.2.x-imx branch(1)(2):

$ torizoncore-builder dto deploy --remote-host <IP> --remote-username torizon --remote-password <password> --force --reboot verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dts

The FDT_ERR_NOTFOUND error should be resolved since all referenced nodes now exist or are properly created within the overlay.

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.

5

Trying to build your suggested overlay file with torizoncore-builder fails. Here is the torizoncore-builder output:

2026-06-22 10:35:17,383 - torizon.tcbuilder.cli.build - INFO - Building image as per configuration file 'tcbuild.yaml'...
2026-06-22 10:35:17,383 - torizon.tcbuilder.cli.build - DEBUG - Substitutions (enabled): {}
2026-06-22 10:35:17,410 - torizon.tcbuilder.cli.build - INFO - 
=>> Handling input section
2026-06-22 10:35:18,077 - torizon.tcbuilder.backend.images - INFO - Unpacking Toradex Easy Installer image.
2026-06-22 10:35:18,077 - torizon.tcbuilder.backend.images - DEBUG - Running tar command: tar -xf /workdir/torizon-docker-verdin-imx8mm-Tezi_7.6.1+build.38.tar -C /storage/tmpfdg45xi8
2026-06-22 10:35:18,225 - torizon.tcbuilder.backend.images - INFO - Unpacking TorizonCore Toradex Easy Installer image.
2026-06-22 10:35:18,225 - torizon.tcbuilder.backend.images - DEBUG - Running tar command: tar --xattrs '--xattrs-include=*' -xhf /storage/tezi/torizon-docker-verdin-imx8mm.ota.tar.zst -C /storage/sysroot --use-compress-program 'zstd -dc'
2026-06-22 10:35:20,228 - torizon.tcbuilder.backend.images - INFO - Importing OSTree revision aca3a0e280280db43070c06fa7b9c520f8510d475480e09447972d917a367296 from local repository...
2026-06-22 10:35:20,229 - torizon.tcbuilder.backend.ostree - DEBUG - Pulling from local repository /storage/sysroot/ostree/repo commit checksum aca3a0e280280db43070c06fa7b9c520f8510d475480e09447972d917a367296
1305 metadata, 9898 content objects imported; 671.9 MB content written                                                                                
2026-06-22 10:35:22,631 - torizon.tcbuilder.backend.ostree - DEBUG - Pulling from local repository /storage/sysroot/ostree/repo commit checksum aca3a0e280280db43070c06fa7b9c520f8510d475480e09447972d917a367296
0 metadata, 0 content objects imported; 0 bytes content written                                                                                       
2026-06-22 10:35:22,664 - torizon.tcbuilder.backend.images - INFO - Unpacked OSTree from Toradex Easy Installer image:
2026-06-22 10:35:22,664 - torizon.tcbuilder.backend.images - INFO -   Commit checksum: aca3a0e280280db43070c06fa7b9c520f8510d475480e09447972d917a367296
2026-06-22 10:35:22,664 - torizon.tcbuilder.backend.images - INFO -   TorizonCore Version: 7.6.1+build.38
2026-06-22 10:35:22,664 - torizon.tcbuilder.cli.build - INFO - 
=>> Handling customization section
2026-06-22 10:35:22,664 - torizon.tcbuilder.cli.build - INFO - 
=> Handling device-tree subsection
2026-06-22 10:35:22,664 - torizon.tcbuilder.cli.build - INFO - 
=> Selecting custom device-tree 'linux/arch/arm64/boot/dts/freescale/imx8mm-verdin-nonwifi-mallow.dts'
2026-06-22 10:35:22,666 - torizon.tcbuilder.backend.kernel - DEBUG - Kernel found at '/storage/sysroot/ostree/deploy/torizon/deploy/aca3a0e280280db43070c06fa7b9c520f8510d475480e09447972d917a367296.0/usr/lib/modules/6.6.138-7.6.1/vmlinuz'
2026-06-22 10:35:22,666 - torizon.tcbuilder.cli.dt - DEBUG - dt_apply: kernel_is_fit=False
2026-06-22 10:35:22,666 - torizon.tcbuilder.cli.dt - DEBUG - dt_apply: include directories: linux/include,device-trees/overlays
2026-06-22 10:35:22,674 - torizon.tcbuilder.backend.dt - INFO - Compiling Device Tree with DTC 1.6.0...
2026-06-22 10:35:22,693 - torizon.tcbuilder.backend.dt - DEBUG - OUTPUT FROM DEVICE TREE COMPILER
2026-06-22 10:35:22,693 - torizon.tcbuilder.backend.dt - DEBUG - linux/arch/arm64/boot/dts/freescale/imx8mm.dtsi:1245.12-1250.7: Warning (unit_address_vs_reg): /soc@0/bus@32c00000/mipi_dsi@32e10000/port@0: node has a unit name, but no reg property
linux/arch/arm64/boot/dts/freescale/imx8mm.dtsi:1227.32-1251.6: Warning (avoid_unnecessary_addr_size): /soc@0/bus@32c00000/mipi_dsi@32e10000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
linux/arch/arm64/boot/dts/freescale/imx8mm.dtsi:1391.24-1424.5: Warning (unique_unit_address): /soc@0/pcie@33800000: duplicate unit-address (also used in node /soc@0/pcie-ep@33800000)
  also defined at linux/arch/arm64/boot/dts/freescale/imx8mm-verdin.dtsi:647.8-657.3
  also defined at linux/arch/arm64/boot/dts/freescale/imx8mm-verdin-mallow.dtsi:102.8-104.3
linux/arch/arm64/boot/dts/freescale/imx8mm.dtsi:675.34-680.6: Warning (unique_unit_address): /soc@0/bus@30000000/caam-snvs@30370000: duplicate unit-address (also used in node /soc@0/bus@30000000/snvs@30370000)

2026-06-22 10:35:22,693 - torizon.tcbuilder.backend.dt - DEBUG - END OF DEVICE TREE COMPILER OUTPUT
2026-06-22 10:35:22,693 - torizon.tcbuilder.backend.dt - INFO - File 'imx8mm-verdin-nonwifi-mallow.dts' compiles successfully.
2026-06-22 10:35:22,719 - torizon.tcbuilder.backend.dt - DEBUG - Found uEnv.txt in deployment: '/storage/sysroot/ostree/deploy/torizon/deploy/aca3a0e280280db43070c06fa7b9c520f8510d475480e09447972d917a367296.0/usr/lib/ostree-boot/uEnv.txt'
2026-06-22 10:35:22,719 - torizon.tcbuilder.cli.dt - INFO - warning: removing currently applied device tree overlays.
2026-06-22 10:35:22,719 - torizon.tcbuilder.backend.dto - DEBUG - Setting overlay list in 'overlays.txt' to []
2026-06-22 10:35:22,732 - torizon.tcbuilder.cli.dt - INFO - Device tree imx8mm-verdin-nonwifi-mallow.dtb successfully applied.
2026-06-22 10:35:22,733 - torizon.tcbuilder.backend.dt - DEBUG - Found uEnv.txt in changes dir: '/storage/dt/usr/lib/ostree-boot/uEnv.txt'
2026-06-22 10:35:22,736 - torizon.tcbuilder.cli.build - INFO - 
=> Adding device-tree overlay 'device-trees/overlays/verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dts'
2026-06-22 10:35:22,737 - torizon.tcbuilder.backend.kernel - DEBUG - Kernel found at '/storage/sysroot/ostree/deploy/torizon/deploy/aca3a0e280280db43070c06fa7b9c520f8510d475480e09447972d917a367296.0/usr/lib/modules/6.6.138-7.6.1/vmlinuz'
2026-06-22 10:35:22,737 - torizon.tcbuilder.cli.dto - DEBUG - dto_apply: kernel_is_fit=False
2026-06-22 10:35:22,749 - torizon.tcbuilder.backend.dto - DEBUG - Found overlays.txt in changes dir: '/storage/dt/usr/lib/modules/6.6.138-7.6.1/dtb/overlays.txt'
2026-06-22 10:35:22,757 - torizon.tcbuilder.backend.dt - INFO - Compiling Device Tree with DTC 1.6.0...
2026-06-22 10:35:22,764 - torizon.tcbuilder.backend.dt - DEBUG - OUTPUT FROM DEVICE TREE COMPILER
2026-06-22 10:35:22,764 - torizon.tcbuilder.backend.dt - DEBUG - device-trees/overlays/verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dts:128.9-133.4: Warning (unit_address_vs_reg): /fragment@4/__overlay__/port@1: node has a unit name, but no reg property
device-trees/overlays/verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dts:123.11-134.3: Warning (avoid_unnecessary_addr_size): /fragment@4/__overlay__: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property

2026-06-22 10:35:22,764 - torizon.tcbuilder.backend.dt - DEBUG - END OF DEVICE TREE COMPILER OUTPUT
2026-06-22 10:35:22,764 - torizon.tcbuilder.backend.dt - INFO - File 'verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dts' compiles successfully.
2026-06-22 10:35:22,764 - torizon.tcbuilder.cli.dto - DEBUG - No base DTB specified; picking the currently applied one.
2026-06-22 10:35:22,765 - torizon.tcbuilder.backend.dt - DEBUG - Found uEnv.txt in changes dir: '/storage/dt/usr/lib/ostree-boot/uEnv.txt'
2026-06-22 10:35:22,785 - torizon.tcbuilder.backend.dto - ERROR - 
Failed to apply '/tmp/tmpgyyfpzk3.dtbo': FDT_ERR_NOTFOUND

2026-06-22 10:35:22,785 - torizon.tcbuilder.backend.dto - ERROR - error: cannot apply device tree overlays ['tmpgyyfpzk3.dtbo'] against device tree imx8mm-verdin-nonwifi-mallow.dtb.
2026-06-22 10:35:22,785 - torizon.tcbuilder.cli.dto - ERROR - error: overlay 'device-trees/overlays/verdin-imx8mm_panel-cap-touch-15inch-dsi-bg_overlay.dts' is not applicable.
6

Hi @Bernd1170!

For Torizon 7.6, you must use the toradex_6.6-2.2.x-imx kernel branch, as mentioned by the Toradex AI. You can also verify this in our Release Matrix article.

That said, the FDT_ERR_NOTFOUND error is usually caused by references to nodes that do not exist or are not present in any of the included device tree files.

I recommend rebuilding the overlay by following our Build Device Tree Overlays from Source Code and Device Tree Overlays on Torizon article.

Since this issue is directly related to your customization, we do not have the necessary hardware setup to reproduce or debug it on our side. If you need further assistance, I recommend checking our Partner Network, where you can find partners with the necessary expertise to test a custom setup similar to yours and help you.

Best regards.

7

Hi Lucas.
Thanks for your answer.
After deeper investigation, I have found some modules that was not defined or was renamed in verdin device tree. I wondered, that when I compile the device trees via Makefile (as suggested e.g. by reverdi), there was no issue. So, my thoughts was, that should be ok. However, now It works, but there is still an error message regarding to the mipi_dsi in the console.

[    1.741166] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi
[    1.749685] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -517
...
[   10.845178] tpm tpm0: A TPM error (256) occurred attempting the self test

I’m still facing some issues when I try to run a Qt app, but I will write a new topic.

BR
Bernd

1 Like
8

Hi @Bernd1170!

Device tree development can be a little tricky, but I’m glad you were able to resolve this issue.

Perfect, we always recommend opening a new topic for each new issue.

Best regards.