uploading error

i have the freeduino sb and i was able to upload before. suddenly it started coming up with an error.
avrdude: stk500_getsync(): not in sync: resp=0x00

i have no idea what it means and it is super incredibly frustrating. i have tried 10 guides and all of the solutions failed. i tried resetting, compiling, updating drivers, and everything. sometimes when i try uploading the rx led flashes but the tx led never flashes except for right when i power on the arduino.What can i do?

Sorry no help here other than I am having the exact same problem with a brand new Arduino UNO. Same error same non flashing TX light. I am using the Arduino-1.0 Software. I have tried the driver Windows preferred, the UNO.inf file and the UNO Rev3.inf file drivers. Changed com ports and com port settings (baud rates, port number) and have the exact same error everytime. I have not gotten it to connect once. Same error from the very first time.

Hopefully someone has an idea. I think I am going to try an earlier software revision anyway just to see what happens.

Has anyone catalogued a list of the errors? I know if I switch it to the wrong com port in the tools dropdown the error changes from "resp=0x00" to "resp=0x30".

Curious to see what the problem turns out to be.

Do the loop-back test please (see below).

I also have a brand new UNO i purchased last week that I cannot upload any sketch to.

Yes, I read through the guides and tried swapping cables (I am using the same cable that sucessfully programs a Mega 2560), updated to newest version that I could find (arduino 1.0), changed drivers, etc.

When I do the loopback test I enter "testtesttest" and it responds with
"testt" and nothing further on any subsequent entries to it.
I have to do a power down cycle for it to respond again.

When I try to upload blink this is what it says:

Binary sketch size: 1026 bytes (of a 32256 byte maximum)

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x41

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x41
avrdude: stk500_initialize(): (a) protocol error, expect=0x14, resp=0x42
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.

avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51

When I press shift upload:

Binary sketch size: 1026 bytes (of a 32256 byte maximum)
avrdude: usbdev_open(): did not find any USB device "usb"

I can see the arduino listed in windows' device mangler com ports as com 11. It also will go away when unplugged and return working properly when plugged back in.

If I use arduino ver 00.22 and it's UNO driver, with a shift upload then this is what it prints:

Binary sketch size: 1018 bytes (of a 32256 byte maximum)
D:\arduino\arduino-0022\hardware/tools/avr/bin/avrdude -CD:\arduino\arduino-0022\hardware/tools/avr/etc/avrdude.conf -v -v -v -v -patmega328p -cstk500v1 -P\.\COM11 -b115200 -D -Uflash:w:C:\DOCUME~1\STUDYC~1\LOCALS~1\Temp\build4371714467456052767.tmp\Blink.cpp.hex:i

avrdude: Version 5.4-arduino, compiled on Oct 11 2007 at 19:12:32
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/

System wide configuration file is "D:\arduino\arduino-0022\hardware/tools/avr/etc/avrdude.conf"

Using Port : \.\COM11
Using Programmer : stk500v1
Overriding Baud Rate : 115200
avrdude: ser_open(): setting dtr
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Recv:
avrdude: Recv:
AVR Part : ATMEGA328P
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PC2
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :

Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack


eeprom 65 5 4 0 no 1024 4 0 3600 3600 0xff 0xff
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack


flash 65 6 128 0 yes 32768 128 256 4500 4500 0xff 0xff
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack


lfuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack


hfuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack


efuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack


lock 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack


calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack


signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00

Programmer Type : STK500
Description : Atmel STK500 Version 1.x firmware
avrdude: Send: A [41] . [80] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x86
avrdude: Send: A [41] . [81] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x18
avrdude: Send: A [41] . [82] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x18
avrdude: Send: A [41] . [98] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x00
Hardware Version: 4174060
Firmware Version: 4417552.4368076
avrdude: Send: A [41] . [84] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x86
avrdude: Send: A [41] . [85] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x86
avrdude: Send: A [41] . [86] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x00
avrdude: Send: A [41] . [87] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x18
avrdude: Send: A [41] . [89] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x1e
Vtarget : 201333138.4 V
Varef : 229372.8 V
Oscillator : 0.002 Hz
SCK period : 2184798758.7 us

avrdude: Send: A [41] . [81] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x66
avrdude: Send: A [41] . [82] [20]
avrdude: Recv:

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x60
avrdude: Send: B [42] . [86] . [00] . [00] . [01] . [01] . [01] . [01] . [03] . [ff] . [ff] . [ff] . [ff] . [00] . [80] . [04] . [00] . [00] . [00] . [80] . [00] [20]
avrdude: Recv:
avrdude: stk500_initialize(): (a) protocol error, expect=0x14, resp=0x06
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.

avrdude: Send: Q [51] [20]
avrdude: Recv:
avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51

avrdude done. Thank you.

The loop-back test should "echo" back everything you type, as often as you type and send. No power-cycling should be needed.

If that does not happen, there are a three likely possibilities:

  • you didn't follow the instructions word-by-word
  • something is wrong with the USB converter chip
  • winblows is confused

If you can exclude a confused operating system (either re-install - as a winblows user you should be familiar with that concept - or test it on a different machine) and this is indeed a new and unspoiled board, I'd consider getting it exchanged.

Thank you mad worm, Yes I think I followed the instructions word for word ( repeated this loopback test with the jumpers several times).

Sometimes I will get a longer echo but still only one line. I do notice that both LEDs tx and rx light up, although it seems to me that the baud rate is very slow, because they stay on for 5-10 seconds with a sentence like this sent:
"now is the time for all good men to come to the aid of their country"

Oh, I also did test this board out on two different windblows machines (win 7 and win 2K) same ol same ole. :frowning:

What is the preferred way to get this board exchanged?
Thanks again

10 seconds seems quite hilarious. Did you try setting the port speed to something higher, like 115200? I mention 115200, as this speed is what the bootloader of the UNO expects. If that doesn't work on the hardware level, get a replacement.

Still testing this one on a different machine may be useful. Just in case the seller will ask you to do the same :wink:

Yes I tried setting the port speed up to 115200, 9600, and in between. One other thing is that windows freaks out and shuts down access to the usb port after a few failures with this board and power cycling (unplugging the usb cable) does not fix it - only restarting the computer will clear the fault code. (its a wonder I have any hair left at all) :-D.
Thank you and I think I understand what I need to do, even though it is hard to know what the issue is (ie UNO bad design, just a bad board, software versions incompatible, board revisions flakey, or win#!@%&*$).

Thank you again.

Hi, an update:

After messing with the baud rate in both windows com port settings and the preferences file, I used hyperterminal to to another loopback test at 115200.
This loopback test worked and echoed everything back.

However on this win2k 'puter I could not get any sketch (BLINK) etc. to upload without an error uploading to board.
After sending an email to the seller requesting a return merchandise authorization for a failed board, and reading about IDE ver 1.0 probs with other people, I decided to use another 'puter.
That computer is running my mega 2560 data aquisition and monitoring system (win XP).
I did not want to mess up a working system by installing IDE ver 1.0 on it, but it would not recognize the UNO R3 under IDE Ver 0022.

SOLUTION:
I copied ONLY the UNO R3 driver from the computer with IDE Ver 1.0 .../arduino-1.0/drivers folder to the XP computer running IDE Ver 0022 in .../arduino-0022/drivers folder. After fussing with the workarounds to get it to recognize the UNO R3 in device mangler and switching from MEGA 2560 to UNO in the boards menu in the IDE, it uploads!!!:slight_smile:

Now I need to cancel the RMA and get back to work coding (been 5 days of fighting this).