Rock PI 4b 7 inch Display Touchscreen issue

The touchscreen does not work correctly on 7 inch Raspberry Display.
Sometimes there is no reaction to movement. Sometimes when you tap on the screen, the input event is duplicated.

There are many errors in dmesg logs:
[58093.177155] rockpi-ft5406: fts_i2c_read: i2c read error, -6
[58093.177671] rockpi-ft5406: fts_read_td_status: get reg td_status failed, -6
[58093.296881] rockpi-ft5406: fts_i2c_read: i2c read error, -6
[58093.297397] rockpi-ft5406: fts_read_td_status: get reg td_status failed, -6
[58093.416833] rockpi-ft5406: fts_i2c_read: i2c read error, -6
[58093.417350] rockpi-ft5406: fts_read_td_status: get reg td_status failed, -6

evtest log (tap on screen and hold):

Event: time 1637317152.018684, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 81
Event: time 1637317152.018684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 102
Event: time 1637317152.018684, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 257
Event: time 1637317152.018684, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1637317152.018684, -------------- SYN_REPORT ------------
Event: time 1637317152.042661, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1637317152.042661, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1637317152.042661, -------------- SYN_REPORT ------------
Event: time 1637317152.354578, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 82
Event: time 1637317152.354578, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 105
Event: time 1637317152.354578, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 261
Event: time 1637317152.354578, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1637317152.354578, -------------- SYN_REPORT ------------
Event: time 1637317152.377796, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1637317152.377796, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1637317152.377796, -------------- SYN_REPORT ------------
Event: time 1637317152.522610, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 83
Event: time 1637317152.522610, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1637317152.522610, -------------- SYN_REPORT ------------
Event: time 1637317152.545817, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1637317152.545817, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1637317152.545817, -------------- SYN_REPORT ------------
Event: time 1637317152.978610, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 84
Event: time 1637317152.978610, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1637317152.978610, -------------- SYN_REPORT ------------
Event: time 1637317153.001985, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1637317153.001985, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1637317153.001985, -------------- SYN_REPORT ------------
Event: time 1637317153.290575, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 85
Event: time 1637317153.290575, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1637317153.290575, -------------- SYN_REPORT ------------
Event: time 1637317153.313787, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1637317153.313787, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1637317153.313787, -------------- SYN_REPORT ------------
Event: time 1637317153.602839, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 86
Event: time 1637317153.602839, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1637317153.602839, -------------- SYN_REPORT ------------
Event: time 1637317153.626220, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1637317153.626220, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1637317153.626220, -------------- SYN_REPORT ------------
Event: time 1637317153.890479, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 87
Event: time 1637317153.890479, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1637317153.890479, -------------- SYN_REPORT ------------
Event: time 1637317153.914830, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1637317153.914830, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1637317153.914830, -------------- SYN_REPORT ------------
Event: time 1637317154.370732, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 88
Event: time 1637317154.370732, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1637317154.370732, -------------- SYN_REPORT ------------
Event: time 1637317154.394840, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1637317154.394840, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1637317154.394840, -------------- SYN_REPORT ------------
Event: time 1637317155.318675, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 89
Event: time 1637317155.318675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1637317155.318675, -------------- SYN_REPORT ------------
Event: time 1637317155.341784, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1637317155.341784, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1637317155.341784, -------------- SYN_REPORT ------------

Power supply 12v 3 a.

Did you ever get this to work. I am running into a similar issue.

Hello I am new to this but after hours of troubleshooting I was able to get my RIP 7in to work. I first downloaded an image from https://github.com/radxa/rock-pi-images-released/releases. I then went ahead and edited the /boot/hw_intfc.conf file. I changed intfc:i2c2=on, intfc:i2c6=on, intfc:i2c7=on. I then uncommented the line "intfc:dtoverlay=raspberrypi-7-inch-lcd. From there along with the 5v and ground pins I plugged in the SDA and SCL. SDA into GPIO 3 and SCL into GIPO 5. Note you will need to reboot your system after editing the .conf file. Hope this helps!

Has anybody ever gotten any DSI panels to work in Armbian? I can’t get the panel to show any output no matter what I do, at least with the 5.10.x kernel. I know some of the node names changed, so I had to rewrite the overlay to switch from dsi to mipi_dsi, but still no luck, though at least I see the changes in the device tree now, so the device tree overlay is at least getting loaded; it just isn’t doing anything.

The only thing even slightly related I see in dmesg is this:

[ 3.074915] vcc_mipi: failed to get the current voltage: -EPROBE_DEFER
[ 3.074934] vcc_mipi: supplied by vcc3v3_sys

which I’m assuming is just one device probing before a dependency’s driver loads, and is uninteresting. And this is six hours into trying to get this thing to actually paint the screen. This really shouldn’t be that hard…

Does anybody have a working overlay that enables DSI output on a 5.10.x or later kernel?