Tiny AVR Programmer - Initialization

When trying to upload a program using the Tiny AVR Programmer, I always receive an initialization error. I’m using Arduino IDE V1.8.10 running on a Windows 10 64-bit computer. USBtinyISP is selected as the programmer. The Windows Device Manager shows that LibUSB-Win32 Device is working properly. This is the first and only time I’ve tried to use this programmer.

The exact error message is:

initialization failed, rc=-1

Double check connections and try again, or use -F to override this check.

Any suggestions?

Thanks.

Hi hgoldberg11.

That error indicates Arduino is talking to the programmer but the chip you’re trying to program isn’t responding to the programmer.

What are you programming and are you sure it’s functional?

Hi Chris,

I’m trying to program an ATtiny 85. The exact P/N is ATtiny85-20PU. I have tried two devices so far, the programmer responds the same for both.

Thanks.

OK, can you post a photo showing how you have the ATtiny85 connected to the programmer? Also, are these new ATtiny85’s or previously programmed 85’s?

It’s possible if they were previously programmed and the fuse bits enabled an external oscillator, you might need to add a crystal to the 85 before it will accept code.

When you load your code, what “board” setting are you using in Arduino?

Hi Chris,

I purchased 5 new ATtiny 85’s from Digikey. I have found the following:

  1. I can program an unused device from the tube as long as I don’t try to “burn the bootloader”.

  2. My program requires an 8 MHz external crystal. My selections are:

Board: ATtiny 25/45/85

Chip: ATtiny 85

Clock: 8 MHz external

B.O.D level: B.O.D disabled

Save EEPROM: EEPROM retained

millis()/micros(): Enabled

If I try to burn the bootloader prior to programming, I get the error message described earlier in the thread when the programmer tries to burn. If I try to program a device after the failed burn attempt, I get the error message. If I try to program a device without burning the bootloader, there is no error message but the device does not operate in the target. I can’t detect crystal oscillation with an oscilloscope.

A picture of the ATtiny 85 in the programmer is attached.

OK, it looks like you forgot to attach the image, but from your settings, it sounds like you’ve enabled the external oscillator on the chip and there isn’t an oscillator on the board.

The only way I know of to recover those unresponsive units would be to add an external 8MHz crystal between IC pins 2 and 3. That should enable you to upload to them.