On a related note, using the USBasp from Fasttech, I had no trouble flashing a 32x7135 driver and I didn’t need to cut any traces or anything. I haven’t had issues flashing any attiny13-based driver with it, unless the driver had extra pins grounded (stars soldered). The only tricky part is getting a solid connection on the clip; sometimes that takes a few tries.
I tried it on another 2.8A Convoy S2+ and again had to cut the track to flash it.
Each AMC7135 needs 0.2mA supply so it would be 1.6mA with 8 of them which is well within specs of the programming chip. But these are DC specs and it gets worse with impedance and high programming frequencies.
I did update the EvUSBasp’s firmware to the latest v2011-05-28.
I will get a Fasttech USBasp on my next order.
Hmmm… the cops just busted some dude flashing his tiny around town… :party:
Ahh… easy way to increase post count 
Figures…
So…
You want us to pass the hat for your bail?
0:)
Nah, but they confiscated my favorite overcoat… J)
I got in a bunch of mega328 chips that have the default fuses set to use a crystal oscillator… bastards… can’t use my neat little ISP adapter with the ZIF socket. It is set up to handle tinys, 2313’s, and mega328’s. Supporting the 2313 winds up grounding the oscillator lines so I can just kludge on a crystal. Now I gotta hack up another board and buy another zif socket.
Anybody do this on Windows 10 yet? I can’t get AVR Dude to recognize my USBasp.
Solved my own problem, but in case anyone else is interested, this was super easy:
http://rayshobby.net/dead-simple-driver-installation-for-usbasp-and-usbtiny-on-windows/
Yes - needed to get the new driver that supports it. I wrote bout this before... Hhmm. Should find a link to dnld here: http://www.protostack.com/accessories/usbasp-avr-programmer
This is a pretty goof forum on ATMEL stuff in general: http://www.avrfreaks.net/
Hey guys I’ve been trying to flash an attiny25 driver I have hand soldered but it isn’t working. I get contact with some other 13a based drivers not built by myself but the 25 just won’t work. I usually get this output:
But I’ve gotten this too a few times:
I’ve tried flashing a spare attiny25 and that actually made contact and flashed. So I’m thinking either my cheap China soic8 clip is not making contact or my attiny is dead. I’ve tried my best removing excess solder from the legs but it hasn’t worked so far. Anyone have any ideas?
It looks like a bad connection, although the second error I haven't seen before. Sometimes the excess solder on the legs makes it really hard to get a good connection with the SOIC clip.
I got a big problem here
I am flashing Attiny 85s for Narsil
first flash works perfectly
then I flash again with adjusted temperature offset
and it says cant veryfiy first byte 0x0000 of the written data
the chip has 0x00 not 0x44, so it seems after first erase its stuck
I just took a brand new one
and flashed it 2 times at the same time, same error
this is now the 2. Attiny I cant flash a second time, if I get more I get in trouble
I got that sometimes. Re-clipping or cleaning up the clip connections with isop. alcohol usually helps.
no its not the 8. chip in a row with that behavior, even the brand new out of the cut tape give me this error
I flashed over hundred chips and usually reclipping helped, but first I reclipped like 10 times with no change
then I reflowed a brand new
first flash worked fine
did the temperature offset
then flash 2. time again this error
checked the last 11 Narsil boards I had reflowed
6 were OK 5 were not ok
Then I too another new from tape and got this error again
then I made a video to have proof to get to Digikey support to get replacements asap
just used a Bistro hex to get the video shorter
Hhmm. I use the Pomona clip for my every day programming.
If they work first time and fail the 2nd, wonder if the fuses are setting the reset pin as an I/O pin - can't recover from that using our standard USB AVR setup. Suppose you checked that already...
I always use the same fuses saved in a txt file
avrdude -p attiny85 -c usbasp -u -Uflash:w:NarsilTriple.hex:a -U lfuse:w:0xe2:m -U hfuse:w:0xde:m -U efuse:w:0xff:m
:exclamation: 
You made sure all six pins are wired up correctly, yes?
I flashed over 100 drivers before
It turned out the use had worn down one lead, having a bad contact, not sure why always the first flash suceeded on about 10 chips and then the 2. failed
My images are locked by photobucket…best how-to I have seen here is Guide: how to flash ATtiny13a based drivers (NANJG, QLITE, etc.) with custom firmware