next topic »

[on:]

Hi!

I bought myself a nice Colorduino with an 8x8 led matrix from ebay and I'm trying to get started with it. I've installed the IDE (with Ubuntu 12.04 64bit), downloaded and installed the library from http://blog.lincomatic.com/ and built the example. But I can't seem to flash it. I've google a lot and found that I could use an FTDI cable, which I have connected according to this:

 FTDI RX -> Colorduino TX
 FTDI TX -> Colorduino RX
 FTDI RTS -> Colorduino DTR
 FTDI GND -> Colorduino GND

I use an external 5v power adapter as well. I've set the board to Arduino Nano w/ATmega 328 and the programmer is default (AVRISP mkII). The port is ttyUSB0 and I have set permissions to read/write to it (had to do that, even though I'm in the dialout group, don't know why). I get the following output:

ioctl("TIOCMGET"): Broken pipe
ioctl("TIOCMGET"): Broken pipe
avrdude: stk500_recv(): programmer is not responding
ioctl("TIOCMGET"): Broken pipe

I really don't know what to do now, so all input is welcome!

[Reply #1 on:]

Can anyone at least tell me if you've got it to work using an FTDI cable?

[Reply #2 on:]

I would first plug it in and look at the output of "dmesg". You should see recent activity indicating Linux found the USB device and has created a device such as /dev/ttyUSB0 or some such entry. If you don't see this - this is your first hit at a problem. If you do see it, you might try a common program like kermit and add a loop back to the far end of the cable. Then, simply type something. You should see it echo back as if you were typing into an editor. If all that works and the Arduino SDK still doesn't - I would next suspect that the Arduino SDK is trying to create lock files to prevent other programs from using the /dev/ttyUSB0 device (or what ever it was called) but failed. At this point, I (briefly) ran the Arduino SDK as root as a test.

[Reply #3 on:]

I would first plug it in and look at the output of "dmesg". You should see recent activity indicating Linux found the USB device and has created a device such as /dev/ttyUSB0 or some such entry. If you don't see this - this is your first hit at a problem. If you do see it, you might try a common program like kermit and add a loop back to the far end of the cable. Then, simply type something. You should see it echo back as if you were typing into an editor. If all that works and the Arduino SDK still doesn't - I would next suspect that the Arduino SDK is trying to create lock files to prevent other programs from using the /dev/ttyUSB0 device (or what ever it was called) but failed. At this point, I (briefly) ran the Arduino SDK as root as a test.

The port is discovered as it should and I have used this FTDI cable with an Arduino Pro before, so it's nothing wrong with that. What I'm wondering is if anyone got it to work with the colorduino as it is not build for using an FTDI cable directly. Are everyone using another modified arduino board in between? Seems a bit stupid that you have to do it that way. Is there really no better way to flash the colorduino?