From: Nathaniel M. <nat...@gm...> - 2009-12-14 05:56:52
|
Hi all- Sorry for a total newbie question here, but I've been googling for a while trying to find a basic "hello world" tutorial for the Gumstix Overo, but haven't had much luck. I've seen a "hello world" tutorial mentioned a few times, but that seems to be a 404 now. I have a Gumstix Overo Air with a Summit expansion board. I've successfully booted it up, and connected to the console over USB. My development platform is Ubuntu 9.04 running in VirtualBox under Snow Leopard. I've completed all the steps at http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html My basic question is: Now what? I'd like to compile a basic Hello World program, transfer it over to the Overo, and run it. But I'm really unclear on what the steps are to do this, or how to find the documentation that explains this. Thanks in advance to anyone that can point me in the right direction. Thanks, Nate |
From: ScottEllis <sco...@gm...> - 2009-12-14 11:12:51
|
Use a Makefile like this to use the cross-compile tools OE built for you. OETMP = ${OVEROTOP}/tmp TOOLDIR = ${OETMP}/cross/armv7a/bin STAGEDIR = ${OETMP}/staging/armv7a-angstrom-linux-gnueabi/usr CC = ${TOOLDIR}/arm-angstrom-linux-gnueabi-gcc LIBDIR = ${STAGEDIR}/lib INCDIR = ${STAGEDIR}/include helloworld : helloworld.c ${CC} -I ${INCDIR} -L ${LIBDIR} helloworld.c -o helloworld -- View this message in context: http://old.nabble.com/Overo-Hello-World-tutorial--tp26773361p26776185.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Nathaniel M. <nat...@gm...> - 2009-12-14 19:47:37
|
Thanks, I'll try that out tonight. After I have a binary of my "helloworld," how do I go about transferring that over to the Overo? Thanks, Nate On Mon, Dec 14, 2009 at 3:12 AM, ScottEllis <sco...@gm...>wrote: > > Use a Makefile like this to use the cross-compile tools OE built for you. > > OETMP = ${OVEROTOP}/tmp > TOOLDIR = ${OETMP}/cross/armv7a/bin > STAGEDIR = ${OETMP}/staging/armv7a-angstrom-linux-gnueabi/usr > CC = ${TOOLDIR}/arm-angstrom-linux-gnueabi-gcc > LIBDIR = ${STAGEDIR}/lib > INCDIR = ${STAGEDIR}/include > > helloworld : helloworld.c > ${CC} -I ${INCDIR} -L ${LIBDIR} helloworld.c -o helloworld > > -- > View this message in context: > http://old.nabble.com/Overo-Hello-World-tutorial--tp26773361p26776185.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Scott E. <sco...@gm...> - 2009-12-15 12:45:12
|
If you have networking wifi, ethernet, usbnet, use scp. Otherwise, if you are booting from an mmc card, after you untar the rootfs onto the card but before you unmount it, copy your program executable to it. This is not how you want to do it more then once or twice though. On 12/14/09, Nathaniel Martin <nat...@gm...> wrote: > Thanks, I'll try that out tonight. > > After I have a binary of my "helloworld," how do I go about transferring > that over to the Overo? > > Thanks, > Nate > > On Mon, Dec 14, 2009 at 3:12 AM, ScottEllis > <sco...@gm...>wrote: > >> >> Use a Makefile like this to use the cross-compile tools OE built for you. >> >> OETMP = ${OVEROTOP}/tmp >> TOOLDIR = ${OETMP}/cross/armv7a/bin >> STAGEDIR = ${OETMP}/staging/armv7a-angstrom-linux-gnueabi/usr >> CC = ${TOOLDIR}/arm-angstrom-linux-gnueabi-gcc >> LIBDIR = ${STAGEDIR}/lib >> INCDIR = ${STAGEDIR}/include >> >> helloworld : helloworld.c >> ${CC} -I ${INCDIR} -L ${LIBDIR} helloworld.c -o helloworld >> >> -- >> View this message in context: >> http://old.nabble.com/Overo-Hello-World-tutorial--tp26773361p26776185.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> >> ------------------------------------------------------------------------------ >> Return on Information: >> Google Enterprise Search pays you back >> Get the facts. >> http://p.sf.net/sfu/google-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > |
From: Nathaniel M. <nat...@gm...> - 2009-12-15 18:52:09
|
If I'm still just connecting through the USB console, what is the preferred way to transfer the binary? Thanks, nate On Tue, Dec 15, 2009 at 4:44 AM, Scott Ellis <sco...@gm... > wrote: > If you have networking wifi, ethernet, usbnet, use scp. > > Otherwise, if you are booting from an mmc card, after you untar the > rootfs onto the card but before you unmount it, copy your program > executable to it. This is not how you want to do > it more then once or twice though. > > On 12/14/09, Nathaniel Martin <nat...@gm...> wrote: > > Thanks, I'll try that out tonight. > > > > After I have a binary of my "helloworld," how do I go about transferring > > that over to the Overo? > > > > Thanks, > > Nate > > > > On Mon, Dec 14, 2009 at 3:12 AM, ScottEllis > > <sco...@gm...>wrote: > > > >> > >> Use a Makefile like this to use the cross-compile tools OE built for > you. > >> > >> OETMP = ${OVEROTOP}/tmp > >> TOOLDIR = ${OETMP}/cross/armv7a/bin > >> STAGEDIR = ${OETMP}/staging/armv7a-angstrom-linux-gnueabi/usr > >> CC = ${TOOLDIR}/arm-angstrom-linux-gnueabi-gcc > >> LIBDIR = ${STAGEDIR}/lib > >> INCDIR = ${STAGEDIR}/include > >> > >> helloworld : helloworld.c > >> ${CC} -I ${INCDIR} -L ${LIBDIR} helloworld.c -o helloworld > >> > >> -- > >> View this message in context: > >> > http://old.nabble.com/Overo-Hello-World-tutorial--tp26773361p26776185.html > >> Sent from the Gumstix mailing list archive at Nabble.com. > >> > >> > >> > >> > ------------------------------------------------------------------------------ > >> Return on Information: > >> Google Enterprise Search pays you back > >> Get the facts. > >> http://p.sf.net/sfu/google-dev2dev > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > > > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2009-12-15 19:19:30
|
Hi Nate, On Tue, Dec 15, 2009 at 10:51 AM, Nathaniel Martin <nat...@gm...> wrote: > If I'm still just connecting through the USB console, what is the preferred > way to transfer the binary? Normally, I would use Z-Modem. I found some instructions over here: <http://ossie.wireless.vt.edu/trac/wiki/BeagleBoard> Then search for ZMODEM. This assumes that you're booting from a micro-SD card. In a nutshell, you need to build lrzsz: bitbake lrzsz Then you can copy the ipk file from tmp/deploy/glibc/ipk/armv7a/lrzsz_0.12.20-r4.1_armv7a.ipk onto the uSD card. Once that's done, you can put the uSD back in the overo and reboot. Then from the overo do: opkg install lrzsz_0.12.20-r4.1_armv7a.ipk from the directory where you downloaded the ipk file to. Once this is done, you can issue rz from the overo and then send a file using zmodem from the host. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: ScottEllis <sco...@gm...> - 2009-12-15 19:36:53
|
I just tried sending with kermit and it worked. At least for a text file. If you are using kermit for your console session, Ctrl-\ C back to the kermit prompt, and then send <filename> and then type connect to get back to the gumstix. But it was really slow. A network connection would be a whole lot faster. -- View this message in context: http://old.nabble.com/Overo-Hello-World-tutorial--tp26773361p26800482.html Sent from the Gumstix mailing list archive at Nabble.com. |