Arduino Nano - avrdude: stk500_getsync(): not in sync: resp=0x00

Hi -

I have an Arduino Nano Rev 3.0 which has worked well for some time.

After uploading a program yesterday, the Nano cannot be bothered to upload anything new, the IDE returns avrdude: stk500_getsync(): not in sync: resp=0x00.

When I connect the Nano to a serial port and read it's output, it still executes the program that I uploaded last and provides some date over the serial port. Reset button just starts the program in flash over and over.

I have reinstalled the USB and serial drivers on my Mac, no different results.

Any suggestion would be welcome.

Thanks, Ralph

I've just got the same problem. I think it may possibly be a windows COM port thing.

My desktop gives me this error:
avrdude: stk500_getsync(): not in sync: resp=0x00

However, my laptop still programmes it fine....

...EDIT:

Just used a USB hub on my desktop, programmes fine through that. Just the USB ports on the towers not working (all of a sudden, fine before).

Very odd

I had issues like this but in the end it turned out to be the USB cable. you probably have but if you have not, id suggest trying a different one.

I have an Arduino Uno giving the same error. It was working well all this while (about 3 months.) I mounted an Arduino compatible L298N shield that drives a couple of DC motors.

Using Port : \.\COM5
Using Programmer : arduino
Overriding Baud Rate : 115200
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Recv:
avrdude: stk500_getsync(): not in sync: resp=0x00

avrdude done. Thank you.

When I try to upload a sketch, the TX led flickers but there is absolutely no response from the RX led. What could be the issue? Is there a chance that the board got short-circuited?
Any help appreciated, thanks a lot.

I had the exact problem last week with a new ATMega 328 chip. Turns out the baud rate in the new chip that I swapped in was different than my config file. Loopback worked, but avrdude didn't. I futzed around with baud rates until I found one that matched what the new chip was programmed to read at. Good luck.