Densitron Display Touch not working on BalenaFin v1.1 with Raspbian with Desktop

I am trying to use BalenaFin v1.1 with Densitron Display with USB touch. The display is working fine but the USB touch is not. I tested the display with Raspberry Pi 4 and it’s working fine.

Relevant dmesg entry:

[ 2.298399] usb 1-1.4: New USB device found, idVendor=1a86, idProduct=e5e3, bcdDevice= 0.00
[ 2.298417] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.298426] usb 1-1.4: Product: USB2IIC_CTP_CONTROL
[ 2.298437] usb 1-1.4: Manufacturer:
[ 2.337757] input: USB2IIC_CTP_CONTROL as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/0003:1A86:E5E3.0001/input/input0
[ 2.338926] hid-generic 0003:1A86:E5E3.0001: input,hidraw0: USB HID v1.00 Device [ USB2IIC_CTP_CONTROL] on usb-3f980000.usb-1.4/input0

Please help in getting this touch issue solved.

Hi there, on the logs you’ve shared I don’t see something alerting.
Could you please give me some extra context and let me know what do you mean the USB touch is not working on BalenaFin? You don’t see anything on the screen or do you only see the logo screen?

The screen is working fine. But the touch is not working.

I followed this article to see if I could debug:

I did this:

cat /dev/input/event? # replace ? with the event numbers

But I did not see any output from this on touching the screen.

I followed the same procedure in Raspberry Pi 4B, and I could see the output when I touched the screen.

Hi there – thanks for the additional information. I’ve asked our engineers to take a look at this, and we’ll get back to you with some troubleshooting suggestions.

All the best,

Hello, can you try verifying that the usbtouchscreen is indeed being used on the Pi4? You can do this by running lsmod | grep usbtouchscreen, if the driver does not appear, or is not being used can you send us the whole output os lsmod? Once we identified which driver is being used you can try running modprobe usbtouchscreen on the Fin (or replace usbtouchscreen with the correct driver). If all works you should be able to see events showing up in /dev/input/event0 when touching the screen