328P to 328P-PU bootloader UNO

Greetings

I am trying to burn bootloader to a uno with a 328P-PU (target). The "programer" uno has a 328P chip.

Here are the steps I have followed

  1. Upload ArduinoISP sketch to new uno (programer)
  2. Connecting target to programmer per:

https://support.arduino.cc/hc/en-us/articles/360012048080-How-to-burn-the-bootloader-between-two-Arduino-UNO

  1. Changed Programmer to Arduino as ISP
  2. Burn Bootloader

I did not change or edit the avrdude.conf (hardware\tools\avr\etc)

the error I get:

Error :
Error while burning bootloader.
Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.
Double check connections and try again, or use -F to override
this check.

Please help, thanks in advance!

Can you show a photo of YOUR wiring please. Hopefully it's an easy fix.

uno with plastic case is the programmer.

Looks OK. Can you swap the jumper cables, just incase one is faulty!

new jumpers = same error

avrdude: Device signature = 0x000000 (retrying)

Error while burning bootloader.
Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.
Double check connections and try again, or use -F to override
this check.

avrdude done. Thank you.

Doesn't the programmer Uno need to have its reset disabled after the ArduinoISP sketch has been loaded ? A 10uF cap from the programmer's reset to ground.

Reply #5 of this thread.

Tried it with a 100 UF cap and still same error.

Do you have access to an oscilloscope? you could test the pins on the ATMEGA to see if there is activity.

It could be a dead ATMEGA, though I have seen faulty crystals(Resonators) as well. Do you have onther ATMEGA to swap over on the 'dead' board?

Yes but the symptom would not be a "Device signature = 0x000000". The UNO bootloader will return the signature for an ATmega328p. Problems will happen later, typically a verify error because the bootloader doesn't actually write to the fuses or bootloader area.

Thanks for all the feedback.
Unfortunately I do not have access to an oscilloscope. Nor do I have access to a spare ATMEGA.

If I do not want to replace any hardware on the target UNO, at what point do I call the board bricked?

You can get the “mighty core” from git , that may well do it as you can select the 328 processor type in that ( worth a punt)

The core to use if you have the mega328 (Uno, Nano) use the MiniCore core. The MiniCore core is available through the IDE Boards manager.

Agree - I get them confused !!

1 Like

To test if the board is faulty, or just the chip, you could swap the 328 between the 2 boards, and test the currently non working board. This would tell you if it is the Chip, If it is, a couplke of Pounds/Euros/Dollars would get you up and running.

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