Hello.
I've experienced some problems with one of my arduino uno r3 and I've come to the conclusion that it is a problem with the Atmega 16u2 chip. I have then tried to follow this tutorial on how to reset it:
However, it says that, when connecting the jumper between reset and GND, my computer continues to recognise the Arduino.
Please help, is my arduino dead or it can be still saved?
So you want to get your Arduino into DFU mode but your computer doesn´t recognise it as "Arduino Uno (DFU)" even if you connect reset pin and GND pin?
That's exactly whaat happens. Even when onnecting reset to GND, the computer continues to recognise it as an Arduino Uno, not as Arduino Uno DFU or anything similar
A couple of ways to get the firmware on the 16U2 chip.
I just updated an atmega16u2 on an Uno Clone using Linux Mint and IDE1.8.5.
$ locate atmegaxxu2
I then cd into:
cd /home/kprims/ken/Downloads/arduino-1.8.5/hardware/arduino/avr/firmwares/atmegaxxu2
Check out the README.txt
I used the avrdude command for the Uno v3 and changed it to this.You may have to use the avrdude with the arduino IDE. Something like this:
/home/kprims/.arduino15/packages/arduino/tools/avrdude/6.3.0-arduino14/bin/avrdude -C/home/kprims/.arduino15/packages/arduino/tools/avrdude/6.3.0-arduino14/etc/avrdude.conf -v -p atmega16u2 -cstk500v1 -P/dev/ttyACM0 -b19200 -U flash:w:Arduino-COMBINED-dfu-usbserial-atmega16u2-Uno-Rev3.hex -U lfuse:w:0xFF:m -U hfuse:w:0xD9:m -U efuse:w:0xF4:m -U lock:w:0x0F:m
Notice I changed the -p atmega16u2 , the -c usbasp and the Arduino-COMBINED-dfu-usbserial-atmega16u2-Uno-Rev3.hex
If you are using arduino as isp you would use -cstk500v1 -P/dev/ttyACM0 -b19200
avrdude -p atmega16u2 -P usb -c usbasp -U flash:w:Arduino-COMBINED-dfu-usbserial-atmega16u2-Uno-Rev3.hex -U lfuse:w:0xFF:m -U hfuse:w:0xD9:m -U efuse:w:0xF4:m -U lock:w:0x0F:m
Did it work for You?
Did it work for You?
No, it didn't work. I just wanted to waste your time and mine.
I didn´t ask you kprims.
Hello,
I've experienced some problems with one of my arduino uno r3 and I've come to the conclusion that it is a problem with the Atmega 16u2 chip
Have you ever removed the IC?