Show Posts
Pages: [1]
1  Using Arduino / Microcontrollers / Re: Invalid device signature -ATtiny85 on: November 14, 2012, 12:42:55 pm
As some of the chips worked but not all I wonder if they have been programmed already (grey imports?) and need an external crystal as fuses have been set for that. Adafruit have an ArduinoISP2 that can supply a 8Mhz clock signal from an UNO pin that is maybe good enough to reset fuses.
Another possibility is the fuses have been set to disable Reset pin or ISP. I think you would need a high voltage programmer to fix this problem.

RIVA:  I looked at the chips under a magnifier and they are all marked ATmel ATtiny85-20PU.  The Mouser catalog only shows the max speed as being 20MHz. The 230 page data sheet lumps the tiny25/45/85 and I get lost in the details.  I will look at the Adafruit option and order another batch of theTiny85s and hope.  Thanks!

Still gonna keep trying, though smiley-cool
2  Using Arduino / Microcontrollers / Re: Invalid device signature -ATtiny85 on: November 14, 2012, 11:34:17 am
I'm using a ZIF socket for the chips and did a continuity check with an ohmmeter to make sure each pin is working. Everything from the UNO pin to the ZIF pin works okay.
The bootloader simply tells me that it is working on a Tiny85 @8MHz, talks back and forth with it and then gives the error msg. The puzzling thing is that it worked smoothly the first three times and the UNO and that breadboard were unused while I fiddled around with the other stuff. When it didn't work on #4, I reset and reloaded and the bootloader seemed to be running okay... until it didn't.

As far as I know, the UNO is not going to change anything on the PC so those files should be okay and reloading the ISP should work.  The heartbeat light on pin 9 shows that the ISP is running; just the bootloader is weird.
3  Using Arduino / Microcontrollers / Re: Invalid device signature -ATtiny85 on: November 14, 2012, 11:09:18 am
YES to all. The verbose dialogue prints that the bootloader goes a long way into the process and gets responses...then stops with the error msg.
4  Using Arduino / Microcontrollers / Invalid device signature -ATtiny85 on: November 14, 2012, 10:34:31 am
It didn't start out this way. I have the Tiny85 breadboarded for programming and a new tube of 20 of the Tiny 85 chips. I have a new UNO R3 and am using arduino-1.0.2.  I took the first three chips in the tube and ran the bootloader on each of them with no problems at all. Over a two day period, I loaded sketches on each of them and used them in breadboarded circuits and they all worked fine. With changes to the different sketches, each chip went through the use cycle maybe four times each. Everything was ready to make another set of chips.

I loaded Arduino ISP into the UNO and then the bootloader to an Tiny85 @8MHz chip and got

 avrdude: Device signature = 0x000000
 avrdude: Yikes!  Invalid device signature

Everything I can think of checked okay and I tried and re-tried the chip but with the same results. 
I tried the next chip from the tube: same results.  The next chip: same results.  So with the next two chips...and with the last one in the tube. Not likely 8 dead chips!

I reset the UNO, reloaded the Arduino ISP, but with the same results. I put sketches on the UNO and they work fine. I made each of the UNO ports blink LEDs and the ports work.  I get a heartbeat LED blinking on pin 9 on the breadboard when the Arduino ISP is running.  I ran a backup copy of the arduino from another drive - same results.
I even replaced the ATmega328P-PU. Everything seems okay, just won't take the bootloader.

The ISP reports it is programming an ATtiny85
  The Arduino ISP is  v 04m3
    Avrdude is v5.11 compiled 9-2-2011
      using programmer  STK500 v1

I'm new at this, so any ideas would be most welcome.

Pages: [1]