7" resistive display resolution mismatch on Colibri IMX8X

Hi,
We are having a Colibri IMX8X SOC with a Colibri evaluation board (2GB BT/WIFI) and a Toradex 7" resistive touch screen display.
The display resolution seems wrong and the touch is not properly calibrated(touch inputs get registered on wrong areas). Image attached.
Please let us know how this can be fixed.
regards,
Vineeth

Hey @vsr138,

Thanks for writing to Toradex Support!
May I ask what type of image you are running on the module? It would be helpful if you could send me the output of tdx-info (please follow this document for more details)

Hi Rudhi,

We are running a Torizon core image with evaluation containers from the Easy installer. The output from tdx-info is below,

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           5.15.77-6.2.0+git.aa0ff7e3554e #1-TorizonCore SMP PREE                                                                                                                                                             MPT Wed Mar 29 15:33:40 UTC 2023
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo v                                                                                                                                                             t.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ost                                                                                                                                                             ree=/ostree/boot.1/torizon/decdcdd4a4ca02824cd2e34fae717ba7d1b76df4b86a8881b3f5f                                                                                                                                                             f83fa8d25fc/0
Distro name:              NAME="TorizonCore"
Distro version:           VERSION_ID=6.2.0-build.2
Hostname:                 colibri-imx8x-07251264
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Colibri iMX8QXP on Colibri Evaluation Board V3
Toradex version:          0038 V1.0D
Serial number:            07251264
Processor arch:           aarch64

Hi @vsr138,

Have you tried calibrating the touch screen as it is explained here: Touch Screen Calibration (Torizon) | Toradex Developer Center

Hello,

Running the weston-touch-calibrator gave me the following result,

NXP EULA has already been accepted.

[05:47:17.372] weston 9.0.0

https://wayland.freedesktop.org

Bug reports to: https://gitlab.freedesktop.org/wayland/weston/isues/

Build: 9.0.0

[05:47:17.373] Command line: /usr/bin/weston

[05:47:17.373] OS: Linux, 5.15.77-6.2.0+git.aa0ff7e3554e, #1-TorizonCore SMP PREMPT Wed Mar 29 15:33:40 UTC 2023, aarch64

[05:47:17.373] warning: XDG_RUNTIME_DIR “/tmp/weston-xdg” is not configured

correctly. Unix access mode must be 0700 (current mode is 755),

and must be owned by the user (current owner is UID 0).

Refer to your distribution on how to get it, or

http://www.freedesktop.org/wiki/Specifications/basedir-spec

on how to implement it.

.

.

.

.

[05:47:17.532] libinput: configuring device “Logitech USB Receiver”.

[05:47:17.532] libinput: configuring device “Logitech USB Receiver Mouse”.

[05:47:17.532] libinput: configuring device “Logitech USB Receiver Consumer Conrol”.

[05:47:17.532] libinput: configuring device “Logitech USB Receiver System Contrl”.

[05:47:17.532] libinput: configuring device “gpio-keys”.

[05:47:17.532] libinput: configuring device “sc-powerkey”.

[05:47:17.533] DRM: head ‘DPI-1’ found, connector 35 is connected, EDID make ‘uknown’, model ‘unknown’, serial ‘unknown’

[05:47:17.534] Registered plugin API ‘weston_drm_output_api_v1’ of size 24

[05:47:17.534] Registered plugin API ‘weston_drm_virtual_output_api_v1’ of size48

[05:47:17.536] Chosen EGL config details: id: 41 rgba: 8 8 8 0 buf: 24 dep: 0stcl: 0 int: 1-60 type: win|pix|pbf|swap_preserved vis_id: XRGB8888 (0x34325258

[05:47:17.537] Output DPI-1 (crtc 33) video modes:

640x480@59.9, preferred, current, 25.2 MHz

[05:47:17.537] associating input device event2 with output DPI-1 (none by udev)

[05:47:17.537] associating input device event3 with output DPI-1 (none by udev)

[05:47:17.537] associating input device event4 with output DPI-1 (none by udev)

[05:47:17.537] associating input device event5 with output DPI-1 (none by udev)

[05:47:17.537] associating input device event1 with output DPI-1 (none by udev)

[05:47:17.537] associating input device event0 with output DPI-1 (none by udev)

[05:47:17.537] Output ‘DPI-1’ enabled with head(s) DPI-1

[05:47:17.537] Compositor capabilities:

arbitrary surface rotation: yes

screen capture uses y-flip: yes

presentation clock: CLOCK_MONOTONIC, id 1

presentation clock resolution: 0.000000001 s

[05:47:17.538] Loading module ‘/usr/lib/aarch64-linux-gnu/weston/desktop-shell.o’

[05:47:17.540] launching ‘/usr/lib/aarch64-linux-gnu/weston-keyboard’

[05:47:17.549] Loading module ‘/usr/lib/aarch64-linux-gnu/libweston-9/xwayland.o’

[05:47:17.584] Registered plugin API ‘weston_xwayland_v1’ of size 32

[05:47:17.584] Registered plugin API ‘weston_xwayland_surface_v1’ of size 16

[05:47:17.585] xserver listening on display :0

[05:47:17.585] launching ‘/usr/lib/aarch64-linux-gnu/weston-desktop-shell’

could not load cursor ‘dnd-move’

could not load cursor ‘dnd-move’

could not load cursor ‘dnd-copy’

could not load cursor ‘dnd-copy’

could not load cursor ‘dnd-none’

could not load cursor ‘dnd-none’

could not load cursor ‘dnd-move’

could not load cursor ‘dnd-copy’

could not load cursor ‘dnd-none’

weston-touch-calibrator error: “:0” was not found.

Could you please advise further?
Thanks!

Hi Rudhi,
Sorry for the delay. We did not try this out as we had to move to Android from Torizon.
Now the resolution issue seems to be resolved however we do not have any touch input.
Are we missing something here? Should touch be supported out of the box?

Hi @vsr138,

The display should work with the right resolution. Have you applied the right device tree overlay? Please find more information on which device tree and how to apply it here in this article: Device Tree Overlays on Torizon | Toradex Developer Center

Also, you should calibrate the touch screen as it is mentioned in the article I referred to you earlier.

Hi @rudhi.tx
As I mentioned, we moved from Torizon to Android. Now resolution is as expected.
But no touch input.

Hello @vsr138 ,
regarding the other issue

can you please create another topic? That is in order not to have multiple issues in a single topic.

Best regards,
Josep

1 Like