1

Topic: Firmware upgrade error? "avrdude: stk500_getsync(): not in sync:"

So after stumbling through the firmware upgrade process as best as I understand it, I am getting the following error trying to upload the firmware.

Binary sketch size: 52398 bytes (of a 63488 byte maximum)
avrdude: stk500_getsync(): not in sync: resp=0x00
avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51

Much googling yields a bunch of various "reset" strategies, but none of them seem to work for me. I also stumbled upon another thread that seems similar to my issue.

soliforum.com/topic/522/firmware-update-problem

Thoughts?

2

Re: Firmware upgrade error? "avrdude: stk500_getsync(): not in sync:"

I was in the same boat as you. Couldn't get it to update - no matter what I tried. I then ordered a 1284P microprocessor to swap instead of the 644P. Flashing works fine now. I bought it from here: http://cgi.ebay.com/ws/eBayISAPI.dll?Vi … 1159576371

This is sort of a last resort solution in case nothing else works.

3

Re: Firmware upgrade error? "avrdude: stk500_getsync(): not in sync:"

Happened to have a USBasp from my multirotor projects and after some fiddling managed to burn a new boot loader onto the board and successfully upload the latest firmware!

4

Re: Firmware upgrade error? "avrdude: stk500_getsync(): not in sync:"

Dave thanks for the link. I just order that chip as I too can't get the flash upgrade to work. Figure I'll still have the old one if teh new one doesn't work.

5

Re: Firmware upgrade error? "avrdude: stk500_getsync(): not in sync:"

I tried doing the update on the installed chip but got this error in Arduino 0022:

Error compliling.

core.a(main.cpp.o): In function 'main':
C:\SolidoodleFirmare\arduion-022\hardware\Sanguino\cores\cpp: 7: undefiend reference to 'setup'
C:\SolidoodleFirmare\arduion-022\hardware\Sanguino\cores\cpp: 10: undefiend reference to 'loop'

I jsut downloaded everything so it's recent.

6

Re: Firmware upgrade error? "avrdude: stk500_getsync(): not in sync:"

I think they've had issues more recently with bootloaders on chips.  Don't quote me but I think I remember seeing a few people with the same issue more recently.