From: Stefano C. [EDALab] <ste...@ed...> - 2010-10-25 16:20:52
|
Hi all, I have an Overo Fire + Chestnut43 board. Up to some time ago, I could only see a white LCD display (no desktop or other image) even when loading desktop OE images. Now I can't see anything, so my guess is: 1) the lcd backlight is broken 2) the flat connector is broken 3) the Chestnut43 is broken 4) some sw configuration is wrong. For what is concerned 1), 2) and 3), the ts_calibrate utility detects touches, so at least something should work, but it's hard to say wheter some wire in the LCD flat cable is broken or what... For what is concerned 4), this is my u-boot env: 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 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#=07fa00040000000004035c141901f017 ethact=smc911x-0 dvimode=480x272MR-16@60 anddisplay=vram=8M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=lcd43 androot=root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init andbootargs=setenv bootargs mpurate=500 ${andconsole} ${androot} ${anddisplay} andbootcmd=mmc init; fatload mmc 0 ${loadaddr} uImage; run andbootargs; bootm ${loadaddr} andconsole=console=ttyS0,115200n8 console=tty0 androidboot.console=ttyS0 defaultdisplay=lcd43 bootargs=mem=128M console=tty0 console=ttyS0,115200n8 root=/dev/mmcblk0p2 rw init=/init rootwait omap-dss.def_disp=lcd43 omapfb.video_mode=480x272MR-16@60 omapfb.debug=y omapdss.debug=y stdin=serial stdout=serial stderr=serial Don't care about and* variables, they are here because of some Android tests and should hopefully be harmless... Any idea about the problem and other ways to do thorough diagnosis? TIA, Stefano -- Stefano Cailotto --------------------------------------------------------------------------- EDALab s.r.l. - Networked Embedded Systems Sede legale e operativa: Cà Vignal 2, Strada Le Grazie, 15, 37134 Verona - Italy C.F./P.IVA/Iscr. Reg. Imprese di Verona n. 03706250234 Numero REA: VR - 358813 Capitale sociale: 10.000 euro --------------------------------------------------------------------------- email: ste...@ed... web: http://www.edalab.it skype: stefano.cailotto tel: +39-045-802-7062 fax: +39-045-802-7068 mobile: +39-348-987-5853 --------------------------------------------------------------------------- |