Who is still flashing his/her own drivers?

[MRsDNF]

@ChibiM

Just reading the instructions was still way too complicated :—)

I have this problem as well and not just with flashing drivers. Some seem to understand what is being written but I have no idea. If it was not for the patience of a few members here in particular TomE I would still be at a loss.

[ChibiM]

@MRsDNF

@ChibiM

Just reading the instructions was still way too complicated :--)

I have this problem as well and not just with flashing drivers. Some seem to understand what is being written but I have no idea. If it was not for the patience of a few members here in particular TomE I would still be at a loss.

+1

[DavidEF]

@manithree

I just got the USB gear, but my soldering skills and tools are lacking, so I haven’t even tried yet. I think I’m going to start upgrading all my old Convoys to biscotti.

I’m a programmer by trade, and I’ve done arduino stuff with my kids for science fair projects. Customizing drivers looks like fun.

If you’ve done Arduino stuff, does that mean you’ve flashed those chips before? If so, this stuff will be VERY familiar to you. I think there’s at least one guy around here who actually developed his flashlight driver UI using Arduino tools. :partying_face:

[ToyKeeper]

* raises hand *

[gchart]

will the real ToyKeeper please stand up, please stand up, please stand up

[d_t_a]

@~~X3~~

I tried some months ago…
Fried 3 convoy drivers, succeed with one.
I don’t know why, wiring is done like it should, I use the right USB thing, the right drivers and yet it’s a random result…
I gave up but it sadden me :weary:

I purchased a USBASP programmer device several weeks ago, so I could try flashing Biscotti to a Convoy C8 (it uses old firmware) and also to reflash the BLF Q8 (either the NarsilM v1.2 or Anduril).

I first tried the Convoy C8, but had no success (the avrdude “test” command does not recognize the driver; the Convoy C8 driver indicates “ATTiny13”). Since I had not success, I didn’t continue to try flashing the BLF Q8.

But after reading other people with success on how-to flash the Q8, I decided to try it on the Q8, and was happy to finally flash it successfully!

However, the Convoy C8 still won’t flash. I even bought a Convoy Biscotti firmware driver (7135x6 Biscotti) and also attempted to re-flash it (just for testing purposes), but for some reason, the USBASP programmer device does not recognize it either.

I’m no good at soldering/de-soldering, so I can try flashing only on flashlights that have easily accessible driver chips… and so far only the BLF Q8 seems to have that feature (just unscrew 2 screws, turn over the board and connect the USBASP programmer device).

[duramax]

I used a Raspberry Pi to flash my driver, it was relatively easy. My technical background has nothing to do with software/firmware development.

[gchart]

@d_t_a

I first tried the Convoy C8, but had no success

The Convoy drivers have pin 5 of the MCU grounded unnecessarily, which prevents flashing. By carefully cutting that trace, you should be off to the races in no time. Have a read through pretty much this whole page. There are some good pictures and explanations. If you run into more trouble (or to tell of your success story), hit us up over on that thread perhaps?

[ZozzV6]

I mostly build and flash my drivers.

[Flashy_Mike]

Me, I solely use lights with my own firmware (and mostly also my self designed drivers). I want the perfect UI (still a project in work, but close meanwhile) and I don’t want to memorize different UIs.

[manithree]

@DavidEF

If you’ve done Arduino stuff, does that mean you’ve flashed those chips before? If so, this stuff will be VERY familiar to you. I think there’s at least one guy around here who actually developed his flashlight driver UI using Arduino tools. :partying_face:

Yeah, but it’s a lot easier with the arduinos I’ve used. Just plug in the USB port, and let the IDE do everything else.

I think it’s the same C-subset language, IIRC, but flashing a dev board makes things significantly simpler than attinys on flashlight drivers.

[Chatika_vas_Paus]

I have some remains of knowledge and equipment from school times, so it is not a big challenge for me. Only need a little more time and willingness…

[joechina]

Me scrolling down and saw this:

@ToyKeeper

* raises hand *

I had quite a laugh

[Mike_C]

@WTF

@Mike C

I design my own drivers using a MCU that (to my knowledge) no one else here uses, so I gotta flash’em to use’em.

Are you referring to something like this?

https://www.tindie.com/products/DrAzzy/attiny1634-dev-board-woptiboot-assembled/?pt=ac_prod_search#product-description

I don’t use anything like that. The 1634 is the MCU that I use for my drivers, but I use the QFN size one and flash them using what I call “acupuncture style” method: Mod: BMF SRK v2 Roche Edition (Rebuilt into triple XHP 35 HI) - #18 by Mike_C

[Persechini]

Tried a few times but never got atmel studio or usbasp working properly

[WTF]

I was just checking to see if you were still on that MCU or had moved onto something else. Plus it was an easy way to let others know there is a development board available for the 1634.

Is that little QFN package any worse than an 85 when it comes to the internal clock changing speed with voltage and temperature?

[waffle_stomper]

I flash mine because I like very specific things in firmware and they’re not always available as options.

[Ratus]

@~~X3~~

Fried 3 convoy drivers, succeed with one.
I don’t know why, wiring is done like it should, I use the right USB thing, the right drivers and yet it’s a random result…
I gave up but it sadden me :weary:

:blink: How?

Is your set to 5v or 3.3v?

I had problems trying to flash with it set to 3.3v.

[caplang]

@duramax

I used a Raspberry Pi to flash my driver, it was relatively easy. My technical background has nothing to do with software/firmware development.

Any guide how to do this on Raspberry Pi?

[Mike_C]

@WTF

I was just checking to see if you were still on that MCU or had moved onto something else.

Yeah, I’ll be sticking with the 1634 for a while. All the newer ones appear to be smaller or tighter packages, making adding paste more difficult. I’ve had enough problems as it is now, took awhile to get the pasting technique dialed in and the right sized holes in the stencils. 20 pins on 4x4mm is as tight as I want to go, so the 1634 is currently my best choice. I thought others would be well into the 1616 or 1617 by now considering the interest some showed in them, but have yet to see such a driver. Maybe it’s still in development.

@WTF

Is that little QFN package any worse than an 85 when it comes to the internal clock changing speed with voltage and temperature?

I haven’t tested myself but my impression is that the 1634 QFN isn’t any better than the 85 SOIC. I don’t worry too much about that though. I remember when I used those temperature characteristics to code an “internal temperature sensor” in the ATtiny13A. It took too much out of the 1kb program size to be of any use for flashlight firmware… but it was fun, it worked