Programming Errors...

Howdy, Ya'll!!!

I want to make sure I am not violating any rules here, so without posting anything, I will explain my issue:

I recently purchased several ATtiny85's from eBay. They all work GREAT!!! I also recently purchased 10 of these beauty's from Digikey, and I cannot program them. I get an error, which I have saved, but, want to make sure I post it properly.

The chips give me a device signature error. I cannot even program the boot loader. At this point, I pulled out one of the known "GOOD" chips, and put it in the programmer, and it programmed PERFECTLY!!!

I noticed the numbers are different. The ones that are working, are Atmel Tiny85-20U.
The NEW ones, are ATTINY85-20PU. At this point, I am going to assume, that the Config file is not up to date, or needs something added to it, as there has been the same type of errors, when using the Atmega328 chips, giving the same errors.

I will post the complete error message, when someone can tell me how to do it right. It is not 'CODE', but, I want to make sure I don't get dinged, by not following the rules. Forgive me, I am a retired electronics engineer, and have really gotten into these MU's, and I am having a blast, however, i am NOT PC, and I DO strive to learn, and these forums are nice, but, at times confusing. @65, I think I have that right!!! lol!!

Thanks in advance for your help!!!

Taz...

PS - I decided to attach the file as a doc

Untitled 1.doc (17.5 KB)

Hi old Phart!

FYI
You can post your errors with code tags as below.
Use CTRL T to format your code.
Attach your ‘complete’ sketch between code tags, use the </> icon in the posting menu.
[code]Paste your sketch here[/code]

Arduino: 1.8.9 (Windows 7), Board: "ATtiny45/85 (Optiboot), Disabled, CPU, ATtiny85, 8 MHz (internal), EEPROM retained, B.O.D. Disabled"
 
C:\Users\Kims\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino8/bin/avrdude -CC:\Program Files (x86)\Arduino\hardware\ATTinyCore-master\avr/avrdude.conf -v -pattiny85 -carduino -PCOM7 -b19200 -e -Uefuse:w:0xFE:m -Uhfuse:w:0b11010111:m -Ulfuse:w:0xE2:m
 
avrdude: Version 6.3, compiled on Dec 16 2016 at 13:33:19
        Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
        Copyright (c) 2007-2014 Joerg Wunsch
 
        System wide configuration file is "C:\Program Files (x86)\Arduino\hardware\ATTinyCore-master\avr/avrdude.conf"
 
        Using Port                    : COM7
        Using Programmer              : arduino
        Overriding Baud Rate          : 19200
        Setting bit clk period        : 5.0
        AVR Part                      : ATtiny85
        Chip Erase delay              : 400000 us
        PAGEL                         : P00
        BS2                           : P00
        RESET disposition             : possible i/o
        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    12     4    0 no        512    4      0  4000  4500 0xff 0xff
          flash         65    12    32    0 yes      8192   64    128 30000 30000 0xff 0xff
          signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00
          lock           0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
          lfuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
          hfuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
          efuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
          calibration    0     0     0    0 no          2    0      0     0     0 0x00 0x00
 
        Programmer Type : Arduino
        Description     : Arduino
        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.00s
 
avrdude: Device signature = 0x000000 (retrying)
 
Reading | ################################################## | 100% 0.01s
 
avrdude: Device signature = 0x000000 (retrying)
 
Error while burning bootloader.
Reading | ################################################## | 100% 0.00s
 
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.

I have not used the ATTINY85, this might help.

Well, I thought it may be the same, but, "who - da - thunk - it...." right?? lol!!!
Thanks!! I see you re-posted it.

I read the URL references, and found a few interesting items, that can be tried. It still doesn't help me with this issue really. I could be wrong, but, doesn't the config file need to have all of these set up for each chip? Shouldn't it be added? If so, how can I do this?

I am still in need of more ideas from the gallery outside of our forum, looking in...

How about it, all you Arduino geniuses!!! Lets find the solution for all of us!!!

