From: Derek B. <der...@pa...> - 2011-01-21 12:02:42
|
Hi, We have several gumstix overo with chestnut expansion board and LCD touch screen. They boot OK and display the default desktop, but the touch screen is virtually unusable. It is even a challenge to run the calibration utility (forced by removing /etc/pointercal). I had to resort to using one of the gumstix aerials as a stylus, as the touch screen would not accept any of my finger presses. We are using a pre-built image from October 2010: $ uname -a Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l GNU/Linux Overo # printenv dvimode=1024x768MR-16@60 defaultdisplay=lcd43 How can I fix this? Thanks, Derek |
From: BrentP <bre...@ic...> - 2011-01-27 23:13:40
|
I'm having precisely the same issue. I've seen it on prebuilt images and ones I've bitbaked. Right now I'm running the omap3-console-image which boots to a login prompt to the LCD. I noticed a clue this morning. When the local console blanks (the LCD) I notice that the output from ts_test is *much* faster, as low as 5 ms between samples (the poll rate to the ADS7846). If the console is not blanked, and I use ts_test to test the touchscreen, the time between samples is slow, up to 500ms between samples. If I use a USB mouse as input, the motion is very smooth in both X Windows and a Qt Embedded app. There seems to be some interaction between drawing to the framebuffer and the touchscreen driver. Derek Baum wrote: > > Hi, > > We have several gumstix overo with chestnut expansion board and LCD touch > screen. > > They boot OK and display the default desktop, but the touch screen is > virtually unusable. > > It is even a challenge to run the calibration utility (forced by removing > /etc/pointercal). I had to resort to using one of the gumstix aerials as a > stylus, as the touch screen would not accept any of my finger presses. > > We are using a pre-built image from October 2010: > > $ uname -a > Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l GNU/Linux > > > Overo # printenv > dvimode=1024x768MR-16@60 > defaultdisplay=lcd43 > > How can I fix this? > > Thanks, > > Derek > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30778005.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2011-01-28 18:33:00
|
Hi, I haven't seen this behaviour but these symptoms seemed bizarre and got me wondering. I'm just thinking aloud here: * is this a hardware or a software issue? If it is a hardware issue due to noise or settling time, is there a software workaround just by running at a different clock rate? * the driver for the touchscreen is found in drivers/input/touchscreen/ads7846.c and there is a TS_POLL_PERIOD parameter that, by varying, might show whether this is a software resource contention issue. * notably, the touchscreen driver uses the input subsystem, the spi bus, interrupts, and a high-resolution timer. Based on the symptoms, there is no resource contention in the input subsystem (USB is fine). Interrupts? * app note sbaa036 explains the possible electrical interference problems due to LCD backlight circuits. The backlight circuit and the ADS chip are physically distant in the board layout for the Chestnut43 and some of the interference reduction recommendations are followed but perhaps more filtering is required. * do changing the ads7846_config parameters in arch/arm/board_overo.c have any effect? * does changing the PWM signal supplied to the LCD backlight change the performance of the touchscreen. This is possible using Scott Ellis's PWM module (https://github.com/scottellis/omap3-pwm) -Ash On Fri, Jan 28, 2011 at 8:26 AM, BrentP <bre...@ic...> wrote: > > If I set the defaultdisplay to dvi in u-boot, i consistent see fast results > from the output of ts_print almost 100 samples per second). If I set the > defaultdisplay to lcd43 the output is closer to 5 samples per second on > average. > > I don't know why there is this interaction and I have no idea how to fix it. > > Have you had any breakthroughs, Derek? > > > > BrentP wrote: >> >> I'm having precisely the same issue. I've seen it on prebuilt images and >> ones I've bitbaked. Right now I'm running the omap3-console-image which >> boots to a login prompt to the LCD. >> >> I noticed a clue this morning. When the local console blanks (the LCD) I >> notice that the output from ts_test is *much* faster, as low as 5 ms >> between samples (the poll rate to the ADS7846). If the console is not >> blanked, and I use ts_test to test the touchscreen, the time between >> samples is slow, up to 500ms between samples. >> >> If I use a USB mouse as input, the motion is very smooth in both X Windows >> and a Qt Embedded app. >> >> There seems to be some interaction between drawing to the framebuffer and >> the touchscreen driver. >> >> >> >> Derek Baum wrote: >>> >>> Hi, >>> >>> We have several gumstix overo with chestnut expansion board and LCD touch >>> screen. >>> >>> They boot OK and display the default desktop, but the touch screen is >>> virtually unusable. >>> >>> It is even a challenge to run the calibration utility (forced by removing >>> /etc/pointercal). I had to resort to using one of the gumstix aerials as >>> a >>> stylus, as the touch screen would not accept any of my finger presses. >>> >>> We are using a pre-built image from October 2010: >>> >>> $ uname -a >>> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l GNU/Linux >>> >>> >>> Overo # printenv >>> dvimode=1024x768MR-16@60 >>> defaultdisplay=lcd43 >>> >>> How can I fix this? >>> >>> Thanks, >>> >>> Derek >>> >>> ------------------------------------------------------------------------------ >>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>> Finally, a world-class log management solution at an even better >>> price-free! >>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>> February 28th, so secure your free ArcSight Logger TODAY! >>> http://p.sf.net/sfu/arcsight-sfd2d >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> > > -- > View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: BrentP <bre...@ic...> - 2011-01-28 16:27:06
|
If I set the defaultdisplay to dvi in u-boot, i consistent see fast results from the output of ts_print almost 100 samples per second). If I set the defaultdisplay to lcd43 the output is closer to 5 samples per second on average. I don't know why there is this interaction and I have no idea how to fix it. Have you had any breakthroughs, Derek? BrentP wrote: > > I'm having precisely the same issue. I've seen it on prebuilt images and > ones I've bitbaked. Right now I'm running the omap3-console-image which > boots to a login prompt to the LCD. > > I noticed a clue this morning. When the local console blanks (the LCD) I > notice that the output from ts_test is *much* faster, as low as 5 ms > between samples (the poll rate to the ADS7846). If the console is not > blanked, and I use ts_test to test the touchscreen, the time between > samples is slow, up to 500ms between samples. > > If I use a USB mouse as input, the motion is very smooth in both X Windows > and a Qt Embedded app. > > There seems to be some interaction between drawing to the framebuffer and > the touchscreen driver. > > > > Derek Baum wrote: >> >> Hi, >> >> We have several gumstix overo with chestnut expansion board and LCD touch >> screen. >> >> They boot OK and display the default desktop, but the touch screen is >> virtually unusable. >> >> It is even a challenge to run the calibration utility (forced by removing >> /etc/pointercal). I had to resort to using one of the gumstix aerials as >> a >> stylus, as the touch screen would not accept any of my finger presses. >> >> We are using a pre-built image from October 2010: >> >> $ uname -a >> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l GNU/Linux >> >> >> Overo # printenv >> dvimode=1024x768MR-16@60 >> defaultdisplay=lcd43 >> >> How can I fix this? >> >> Thanks, >> >> Derek >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better >> price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Brent P. <Bre...@ic...> - 2011-01-28 19:32:25
|
The fact that setting defaultdisplay to dvi was a clue and got me to looking closer. If I set to dvi and use fbset to set the resolution to 480x272, I get output to the lcd that is mostly correct - there is a white stripe on the right hand side, but otherwise the video looks correct. In this mode, running ts_test works as expected. The touchscreen is very responsive. I dug into which video driver was being used when setting defaultdisplay to lcd43 vs. dvi. Long story short, lcd43 uses driver "samsung_lte_panel" (which is for Samsung SAMSUNG_LTE430WQ) and dvi uses "generic_panel." The 4.3" display I have that I bought from Gumstix is an LG/Philips LB043WQ2. The Samsung driver sets the pixel clock to 9200. When in "dvi" mode the clock is at 42553 (according to the output of fbset). I'm messing around to get the right timing settings for fbset to output the full resolution to my display to see if it is indeed just the LCD driver used. It seems strange to me that this would be the cause of the slow touchscreen response, but I'm not terribly familiar with the way things happen in the kernel. Brent -----Original Message----- From: Ash Charles [mailto:ash...@gm...] Sent: Friday, January 28, 2011 12:33 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] LCD touch screen unusable on Overo/Chestnut Hi, I haven't seen this behaviour but these symptoms seemed bizarre and got me wondering. I'm just thinking aloud here: * is this a hardware or a software issue? If it is a hardware issue due to noise or settling time, is there a software workaround just by running at a different clock rate? * the driver for the touchscreen is found in drivers/input/touchscreen/ads7846.c and there is a TS_POLL_PERIOD parameter that, by varying, might show whether this is a software resource contention issue. * notably, the touchscreen driver uses the input subsystem, the spi bus, interrupts, and a high-resolution timer. Based on the symptoms, there is no resource contention in the input subsystem (USB is fine). Interrupts? * app note sbaa036 explains the possible electrical interference problems due to LCD backlight circuits. The backlight circuit and the ADS chip are physically distant in the board layout for the Chestnut43 and some of the interference reduction recommendations are followed but perhaps more filtering is required. * do changing the ads7846_config parameters in arch/arm/board_overo.c have any effect? * does changing the PWM signal supplied to the LCD backlight change the performance of the touchscreen. This is possible using Scott Ellis's PWM module (https://github.com/scottellis/omap3-pwm) -Ash On Fri, Jan 28, 2011 at 8:26 AM, BrentP <bre...@ic...> wrote: > > If I set the defaultdisplay to dvi in u-boot, i consistent see fast results > from the output of ts_print almost 100 samples per second). If I set the > defaultdisplay to lcd43 the output is closer to 5 samples per second on > average. > > I don't know why there is this interaction and I have no idea how to fix it. > > Have you had any breakthroughs, Derek? > > > > BrentP wrote: >> >> I'm having precisely the same issue. I've seen it on prebuilt images and >> ones I've bitbaked. Right now I'm running the omap3-console-image which >> boots to a login prompt to the LCD. >> >> I noticed a clue this morning. When the local console blanks (the LCD) I >> notice that the output from ts_test is *much* faster, as low as 5 ms >> between samples (the poll rate to the ADS7846). If the console is not >> blanked, and I use ts_test to test the touchscreen, the time between >> samples is slow, up to 500ms between samples. >> >> If I use a USB mouse as input, the motion is very smooth in both X Windows >> and a Qt Embedded app. >> >> There seems to be some interaction between drawing to the framebuffer and >> the touchscreen driver. >> >> >> >> Derek Baum wrote: >>> >>> Hi, >>> >>> We have several gumstix overo with chestnut expansion board and LCD touch >>> screen. >>> >>> They boot OK and display the default desktop, but the touch screen is >>> virtually unusable. >>> >>> It is even a challenge to run the calibration utility (forced by removing >>> /etc/pointercal). I had to resort to using one of the gumstix aerials as >>> a >>> stylus, as the touch screen would not accept any of my finger presses. >>> >>> We are using a pre-built image from October 2010: >>> >>> $ uname -a >>> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l GNU/Linux >>> >>> >>> Overo # printenv >>> dvimode=1024x768MR-16@60 >>> defaultdisplay=lcd43 >>> >>> How can I fix this? >>> >>> Thanks, >>> >>> Derek >>> >>> ------------------------------------------------------------------------------ >>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>> Finally, a world-class log management solution at an even better >>> price-free! >>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>> February 28th, so secure your free ArcSight Logger TODAY! >>> http://p.sf.net/sfu/arcsight-sfd2d >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> > > -- > View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: BrentP <bre...@ic...> - 2011-01-29 21:03:45
|
I confirmed yesterday that my touchscreen responsiveness was directly related to the pixel clock setting of the LCD. I still don't understand why, but if I set the pixel clock to 9.6MHz (the nominal clock in the datasheet of the LCD), the touchscreen response was sluggish. As I increased it, it became better and better. I currently have it set to 15Mhz which is the top end spec'd in the datasheet. I had it as higha s 23.5MHz and everything was still working well. Any clues as to why the pixel clock on the LCD would effect things like this? Brent BrentP wrote: > > The fact that setting defaultdisplay to dvi was a clue and got me to > looking closer. If I set to dvi and use fbset to set the resolution to > 480x272, I get output to the lcd that is mostly correct - there is a white > stripe on the right hand side, but otherwise the video looks correct. In > this mode, running ts_test works as expected. The touchscreen is very > responsive. > > I dug into which video driver was being used when setting defaultdisplay > to lcd43 vs. dvi. > > Long story short, lcd43 uses driver "samsung_lte_panel" (which is for > Samsung SAMSUNG_LTE430WQ) and dvi uses "generic_panel." The 4.3" display > I have that I bought from Gumstix is an LG/Philips LB043WQ2. The Samsung > driver sets the pixel clock to 9200. When in "dvi" mode the clock is at > 42553 (according to the output of fbset). > > I'm messing around to get the right timing settings for fbset to output > the full resolution to my display to see if it is indeed just the LCD > driver used. It seems strange to me that this would be the cause of the > slow touchscreen response, but I'm not terribly familiar with the way > things happen in the kernel. > > Brent > > -----Original Message----- > From: Ash Charles [mailto:ash...@gm...] > Sent: Friday, January 28, 2011 12:33 PM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] LCD touch screen unusable on Overo/Chestnut > > Hi, > > I haven't seen this behaviour but these symptoms seemed bizarre and > got me wondering. > > I'm just thinking aloud here: > * is this a hardware or a software issue? If it is a hardware issue > due to noise or settling time, is there a software workaround just by > running at a different clock rate? > * the driver for the touchscreen is found in > drivers/input/touchscreen/ads7846.c and there is a TS_POLL_PERIOD > parameter that, by varying, might show whether this is a software > resource contention issue. > * notably, the touchscreen driver uses the input subsystem, the spi > bus, interrupts, and a high-resolution timer. Based on the symptoms, > there is no resource contention in the input subsystem (USB is fine). > Interrupts? > * app note sbaa036 explains the possible electrical interference > problems due to LCD backlight circuits. The backlight circuit and the > ADS chip are physically distant in the board layout for the Chestnut43 > and some of the interference reduction recommendations are followed > but perhaps more filtering is required. > * do changing the ads7846_config parameters in arch/arm/board_overo.c > have any effect? > * does changing the PWM signal supplied to the LCD backlight change > the performance of the touchscreen. This is possible using Scott > Ellis's PWM module (https://github.com/scottellis/omap3-pwm) > > -Ash > > On Fri, Jan 28, 2011 at 8:26 AM, BrentP <bre...@ic...> wrote: >> >> If I set the defaultdisplay to dvi in u-boot, i consistent see fast >> results >> from the output of ts_print almost 100 samples per second). If I set the >> defaultdisplay to lcd43 the output is closer to 5 samples per second on >> average. >> >> I don't know why there is this interaction and I have no idea how to fix >> it. >> >> Have you had any breakthroughs, Derek? >> >> >> >> BrentP wrote: >>> >>> I'm having precisely the same issue. I've seen it on prebuilt images and >>> ones I've bitbaked. Right now I'm running the omap3-console-image which >>> boots to a login prompt to the LCD. >>> >>> I noticed a clue this morning. When the local console blanks (the LCD) >>> I >>> notice that the output from ts_test is *much* faster, as low as 5 ms >>> between samples (the poll rate to the ADS7846). If the console is not >>> blanked, and I use ts_test to test the touchscreen, the time between >>> samples is slow, up to 500ms between samples. >>> >>> If I use a USB mouse as input, the motion is very smooth in both X >>> Windows >>> and a Qt Embedded app. >>> >>> There seems to be some interaction between drawing to the framebuffer >>> and >>> the touchscreen driver. >>> >>> >>> >>> Derek Baum wrote: >>>> >>>> Hi, >>>> >>>> We have several gumstix overo with chestnut expansion board and LCD >>>> touch >>>> screen. >>>> >>>> They boot OK and display the default desktop, but the touch screen is >>>> virtually unusable. >>>> >>>> It is even a challenge to run the calibration utility (forced by >>>> removing >>>> /etc/pointercal). I had to resort to using one of the gumstix aerials >>>> as >>>> a >>>> stylus, as the touch screen would not accept any of my finger presses. >>>> >>>> We are using a pre-built image from October 2010: >>>> >>>> $ uname -a >>>> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l GNU/Linux >>>> >>>> >>>> Overo # printenv >>>> dvimode=1024x768MR-16@60 >>>> defaultdisplay=lcd43 >>>> >>>> How can I fix this? >>>> >>>> Thanks, >>>> >>>> Derek >>>> >>>> ------------------------------------------------------------------------------ >>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>> Finally, a world-class log management solution at an even better >>>> price-free! >>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>> February 28th, so secure your free ArcSight Logger TODAY! >>>> http://p.sf.net/sfu/arcsight-sfd2d >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better >> price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30796698.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <as...@gu...> - 2011-01-31 21:26:49
|
Hi Brent, Thanks for the update. I wonder that you are seeing electrical interference between the backlight circuitry and the touchscreen ADC sampling---this sounds increasingly like a hardware issue. Can you take a photo or describe inductor L2 on the Chestnut board? As noted here (http://pubs.gumstix.com/boards/CHESTNUT/PCB30005-2467/Readme.txt), the part has been changed so I'd like to determine which you have. -Ash On Sat, Jan 29, 2011 at 1:03 PM, BrentP <bre...@ic...> wrote: > > I confirmed yesterday that my touchscreen responsiveness was directly related > to the pixel clock setting of the LCD. I still don't understand why, but if > I set the pixel clock to 9.6MHz (the nominal clock in the datasheet of the > LCD), the touchscreen response was sluggish. As I increased it, it became > better and better. I currently have it set to 15Mhz which is the top end > spec'd in the datasheet. I had it as higha s 23.5MHz and everything was > still working well. > > Any clues as to why the pixel clock on the LCD would effect things like > this? > > Brent > > > > BrentP wrote: >> >> The fact that setting defaultdisplay to dvi was a clue and got me to >> looking closer. If I set to dvi and use fbset to set the resolution to >> 480x272, I get output to the lcd that is mostly correct - there is a white >> stripe on the right hand side, but otherwise the video looks correct. In >> this mode, running ts_test works as expected. The touchscreen is very >> responsive. >> >> I dug into which video driver was being used when setting defaultdisplay >> to lcd43 vs. dvi. >> >> Long story short, lcd43 uses driver "samsung_lte_panel" (which is for >> Samsung SAMSUNG_LTE430WQ) and dvi uses "generic_panel." The 4.3" display >> I have that I bought from Gumstix is an LG/Philips LB043WQ2. The Samsung >> driver sets the pixel clock to 9200. When in "dvi" mode the clock is at >> 42553 (according to the output of fbset). >> >> I'm messing around to get the right timing settings for fbset to output >> the full resolution to my display to see if it is indeed just the LCD >> driver used. It seems strange to me that this would be the cause of the >> slow touchscreen response, but I'm not terribly familiar with the way >> things happen in the kernel. >> >> Brent >> >> -----Original Message----- >> From: Ash Charles [mailto:ash...@gm...] >> Sent: Friday, January 28, 2011 12:33 PM >> To: General mailing list for gumstix users. >> Subject: Re: [Gumstix-users] LCD touch screen unusable on Overo/Chestnut >> >> Hi, >> >> I haven't seen this behaviour but these symptoms seemed bizarre and >> got me wondering. >> >> I'm just thinking aloud here: >> * is this a hardware or a software issue? If it is a hardware issue >> due to noise or settling time, is there a software workaround just by >> running at a different clock rate? >> * the driver for the touchscreen is found in >> drivers/input/touchscreen/ads7846.c and there is a TS_POLL_PERIOD >> parameter that, by varying, might show whether this is a software >> resource contention issue. >> * notably, the touchscreen driver uses the input subsystem, the spi >> bus, interrupts, and a high-resolution timer. Based on the symptoms, >> there is no resource contention in the input subsystem (USB is fine). >> Interrupts? >> * app note sbaa036 explains the possible electrical interference >> problems due to LCD backlight circuits. The backlight circuit and the >> ADS chip are physically distant in the board layout for the Chestnut43 >> and some of the interference reduction recommendations are followed >> but perhaps more filtering is required. >> * do changing the ads7846_config parameters in arch/arm/board_overo.c >> have any effect? >> * does changing the PWM signal supplied to the LCD backlight change >> the performance of the touchscreen. This is possible using Scott >> Ellis's PWM module (https://github.com/scottellis/omap3-pwm) >> >> -Ash >> >> On Fri, Jan 28, 2011 at 8:26 AM, BrentP <bre...@ic...> wrote: >>> >>> If I set the defaultdisplay to dvi in u-boot, i consistent see fast >>> results >>> from the output of ts_print almost 100 samples per second). If I set the >>> defaultdisplay to lcd43 the output is closer to 5 samples per second on >>> average. >>> >>> I don't know why there is this interaction and I have no idea how to fix >>> it. >>> >>> Have you had any breakthroughs, Derek? >>> >>> >>> >>> BrentP wrote: >>>> >>>> I'm having precisely the same issue. I've seen it on prebuilt images and >>>> ones I've bitbaked. Right now I'm running the omap3-console-image which >>>> boots to a login prompt to the LCD. >>>> >>>> I noticed a clue this morning. When the local console blanks (the LCD) >>>> I >>>> notice that the output from ts_test is *much* faster, as low as 5 ms >>>> between samples (the poll rate to the ADS7846). If the console is not >>>> blanked, and I use ts_test to test the touchscreen, the time between >>>> samples is slow, up to 500ms between samples. >>>> >>>> If I use a USB mouse as input, the motion is very smooth in both X >>>> Windows >>>> and a Qt Embedded app. >>>> >>>> There seems to be some interaction between drawing to the framebuffer >>>> and >>>> the touchscreen driver. >>>> >>>> >>>> >>>> Derek Baum wrote: >>>>> >>>>> Hi, >>>>> >>>>> We have several gumstix overo with chestnut expansion board and LCD >>>>> touch >>>>> screen. >>>>> >>>>> They boot OK and display the default desktop, but the touch screen is >>>>> virtually unusable. >>>>> >>>>> It is even a challenge to run the calibration utility (forced by >>>>> removing >>>>> /etc/pointercal). I had to resort to using one of the gumstix aerials >>>>> as >>>>> a >>>>> stylus, as the touch screen would not accept any of my finger presses. >>>>> >>>>> We are using a pre-built image from October 2010: >>>>> >>>>> $ uname -a >>>>> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l GNU/Linux >>>>> >>>>> >>>>> Overo # printenv >>>>> dvimode=1024x768MR-16@60 >>>>> defaultdisplay=lcd43 >>>>> >>>>> How can I fix this? >>>>> >>>>> Thanks, >>>>> >>>>> Derek >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>> Finally, a world-class log management solution at an even better >>>>> price-free! >>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html >>> Sent from the Gumstix mailing list archive at Nabble.com. >>> >>> >>> ------------------------------------------------------------------------------ >>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>> Finally, a world-class log management solution at an even better >>> price-free! >>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>> February 28th, so secure your free ArcSight Logger TODAY! >>> http://p.sf.net/sfu/arcsight-sfd2d >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better >> price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better >> price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- > View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30796698.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: BrentP <bre...@ic...> - 2011-01-31 22:37:06
|
I guess I didn't mention but I'm actually using the new Gallop43 board which has only one revision (I think?). Ash Charles-2 wrote: > > Hi Brent, > > Thanks for the update. I wonder that you are seeing electrical > interference between the backlight circuitry and the touchscreen ADC > sampling---this sounds increasingly like a hardware issue. > > Can you take a photo or describe inductor L2 on the Chestnut board? As > noted here > (http://pubs.gumstix.com/boards/CHESTNUT/PCB30005-2467/Readme.txt), > the part has been changed so I'd like to determine which you have. > > -Ash > > On Sat, Jan 29, 2011 at 1:03 PM, BrentP <bre...@ic...> wrote: >> >> I confirmed yesterday that my touchscreen responsiveness was directly >> related >> to the pixel clock setting of the LCD. I still don't understand why, but >> if >> I set the pixel clock to 9.6MHz (the nominal clock in the datasheet of >> the >> LCD), the touchscreen response was sluggish. As I increased it, it >> became >> better and better. I currently have it set to 15Mhz which is the top end >> spec'd in the datasheet. I had it as higha s 23.5MHz and everything was >> still working well. >> >> Any clues as to why the pixel clock on the LCD would effect things like >> this? >> >> Brent >> >> >> >> BrentP wrote: >>> >>> The fact that setting defaultdisplay to dvi was a clue and got me to >>> looking closer. If I set to dvi and use fbset to set the resolution to >>> 480x272, I get output to the lcd that is mostly correct - there is a >>> white >>> stripe on the right hand side, but otherwise the video looks correct. >>> In >>> this mode, running ts_test works as expected. The touchscreen is very >>> responsive. >>> >>> I dug into which video driver was being used when setting defaultdisplay >>> to lcd43 vs. dvi. >>> >>> Long story short, lcd43 uses driver "samsung_lte_panel" (which is for >>> Samsung SAMSUNG_LTE430WQ) and dvi uses "generic_panel." The 4.3" >>> display >>> I have that I bought from Gumstix is an LG/Philips LB043WQ2. The Samsung >>> driver sets the pixel clock to 9200. When in "dvi" mode the clock is at >>> 42553 (according to the output of fbset). >>> >>> I'm messing around to get the right timing settings for fbset to output >>> the full resolution to my display to see if it is indeed just the LCD >>> driver used. It seems strange to me that this would be the cause of the >>> slow touchscreen response, but I'm not terribly familiar with the way >>> things happen in the kernel. >>> >>> Brent >>> >>> -----Original Message----- >>> From: Ash Charles [mailto:ash...@gm...] >>> Sent: Friday, January 28, 2011 12:33 PM >>> To: General mailing list for gumstix users. >>> Subject: Re: [Gumstix-users] LCD touch screen unusable on Overo/Chestnut >>> >>> Hi, >>> >>> I haven't seen this behaviour but these symptoms seemed bizarre and >>> got me wondering. >>> >>> I'm just thinking aloud here: >>> * is this a hardware or a software issue? If it is a hardware issue >>> due to noise or settling time, is there a software workaround just by >>> running at a different clock rate? >>> * the driver for the touchscreen is found in >>> drivers/input/touchscreen/ads7846.c and there is a TS_POLL_PERIOD >>> parameter that, by varying, might show whether this is a software >>> resource contention issue. >>> * notably, the touchscreen driver uses the input subsystem, the spi >>> bus, interrupts, and a high-resolution timer. Based on the symptoms, >>> there is no resource contention in the input subsystem (USB is fine). >>> Interrupts? >>> * app note sbaa036 explains the possible electrical interference >>> problems due to LCD backlight circuits. The backlight circuit and the >>> ADS chip are physically distant in the board layout for the Chestnut43 >>> and some of the interference reduction recommendations are followed >>> but perhaps more filtering is required. >>> * do changing the ads7846_config parameters in arch/arm/board_overo.c >>> have any effect? >>> * does changing the PWM signal supplied to the LCD backlight change >>> the performance of the touchscreen. This is possible using Scott >>> Ellis's PWM module (https://github.com/scottellis/omap3-pwm) >>> >>> -Ash >>> >>> On Fri, Jan 28, 2011 at 8:26 AM, BrentP <bre...@ic...> wrote: >>>> >>>> If I set the defaultdisplay to dvi in u-boot, i consistent see fast >>>> results >>>> from the output of ts_print almost 100 samples per second). If I set >>>> the >>>> defaultdisplay to lcd43 the output is closer to 5 samples per second on >>>> average. >>>> >>>> I don't know why there is this interaction and I have no idea how to >>>> fix >>>> it. >>>> >>>> Have you had any breakthroughs, Derek? >>>> >>>> >>>> >>>> BrentP wrote: >>>>> >>>>> I'm having precisely the same issue. I've seen it on prebuilt images >>>>> and >>>>> ones I've bitbaked. Right now I'm running the omap3-console-image >>>>> which >>>>> boots to a login prompt to the LCD. >>>>> >>>>> I noticed a clue this morning. When the local console blanks (the >>>>> LCD) >>>>> I >>>>> notice that the output from ts_test is *much* faster, as low as 5 ms >>>>> between samples (the poll rate to the ADS7846). If the console is not >>>>> blanked, and I use ts_test to test the touchscreen, the time between >>>>> samples is slow, up to 500ms between samples. >>>>> >>>>> If I use a USB mouse as input, the motion is very smooth in both X >>>>> Windows >>>>> and a Qt Embedded app. >>>>> >>>>> There seems to be some interaction between drawing to the framebuffer >>>>> and >>>>> the touchscreen driver. >>>>> >>>>> >>>>> >>>>> Derek Baum wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> We have several gumstix overo with chestnut expansion board and LCD >>>>>> touch >>>>>> screen. >>>>>> >>>>>> They boot OK and display the default desktop, but the touch screen is >>>>>> virtually unusable. >>>>>> >>>>>> It is even a challenge to run the calibration utility (forced by >>>>>> removing >>>>>> /etc/pointercal). I had to resort to using one of the gumstix aerials >>>>>> as >>>>>> a >>>>>> stylus, as the touch screen would not accept any of my finger >>>>>> presses. >>>>>> >>>>>> We are using a pre-built image from October 2010: >>>>>> >>>>>> $ uname -a >>>>>> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l >>>>>> GNU/Linux >>>>>> >>>>>> >>>>>> Overo # printenv >>>>>> dvimode=1024x768MR-16@60 >>>>>> defaultdisplay=lcd43 >>>>>> >>>>>> How can I fix this? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Derek >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>>> Finally, a world-class log management solution at an even better >>>>>> price-free! >>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>> _______________________________________________ >>>>>> gumstix-users mailing list >>>>>> gum...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html >>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>> Finally, a world-class log management solution at an even better >>>> price-free! >>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>> February 28th, so secure your free ArcSight Logger TODAY! >>>> http://p.sf.net/sfu/arcsight-sfd2d >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>> >>> ------------------------------------------------------------------------------ >>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>> Finally, a world-class log management solution at an even better >>> price-free! >>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>> February 28th, so secure your free ArcSight Logger TODAY! >>> http://p.sf.net/sfu/arcsight-sfd2d >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> ------------------------------------------------------------------------------ >>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>> Finally, a world-class log management solution at an even better >>> price-free! >>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>> February 28th, so secure your free ArcSight Logger TODAY! >>> http://p.sf.net/sfu/arcsight-sfd2d >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30796698.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better >> price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30811526.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steven D. <zen...@ma...> - 2011-02-02 02:01:49
|
I had this issue with a Fire on either Chestnut43 or Palo43. Commenting out the pthres module in /etc/ts.conf solved the problem. It's supposed to smooth the input if memory serves, but it does the job a little TOO well... :-) --S On Jan 21, 2011, at 3:33 AM, Derek Baum wrote: > Hi, > > We have several gumstix overo with chestnut expansion board and LCD touch screen. > > They boot OK and display the default desktop, but the touch screen is virtually unusable. > > It is even a challenge to run the calibration utility (forced by removing /etc/pointercal). I had to resort to using one of the gumstix aerials as a stylus, as the touch screen would not accept any of my finger presses. > > We are using a pre-built image from October 2010: > > $ uname -a > Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l GNU/Linux > > > Overo # printenv > dvimode=1024x768MR-16@60 > defaultdisplay=lcd43 > > How can I fix this? > > Thanks, > > Derek > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d_______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: dcraw101 <dcr...@ya...> - 2011-05-24 00:16:40
|
I have the exact same problem with an Overo water and Chestnut. I tried commenting out the pthres module, but that did not help. Interestingly, If I set defaultdisplay to dvi, the touch panel is no longer recognized. If the defaultdisplay is set to lcd43 the ts_print delay between samples is very long. When the LCD times out ts_print works just fine. I am using a very recent omap3-console-image with 2.6.36. Steven Doyle wrote: > > I had this issue with a Fire on either Chestnut43 or Palo43. Commenting > out the pthres module in /etc/ts.conf solved the problem. It's supposed > to smooth the input if memory serves, but it does the job a little TOO > well... :-) > > --S > > On Jan 21, 2011, at 3:33 AM, Derek Baum wrote: > >> Hi, >> >> We have several gumstix overo with chestnut expansion board and LCD touch >> screen. >> >> They boot OK and display the default desktop, but the touch screen is >> virtually unusable. >> >> It is even a challenge to run the calibration utility (forced by removing >> /etc/pointercal). I had to resort to using one of the gumstix aerials as >> a stylus, as the touch screen would not accept any of my finger presses. >> >> We are using a pre-built image from October 2010: >> >> $ uname -a >> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l GNU/Linux >> >> >> Overo # printenv >> dvimode=1024x768MR-16@60 >> defaultdisplay=lcd43 >> >> How can I fix this? >> >> Thanks, >> >> Derek >> >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better >> price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d_______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31686510.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: JamesAng <ang...@gm...> - 2011-06-01 09:04:36
|
I've a Overo Fire FE with Chestnut and 4.3" LCD. I do encounter the same problem with the vertical inversion and long delay with the touchscreen. Will we be seeing a commit for the solution proposed soon to the the main git? Thks in adv. -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31747808.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: JamesAng <ang...@gm...> - 2011-06-23 01:48:57
|
Hi Ash, I'm using the Chestnut board & I experience the same issue. For the L2 inductor on my board, it's a 3mm(W)x4mm(L)x~2mm(H) black box with no surface-marking. The surrounding of the inductor is concaved. My board is PCB30005-R2467 & bought recently about a month ago. Please advise. Thanks in adv. James. Ash Charles-2 wrote: > > Hi Brent, > > Thanks for the update. I wonder that you are seeing electrical > interference between the backlight circuitry and the touchscreen ADC > sampling---this sounds increasingly like a hardware issue. > > Can you take a photo or describe inductor L2 on the Chestnut board? As > noted here > (http://pubs.gumstix.com/boards/CHESTNUT/PCB30005-2467/Readme.txt), > the part has been changed so I'd like to determine which you have. > > -Ash > > On Sat, Jan 29, 2011 at 1:03 PM, BrentP <bre...@ic...> wrote: >> >> I confirmed yesterday that my touchscreen responsiveness was directly >> related >> to the pixel clock setting of the LCD. I still don't understand why, but >> if >> I set the pixel clock to 9.6MHz (the nominal clock in the datasheet of >> the >> LCD), the touchscreen response was sluggish. As I increased it, it >> became >> better and better. I currently have it set to 15Mhz which is the top end >> spec'd in the datasheet. I had it as higha s 23.5MHz and everything was >> still working well. >> >> Any clues as to why the pixel clock on the LCD would effect things like >> this? >> >> Brent >> >> >> >> BrentP wrote: >>> >>> The fact that setting defaultdisplay to dvi was a clue and got me to >>> looking closer. If I set to dvi and use fbset to set the resolution to >>> 480x272, I get output to the lcd that is mostly correct - there is a >>> white >>> stripe on the right hand side, but otherwise the video looks correct. >>> In >>> this mode, running ts_test works as expected. The touchscreen is very >>> responsive. >>> >>> I dug into which video driver was being used when setting defaultdisplay >>> to lcd43 vs. dvi. >>> >>> Long story short, lcd43 uses driver "samsung_lte_panel" (which is for >>> Samsung SAMSUNG_LTE430WQ) and dvi uses "generic_panel." The 4.3" >>> display >>> I have that I bought from Gumstix is an LG/Philips LB043WQ2. The Samsung >>> driver sets the pixel clock to 9200. When in "dvi" mode the clock is at >>> 42553 (according to the output of fbset). >>> >>> I'm messing around to get the right timing settings for fbset to output >>> the full resolution to my display to see if it is indeed just the LCD >>> driver used. It seems strange to me that this would be the cause of the >>> slow touchscreen response, but I'm not terribly familiar with the way >>> things happen in the kernel. >>> >>> Brent >>> >>> -----Original Message----- >>> From: Ash Charles [mailto:ash...@gm...] >>> Sent: Friday, January 28, 2011 12:33 PM >>> To: General mailing list for gumstix users. >>> Subject: Re: [Gumstix-users] LCD touch screen unusable on Overo/Chestnut >>> >>> Hi, >>> >>> I haven't seen this behaviour but these symptoms seemed bizarre and >>> got me wondering. >>> >>> I'm just thinking aloud here: >>> * is this a hardware or a software issue? If it is a hardware issue >>> due to noise or settling time, is there a software workaround just by >>> running at a different clock rate? >>> * the driver for the touchscreen is found in >>> drivers/input/touchscreen/ads7846.c and there is a TS_POLL_PERIOD >>> parameter that, by varying, might show whether this is a software >>> resource contention issue. >>> * notably, the touchscreen driver uses the input subsystem, the spi >>> bus, interrupts, and a high-resolution timer. Based on the symptoms, >>> there is no resource contention in the input subsystem (USB is fine). >>> Interrupts? >>> * app note sbaa036 explains the possible electrical interference >>> problems due to LCD backlight circuits. The backlight circuit and the >>> ADS chip are physically distant in the board layout for the Chestnut43 >>> and some of the interference reduction recommendations are followed >>> but perhaps more filtering is required. >>> * do changing the ads7846_config parameters in arch/arm/board_overo.c >>> have any effect? >>> * does changing the PWM signal supplied to the LCD backlight change >>> the performance of the touchscreen. This is possible using Scott >>> Ellis's PWM module (https://github.com/scottellis/omap3-pwm) >>> >>> -Ash >>> >>> On Fri, Jan 28, 2011 at 8:26 AM, BrentP <bre...@ic...> wrote: >>>> >>>> If I set the defaultdisplay to dvi in u-boot, i consistent see fast >>>> results >>>> from the output of ts_print almost 100 samples per second). If I set >>>> the >>>> defaultdisplay to lcd43 the output is closer to 5 samples per second on >>>> average. >>>> >>>> I don't know why there is this interaction and I have no idea how to >>>> fix >>>> it. >>>> >>>> Have you had any breakthroughs, Derek? >>>> >>>> >>>> >>>> BrentP wrote: >>>>> >>>>> I'm having precisely the same issue. I've seen it on prebuilt images >>>>> and >>>>> ones I've bitbaked. Right now I'm running the omap3-console-image >>>>> which >>>>> boots to a login prompt to the LCD. >>>>> >>>>> I noticed a clue this morning. When the local console blanks (the >>>>> LCD) >>>>> I >>>>> notice that the output from ts_test is *much* faster, as low as 5 ms >>>>> between samples (the poll rate to the ADS7846). If the console is not >>>>> blanked, and I use ts_test to test the touchscreen, the time between >>>>> samples is slow, up to 500ms between samples. >>>>> >>>>> If I use a USB mouse as input, the motion is very smooth in both X >>>>> Windows >>>>> and a Qt Embedded app. >>>>> >>>>> There seems to be some interaction between drawing to the framebuffer >>>>> and >>>>> the touchscreen driver. >>>>> >>>>> >>>>> >>>>> Derek Baum wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> We have several gumstix overo with chestnut expansion board and LCD >>>>>> touch >>>>>> screen. >>>>>> >>>>>> They boot OK and display the default desktop, but the touch screen is >>>>>> virtually unusable. >>>>>> >>>>>> It is even a challenge to run the calibration utility (forced by >>>>>> removing >>>>>> /etc/pointercal). I had to resort to using one of the gumstix aerials >>>>>> as >>>>>> a >>>>>> stylus, as the touch screen would not accept any of my finger >>>>>> presses. >>>>>> >>>>>> We are using a pre-built image from October 2010: >>>>>> >>>>>> $ uname -a >>>>>> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l >>>>>> GNU/Linux >>>>>> >>>>>> >>>>>> Overo # printenv >>>>>> dvimode=1024x768MR-16@60 >>>>>> defaultdisplay=lcd43 >>>>>> >>>>>> How can I fix this? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Derek >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>>> Finally, a world-class log management solution at an even better >>>>>> price-free! >>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>> _______________________________________________ >>>>>> gumstix-users mailing list >>>>>> gum...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html >>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>> Finally, a world-class log management solution at an even better >>>> price-free! >>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>> February 28th, so secure your free ArcSight Logger TODAY! >>>> http://p.sf.net/sfu/arcsight-sfd2d >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>> >>> ------------------------------------------------------------------------------ >>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>> Finally, a world-class log management solution at an even better >>> price-free! >>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>> February 28th, so secure your free ArcSight Logger TODAY! >>> http://p.sf.net/sfu/arcsight-sfd2d >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> ------------------------------------------------------------------------------ >>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>> Finally, a world-class log management solution at an even better >>> price-free! >>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>> February 28th, so secure your free ArcSight Logger TODAY! >>> http://p.sf.net/sfu/arcsight-sfd2d >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30796698.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better >> price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31908184.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <as...@gu...> - 2011-06-23 17:08:51
|
Hi James, You've mentioned two issues: - vertical flip of display: this seems to be an issue in the April15th image. We are looking in to a fix but for the time being, switching to a different image or changing the version of Xorg would be my suggestion. - low touchscreen sensitivity. As discussed in this thread, there are several software work-arounds all of which effectively change the frequency of the LCD clock. Sorry I don't have more details here but this particular problem seems real but is hard to replicate. Thanks for providing the details about the inductor---this helps us isolate any hardware issues. -Ash On Wed, Jun 22, 2011 at 6:48 PM, JamesAng <ang...@gm...> wrote: > > Hi Ash, > > I'm using the Chestnut board & I experience the same issue. > > For the L2 inductor on my board, it's a 3mm(W)x4mm(L)x~2mm(H) black box with > no surface-marking. > The surrounding of the inductor is concaved. > > My board is PCB30005-R2467 & bought recently about a month ago. > > Please advise. > > Thanks in adv. > > James. > > > Ash Charles-2 wrote: >> >> Hi Brent, >> >> Thanks for the update. I wonder that you are seeing electrical >> interference between the backlight circuitry and the touchscreen ADC >> sampling---this sounds increasingly like a hardware issue. >> >> Can you take a photo or describe inductor L2 on the Chestnut board? As >> noted here >> (http://pubs.gumstix.com/boards/CHESTNUT/PCB30005-2467/Readme.txt), >> the part has been changed so I'd like to determine which you have. >> >> -Ash >> >> On Sat, Jan 29, 2011 at 1:03 PM, BrentP <bre...@ic...> wrote: >>> >>> I confirmed yesterday that my touchscreen responsiveness was directly >>> related >>> to the pixel clock setting of the LCD. I still don't understand why, but >>> if >>> I set the pixel clock to 9.6MHz (the nominal clock in the datasheet of >>> the >>> LCD), the touchscreen response was sluggish. As I increased it, it >>> became >>> better and better. I currently have it set to 15Mhz which is the top end >>> spec'd in the datasheet. I had it as higha s 23.5MHz and everything was >>> still working well. >>> >>> Any clues as to why the pixel clock on the LCD would effect things like >>> this? >>> >>> Brent >>> >>> >>> >>> BrentP wrote: >>>> >>>> The fact that setting defaultdisplay to dvi was a clue and got me to >>>> looking closer. If I set to dvi and use fbset to set the resolution to >>>> 480x272, I get output to the lcd that is mostly correct - there is a >>>> white >>>> stripe on the right hand side, but otherwise the video looks correct. >>>> In >>>> this mode, running ts_test works as expected. The touchscreen is very >>>> responsive. >>>> >>>> I dug into which video driver was being used when setting defaultdisplay >>>> to lcd43 vs. dvi. >>>> >>>> Long story short, lcd43 uses driver "samsung_lte_panel" (which is for >>>> Samsung SAMSUNG_LTE430WQ) and dvi uses "generic_panel." The 4.3" >>>> display >>>> I have that I bought from Gumstix is an LG/Philips LB043WQ2. The Samsung >>>> driver sets the pixel clock to 9200. When in "dvi" mode the clock is at >>>> 42553 (according to the output of fbset). >>>> >>>> I'm messing around to get the right timing settings for fbset to output >>>> the full resolution to my display to see if it is indeed just the LCD >>>> driver used. It seems strange to me that this would be the cause of the >>>> slow touchscreen response, but I'm not terribly familiar with the way >>>> things happen in the kernel. >>>> >>>> Brent >>>> >>>> -----Original Message----- >>>> From: Ash Charles [mailto:ash...@gm...] >>>> Sent: Friday, January 28, 2011 12:33 PM >>>> To: General mailing list for gumstix users. >>>> Subject: Re: [Gumstix-users] LCD touch screen unusable on Overo/Chestnut >>>> >>>> Hi, >>>> >>>> I haven't seen this behaviour but these symptoms seemed bizarre and >>>> got me wondering. >>>> >>>> I'm just thinking aloud here: >>>> * is this a hardware or a software issue? If it is a hardware issue >>>> due to noise or settling time, is there a software workaround just by >>>> running at a different clock rate? >>>> * the driver for the touchscreen is found in >>>> drivers/input/touchscreen/ads7846.c and there is a TS_POLL_PERIOD >>>> parameter that, by varying, might show whether this is a software >>>> resource contention issue. >>>> * notably, the touchscreen driver uses the input subsystem, the spi >>>> bus, interrupts, and a high-resolution timer. Based on the symptoms, >>>> there is no resource contention in the input subsystem (USB is fine). >>>> Interrupts? >>>> * app note sbaa036 explains the possible electrical interference >>>> problems due to LCD backlight circuits. The backlight circuit and the >>>> ADS chip are physically distant in the board layout for the Chestnut43 >>>> and some of the interference reduction recommendations are followed >>>> but perhaps more filtering is required. >>>> * do changing the ads7846_config parameters in arch/arm/board_overo.c >>>> have any effect? >>>> * does changing the PWM signal supplied to the LCD backlight change >>>> the performance of the touchscreen. This is possible using Scott >>>> Ellis's PWM module (https://github.com/scottellis/omap3-pwm) >>>> >>>> -Ash >>>> >>>> On Fri, Jan 28, 2011 at 8:26 AM, BrentP <bre...@ic...> wrote: >>>>> >>>>> If I set the defaultdisplay to dvi in u-boot, i consistent see fast >>>>> results >>>>> from the output of ts_print almost 100 samples per second). If I set >>>>> the >>>>> defaultdisplay to lcd43 the output is closer to 5 samples per second on >>>>> average. >>>>> >>>>> I don't know why there is this interaction and I have no idea how to >>>>> fix >>>>> it. >>>>> >>>>> Have you had any breakthroughs, Derek? >>>>> >>>>> >>>>> >>>>> BrentP wrote: >>>>>> >>>>>> I'm having precisely the same issue. I've seen it on prebuilt images >>>>>> and >>>>>> ones I've bitbaked. Right now I'm running the omap3-console-image >>>>>> which >>>>>> boots to a login prompt to the LCD. >>>>>> >>>>>> I noticed a clue this morning. When the local console blanks (the >>>>>> LCD) >>>>>> I >>>>>> notice that the output from ts_test is *much* faster, as low as 5 ms >>>>>> between samples (the poll rate to the ADS7846). If the console is not >>>>>> blanked, and I use ts_test to test the touchscreen, the time between >>>>>> samples is slow, up to 500ms between samples. >>>>>> >>>>>> If I use a USB mouse as input, the motion is very smooth in both X >>>>>> Windows >>>>>> and a Qt Embedded app. >>>>>> >>>>>> There seems to be some interaction between drawing to the framebuffer >>>>>> and >>>>>> the touchscreen driver. >>>>>> >>>>>> >>>>>> >>>>>> Derek Baum wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> We have several gumstix overo with chestnut expansion board and LCD >>>>>>> touch >>>>>>> screen. >>>>>>> >>>>>>> They boot OK and display the default desktop, but the touch screen is >>>>>>> virtually unusable. >>>>>>> >>>>>>> It is even a challenge to run the calibration utility (forced by >>>>>>> removing >>>>>>> /etc/pointercal). I had to resort to using one of the gumstix aerials >>>>>>> as >>>>>>> a >>>>>>> stylus, as the touch screen would not accept any of my finger >>>>>>> presses. >>>>>>> >>>>>>> We are using a pre-built image from October 2010: >>>>>>> >>>>>>> $ uname -a >>>>>>> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l >>>>>>> GNU/Linux >>>>>>> >>>>>>> >>>>>>> Overo # printenv >>>>>>> dvimode=1024x768MR-16@60 >>>>>>> defaultdisplay=lcd43 >>>>>>> >>>>>>> How can I fix this? >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Derek >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>>>> Finally, a world-class log management solution at an even better >>>>>>> price-free! >>>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>>> _______________________________________________ >>>>>>> gumstix-users mailing list >>>>>>> gum...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html >>>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>> Finally, a world-class log management solution at an even better >>>>> price-free! >>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>> Finally, a world-class log management solution at an even better >>>> price-free! >>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>> February 28th, so secure your free ArcSight Logger TODAY! >>>> http://p.sf.net/sfu/arcsight-sfd2d >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> ------------------------------------------------------------------------------ >>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>> Finally, a world-class log management solution at an even better >>>> price-free! >>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>> February 28th, so secure your free ArcSight Logger TODAY! >>>> http://p.sf.net/sfu/arcsight-sfd2d >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30796698.html >>> Sent from the Gumstix mailing list archive at Nabble.com. >>> >>> >>> ------------------------------------------------------------------------------ >>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>> Finally, a world-class log management solution at an even better >>> price-free! >>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>> February 28th, so secure your free ArcSight Logger TODAY! >>> http://p.sf.net/sfu/arcsight-sfd2d >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better >> price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- > View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31908184.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with vRanger. > Installation's a snap, and flexible recovery options mean your data is safe, > secure and there when you need it. Data protection magic? > Nope - It's vRanger. Get your free trial download today. > http://p.sf.net/sfu/quest-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Gerald M. <gjm...@ve...> - 2011-06-24 01:05:20
|
I have the same Chestnut board with the same inductor and am experiencing the same problems with the touch screen. |
From: JamesAng <ang...@gm...> - 2011-06-24 01:38:18
|
Hi Ash, Thanks for the suggestion for my 2 issues. As I'm a newbie to Linux world thus I follows closely the wiki guides to setup my development machine on Ubuntu 10.04 LTS ( http://www.gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html http://www.gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html ) and appreciate all the help that I can get from the community. I understand that I've to make changes to the source files to overcome some of the issues I encountered with the touchscreen. But, I don't know where are the source files located in my development machine to make the changes so that it will be pickup and compile using the 'bitbake omap3-desktop-nand-image' command. The following are the directories in my overo-oe folder: bitbake org.openembedded.dev build sources tmp Can you tell me where I should modify these driver's files so that it can be bitbake? or did I missed cloning some source's repository? Thks a million in adv. :) James. Ash Charles-2 wrote: > > Hi James, > > You've mentioned two issues: > - vertical flip of display: this seems to be an issue in the April15th > image. We are looking in to a fix but for the time being, switching > to a different image or changing the version of Xorg would be my > suggestion. > - low touchscreen sensitivity. As discussed in this thread, there are > several software work-arounds all of which effectively change the > frequency of the LCD clock. Sorry I don't have more details here but > this particular problem seems real but is hard to replicate. > > Thanks for providing the details about the inductor---this helps us > isolate any hardware issues. > > -Ash > On Wed, Jun 22, 2011 at 6:48 PM, JamesAng <ang...@gm...> wrote: >> >> Hi Ash, >> >> I'm using the Chestnut board & I experience the same issue. >> >> For the L2 inductor on my board, it's a 3mm(W)x4mm(L)x~2mm(H) black box >> with >> no surface-marking. >> The surrounding of the inductor is concaved. >> >> My board is PCB30005-R2467 & bought recently about a month ago. >> >> Please advise. >> >> Thanks in adv. >> >> James. >> >> >> Ash Charles-2 wrote: >>> >>> Hi Brent, >>> >>> Thanks for the update. I wonder that you are seeing electrical >>> interference between the backlight circuitry and the touchscreen ADC >>> sampling---this sounds increasingly like a hardware issue. >>> >>> Can you take a photo or describe inductor L2 on the Chestnut board? As >>> noted here >>> (http://pubs.gumstix.com/boards/CHESTNUT/PCB30005-2467/Readme.txt), >>> the part has been changed so I'd like to determine which you have. >>> >>> -Ash >>> >>> On Sat, Jan 29, 2011 at 1:03 PM, BrentP <bre...@ic...> wrote: >>>> >>>> I confirmed yesterday that my touchscreen responsiveness was directly >>>> related >>>> to the pixel clock setting of the LCD. I still don't understand why, >>>> but >>>> if >>>> I set the pixel clock to 9.6MHz (the nominal clock in the datasheet of >>>> the >>>> LCD), the touchscreen response was sluggish. As I increased it, it >>>> became >>>> better and better. I currently have it set to 15Mhz which is the top >>>> end >>>> spec'd in the datasheet. I had it as higha s 23.5MHz and everything >>>> was >>>> still working well. >>>> >>>> Any clues as to why the pixel clock on the LCD would effect things like >>>> this? >>>> >>>> Brent >>>> >>>> >>>> >>>> BrentP wrote: >>>>> >>>>> The fact that setting defaultdisplay to dvi was a clue and got me to >>>>> looking closer. If I set to dvi and use fbset to set the resolution >>>>> to >>>>> 480x272, I get output to the lcd that is mostly correct - there is a >>>>> white >>>>> stripe on the right hand side, but otherwise the video looks correct. >>>>> In >>>>> this mode, running ts_test works as expected. The touchscreen is very >>>>> responsive. >>>>> >>>>> I dug into which video driver was being used when setting >>>>> defaultdisplay >>>>> to lcd43 vs. dvi. >>>>> >>>>> Long story short, lcd43 uses driver "samsung_lte_panel" (which is for >>>>> Samsung SAMSUNG_LTE430WQ) and dvi uses "generic_panel." The 4.3" >>>>> display >>>>> I have that I bought from Gumstix is an LG/Philips LB043WQ2. The >>>>> Samsung >>>>> driver sets the pixel clock to 9200. When in "dvi" mode the clock is >>>>> at >>>>> 42553 (according to the output of fbset). >>>>> >>>>> I'm messing around to get the right timing settings for fbset to >>>>> output >>>>> the full resolution to my display to see if it is indeed just the LCD >>>>> driver used. It seems strange to me that this would be the cause of >>>>> the >>>>> slow touchscreen response, but I'm not terribly familiar with the way >>>>> things happen in the kernel. >>>>> >>>>> Brent >>>>> >>>>> -----Original Message----- >>>>> From: Ash Charles [mailto:ash...@gm...] >>>>> Sent: Friday, January 28, 2011 12:33 PM >>>>> To: General mailing list for gumstix users. >>>>> Subject: Re: [Gumstix-users] LCD touch screen unusable on >>>>> Overo/Chestnut >>>>> >>>>> Hi, >>>>> >>>>> I haven't seen this behaviour but these symptoms seemed bizarre and >>>>> got me wondering. >>>>> >>>>> I'm just thinking aloud here: >>>>> * is this a hardware or a software issue? If it is a hardware issue >>>>> due to noise or settling time, is there a software workaround just by >>>>> running at a different clock rate? >>>>> * the driver for the touchscreen is found in >>>>> drivers/input/touchscreen/ads7846.c and there is a TS_POLL_PERIOD >>>>> parameter that, by varying, might show whether this is a software >>>>> resource contention issue. >>>>> * notably, the touchscreen driver uses the input subsystem, the spi >>>>> bus, interrupts, and a high-resolution timer. Based on the symptoms, >>>>> there is no resource contention in the input subsystem (USB is fine). >>>>> Interrupts? >>>>> * app note sbaa036 explains the possible electrical interference >>>>> problems due to LCD backlight circuits. The backlight circuit and the >>>>> ADS chip are physically distant in the board layout for the Chestnut43 >>>>> and some of the interference reduction recommendations are followed >>>>> but perhaps more filtering is required. >>>>> * do changing the ads7846_config parameters in arch/arm/board_overo.c >>>>> have any effect? >>>>> * does changing the PWM signal supplied to the LCD backlight change >>>>> the performance of the touchscreen. This is possible using Scott >>>>> Ellis's PWM module (https://github.com/scottellis/omap3-pwm) >>>>> >>>>> -Ash >>>>> >>>>> On Fri, Jan 28, 2011 at 8:26 AM, BrentP <bre...@ic...> >>>>> wrote: >>>>>> >>>>>> If I set the defaultdisplay to dvi in u-boot, i consistent see fast >>>>>> results >>>>>> from the output of ts_print almost 100 samples per second). If I set >>>>>> the >>>>>> defaultdisplay to lcd43 the output is closer to 5 samples per second >>>>>> on >>>>>> average. >>>>>> >>>>>> I don't know why there is this interaction and I have no idea how to >>>>>> fix >>>>>> it. >>>>>> >>>>>> Have you had any breakthroughs, Derek? >>>>>> >>>>>> >>>>>> >>>>>> BrentP wrote: >>>>>>> >>>>>>> I'm having precisely the same issue. I've seen it on prebuilt images >>>>>>> and >>>>>>> ones I've bitbaked. Right now I'm running the omap3-console-image >>>>>>> which >>>>>>> boots to a login prompt to the LCD. >>>>>>> >>>>>>> I noticed a clue this morning. When the local console blanks (the >>>>>>> LCD) >>>>>>> I >>>>>>> notice that the output from ts_test is *much* faster, as low as 5 ms >>>>>>> between samples (the poll rate to the ADS7846). If the console is >>>>>>> not >>>>>>> blanked, and I use ts_test to test the touchscreen, the time between >>>>>>> samples is slow, up to 500ms between samples. >>>>>>> >>>>>>> If I use a USB mouse as input, the motion is very smooth in both X >>>>>>> Windows >>>>>>> and a Qt Embedded app. >>>>>>> >>>>>>> There seems to be some interaction between drawing to the >>>>>>> framebuffer >>>>>>> and >>>>>>> the touchscreen driver. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Derek Baum wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> We have several gumstix overo with chestnut expansion board and LCD >>>>>>>> touch >>>>>>>> screen. >>>>>>>> >>>>>>>> They boot OK and display the default desktop, but the touch screen >>>>>>>> is >>>>>>>> virtually unusable. >>>>>>>> >>>>>>>> It is even a challenge to run the calibration utility (forced by >>>>>>>> removing >>>>>>>> /etc/pointercal). I had to resort to using one of the gumstix >>>>>>>> aerials >>>>>>>> as >>>>>>>> a >>>>>>>> stylus, as the touch screen would not accept any of my finger >>>>>>>> presses. >>>>>>>> >>>>>>>> We are using a pre-built image from October 2010: >>>>>>>> >>>>>>>> $ uname -a >>>>>>>> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l >>>>>>>> GNU/Linux >>>>>>>> >>>>>>>> >>>>>>>> Overo # printenv >>>>>>>> dvimode=1024x768MR-16@60 >>>>>>>> defaultdisplay=lcd43 >>>>>>>> >>>>>>>> How can I fix this? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Derek >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD >>>>>>>> value)! >>>>>>>> Finally, a world-class log management solution at an even better >>>>>>>> price-free! >>>>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>>>> _______________________________________________ >>>>>>>> gumstix-users mailing list >>>>>>>> gum...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html >>>>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>>> Finally, a world-class log management solution at an even better >>>>>> price-free! >>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>> _______________________________________________ >>>>>> gumstix-users mailing list >>>>>> gum...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>> Finally, a world-class log management solution at an even better >>>>> price-free! >>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> ------------------------------------------------------------------------------ >>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>> Finally, a world-class log management solution at an even better >>>>> price-free! >>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30796698.html >>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>> Finally, a world-class log management solution at an even better >>>> price-free! >>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>> February 28th, so secure your free ArcSight Logger TODAY! >>>> http://p.sf.net/sfu/arcsight-sfd2d >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>> >>> ------------------------------------------------------------------------------ >>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>> Finally, a world-class log management solution at an even better >>> price-free! >>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>> February 28th, so secure your free ArcSight Logger TODAY! >>> http://p.sf.net/sfu/arcsight-sfd2d >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31908184.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> Simplify data backup and recovery for your virtual environment with >> vRanger. >> Installation's a snap, and flexible recovery options mean your data is >> safe, >> secure and there when you need it. Data protection magic? >> Nope - It's vRanger. Get your free trial download today. >> http://p.sf.net/sfu/quest-sfdev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with > vRanger. > Installation's a snap, and flexible recovery options mean your data is > safe, > secure and there when you need it. Data protection magic? > Nope - It's vRanger. Get your free trial download today. > http://p.sf.net/sfu/quest-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31916123.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <as...@gu...> - 2011-06-25 01:16:11
|
Hi James, For my suggestion to change the version of Xorg, you should just be able to opkg a different version. Here is some documentation on the opkg command: http://gumstix.org/add-software-packages.html. Editing the source for various packages in OE is a trickier proposition as OE recipes use different mechanisms to fetch and build source. For recipes that just use source code in your recipes folder, you can simple edit and re-bitbake. Most recipes are fetched from source control or tarballs so editing the source so it is picked up by bitbake would mean changing something upstream. Again, there are workarounds but it requires a knowledge of bitbake. There is some basic documentation here: http://gumstix.org/software-development/open-embedded.html. However, if you post back about what specific source code you wish to change, the community will likely have some good suggestion on how best to handle that particular case. Vague answer---sorry---it is just a lot to explain in one go! -Ash On Thu, Jun 23, 2011 at 6:38 PM, JamesAng <ang...@gm...> wrote: > > Hi Ash, > > Thanks for the suggestion for my 2 issues. > > As I'm a newbie to Linux world thus I follows closely the wiki guides to > setup my development machine on Ubuntu 10.04 LTS ( > http://www.gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html > http://www.gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html > ) and appreciate all the help that I can get from the community. > > I understand that I've to make changes to the source files to overcome some > of the issues I encountered with the touchscreen. But, I don't know where > are the source files located in my development machine to make the changes > so that it will be pickup and compile using the 'bitbake > omap3-desktop-nand-image' command. > > The following are the directories in my overo-oe folder: > bitbake > org.openembedded.dev > build > sources > tmp > > Can you tell me where I should modify these driver's files so that it can be > bitbake? > or did I missed cloning some source's repository? > > Thks a million in adv. :) > > James. > > > > Ash Charles-2 wrote: >> >> Hi James, >> >> You've mentioned two issues: >> - vertical flip of display: this seems to be an issue in the April15th >> image. We are looking in to a fix but for the time being, switching >> to a different image or changing the version of Xorg would be my >> suggestion. >> - low touchscreen sensitivity. As discussed in this thread, there are >> several software work-arounds all of which effectively change the >> frequency of the LCD clock. Sorry I don't have more details here but >> this particular problem seems real but is hard to replicate. >> >> Thanks for providing the details about the inductor---this helps us >> isolate any hardware issues. >> >> -Ash >> On Wed, Jun 22, 2011 at 6:48 PM, JamesAng <ang...@gm...> wrote: >>> >>> Hi Ash, >>> >>> I'm using the Chestnut board & I experience the same issue. >>> >>> For the L2 inductor on my board, it's a 3mm(W)x4mm(L)x~2mm(H) black box >>> with >>> no surface-marking. >>> The surrounding of the inductor is concaved. >>> >>> My board is PCB30005-R2467 & bought recently about a month ago. >>> >>> Please advise. >>> >>> Thanks in adv. >>> >>> James. >>> >>> >>> Ash Charles-2 wrote: >>>> >>>> Hi Brent, >>>> >>>> Thanks for the update. I wonder that you are seeing electrical >>>> interference between the backlight circuitry and the touchscreen ADC >>>> sampling---this sounds increasingly like a hardware issue. >>>> >>>> Can you take a photo or describe inductor L2 on the Chestnut board? As >>>> noted here >>>> (http://pubs.gumstix.com/boards/CHESTNUT/PCB30005-2467/Readme.txt), >>>> the part has been changed so I'd like to determine which you have. >>>> >>>> -Ash >>>> >>>> On Sat, Jan 29, 2011 at 1:03 PM, BrentP <bre...@ic...> wrote: >>>>> >>>>> I confirmed yesterday that my touchscreen responsiveness was directly >>>>> related >>>>> to the pixel clock setting of the LCD. I still don't understand why, >>>>> but >>>>> if >>>>> I set the pixel clock to 9.6MHz (the nominal clock in the datasheet of >>>>> the >>>>> LCD), the touchscreen response was sluggish. As I increased it, it >>>>> became >>>>> better and better. I currently have it set to 15Mhz which is the top >>>>> end >>>>> spec'd in the datasheet. I had it as higha s 23.5MHz and everything >>>>> was >>>>> still working well. >>>>> >>>>> Any clues as to why the pixel clock on the LCD would effect things like >>>>> this? >>>>> >>>>> Brent >>>>> >>>>> >>>>> >>>>> BrentP wrote: >>>>>> >>>>>> The fact that setting defaultdisplay to dvi was a clue and got me to >>>>>> looking closer. If I set to dvi and use fbset to set the resolution >>>>>> to >>>>>> 480x272, I get output to the lcd that is mostly correct - there is a >>>>>> white >>>>>> stripe on the right hand side, but otherwise the video looks correct. >>>>>> In >>>>>> this mode, running ts_test works as expected. The touchscreen is very >>>>>> responsive. >>>>>> >>>>>> I dug into which video driver was being used when setting >>>>>> defaultdisplay >>>>>> to lcd43 vs. dvi. >>>>>> >>>>>> Long story short, lcd43 uses driver "samsung_lte_panel" (which is for >>>>>> Samsung SAMSUNG_LTE430WQ) and dvi uses "generic_panel." The 4.3" >>>>>> display >>>>>> I have that I bought from Gumstix is an LG/Philips LB043WQ2. The >>>>>> Samsung >>>>>> driver sets the pixel clock to 9200. When in "dvi" mode the clock is >>>>>> at >>>>>> 42553 (according to the output of fbset). >>>>>> >>>>>> I'm messing around to get the right timing settings for fbset to >>>>>> output >>>>>> the full resolution to my display to see if it is indeed just the LCD >>>>>> driver used. It seems strange to me that this would be the cause of >>>>>> the >>>>>> slow touchscreen response, but I'm not terribly familiar with the way >>>>>> things happen in the kernel. >>>>>> >>>>>> Brent >>>>>> >>>>>> -----Original Message----- >>>>>> From: Ash Charles [mailto:ash...@gm...] >>>>>> Sent: Friday, January 28, 2011 12:33 PM >>>>>> To: General mailing list for gumstix users. >>>>>> Subject: Re: [Gumstix-users] LCD touch screen unusable on >>>>>> Overo/Chestnut >>>>>> >>>>>> Hi, >>>>>> >>>>>> I haven't seen this behaviour but these symptoms seemed bizarre and >>>>>> got me wondering. >>>>>> >>>>>> I'm just thinking aloud here: >>>>>> * is this a hardware or a software issue? If it is a hardware issue >>>>>> due to noise or settling time, is there a software workaround just by >>>>>> running at a different clock rate? >>>>>> * the driver for the touchscreen is found in >>>>>> drivers/input/touchscreen/ads7846.c and there is a TS_POLL_PERIOD >>>>>> parameter that, by varying, might show whether this is a software >>>>>> resource contention issue. >>>>>> * notably, the touchscreen driver uses the input subsystem, the spi >>>>>> bus, interrupts, and a high-resolution timer. Based on the symptoms, >>>>>> there is no resource contention in the input subsystem (USB is fine). >>>>>> Interrupts? >>>>>> * app note sbaa036 explains the possible electrical interference >>>>>> problems due to LCD backlight circuits. The backlight circuit and the >>>>>> ADS chip are physically distant in the board layout for the Chestnut43 >>>>>> and some of the interference reduction recommendations are followed >>>>>> but perhaps more filtering is required. >>>>>> * do changing the ads7846_config parameters in arch/arm/board_overo.c >>>>>> have any effect? >>>>>> * does changing the PWM signal supplied to the LCD backlight change >>>>>> the performance of the touchscreen. This is possible using Scott >>>>>> Ellis's PWM module (https://github.com/scottellis/omap3-pwm) >>>>>> >>>>>> -Ash >>>>>> >>>>>> On Fri, Jan 28, 2011 at 8:26 AM, BrentP <bre...@ic...> >>>>>> wrote: >>>>>>> >>>>>>> If I set the defaultdisplay to dvi in u-boot, i consistent see fast >>>>>>> results >>>>>>> from the output of ts_print almost 100 samples per second). If I set >>>>>>> the >>>>>>> defaultdisplay to lcd43 the output is closer to 5 samples per second >>>>>>> on >>>>>>> average. >>>>>>> >>>>>>> I don't know why there is this interaction and I have no idea how to >>>>>>> fix >>>>>>> it. >>>>>>> >>>>>>> Have you had any breakthroughs, Derek? >>>>>>> >>>>>>> >>>>>>> >>>>>>> BrentP wrote: >>>>>>>> >>>>>>>> I'm having precisely the same issue. I've seen it on prebuilt images >>>>>>>> and >>>>>>>> ones I've bitbaked. Right now I'm running the omap3-console-image >>>>>>>> which >>>>>>>> boots to a login prompt to the LCD. >>>>>>>> >>>>>>>> I noticed a clue this morning. When the local console blanks (the >>>>>>>> LCD) >>>>>>>> I >>>>>>>> notice that the output from ts_test is *much* faster, as low as 5 ms >>>>>>>> between samples (the poll rate to the ADS7846). If the console is >>>>>>>> not >>>>>>>> blanked, and I use ts_test to test the touchscreen, the time between >>>>>>>> samples is slow, up to 500ms between samples. >>>>>>>> >>>>>>>> If I use a USB mouse as input, the motion is very smooth in both X >>>>>>>> Windows >>>>>>>> and a Qt Embedded app. >>>>>>>> >>>>>>>> There seems to be some interaction between drawing to the >>>>>>>> framebuffer >>>>>>>> and >>>>>>>> the touchscreen driver. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Derek Baum wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> We have several gumstix overo with chestnut expansion board and LCD >>>>>>>>> touch >>>>>>>>> screen. >>>>>>>>> >>>>>>>>> They boot OK and display the default desktop, but the touch screen >>>>>>>>> is >>>>>>>>> virtually unusable. >>>>>>>>> >>>>>>>>> It is even a challenge to run the calibration utility (forced by >>>>>>>>> removing >>>>>>>>> /etc/pointercal). I had to resort to using one of the gumstix >>>>>>>>> aerials >>>>>>>>> as >>>>>>>>> a >>>>>>>>> stylus, as the touch screen would not accept any of my finger >>>>>>>>> presses. >>>>>>>>> >>>>>>>>> We are using a pre-built image from October 2010: >>>>>>>>> >>>>>>>>> $ uname -a >>>>>>>>> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l >>>>>>>>> GNU/Linux >>>>>>>>> >>>>>>>>> >>>>>>>>> Overo # printenv >>>>>>>>> dvimode=1024x768MR-16@60 >>>>>>>>> defaultdisplay=lcd43 >>>>>>>>> >>>>>>>>> How can I fix this? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> Derek >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD >>>>>>>>> value)! >>>>>>>>> Finally, a world-class log management solution at an even better >>>>>>>>> price-free! >>>>>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>>>>> _______________________________________________ >>>>>>>>> gumstix-users mailing list >>>>>>>>> gum...@li... >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> View this message in context: >>>>>>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html >>>>>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>>>> Finally, a world-class log management solution at an even better >>>>>>> price-free! >>>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>>> _______________________________________________ >>>>>>> gumstix-users mailing list >>>>>>> gum...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>>> Finally, a world-class log management solution at an even better >>>>>> price-free! >>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>> _______________________________________________ >>>>>> gumstix-users mailing list >>>>>> gum...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>> ------------------------------------------------------------------------------ >>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>>> Finally, a world-class log management solution at an even better >>>>>> price-free! >>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>> _______________________________________________ >>>>>> gumstix-users mailing list >>>>>> gum...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>> >>>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30796698.html >>>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>> Finally, a world-class log management solution at an even better >>>>> price-free! >>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>> Finally, a world-class log management solution at an even better >>>> price-free! >>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>> February 28th, so secure your free ArcSight Logger TODAY! >>>> http://p.sf.net/sfu/arcsight-sfd2d >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31908184.html >>> Sent from the Gumstix mailing list archive at Nabble.com. >>> >>> >>> ------------------------------------------------------------------------------ >>> Simplify data backup and recovery for your virtual environment with >>> vRanger. >>> Installation's a snap, and flexible recovery options mean your data is >>> safe, >>> secure and there when you need it. Data protection magic? >>> Nope - It's vRanger. Get your free trial download today. >>> http://p.sf.net/sfu/quest-sfdev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> Simplify data backup and recovery for your virtual environment with >> vRanger. >> Installation's a snap, and flexible recovery options mean your data is >> safe, >> secure and there when you need it. Data protection magic? >> Nope - It's vRanger. Get your free trial download today. >> http://p.sf.net/sfu/quest-sfdev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- > View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31916123.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense.. > http://p.sf.net/sfu/splunk-d2d-c1 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: JamesAng <ang...@gm...> - 2011-06-29 09:57:26
|
Ash Charles-2 wrote: > > Hi James, > For my suggestion to change the version of Xorg, you should just be > able to opkg a different version. Here is some documentation on the > opkg command: http://gumstix.org/add-software-packages.html. > Hi Ash, I tried using opkg to update the Xorg in Gumstix but the "opkg list_installed" and "opkg list" has both the same version of xserver-xorg - 2:1.9.4-r19.0.9 Search Angstrom-Distribution Package Feed at http://www.angstrom-distribution.org/repo/ http://www.angstrom-distribution.org/repo/ shows only 1.3.0.0-r4 So, what are the commands that I need to execute in Gumstix to change the installed Xorg and from which source? Thks in adv. James. -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31953333.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: JamesAng <ang...@gm...> - 2011-06-28 06:09:31
|
Hi Ash, 1) For the touchscreen sluggish issue, I intend to use the frequency hack for the moment as discussed in the thread by BrentP while I hope a permanent solution will be found in the coming stable release image. Thus, I wish to know where I should edit the source file so that bitbake will pickup the modified source file and rebuild the image with the new frequency. Or, can I duplicate the LCD panel driver files, create a new one for LG LB043WQ2 (alpha) where it can be selected to be used when building the kernel via the build configuration file? 2) For changing Xorg, can it be done by defining the preferred version to use in the bitbake recipe? If yes, where should I start or edit? 3) I'm connecting the J5 ISP port to another image sensor which uses UART for command & control. I've to use a NXP SC16IS750 I2C/SPI-UART chip to bridge the I2C signal from J5 to the NXP SC16IS750 chip to add a UART. This NXP chip has both a UART and GPIO ports. Is the driver to utilize this chip available in the kernel tree? If not, I would be happy to work on this driver with guidance from you & the community. :-) I'm inexperience and thus a lot of questions. =^D But being a newbie allows me to contribute with a "Get Start for Newbie" like me in the future. B-) Thks in adv. James. Ash Charles-2 wrote: > > Hi James, > > For my suggestion to change the version of Xorg, you should just be > able to opkg a different version. Here is some documentation on the > opkg command: http://gumstix.org/add-software-packages.html. > > Editing the source for various packages in OE is a trickier > proposition as OE recipes use different mechanisms to fetch and build > source. For recipes that just use source code in your recipes folder, > you can simple edit and re-bitbake. Most recipes are fetched from > source control or tarballs so editing the source so it is picked up by > bitbake would mean changing something upstream. Again, there are > workarounds but it requires a knowledge of bitbake. There is some > basic documentation here: > http://gumstix.org/software-development/open-embedded.html. > However, if you post back about what specific source code you wish to > change, the community will likely have some good suggestion on how > best to handle that particular case. > > Vague answer---sorry---it is just a lot to explain in one go! > > -Ash > > > > On Thu, Jun 23, 2011 at 6:38 PM, JamesAng <ang...@gm...> wrote: >> >> Hi Ash, >> >> Thanks for the suggestion for my 2 issues. >> >> As I'm a newbie to Linux world thus I follows closely the wiki guides to >> setup my development machine on Ubuntu 10.04 LTS ( >> http://www.gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html >> http://www.gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html >> ) and appreciate all the help that I can get from the community. >> >> I understand that I've to make changes to the source files to overcome >> some >> of the issues I encountered with the touchscreen. But, I don't know >> where >> are the source files located in my development machine to make the >> changes >> so that it will be pickup and compile using the 'bitbake >> omap3-desktop-nand-image' command. >> >> The following are the directories in my overo-oe folder: >> bitbake >> org.openembedded.dev >> build >> sources >> tmp >> >> Can you tell me where I should modify these driver's files so that it can >> be >> bitbake? >> or did I missed cloning some source's repository? >> >> Thks a million in adv. :) >> >> James. >> >> >> >> Ash Charles-2 wrote: >>> >>> Hi James, >>> >>> You've mentioned two issues: >>> - vertical flip of display: this seems to be an issue in the April15th >>> image. We are looking in to a fix but for the time being, switching >>> to a different image or changing the version of Xorg would be my >>> suggestion. >>> - low touchscreen sensitivity. As discussed in this thread, there are >>> several software work-arounds all of which effectively change the >>> frequency of the LCD clock. Sorry I don't have more details here but >>> this particular problem seems real but is hard to replicate. >>> >>> Thanks for providing the details about the inductor---this helps us >>> isolate any hardware issues. >>> >>> -Ash >>> On Wed, Jun 22, 2011 at 6:48 PM, JamesAng <ang...@gm...> wrote: >>>> >>>> Hi Ash, >>>> >>>> I'm using the Chestnut board & I experience the same issue. >>>> >>>> For the L2 inductor on my board, it's a 3mm(W)x4mm(L)x~2mm(H) black box >>>> with >>>> no surface-marking. >>>> The surrounding of the inductor is concaved. >>>> >>>> My board is PCB30005-R2467 & bought recently about a month ago. >>>> >>>> Please advise. >>>> >>>> Thanks in adv. >>>> >>>> James. >>>> >>>> >>>> Ash Charles-2 wrote: >>>>> >>>>> Hi Brent, >>>>> >>>>> Thanks for the update. I wonder that you are seeing electrical >>>>> interference between the backlight circuitry and the touchscreen ADC >>>>> sampling---this sounds increasingly like a hardware issue. >>>>> >>>>> Can you take a photo or describe inductor L2 on the Chestnut board? As >>>>> noted here >>>>> (http://pubs.gumstix.com/boards/CHESTNUT/PCB30005-2467/Readme.txt), >>>>> the part has been changed so I'd like to determine which you have. >>>>> >>>>> -Ash >>>>> >>>>> On Sat, Jan 29, 2011 at 1:03 PM, BrentP <bre...@ic...> >>>>> wrote: >>>>>> >>>>>> I confirmed yesterday that my touchscreen responsiveness was directly >>>>>> related >>>>>> to the pixel clock setting of the LCD. I still don't understand why, >>>>>> but >>>>>> if >>>>>> I set the pixel clock to 9.6MHz (the nominal clock in the datasheet >>>>>> of >>>>>> the >>>>>> LCD), the touchscreen response was sluggish. As I increased it, it >>>>>> became >>>>>> better and better. I currently have it set to 15Mhz which is the top >>>>>> end >>>>>> spec'd in the datasheet. I had it as higha s 23.5MHz and everything >>>>>> was >>>>>> still working well. >>>>>> >>>>>> Any clues as to why the pixel clock on the LCD would effect things >>>>>> like >>>>>> this? >>>>>> >>>>>> Brent >>>>>> >>>>>> >>>>>> >>>>>> BrentP wrote: >>>>>>> >>>>>>> The fact that setting defaultdisplay to dvi was a clue and got me to >>>>>>> looking closer. If I set to dvi and use fbset to set the >>>>>>> resolution >>>>>>> to >>>>>>> 480x272, I get output to the lcd that is mostly correct - there is a >>>>>>> white >>>>>>> stripe on the right hand side, but otherwise the video looks >>>>>>> correct. >>>>>>> In >>>>>>> this mode, running ts_test works as expected. The touchscreen is >>>>>>> very >>>>>>> responsive. >>>>>>> >>>>>>> I dug into which video driver was being used when setting >>>>>>> defaultdisplay >>>>>>> to lcd43 vs. dvi. >>>>>>> >>>>>>> Long story short, lcd43 uses driver "samsung_lte_panel" (which is >>>>>>> for >>>>>>> Samsung SAMSUNG_LTE430WQ) and dvi uses "generic_panel." The 4.3" >>>>>>> display >>>>>>> I have that I bought from Gumstix is an LG/Philips LB043WQ2. The >>>>>>> Samsung >>>>>>> driver sets the pixel clock to 9200. When in "dvi" mode the clock >>>>>>> is >>>>>>> at >>>>>>> 42553 (according to the output of fbset). >>>>>>> >>>>>>> I'm messing around to get the right timing settings for fbset to >>>>>>> output >>>>>>> the full resolution to my display to see if it is indeed just the >>>>>>> LCD >>>>>>> driver used. It seems strange to me that this would be the cause of >>>>>>> the >>>>>>> slow touchscreen response, but I'm not terribly familiar with the >>>>>>> way >>>>>>> things happen in the kernel. >>>>>>> >>>>>>> Brent >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Ash Charles [mailto:ash...@gm...] >>>>>>> Sent: Friday, January 28, 2011 12:33 PM >>>>>>> To: General mailing list for gumstix users. >>>>>>> Subject: Re: [Gumstix-users] LCD touch screen unusable on >>>>>>> Overo/Chestnut >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I haven't seen this behaviour but these symptoms seemed bizarre and >>>>>>> got me wondering. >>>>>>> >>>>>>> I'm just thinking aloud here: >>>>>>> * is this a hardware or a software issue? If it is a hardware issue >>>>>>> due to noise or settling time, is there a software workaround just >>>>>>> by >>>>>>> running at a different clock rate? >>>>>>> * the driver for the touchscreen is found in >>>>>>> drivers/input/touchscreen/ads7846.c and there is a TS_POLL_PERIOD >>>>>>> parameter that, by varying, might show whether this is a software >>>>>>> resource contention issue. >>>>>>> * notably, the touchscreen driver uses the input subsystem, the spi >>>>>>> bus, interrupts, and a high-resolution timer. Based on the >>>>>>> symptoms, >>>>>>> there is no resource contention in the input subsystem (USB is >>>>>>> fine). >>>>>>> Interrupts? >>>>>>> * app note sbaa036 explains the possible electrical interference >>>>>>> problems due to LCD backlight circuits. The backlight circuit and >>>>>>> the >>>>>>> ADS chip are physically distant in the board layout for the >>>>>>> Chestnut43 >>>>>>> and some of the interference reduction recommendations are followed >>>>>>> but perhaps more filtering is required. >>>>>>> * do changing the ads7846_config parameters in >>>>>>> arch/arm/board_overo.c >>>>>>> have any effect? >>>>>>> * does changing the PWM signal supplied to the LCD backlight change >>>>>>> the performance of the touchscreen. This is possible using Scott >>>>>>> Ellis's PWM module (https://github.com/scottellis/omap3-pwm) >>>>>>> >>>>>>> -Ash >>>>>>> >>>>>>> On Fri, Jan 28, 2011 at 8:26 AM, BrentP <bre...@ic...> >>>>>>> wrote: >>>>>>>> >>>>>>>> If I set the defaultdisplay to dvi in u-boot, i consistent see fast >>>>>>>> results >>>>>>>> from the output of ts_print almost 100 samples per second). If I >>>>>>>> set >>>>>>>> the >>>>>>>> defaultdisplay to lcd43 the output is closer to 5 samples per >>>>>>>> second >>>>>>>> on >>>>>>>> average. >>>>>>>> >>>>>>>> I don't know why there is this interaction and I have no idea how >>>>>>>> to >>>>>>>> fix >>>>>>>> it. >>>>>>>> >>>>>>>> Have you had any breakthroughs, Derek? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> BrentP wrote: >>>>>>>>> >>>>>>>>> I'm having precisely the same issue. I've seen it on prebuilt >>>>>>>>> images >>>>>>>>> and >>>>>>>>> ones I've bitbaked. Right now I'm running the omap3-console-image >>>>>>>>> which >>>>>>>>> boots to a login prompt to the LCD. >>>>>>>>> >>>>>>>>> I noticed a clue this morning. When the local console blanks (the >>>>>>>>> LCD) >>>>>>>>> I >>>>>>>>> notice that the output from ts_test is *much* faster, as low as 5 >>>>>>>>> ms >>>>>>>>> between samples (the poll rate to the ADS7846). If the console is >>>>>>>>> not >>>>>>>>> blanked, and I use ts_test to test the touchscreen, the time >>>>>>>>> between >>>>>>>>> samples is slow, up to 500ms between samples. >>>>>>>>> >>>>>>>>> If I use a USB mouse as input, the motion is very smooth in both X >>>>>>>>> Windows >>>>>>>>> and a Qt Embedded app. >>>>>>>>> >>>>>>>>> There seems to be some interaction between drawing to the >>>>>>>>> framebuffer >>>>>>>>> and >>>>>>>>> the touchscreen driver. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Derek Baum wrote: >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> We have several gumstix overo with chestnut expansion board and >>>>>>>>>> LCD >>>>>>>>>> touch >>>>>>>>>> screen. >>>>>>>>>> >>>>>>>>>> They boot OK and display the default desktop, but the touch >>>>>>>>>> screen >>>>>>>>>> is >>>>>>>>>> virtually unusable. >>>>>>>>>> >>>>>>>>>> It is even a challenge to run the calibration utility (forced by >>>>>>>>>> removing >>>>>>>>>> /etc/pointercal). I had to resort to using one of the gumstix >>>>>>>>>> aerials >>>>>>>>>> as >>>>>>>>>> a >>>>>>>>>> stylus, as the touch screen would not accept any of my finger >>>>>>>>>> presses. >>>>>>>>>> >>>>>>>>>> We are using a pre-built image from October 2010: >>>>>>>>>> >>>>>>>>>> $ uname -a >>>>>>>>>> Linux gumstix1 2.6.34 #1 Wed Oct 13 12:00:38 PDT 2010 armv7l >>>>>>>>>> GNU/Linux >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Overo # printenv >>>>>>>>>> dvimode=1024x768MR-16@60 >>>>>>>>>> defaultdisplay=lcd43 >>>>>>>>>> >>>>>>>>>> How can I fix this? >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> >>>>>>>>>> Derek >>>>>>>>>> >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD >>>>>>>>>> value)! >>>>>>>>>> Finally, a world-class log management solution at an even better >>>>>>>>>> price-free! >>>>>>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>>>>>> _______________________________________________ >>>>>>>>>> gumstix-users mailing list >>>>>>>>>> gum...@li... >>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> View this message in context: >>>>>>>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30788570.html >>>>>>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD >>>>>>>> value)! >>>>>>>> Finally, a world-class log management solution at an even better >>>>>>>> price-free! >>>>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>>>> _______________________________________________ >>>>>>>> gumstix-users mailing list >>>>>>>> gum...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>>>> Finally, a world-class log management solution at an even better >>>>>>> price-free! >>>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>>> _______________________________________________ >>>>>>> gumstix-users mailing list >>>>>>> gum...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>> ------------------------------------------------------------------------------ >>>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>>>> Finally, a world-class log management solution at an even better >>>>>>> price-free! >>>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>>> _______________________________________________ >>>>>>> gumstix-users mailing list >>>>>>> gum...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p30796698.html >>>>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>>> Finally, a world-class log management solution at an even better >>>>>> price-free! >>>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>>> _______________________________________________ >>>>>> gumstix-users mailing list >>>>>> gum...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>>>> Finally, a world-class log management solution at an even better >>>>> price-free! >>>>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>>>> February 28th, so secure your free ArcSight Logger TODAY! >>>>> http://p.sf.net/sfu/arcsight-sfd2d >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31908184.html >>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Simplify data backup and recovery for your virtual environment with >>>> vRanger. >>>> Installation's a snap, and flexible recovery options mean your data is >>>> safe, >>>> secure and there when you need it. Data protection magic? >>>> Nope - It's vRanger. Get your free trial download today. >>>> http://p.sf.net/sfu/quest-sfdev2dev >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>> >>> ------------------------------------------------------------------------------ >>> Simplify data backup and recovery for your virtual environment with >>> vRanger. >>> Installation's a snap, and flexible recovery options mean your data is >>> safe, >>> secure and there when you need it. Data protection magic? >>> Nope - It's vRanger. Get your free trial download today. >>> http://p.sf.net/sfu/quest-sfdev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31916123.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense.. >> http://p.sf.net/sfu/splunk-d2d-c1 >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense.. > http://p.sf.net/sfu/splunk-d2d-c1 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31943611.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2011-06-28 17:46:05
|
Hi, On Mon, Jun 27, 2011 at 11:09 PM, JamesAng <ang...@gm...> wrote: > Thus, I wish to know where I should edit the source file so that bitbake > will pickup the modified source file and rebuild the image with the new > frequency. I'm guessing that Brent edited the LCD screen driver in the linux kernel. This would be <kernel>/drivers/video/omap2/displays/panel-generic-dpi.c. Scott Ellis has put some great documentation on how to edit the kernel for Gumstix here: http://www.jumpnowtek.com/index.php?option=com_content&view=article&id=46&Itemid=54 (thanks again Scott!). > > Or, can I duplicate the LCD panel driver files, create a new one for LG > LB043WQ2 (alpha) where it can be selected to be used when building the > kernel via the build configuration file? > > 2) For changing Xorg, can it be done by defining the preferred version to > use in the bitbake recipe? If yes, where should I start or edit? Yes---you can modify the PREFERRED_VERSION in the conf files for OE. I recommend the OE manual if you decide to take this route. I'd try to use opkg first to confirm the fix though. > > 3) I'm connecting the J5 ISP port to another image sensor which uses UART > for command & control. I've to use a NXP SC16IS750 I2C/SPI-UART chip to > bridge the I2C signal from J5 to the NXP SC16IS750 chip to add a UART. This > NXP chip has both a UART and GPIO ports. Is the driver to utilize this chip > available in the kernel tree? If not, I would be happy to work on this > driver with guidance from you & the community. :-) A separate thread might be good here. Grepping the kernel sources/searching online may also give a better idea of the state of any current support for this chip in the kernel---there is a chance that someone has worked on it even if it is not supported in the mainline kernel. > > I'm inexperience and thus a lot of questions. =^D > But being a newbie allows me to contribute with a "Get Start for Newbie" > like me in the future. B-) Wahoo! Questions are always fair game especially if you are willing to help others get started :D. The learning curve can be a bit intimidating some times. -Ash |
From: JamesAng <ang...@gm...> - 2011-06-29 03:19:37
|
Ash Charles wrote: > > Hi, > > On Mon, Jun 27, 2011 at 11:09 PM, JamesAng <ang...@gm...> wrote: >> Thus, I wish to know where I should edit the source file so that bitbake >> will pickup the modified source file and rebuild the image with the new >> frequency. > I'm guessing that Brent edited the LCD screen driver in the linux > kernel. This would be > <kernel>/drivers/video/omap2/displays/panel-generic-dpi.c. Scott > Ellis has put some great documentation on how to edit the kernel for > Gumstix here: > http://www.jumpnowtek.com/index.php?option=com_content&view=article&id=46&Itemid=54 > (thanks again Scott!). > Noted with Thanks! I'll look closely at that document. :) I'll also pop a message to Brent to see if he can provide insight to this too. Ash Charles wrote: > >> Or, can I duplicate the LCD panel driver files, create a new one for LG >> LB043WQ2 (alpha) where it can be selected to be used when building the >> kernel via the build configuration file? > Is there a plan in the roadmap to produce a new driver specifically for this LG LB043WQ2? If not, I wouldn't mind starting this in its own thread. Ash Charles wrote: > >> 2) For changing Xorg, can it be done by defining the preferred version to >> use in the bitbake recipe? If yes, where should I start or edit? > Yes---you can modify the PREFERRED_VERSION in the conf files for OE. > I recommend the OE manual if you decide to take this route. I'd try > to use opkg first to confirm the fix though. > For a quick start, which conf files should I place this PREFERRED_VERSION into? any short example will be very helpful. :) Ash Charles wrote: > >> >> 3) I'm connecting the J5 ISP port to another image sensor which uses UART >> for command & control. I've to use a NXP SC16IS750 I2C/SPI-UART chip to >> bridge the I2C signal from J5 to the NXP SC16IS750 chip to add a UART. >> This >> NXP chip has both a UART and GPIO ports. Is the driver to utilize this >> chip >> available in the kernel tree? If not, I would be happy to work on this >> driver with guidance from you & the community. :-) > A separate thread might be good here. Grepping the kernel > sources/searching online may also give a better idea of the state of > any current support for this chip in the kernel---there is a chance > that someone has worked on it even if it is not supported in the > mainline kernel. > Noted. I'll start a separate thread so that all can contribute to it and serves as a guide/tutorial for future developers. :) Ash Charles wrote: > >> I'm inexperience and thus a lot of questions. =^D >> But being a newbie allows me to contribute with a "Get Start for Newbie" >> like me in the future. B-) > Wahoo! Questions are always fair game especially if you are willing > to help others get started :D. The learning curve can be a bit > intimidating some times. > > -Ash > Yes, the learning curve is very steep and intimidating at some time. But, no pain no gain. :) -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31951645.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: JamesAng <ang...@gm...> - 2011-06-29 08:20:09
|
BrentP wrote: > > I confirmed yesterday that my touchscreen responsiveness was directly > related to the pixel clock setting of the LCD. I still don't understand > why, but if I set the pixel clock to 9.6MHz (the nominal clock in the > datasheet of the LCD), the touchscreen response was sluggish. As I > increased it, it became better and better. I currently have it set to > 15Mhz which is the top end spec'd in the datasheet. I had it as higha s > 23.5MHz and everything was still working well. > > Any clues as to why the pixel clock on the LCD would effect things like > this? > > Brent > Hi Brent, I'm also experiencing the same sluggish of the touchscreen on my Chestnut and LG LCD screen. Can you share with the community the exact steps to change the frequency of the pixel clock and how to have bitbake uses the modified file when compiling. Many Thanks in adv. James. -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31952736.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: BrentP <bre...@ic...> - 2011-06-29 13:20:08
|
James: I didn't actually get as far as modifying the driver just yet. I had to put my Gumstix project on the back burner soon after posting this, but I should be getting back to it soon. I can dig up some more details in a bit, but basically, I believe I set "defaultdisplay=dvi" in U-Boot which then uses the generic LCD driver. I then used a combination of "fbset" and echo'ing timings to "/sys/devices/omapdss/display0/timings" According to my notes I did: echo "15000,480/1/15/14,272/1/45/33" > /sys/devices/omapdss/display0/timings I'd have to go back and try that again to make sure that's exactly what did it, but that was the path I was on. I'll try to post something more detailed later, but maybe this can get you going in the right direction. Ultimately, we need to patch the driver as a workaround until the hardware issue is solved. Brent JamesAng wrote: > > > BrentP wrote: >> >> I confirmed yesterday that my touchscreen responsiveness was directly >> related to the pixel clock setting of the LCD. I still don't understand >> why, but if I set the pixel clock to 9.6MHz (the nominal clock in the >> datasheet of the LCD), the touchscreen response was sluggish. As I >> increased it, it became better and better. I currently have it set to >> 15Mhz which is the top end spec'd in the datasheet. I had it as higha s >> 23.5MHz and everything was still working well. >> >> Any clues as to why the pixel clock on the LCD would effect things like >> this? >> >> Brent >> > > Hi Brent, > > I'm also experiencing the same sluggish of the touchscreen on my Chestnut > and LG LCD screen. > > Can you share with the community the exact steps to change the frequency > of the pixel clock and how to have bitbake uses the modified file when > compiling. > > Many Thanks in adv. > > James. > -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31954690.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: JamesAng <ang...@gm...> - 2011-06-30 02:29:48
|
BrentP wrote: > > James: > > I didn't actually get as far as modifying the driver just yet. I had to > put my Gumstix project on the back burner soon after posting this, but I > should be getting back to it soon. > > I can dig up some more details in a bit, but basically, I believe I set > "defaultdisplay=dvi" in U-Boot which then uses the generic LCD driver. I > then used a combination of "fbset" and echo'ing timings to > "/sys/devices/omapdss/display0/timings" > > According to my notes I did: > > echo "15000,480/1/15/14,272/1/45/33" > > /sys/devices/omapdss/display0/timings > > I'd have to go back and try that again to make sure that's exactly what > did it, but that was the path I was on. > > I'll try to post something more detailed later, but maybe this can get you > going in the right direction. Ultimately, we need to patch the driver as > a workaround until the hardware issue is solved. > > > Brent > Hi Brent, Understood. :) But your investigation into the timing issue do help to narrow the search for a permanent solution. I look forward to more details that you can provide so that I can also try to solve it at my end over here. Cheers~! James. -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p31959768.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: dcraw101 <dcr...@ya...> - 2011-09-19 21:34:00
|
JamesAng wrote: > > > BrentP wrote: >> >> James: >> >> I didn't actually get as far as modifying the driver just yet. I had to >> put my Gumstix project on the back burner soon after posting this, but I >> should be getting back to it soon. >> >> I can dig up some more details in a bit, but basically, I believe I set >> "defaultdisplay=dvi" in U-Boot which then uses the generic LCD driver. I >> then used a combination of "fbset" and echo'ing timings to >> "/sys/devices/omapdss/display0/timings" >> >> According to my notes I did: >> >> echo "15000,480/1/15/14,272/1/45/33" > >> /sys/devices/omapdss/display0/timings >> >> I'd have to go back and try that again to make sure that's exactly what >> did it, but that was the path I was on. >> >> I'll try to post something more detailed later, but maybe this can get >> you going in the right direction. Ultimately, we need to patch the >> driver as a workaround until the hardware issue is solved. >> >> >> Brent >> > > Hi Brent, > > Understood. :) > But your investigation into the timing issue do help to narrow the search > for a permanent solution. > > I look forward to more details that you can provide so that I can also try > to solve it at my end over here. > > Cheers~! > > James. > > I am trying to connect the Chestnut to a an AUO 5.7" LCD. If I set the pixel clock to 25 MHz (as per the AUO datasheet) then the touch panel is very erratic and updates very slowly. if I change the pixel clock down to 10MHz then the touch panel is much more responsive, but now my LCD is refreshing too slow. Could this be an electical interferrence or cross-talk issue? Could it help to lower the speed of the SPI bus communicating with the ADS7846? thanks, Doug -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p32498692.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: JamesAng <ang...@gm...> - 2011-09-21 02:17:15
|
Hi Doug, dcraw101 wrote: > > > > JamesAng wrote: >> >> >> BrentP wrote: >>> >>> James: >>> >>> I didn't actually get as far as modifying the driver just yet. I had to >>> put my Gumstix project on the back burner soon after posting this, but I >>> should be getting back to it soon. >>> >>> I can dig up some more details in a bit, but basically, I believe I set >>> "defaultdisplay=dvi" in U-Boot which then uses the generic LCD driver. >>> I then used a combination of "fbset" and echo'ing timings to >>> "/sys/devices/omapdss/display0/timings" >>> >>> According to my notes I did: >>> >>> echo "15000,480/1/15/14,272/1/45/33" > >>> /sys/devices/omapdss/display0/timings >>> >>> I'd have to go back and try that again to make sure that's exactly what >>> did it, but that was the path I was on. >>> >>> I'll try to post something more detailed later, but maybe this can get >>> you going in the right direction. Ultimately, we need to patch the >>> driver as a workaround until the hardware issue is solved. >>> >>> >>> Brent >>> >> >> Hi Brent, >> >> Understood. :) >> But your investigation into the timing issue do help to narrow the search >> for a permanent solution. >> >> I look forward to more details that you can provide so that I can also >> try to solve it at my end over here. >> >> Cheers~! >> >> James. >> >> > > I am trying to connect the Chestnut to a an AUO 5.7" LCD. If I set the > pixel clock to 25 MHz (as per the AUO datasheet) then the touch panel is > very erratic and updates very slowly. if I change the pixel clock down to > 10MHz then the touch panel is much more responsive, but now my LCD is > refreshing too slow. Could this be an electical interferrence or > cross-talk issue? Could it help to lower the speed of the SPI bus > communicating with the ADS7846? > > thanks, > Doug > ATM, I've put this at a lower priority. Have you tried to see if the response between "ts_test"'s draw and that on the GUI is vastly different? For mine without any modification, ts_test give a good response time but sluggish when on the GUI.. But why??.. -- View this message in context: http://old.nabble.com/LCD-touch-screen-unusable-on-Overo-Chestnut-tp30728009p32503706.html Sent from the Gumstix mailing list archive at Nabble.com. |