Bootloader fails to load?

I have 2 Uno R3's and 3 atmega 328p chips.
Until recently all 3 chips worked in both Uno's.
1 chip stopped working so, thinking it might be a bootloader problem I loaded the Arduino ISP sketch from examples into the good arduino, connected both arduino's up with the ICSP socket, The 'burn a bootloader' advice from arduino support shows both mosi connected to mosi and miso connected to miso, is this correct? That is how I connected them. Put the suspect chip on the other arduino , selected Arduino AS ISP, checked the port and clicked on 'burn bootloader' I got
"avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x03"
I checked the address of avrdude and avrdude .conf are correct.
I replaced the chip on the 'other' arduino and tried again with the same result?
If I separate the arduino's I can get both to load the blink sketch successfully when the good chip is in place but not the suspect chip?
I checked I have a good connection between the Uno's with a test meter on the pins on the underside of both Uno's.
Before I do anything else I always disconnect the power.
Should the bootloader at least load onto a good chip?
I have never tried to burn a bootloader before now.

Just last week I tried the same thing using this post:

and had to use the "trick" of adding the clock line from "pin 9", but was able to put a boot loader onto 5 328P chips from DigiKey. The link was VERY helpful.

MMM I worked through the example for one chip arduino and the bit on bootloading , it sends you here, added the board info, connected up as it said (one says use a 0.1 micro farad cap so I tried both ways). With my good chip I get 'did not find any USB device ... failed chip erase'
I selected Arduino AS ISP and ran it again on my good chip, now I get my original errors.

Did you check that you got the right port for the programmer?

For me, I didn't get success until I put the 0.1uF cap directly across the body of the chip between the power leads; also, make sure the DTR from the USB to Serial output is active when you get to programming the new chip with the bootloader on board. I found I had to swap what I thought were "good" serial converters.

mmm I wonder if I did get the wrong port, when I do it now I get


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:\Users\User\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino17/etc/avrdude.conf"

         Using Port                    : COM10
         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.03s

avrdude: Device signature = 0x000000 (retrying)

Reading | ################################################## | 100% 0.03s

avrdude: Device signature = 0x000000 (retrying)

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

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

avrdude done.  Thank you.

Failed chip erase: uploading error: exit status 1

I tried with a 0.1 uF cap across pins 7 and 8 of the chip (connected to 5v and gnd) and with it removed.
I have a led and resistor across the power and gnd on the breadboard so I can see there is power to the chip.
It happens with both the good chip and the one I suspect has no bootloader in it.
Can you see what might be wrong?

I don't have an interpretation on what you attached, but I used the ATmega328P DIP chips from DigiKey and had to use the extra line from my Uno to generate the 50% PWM clock to flip the internals and undo the boot loader that was already stored in the chip that was expecting to see a crystal or oscillator attached. And, I put an LED with a resistor on the RESET pin 1 to watch it go low from the DTR connection when programming my own code via the serial connection once the internal oscillator boot loader was put onto the chip from my Uno board as per the instructions in the Instructables page. Sorry, just anecdotal "help" I'm afraid.

Also, my .1 cap was physically across the chip between pins 7 and 22, as shown in the Fritzing picture in the Instructable. That surprised me that it didn't work when connected otherwise ...

I've learned the cap is only used for only a few models, but it won't hurt if you use it anyway.

Only thing I can think of is if the chip got the wrong clock settings.

If you have two Unos, then use one as the ISP programmer and use the other to hold the target IC you are trying to program, then just burn the bootloader.

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