Error uploading bootloader UNO to UNO

I double checked the connections but get the error below. Looks like the wrong device type is being read. I checked both processors and they are both a 328P.

Arduino: 1.8.13 (Windows 10), Board: "Arduino Uno"
C:_MyInstalls\Arduino\hardware\tools\avr/bin/avrdude -CC:_MyInstalls\Arduino\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM15 -b19200 -e -Ulock:w:0x3F:m -Uefuse:w:0xFD:m -Uhfuse:w:0xDE:m -Ulfuse:w:0xFF:m

avrdude: Version 6.3-20190619
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

     System wide configuration file is "C:\_MyInstalls\Arduino\hardware\tools\avr/etc/avrdude.conf"

     Using Port                    : COM15
     Using Programmer              : stk500v1
     Overriding Baud Rate          : 19200
     AVR Part                      : ATmega328P
     Chip Erase delay              : 9000 us
     PAGEL                         : PD7
     BS2                           : PC2
     RESET disposition             : dedicated
     RETRY pulse                   : SCK
     serial program mode           : yes
     parallel program mode         : yes
     Timeout                       : 200
     StabDelay                     : 100
     CmdexeDelay                   : 25
     SyncLoops                     : 32
     ByteDelay                     : 0
     PollIndex                     : 3
     PollValue                     : 0x53
     Memory Detail                 :

                              Block Poll               Page                       Polled
       Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
       ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
       eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
       flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
       lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
       hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
       efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
       lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
       calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
       signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

     Programmer Type : STK500
     Description     : Atmel STK500 Version 1.x firmware
     Hardware Version: 2
     Firmware Version: 1.18
     Topcard         : Unknown
     Vtarget         : 0.0 V
     Varef           : 0.0 V
     Oscillator      : Off
     SCK period      : 0.1 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x000000 (retrying)

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x000000 (retrying)

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

avrdude: Device signature = 0xff00ff
avrdude: Expected signature for ATmega328P is 1E 95 0F
Double check chip, or use -F to override this check.
avrdude done. Thank you.

Sort of, but this is actually just that no device signature at all is being read, rather than a situation where it's reading a legitimate signature from the chip, but just not the expected one (e.g., ATmega168 vs ATmega328P).

I know you said you checked your connections, but I recommend you to triple-check the wiring is like so:

Note especially that pin 10 on the programmer board is connected to the RESET pin on the target board.

If the connections are right, you might have a defective jumper wire. The internal electrical connections can sometimes break or become intermittent. you can check the continuity on each wire with a multimeter or LED or try swapping out the jumpers for different ones.

And then there is the elephant in the room that most people use "Burn Bootloader" as an attempt to resuscitate an Arduino board that has mysteriously stopped working. That does sometimes recover the board, but in the case of physical damage, no amount of "Burn Bootloader" can ever put the magic smoke back in the chip.

HI in0,
I checked everything again and it is wired properly. I have also tried a different set of wires - just in case. Still no joy. If I replace the 328P can I program the bootloader to it?

Do you have the capacitor between RESET and GND on the UNO being used as the programmer?

Hi David_2018,

I looked at two tutorials and neither mentioned a capacitor. What value of capacitor? And, do you know why it is necessary?

Capacitor is usually a 10uF electrolytic, and the purpose is to prevent the programmer UNO from resetting during the programming process. The USB to serial converter on the UNO can generate a reset when the serial connection between the computer and the UNO is established by the various arvdude commands - this is a normal process designed to reset the UNO and run the bootloader when uploading a sketch, but is not desirable when using the UNO as an ISP programmer.

HI David_2018

Still no joy. If I replace the 328P can I program the bootloader to it?