Flashlight Firmware Repository

It’s been around a long time to run VM’s, either a shareware, or full up 3rd party sources. Pretty much everyone in development does this now - I’m not sure I know a developer who doesn’t run multiple OS’s on their computers via VM’s. I would think most servers are now running under VM’s as well - VMWare dominates the market there. Both my clients converted to VMWare a few years back, and pretty much all other shops I’ve heard of with servers to manage have done the same. There’s just so many advantages to it.

I have a Win 7 desktop for my primary development @work, but with Oracle VM VirtualBox, I run Win XP when I need to run old dev tools. For testing, we have VM’s of a whole bunch of Win versions (XP/Win7, Win8’s, Win10 in 32/64 bit versions), including International versions. Same thing can be done for various Unix/Linux/etc VM’s.

I’m not sure if extending Win10 to have the native support is that much of an advantage, maybe some advantages.

Ish. There’s a definite push to have lots of little servers instead of one big one, and to make those little servers independent of the hardware. But instead of fully virtual machines, it’s a lot more efficient to use containers (LXC, chroot, bsd jails, etc). Isolation instead of emulation. And preferably with automatic deployment and load scaling. This often gets grouped under the label of “cloud” computing, using popular tools like OpenStack.

The thing Microsoft just did is to make it possible to run an Ubuntu container under Windows. This probably required a lot of kernel-level API glue code, to translate Linux system calls into Windows system calls, but otherwise should be relatively simple.

Virtual machine-based solutions are still popular, using VMware and Xen and similar tech, but after peaking in 2009 it seems to be declining now in favor of lightweight isolation. This isn’t the best representation, but here’s a trend graph from Google.

I am very interested in trying this… but kinda hate to on my main system since it is all beta… I will give it a little time and will try it!

I have no idea if it’ll actually work (the bash-on-Windows stuff) because I don’t have a Windows computer to try it on. However, it’s supposed to be pretty close to the real thing.

In particular, I’m really unsure if the avrdude step will work, because that requires Microsoft to have all the USB access stuff wrapped properly… and that’s not an easy thing to do. They may have done just networking and task management, since that’s all it would need to get basic web development tools working.

Hi All,

Does anyone have theory as to why I can no longer get atmel 6.2 to recognize my programmer? When I click into the programming box there was always an option that said AVRISP MKII. Now it only says “simulator”

When I disconnected and reconnect the box it makes the noise you would expect. In device manager windows claims its working properly.

Any ideas would be helpful :slight_smile:

A little help here… I’m running windows 10 64 bits and have been trying to get my USBASP recognized by either AVRdude and eXtreme burner AVR and nothing…

I did the necessary steps to get the drivers correctly installed, it already appears as USB ASP device in device manager.

This is my programmer and has a jumper to select 3.3V and 5V, I suppose it goes in the 3.3V slot?

Thanks!

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… :slight_smile:

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. :slight_smile:

:open_mouth:
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:)