I believe the previous posts recommending you upgrade to the latest version of avrdude are correct, and doing so should resolve your issue.
Depending on your OS and method of install, the method to upgrade avrdude will be different. If you run into trouble, make sure you provide these details and we’ll be happy to help.
Well, I’ve tried to flash my D4V2 using my Macbook, but no cigar. I suspect I’m losing my way with AVRDUDE, etc. (I’m crap with programming of any kind), plus my eyesight is poor… maybe I’m not getting the pins aligned properly. So I’m wondering whether anyone might be willing to flash it for me… I can even send the flash thingy I received from Hank if anyone wants one. I will pay for postage, too. If anyone in the U.S. can help, please PM me. Thanks! (I’m in New Orleans, if that matters.)
Run cmd as Admin in the AVRDUDE install dir. (copy/paste in Notepad > save as .bat > execute.. )
EDIT:
Really fancy the latest changes in the FW :)
- The "release for On" instead of "press for On" - feels much more intuitive now
- The ramping down after a short release in the Strobe Modes - now consistent with the main ramping (always thought that I was doing something wrong when I was trying to ramp down in any Strobe mode.. )
- Factory Reset -Yay! Nice to have a fail-safe, just in case..
The rest of the updates were already on my D4V2. Not on my FF's tho,, thus, next I'll need to cook up some Dupont wires to flash my FF's as they're becoming, umm.. outdated :))
Now..
- How would I go about compiling my own custom Anduril.. ? Would I need to.. idk, clone a custom fork or something.. ? And is the compiler online, on the launchpad site, or.. ?
I just want to start making some small changes to customize my lights, now that I've got my Flashing Kit on yesterday.
Things like stop at Moonlight while 1H from Off, instead of continuing to ramp, removing Muggle mode entirely, maybe change the Aux LED's R&G only as Batt. Lvl. Indicator and B as Cfg. Mode Status (instead of the main LED's) change the batt. cut-off voltage to ~3.2V, remove the mid ramp blinks, change the default On brightness (say.. a fraction of the ceil, ex. 1/2, 1/3, 1/4, 1/5... etc. of the ceil) and other fun bits like these..
Hey everyone, I was able to flash my D4V2 with “anduril.2019-09-28.emisar-d4v2.hex” on the z flasher app app fine. When I tried to flash my D1 with “anduril.2019-09-28.emisar-d1.hex” and with the 8/5 version, D1 no longer works. The LED with flicker erratically, but no response. Is it bricked? How do you successfully flash the D1?
No, it is not bricked. As long as you don’t change the fuses it’s almost impossible to “brick” an ATtiny. You can simply try to flash it again (using the correct parameters and hex file). The flashing app should have noticed that it’s a different MCU.
Glad it’s not bricked. Initially I chose attiny1634, the app said flash successful. Then I tried attiny 85 and the flash was unsuccessful. Did this a few times. I can try again tonight.
I tried using otg adapter using my S10+. It’s saying error. When I looked in the log it said it wasn’t the right format. Does anyone know what I might have done wrong?
I attempted it again afew times with the attiny85 in the settings in the mobile app. Same result. There’s a pop-up with the message ” operation complete with errors!” The last few lines of the log read:
Tried the windows method with that command line, same error. Also tried both attiny1634 and attiny85 options on both windows and mobile app, same result, light not operational