Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
As part of an MSc course, I am building a robot which uses a gumstix &
robostix for control.
I have got wireless access to the gumstix up and running so I can log in
and edit files using vi and so on.
For Rapid Application Development in situ on the gumstix I would like to
achieve the following....
1} Get a buildroot that has tcl, spi & i2c included
2) create a shared library that can be loaded in tcl to provide commands
that access the underlying C api for spi & i2c
3) develop tcl scripts in situ on the gumstix, interfacing with robot
sensors by using the new tcl commands
I figure it would be much easier to fiddle If I can provide access to
the IO programmatically through tcl commands as there isn't the space to
host a full gcc dev environment on the gumstix itself.
Is this a feasible idea ? Does anyone have any pointers ?
I'm reasonably competent regarding writing C code that can be accessed
easily from within tcl. I need some pointers to the SPI & I2C C api and
just some advice on getting this set up working.