Avrdude (again)

Hi!

since the last topic didnt gave me a clear answer i'd like to start a new one:

Since the beginning i bought the board it doesnt work. Every time i try to upload the led program i get this:

avrdude: stk500_getsync(): not in sync: resp=0x00
avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51

Some info:
Arduino Diecimila (freeduino clone 00012)
Windows XP
No firewall or what so ever.
Com5, but the board is USB with FTDI USB Drivers.

When connected:
Pwr led always on
TX and RX blinks 3 times, then the "13" led blinks 3 tmes...then it stops

When trying to upload:
RX blinks blinks 3 times, then stops, then 3 times etc. until the error comes. TX and "13" blinks acfter Rx but only the first time then its off.
Pwr led is still on

When i hit the reset button:
nothing... (but i don't question my solder skills and its perfectly connected)

I tried the troubleshooting FAQ but it didnt help. I cant go back to the manfacturer cuz we bought it with 200 ppl together or so from some foreign country :smiley:

I dont have acces to a ICSP thingy..

can someone plz help? :smiley:

Have you tried forcing the Com port to be something different than 5?

nope, with the FTDI USB Drivers i can only pick com5

Plug the usb cable into another port or try loading version 0011. Make sure you are using the autoreset jumper or pressing the reset button.

Remove the AVR from the circuit.
Connect a wire between digital 1 and digital 0 (TX and RX)
connect to your computer via USB.
Run Arduino, and select the serial monitor.
Type stuff in the send window and see if it echos back when you send.

Report back. If this works, it shows that the FTDI chip and drivers are operating properly and the problem lies elsewhere.

Change this serial port setting: Device Manager -> Com Ports -> USB Serial Port -> Port Settings -> Advanced button -> Set RTS On Close"

Hi again!

thanks for help!
I shirted port 1 and 2 (tx and rx) together and when i type something i can see it appear on the program. I also tried hyperterminal and that works too :stuck_out_tongue:

bootloader issue?