LVDS connected to X2 of colibri imx8dx

I have connected LVDS display to X2, but I do not see the Weston application
how to configure LVDS connected to X2 of Colibri IMX8DX, please help, so I can bring up the display
(having torizon-core-docker-colibri-imx8x-Tezi_5.7.2+build.20.tar)

Thank you

You need to adjust the device tree to enable LVDS output. Please refer to this article for detailed instructions. Additionally, please be aware that the Colibri iMX8DX only supports single channel LVDS displays by default.

1 Like

In a project I used the X2 with lvds on my own hardware.
I used this dts file as a base.

You need to change the clock-frequency, hback-porch, vback-porch, vfront-porch, hsync-len and vsync-len according to your display datasheet.

If your backlight is also connected to the imx8, you need to activate it to.
&backlight {
pinctrl-0 = <&pinctrl_gpio_bkl_on>;
enable-gpios = <&lsio_gpio0 16 GPIO_ACTIVE_HIGH>;
default-brightness-level = <4>;
brightness-levels = <0 45 63 88 119 158 203 255>;
status = “okay”;


Thank you I will try above article

Thank you I will try above information

@alex.tx @rsquare
I deployed lvds-single-channel dtbo like
torizoncore-builder dto deploy --remote-host board_ip --remote-username torizon --remote-password torizon --force --reboot device-trees/dts-arm64/imx8qxp-colibri-lvds-single-channel.dts

and then I started a weston vivante container like below
docker run -e ACCEPT_FSL_EULA=1 --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 13:* rmw’ --device-cgroup-rule=‘c 199:* rmw’ --device-cgroup-rule=‘c 226:* rmw’ torizon/weston-vivante:$CT_TAG_WESTON_VIVANTE

and then the GTK app container
docker run -it -e DISPLAY=$DISPLAY -e ACCEPT_FSL_EULA=1 -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’ --net=host --privileged --user=torizon gtk_demo3:latest

the GTK app is correctly displayed on the display connected via VGA
but no app is displayed on LVDS display

do I miss any thing ?

boot log :

flash target is MMC:0
Net: eth0: ethernet@5b040000 [PRIME]
Fastboot: Normal
Saving Environment to MMC… Writing to MMC(0)… OK
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1…
Found U-Boot script /boot.scr
973 bytes read in 9 ms (105.5 KiB/s)

Executing script at 83200000

5436 bytes read in 20 ms (264.6 KiB/s)
122865 bytes read in 34 ms (3.4 MiB/s)
93 bytes read in 27 ms (2.9 KiB/s)
Applying Overlay: colibri-imx8x_vga-640x480_overlay.dtbo
2062 bytes read in 36 ms (55.7 KiB/s)
Applying Overlay: imx8qxp-colibri-lvds-single-channel.dtbo
126383 bytes read in 36 ms (3.3 MiB/s)
13355717 bytes read in 321 ms (39.7 MiB/s)
Uncompressed size: 35342848 = 0x21B4A00
11503951 bytes read in 277 ms (39.6 MiB/s)

Flattened Device Tree blob at 83100000

Booting using the fdt blob at 0x83100000
Loading Ramdisk to bcb73000, end bd66b94f … OK
Loading Device Tree to 00000000bcb31000, end 00000000bcb72fff … OK

Starting kernel …

[ 1.575008] rtc-ds1307 1-0068: hctosys: unable to read the hardware clock
[ 1.681206] imx6q-pcie 5f010000.pcie: ERROR PM_REQ_CORE_RST is still set.
[ 1.705911] debugfs: Directory ‘lvds1’ with parent ‘pm_genpd’ already present!
[ 1.713243] debugfs: Directory ‘mipi1-i2c1’ with parent ‘pm_genpd’ already present!
[ 1.721556] debugfs: Directory ‘mipi1-i2c0’ with parent ‘pm_genpd’ already present!
[ 1.729346] debugfs: Directory ‘mipi1-pwm0’ with parent ‘pm_genpd’ already present!
[ 1.737030] debugfs: Directory ‘mipi1’ with parent ‘pm_genpd’ already present!
[ 2.088605] imx6q-pcie 5f010000.pcie: PCIe PLL lock timeout
Starting version 250.5+
[ 4.558339] sd 0:0:0:0: [sda] Asking for cache data failed
[ 4.567085] sd 0:0:0:0: [sda] Assuming drive cache: write through

TorizonCore 6.2.0+build.2 colibri-imx8x-07202984 ttyLP3

Thank you, it works now after applying custom device tree, hence it is resolved