Bad signature while burning bootloader

Using Arduino Microcontrollers
1

Hello, I have a sparkfun redboard using the ATMEGA328P chip to which I cannot upload code. The loopback test works and so I'm trying to burn the bootloader onto the redboard using a working arduino uno using the same chip. I have it hooked up using old style wiring (yes, I did uncomment line 81 enabling me to use this wiring configuration) and have triple checked connections and that the target board is selected under tools. Still I am receiving garbage device signatures whenever I attempt to upload the bootloader. The verbose upload response is as follows:

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\andre\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino17/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.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

Is there a way to fix this or is my reboard just bricked?

2

This error points to bad wiring. All zero response means there is no connection to the target. Occasional FF looks like floating wire but hard to say. Post your wiring setup.

What does it mean?

It is good to post log with uploading command at the beginning. It could help.

3

I've been following the guide provided at https://docs.arduino.cc/built-in-examples/arduino-isp/ArduinoISP. I am using the basic ArduinoISP example and mentioned line 81 as it defines the variables for burning the bootloader using the old school wiring setup. Uncommenting this line is the only change I have made to the example sketch.

If you think it would be beneficial still I can upload the code despite it being amongst the basic examples. I've tried a great deal to get this working and went through a number of old posts in the forum experiencing similar issues to make it this far. I might have to test my jumpers and connections whenever I come back to this tomorrow. Thank you for your time and consideration.

4

I would say it is wiring/setup problem. In 99% of cases I've read on the forum it was so. Focus to this at first.
Of course, there is a minor chance the 328P is damaged. In this case the biggest obstacle is SMD chip If this is your board

6

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