Yikes! invalid device signature

[GoogleCodeExporter]

What steps will reproduce the problem?
1. avrdude -p m8 -b 19200 -P com8 -c avrisp -F -e -U
flash:w:"D:/desktop/atmega/SID/monijonsyn.hex":a

similar error with all other tries.

- What is the expected output? What do you see instead?

i want to download the .hex file to the atmega8 (16)

if i dont do the -F in avrdude the error message comes earlier.
it then does erase and write stuff on the chip, but a mismatch in the end

- What version of the product are you using? On what operating system?

i use ur avrisp on winxp. downloading the avrisp.pde to my arduino seems to
work ok, the heartbeat led shines and the serial led turns on during comm.
the error led is never on.

can you help on that?

dusjagr

Original issue reported on code.google.com by dusjagr@gmail.com on 20 Mar 2008 at 5:27

Attachments:

• write_file_to_atmega8.jpg

[GoogleCodeExporter]

How is your arduino wired up to your atmega8 chip? avrdude is getting a 00 00 00
signature instead of the expected 1E 93 07. A wiring diagram or even a photo 
would
help. Could be a wiring problem or perhaps the mega8 chip is bad.

See http://www.flickr.com/photos/rsbohn/1067253851/ for a mega8 with the SPI and
other wires connected for programming. You need six connections to the mega8:

Power +5V (Pin 7)
Ground (Pin 8)

Reset (Pin 1) (Arduino Pin 10)

SCK (Pin 19) (Arduino Pin 11)
MISO (Pin 18) (Arduino Pin 12)
MOSI (Pin 17) (Arduino Pin 13)

(Arduino is the Master, the other Mega8 is the Slave)

Original comment by rsb...@gmail.com on 26 Mar 2008 at 8:09

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

I'm having this same issue (except with a attiny13V as the target):

Arduino Pin 10 -> ATTiny13V Pin 1 (RESET)
Arduino Pin 11 -> ATTiny13V Pin 7 (MISO)
Arduino Pin 12 -> ATTiny13V Pin 6 (MOSI)
Arduino Pin 13 -> ATTiny13V Pin 7 (SCK)

$ avrdude  -b 19200 -P /dev/tty.usbserial-FTDOMRGU -p t13 -c avrisp

avrdude: please define PAGEL and BS2 signals in the configuration file for part 
ATtiny13
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.10s

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.

(Arduino-0010, an a BBB Freeduino as the programmer).

Do I have the MISO and MOSI wired correctly?  I've tried it both ways, but get 
the same results. 

Original comment by james.neal on 1 Apr 2008 at 6:50

[GoogleCodeExporter]

I've noticed a mix up in the pin assignments. SCK is on 13 and MOSI is on 11. 
You can
either swap the wires on your arduino, or change the definitions in the sketch 
and
reload.

Original comment by voiknal...@gmail.com on 23 Apr 2008 at 10:53

[GoogleCodeExporter]

The correct pins (updated in avrisp.01.zip) on the Arduino side are:
13 SCK
12 MISO
11 MOSI
10 RESET

Original comment by rsb...@gmail.com on 27 May 2008 at 4:38

[GoogleCodeExporter]

avrdude -C "..\etc\avrdude.conf" -P com1 -p t85 -c avrisp -b 19200
No matter if there is a chip connected or not it always gives me the ATMega168's
signature.

When I try to override it to do something like read the first 10 bytes of flash
avrdude reports
"avrdude: stk500_cmd(): programmer is out of sync"

Original comment by EmperorA...@gmail.com on 10 Nov 2008 at 2:54

[GoogleCodeExporter]

Hello,

I am experiencing the same issue when trying to program the mega 168.

Steps to Reproduce
-Upload .pde to arduino master
-Connect wires (Master 13 -> 19, 12 -> 18, 11 -> 17, 10 -> 1, GND -> 8 & 22, 
VCC -> 7)
-The heartbeat LED is pulsing on / off; at this time, no other LEDs are lit.
-Try to connect with avrdude using command 'avrdude -p m168 -P
/dev/tty.usbserial-FTE0U36U -c avrisp -b 19200'

