How To Build a Flashlight With Perfect Modes (picture heavy)

I am using this USB isp programmer perhaps this is my problem?

It looks like you are not executing avrdude in the directory the target files are located in. Either cd into the directory holding the target files or give a full path on the command line.

Btw, before going to jump on the programming bandwagon i would like some answers from the masterminds behind this.

1. Are the KD 3x amc based drivers still working with this equipment?

2. Is it possible to program the chip to have lets say 1A high 500mA med and 50mA low AND have a beacon mode added 0,1Hz?

3. Is it possible to implement ramping with memory?

4. Can a potential beacon mode be hidden in the UI?

5. Can this be done also on the 8xamc based KD driver also?

Thanks. :)

Thanks Tido I changed the location of the target files now it only cannot find the .eep file

Probably yes. The last batch I ordered about three months ago was still equipped with ATtiny13s.

Yes. Well, not truly constant 50/500mA, but a PWM level that averages out to this values.

No. This would require one write cycle to the EEPROM for every light level passed during the ramping. Since the EEPROM ist rated for "only" 100,000 write cycles, this would probably wear it out in less than 1000 ramping operations.

Yes. Put it in the extended mode group, but not the main one.

If it is still based on the ATtiny13, yes.

You're welcome ;)

Have you moved both files (BLF-VLD.hex and BLF-VLD.eep)?

Tido, thank you very much. :)

It would be nice if someone makes a frontend for all that load of apps with dropboxes to quick select custom driver options and autocompile the choices in a flash ready format.

It can be done but someone must really sweat that one app. Willing to donate a few bucks for the martyr who would like to try such project and i bet i'm not the only one willing to contribute.

I really do not like the idea of learning some C++ or what is this based on (at least is not plain assembler).

Not me. I've even given up on keeping all possible driver configurations within a single source file. It's much easier and less error prone to just paste together a new driver from a library of standard functions and then add some glue code to make it all work together. At least if you know some basic C programming.

Sadly 0 programming experience. :/

Actually the only reason i don't have the hardware yet is i never fully understood the rewiring of the soic clip to the usb programmer interface as from what i gathered have to be fiddled with.

Anybody got any ideas?

Hi first post,

I have been following this thread with great interest (thank you Tido and everyone for the resource) and have purchased an avrispmkII and 3M soic clip. I am trying to reprogram a 2.8amp (8x 7135) driver that I purchased from Shiningbeam. I've hit a snag. Below is a screenshot of the error message I'm receiving. At first I thought the connection was bad but the green light comes on after I run the command, apparently indicating that the chip/target is receiving power. I've checked pinout three times, and I seem to have continuity in all pins. Any ideas from anyone? Is this the type of message I would get if the reprogramming fuse is set to prevent re-writing? Anything else I could check?

-Jon

Macintosh-3:~ JCI$ avrdude -P usb -p t13 -c avrispmkII -n

avrdude: stk500v2_command(): command failed

avrdude: stk500v2_command(): unknown status 0xc9

avrdude: stk500v2_program_enable(): cannot get connection status

avrdude: initialization failed, rc=-1

Double check connections and try again, or use -F to override

this check.

avrdude done. Thank you.

Looks like your connection isn't good, but I gave up a while ago I hit a dead end with my programming at this point. I actually de soldered a tiny13 chip to play around with so I can get the connections on easier. Sorry I couldn't be more help.

Use your multimeter and go from the clip to the programmer and make sure there is continuity again. It is written kind of weird I had to do mine twice because i read it wrong the first time before i got the right connections.

http://flashlight-wiki.com/AVR_Drivers

Thanks for the suggestion, I double checked the continuity with DMM and even soldered the leads directly to the pins on the chip, and the continuity was good between avrisp board pins and the chip pins. I don't know what else to do. I have another question: if you test the voltage between the vcc and gnd pins on the programmer (avrispmkII), should there be a constant voltage of 5V? Mine is showing basically no voltage between vcc and gnd on the programmer. I know I'm using a power usb.

I just pinned mine out and except for the ground closest to the VCC pin the rest have 5 volts (VCC-Ground)

So I just finished reading a review of the avrisp mkII, and it happened to mention that this programmer only senses voltage, but does NOT supply power to the target. Oops. So, I connected an xml to the driver, and soldered up a simple switched circuit to power the driver with 1 18650 3.7V li-ion, and wouldn't you know it, now I get a response! Of course, being me, I don't get the correct response:

Macintosh-3:~ JCI$ avrdude -P usb -p t13 -c avrispmkII -B 1 -u -Uflash:r:flash-dump.hex:i -Ueeprom:r:eeprom-dump.hex:i -Ulfuse:r:lfuse-dump.hex:i -Uhfuse:r:hfuse-dump.hex:i

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x068001

avrdude: Expected signature for ATtiny13 is 1E 90 07

Double check chip, or use -F to override this check.

avrdude done. Thank you.

Does anyone know why my attiny13A chip would spit out the wrong device sig? Anything I can do about it?

One thing I do know is that I'm getting a USBtinyisp so I don't have to rig a separate power source, which is cumbersome and impractical to use.

So, some progress, but still not able to load Tido's code yet.

-Jon

that is were i have been for about 2 months now

Wow,

When I first saw this thread, I was excited. I was thinking that I could get a 4-Mode driver w/memory, High-100%, Medium-50%, Low-15%, Moon-light-2%.

This conversation has gone so far over my head, that I'm back to searching the internet for an alternative. I don't think that this level of modding is EVER going to be within my reach 8-( .

Just to throw in my 2¢, if anyone gets to where they are custom programming some of these drivers, I'd like to buy 3-5 of them. Nothing fancy, just 4 modes, no strobes, w/memory.

Let us non-programmer types know. I'm still going to keep watching, but I'm not understanding a lot of what I'm reading.

Thanks, and keep up the good work!

I here you man I have been fighting with this for a couple months at this point I have given up. Maybe I will try again soon.

Let's make a pool to make someone savvy make a few custom flash ready images with desired modes for us to use. That's it.

Get the soic clip the usb programmer load that load of apps and flash rightaway. About 5 versions per drivery type (the most common would probably fit 90% of requests). Unless i'm missing something it would certainly be doable.

4 modes with low low, 3 modes with XY spacing, 4 mode H-M-L or L-M-H with beacon. etc...