Go Down

Topic: atmega16u2 bootloader not working (Read 2282 times) previous topic - next topic


Aug 28, 2013, 11:25 am Last Edit: Aug 28, 2013, 12:12 pm by aureliusss Reason: 1
hi everyone, i uploaded the hex file i found in the path arduino-1.5.2\hardware\arduino\sam\firmwares\atmega16u2\Arduino-DUE-usbserial.hex into my arduino based board on which i put an ATMEGA16u2 but it doesn't work. when i try to upload a sketch the ide stops saying "no device found on com".

thus i tried to upload the on the sam3x of my own board through the atmega16u2 mounted on an arduino due, connecting power supply and serial communication lines: i made it.

could it be that different packages means different bootloader?

is there anyway to copy the firmware flashed in the atmega16u2 of an ArduinoDUE?


i made into copying the bootloader from the atmega16u2 of the arduino due(or at least i guess i made it)
using an arduino uno as isp i wrote on the CMD the following line:
your_path\arduino-1.5.2\hardware\tools\avr\bin>avrdude.exe -C avrdude.conf -c arduino -P COM9 -b 19200 -p m16u2 -vvv -U flash:r:bootloader.hex:i

this is totally different from the one assumed to be the right one in the IDE folder.
did i get wrong reading the firmware from the arduino due board or the hex file given in the IDE is not the one that should be?

i don't have another arduino due to try. please let me know


Hello Aureliuss,

I regret that I cannot help you right now with your test. And may be you are already aware of this step-by-step tutorial from the Arduino team, but here the link just in case:


Good luck!


this is(attached below) the firmware i read from 3 different Arduino DUEs. can anyone tell me if it is the same on their boards?


To verify whether the flash content is identical to the that of a given hex file you can use avrdude:
specify the given hex file, and as memory operation specify v for verify, like this:
Code: [Select]

... -U flash:v:path_to_hex_file.hex:i

This avoids the problem that avrdude writes the hex file with a different record length compared to the hex file produced by building the bootloader.

That said, if anyone can suggest a good (linux) utility to convert intel hex to binary, I would be interested. (so you could just compare two differently formatted hex files).

Go Up