From: Roger V. <ro...@md...> - 2006-11-29 16:46:06
|
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 P.S. I like your tag line, Dr. Borasky. "If Klingons had intended glommers to eat tribbles cooked, they would have genetically engineered them with lasers on their heads." |
From: Roger V. <ro...@md...> - 2006-12-03 00:23:07
|
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 |
From: Benjamin B. <ben...@wi...> - 2006-12-03 06:54:23
|
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 > 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 > > > > |
From: Roger V. <ro...@md...> - 2006-12-03 18:28:36
|
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 reboot=cold,hard video=pxafb:mode:640x480-16,passive,color,hsynclen:3,right:5,left:10,vsynclen:39,pixclock:100000,hsync:1,vsync:1,pixclockpol:0 (note, I've also tried it without the extra console=tty0 in the bootargs) The output from the kernel includes: ...snip... 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 ...snip... When I look at "pxaregs LCCR", I get very minor variations of the output at http://docwiki.gumstix.org/Display#Connecting_a_Panasonic_EDMGRB8KJF_LCD_to_a_gumstix . 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 something. 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, --Roger > 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 |
From: Chris D. <chr...@gm...> - 2006-12-03 18:40:24
|
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. Chris On 12/3/06, Roger Venable <ro...@md...> 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 > reboot=cold,hard > video=pxafb:mode:640x480-16,passive,color,hsynclen:3,right:5,left:10,vsynclen:39,pixclock:100000,hsync:1,vsync:1,pixclockpol:0 > > (note, I've also tried it without the extra console=tty0 in the bootargs) > The output from the kernel includes: > > ...snip... > 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 > ...snip... > > When I look at "pxaregs LCCR", I get very minor variations of the output > at > http://docwiki.gumstix.org/Display#Connecting_a_Panasonic_EDMGRB8KJF_LCD_to_a_gumstix > . 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 > something. > > 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, > --Roger > > > 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 > 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 > |
From: Roger V. <ro...@md...> - 2006-12-03 19:14:08
|
Not at all, very legitimate. I replaced the 1000 volt backlight CCFT with a set of white LEDs drilled and glued into the top of the LCD. They are controlled with a Maxim I2C chip, and I can turn them on with 32 steps of brightness. At full blast, they take a bit of juice, but still can't see anything on the LCD. The "mw" commands in the u-boot seem to work to turn on DISPON, the LCD screen lightens when those happen, then when I switch on the backlight LEDs, nothing there. I've tried pxaregs scripts as well to turn on DISPON, and I can confirm the signal is high (I have the DISPON signal coming from PW0 and the VCON on a potentiometer currently full over to Vcc). Can I write to the framebuffer memory directly before boot, with the same "mw" u-boot command or with a small utility app? Turning it all white would at least let me fine tune the electricals before I screw the box shut. > 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. > > Chris > |
From: Chris D. <chr...@gm...> - 2006-12-03 19:42:04
|
Strange.... I don't know of a way to write to the framebuffer before boot time, but if you have the framebuffer driver setup correctly there shouldn't be any reason that you can't get it to output something in linux. 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. And have you enabled the options in your kernel to output the console to the framebuffer (which also requires a change to your bootargs)? That is probably the easiest way to troubleshoot framebuffer problems. Chris On 12/3/06, Roger Venable <ro...@md...> wrote: > Not at all, very legitimate. I replaced the 1000 volt backlight CCFT with > a set of white LEDs drilled and glued into the top of the LCD. They are > controlled with a Maxim I2C chip, and I can turn them on with 32 steps of > brightness. At full blast, they take a bit of juice, but still can't see > anything on the LCD. > > The "mw" commands in the u-boot seem to work to turn on DISPON, the LCD > screen lightens when those happen, then when I switch on the backlight > LEDs, nothing there. I've tried pxaregs scripts as well to turn on > DISPON, and I can confirm the signal is high (I have the DISPON signal > coming from PW0 and the VCON on a potentiometer currently full over to > Vcc). > > Can I write to the framebuffer memory directly before boot, with the same > "mw" u-boot command or with a small utility app? Turning it all white > would at least let me fine tune the electricals before I screw the box > shut. > > > 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. > > > > Chris > > > > > > ------------------------------------------------------------------------- > 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 > |
From: Roger V. <ro...@md...> - 2006-12-03 23:02:01
|
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,vsynclen: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 |
From: Nicolaas H. <nic...@gm...> - 2006-12-04 00:11:02
|
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 |
From: Chris D. <chr...@gm...> - 2006-12-04 00:28:20
|
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 > > > ------------------------------------------------------------------------- > 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 > |
From: Roger V. <ro...@md...> - 2006-12-04 01:22:37
|
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 >> |
From: Roger V. <ro...@md...> - 2006-12-04 02:53:53
|
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 |
From: Roger V. <ro...@md...> - 2006-12-03 23:28:45
|
Ah ha!! I got a little of what I'm looking for, the command: dd if=/dev/zero of=/dev/fb0 count=1 bs=614400 'clutters' up the screen, and dd if=/dev/zero of=/dev/fb0 count=1 bs=614400 clears it again. 614400 = 640 * 480 * 2, but it's not particularly intuitive to me why it's only two bits? Okay, now I know it *physically* works. Now to get console on it... what am I missing?? --Roger > > 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,vsynclen: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 |
From: Dave H. <dhy...@gm...> - 2006-12-04 02:34:57
|
Hi Roger, > dd if=/dev/zero of=/dev/fb0 count=1 bs=614400 > > clears it again. 614400 = 640 * 480 * 2, but it's not particularly > intuitive to me why it's only two bits? That would be 2 bytes, or 16 bits, not 2 bits. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |