[C.CC USERS] Make upload probs

Matt Jadud jadudm at gmail.com
Tue Apr 27 02:44:39 BST 2010


Hi Aaron,

On Mon, Apr 26, 2010 at 6:57 PM, Aaron Ryan <amrphoto1 at gmail.com> wrote:
> ....even trying to upload the firmware again with 'make upload' brings me
> back to 'blink' on the board.

Truly, we need to finish the build process.

Please grab:

http://www.transterpreter.org/downloads/lin/2010-02-27-occam.tar.gz

If placed in

/opt/

and decompressed there, the hard-coded paths in the scripts will work.
Or, you can edit things to make them work against the tools you've
compiled.

Either way, there is a bash script called

arduinocc

which does some sensible things. For example,

arduinocc /dev/null firmware

will upload the actual firmware, and

arduinocc /dev/null blink.occ

will compile, convert, and upload an occam program.

In theory, you might even be able to add

/opt/occam/arduino/bin

to your path and have everything work. (Certainly, you need it there
for the compilation script to find everything, unless you edit it.)

This is absolutely not how software should be distributed for Linux.
However, I haven't had time to do the bundling of .rpms or .deb
packages, which will eliminate all of this time. (Keeping up with the
semester, sometimes, is all I can do.) So, in just another short week
or two, I'll be able to dive in more fully. In the meantime, if you
would see if that helps (if nothing else, reading the arduinocc script
will tell you about what commands you need to run), that would be
great.

Do keep asking questions. We'll try and keep providing answers.

Cheers,
Matt




More information about the users mailing list