Capacitive touch panel causes Odroid to hang

[benwillcox]

Hi there,

I'm currently testing a capacitive touch panel and USB controller with my Odroid C2 running Android 6.0.1 (latest build). The device id is 222a:0001 and it shows the following with dmesg:

[ 318.127261@0] input: ILITEK Multi-Touch-V3000 as /devices/dwc2_b/usb1/1-1/1-1.3/1-1.3:1.0/0003:222A:0001.0005/input/input8
[ 318.133861@0] hid-multitouch 0003:222A:0001.0005: input: USB HID v1.10 Device [ILITEK Multi-Touch-V3000] on usb-dwc2_b-1.3/input0
[ 318.147395@0] input: ILITEK Multi-Touch-V3000 as /devices/dwc2_b/usb1/1-1/1-1.3/1-1.3:1.1/0003:222A:0001.0006/input/input9
[ 318.156571@0] hid-generic 0003:222A:0001.0006: input,hiddev0: USB HID v1.10 Mouse [ILITEK Multi-Touch-V3000] on usb-dwc2_b-1.3/input1

It works just fine for a seemingly random amount of time, from a couple of minutes up to about 15 or 20 minutes, then the Odroid completely hangs and the blue heartbeat LED stops flashing. There are no other USB devices connected to the Odroid. I have to power cycle the Odroid to recover from this.

Would there be any way of debugging what could be causing this?

Thanks,
Ben

[odroid]

Try to use the OTG(micro-USB) port with a host cable something like this.
http://www.hardkernel.com/main/products ... 0193470720

You have to connect a power supply to the DC barrel jack instead of micro-USB.
Don't forget to remove the J1 jumper.
https://wiki.odroid.com/odroid-c2/hardw ... wer_enable

[benwillcox]

Thanks, I already tried that as I have to do this with my resistive touch controller AR1100 to prevent a malfunction with the GPS module. Unfortunately it makes no difference on the OTG port or the main USB ports with this new capacitive controller.

Ben

[odroid]

Can you find any clue in "dmesg" output?

[benwillcox]

Hi, I will have to do some more testing, the problem seems much worse with the GPS module connected.

The problem with running dmesg is that when the Odroid hangs, I can't obviously run this - is there a way to get a continuous syslog output like you would do on Linux?

Thanks,
Ben

[odroid]

I have no idea syslog-like feature in Android.
I think "logcat" seems to be a solution.

Can you show us lsusb -t output on a Linux machine with GPS and touchscreen connection?

[benwillcox]

Hi, I made a little more progress, and I think that in fact the system hanging may be due to the Odroid clock frequency being set to maximum.

I recently replaced my C2 board that I have had for over a year, with a brand new C2 board (swapped the eMMC so didn't re-install any software). As with the old board, I run this at maximum clock frequency available in Odroid Utility. I tried setting the frequency back to standard (1536000) and ran the system for a while, and it doesn't hang.
Is the Odroid supposed to be able to reliably run at 1752000 frequency, or could this cause the system to hang? Perhaps my new board is not tolerance of the maximum frequency like the old board was?

I still have an issue with the Capacitive USB touch, which often causes the GPS to drop out and stop working. I had the same issue with the AR-1100 resistive touch, which could be solved by putting the AR-1100 on the OTG port and the GPS on the main USB bus. This does help with the new capacitive touch, but the GPS does still stop working now and then.

However, to recover from this situation, it needs the Odroid to be rebooted. This is the same case if the USB GPS gets unplugged and plugged back in during normal operation. It would be a great help and make the system more resilient if the USB GPS could be hot-plugged so that you don't need to reboot if there is a problem with it. Do you think this could be possible to solve?

Thanks,
Ben

[rooted]

Is the Odroid supposed to be able to reliably run at 1752000 frequency, or could this cause the system to hang? Perhaps my new board is not tolerance of the maximum frequency like the old board was?

No, this is overclocked. It is unlikely to be stable, it's why it must be enabled manually.

[benwillcox]

Thank you @rooted, then I better keep it at the default speed for best reliability.

Thanks,
Ben