Arduino Nano MEGA 328P

Development Tools Uploading
1

I have recently moved on to my first Nano however, upon my first attempt at uploading a sketch I get an error message.

Using Port : COM1
Using Programmer : arduino
Overriding Baud Rate : 57600
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0xae
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0xae

this continues on until it reaches 10 and ultimately fails, when I go into tools my I cannot connect to a com port, my processor is "ATmega 328P old (bootloader)" and my programmer is ArduinoISP.org.

3

Select Tools > Processor > ATmega328P and then try uploading again.

4

When you plug in the Nano, does a different COM port show up under Tools:Port?
Select that new port.

For example, my Port shows COM3 when no hardware is connected, I would guess yours shows COM1 when no hardware is connected.

5

I get COM1 with no hardware and COM5 when hardware is connected, I choose COM5 but the same problem as before comes up

avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0xae
avrdude: stk500_recv(): programmer is not responding

its definitely an issue with the programmer for this board not responding, I not sure what to do to fix this.

6

Do you have the correct driver for the USB chip on your Nano?
Flip it over. Is the chip next to the USB connector an FT232 or something else?
FTDIchip.com has FT232 drivers.
VCP Drivers - FTDI
2.12.28 is what is running on my Win10Pro machine.

The "Programmer" selected does not matter, that only comes into play when you connect a Programmer to the ICSP header, usually for instaling a bootloader into the 328P, when then talks to the PC via serial interface for downloading the sketch.

A Programmer will also let you download the latest bootloader into the Nano. I bootload all my 328P chips as an Uno so I don't have to keep track of what chip has what.
This inexpensive Programmer is very handy. Can be connected to an ICSP header (or the equivalent pins) for bootloading, or it can be used as a USB/Serial interface if you are loading code into a ProMini for example.

Free shipping to US addresses. Good tool to have.

7

im going to look further into this AVR programmer and how to use it, and I will get back to you asap with the results, thanks!

8

One thing I've noted this week - nanos I bought last month, from the same supplier I bought from a year ago, have suddenly become compliant with the new loader, not the old loader. Same messages as you; I pulled a lot of hair finding that one, as the info on Amazon still stated "old bootloader". Try that, it might work.

9

Just get a Programmer and rebootload them so you know what you have, skip all the guessing games.

10

So, will the older Nano 'take' updated code, or would I have to backdate the new Nanos with an old bootloader? Do you know? Right now, I have 5 I program with the old bootloader, and 10 I will program with the new one.

11

I've ordered the AVR programmer, should be here tomorrow

12

" will the older Nano ‘take’ updated code,"
Yes, as long as you select the right processor/bootloader in the IDE menu.

If you rebootload them all to be Unos, then you can just select the same thing in the IDE for every board, no more guessing as to what the processor has for a bootloader. And you gain some Flash memory space back too.

13

Either bootloader can be used on any nano, there is no difference in the hardware. If you are going to be changing the bootloader, do not use either Nano bootloader, use the UNO bootloader then select UNO when compiling code for the boards, this will give you an additional 1.5K bytes of flash memory for your code.

A bit of history on the Nano bootloader. The original ("old") bootloader required that 2K bytes of flash memory be allocated for the bootloader. The current ("new") bootloader only needs 0.5K bytes of flash memory, but the 2K byte allocation was not changed for some reason (possibly for compatibility purposes, because that could result in code working with the new bootloader but failing to compile because of lack of memory with the old bootloader). The "new" bootloader is optiboot, the same bootloader used on the UNO, but in the case of the UNO the proper allocation of flash memory is used for the bootloader.

14

Thank you, David, that was the underlying reason I was seeking. Guess my older set will be be updated at some point.
Thanks again

15

And thank you, Crossroads.

16

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