From: Thomas E. <tho...@gm...> - 2010-10-15 18:32:09
|
I am having some problems with the touchscreen on my overo Fire with chestnut43 and LG lcd touchscreen combination. The touchscreen works and is calibrated fairly well, but it has significant problems. I have tried 2 LG lcd displays and had similar results. It can be visually seen when I load the full-screen keyboard. When I tap somewhere, the X cursor is accurately placed where I tap, but the button that gets pressed is quite frequently not where the cursor is. Often times I can see the cursor jump to an incorrect place for a small fraction of a second then to the correct location. The highlighted button (if I tap and hold) is sometimes no button at all, the button next to the correct one, or a button on the other side of the screen. The touchscreen is clearly unusable in this condition. Any ideas? -- Thomas Epperson Build a man a fire, and he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life. - Terry Pratchett. |
From: uglyoldbob <tho...@gm...> - 2010-10-18 05:03:02
|
Nobody else is having these touchscreen problems with the chestnut43 expansion board? uglyoldbob wrote: > > I am having some problems with the touchscreen on my overo Fire with > chestnut43 and LG lcd touchscreen combination. > > The touchscreen works and is calibrated fairly well, but it has > significant > problems. I have tried 2 LG lcd displays and had similar results. > > It can be visually seen when I load the full-screen keyboard. When I tap > somewhere, the X cursor is accurately placed where I tap, but the button > that gets pressed is quite frequently not where the cursor is. Often times > I > can see the cursor jump to an incorrect place for a small fraction of a > second then to the correct location. The highlighted button (if I tap and > hold) is sometimes no button at all, the button next to the correct one, > or > a button on the other side of the screen. > > The touchscreen is clearly unusable in this condition. Any ideas? > -- > Thomas Epperson > Build a man a fire, and he'll be warm for a day. Set a man on fire, and > he'll be warm for the rest of his life. - Terry Pratchett. > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/overo-chestnut43-touchscreen-problems-tp29974295p29987449.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Chris A. <chr...@gm...> - 2011-07-10 12:56:56
|
I know this is a bit of an older post but I have a similar problem. I posted this a few days a go: http://old.nabble.com/Touch-Screen-Issue-td32026453.html http://old.nabble.com/Touch-Screen-Issue-td32026453.html My problem is different where my touch screen does not work at all. Did you have to do anything special to get the touch screen to work? Or is my hardware bad? -- View this message in context: http://old.nabble.com/overo-chestnut43-touchscreen-problems-tp29974295p32031561.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Neil M. <ne...@gu...> - 2011-07-11 15:35:21
|
On 11-07-10 05:56 AM, Chris Anilao wrote: > > I know this is a bit of an older post but I have a similar problem. I posted > this a few days a go: > > http://old.nabble.com/Touch-Screen-Issue-td32026453.html > http://old.nabble.com/Touch-Screen-Issue-td32026453.html > > My problem is different where my touch screen does not work at all. Did you > have to do anything special to get the touch screen to work? Or is my > hardware bad? > > Have you tried recalibrating the touchscreen and then restarting gpe-dm? # ts_calibrate # /etc/init.d/gpe-dm stop # /etc/init.d/gpe-dm start - Neil |
From: Chris A. <chr...@gm...> - 2011-07-12 04:24:05
|
When I run ts_calibrate, I get: ts_open: No such file or directory I also ran ts_test and it says: /dev/input/touchscreen0: No such file or directory Any ideas why I would see these messages? Thanks! Chris enmach wrote: > > On 11-07-10 05:56 AM, Chris Anilao wrote: >> >> I know this is a bit of an older post but I have a similar problem. I >> posted >> this a few days a go: >> >> http://old.nabble.com/Touch-Screen-Issue-td32026453.html >> http://old.nabble.com/Touch-Screen-Issue-td32026453.html >> >> My problem is different where my touch screen does not work at all. Did >> you >> have to do anything special to get the touch screen to work? Or is my >> hardware bad? >> >> > > Have you tried recalibrating the touchscreen and then restarting gpe-dm? > > # ts_calibrate > # /etc/init.d/gpe-dm stop > # /etc/init.d/gpe-dm start > > - > Neil > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/overo-chestnut43-touchscreen-problems-tp29974295p32043181.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Chris A. <chr...@gm...> - 2011-07-12 04:31:43
|
Update: I did a modprobe -r ads7846 then a modprobe ads7846 and I got this: ads7846 spi1.0: touchscreen, irq 274 ads7846 spi1.0: no device detected, test read result was 0x00000000 I hope this helps. - Chris Chris Anilao wrote: > > When I run ts_calibrate, I get: > > ts_open: No such file or directory > > I also ran ts_test and it says: > > /dev/input/touchscreen0: No such file or directory > > Any ideas why I would see these messages? > > Thanks! > Chris > > > > enmach wrote: >> >> On 11-07-10 05:56 AM, Chris Anilao wrote: >>> >>> I know this is a bit of an older post but I have a similar problem. I >>> posted >>> this a few days a go: >>> >>> http://old.nabble.com/Touch-Screen-Issue-td32026453.html >>> http://old.nabble.com/Touch-Screen-Issue-td32026453.html >>> >>> My problem is different where my touch screen does not work at all. Did >>> you >>> have to do anything special to get the touch screen to work? Or is my >>> hardware bad? >>> >>> >> >> Have you tried recalibrating the touchscreen and then restarting gpe-dm? >> >> # ts_calibrate >> # /etc/init.d/gpe-dm stop >> # /etc/init.d/gpe-dm start >> >> - >> Neil >> >> ------------------------------------------------------------------------------ >> All of the data generated in your IT infrastructure is seriously >> valuable. >> Why? It contains a definitive record of application performance, security >> threats, fraudulent activity, and more. Splunk takes this data and makes >> sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- View this message in context: http://old.nabble.com/overo-chestnut43-touchscreen-problems-tp29974295p32043198.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Chris A. <chr...@gm...> - 2011-07-12 04:31:43
|
Update: I did a modprobe -r ads7846 then a modprobe ads7846 and I got this: ads7846 spi1.0: touchscreen, irq 274 ads7846 spi1.0: no device detected, test read result was 0x00000000 I hope this helps. - Chris Chris Anilao wrote: > > When I run ts_calibrate, I get: > > ts_open: No such file or directory > > I also ran ts_test and it says: > > /dev/input/touchscreen0: No such file or directory > > Any ideas why I would see these messages? > > Thanks! > Chris > > > > enmach wrote: >> >> On 11-07-10 05:56 AM, Chris Anilao wrote: >>> >>> I know this is a bit of an older post but I have a similar problem. I >>> posted >>> this a few days a go: >>> >>> http://old.nabble.com/Touch-Screen-Issue-td32026453.html >>> http://old.nabble.com/Touch-Screen-Issue-td32026453.html >>> >>> My problem is different where my touch screen does not work at all. Did >>> you >>> have to do anything special to get the touch screen to work? Or is my >>> hardware bad? >>> >>> >> >> Have you tried recalibrating the touchscreen and then restarting gpe-dm? >> >> # ts_calibrate >> # /etc/init.d/gpe-dm stop >> # /etc/init.d/gpe-dm start >> >> - >> Neil >> >> ------------------------------------------------------------------------------ >> All of the data generated in your IT infrastructure is seriously >> valuable. >> Why? It contains a definitive record of application performance, security >> threats, fraudulent activity, and more. Splunk takes this data and makes >> sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- View this message in context: http://old.nabble.com/overo-chestnut43-touchscreen-problems-tp29974295p32043199.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <as...@gu...> - 2011-07-12 15:40:28
|
Hi Chris, Do you see any evidence in dmesg of the ads7846 being initialized on boot? Is the chip actually present on your board (certainly this is a reason for an RMA if it is not.)? Thanks, Ash On Mon, Jul 11, 2011 at 9:31 PM, Chris Anilao <chr...@gm...> wrote: > I did a modprobe -r ads7846 then a modprobe ads7846 and I got this: > > ads7846 spi1.0: touchscreen, irq 274 > ads7846 spi1.0: no device detected, test read result was 0x00000000 > |
From: Chris A. <chr...@gm...> - 2011-07-13 03:08:07
|
Hi Ash, I see these lines when scan through dmesg: ads7846 spi1.0: touchscreen, irq 274 ads7846 spi1.0: no device detected, test read result was 0x00000000 Pretty much the same when I unload and load the driver. My board has bad Ethernet hardware and touchscreen hardware... So I guess I'm going to need an RMA huh? Thanks, Chris -- View this message in context: http://old.nabble.com/overo-chestnut43-touchscreen-problems-tp29974295p32050764.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2011-07-18 17:22:47
|
Hi Chris, On Tue, Jul 12, 2011 at 8:07 PM, Chris Anilao <chr...@gm...> wrote: > My board has bad Ethernet hardware and touchscreen hardware... > > So I guess I'm going to need an RMA huh? Yes---I would say so! -Ash |