Verdin iMX8M Plus + Capacitive Touch Display 10.1" DSI

Shadiez · June 3, 2025, 12:57am

torizon@verdin-imx8mp-15337091:~$ dmesg | grep -i dsi
grep -i panel
[ 0.046441] /soc@0/bus@30800000/i2c@30a30000/bridge@2c: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[ 0.046757] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/lcd-controller@32e80000
[ 0.046796] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a30000/bridge@2c
[ 0.046877] /soc@0/bus@32c00000/lcd-controller@32e80000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[ 0.055341] /soc@0/bus@30800000/i2c@30a30000/bridge@2c: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[ 0.058288] /soc@0/bus@30800000/i2c@30a30000/bridge@2c: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[ 0.061580] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/lcd-controller@32e80000
[ 0.061625] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a30000/bridge@2c
[ 0.061739] /soc@0/bus@32c00000/lcd-controller@32e80000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[ 0.062000] /soc@0/bus@30800000/i2c@30a30000/bridge@2c: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[ 0.062091] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/lcd-controller@32e80000
[ 0.062133] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a30000/bridge@2c
[ 0.062358] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/lcd-controller@32e80000
[ 0.062464] /soc@0/bus@32c00000/lcd-controller@32e80000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[ 1.126012] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a30000/bridge@2c
[ 1.126242] /soc@0/bus@30800000/i2c@30a30000/bridge@2c: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[ 1.675055] Kernel module loaded from ramdisk: sec_dsim - result: 0
[ 1.686982] imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200
[ 1.687044] [drm:drm_bridge_attach] ERROR failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-34: -517
[ 1.698752] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[ 1.707048] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[ 1.716208] Kernel module loaded from ramdisk: sec_mipi_dsim_imx - result: 0
[ 1.731061] sn65dsi83 1-002c: supply vcc not found, using dummy regulator
[ 1.732484] Kernel module loaded from ramdisk: ti_sn65dsi83 - result: 0
[ 1.735665] imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200
[ 1.736034] imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops [sec_mipi_dsim_imx])
[ 1.817897] sn65dsi83 1-002c: failed to lock PLL, ret=-6
[ 35.729673] sn65dsi83 1-002c: failed to lock PLL, ret=-6
torizon@verdin-imx8mp-15337091:~$ dmesg | grep -i touch
torizon@verdin-imx8mp-15337091:~$ dmesg | grep -i panel
[ 0.046479] /soc@0/bus@30800000/i2c@30a30000/bridge@2c: Fixed dependency cycle(s) with /panel-rvt101hvdwc00b
[ 0.055371] /soc@0/bus@30800000/i2c@30a30000/bridge@2c: Fixed dependency cycle(s) with /panel-rvt101hvdwc00b
[ 0.058324] /soc@0/bus@30800000/i2c@30a30000/bridge@2c: Fixed dependency cycle(s) with /panel-rvt101hvdwc00b
[ 1.126125] /panel-rvt101hvdwc00b: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a30000/bridge@2c
[ 1.126305] /soc@0/bus@30800000/i2c@30a30000/bridge@2c: Fixed dependency cycle(s) with /panel-rvt101hvdwc00b
torizon@verdin-imx8mp-15337091:~$

Here is some output I’m getting. Looks like some failed pll thing?

allan.tx · June 3, 2025, 3:04pm

Hi @Shadiez

I created this new image with everything setup.

Torizon OS 7.2.0
DSI 10.1in display overlay
Weston container app

You should be able to see the weston screen right after installing it.

https://docs1.toradex.com/116960-torizon-core-docker-verdin-imx8mp-tezi_7.2.0build.13.custom-dsi-weston.zip

You can find instructions on how to flash a new image here:

Shadiez · June 3, 2025, 8:57pm

Is it possible to enter recovery without the debug UART? I don’t have it.

I can plug in a usb cable but dont have a uart debugger tool

allan.tx · June 3, 2025, 10:18pm

