Hi: I'm using st-image-weston-openstlinux-weston-stm32mp1.ext4. The USB mouse works, but the touch screen doesn't respond.

[zxiao.4]

Using hexdump /dev/input/event1, you can see the data changes. when I use ts_ test command, "open fbdevice: no such file or directory" will appear. Please help me, I really don't know how to configure it.I am sure that the touch screen monitoring is correct and the data is uploaded correctly.

[Gregory PLANCHON]

Hi @zxiao.4​ ,

I need additional information in order to find the problem.

Can you tell me which card you use and which version of openstlinux ?

What did you do for the moment ? 

Did you follow the distribution package ?

regards,

Grégory

[zxiao.4]

Hi：

I use a customized board, similar to stm32mp157d-dk1. Opstlinux 5.15.04 kernel. The error log of Weston is as follows:​

read-back format: BGRA

        EGL Wayland extension: yes

[13:49:56.022] event0 - gpio-keys: is tagged by udev as: Keyboard

[13:49:56.022] event0 - gpio-keys: device is a keyboard

[13:49:56.050] event1 - generic ft5x06 (82): is tagged by udev as: Touchscreen

[13:49:56.056] event1 - generic ft5x06 (82): device is a touch device

[13:49:56.264] libinput: configuring device "gpio-keys".

[13:49:56.265] Touchscreen - generic ft5x06 (82) - /sys/devices/platform/soc/40013000.i2c/i2c-1/1-0038/input/input1/event1

[13:49:56.265] libinput: configuring device "generic ft5x06 (82)".

[13:49:56.265] input device event1 has no enabled output associated (none named), skipping calibration for now.

[13:49:56.265] DRM: head 'DPI-1' updated, connector 32 is connected, EDID make 'unknown', model 'unknown', serial 'unknown'

[13:49:56.266] DRM: head 'DPI-1' found, connector 32 is connected, EDID make 'unknown', model 'unknown', serial 'unknown'

[13:49:56.267] Registered plugin API 'weston_drm_output_api_v1' of size 12

[13:49:56.267] Color manager: no-op

[13:49:56.268] Output 'DPI-1' using color profile: built-in default sRGB SDR profile

[13:49:56.307] Chosen EGL config details: id: 11 rgba: 8 8 8 0 buf: 24 dep: 0 stcl: 0 int: 1-60 type: win|pix|pbf|swap_preserved vis_id: XRGB8888 (0x34325258)

[13:49:56.307] Output DPI-1 (crtc 37) video modes:

        1024x600@60.0, preferred, current, 51.2 MHz

[13:49:56.308] associating input device event0 with output DPI-1 (none by udev)

[13:49:56.308] associating input device event1 with output DPI-1 (none by udev)

[13:49:56.310] Output 'DPI-1' enabled with head(s) DPI-1

[13:49:56.310] Compositor capabilities:

        arbitrary surface rotation: yes

        screen capture uses y-flip: yes

        cursor planes: yes

        arbitrary resolutions: no

        view mask clipping: yes

        explicit sync: yes

        color operations: no

        presentation clock: CLOCK_MONOTONIC, id 1

        presentation clock resolution: 0.000000001 s

[13:49:56.315] Loading module '/usr/lib/weston/desktop-shell.so'

[13:49:56.331] launching '/usr/libexec/weston-keyboard'

[13:49:56.336] Warning: support for deprecated wl_shell interface is enabled. Please migrate legacy clients to xdg-shell.

[13:49:56.339] Loading module '/usr/lib/weston/systemd-notify.so'

[13:49:56.341] launching '/usr/libexec/weston-desktop-shell'

[zxiao.4]

input device event1 has no enabled output associated (none named), skipping calibration for now.

I think this should be the reason for the mistake, but I don't know how to correct it.

[Gregory PLANCHON]

Hello,

Could you share me your device tree In order to check if the I2C is well configured.

regards,

Grégory

[zxiao.4]

&i2c2 {

    ft5x06: ft5x06@38 {

        compatible = "edt,edt-ft5x06","edt,edt-ft5406";

        interrupt-parent = <&gpioi>;

        interrupts = <1 IRQ_TYPE_EDGE_FALLING>; /* TOUCH_INT# */

        vcc-supply = <&v3v3>;

        reg = <0x38>;

        reset-gpios = <&gpioh 15 GPIO_ACTIVE_LOW>;  /* TOUCH_RESET# */

        touchscreen-size-x = <1024>;

        touchscreen-size-y = <600>;

        status = "okay";

    };

};

root@stm32mp1:~# evtest

No device specified, trying to scan all of /dev/input/event*

Available devices:

/dev/input/event0:   gpio-keys

/dev/input/event1:   generic ft5x06 (82)

Select the device event number [0-1]: 1

Input driver version is 1.0.1

Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0

Input device name: "generic ft5x06 (82)"

Supported events:

 Event type 0 (EV_SYN)

 Event type 1 (EV_KEY)

  Event code 330 (BTN_TOUCH)

 Event type 3 (EV_ABS)

  Event code 0 (ABS_X)

   Value  574

   Min    0

   Max   1023

  Event code 1 (ABS_Y)

   Value   70

   Min    0

   Max   599

  Event code 47 (ABS_MT_SLOT)

   Value   0

   Min    0

   Max    4

  Event code 53 (ABS_MT_POSITION_X)

   Value   0

   Min    0

   Max   1023

  Event code 54 (ABS_MT_POSITION_Y)

   Value   0

   Min    0

   Max   599

  Event code 57 (ABS_MT_TRACKING_ID)

   Value   0

   Min    0

   Max  65535

Properties:

 Property type 1 (INPUT_PROP_DIRECT)

Testing ... (interrupt to exit)

Event: time 1659402314.202796, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 6

Event: time 1659402314.202796, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 348

Event: time 1659402314.202796, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416

Event: time 1659402314.202796, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1

Event: time 1659402314.202796, type 3 (EV_ABS), code 0 (ABS_X), value 348

Event: time 1659402314.202796, type 3 (EV_ABS), code 1 (ABS_Y), value 416

Event: time 1659402314.202796, -------------- SYN_REPORT ------------

Event: time 1659402314.214664, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 347

Event: time 1659402314.214664, type 3 (EV_ABS), code 0 (ABS_X), value 347

Event: time 1659402314.214664, -------------- SYN_REPORT ------------

Event: time 1659402314.296616, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1

Event: time 1659402314.296616, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0

Event: time 1659402314.296616, -------------- SYN_REPORT ------------

I can detect events, but the screen just doesn't respond.

[Gregory PLANCHON]

Hello,

I am looking for the cause of the problem and I need to know your use case to try to understand.

Regards,

Grégory

[zxiao.4 · Accepted solution]

I've fixed it. It should be the problem of touch coordinates. I just rotate in the device tree and reverse direction.