Go Down

Topic: Can't upload a sketch from the IDE to my bare-bone Arduino Nano (Read 2 times) previous topic - next topic

magagna

The standard Nano you have is using the Duemilanove bootloader, which works at 57600. Even though it's a different form factor, you program it by picking "Duemilanove" from the board type menu.

The Uno uses OptiBoot for its bootloader, which works at 115200 baud. It's the new standard because it's smaller (512 bytes vs about 2K). When you burned your new standalone chip you got OptiBoot.

So, if you treat your new Nano clone as a Uno, everything should work fine.

Good luck!
http://en.wiktionary.org/wiki/magagna <-- My last name.  Pretty apt.

retrolefty


The standard Nano you have is using the Duemilanove bootloader, which works at 57600. Even though it's a different form factor, you program it by picking "Duemilanove" from the board type menu.

The Uno uses OptiBoot for its bootloader, which works at 115200 baud. It's the new standard because it's smaller (512 bytes vs about 2K). When you burned your new standalone chip you got OptiBoot.

So, if you treat your new Nano clone as a Uno, everything should work fine.

Good luck!



Yes he somehow loaded the Uno's bootloader onto his standalone nano setup. That will work if he selects the Uno as the board selection prior to performing a IDE serial upload.

However he will lose I believe the ability to use the extra 2 analog input pins that the nano's version of the SMD 328p chip has. If he wants those back be has to edit the nano/328 entry in the core's boards.txt file to reflect having the Uno's bootloader name, path, baud rate, fuse bytes, memory size, etc.

Lefty

magagna

Quote
However he will lose I believe the ability to use the extra 2 analog input pins that the nano's version of the SMD 328p chip has. If he wants those back be has to edit the nano/328 entry in the core's boards.txt file to reflect having the Uno's bootloader name, path, baud rate, fuse bytes, memory size, etc.


No need for anything like that. A6 & A7 are defined in pins_arduino.h, which is common for all "standard" board entries.
http://en.wiktionary.org/wiki/magagna <-- My last name.  Pretty apt.

retrolefty


Quote
However he will lose I believe the ability to use the extra 2 analog input pins that the nano's version of the SMD 328p chip has. If he wants those back be has to edit the nano/328 entry in the core's boards.txt file to reflect having the Uno's bootloader name, path, baud rate, fuse bytes, memory size, etc.


No need for anything like that. A6 & A7 are defined in pins_arduino.h, which is common for all "standard" board entries.


If that is true why does the core's board.txt have an entry for just some boards but not for instance the Uno board?

#nano328.build.variant=eightanaloginputs

Lefty

szangvil

Defining the board as Uno does the trick and lets me upload the sketch.
What I don't understand is that I BURNED the SAME bootloader to both Nanos (mine and the standard). And to the standard, there was no problem and it acted "normally" where mine does not.

Go Up