New ts not working

vysero · 08-19-2019, 02:43 PM

My ts (touchscreen) broke so a replacement was sent and it's not working. The application is running and is showing up on the screen but I can not interact with it. I thought perhaps I would just have to run ts_calibrate @usr/bin but that wasn't recognizing any devices. I figured perhaps I needed to specify the device so I ran lsusb:

Code:

root:/usr/bin# lsusb
Bus 001 Device 002: ID 0424:2514  
Bus 001 Device 001: ID 1d6b:0002

I tried specifying both ID's too ts_calibrate but neither was recognized. So I plugged in the old ts (still works just cracked) and ran lsusb and it is showing 3 devices instead of two:

Code:

root@ccimx6qpsbc:/# lsusb
Bus 001 Device 003: ID 2808:81c9  
Bus 001 Device 002: ID 0424:2514  
Bus 001 Device 001: ID 1d6b:0002

Do I need to configure the usb for the new ts somehow? I feel like it should have been plug-n-play if it was working correctly but perhaps not?

teckk · 08-19-2019, 03:24 PM

Quote:

My ts broke

What is a ts? What does it do? All that you have said is that it is some kind of USB device. A touch screen?
https://www.mankier.com/1/ts_calibrate

Quote:

The application is running

What application is running?

Quote:

Do I need to configure the usb for the new ts somehow?

How could anyone possibly know? Do you want to give some basic info?

vysero · 08-19-2019, 03:44 PM

@teckk Sure yeah ts stands for touchscreen. The application is a bit to complicated to explain but I doubt it has anything to do with why the ts isn't working. I was hoping someone might "possible know" because they might have run into a similar issue when trying to use a new replacement ts.

TB0ne · 08-21-2019, 01:37 PM

Quote:

Originally Posted by vysero

@teckk Sure yeah ts stands for touchscreen. The application is a bit to complicated to explain but I doubt it has anything to do with why the ts isn't working. I was hoping someone might "possible know" because they might have run into a similar issue when trying to use a new replacement ts.

Since you won't say what the brand/model of your touchscreen is, version/distro of Linux, hardware it's plugged in to, or give us ANY details, what do you think we'll be able to tell you? All we know is there is an 'application' involved, but you won't say anything about that either.

Without details there's zero we can tell you.

vysero · 08-21-2019, 04:00 PM

@TB0ne You sound angry? It's not that I wont give you any details it's that I don't know what details are relevant. The touchscreen is an 8" color TFT display with 1024x768 resolution PCAP with Atemel silicon used: it is the FEMA P/N GM1024768DW-80-TIX2-HLTGG ts. The processing core is an i.MX6 based System on a Module (SOM). It uses the quad core i.MX6+. The ts is plugging into the board via USB. The application varies we run multiple and various applications on the same hardware. In this case it is a simple GUI I have created for an audio interface system. The kernel is: Linux version 4.9.135

TB0ne · 08-22-2019, 06:34 AM

Quote:

Originally Posted by vysero

@TB0ne You sound angry? It's not that I wont give you any details it's that I don't know what details are relevant. The touchscreen is an 8" color TFT display with 1024x768 resolution PCAP with Atemel silicon used: it is the FEMA P/N GM1024768DW-80-TIX2-HLTGG ts. The processing core is an i.MX6 based System on a Module (SOM). It uses the quad core i.MX6+. The ts is plugging into the board via USB. The application varies we run multiple and various applications on the same hardware. In this case it is a simple GUI I have created for an audio interface system. The kernel is: Linux version 4.9.135

Not angry at all, but you're asking for advice and not giving a single detail, even though several were specifically mentioned. Not sure why that's hard to understand; post #2 and #4 asked specific questions, which you didn't answer.

Since you have the touchscreen running on an embedded device, is it also safe to assume the version/distro of Linux was done for that device?? If so, you're again asking us for things we will have no idea about; a custom version of Linux, running on an embedded device, and an application that you put together, and a niche device plugged into it. Not like anyone here is going to have much idea for comparison, will we?

Have you done any basic troubleshooting, to see if the screen is actually good? Cable? Have you plugged it in to another system of any type, to see if it's recognized? There appears to be a driver for Windows on their website, which will at least allow you to test it, but based on your first post, not sure what's not clear. Your device isn't even showing up as a basic USB device, known or unknown. Everything would obviously seem to point to bad hardware somewhere. Since you plug the broken one in and it DOES show up, that narrows it down, since you can now rule out the USB port on the system, and the system itself.

vysero · 08-22-2019, 09:26 AM

@TB0ne Post #2 asked what a ts was and I answered and it asked about the application and I responded that I don't believe it is relevant, as you said this seems like a hardware problem. Post #4 was yours and I do believe that I answered with all of the information you asked for.

In any case, I have done some basic troubleshooting as I talked about in my first post. I am no Kernel expert but this seems like a usb recognition problem. I am not sure how I might go about troubleshooting usb recognition problems in the kernel. From what I understand most of the Linux usb stuff is handled by the udev subsystem: /etc/udev/udev.d/ but I am in no way confident that I know how to troubleshoot that system. I thought perhaps there was just some simple script I could run to help the kernel recognize a new usb device but if this is supposed to happen automatically then perhaps I am safe in assuming the ts itself has some bad components?

TB0ne · 08-22-2019, 09:52 AM

Quote:

Originally Posted by vysero

@TB0ne Post #2 asked what a ts was and I answered and it asked about the application and I responded that I don't believe it is relevant, as you said this seems like a hardware problem. Post #4 was yours and I do believe that I answered with all of the information you asked for.

Post #2 asked what application, and asked for basic info. Past saying that ts meant touchscreen (which you did say in your first post), your reply didn't say anything past that. You did then reply with information after being prompted a second time.

Quote:

In any case, I have done some basic troubleshooting as I talked about in my first post. I am no Kernel expert but this seems like a usb recognition problem. I am not sure how I might go about troubleshooting usb recognition problems in the kernel. From what I understand most of the Linux usb stuff is handled by the udev subsystem: /etc/udev/udev.d/ but I am in no way confident that I know how to troubleshoot that system. I thought perhaps there was just some simple script I could run to help the kernel recognize a new usb device but if this is supposed to happen automatically then perhaps I am safe in assuming the ts itself has some bad components?

Sorry, but you don't seem to have read or understood what you were told before; did you think about what you already posted???

You plugged in the OLD broken one, and see it show up as a USB device
You plugged in the NEW one, and it **DOES NOT SHOW UP**

What does that tell you??? Your system obviously already recognizes the hardware itself, right??? It picked up the old one, which you ostensibly had working. So AGAIN:

You have ruled out the OS
You have ruled out the USB port
You have ruled out the application

Now what's left?? The hardware; again, you either have a defective replacement, or a bad USB cable. Have you tried plugging the new one into another system?? ANY system will work, since all you need it to do is show up as a device, known or unknown. Nothing to do with the kernel or 'usb stuff'.