Double check connections and try again, or use -F to override
this check.
Error while burning bootloader.
This report would have more information with
"Show verbose output during compilation"
enabled in File > Preferences.
OK -- so to verify, I switched back to 8 mhz internal; same error.
I closed arduino/relaunched - same thing.
rebooted, same thing.
uninstalled arduino & re-installed...
I tried about 1/2 dozen attiny85's (1 might be a clone) with same failure. Tried two isp's; Tried two attiny cores.
Frustrating as I've been working a lot with attiny85's recently and have burned bootloaders & uploaded code w/o issues; I put the project on the side for a few weeks, and when returned, can't do squat.
I tried with 1.6 release, rc2, rc5, "nightly" all same results.
Did you have the crystal installed? ISP programming won't work without the chip's system clock running and once you set the configuration fuses to use a crystal you need the crystal to continue running.
Since the chips worked before you set them to use external crystal, but now no longer work, that's a good sign that the external crystal is not connected correctly.
Ensure that you have the crystal connected to the right pins, and appropriate loading capacitors per manufacturer specifications from the two crystal pins to ground. If using a breadboard, you may need to use lower value capacitors, or remove them entirely, due to stray capacitance from the breadboard.
Not sure what happened, but now I cannot upload or burn a bootloader to an attiny85 (I have, and did, upload using the isp programmer a few atmega328u boards, and burn bootloaders0
The error I get now is:
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.
I guess I'll have to remove all my arduino files/libraries/settings & start completely over.
This isn't the 1st time something changed on its own and failed to compile sketches.
I already tried uninstalling & reinstalling, but this , of course, left my user libraries & sketches in tact...
frustrating
So today (now 2pm, I started at 9am) I verified that had things wired correctly and verified that burning a boot loader and uploading sketches failed using USBTinyISP and USBASP. I verified it a few times, trying with both 6 and 10 pin cables. (usbasp only has 10pin, usbtinyisp supports both).
I grabbed a brand new (still hermetically sealed in the bag) attiny85 and tried that. (Failed).
Then I grabbed my Uno (which had failed as an ISP a few days ago) -- suddenly that was able to upload sketches & burn a bootloader.
OK -- maybe I made a mistake with the uno wiring; so I tried again with the isp programmers (since I had wasted the morning, why not the afternoon too, right?) -- and damned if it worked with those two as well.
I used all the methods I had previously used (wiring manually, using a cable directly etc) -- and now; it always works no matter what I use.
I grabbed the (suspected) non-authentic attiny85 out of the bitbucket and it worked too.
Software wise, I changed nothing.
I did not reboot. I didn't reload arduino ide from yesterday.
it's the machines, dumb as the people who use them!
update:
I went back to burn the bootloader so I was sure that it was set to use 8mhz external.
Now, no mater what I try; I'm back to an error:
java.io.IOException: Cannot run program "{path}/bin/avrdude": CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at processing.app.helpers.ProcessUtils.exec(ProcessUtils.java:26)
at cc.arduino.packages.Uploader.executeUploadCommand(Uploader.java:113)
at cc.arduino.packages.uploaders.SerialUploader.burnBootloader(SerialUploader.java:349)
at processing.app.Editor$57.run(Editor.java:2768)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
Arduino IDE was not reloaded, but I did open a couple of other sketches. Changed destination (atmega instead of attiny) -- but changed it all back. I never even unplugged the isp or the tiny from the breadboard from the successful runs; so hardware wise: exactly the same; software: Ok; I loaded other sketches for unrelated stuff (view only) but now I burn (uploading a sketch works) no go. Since I'm just selecting menu options to burn a bootloader, there's no coding involved that I could have screwed up...
Frustrating doesn't come close to describe the feelings I have. It simply doesn't make sense.
I'm going to try the uno again to see if that starts a run of good luck...
