This may be another obvious one, but do you have the backlight turned
on for the lcd? I made that mistake once trying to get a passive lcd
to work with a gumstix.
On 12/3/06, Roger Venable <roger38@...> wrote:
> Thanks, something obvious is what I think I'm overlooking right now. The
> framebuffer appears to be getting initialized by the kernel, with these
> u-boot args:
> 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
> (note, I've also tried it without the extra console=tty0 in the bootargs)
> The output from the kernel includes:
> pxa2xx-fb pxa2xx-fb: overriding resolution: 640x480
> pxa2xx-fb pxa2xx-fb: overriding bit depth: 16
> pxa2xx-fb pxa2xx-fb: override hsynclen: 3
> pxa2xx-fb pxa2xx-fb: override right: 5
> pxa2xx-fb pxa2xx-fb: override left: 10
> pxa2xx-fb pxa2xx-fb: override vsynclen: 39
> pxa2xx-fb pxa2xx-fb: override pixclock: 100000
> pxa2xx-fb pxa2xx-fb: override hsync: Active High
> pxa2xx-fb pxa2xx-fb: override vsync: Active High
> pxa2xx-fb pxa2xx-fb: override pixel clock polarity: falling edge
> When I look at "pxaregs LCCR", I get very minor variations of the output
> . Physically, everything looks fine, I can see the clock pulses on the
> connector wires from the GPSstix to the LCD. All the data lines output
> constant 0 volts, I assume because all pixels are black.
> I compile tinyX in with buildroot (rev 1183) and it all flashes, boots,
> connects to network. I can set up the I2C devices with the test 'i2c'
> utility in SVN at robostix/gumstix/i2c. But I'm missing the next step, I
> can't seem to actually get any software to put something to the
> framebuffer, much less console output. It's got to be simple, I'm missing
> You must be right about TextModeLCD, right now I'm fishing in all
> directions. Thanks for the suggestions, I really do appreciate the note.
> I'm hoping to get past this and on to writing the drivers for all the
> little critters I just hooked up on that I2C bus. Stagger, stagger,
> crawl, crawl.
> Thanks again,
> > I'm probably pointing out the obvious, but have you tried getting the
> > framebuffer driver to work first? Even if it's just an exercise, you've
> > gotta crawl before you can walk...
> > I could be/probably am wrong about this, but I thought "TextModeLCD" is
> > referring to character LCDs.
> > Let me know if you have any success at all, please. I'm going to be
> > going through your pain (tinyX/Matchbox in about two weeks w/ a screen
> > I'm ripping from a PDA. It'd be nice to avoid as much hassle as possible.
> > Ben
> > Roger Venable wrote:
> >> I'm still working to get a Panasonic EDMGRB8KJF touchscreen LCD
> >> interfaced
> >> and show *anything* at all.
> >> The rxvt package is broken, the FTP site no longer allows anonymous
> >> login.
> >> Fetching from SourceForge works, but it still doesn't compile. I have
> >> tinyX selected from the package list, and I see the tinyX export
> >> libraries
> >> in the rvxt compile, but there are still lots of undefined references.
> >> This is the same trouble I'm having with Matchbox, and so I'm stuck
> >> again.
> >> Please... it would seem that there are quite a few people who have
> >> gotten
> >> this to work, can I just get a few tips on how to proceed? When
> >> searching
> >> the web, the old Gumstix tikiwiki page "TextModeLCD" gets referenced a
> >> lot, but no longer exists. The pages I can find on the web which seem
> >> to
> >> deal with matchbox and tinyX are usually in Finnish or Korean.
> >> Some good news, tinyX still compiles. Not sure what I can do with it
> >> without a window manager, but a 'startx' gives:
> >> # startx
> >> killall: Xfbdev: no process killed
> >> Fatal server error:
> >> LinuxInit: Cannot open /dev/tty0 (No such file or directory)
> >> /bin/startx: /bin/startx: 7: /usr/X11R6/bin/matchbox: not found
> >> /bin/startx: /bin/startx: 9: /usr/X11R6/bin/minisys: not found
> >> /bin/startx: /bin/startx: 10: /usr/X11R6/bin/minitime: not found
> >> # /bin/startx: /bin/startx: 11: /usr/X11R6/bin/rxvt: not found
> >> Looks like it's ready for matchbox, so there's some light at the end of
> >> this tunnel. I'm pulling out my hair, any suggestions are greatly
> >> appreciated. If I've broken some unspoken tennet of behavior towards
> >> this
> >> list, I am very very sorry. Thank you in advance for any assistance or
> >> resource anyone can suggest.
> >>> I'm trying to add the Matchbox window manager to the buildroot (
> >>> http://projects.o-hand.com/matchbox/ ). It's pretty complex and has a
> >>> lot
> >>> of dependencies... tiny-X and libpng for examples. I've added a
> >>> matchbox
> >>> directory to the packages, and added a line to Config.in in the
> >>> packages
> >>> directory so I can select Matchbox in the Gumstix menuconfig.
> >>> Looking at other package configurations in the buildroot, I'd like a
> >>> confirmation of what I think I'm seeing. Some of the packages have
> >>> patch
> >>> files applied after tarball dearchiving.
> >>> What's a good example I might follow of one package that depends on
> >>> other
> >>> packages? Is there a place the dependencies are declared? I'm looking
> >>> at
> >>> the build and libtool patches in the jpeg package, they're kinda scary,
> >>> but I think they're similar to what I need to do in order to correctly
> >>> point to the library files and include directories. Is there a better
> >>> example?
> >>> ...and while I'm asking, I might as well go for broke... Any
> >>> infinitesimal
> >>> chance someone's already got Matchbox linking already and can share
> >>> their
> >>> configs?
> >>> Any tips are greatly appreciated. Thank you all for your thoughtful
> >>> consideration.
> >>> --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
> gumstix-users mailing list