Any further progress?
I finally found work (yay) so I’ve been busy this week and haven’t had time to work on it anymore
Still not 100% I’ve got rid of extra bits and the turn off function works beautifully but when you unplug and try to turn it back on sometimes it will shut off after a second but if left for 6 ish seconds it works perfectly just need to get the turn back on function tweaked. I’ve just been really busy with work this week and trying to get some outstanding builds done. (Red S2+, MTG2 Mag and MTG2 MT40) I’ll keep playing with it after the weekend.
When you say “I finally found work (yay)”, did you mean you just got a new job? If so, congrats!!!
Jim
Is this a good program for flashing?
It looks good to me, but most of this is still martian at my level of understanding…
I have been playing with it a bit, but not flashed anything yet…
I would appreciate more experienced “flashers” opinion.
Looks fine to me, a GUI wrapper for avrdude. I can’t really say much about GUIs or Windows or OSX though, since I don’t use them. Perhaps someone else has thoughts? Does AVR Studio have avrdude stuff built in?
My typical development session looks about like this:
tk @ home : ~/> cd src/torches/sandbox/ToyKeeper/foo
tk @ home : foo/> gvim foo.c
tk @ home : foo/> ../../bin/build.sh foo
tk @ home : foo/> ../../bin/flash.sh foo.hex
tk @ home : foo/> ../../bin/build.sh foo
tk @ home : foo/> ../../bin/flash.sh foo.hex
tk @ home : foo/> ../../bin/build.sh foo
tk @ home : foo/> ../../bin/flash.sh foo.hex
...
Except I don’t have to type most of that. The tab key auto-completes a lot of things, and the repeated commands at the end are simply “up, up, enter”. And I left out the revision control commands, but I recommend using bzr or git if you want to do much serious development.
I was switching over to a new PC today, & went to d/load v6.2, but noticed that v7 had just been released.
I'm still d/loading as I type, so can't give any feedback yet.
Anyone else taken the plunge?
v7 Up & running, tested by building the A6 firmware.
Had to set the optimize for size (-Os), as per previous versions.
Cool. BTW, what size was the output? Does it let you see the actual gcc command line? I get 1002 bytes:
[-(Sun 2015-09-27 14:43:22)-(~/src/torches/trunk/ToyKeeper/blf-a6/)-]> ../../bin/build.sh blf-a6
avr-gcc -Wall -g -Os -mmcu=attiny13 -c -std=gnu99 -DATTINY=13 -o blf-a6.o -c blf-a6.c
avr-gcc -Wall -g -Os -mmcu=attiny13 -o blf-a6.elf blf-a6.o
avr-objcopy --set-section-flags=.eeprom=alloc,load --change-section-lma .eeprom=0 --no-change-warnings -O ihex blf-a6.elf blf-a6.hex
Program: 1002 bytes (97.9% Full)
Data: 13 bytes (20.3% Full)
Here's the entire output stream;
---------------
"D:\Program Files (x86)\Atmel\Studio\7.0\toolchain\avr8\avr8-gnu-toolchain\bin\avr-gcc.exe" -o GccApplication2.elf main.o -Wl,-Map="GccApplication2.map" -Wl,--start-group -Wl,-lm -Wl,--end-group -Wl,--gc-sections -mmcu=attiny13a -B "D:\Program Files (x86)\Atmel\Studio\7.0\Packs\atmel\ATtiny_DFP\1.0.68\gcc\dev\attiny13a"
Finished building target: GccApplication2.elf
"D:\Program Files (x86)\Atmel\Studio\7.0\toolchain\avr8\avr8-gnu-toolchain\bin\avr-objcopy.exe" -O ihex -R .eeprom -R .fuse -R .lock -R .signature -R .user_signatures "GccApplication2.elf" "GccApplication2.hex"
"D:\Program Files (x86)\Atmel\Studio\7.0\toolchain\avr8\avr8-gnu-toolchain\bin\avr-objcopy.exe" -j .eeprom --set-section-flags=.eeprom=alloc,load --change-section-lma .eeprom=0 --no-change-warnings -O ihex "GccApplication2.elf" "GccApplication2.eep" || exit 0
"D:\Program Files (x86)\Atmel\Studio\7.0\toolchain\avr8\avr8-gnu-toolchain\bin\avr-objdump.exe" -h -S "GccApplication2.elf" > "GccApplication2.lss"
"D:\Program Files (x86)\Atmel\Studio\7.0\toolchain\avr8\avr8-gnu-toolchain\bin\avr-objcopy.exe" -O srec -R .eeprom -R .fuse -R .lock -R .signature -R .user_signatures "GccApplication2.elf" "GccApplication2.srec"
"D:\Program Files (x86)\Atmel\Studio\7.0\toolchain\avr8\avr8-gnu-toolchain\bin\avr-size.exe" "GccApplication2.elf"
text data bss dec hex filename
996 0 13 1009 3f1 GccApplication2.elf
Done executing task "RunCompilerTask".
Using "RunOutputFileVerifyTask" task from assembly "D:\Program Files (x86)\Atmel\Studio\7.0\Extensions\Application\AvrGCC.dll".
Task "RunOutputFileVerifyTask"
Program Memory Usage : 996 bytes 97.3 % Full
Data Memory Usage : 13 bytes 20.3 % Full
Done executing task "RunOutputFileVerifyTask".
Done building target "CoreBuild" in project "GccApplication2.cproj".
Target "PostBuildEvent" skipped, due to false condition; ('$(PostBuildEvent)' != '') was evaluated as ('' != '').
Target "Build" in file "D:\Program Files (x86)\Atmel\Studio\7.0\Vs\Avr.common.targets" from project "C:\Users\FmC\Documents\Atmel Studio\7.0\GccApplication2\GccApplication2\GccApplication2.cproj" (entry point):
Done building target "Build" in project "GccApplication2.cproj".
Done building project "GccApplication2.cproj".
---------------
Hi,
Does anyone know if there is firmware that works similar to the FT NANJGs, i.e., where you can switch between one of 2 mode groups via clicking in low mode and which would work with a single FET driver with PWM on pin 6 on an ATTINY13A:
Group 1: Low - Medium - High
Group 2: Low - Medium - High - Strobe - SOS
Also, where it’d be fairly easy to modify the modes in the mode groups in the source.
Basically, I want to have a UI in a ATTINY13A-based FET driver that mimics the FT NANJGs, but where I’d probably add a moonlight to both mode groups.
Thanks,
Jim
Using JohnyCs star off time how would I get a tubo timer that is like 6 min?
http://bazaar.launchpad.net/~toykeeper/flashlight-firmware/trunk/view/head:/JonnyC/STAR/STAR_off_time/STAR_off_time.c
I see that I need either more possible ticks than 255 or longer than 500ms, but I am not certain what to change.
Oops, I just realized this thread wasn’t sticky. It is now.
Thanks! Good idea :)!
D’oh. It looks like that includes everything except the first step, the one where it converts a .c file into a .o file. And that’s the one I’m most hoping to see. 
In any case, it appears that the new version saves about 6 bytes. I’d like to know what build options it uses to make the result smaller. Maybe it’s just a newer version of gcc, but maybe not.
The main options right now are STAR or NLITE, and neither is quite what you described. I don’t think anyone has done the mode group switch via blink-on-low, because very few people seem to like that. Neither one has blinky modes, either. STAR’s code is open though, if you’d like to use it as a starting point.
Change the ‘ticks’ variable to a uint16_t and set its limit to 65535, and then you can have a turbo timeout up to about 9 hours.
This may be what you are interested in?;
Invoking: AVR/GNU C Compiler : 4.9.2
"D:\Program Files (x86)\Atmel\Studio\7.0\toolchain\avr8\avr8-gnu-toolchain\bin\avr-gcc.exe" -x c -funsigned-char -funsigned-bitfields -DDEBUG -I"D:\Program Files (x86)\Atmel\Studio\7.0\Packs\atmel\ATtiny_DFP\1.0.68\include" -Os -ffunction-sections -fdata-sections -fpack-struct -fshort-enums -g2 -Wall -mmcu=attiny13a -B "D:\Program Files (x86)\Atmel\Studio\7.0\Packs\atmel\ATtiny_DFP\1.0.68\gcc\dev\attiny13a" -c -std=gnu99 -MD -MP -MF "main.d" -MT"main.d" -MT"main.o" -o "main.o" ".././main.c"
Finished building: .././main.c
Maybe I missed it this morning, as I was running late for work when I posted.
Thanks TK.
I clipped this beginning at line 272.
ISR(WDT_vect) { static uint8_t ticks = 0; if (ticks < 255) ticks++; // If you want more than 255 for longer turbo timeouts //static uint16_t ticks = 0; //if (ticks < 60000) ticks++;Is this the correct place to change it from?
So it will look like this?
ISR(WDT_vect) {
static uint16_t ticks = 0;
if (ticks < 65535) ticks++;
// If you want more than 255 for longer turbo timeouts
//static uint16_t ticks = 0;
//if (ticks < 60000) ticks++;
Think it should be:
ISR(WDT_vect) {
//static uint8_t ticks = 0;
//if (ticks < 255) ticks++;
// If you want more than 255 for longer turbo timeouts
static uint16_t ticks = 0;
if (ticks < 65535) ticks++;
Oh duh, your probly right. I did not even notice that bit at the bottom where it already had the static uint16_t ticks = 0; bit.
I had tried before asking in the thread by just enabling the 6000 ticks part and commenting out the unit_8 bit.
I will try that and report back.