HELP! Programming ATtiny85 using Arduino as ISP

Hi, I'm new to this all and am trying to burn the bootloader onto the ATtiny but get the same recurring issue no matter what I change.

I am using the Arduino IDE 2.2.1 with the attiny board manager form (https://raw.githubusercontent.com/damellis/attiny/ide-1.6.x-boards-manager/package_damellis_attiny_index.json)

I'm very certain that I've wired it correctly and have a 10uF cap from the Reset to GND on the Arduino.

I'm using an Arduino Uno R4 Wifi with the ISP example loaded onto it. I've tried using a different cable, the board manage from DrAzzy, resistor across 10kOhm the reset and a different ATtiny85 chip.

The error I get is:

"C:\Users\Sebastian Nolan\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino17/bin/avrdude" "-CC:\Users\Sebastian Nolan\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino17/etc/avrdude.conf" -v -v -v -v -pattiny85 -cstk500v1 -PCOM5 -b19200 -e -Uefuse:w:0xff:m -Uhfuse:w:0xdf:m -Ulfuse:w:0xe2:m

avrdude: Version 6.3-20190619
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

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

         Using Port                    : COM5
         Using Programmer              : stk500v1
         Overriding Baud Rate          : 19200
avrdude: Send: 0 [30]   [20] 
avrdude: Send: 0 [30]   [20] 
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x03

avrdude done.  Thank you.

Failed chip erase: uploading error: exit status 1

Any suggestions are greatly appreciated!!!

An ATtiny85 cannot be 'bootloaded'.
It can be programmed via ISP/ICSP, but not bootloaded.

Have you tried it using an R3 as the programmer?

In all of the tutorials I’ve watched, they tell you to Burn the bootloader on the chip. Is this not needed?

Could you tell me what an R3 is?

You mean a rev 3 uno? No, I only have the R4

Arduino Uno R3

This is a very easy watch video. Seven minutes.

It is needed. The Arduino IDE developers gave the menu item the name "Burn Bootloader", but the boards platform developer can configure that operation to do anything they like. In the case where it doesn't make sense to flash a bootloader to the target board (as is usually the case with the ATtiny85), the platform developer will use the operation to set the configuration fuses on the microcontroller as needed. So you must perform a "Burn Bootloader" operation in order to initialize a new chip (since the default fuse settings from the factory might not be appropriate), and then again any time you make relevant changes to the board configuration in Arduino IDE (e.g., the Tools > Clock menu) even when you are not using a bootloader on the chip.

@runaway_pancake check the avrdude command shown in the output shared by @offsidelion to understand what a "Burn Bootloader" operation does for this target:

Shows us the wiring regardless, because i never have a Cap between Reset & GND on the Arduino.
The sketch that is on the Arduino actually needs to run (The Arduino as ISP sketch from the examples)

Then in the IDE under Tools->Programmer i select Arduino as ISP

And then i hit Tools->Burn Bootloader to set the fuses for the appropriate speed, make sure that it is set for '8Mhz internal' or you may brick the Attiny, unless you have crystals for the speed you set it too.

After this is successful you can upload a sketch using Sketch->Upload using programmer.

I am running this from IDE 1.8.x but i suspect that IDE 2. x.x is not that different. Not sure if it also works with an UNO R4, don't have one of those, but it should or the Arduino team made (yet another) goof !

I have used this with a dedicated Uno and a 'shield' (they're "inseparable") for years

The video demo (xfpd) has the right idea too.

I created a small programmer that is wired the way the Arduino as ISP sketch is suggesting + a LED & Resistor on PB4. I usually use Attiny13a 's which also causes me to forget that you have to click 'Upload using programmer' instead of 'Upload' which also does the trick when using MicroCore.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.