From: Laurent D. <Lau...@ar...> - 2006-05-31 12:14:13
|
That's pretty obvious: > No space left on device Laurent =20 > -----Original Message----- > From: gum...@li...=20 > [mailto:gum...@li...] On Behalf=20 > Of Demetris Zavorotnichenko > Sent: 31 May 2006 14:11 > To: gum...@li... > Subject: Re: [Gumstix-users] Buildroot Questions >=20 > ok, so i have installed Fedora, and run the svn, make defconfig, make >=20 > after make and allot of downloading and processing i still=20 > haven't found the=20 > image of the Gumsrtix root in the folder. >=20 > Here are the last errors(since there is allot to paste) >=20 > I.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/gcc/.=20 > =20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/../include/home/gumstix-buildroot/toolchain_build_arm_nofp > u/gcc-3.4.5/gcc/optabs.c -ooptabs.ogcc -c -g -O2 -DIN_GCC=20 > -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes=20 > -Wmissing-prototypes -pedantic -Wno-long-long -DHAVE_CONFIG_H=20 > -I. -I.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/../include/home/gumstix-buildroot/toolchain_build_arm_nofp > u/gcc-3.4.5/gcc/opts.c -oopts.ogcc -c -g -O2 -DIN_GCC=20 > -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes=20 > -Wmissing-prototypes -pedantic -Wno-long-long -DHAVE_CONFIG_H=20 > -I. -I.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/../include/home/gumstix-buildroot > /toolchain_build_arm_nofpu/gcc-3.4.5/gcc/params.c=20 > -oparams.ogcc -c -g -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall=20 > -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes=20 > -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/../include/home/gumstix-buildroot/toolchain_build_arm_nofp > u/gcc-3.4.5/gcc/postreload.c -o postreload.ogcc -c -g -O2=20 > -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings=20 > -Wstrict-prototypes -Wmissing-prototypes -pedantic=20 > -Wno-long-long -DHAVE_CONFIG_H -I. -I.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/../include/home/gumstix-buildroot/toolchain_build_arm_nofp > u/gcc-3.4.5/gcc/print-rtl.c -o print-rtl.ogcc -c -g -O2 -DIN_ > GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings=20 > -Wstrict-prototypes -Wmissing-prototypes -pedantic=20 > -Wno-long-long -DHAVE_CONFIG_H -I. -I.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/../include/home/gumstix-buildroot/toolchain_build_arm_nofp > u/gcc-3.4.5/gcc/print-tree.c -o print-tree.ogcc -c -g -O2=20 > -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings=20 > -Wstrict-prototypes -Wmissing-prototypes -pedantic=20 > -Wno-long-long -DHAVE_CONFIG_H -I. -I.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/../include/home/gumstix-buildroot/toolchain_build_arm_nofp > u/gcc-3.4.5/gcc/value-prof.c -o value-prof.ogcc -c -g -O2=20 > -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings=20 > -Wstrict-prototypes -Wmissing-pr > ototypes -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/../include/home/gumstix-buildroot/toolchain_build_arm_nofp > u/gcc-3.4.5/gcc/ra.c -o ra.ogcc -c -g -O2 -DIN_GCC=20 > -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes=20 > -Wmissing-prototypes -pedantic -Wno-long-long -DHAVE_CONFIG_H=20 > -I. -I.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/../include/home/gumstix-buildroot/toolchain_build_arm_nofp > u/gcc-3.4.5/gcc/ra-build.c -o ra-build.ogcc -c -g -O2=20 > -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings=20 > -Wstrict-prototypes -Wmissing-prototypes -pedantic=20 > -Wno-long-long -DHAVE_CONFIG_H -I. -I.=20 > -I/home/gumstix-buildroot/toolchain_bui > ld_arm_nofpu/gcc-3.4.5/gcc=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/.=20 > -I/home/gumstix-buildroot/toolchain_build_arm_nofpu/gcc-3.4.5/ > gcc/../include/home/gumstix-buildroot/toolchain_build_arm_nofp > u/gcc-3.4.5/gcc/ra-colorize.c -o ra-colorize.oloop.o: No=20 > space left on device/tmp/ccFJQnsl.s: Assembler=20 > messages:/tmp/ccFJQnsl.s:68951: FATAL: Can't write loop.o:=20 > Illegal seekmake[2]: *** [loop.o] Error 1make[2]: *** Waiting=20 > for unfinished jobs....ra-build.o: No space left on=20 > device/tmp/ccVeR5Ce.s: Assembler=20 > messages:/tmp/ccVeR5Ce.s:31538: FATAL: Can't write=20 > ra-build.o: Illegal seekmake[2]: *** [ra-build.o] Error=20 > 1ra-colorize.o: No space left on device/tmp/ccmDCI3Z.s:=20 > Assembler messages:/tmp/ccmDCI3Z.s:30732: FATAL: Can't write=20 > ra-colorize.o: Illegal seekmake[2]: *** [ra-colorize.o] Error=20 > 1make[1]: *** [all-gcc] Error 2make[1]: Leaving=20 > directory`/home/gumstix-buildroot/toolchain_build_arm_nofpu/gc > c-3.4.5-final'make: ***[/home/gumstix-buildroot/toolchain_build_ > arm_nofpu/gcc-3.4.5-final/.compiled] Error 2You have mail in=20 > /var/spool/mail/rootso what is wrong ? >=20 >=20 > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost=20 > and Risk! > Fully trained technicians. The highest number of Red Hat=20 > certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D107521&bid=3D248729& > dat=3D121642 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users >=20 -- IMPORTANT NOTICE: The contents of this email and any attachments are = confidential and may also be privileged. If you are not the intended = recipient, please notify the sender immediately and do not disclose the = contents to any other person, use it for any purpose, or store or copy = the information in any medium. Thank you. |
From: Laurent D. <Lau...@ar...> - 2006-05-31 12:26:53
|
> the /home partition for the Gumstix buildroot is about 1 GB=20 > do i need more=20 > than that?=20 It is your /tmp partition that is full. And 1 GB looks small to me anyway (though I don't know how much you need to hold sources + binaries during compilation of Gumstix buildroot). Laurent -- IMPORTANT NOTICE: The contents of this email and any attachments are = confidential and may also be privileged. If you are not the intended = recipient, please notify the sender immediately and do not disclose the = contents to any other person, use it for any purpose, or store or copy = the information in any medium. Thank you. |
From: Demetris Z. <fgc...@cy...> - 2006-05-31 12:29:48
|
the root of the system is about 8 GB so not to have the /tmp full if i=20 install gumstix buildroot in a directory in root will this work? ----- Original Message -----=20 From: "Laurent Desnogues" <Lau...@ar...> To: <gum...@li...> Sent: Wednesday, May 31, 2006 3:26 PM Subject: RE: [Gumstix-users] Buildroot Questions > the /home partition for the Gumstix buildroot is about 1 GB > do i need more > than that? It is your /tmp partition that is full. And 1 GB looks small to me anyway (though I don't know how much you need to hold sources + binaries during compilation of Gumstix buildroot). Laurent -- IMPORTANT NOTICE: The contents of this email and any attachments are=20 confidential and may also be privileged. If you are not the intended=20 recipient, please notify the sender immediately and do not disclose the=20 contents to any other person, use it for any purpose, or store or copy th= e=20 information in any medium. Thank you. ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications i= n the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=107521&bid$8729&dat=121642 _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users=20 |
From: Demetris Z. <fgc...@cy...> - 2006-05-31 14:35:35
|
It looks like it needs more than 1GB since i have sucsessfully built the Jffs2 on root directory with 8GB. Thnx for the help guys |
From: Demetris Z. <fgc...@cy...> - 2006-06-01 19:46:11
|
On Holly's tutorial about setting up LCD screen there is a part that explains on setting the "pxaregs LCCR" for the lcd and specifies how to create a script to enable it on startup like a script. Can i modify this settings in the Gumstix-buildroot and compile the Kernel with this settings so i have it on my jffs2 image all setup and ready to run? Demetris |
From: Craig H. <cr...@gu...> - 2006-06-01 20:16:17
|
On Jun 1, 2006, at 12:45 PM, Demetris Zavorotnichenko wrote: > On Holly's tutorial about setting up LCD screen there is a part that > explains on setting the "pxaregs LCCR" for the lcd and specifies > how to > create a script to enable it on startup like a script. > > Can i modify this settings in the Gumstix-buildroot and compile the > Kernel > with this settings so i have it on my jffs2 image all setup and > ready to > run? I think the best way to do this is actually to figure out what the params are which need to be passed to the pxafb module, and then pass them. You shouldn't need to use pxaregs afaik to set up the PXA fb. C |
From: Demetris Z. <fgc...@cy...> - 2006-06-02 07:45:18
|
I saw that there is a way to add the same LCCR registers through U-boot bootargs. the LCCR registers that i need to setup for the Samsung LCD are : pxaregs GPCR0_16 1 pxaregs GPDR0_16 1 pxaregs GPSR0_16 1 <= (to enable the LCD) LCD Controller Control Register 0 (7-23) LCCR0 0x00300879 00000000 00110000 00001000 01111001 LCCR0_ENB 1 LCD controller enable LCCR0_CMS 0 LCD monochrome operation enable LCCR0_SDS 0 LCD dual panel display enable LCCR0_LDM 1 LCD disable done IRQ disable LCCR0_SFM 1 LCD start of frame IRQ disable LCCR0_IUM 1 LCD fifo underrun error IRQ disable LCCR0_EFM 1 LCD end of frame IRQ disable LCCR0_PAS 0 LCD active display enable LCCR0_DPD 0 LCD send 8 pixel on L_DD7:0 at each clock LCCR0_DIS 0 LCD controller disable LCCR0_QDM 1 LCD quick disable IRQ disable LCCR0_PDD 0 LCD palette DMA request delay LCCR0_BM 1 LCD branch start IRQ disable LCCR0_OUM 1 LCD fifo underrun IRQ disable LCD Controller Control Register 1 (7-26) LCCR1 0x06040a7f 00000110 00000100 00001010 01111111 LCCR1_PPL 639 LCD pixels per line (+1) LCCR1_HSW 2 LCD horizontal sync pulse width (+1) LCCR1_ELW 4 LCD end of line pixel clock wait count (+1) LCCR1_BLW 6 LCD beginning of line pixel clock wait count (+1) LCD Controller Control Register 2 (7-28) LCCR2 0x000099df 00000000 00000000 10011001 11011111 LCCR2_LPP 479 LCD lines per panel (+1) LCCR2_VSW 38 LCD vertical sync pulse width (+1) LCCR2_EFW 0 LCD end of frame line clock wait count (+1) LCCR2_BFW 0 LCD beginning of frame line clock wait count (+1) LCD Controller Control Register 3 (7-31) LCCR3 0x04400003 00000100 01000000 00000000 00000011 LCCR3_PCD 3 LCD pixel clock divisor (+1) LCCR3_ACB 0 LCD AC bias pin frequency (+1) LCCR3_API 0 LCD AC bias pin transitions per interrupt LCCR3_VSP 0 LCD L_FCLK vertical sync polarity active low LCCR3_HSP 0 LCD L_LCLK horizontal sync polarity active low LCCR3_PCP 1 LCD data sampled on falling edge of L_PCLK LCCR3_OEP 0 LCD L_BIAS output enable active low LCCR3_BPP 16 LCD bits per pixel LCCR3_DPC 0 LCD double pixel clock rate at L_PCLK Here how is done for the Sony ACX705AKM with the registers /root/pxaregs GPCR2_81 1 /root/pxaregs GPDR2_81 1 /root/pxaregs LCCR1_HSW 6 /root/pxaregs LCCR1_ELW 15 /root/pxaregs LCCR1_BLW 4 /root/pxaregs LCCR2_VSW 1 /root/pxaregs LCCR2_EFW 19 /root/pxaregs LCCR2_BFW 19 /root/pxaregs LCCR3_PCD 10 /root/pxaregs LCCR3_VSP 0 /root/pxaregs LCCR3_HSP 0 /root/pxaregs LCCR3_PCP 1 and here how it is setup in the U-boot: console=ttyS0,115200n8 root=1f02 rootfstype=jffs2 reboot=cold,hard video=pxafb:mode:240x160-16,active,hsynclen:7,right:16,left:5,upper:19,lower:19,vsynclen:2, hsync:1,vsync:1,pixclockpol:0,pixclock:216363 The settings without the registers for the Samsung are: setenv bootargs console=ttyS0,115200n8 root=1f02 rootfstype=jffs2 reboot=cold,hard video=pxafb:mode:640x480-16,passive,color,hsynclen:3,right:5,left:7,vsynclen:39,pixclock:80000,hsync:1,vsync:1,pixclockpol:1 How do i add the registers for the Samsung in the U-boot based on the bove? ----- Original Message ----- From: "Craig Hughes" <cr...@gu...> To: "General mailing list for gumstix users." <gum...@li...> Sent: Thursday, June 01, 2006 11:16 PM Subject: Re: [Gumstix-users] Buildroot Questions > On Jun 1, 2006, at 12:45 PM, Demetris Zavorotnichenko wrote: > >> On Holly's tutorial about setting up LCD screen there is a part that >> explains on setting the "pxaregs LCCR" for the lcd and specifies >> how to >> create a script to enable it on startup like a script. >> >> Can i modify this settings in the Gumstix-buildroot and compile the >> Kernel >> with this settings so i have it on my jffs2 image all setup and >> ready to >> run? > > I think the best way to do this is actually to figure out what the > params are which need to be passed to the pxafb module, and then pass > them. You shouldn't need to use pxaregs afaik to set up the PXA fb. > > C > > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Craig H. <cr...@gu...> - 2006-06-02 15:53:13
|
On Jun 2, 2006, at 12:14 AM, Demetris Zavorotnichenko wrote: > pxaregs GPCR0_16 1 > pxaregs GPDR0_16 1 > pxaregs GPSR0_16 1 <= (to enable the LCD) > How do i add the registers for the Samsung in the U-boot based on > the bove? u-boot doesn't have an easy way to set the GPxx registers (though it would be pretty easy to add a "gpio" command similar to the linux / proc/gpio thing). You'd have to use mw.l to write the register directly in memory; you could do that in your bootcmd before the "bootm" call. Alternatively, if you don't need the Samsung GPIO thing set before linux runs, then you could have a simple /etc/init.d script which uses /proc/gpio to twiddle the line you want. C |
From: Demetris Z. <fgc...@cy...> - 2006-06-02 16:02:20
|
ok, i set up the screen and followed the steps for the LCd, when i reboot the screen Flickers but displays nothing is this normal? ----- Original Message ----- From: "Craig Hughes" <cr...@gu...> To: "General mailing list for gumstix users." <gum...@li...> Sent: Friday, June 02, 2006 6:53 PM Subject: Re: [Gumstix-users] Buildroot Questions > On Jun 2, 2006, at 12:14 AM, Demetris Zavorotnichenko wrote: > >> pxaregs GPCR0_16 1 >> pxaregs GPDR0_16 1 >> pxaregs GPSR0_16 1 <= (to enable the LCD) > >> How do i add the registers for the Samsung in the U-boot based on >> the bove? > > u-boot doesn't have an easy way to set the GPxx registers (though it > would be pretty easy to add a "gpio" command similar to the linux / > proc/gpio thing). You'd have to use mw.l to write the register > directly in memory; you could do that in your bootcmd before the > "bootm" call. Alternatively, if you don't need the Samsung GPIO > thing set before linux runs, then you could have a simple /etc/init.d > script which uses /proc/gpio to twiddle the line you want. > > C > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Craig H. <cr...@gu...> - 2006-06-02 16:31:48
|
Depends what you mean by flicker. If you don't draw anything to the fb though, it'll be blank. You can do a quick test: dd if=/dev/urandom of=/dev/fb/0 You should then get snow on the screen. C On Jun 2, 2006, at 9:02 AM, Demetris Zavorotnichenko wrote: > ok, i set up the screen and followed the steps for the LCd, when i > reboot > the screen Flickers but displays nothing > is this normal? > > > ----- Original Message ----- > From: "Craig Hughes" <cr...@gu...> > To: "General mailing list for gumstix users." > <gum...@li...> > Sent: Friday, June 02, 2006 6:53 PM > Subject: Re: [Gumstix-users] Buildroot Questions > > >> On Jun 2, 2006, at 12:14 AM, Demetris Zavorotnichenko wrote: >> >>> pxaregs GPCR0_16 1 >>> pxaregs GPDR0_16 1 >>> pxaregs GPSR0_16 1 <= (to enable the LCD) >> >>> How do i add the registers for the Samsung in the U-boot based on >>> the bove? >> >> u-boot doesn't have an easy way to set the GPxx registers (though it >> would be pretty easy to add a "gpio" command similar to the linux / >> proc/gpio thing). You'd have to use mw.l to write the register >> directly in memory; you could do that in your bootcmd before the >> "bootm" call. Alternatively, if you don't need the Samsung GPIO >> thing set before linux runs, then you could have a simple /etc/init.d >> script which uses /proc/gpio to twiddle the line you want. >> >> C >> >> >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Demetris Z. <fgc...@cy...> - 2006-06-03 15:37:01
|
When typing make ARCH=arm CROSS_COMPILE=$PWD/../staging_dir/bin/arm-linux-uclibc- uImagethere is an error at the end saying "mkimage" command not found - U - Boot images will not be built.How do i fix that? |
From: Dave H. <dhy...@gm...> - 2006-06-03 15:45:24
|
Hi Demetris, > make ARCH=arm CROSS_COMPILE=$PWD/../staging_dir/bin/arm-linux-uclibc- > uImagethere is an error at the end saying "mkimage" command not found - U - > Boot images will not be built.How do i fix that? Which directory are you issuing this command from? -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Demetris Z. <fgc...@cy...> - 2006-06-03 15:55:53
|
I'm running this command from "gumstix-buildroot/build_arm_nofpu/linux-2.6.15gum" ----- Original Message ----- From: "Dave Hylands" <dhy...@gm...> To: "General mailing list for gumstix users." <gum...@li...> Sent: Saturday, June 03, 2006 6:45 PM Subject: Re: [Gumstix-users] uImage > Hi Demetris, > >> make ARCH=arm CROSS_COMPILE=$PWD/../staging_dir/bin/arm-linux-uclibc- >> uImagethere is an error at the end saying "mkimage" command not found - >> U - >> Boot images will not be built.How do i fix that? > > Which directory are you issuing this command from? > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Craig H. <cr...@gu...> - 2006-06-05 18:48:43
|
Remove the "uImage" part at the end of the line, and try again. C On Jun 3, 2006, at 8:55 AM, Demetris Zavorotnichenko wrote: > I'm running this command from > "gumstix-buildroot/build_arm_nofpu/linux-2.6.15gum" > ----- Original Message ----- > From: "Dave Hylands" <dhy...@gm...> > To: "General mailing list for gumstix users." > <gum...@li...> > Sent: Saturday, June 03, 2006 6:45 PM > Subject: Re: [Gumstix-users] uImage > > >> Hi Demetris, >> >>> make ARCH=arm CROSS_COMPILE=$PWD/../staging_dir/bin/arm-linux- >>> uclibc- >>> uImagethere is an error at the end saying "mkimage" command not >>> found - >>> U - >>> Boot images will not be built.How do i fix that? >> >> Which directory are you issuing this command from? >> >> -- >> Dave Hylands >> Vancouver, BC, Canada >> http://www.DaveHylands.com/ >> >> >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Demetris Z. <fgc...@cy...> - 2006-06-05 18:53:13
|
Tnx for the tip Craig. I'll doo that ----- Original Message ----- From: "Craig Hughes" <cr...@gu...> To: "General mailing list for gumstix users." <gum...@li...> Sent: Monday, June 05, 2006 9:48 PM Subject: Re: [Gumstix-users] uImage > Remove the "uImage" part at the end of the line, and try again. > > C > > On Jun 3, 2006, at 8:55 AM, Demetris Zavorotnichenko wrote: > >> I'm running this command from >> "gumstix-buildroot/build_arm_nofpu/linux-2.6.15gum" >> ----- Original Message ----- >> From: "Dave Hylands" <dhy...@gm...> >> To: "General mailing list for gumstix users." >> <gum...@li...> >> Sent: Saturday, June 03, 2006 6:45 PM >> Subject: Re: [Gumstix-users] uImage >> >> >>> Hi Demetris, >>> >>>> make ARCH=arm CROSS_COMPILE=$PWD/../staging_dir/bin/arm-linux- >>>> uclibc- >>>> uImagethere is an error at the end saying "mkimage" command not >>>> found - >>>> U - >>>> Boot images will not be built.How do i fix that? >>> >>> Which directory are you issuing this command from? >>> >>> -- >>> Dave Hylands >>> Vancouver, BC, Canada >>> http://www.DaveHylands.com/ >>> >>> >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Demetris Z. <fgc...@cy...> - 2006-06-03 17:07:41
|
Robostix is a board hosting the Atmega 128 micro. If i want to control motors, servo's, led's e.t.c. from Gumstix then i would just do it like an ordinary setup of Atmega connected to a PC? (write software for the Atmega, flash the Atmega with the software and control the atmega from gumstix using the setup i made on atmega (Serial)? |
From: Dave H. <dhy...@gm...> - 2006-06-03 23:57:33
|
Hi Demetris, On 6/3/06, Demetris Zavorotnichenko <fgc...@cy...> wrote: > Robostix is a board hosting the Atmega 128 micro. > > If i want to control motors, servo's, led's e.t.c. from Gumstix then i would > just do it like an ordinary setup of Atmega connected to a PC? (write > software for the Atmega, flash the Atmega with the software and control the > atmega from gumstix using the setup i made on atmega (Serial)? Yep - that's definitely a viable option. The ATMega i2c is connected to the gumstix if they're plugged together. You can easily jumper atmega UART-0 to the STUART port on the gumstix (see the gumstix-ISP page). You can program the robostix in standalone mode (no gumstix connected) by using the ISP connector on the robostix. If you plug the gumstix and robostix together, you can program the robostix from the gumstix: http://gumstix.org/tikiwiki/tiki-index.php?page=Robostix-Gumstix-ISP I've also created an i2c Bootloader, which once programmed, allows new programs to be downloaded via i2c. http://gumstix.org/tikiwiki/tiki-index.php?page=Robostix-i2c-bootloader I've also created the i2c-io program: http://gumstix.org/tikiwiki/tiki-index.php?page=Robostix-i2c-io which allows GPIO's, etc on the robostix to be controlled from the gumstix (either from the gumstix command line using the i2c-io program, or by linking the appropriate source files into your program. The i2c-io program will allow any of the registers on the ATMega128 to be manipulated symbolically (the register names, not the bits withing the register). -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Demetris Z. <fgc...@cy...> - 2006-06-04 18:31:53
|
I2c-IO is exacty what i needed Dave, tnx allot for the tip. So with this i can control Robostix directly from Gumstix with my source? that's greate. ----- Original Message ----- From: "Dave Hylands" <dhy...@gm...> To: "General mailing list for gumstix users." <gum...@li...> Sent: Sunday, June 04, 2006 2:57 AM Subject: Re: [Gumstix-users] Controlling Robostix > Hi Demetris, > > On 6/3/06, Demetris Zavorotnichenko <fgc...@cy...> wrote: >> Robostix is a board hosting the Atmega 128 micro. >> >> If i want to control motors, servo's, led's e.t.c. from Gumstix then i >> would >> just do it like an ordinary setup of Atmega connected to a PC? (write >> software for the Atmega, flash the Atmega with the software and control >> the >> atmega from gumstix using the setup i made on atmega (Serial)? > > Yep - that's definitely a viable option. The ATMega i2c is connected > to the gumstix if they're plugged together. You can easily jumper > atmega UART-0 to the STUART port on the gumstix (see the gumstix-ISP > page). > > You can program the robostix in standalone mode (no gumstix connected) > by using the ISP connector on the robostix. > > If you plug the gumstix and robostix together, you can program the > robostix from the gumstix: > http://gumstix.org/tikiwiki/tiki-index.php?page=Robostix-Gumstix-ISP > > I've also created an i2c Bootloader, which once programmed, allows new > programs to be downloaded via i2c. > http://gumstix.org/tikiwiki/tiki-index.php?page=Robostix-i2c-bootloader > > I've also created the i2c-io program: > http://gumstix.org/tikiwiki/tiki-index.php?page=Robostix-i2c-io > > which allows GPIO's, etc on the robostix to be controlled from the > gumstix (either from the gumstix command line using the i2c-io > program, or by linking the appropriate source files into your program. > The i2c-io program will allow any of the registers on the ATMega128 to > be manipulated symbolically (the register names, not the bits withing > the register). > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2006-06-04 21:38:15
|
HI Demetris, On 6/4/06, Demetris Zavorotnichenko <fgc...@cy...> wrote: > I2c-IO is exacty what i needed Dave, tnx allot for the tip. So with this i > can control Robostix directly from Gumstix with my source? that's greate. You can control simple things. There is no mechanism for dealing with interruputs of any sort. And serial stuff isn't really dealt with although you could send characters slowly... -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Demetris Z. <fgc...@cy...> - 2006-06-02 16:48:49
|
it seems that i don't have the "fb" directory in "dev" this means that i dodn't set up the framebuffer when i was compiling the Kernel ? if yes then i typed on the Linux machine: make ARCH=arm CROSS_COMPILE=$PWD../staging_dir/bin/arm-linux-uclibc- menuconfigand enabled everything i need in the setup then i went to gumstix-buildroot and typed MAKE isn't this the correct way to make the Kernel with the settings i made? ----- Original Message ----- From: "Craig Hughes" <cr...@gu...> To: "General mailing list for gumstix users." <gum...@li...> Sent: Friday, June 02, 2006 7:31 PM Subject: Re: [Gumstix-users] Buildroot Questions > Depends what you mean by flicker. If you don't draw anything to the > fb though, it'll be blank. You can do a quick test: > > dd if=/dev/urandom of=/dev/fb/0 > > You should then get snow on the screen. > > C > > On Jun 2, 2006, at 9:02 AM, Demetris Zavorotnichenko wrote: > >> ok, i set up the screen and followed the steps for the LCd, when i >> reboot >> the screen Flickers but displays nothing >> is this normal? >> >> >> ----- Original Message ----- >> From: "Craig Hughes" <cr...@gu...> >> To: "General mailing list for gumstix users." >> <gum...@li...> >> Sent: Friday, June 02, 2006 6:53 PM >> Subject: Re: [Gumstix-users] Buildroot Questions >> >> >>> On Jun 2, 2006, at 12:14 AM, Demetris Zavorotnichenko wrote: >>> >>>> pxaregs GPCR0_16 1 >>>> pxaregs GPDR0_16 1 >>>> pxaregs GPSR0_16 1 <= (to enable the LCD) >>> >>>> How do i add the registers for the Samsung in the U-boot based on >>>> the bove? >>> >>> u-boot doesn't have an easy way to set the GPxx registers (though it >>> would be pretty easy to add a "gpio" command similar to the linux / >>> proc/gpio thing). You'd have to use mw.l to write the register >>> directly in memory; you could do that in your bootcmd before the >>> "bootm" call. Alternatively, if you don't need the Samsung GPIO >>> thing set before linux runs, then you could have a simple /etc/init.d >>> script which uses /proc/gpio to twiddle the line you want. >>> >>> C >>> >>> >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Demetris Z. <fgc...@cy...> - 2006-06-04 18:23:49
|
When all the settings for the LCD are correct will i see the Penguin at Boot time ? How can i test if the Framebuffer is enabled or if the LCD is working? |
From: Sumit B. <sb...@ta...> - 2006-06-04 22:06:25
|
I just got my framebuffer working. Don't see any penguin at boot time. You can however, find lines about pxafb while booting up (use dmesg). pxa2xx-fb pxa2xx-fb: overriding resolution: 320x240 pxa2xx-fb pxa2xx-fb: overriding bit depth: 16 pxa2xx-fb pxa2xx-fb: override hsynclen: 12 pxa2xx-fb pxa2xx-fb: override left: 72 pxa2xx-fb pxa2xx-fb: override upper: 6 pxa2xx-fb pxa2xx-fb: override pixclock: 158730 Some things you can try - 1. 'cat /dev/urandom > /dev/fb0' to put noise on the screen. 2. 'pxaregs LCCR' will print the LCD register values; one of them will indicate whether the LCD controller is enabled or not. 3. Download a simple C program I wrote which outputs a few patterns to screen (works only with 16 and 32 bit framebuffers). http://sumitbirla.com/braindump/ Demetris Zavorotnichenko wrote: > When all the settings for the LCD are correct will i see the Penguin at Boot > time ? How can i test if the Framebuffer is enabled or if the LCD is > working? > > |
From: Demetris Z. <fgc...@cy...> - 2006-06-05 07:29:34
|
Did anyone manage to get the Panasonic LCD working? It seems that whatever i do i get no responce from the LCD, Could really use some help here. When booting up or restarting Gumstix i get a Sudden Flash from the monitor and then blank whatever i do, I enabled the Framebuffer and gone through the process described on the WIKI tutorial several times but still no responce. |
From: Demetris Z. <fgc...@cy...> - 2006-06-05 06:29:18
|
What steps did you follow Birla? On the linux machine did you run menuconfig, then make and reflashed Gumstix? Could you point out the commands to see if mine are correct pls. ----- Original Message ----- From: "Sumit Birla" <sb...@ta...> To: "General mailing list for gumstix users." <gum...@li...> Sent: Monday, June 05, 2006 1:06 AM Subject: Re: [Gumstix-users] LCD Frame Buffer >I just got my framebuffer working. Don't see any penguin at boot time. > You can however, find lines about pxafb while booting up (use dmesg). > > pxa2xx-fb pxa2xx-fb: overriding resolution: 320x240 > pxa2xx-fb pxa2xx-fb: overriding bit depth: 16 > pxa2xx-fb pxa2xx-fb: override hsynclen: 12 > pxa2xx-fb pxa2xx-fb: override left: 72 > pxa2xx-fb pxa2xx-fb: override upper: 6 > pxa2xx-fb pxa2xx-fb: override pixclock: 158730 > > Some things you can try - > > 1. 'cat /dev/urandom > /dev/fb0' to put noise on the screen. > 2. 'pxaregs LCCR' will print the LCD register values; one of them will > indicate whether the LCD controller is enabled or not. > 3. Download a simple C program I wrote which outputs a few patterns to > screen (works only with 16 and 32 bit framebuffers). > http://sumitbirla.com/braindump/ > > > > Demetris Zavorotnichenko wrote: >> When all the settings for the LCD are correct will i see the Penguin at >> Boot >> time ? How can i test if the Framebuffer is enabled or if the LCD is >> working? >> >> > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Sumit B. <sb...@ta...> - 2006-06-05 11:24:53
|
I essentially followed the steps described in the wiki. 1. cd to linux directory 2. make menuconfig 3. select PXA framebuffer and helper functions 4. cd ../../ 5. make 6. Flash the new image to gumstix 7. U-boot: set bootargs to include video=:pxafb:mode:320x240-16,active,pixclock:158730 (for my LCD) 8. reset For me, regardless of what was on the screen, it goes blank as soon as the kernel starts loading. It stays that way until I write something to the framebuffer. Can you send the output of 'dmesg' and 'pxaregs LCCR' commands from your gumstix? - Sumit Demetris Zavorotnichenko wrote: > What steps did you follow Birla? > > On the linux machine did you run menuconfig, then make and reflashed > Gumstix? > > Could you point out the commands to see if mine are correct pls. > > |