I use use i2c-io (courtesy of Dave) to communicate between the robostix and the gumstix. But before you do that you need the i2c modules loaded (i2c-dev and i2c-pxa) and i2c-load loaded. Those are also .ipk modules which you can install. First put the i2c bootloader on the robostix then use i2c-load to load the i2c-io.hex file onto the robostix. It works very well when done correctly.
[mailto:firstname.lastname@example.org] On Behalf Of Jose Gomez
Sent: Monday, July 14, 2008 12:59 PM
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] Hello world! problems
First of all thank you Mark and John for helping me with my Hello world problem, I was able to do the cross-compiling and run the exe file on the gumstix.
Second, I would like to know if there is an example (meaning me being able to run the bitbake file) on how to use the i2c to communicate from OE gumstix to robostix, something like turning on and off an LED? and if not, if it is not too much trouble that is, can someone tell how to do it?
On Thu, Jul 10, 2008 at 3:19 PM, Dave Hylands <email@example.com> wrote:
> The .ipk file is 200k, and the unpacked "helloworld" package is 400k for a total of 600k (until I delete the .ipk)
> First, how would I go about linking dynamically instead of statically using bitbake (not buildroot)?
> Do I use the arm-angstrom-linux-gnueabi-c++ compiler istead of making the cumbersome package and recipe combination?
Sorry - I'm not familiar with OE yet, so I'll have to let somebody
else answer that one.
> Second, If I was to use buildroot, then how would I be able to run the programs on the gumstix (which is currently running the OE filesystem and kernel) without having /bin/bash to execute them?
You probably can't use the buildroot toolchain with an OE system.
> Flashing the gumstix with a buildroot kernel and filesystem nets me a corrupt terminal.
> Also, how would I perform static vs dynamic linking with the buildroot (arm-linux-g++) cross compiler?
> I suppose it would be the same was as the arm-angstrom-linux-gnueabi-c++ one.
Normally, the toolchain defaults to dynamic. To force it to use
static, you pass -static on the command line to gcc/g++ when compiling
and when linking. Similarly to force dynamic, you use -dynamic.
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
gumstix-users mailing list