AND THANK YOU!!!!

Taz...

Just for clarification, are you using SpenceKonde's TinyCore? The creator of that core goes by the handle DrAzzy on these forums and will probably be along at some point to help.
This error:

avrdude: Device signature = 0x000000 (retrying)

is usually caused by a wiring error, or when the chip is configured to use an external clock and there isn't a clock source present. It looks like you've already ruled out wiring errors it might be worth trying feeding the chips a clock signal (even thought the chips should be set up to use the internal clock straight from the factory).
It looks like you're using an Arduino as an ISP, is that correct? It looks like this version of the ArduinoISP sketch generates an 8MHz clock signal on pin 9 of the programmer, you could easily try that out and see if it helps at all.

Thank you!! I AM using Spence/Konde. and I have tried both methods you mentioned. SAME error. Since I programmed the other chips, it proved the wiring is correct. Also, if it wasn't wired correctly, wouldn't you get a different error? I can't imagine them changing the pinout. But, who knows... I'm new at this stuff. Tremendously more fascinating than frustrating, but, I hate being frustrated, and have to find an answer.

Here is the old chip number - ATMEL Tiny85-20U

The NEW chips are - ATtiny85-20PU

I am told the 'P' is used for type of packaging. Not sure. Other than that, I am at a loss.....

Thanks all!!! I hope we find out the issue.....

Taz...

Someone will chime in and give you the answer, keep the faith.

The markings for packages were changed when Microchip took over to harmonize with Microchip's marking conventions. The chips should not behave any differently.

That issue is mysterious - error indicates either wiring problem, or part set to use a clock source (eg, crystal or external clock) which is not present, but a virgin chip should be set to use internal oscillator at 1MHz, and Arduino as ISP definitely works to bootload virgin attiny/atmega chips (some programmers, under some conditions, try to use an sck clock too fast for a chip running at 1MHz, or need a jumper to be set to make it slow down the sck clock).

Now, if the first time you tried it with a given chip, you had an option specifying a crystal, and didn't have one connected, that would do it, and the chip could not be programmed, even to set it to not use a crystal, without providing it with a clock signal or a crystal.

As an aside, there's no reason to bootload using the Optiboot option unless you plan to do further programming via a USB-serial adapter, as opposed to an ISP programmer. Though on most of the attiny's it doesn't matter as much as it does on a chip with hardware bootloader support, as the first ISP upload will erase the bootloader and it will be as if you bootloaded with the no bootloader version (ie, just setting the fuses).

HOWDY DOC!!!

Ok, I have found the problem. NOTHING to sweat, I hope...

What are the odds of 3, yes, I said THREE of the Tiny85's, were BAD!!! It was the first three out of the tube!! Now, trust me, I wasn't even worried, even at 2, not being recognized, but when I hit THREE... THAT was my magic number. I have talked to the supplier, and they said it is very rare that this would happen. But, it does occasionally.

So sorry y'all for the false alarm. I was stunned a bit too. Maybe we made some aware of some things happining like this. It was a good thing!!!

Y'all are great!!!!
Have a OUTSTANDING weekend!!!

Taz...

Very strange. I am quite surprised by this. ESD maybe?

I am not sure.... Hard to prove, as you know, but, they could have been fall offs, I know we had that happen with Microprocessors in P.R. at the Intel plant. It happened regularly, but, were caught by the cameras that control the machinery. I used to engineer those machines, so, I have seen it first hand.

Strange indeed, but, plausible!!! lol!!! I was truly surprised by this.... They were never removed from the tube, except for the ones I tried to program, one at a time, so static was not an issue. I am VERY careful about static. I have NEVER lost a chip to static, during the last 55 years of experience. AND I have handled stuff not grounded, and never lost one. Not even in circuit!

I'm hoping that I got them all out of the way for the rest of my life!!! lol!!!! ALL AT ONCE!!!

By the way, love your boot loader. Works so sweetly....

Best regards;

Taz...