Hi! I just got my Seeeduino today, and was excited to try it out. Unfortunately I get multiple errors (I have tested it on three different computers, one running Windows 7 (x86_64) and Linux (x86_64), one running Windows Server 2008 (x86_64) and another one running Windows XP (SP3, 32-bit).
On the first computer, running Windows 7, I get the following errors when trying to upload a sketch with the Arduino IDE:
avrdude: stk500_getsync(): not in sync: resp=0x00
avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51
Which seems to be what many many others get too.
On Linux, I get the following:
avrdude: stk500_recv(): programmer is not responding
I managed to get one sketch uploaded (the Blink example) on Linux, but that was when I chose LilyPad w/ ATmega328 from the Arduino menu. After that, I haven’t got anything uploaded, not on Linux, not on Windows, not with Arduino Duemilanove w/ ATmega 328 selected from the IDE menu or with LilyPad w/ ATmega328. Whenever I try to upload a sketch, the RX light on the Seeeduino blinks three times. A few seconds later it blinks once, but I still get an error. The TX light isn’t blinking at all.
I have also tried this tutorial: geocities.jp/arduino_diecimi … ex_en.html but avrdude doesn’t read my fuses properly:
avrdude.exe: BitBang OK
avrdude.exe: pin assign miso 3 sck 5 mosi 6 reset 7
avrdude.exe: drain OK
ft245r: bitclk 4800 -> ft baud 2400
avrdude.exe: ft245r_program_enable: failed
avrdude.exe: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.
avrdude.exe done. Thank you.
Of course I have soldered the UART pinheader and connected it to the ISP connector by the diagram in this PDF: seeedstudio.com/depot/datasheet/ … eduino.pdf
If I add -F to the command line, it reads the fuses, but they’re not what they’re supposed to be. hFuse is 0xFF, lFuse is 0xFF and eFuse is 0x07. Lock bit is 0x3F. Writing the fuses doesn’t work, they’re back to the old values when avrdude does the verification. I haven’t tried to burn in a new bootloader due to these things failing.
What could be the problem, or is my Seeeduino just broken?