@Shadiez

You don’t need to access the debug UART.

Download the image, unzip it and put in a USB media.

Download the easy installer
Download Toradex Easy Installer | Toradex Developer Center
Connect an USB-C cable on mallow and your PC
Put device on recovery mode
NXP i.MX and TI AM62x Recovery Mode | Toradex Developer Center
Run the Easy installer script

Shadiez · June 4, 2025, 1:11am

I put my device into recovery mode by shorting the bottom connectors as shown in step 1.

I start the recovery-windows batch file.

It says waiting for the usb device, then when my device powers I get this:

Downloading Toradex Easy Installer…
uuu (Universal Update Utility) for nxp imx chips – libuuu_1.5.165-0-g7347a80

Success 0 Failure 1

1:15 1/ 0 [Failure open usb device ]

ECHO is off.
Downloading Toradex Easy Installer failed…
Press any key to continue . . .

I tried extracting so that torizon-core-docker-verdin-imx8mp-Tezi_7.2.0+build.13.CUSTOM-DSI-WESTON is the top file on the usb, and also extracted all the contents into the usb so they are the top files. both say fail to open.

Also I noticed a capacitor seems to not be attached on my board, is this important to functionality?

allan.tx · June 4, 2025, 1:39am

Hi @Shadiez

Check the “Troubleshoot on Windows” section, first dropdown.

allan.tx · June 4, 2025, 1:55am

@Shadiez

The resistor right? Someone from your side soldered it there.
This is a place for a button switch that by default is not assembled.

It can be used to get the device into recovery mode,
but the way it is in your board, it is not connected to anything.

Shadiez · June 4, 2025, 2:55am

Still not working.

I was able to get the OS updated to 7.2.0.

I went into visual code, opened up the device, and clicked apply built-in device tree overlay. I picked the verdin imx8mp panel cap touch 10inch dsi overlay, it shows that it is applied.

I then pasted in the tutorial weston container app:

torizon@verdin-imx8mp-15337091:~$ find /sys/devices -name “edid”
/sys/devices/platform/display-subsystem/drm/card0/card0-LVDS-1/edid
torizon@verdin-imx8mp-15337091:~$ docker container run -d --name=weston --net=host \

--cap-add CAP_SYS_TTY_CONFIG \
-v /dev:/dev -v /tmp:/tmp -v /run/udev/:/run/udev/ \
--device-cgroup-rule="c 4:* rmw" --device-cgroup-rule="c 253:* rmw" \
--device-cgroup-rule="c 13:* rmw" --device-cgroup-rule="c 226:* rmw" \
--device-cgroup-rule="c 10:223 rmw" --device-cgroup-rule="c 199:0 rmw" \
torizon/weston-imx8:4 \
--developer

f199939bc604e60c5e7c2011e33bdc6e093419a8d08cb1bf8b9ef8b070f369d9
torizon@verdin-imx8mp-15337091:~$ docker run -e ACCEPT_FSL_EULA=1 -d --rm --name=wayland-app \

-v /dev/dri:/dev/dri -v /dev/galcore:/dev/galcore -v /tmp:/tmp \
--device-cgroup-rule='c 199:* rmw' --device-cgroup-rule='c 226:* rmw' \
torizon/weston-imx8:4 weston-terminal

2adcc97b0ea298a0eff34ddc57ec0fcae63e168c6829d3402133bc1556c1a978
torizon@verdin-imx8mp-15337091:~$

The screen is still backlit but nothing is showing. I also checked the cable and that is correct.

Shadiez · June 21, 2025, 9:25am

Got a new LCD and it worked! Just followed your steps of double checking the correct overlay is in overlays.txt, sync, reboot.

So apparently the first LCD got “fried” at some point.

There was an in house demo a while ago and the power supply wires apparently touched the board and might have also fried the LCD. It wasn’t known at the time but that seems to be the issue and its now good. Thank you for the help though it was nice to come back and have the steps all good to go.