From: Charles W. <cha...@ha...> - 2009-11-07 16:22:31
Attachments:
IMG_0215.jpg
|
Just received the overo with a chestnut and LCD panel. Booted fine, but the LCD image looks offset. All I see if a white screen with a small green image in one corner. Does anyone know what I should expect or how to get this to work better? Thanks, Charlie |
From: Richard B. <rl...@gm...> - 2009-11-07 18:23:10
|
I am in the same situation and was wondering the same thing. On Sat, Nov 7, 2009 at 12:22 PM, Charles Woloszynski <cha...@ha...> wrote: > Just received the overo with a chestnut and LCD panel. Booted fine, but the > LCD image looks offset. All I see if a white screen with a small green > image in one corner. > > Does anyone know what I should expect or how to get this to work better? > > Thanks, > > Charlie > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Elvis D. <elv...@ma...> - 2009-11-07 18:42:22
|
Honestly, coming to think of it, Gumstix should spend more effort documenting stuff, a lot of new users end up facing the same type of problems, and consequently end up wasting days and weeks due to lack of detailed product documentation, ranging from the simple to the more complex type of stuff like working with GPIOs, muxing the GPIOs or using the ADCs. |
From: Jim D. <jd...@wh...> - 2009-11-07 20:59:10
|
I'll SECOND the need to document e.g. use of GPIO's & timers, especially with bitbake!! Elvis Dowson wrote: > Honestly, coming to think of it, Gumstix should spend more effort > documenting stuff, a lot of new users end up facing the same type of > problems, and consequently end up wasting days and weeks due to lack > of detailed product documentation, ranging from the simple to the more > complex type of stuff like working with GPIOs, muxing the GPIOs or > using the ADCs. > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Elvis D. <elv...@ma...> - 2009-11-07 18:39:38
|
Hi, On Nov 7, 2009, at 10:22 PM, Richard Boyd wrote: > >> Just received the overo with a chestnut and LCD panel. Booted >> fine, but the >> LCD image looks offset. All I see if a white screen with a small >> green >> image in one corner. You need to set the default display. For the Palo43, interrupt the boot process, print out the existing environment variables, set the default display, and save the environment # printenv # setenv defaultdisplay lcd43 # setenv dvimode 480x272MR-16@60 # saveenv Best regards, Elvis |
From: Steve S. <sa...@gm...> - 2009-11-07 23:20:08
|
On Sat, Nov 7, 2009 at 10:39 AM, Elvis Dowson <elv...@ma...> wrote: > Hi, > > On Nov 7, 2009, at 10:22 PM, Richard Boyd wrote: > > Just received the overo with a chestnut and LCD panel. Booted fine, but the > > LCD image looks offset. All I see if a white screen with a small green > > image in one corner. > > You need to set the default display. For the Palo43, interrupt the boot > process, print out the existing environment variables, set the default > display, and save the environment > # printenv > # setenv defaultdisplay lcd43 > # setenv dvimode 480x272MR-16@60 > # saveenv The dvimode change is not needed. No need to change the DVI mode when you've just set the default display to LCD! Makes less work if/when you want to change the default display back to DVI too. Steve > Best regards, > Elvis > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Charles W. <cha...@ha...> - 2009-11-07 19:27:12
|
Thanks for the info. I tried this, but now the LCD is black for the entire boot. No images at all. So, I tried to leave the defaultdisplay to dvi but used the new dvimode value. With that, I got a screen with 'Overo' on it and a progress bar. It flashes, but at least it looks like the screen is being used properly. There is an error in the boot process that may cause this issue. It does finally convert into a text screen with Angstrom image. So, I suggest that using just setenv dvimode 480x272MR-16@60 might be sufficient. The old setting was: > dvimode=1024x768MR-16@60 > defaultdisplay=dvi The new settings (per your suggestions) are: > Hit any key to stop autoboot: 0 > Overo # printenv > bootcmd=if mmc init; then if run loadbootscript; then run > bootscript; else if run loaduimage; then run mmcboot; else run > nandboot; fi; fi; else run nandboot; fi > bootdelay=5 > baudrate=115200 > loadaddr=0x82000000 > console=ttyS2,115200n8 > vram=12M > mmcargs=setenv bootargs console=${console} vram=${vram} > omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=$ > {defaultdisplay} root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait > nandargs=setenv bootargs console=${console} vram=${vram} > omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=$ > {defaultdisplay} root=/dev/mtdblock4 rw rootfstype=jffs2 > loadbootscript=fatload mmc 0 ${loadaddr} boot.scr > bootscript=echo Running bootscript from mmc ...; source ${loadaddr} > loaduimage=fatload mmc 0 ${loadaddr} uImage > mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr} > nandboot=echo Booting from nand ...; run nandargs; nand read $ > {loadaddr} 280000 400000; bootm ${loadaddr} > dieid#=1d7800040000000004035c1402015018 > defaultdisplay=lcd43 > dvimode=480x272MR-16@60 > stdin=serial > stdout=serial > stderr=serial > > Environment size: 1056/131068 bytes > Overo # On Nov 7, 2009, at 1:39 PM, Elvis Dowson wrote: > Hi, > > On Nov 7, 2009, at 10:22 PM, Richard Boyd wrote: >> >>> Just received the overo with a chestnut and LCD panel. Booted >>> fine, but the >>> LCD image looks offset. All I see if a white screen with a small >>> green >>> image in one corner. > > You need to set the default display. For the Palo43, interrupt the > boot process, print out the existing environment variables, set the > default display, and save the environment > > # printenv > # setenv defaultdisplay lcd43 > # setenv dvimode 480x272MR-16@60 > # saveenv > > Best regards, > > Elvis > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july_______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Roch M. C. <rc...@ma...> - 2009-11-07 21:35:13
|
Agreed. When you try the getting started links, they return page not found errors. Makes you wonder (as a first impression) if this is a currently active product. On 7-Nov-09, at 3:58 PM, Jim Doutt wrote: > I'll SECOND the need to document e.g. use of GPIO's & timers, > especially > with bitbake!! > > Elvis Dowson wrote: >> Honestly, coming to think of it, Gumstix should spend more effort >> documenting stuff, a lot of new users end up facing the same type of >> problems, and consequently end up wasting days and weeks due to lack >> of detailed product documentation, ranging from the simple to the >> more >> complex type of stuff like working with GPIOs, muxing the GPIOs or >> using the ADCs. >> >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports >> 2008 30-Day >> trial. Simplify your report design, integration and deployment - >> and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Don A. <do...@gu...> - 2009-11-07 21:50:22
|
Thanks for this feedback. We certainly want to keep our documentation current and useful. Also, please identify any broken links or page not found errors at www.gumstix.net that need correction. Don @ Gumstix ============== On Sat, Nov 7, 2009 at 1:34 PM, Roch M. Comeau <rc...@ma...> wrote: > Agreed. > > When you try the getting started links, they return page not found > errors. Makes you wonder (as a first impression) if this is a > currently active product. > > On 7-Nov-09, at 3:58 PM, Jim Doutt wrote: > > > I'll SECOND the need to document e.g. use of GPIO's & timers, > > especially > > with bitbake!! > > > > Elvis Dowson wrote: > >> Honestly, coming to think of it, Gumstix should spend more effort > >> documenting stuff, a lot of new users end up facing the same type of > >> problems, and consequently end up wasting days and weeks due to lack > >> of detailed product documentation, ranging from the simple to the > >> more > >> complex type of stuff like working with GPIOs, muxing the GPIOs or > >> using the ADCs. > >> > >> > >> > >> > |
From: Steve S. <sa...@gm...> - 2009-11-09 01:17:24
|
On Sat, Nov 7, 2009 at 11:26 AM, Charles Woloszynski < cha...@ha...> wrote: > Thanks for the info. I tried this, but now the LCD is black for the entire > boot. No images at all. > > So, I tried to leave the defaultdisplay to dvi but used the new dvimode > value. With that, I got a screen with 'Overo' on it and a progress bar. It > flashes, but at least it looks like the screen is being used properly. > > There is an error in the boot process that may cause this issue. It does > finally convert into a text screen with Angstrom image. > > So, I suggest that using just > > setenv dvimode 480x272MR-16@60 > > might be sufficient. > The fact that dvimode has any effect at all means that something else is wrong with your setup. Setting defaultdisplay to lcd43 should cause the display subsystem to use the driver for the 4.3" display. If everything is working right the resolution, timings, and sync polarities are fixed in the driver per the lcd spec. It seems that the kernel is ignoring the defaultdisplay setting and continuing to use the dvi driver. The mode you set "sort of" works - but trust me, the timings and sync polarities are wrong! Please reply with a copy of your boot log and we can try to figure out what is wrong with your setup. The change you made to dvimode is *not* the solution! Steve > > |
From: Charles W. <cha...@ha...> - 2009-11-09 12:39:36
|
Thanks for offering to help. After looking at this more to give you a clear picture of the uboot env and the kernel output, I found that I apparently got caught by the 'setenv x=y' issue instead of using 'setenv x y'. So, I did not actually set the defaultdisplay variable, but instead set the variable defaultdisplay=lcd43 !!! With the setenv deaultdisplay lcd43, you are right. It works and the flicker I was seeing goes away. Sorry for the red herring! Charlie On Nov 8, 2009, at 8:17 PM, Steve Sakoman wrote: > On Sat, Nov 7, 2009 at 11:26 AM, Charles Woloszynski <cha...@ha... > > wrote: > Thanks for the info. I tried this, but now the LCD is black for the > entire boot. No images at all. > > So, I tried to leave the defaultdisplay to dvi but used the new > dvimode value. With that, I got a screen with 'Overo' on it and a > progress bar. It flashes, but at least it looks like the screen is > being used properly. > > There is an error in the boot process that may cause this issue. It > does finally convert into a text screen with Angstrom image. > > So, I suggest that using just > > setenv dvimode 480x272MR-16@60 > > might be sufficient. > > The fact that dvimode has any effect at all means that something > else is wrong with your setup. > > Setting defaultdisplay to lcd43 should cause the display subsystem > to use the driver for the 4.3" display. If everything is working > right the resolution, timings, and sync polarities are fixed in the > driver per the lcd spec. > > It seems that the kernel is ignoring the defaultdisplay setting and > continuing to use the dvi driver. The mode you set "sort of" works > - but trust me, the timings and sync polarities are wrong! > > Please reply with a copy of your boot log and we can try to figure > out what is wrong with your setup. The change you made to dvimode > is *not* the solution! > > Steve > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july_______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |