summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bug in jumper mode!!! jumper pin was set to output, creating short circuits! ↵Bluebie2013-05-201-38/+36
| | | | update asap!
* firmware: no functional change - reorganised bootloader config to easily ↵Bluebie2013-03-061-9/+33
| | | | switch on and off -jumper variant by uncommenting out a define near the top
* Added 'jumper' varient of 1.06 to prebuilt releasesBluebie2013-03-063-3/+326
|
* Firmware & Upgrade: Released 1.06! yet to add -jumper release tho. Fixes ↵Bluebie2013-03-046-14/+343
| | | | clock speed thing - always starts at 16.5mhz now!
* firmware: start writing release notes for future 1.06 versionBluebie2013-03-041-0/+8
|
* firmware: added osccal store and retrieve code, untestedBluebie2013-03-042-24/+31
|
* commandline: bugfixes for -1 error after erase on OS X - auto recover now worksBluebie2013-02-202-14/+27
|
* Merge pull request #20 from psychogenic/masterJenna Fox2013-02-191-1/+9
|\ | | | | Fix for linux erase/write issue.
| * Tests on all Linux machines available led to errors such as:Malaclypse The Younger2013-02-191-1/+9
|/ | | | | | | | | | | | | | | | Erasing the memory ... erasing: 66% complete Error erasing: -84>> Abort mission! error has occured ... Please unplug the device and restart the program. Whereas Windows can recover from this condition with Eep! Connection to device lost during erase! Not to worry This happens on some computers - reconnecting... the Linux version could not correctly interpret the -84 error code returned by the USBDEVFS_CONTROL call. This modification fixes this, re-interpreting the -84 code to -2 and allowing the program to reconnect and succesfully upload the firmware.
* release: added release notes for -jumper variantBluebie2013-02-171-0/+12
|
* release & upgrade: added jumper varientBluebie2013-02-172-0/+134
|
* D5 version for deuxvisBluebie2013-02-083-4/+187
|
* experimental build with pin0 as boot button pinBluebie2013-02-081-16/+17
|
* upgrade: added 1.05 release - have tested upgrading from 1.02 to 1.05 and it ↵Bluebie2013-02-082-3/+184
| | | | seems fine.
* upgrade: now automatically reboots in to new bootloader when it's done doing ↵Bluebie2013-02-081-0/+8
| | | | the upgrade and has beeped.
* new release! 1.05 gives you the same more reliable timings from 1.02, with ↵Bluebie2013-02-082-2/+139
| | | | 66 more bytes program memory and an improved timeout mechanism!
* remove a little pointless code..Bluebie2013-02-081-1/+1
|
* remove old changelog file inherited from usbasploader-tiny85 - too confusingBluebie2013-02-081-34/+0
|
* revert timing to be like 1.02 - 5 sec wait, 8ms write delayBluebie2013-02-083-3/+10
|
* commandline: added timeout option (does it work on windows?)Bluebie2013-02-061-1/+25
|
* commandline: added new mac buildBluebie2013-02-061-0/+0
|
* commandline: raw support fixed, added --no-ansi mode for arduino/digispark ↵Bluebie2013-02-061-19/+34
| | | | use, made no-ansi mode on all platforms less spammy
* Fixed assignment in conditional bug. RAW uploads work now maybe? Thanks to ↵Bluebie2013-02-061-2/+2
| | | | @benjie on digistump.com forums
* commandline: Update Windows buildJenna Fox2012-11-301-0/+0
|
* commandline: Update Mac buildBluebie2012-11-301-0/+0
|
* commandline: pspgeek's usb fail workaroundBluebie2012-11-302-5/+27
|
* Added updated micronucleus.exe build, which goes extra slow and uses newer ↵Jenna Fox2012-11-192-1/+2
| | | | micronucleus_lib
* Slightly alter assert in micronucleus_lib.cJenna Fox2012-11-151-1/+1
| | | Maybe a little more future/past proof now?
* Firmware: updated .gitignoreJenna Fox2012-10-141-0/+3
|
* Firmware: Added a low-power release, suitable for chips with ckdiv8 programmed.Jenna Fox2012-10-141-0/+135
| | | | When it launches user program program, the chip is running at 8.0mhz, so can run at 3v within spec so long as PB3/D- isn't pulled high at startup (so skips boot loader) - so this works great if your usb circuitry is in a cable or dongle. If it accidentally runs the boot loader, it's only out of spec for 2.5 seconds.
* commandline: Updated readmeJenna Fox2012-10-101-6/+16
|
* Added some tech detailsBluebie2012-10-061-0/+51
|
* Release Notes for 1.04 releaseBluebie2012-10-051-2/+10
|
* upgrade: Add micronucleus 1.04 upgrade prebuiltBluebie2012-10-052-3/+183
|
* Firmware Release! 1.04 is now out.Bluebie2012-10-055-1/+134
|
* Change back to 2.5 sec bootloader delay - 2.0 seconds wasn't working ↵Bluebie2012-10-051-1/+1
| | | | reliably enough for my taste
* fix makefile to clean some uncleanly filesBluebie2012-10-051-1/+1
|
* Restructured firmware/releases folder, and added a 2.0 seconds build of 1.03Bluebie2012-10-054-0/+132
|
* adjusted default duration down to 2.0 seconds from 2.5 secondsBluebie2012-10-051-1/+1
|
* Reduced default WRITE_SLEEP value from 8 to 6, for 25% faster writing and ↵Bluebie2012-10-051-1/+1
| | | | erasing
* ruby: a little hex-to-bin converter because I was too lazy to find out how ↵Bluebie2012-10-051-0/+9
| | | | to make avr-gcc stuff do it.
* Improved upgrade mechanism - now it should actually work! I've successfully ↵Bluebie2012-10-055-190/+197
| | | | upgraded from 1.02 to 1.03 and 1.03 to 1.03. Haven't tested earlier versions of micronucleus or other bootloaders not based on USBaspLoader-tiny85
* ruby: Added better logging to HexProgramBluebie2012-10-051-1/+1
|
* Upgrade: add warning to readmeBluebie2012-10-051-0/+2
|
* Added low power mode, for chips which need to start with clkdiv8 and only ↵Bluebie2012-10-042-3/+44
| | | | switch to 16.5mhz when usb connection is detected somehow.
* Add license infoBluebie2012-10-041-0/+6
|
* Upgrade: Added note about rubyBluebie2012-10-041-1/+3
|
* Upgrade: Clarification about LED optionBluebie2012-10-041-1/+1
|
* Added viral in place upgrader tool, to upgrade bootloaders via the ↵Bluebie2012-10-047-0/+694
| | | | bootloader itself (should work with any attiny85 bootloader I think, in either direction)
* Fix off by one error in ruby HexProgram ihex parser classBluebie2012-10-041-4/+8
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-02 19:24:17 +0000