Re: [Gumstix-users] Palo43 LCD Issue

[Stephen H. <sh...@si...>]

Yes, I am using the factory image.  The weird thing to me is, previously, I
was able to see that the LCD was at least getting power because I could see
the backlighting coming on.  However, I then realized that the Overo Fire
was not fully seated, yet it was still running.  Once I got the Fire fully
seated, I plugged the USB into the console and booted into hyperterminal,
set the default display and tried again.  That is when there was no sign of
life on the LCD.  Is there any way to test for a bad LCD?  I really don't
understand why the factory image wouldn't work.  The how to video posted on
the site does not say anything about doing an initial build.



Edgardo Cruz wrote:
> 
> Are you using the factory installed linux image?  If you are, try 
> installing either the palmtop or desktop images to an SD card.   I do 
> not know if the factory installed image is supposed to support the LCD 
> display or not, but my Palo35 had similar symptoms to the ones you 
> describe.  It works fine now with either of these images running off a 
> microSD card.
> 
> You can find links to the images and instructions here:
> <http://gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/index.php?option=com_easyfaq&task=view&id=125&Itemid=111>
> 
> 
> 
> 
> 
> On 11/15/2009 10:39 PM, Stephen Haile wrote:
>> I am trying to run an Overo Fire with a Palo43 and a 4.3" LCD.  I
>> followed
>> the instructions on how to set up the defaultdisplay for the LCD but an
>> still seeing a blank screen.  Previously, I could see that the LCD was
>> powering up when I plugged in the power, but now it does absoluetely
>> nothing.  This is the beginging of the boot process pasted out of
>> hyperterminal.  Please advise on what to try next.
>>
>> Uncompressing
>> Linux.............................................................
>> ................................................................................
>> ........................................... done, booting the kernel.
>> Linux version 2.6.30-omap1 (sakoman@otto) (gcc version 4.3.3 (GCC) ) #1
>> Wed
>> Jul
>> 8 21:26:05 PDT 2009
>> CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f
>> CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
>> Machine: Gumstix Overo
>> Memory policy: ECC disabled, Data cache writeback
>> OMAP3430 ES3.1
>> SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
>> Reserving 33554432 bytes SDRAM for VRAM
>> Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
>> 65024
>> Kernel command line: console=ttyS2,115200n8 vram=32m
>> omapfb.mode=dvi:480x272mr-1
>> 6@60 omapfb.debug=y omapdss.def_disp=lcd43 root=/dev/mtdblock4 rw
>> rootfstype=jff
>> s2
>>    
> 
> 
> ------------------------------------------------------------------------------
> 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
> 
> 

-- 
View this message in context: http://old.nabble.com/Palo43-LCD-Issue-tp26366804p26371498.html
Sent from the Gumstix mailing list archive at Nabble.com.