Seeeduino Nano stuck on uploading: programmer is not responding

Hello,

recently I bought a couple of Seeeduino Nano boards and worked with them. Everything worked fine until from one moment on, I am not able to upload my code anymore. I checked many posts on this topic but none apply to me. I have 2 boards that I currently work with and both fail to upload. I also own an Arduino Uno board that uploads successfully. Some more info:

  • I'm trying to upload the "Blink" program from examples to the board
  • I have nothing connected to the board, just the USB cable
  • Board, processor, and port are picked correctly

Do any of you have suggestions on how to deal with this?

Here is the error message copied:

Arduino: 1.8.19 (Windows 10), Board: "Arduino Nano, ATmega328P"

Sketch uses 924 bytes (3%) of program storage space. Maximum is 30720 bytes.

Global variables use 9 bytes (0%) of dynamic memory, leaving 2039 bytes for local variables. Maximum is 2048 bytes.

C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avrdude -CC:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -carduino -PCOM4 -b115200 -D -Uflash:w:C:\Users\nejco\AppData\Local\Temp\arduino_build_48585/Blink.ino.hex:i 



avrdude: Version 6.3-20190619

         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/

         Copyright (c) 2007-2014 Joerg Wunsch



         System wide configuration file is "C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf"



         Using Port                    : COM4

         Using Programmer              : arduino

         Overriding Baud Rate          : 115200

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0xbd

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0xbd

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0xbd

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0xbd

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0xbd

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0xbd

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0xbd

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0xbd

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0xbd

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0xbd



avrdude done.  Thank you.



Problem uploading to board.  See https://support.arduino.cc/hc/en-us/sections/360003198300 for suggestions.



This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

Try to hold down the reset-button for a while and during uploading.

I had this problem with a new Elegoo Nano board which looked exactly like my old ones. It turned out that the old ones needed the "old bootloader" but the new ones the standard. Might work for you?

Tried it, no difference.

Tried this as well and still won't upload. I already worked with this board and it used to work with the default bootloader.

Try to select a different bootloader in Arduino.

Tools -> Processor - > ATmega328p (Old Bootloader)

Already tried it, still doesn't work.

I think there is little ESD protection on the pins for this microprocessor. Could be broken.

Could be, is there any way to check this?
I find it a bit unlikely to have 2 boards with the same problem though.

Might be unlikely but possible, do not throw them out just yet. To my experience they do however fail easily.

Checking might be difficult and I am not an expert there. Maybe you could measure pin activity on boot or otherwise, some microprocessors put out specifics I think...

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.