I donāt know how to get it recognized in Windows, but you probably want it configured for 5V.
I used Hoopās how-to and got a positive test in AVRdude on the BLF attiny13A
How to flash
However I downloaded the latest software, and canāt find the attiny13A in the latest atmel studio. Think Iāll have to downgrade.
But the drivers for the USBasp and AVRdude work fine on my windows 10 system.
Hope this helpsā¦
will34,
This is the ultimate, best source of AVR support/drivers/etc. I know of. I used this for full 8.1 support, think also for Win 10: http://www.protostack.com/accessories/usbasp-avr-programmer. Download and use the latest there. Mine works for the 5v position, not the 3.3v.
I bought my first USBasp from Protostack, then bought my 2nd from FastTech - both worked perfect. One died on my recently, so just ordered another from FT, as I always like having a backup on-hand.
Very Important: Pin #4 on the USBASP V2.0 is not ground - it's TXD. I wire grnd to pin #10 now and it solved several problems I had - originally I followed the pinout description in flashlightwiki.com and it sort of/semi worked, and it's wrong for the newer V2.0 dongles.
I updated this page: http://flashlightwiki.com/AVR_Drivers, to show the proper wiring for USBASP V2.0
Edit: Hoop thread's OP showing the wiring is wrong - I've proved this, did all the testing to prove it. Pin #4 on the dongle is not ground. It may work, it may appear to work - it's wrong. Using pin #10 for grnd is much more stable and reliable I've found.
I wired mine like this, following WarHawk-AVGās guide:
Labeling is wrong, but the wiring appears correct .
Thanks Tom!!! It worked! :partying_face:
Finally did my first FW flash after all these years. However it did not work with extreme burner AVR, it shows āmismatch at location 0x0000ā. So I used AVRdude command instead, success in the first try.
Now I have my Courui D01 flashed with TKās ramping FW, very nice!
Time to start desoldering leadsā¦
Holy cats!
You just un-bricked like a dozen of my drivers. I had a bunch which refused to flash, but I moved one wire, tried a dead driver, and it lives again! Iāve seriously had a wire in the wrong place all this time??? Wow.
Would have been nice to know this last summer.
ToyKeeper too.
When I first got a usbasp I searched google images for the pinout. I found tons of bad pinouts so I didnāt trust any of them. Itās a little conspiracy.
The problem with the bad pinouts, as youāve seen, is that leaving the gnd unconnected actually works on some chips.
Oh boy, good news/bad news (). Really sorry, but I thought I made a big stink bout it at the time. Even got update access to the flashlight wiki to correct the errors, just didn't want to remove the original stuff because I really was unsure if the old dongles were still around.
Think Halo confirmed this at the time as well, also WarHawk had it right way back.
I encountered these problems early on with the 25/45/85's, researched it, then found the fix, but some others already knew about it. It's probably all in the early part of the 25/45/85 thread, I think.
Ok - looked it up, here we go:
Problem - Post #233 here: https://budgetlightforum.com/t/-/34900/233
Problem - Post #241 here: https://budgetlightforum.com/t/-/34900/241
Solution post #263 here: https://budgetlightforum.com/t/-/34900/263
Post #265 mentioned same as just posted earlier: https://budgetlightforum.com/t/-/34900/265
Well Iāve now set up to build my own drivers. Did some practice by flashing luxdrv to a couple 105c drivers. So, I am finally ready to attempt one of these drivers. Could someone some up for me what firmware is out there that will work well with these triple down boards? I love the ability for the user to choose between two mode groups. Iāve been looking at the firmware repository, but Iām a little lost trying to sort through it all.
So far just one firmware (that I know of) that works with the TripleDown. Itās a variation of the BLF-A6 firmware, so it does have 2 mode groups. It is linked in the OP of the TripleDown thread. As downloaded it is set up to test driver function, so you will need to edit some values to give proper function,
Is alt pwm the third channel?
ModesNx are the larger bank of 7135s. Modes1x is the single 7135. Put the word TURBO to toggle the FET
Ok. I donāt real know what I am doing, but I might as well jump in and learn to swim:)
Can the FET only be toggled? I got the attiny85 for the added pwm, so will the 85 go to waste with this firmware, or is there still benefit? Sorry if my questions sound like I donāt know what Iām talking about. please humor my ignorance:)
I donāt know how it works with anything other than a 13, or even if it will work at all. I personally have not left the 13
Don't think there's any added PWM (??). 25/45/85 all have the same PWM limits, as I understand it.
I was talking about the number of outputs, but clearly I donāt know enough to be asking questions yet. I will keep reading. :person_facepalming:
Oh, um, the attiny13a has one PWM counter and two PWM channels. A 3-channel driver will need to use a general I/O pin for one of the channels, which is useful if you want a super-bright turbo and donāt care about the levels between turbo and 100% 7135. So, like, you could use 7135s to go smoothly from moon to about 1000 lumens, then go directly to a 3000-lumen turbo, and you wouldnāt be able to access anything between 1000 and 3000 lumens.
The tiny25/45/85 have two PWM counters and four PWM channels. So, it should be able to go smoothly all the way from moon to turbo even on a 3-channel driver.
I got a tripledown attiny25 board yesterday and am hoping to get bistro working on it soon. So far all Iāve done is update the ramp calculator to support 3 channels, and havenāt gotten into the actual driver code yet. Bistro works on it in 2-channel mode (1x7135 and 6x7135), but the third channel (FET) is currently unused.
Oh, um, the attiny13a has one PWM counter and two PWM channels. A 3-channel driver will need to use a general I/O pin for one of the channels, which is useful if you want a super-bright turbo and donāt care about the levels between turbo and 100% 7135. So, like, you could use 7135s to go smoothly from moon to about 1000 lumens, then go directly to a 3000-lumen turbo, and you wouldnāt be able to access anything between 1000 and 3000 lumens.
The tiny25/45/85 have two PWM counters and four PWM channels. So, it should be able to go smoothly all the way from moon to turbo even on a 3-channel driver.
I got a tripledown attiny25 board yesterday and am hoping to get bistro working on it soon. So far all Iāve done is update the ramp calculator to support 3 channels, and havenāt gotten into the actual driver code yet. Bistro works on it in 2-channel mode (1x7135 and 6x7135), but the third channel (FET) is currently unused.
Ok. Thanks. I was just reading your posts in the tripledown thread. I mistakenly posted a question about the tripledown firmware here. Oh well.
I think you are working on exactly what I am looking for so I will continue to follow the tripledown thread anxiously awaiting your developments. For now Iām going to continue to practice flashing firmware with small customizations so hopefully I will advance my knowledge a bit.
After someone else confirms it works, and maybe the defaults are tweaked back to a more user-focused config, I should be able to merge the tripledown-bistro code into trunk. For now, itās working but is only in the tiny25 development branch.
For tiny13-based tripledown drivers, thatās a different matter. It canāt do PWM on the FET pin, and it has only half as much space, so itās significantly trickier to get working.