Expected signature for ATmega328P is 1E 95 0F error while burning bootloader.

Hello folks,

First time posting here. Full disclosure I am a n00b with the the finesse points of an arduino. I am not sure how avr dude works (if anyone knows of a good online tutorial it would be appreciated).

Already spent a bit searching for this problem but it seems the most threads that came up with this issue were around actually having the wrong chip selected.

Problem:
So I browned out 2 nanos on my project before discovering the culprit power supply. I have a third one that is functional and I am using it to burn a bootloader onto either of the fried ones and I end up with the error in the title.

Method: I have uploaded the Arduino ISP sketch to the functional board (all boards are Nano clones using the CH340G USB communications and all boards having ATMEGA 328P chips) and have it connected up per MISO to D12 SCK to D13 RST to D10 MOSI to D11 and vin and gnd hooked to the appropriate pins on the source board.

I then change the IDE to use Arduino as ISP on the programmer and ensure the 328P is selected on the processor. Then I hit "burn bootloader" and we end up with the titled error.

Any help around this would be appreciated. I am going to forge ahead with using the functional board for my project but I would like to salvage the other two if possible.

Thanks in advance,

I_V

EDIT: So I read up a bit more and found that Verbose output might provide more useful info, here is what it spit out.

avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

Using Port : COM10
Using Programmer : stk500v1
Overriding Baud Rate : 19200
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x03
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x03
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

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

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

avrdude done. Thank you.

Double check your wiring and lead continuity.

Checked and triple checked.

Replace them. Hang on to the bad ones and come back later to re-test after you have practised burning bootloader on ones that work.

So I checked my connections and burning bootloader practice by burning the appropriate bootloader onto an ATTINY 84 and then uploading the blink sketch to it. I am wondering if the brownout reset some fuses responsible for identification, that is a real loose theory from reading into this further.

I don't think a brownout will normally cause any problems. Over voltage however, will let the smoke out permanently. :slight_smile:

If the nanos you are trying to bootload were working, but stopped working after connecting to a bad power supply, that would imply that you damaged the hardware; burning the bootloader is unlikely to rectify the situation if you're even able to do so (ie, the chip isn't damaged in a way that prevents it from being programmed)....

The suspect powersupply was a 12v adapter connected to the vin pin. I figured if the issue was an over voltage it would have taken out the voltage regulator. But well, looks like i have 2 itty bitty bricks now.

Indian_Villager:
The suspect powersupply was a 12v adapter connected to the vin pin. I figured if the issue was an over voltage it would have taken out the voltage regulator. But well, looks like i have 2 itty bitty bricks now.

Hm, 12v on Vin shouldn't do that, I agree. It shouldn't even kill the voltage regulator.

I also just now noticed the signature you were reading. Check the state of the reset pin; could it be that it's being held low somehow? IIRC, if the reset pin isn't released between programming operations, the next attempt reads out consecutive numbers. Do you have the expected 5v on Vcc?

Also, is that the full programming output, or is there a second similar (but successful) programming operation before that? (I could have determined this if you had included the line immediately before what you posted, which contains the avrdude invocation that produced the error.

Hey,

Thank you for taking the time to reply,

I just tried it again.

Here is the error I get when I first try to burn the bootlaoder

Arduino: 1.8.5 (Windows 10), Board: "Arduino Nano, ATmega328P (Old Bootloader)"

C:\Users\myname\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/bin/avrdude -CC:\Users\Alex John\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM10 -b19200 -e -Ulock:w:0x3F:m -Uefuse:w:0xFD:m -Uhfuse:w:0xDA:m -Ulfuse:w:0xFF:m

avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

System wide configuration file is "C:\Users\myname\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/etc/avrdude.conf"

Using Port : COM10
Using Programmer : stk500v1
Overriding Baud Rate : 19200
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x15
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x15
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

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x14

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x02

avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x10
Hardware Version: 4728160
Firmware Version: 0.4598883
Topcard : STK502
Vtarget : 1.8 V
Varef : 0.0 V
Oscillator : Off
SCK period : 0.1 us

avrdude: stk500_initialize(): (b) protocol error, expect=0x10, resp=0x01
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.

avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x10

avrdude done. Thank you.

Error while burning bootloader.

Second Consecutive attempt

Arduino: 1.8.5 (Windows 10), Board: "Arduino Nano, ATmega328P (Old Bootloader)"

C:\Users\myname\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/bin/avrdude -CC:\Users\Alex John\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM10 -b19200 -e -Ulock:w:0x3F:m -Uefuse:w:0xFD:m -Uhfuse:w:0xDA:m -Ulfuse:w:0xFF:m

avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

System wide configuration file is "C:\Users\myname\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/etc/avrdude.conf"

Using Port : COM10
Using Programmer : stk500v1
Overriding Baud Rate : 19200
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x03
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x03
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

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

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

avrdude done. Thank you.

i am having the same issue with you while burning the bootloader.ive even edited the avrdude.conf file but still the same issue.

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

OP - I think those boards are aced; not knowing what's wrong with the power supply that seemed to kill them, I couldn't venture a guess on how it led to that result. That said, a 12v power supply is pushing it for a 5v linear regulator. 9v is better, and 7v is better still.

wattsbleeder:
i am having the same issue with you while burning the bootloader.ive even edited the avrdude.conf file but still the same issue.

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

You should not edit avrdude.conf except to add new entries. You should not do it to make it misidentify a 328 as a 328p - instead, you should use minicore.

You should not hijack other people's threads unless you have the exact same problem.

Enable verbose uploads to see what signature it is seeing. If it's 000000 it's a wiring problem. If it's 1E9-something, the chip is not an atmega328p - recheck the markings on the chip. If it's a 328 (not p. There is no dash between the 8 and the p, do not confuse a 328-PU with a 328P-PU), or a 88/168, use minicore.

Only if you get signature 000102 might you have the same problem as the OP in this thread!

Pardon the delay boss I was out on vacation. Thank you for reading into the situation. To the great recycling bin they go.