From: Victhor <vic...@gm...> - 2010-01-21 16:46:25
|
I have tried reflashing U-Boot, with no success. I set the defaultdisplay to lcd43. What is that GPIO command? U-Boot doesn't seem to have one. > Hopefully you hear from a few other people, because I can't claim to be > the expert especially for Overo, but it sounds like you have power to > the LCD and the back light is coming on -- otherwise it would not be > white at first. But the screen will go gray if the back light enable > bit is turned off. > > It is possible that the back light enable bit (dual purposes as PWM and > high/low in my system) is in the wrong state when the kernel starts up > somehow. If you can determine which bit it is on the schematic, then > after it boots up you can query the state via a GPIO command. There is > a gumstix How-to for this, I don't have the link right in front of me. > You can also reset the bit "manually" and see if the screen then comes on. > > > Victhor wrote: > > I have an Overo Fire and a Palo43 with the LG 4.3" LCD. Of a sudden, my > > system stopped showing the splash screen. It still boots normally, > > however. The screen is white when power is applied, but when the splash > > screen was supposed to show up, a gray screen comes up instead. Xorg > > starts but the screen is still gray. > > This is the output of 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 > > dvimode=1024x768MR-16@60 > > mmcroot=/dev/mmcblk0p2 rw > > mmcrootfstype=ext3 rootwait > > nandroot=/dev/mtdblock4 rw > > nandrootfstype=jffs2 > > mmcargs=setenv bootargs console=${console} vram=${vram} omapfb.mode=dvi: > > ${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} root= > > ${mmcroot} rootfstype=${mmcrootfstype} > > nandargs=setenv bootargs console=${console} vram=${vram} > > omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp= > > ${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype} > > 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#=44a800040000000004035c141700c01c > > vram=16M > > defaultdisplay=lcd43 > > stdin=serial > > stdout=serial > > stderr=serial > > > > Environment size: 1161/131068 bytes > > > > > > ------------------------------------------------------------------------------ > > Throughout its 18-year history, RSA Conference consistently attracts the > > world's best and brightest in the field, creating opportunities for Conference > > attendees to learn about information security's most important issues through > > interactions with peers, luminaries and emerging and established companies. > > http://p.sf.net/sfu/rsaconf-dev2dev > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |