| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Result not always 64 - bad assumption that page size is always 64
|
|
|
|
|
|
|
|
|
|
| |
fine-toothed comb:
main.c
- POSTSCRIPT_SIZE should be 6, not 4, now that there's a word to store OSCCAL
micronucleus_lib.c
- bcdUSB referring to USB Spec 1.1 is used, instead of bcdDevice, referring to the device release number
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Maybe a little more future/past proof now?
|
|
|
|
| |
step progress)
|
|
|
|
| |
throughout commandline c code (all variables underscore_cased, all functions lowerCamelCased).
|
|
|
|
| |
of api which allow risky writing strategies.
|
|
|