Re: [Gumstix-users] still nothing on LCD

[Roger V. <ro...@md...>]

Previously I was using the command "era 1:2-31" to erase the flash when I
was reflashing.  I failed to read the u-boot wiki page completely and
notice that it needed to be 127 blocks for my board.  After that bad
erase, the flash images I was making with the virtual terminal enabled
were completely whacko, and it was easy for me to blame the problem on
including the virtual terminal feature.

I did a nice clean recompile, it's all good now. TinyX brings up the
horehound and the X but can't go any further... as expected.

So yeah, it was something simple and obvious, and I apologize for being a
mo-ron.  I can glue and screw the box shut and stop worrying about
dropping a screwdriver on a power connector, and start on my second
prototype now that I know this hardware set works.

The post a few days/weeks ago about turning off VGA Text console (in
Graphics Devices) when enabling the virtual terminal was helpful.  I can't
find it now to thank who wrote it.

Thanks again!

>
> Hey, thanks a lot!  It really helps to know where and what I need to look
> for.
>
>>>As I said, I've tried with both the extra "console=tty0" and without it.
>
> Note that both tty0 and ttyS0 are included in my bootargs, I assume so
> console will go to both.  Pages in the wiki showed args both with and
> without tty0, so I wasn't sure what it was.  I had played around with the
> virtual terminal character driver, but the last time I included it, the
> kernel booted very very strangely and very little worked.  It was like it
> was in 'run level 1' in any other linux distro.  I'll try it again.
>
> Is /dev/tty0 where the virtual terminal expects to be able to send the
> console output?
>
> Thanks again, this is really helping me out and making me think.  Oh, and
> seconds after I sent the last email, I realized the buffer is 640 x 480 x
> 2 bytes for the 16 bit colors, silly me.
> --Roger
>
>> In addition to what Nick pointed out, I think you also need to add
>> Device Drivers-->
>>   Character Devices-->
>>     [ * ] Virtual Terminal
>>     [ * ]    Support for console on virtual terminal (NEW)
>>
>> to your kernel config to get the console to show up.
>>
>> Chris
>>
>> On 12/3/06, Nicolaas Handojo <nic...@gm...> wrote:
>>> Hi,
>>>
>>> I might be wrong, but this part:
>>>
>>> bootargs=console=tty0
>>>
>>> Shouldn't it be 'ttyS0' instead of 'tty0'?
>>>
>>> Nick.
>>>
>>> -----Original Message-----
>>> From: gum...@li...
>>> [mailto:gum...@li...] On Behalf Of Roger
>>> Venable
>>> Sent: Sunday, December 03, 2006 6:02 PM
>>> To: gum...@li...
>>> Subject: Re: [Gumstix-users] still nothing on LCD
>>>
>>>
>>> Thanks again for the reply...
>>>
>>> > Something else to check is the contrast setting for the lcd... my lcd
>>> > uses a 10k trimpot for contrast adjustment and turning it 90 degrees
>>> > either way will turn my lcd black completely.
>>>
>>> It may be this simple, I'm using a 50K trimpot right now.  I'll swap it
>>> out.  The reason I tied it to Vcc is that there are examples on the
>>> docwiki of the VCON pin set to Vcc, so I thought that would at least be
>>> a
>>> default I should start with.  Moving it around doesn't seem to help
>>> much,
>>> it gets lighter and darker and I can get horizontal interference around
>>> 1.45 volts.  I've also tried adjusting it to 1.95 volts per the LCD
>>> data
>>> sheet.
>>>
>>> > And have you enabled the options in your kernel to output the console
>>> > to the framebuffer (which also requires a change to your bootargs)?
>>>
>>> This is what I'm confused about, the wiki kinda leaves off at this
>>> point.
>>> I enable:
>>>
>>> Device Drivers-> Graphics Support ->
>>> Support for frame buffer device
>>> Enable Video Mode Handling Helpers
>>> PXA LCD framebuffer support
>>> PXA LCD command line parameters
>>>
>>> The important variables in my bootargs env are:
>>>
>>> eas00=mw 40e00024 00010000; mw 40e0000c c183b9f8; mw 40e00018 00010000
>>> eas01=icache on;setenv stderr nulldev; setenv stdout nulldev
>>> eas02=if mmcinit && fatload mmc 0 a2000000 gumstix-factory.script; then
>>> run eas03; else run eas04; fi
>>> eas03=setenv stdout serial; setenv stderr serial; echo Found
>>> gumstix-factory script...; autoscr
>>> eas04=setenv stdout serial; setenv stderr serial; fsload && bootm
>>> bootcmd=run eas00; run eas01; run eas02
>>> bootargs=console=tty0 console=ttyS0,115200n8 root=1f01 rootfstype=jffs2
>>> reboot=cold,hard
>>> video=pxafb:mode:640x480-16,passive,color,hsynclen:3,right:5,left:10,vsyncle
>>> n:39,pixclock:100000,hsync:1,vsync:1,pixclockpol:0
>>>
>>> As I said, I've tried with both the extra "console=tty0" and without
>>> it.
>>> It didn't previously exist, so I created it with mknod.  Can I symlink
>>> it
>>> to /dev/fb0?  This would seem unlikely to me.
>>>
>>> Your suggestions and questions are greatly appreciated,
>>> --Roger
>>>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>


-- 
Roger Venable
(734) 272-0795
ICQ: 729414