From: Bryan Bui-T. <bb...@sp...> - 2008-08-26 21:21:09
|
Afternoon everyone, I have a Connex 400xm + breakout-gs board, but will be designing my own breakout board, and I need to add a touch screen. What pins (gpio/pwm) lines are used to connect the UCB1400 lcd controller to the xpa? Are these pins available on the Connex 400xm 60pin Hirose connector or the breakout-gs board? Are there any 4-wire touch screen controllers that you would recommend? Regards, Bryan |
From: Raziel M <ra_...@ya...> - 2009-03-20 22:55:50
|
Hi, 1.- I want to know if Could I use overo and e-ink to build a touch screen? 2.- Do you know where i can buy the e-ink to test it? Thank you. __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.yahoo.com.mx/ |
From: Dante S. <da...@ma...> - 2009-03-23 13:17:31
|
I don't know about using the overo for this, but I've browsed through this website before- http://www.eink.com/products/index.html They were all too pricey for me to play with. Raziel M wrote: > > Hi, > > 1.- I want to know if Could I use overo and e-ink to build a touch screen? > 2.- Do you know where i can buy the e-ink to test it? > Thank you. > > __________________________________________________ > Correo Yahoo! > Espacio para todos tus mensajes, antivirus y antispam ¡gratis! > Regístrate ya - http://correo.yahoo.com.mx/ > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Touch-screen-tp22630363p22659958.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Paul D. D. <pde...@ix...> - 2011-01-11 21:25:12
|
I'm just starting out with a Fire COM on a Gallop43 module, with a 4.3" LCD. I got it all configured, and it boots up okay from the SD card. It displayed the calibration utility, which I went through, and it now puts up a desktop, but the touch screen is barely working. (Yes, I peeled the protective plastic off.) Touching does nothing unless I hold my finger on a point for a few seconds, after which the cursor jumps to that point. Is there some configuration I need to tweak? Or is there some special technique for using the touch screen as a mouse? Or is the touch screen not really expected to work smoothly on the desktop at all? -- Ciao, Paul D. DeRocco Paul mailto:pde...@ix... |
From: Bob C. <bco...@ve...> - 2011-01-12 02:24:45
|
Hi Paul, I have the Gallop43 board and an LCD too. Later on this week I'm going to start a wiki page for that board. Are you using a brand new prebuilt image on the SD card that has never been booted before? If you have, just wait. You won't see an instant boot, because the Overo is going through a lot of configuration stuff. If you have a slow SD card, like a Class 2 card, the initial boot process can be pretty slow. Eventually, the system will blossom into a desktop. You just need to wait a while. Go enjoy a coffee, or do some other things for a while, and check the LCD every now and then. Eventually you will get some action. And yes this happened to me the very first time with a new image, never-before booted boot partition and rootfs and the LCD. It didn't take hours to configure, but it did take a little while. And subsequent boots are a lot faster. Bob Cochran On 01/11/2011 04:24 PM, Paul D. DeRocco wrote: > I'm just starting out with a Fire COM on a Gallop43 module, with a 4.3" LCD. > I got it all configured, and it boots up okay from the SD card. It displayed > the calibration utility, which I went through, and it now puts up a desktop, > but the touch screen is barely working. (Yes, I peeled the protective > plastic off.) Touching does nothing unless I hold my finger on a point for a > few seconds, after which the cursor jumps to that point. Is there some > configuration I need to tweak? Or is there some special technique for using > the touch screen as a mouse? Or is the touch screen not really expected to > work smoothly on the desktop at all? > |
From: Paul D. D. <pde...@ix...> - 2011-01-12 03:00:08
|
> From: Bob Cochran [mailto:bco...@ve...] > > I have the Gallop43 board and an LCD too. Later on this week > I'm going > to start a wiki page for that board. > > Are you using a brand new prebuilt image on the SD card that > has never > been booted before? If you have, just wait. You won't see an instant > boot, because the Overo is going through a lot of > configuration stuff. > If you have a slow SD card, like a Class 2 card, the initial boot > process can be pretty slow. Eventually, the system will > blossom into a > desktop. You just need to wait a while. Go enjoy a coffee, or do some > other things for a while, and check the LCD every now and then. > Eventually you will get some action. > > And yes this happened to me the very first time with a new image, > never-before booted boot partition and rootfs and the LCD. It didn't > take hours to configure, but it did take a little while. And > subsequent > boots are a lot faster. That's not the issue. Yeah, the first time it took forever because the boot script visible on the USB terminal was configuring a long list of stuff for about half an hour. I do get a desktop, but it's difficult to use. Apparently, this touch screen is really intended for a stylus, not a finger, which I don't recall reading anywhere. It works somewhat better with a stylus, but still not great, and I'm not sure what the stylus equivalents of various mouse-isms are, or where I can find that information. I've looked at the scanty docs on tslib, and it didn't answer my questions. Also, since I did the five-point touch screen cal with my finger, I'd like to do it again with a stylus. How do I get it to re-run the cal? Another question I have is about the display resolution. It looks to me like my desktop (even after disabling the three virtual desktops) is larger than the actual screen. (Yes, I set the U-boot environment variable to "lcd43".) The list of available display resolutions in the dialog box is completely empty. Also, the xdpyinfo command is supposed to give me info on the display that X is running on, but it barfs, complaining that it can't open the display. So did some other commands that are supposed to talk to the display driver. -- Ciao, Paul D. DeRocco Paul mailto:pde...@ix... |
From: Bob C. <bco...@ve...> - 2011-01-12 03:15:33
|
On 01/11/2011 09:59 PM, Paul D. DeRocco wrote: > That's not the issue. Yeah, the first time it took forever because the boot > script visible on the USB terminal was configuring a long list of stuff for > about half an hour. > > I do get a desktop, but it's difficult to use. Apparently, this touch screen > is really intended for a stylus, not a finger, which I don't recall reading > anywhere. It works somewhat better with a stylus, but still not great, and > I'm not sure what the stylus equivalents of various mouse-isms are, or where > I can find that information. I've looked at the scanty docs on tslib, and it > didn't answer my questions. > > Also, since I did the five-point touch screen cal with my finger, I'd like > to do it again with a stylus. How do I get it to re-run the cal? > > Another question I have is about the display resolution. It looks to me like > my desktop (even after disabling the three virtual desktops) is larger than > the actual screen. (Yes, I set the U-boot environment variable to "lcd43".) > The list of available display resolutions in the dialog box is completely > empty. Also, the xdpyinfo command is supposed to give me info on the display > that X is running on, but it barfs, complaining that it can't open the > display. So did some other commands that are supposed to talk to the display > driver. Hi Paul, I don't have a lot of expertise with the LCD. I don't know whether to treat it as a touch screen or not. What I do is connect a USB hub to the USB OTG connector on the Gallop43. I do this with an USB OTG cable. Then in the hub I plug in a USB keyboard and mouse. I use the mouse on the LCD just as if I'm using any other LCD. You could be right that it really responds to a stylus and not a finger touch. I will need to find a stylus -- don't have one over here. That should be proof of my inexperience with the small LCD. I have the very same display resolution problem that you do. I was using an omap3-desktop-image and I think (without having proof) I need to use a palmtop image for the LCD in order to get the resolution fixed. Thanks Bob |
From: Neil M. <ne...@gu...> - 2011-01-22 02:25:40
|
ts_calibrate allows you to recalibrate. As Bob suggested, you might find the palmtop image better suited to the LCd and touchscreen. Neil On 11-01-11 07:15 PM, Bob Cochran wrote: > On 01/11/2011 09:59 PM, Paul D. DeRocco wrote: >> That's not the issue. Yeah, the first time it took forever because the boot >> script visible on the USB terminal was configuring a long list of stuff for >> about half an hour. >> >> I do get a desktop, but it's difficult to use. Apparently, this touch screen >> is really intended for a stylus, not a finger, which I don't recall reading >> anywhere. It works somewhat better with a stylus, but still not great, and >> I'm not sure what the stylus equivalents of various mouse-isms are, or where >> I can find that information. I've looked at the scanty docs on tslib, and it >> didn't answer my questions. >> >> Also, since I did the five-point touch screen cal with my finger, I'd like >> to do it again with a stylus. How do I get it to re-run the cal? >> >> Another question I have is about the display resolution. It looks to me like >> my desktop (even after disabling the three virtual desktops) is larger than >> the actual screen. (Yes, I set the U-boot environment variable to "lcd43".) >> The list of available display resolutions in the dialog box is completely >> empty. Also, the xdpyinfo command is supposed to give me info on the display >> that X is running on, but it barfs, complaining that it can't open the >> display. So did some other commands that are supposed to talk to the display >> driver. > Hi Paul, > > I don't have a lot of expertise with the LCD. I don't know whether to > treat it as a touch screen or not. What I do is connect a USB hub to the > USB OTG connector on the Gallop43. I do this with an USB OTG cable. Then > in the hub I plug in a USB keyboard and mouse. I use the mouse on the > LCD just as if I'm using any other LCD. > > You could be right that it really responds to a stylus and not a finger > touch. I will need to find a stylus -- don't have one over here. That > should be proof of my inexperience with the small LCD. > > I have the very same display resolution problem that you do. I was using > an omap3-desktop-image and I think (without having proof) I need to use > a palmtop image for the LCD in order to get the resolution fixed. > > Thanks > > Bob > > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |