No output from Colibri iMX8X to 10 inch capacitive touch screen with Torizon 5.3.0

Dear Toradex Community,

10 inch capacitive and Iris+Colibri iMX8X are reported as compatible here, then I connected them following this indications about connection here and enabled the device tree as documented here.

Unfortunately I cannot see any output on the display, I expect to see the Portainer UI, which is actually running. Do you have any suggestion or see any error in my procedure or connections? Is there any test one can do on hardware to check the screen is not damaged?

Thank you and best regards,

ldvp

Connection picture attached and overlay command below:

colibri-imx8x-06789167:~$ cat /etc/os-release
ID=torizon
NAME="TorizonCore"
VERSION="5.3.0-devel-202106+build.14 (dunfell)"
VERSION_ID=5.3.0-devel-202106-build.14
PRETTY_NAME="TorizonCore 5.3.0-devel-202106+build.14 (dunfell)"
BUILD_ID="14"
ANSI_COLOR="1;34"
VARIANT="Docker"
colibri-imx8x-06789167:~$ uname -a
Linux colibri-imx8x-06789167 5.4.115-5.3.0-devel+git.64dbf17bb33e #1-TorizonCore SMP PREEMPT Thu May 27 21:52:13 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
colibri-imx8x-06789167:/sysroot/boot/ostree/torizon-7921a7761bcfc96027d90da4345adb46ed70aaf7a14d3b26316f3417bf9db3be/dtb$ sudo sh -c "echo 'fdt_overlays=colibri-imx8x_parallel-rgb-lvds_overlay.dtbo colibri-imx8x_atmel-mxt-connector_overlay.dtbo display-dpi-lt170410_overlay.dtbo' > overlays.txt"
sync
reboot
[...]
Found U-Boot script /boot.scr
1182 bytes read in 11 ms (104.5 KiB/s)
## Executing script at 83200000
4136 bytes read in 20 ms (201.2 KiB/s)
127018 bytes read in 31 ms (3.9 MiB/s)
139 bytes read in 22 ms (5.9 KiB/s)
Applying Overlay: colibri-imx8x_parallel-rgb-lvds_overlay.dtbo
2180 bytes read in 33 ms (64.5 KiB/s)
Applying Overlay: colibri-imx8x_atmel-mxt-connector_overlay.dtbo
523 bytes read in 34 ms (14.6 KiB/s)
Applying Overlay: display-dpi-lt170410_overlay.dtbo
820 bytes read in 32 ms (24.4 KiB/s)
12188679 bytes read in 293 ms (39.7 MiB/s)
Uncompressed size: 30671360 = 0x1D40200
9170402 bytes read in 227 ms (38.5 MiB/s)
## Flattened Device Tree blob at 83100000
   Booting using the fdt blob at 0x83100000
   Loading Ramdisk to fcdad000, end fd66bde2 ... OK
   Loading Device Tree to 00000000fcd6a000, end 00000000fcdacfff ... OK

Starting kernel ...

[    0.163355] No BMan portals available!
[    0.164510] No QMan portals available!
[    1.563879] imx8qxp-lpcg-clk 37620000.clock-controller: failed to get clock parent names
[    2.065160] imx6q-pcie 5f010000.pcie: pcie_ext clock source missing or invalid
[    2.170591] debugfs: Directory '59040000.sai' with parent 'imx8qxp-sgtl5000' already present!
Starting version 244.5+
[    8.112108] mcp251x spi0.0: MCP251x didn't enter in conf mode after reset
[    8.125669] mcp251x spi0.0: Probe failed, err=16
[    8.331912] atmel_mxt_ts 17-004a: __mxt_read_reg: i2c transfer failed (-110)
[    8.338986] atmel_mxt_ts 17-004a: Failed to read 67 messages (-110)
[   10.987737] Bluetooth: hci0: unexpected event for opcode 0x0000

TorizonCore 5.3.0-devel-202106+build.14 colibri-imx8x-06789167 ttyLP3
[...]
    colibri-imx8x-06789167:~$ docker container ls
    CONTAINER ID        IMAGE                        COMMAND                  CREATED             STATUS              PORTS                              NAMES
    f810f4c2f121        torizon/kiosk-mode-browser   "/usr/bin/start-brow…"   12 minutes ago      Up 12 minutes                                          torizon_kiosk_1
    96c556a08d7d        torizon/weston-vivante       "/usr/bin/entry.sh"      12 minutes ago      Up 12 minutes                                          torizon_weston_1
    6680d552f31f        portainer/portainer-ce       "/portainer --templa…"   12 minutes ago      Up About a minute   8000/tcp, 0.0.0.0:8840->9000/tcp   torizon_portainer_1

I have read only now the warning about the 12V:

Important! The LVDS connector is directly connected to the power input connector. For this reason, use only 12V (+/-10%) power supplies with the board. Otherwise, you can damage the LVDS display or observe a malfunction.

This was the problem. Luckily the touch screen was not damaged by the wrong voltage…

Glad you were able to resolve the issue. Also good to hear you didn’t experience any hardware damage on your end.

Best Regards,
Jeremias