Observed Output
When you run the command, the heartbeat immediately goes out.  After about 2.5
seconds, the error LED flashes quickly for about three pulses, then goes off.  
At
this point the heartbeat comes on again.  At no point does the programming LED 
flash.

avrdude gives the following output:

avrdude -p m168 -P /dev/tty.usbserial-FTE0U36U -c avrisp -b 19200

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.05s

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.

Versions / OS
I am on Mac OS X 10.4, running Arduino 012.  I have avrdude compiled from 
macports,
at version 5.5.  I am using AVRISP version 0.2.

I would greatly appreciate any suggestions on where I may have gone wrong.  If 
you
need more information for troubleshooting, please let me know and I will be 
glad to
oblige!

Cheers

Original comment by wyatt.ol...@gmail.com on 12 Feb 2009 at 5:24

[GoogleCodeExporter]

I apologize, I am actually on arduino 013 (not that it would make much of a
difference in this case).

Cheers

Original comment by wyatt.ol...@gmail.com on 12 Feb 2009 at 5:25

[GoogleCodeExporter]

It goes well when arduino-0013/hardware/tools/avr/bin/avrdude is used. 

Original comment by arm...@gmail.com on 14 Feb 2009 at 1:20

[GoogleCodeExporter]

but I have error on next step.

$ ./avrdude -c avrisp -p m168 -t -P /dev/cu.usbserial-A60060V5 -b 19200 -C 
../etc/avrdude.conf

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e9406
avrdude> d efuse
>>> d efuse 
avrdude: stk500_recv(): programmer is not responding

Original comment by arm...@gmail.com on 14 Feb 2009 at 2:39

[GoogleCodeExporter]

Thank you arms22 - it appears that the programming works when using that 
version of
avrdude.  The programming finishes and verifies correctly.

Not sure about the issue you are seeing.

I still have not been able to actually run the program I uploaded, but I think 
that
may be an issue with the fuses being set incorrectly and not using the internal
oscillator... more testing should hopefully get this figured out.

Cheers

Original comment by wyatt.ol...@gmail.com on 18 Feb 2009 at 8:27

[GoogleCodeExporter]

It may help to add -v -v -v -v to your command line to avrdude. It will put out 
a lot
more text, but maybe something interesting will show up.

Glad to hear that Arduino 13 has an avrdude that works with avrisp sketch.

Original comment by rsb...@gmail.com on 25 Feb 2009 at 4:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have the same error message. I can program the ATTiny2313 with no problem 
(!), but
falied to program ATMega8 or ATMega328.
I use the mega-isp code shipped with arduino0018, and used avrdude version 
5.10, the
following command for the mega.

avrdude -c arduino -P com6 -p m8 -b 19200 -U hfuse:r:high.txt -v -v -v

Details attached. (I've also tried other combinations.)

Original comment by pram...@gmail.com on 24 Feb 2010 at 1:37

Attachments:

• ardude-out.txt
• DSC09926c.JPG
• DSC09926a.JPG
• DSC09926b.JPG

[GoogleCodeExporter]

This seems to be a documentation error. The documentation does not say anything 
about
internal/external oscillators. For an AVR fused to external oscillator (which 
is the
case for arduino preloaded microcontrollers) you need a cristal in the wiring. 
After
succesfull fusing to go with internal oscillator the above wiring (without the
oscillator) worked.
Refer http://arduino.cc/en/Tutorial/ArduinoISP

Original comment by pram...@gmail.com on 25 Feb 2010 at 11:13

Attachments:

• DSC09946.JPG

[GoogleCodeExporter]

I was having the same issue with invalid signature until I realized the 5v was 
connected to pin 10 on my arduino, but I was also supplying 5v from a battery 
in 
circuit to the target board.

I used an duemilanove and winavr 5.10 to successfully program a 328P using only 
direct 
jumpers from the arduino.

avrdude -p m328p -P com4 -c avrisp -b 19200 -U flash:w:Simon-v21.hex:a

Original comment by rill...@gmail.com on 25 May 2010 at 9:00

[GoogleCodeExporter]

Original comment by rsb...@gmail.com on 25 Jun 2011 at 3:26

• Changed state: Fixed