I am trying to program an ATTINY85 using my Arduino Mega. I have watched a bunch of Youtube tutorial and have been bouncing around between 1.05,1.06 and now the newest version. I was able to successfully get the tiny boards in my boards list. Everything seems to be set up but when I try to upload it says, "the current selected board needs the core 'Arduino:Arduino' that is not installed".
I have been messing around with this for over an hour, if anyone knows what this means and what I can do to solve it, it would be greatly appreciated.
I have uploaded the ISP sketch.
I selected aTTiny85
USBtinyprogrammer also tried arduino as isp
I just manually added the attiny in board manager and i succesfully installed it but now it is saying im not connected to com8.
It starts uploading then
says invalid device signature
When you encounter an error you'll see a button on the right side of the orange bar "Copy error messages". Click that button and then paste the error messages in a reply here USING CODE TAGS(</> button on the toolbar).
People often connect it incorrectly when using a mega as the isp programmer, because the spi pins arentry in the same place along the outer headers - use the sck/miso/mosi pins on the isp header.
Did you remember to disable reset on the mega with a ~10uf cap from reset to ground?
The errors you got in first post and the reference to ancient versions of the ide suggests that you may be using an old core. What core are you using? You should be using mine ( GitHub - SpenceKonde/ATTinyCore: Arduino core for ATtiny 1634, 828, x313, x4, x41, x5, x61, x7 and x8 or board manager link in my signature ) or damellis's one.
Mine is better, in general, and supports every tiny you could imagine using, though his core brings in new features from the main core faster.
But yeah, definitely always post full output per pert's request
Arduino: 1.8.1 (Windows 7), Board: "ATtiny25/45/85, ATtiny85, External 16 MHz"
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:\Users\Jon\Downloads\arduino-1.8.1-windows\arduino-1.8.1\hardware\tools\avr/etc/avrdude.conf"
Using Port : COM8
Using Programmer : stk500v1
Overriding Baud Rate : 19200
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 6 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 1 0 0 0 0 0x00 0x00
Programmer Type : STK500
Description : Atmel STK500 Version 1.x firmware
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.02s
avrdude: Device signature = 0x000000 (retrying)
Reading | ################################################## | 100% 0.02s
avrdude: Device signature = 0x000000 (retrying)
An error occurred while uploading the sketch
Reading | ################################################## | 100% 0.02s
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 am not using the spi I am using pins 10 11 12 13 like described in tutorial. Using Damellis I think. I do have a cap and even added solder to the leads to make sure it's making contact. Just desoldered a crystal from an old Uno and tried to upload with it set to external crystal, still nothing. I feel like it is something simple but I have no idea what.
Do you have an external crystal connected? If not you soft-bricked it the first time you did burn bootloader. You can't talk to it if it's set to use a crystal and none is connected - the chip isn't running, but still enters programming mode. This results in miso staying low, so the first thing avrdude does, trying to read the sig, gets all zeros
Connect a crystal plus loading caps to the crystal pins and it should work fine. Then you can choose a different clock option and reburn bootloader, then remove the crystal (unless you want it to use external crystal, but who wants to waste 2 of the 5 pins on that, unless you need only 3 IO pins... and a very accurate system clock - esp since you can get it running at ~16mhz off the PLL!)
Draytology:
Using Damellis I think.
Nope, that's my core in that log.
Can you post schematic please?
I only switched to external crystal when i hooked one to pin 2 and 3, made no difference.
I don't have a schematic to post but I have it set up like this:
pin10>pin1
pin11>pin5
pin12>pin6
pin13>pin7
tiny pin 4 ground
tiny pin 8 5v
10uf cap between ground and reset
I have checked my wiring several times including individually checking continuity of each wire
You said you're using a mega running Arduino as ISP, but you're using the connections that you'd use for an Uno. As I said above, you need to use the SPI pins (SCK, MISO, MOSI). Not the pins that happen to have the same number as those pins on the Uno (See below for a rant about this) - that means SCK is 52, MISO is 50, MOSI is 51 (accessible in two places, on the ICSP header or the pins on the end of the board.
Also, you need a 0.1uf cap between power and ground, right next to the tiny85. The wires need to be as short as possible, I had a tiny85 board that I had manufactured that I had to junk because the traces to the cap wound up being too long. It would write one page then choke when I tried to program it. Dead-bug'ed a 0.1uf cap across thetop, and it worked fine. But I couldn't have customers do that, so the boards went in the scrap bin.
If you study the comments in ArduinoISP, they explain, sort of, how you can modify the sketch to use those pin numbers (with bitbanged SPI instead of the hardware SPI).
The mapping of digital pin numbers to physical pins (and the accompanying hardware features) is arbitrary - the designers chose to use different pin numbers for the SPI pins. The reason, as far as I can tell, is that they needed to maintain shield compatibility. Shields can use the ICSP header to get onto the SPI pins, so moving them doesn't matter from a shield's perspective. But shields (mostly motor drivers and stuff like that) depends on PWM on certain pins; for example, if you're making a motor driver shield, you need to be able to PWM the enable pin, for example). So they (I assume) decided to make sure the same pins had PWM. Now, if they'd been thinking clearly, they'd have lined up the pins such that they also used the same timers, so that libraries that had to take over a timer's output compare to control such a shield could do so without modification. But nope. So you still need #ifdefs, and you potentially end up with timers that don't have the same capabilities as on the Uno on those pins. (ex, on Uno, pins 3 and 11 are on the 8-bit async timer. On the mega, an identical async timer is present... mapped to pins 9 and 10, which had a 16-bit timer on the Uno!). But - no problem, the user can just use the ICSP header... except they DIDN'T LABEL THE PINS, AND they put silkscreen on the bottom so you can't see which pin is ground, so you need to use a pinout chart or an ohm meter to find out what the orientation of the ICSP header is. Which you need to know in order to, you know, use it as an ICSP programming header....
Okay, enough of that. Seriously, why didn't I spend that time writing code?
Switched to pins 50-54, switched pin assignments in code, still getting exact same error. Arduino Mega is worthless at programming attiny. This is way to much hassle.