10a26677f8* ChangeLog: Format cleanups. All indents should be a single tab and lines should be less than 80 chars including 8 spaces for the tab. Date should be YYYY-MM-DD not YYYY/MM/DD.
troth
2003-09-05 16:25:00 +0000
06cc3697ac* ChangeLog: Format cleanups. All indents should be a single tab and lines should be less than 80 chars including 8 spaces for the tab. Date should be YYYY-MM-DD not YYYY/MM/DD.
Theodore A. Roth
2003-09-05 16:25:00 +0000
ed14409bf9* ChangeLog: Format cleanups. All indents should be a single tab and lines should be less than 80 chars including 8 spaces for the tab. Date should be YYYY-MM-DD not YYYY/MM/DD.
Theodore A. Roth
2003-09-05 16:25:00 +0000
25116822c0* Makefile.am: Change AM_CPPFLAGS to avrdude_CPPFLAGS. Define avrdude_CFLAGS. * configure.ac: Set ENABLE_WARNINGS to "-Wall" if using gcc.
troth
2003-09-05 04:23:27 +0000
f757b913ff* Makefile.am: Change AM_CPPFLAGS to avrdude_CPPFLAGS. Define avrdude_CFLAGS. * configure.ac: Set ENABLE_WARNINGS to "-Wall" if using gcc.
Theodore A. Roth
2003-09-05 04:23:27 +0000
ea652e7b78* Makefile.am: Change AM_CPPFLAGS to avrdude_CPPFLAGS. Define avrdude_CFLAGS. * configure.ac: Set ENABLE_WARNINGS to "-Wall" if using gcc.
Theodore A. Roth
2003-09-05 04:23:27 +0000
4df01a2189Add an extended example of using the -U option to update the flash, eeprom, efuse, hfuse, and lfuse on a single command line. Much of the output had to be ommitted from the example since the texi commands for formatting the example don't allow page breaks within the example. If someone knows a better way to format it, please feel free to do so.
bdean
2003-09-04 01:01:40 +0000
181436e0b8Add an extended example of using the -U option to update the flash, eeprom, efuse, hfuse, and lfuse on a single command line. Much of the output had to be ommitted from the example since the texi commands for formatting the example don't allow page breaks within the example. If someone knows a better way to format it, please feel free to do so.
Brian S. Dean
2003-09-04 01:01:40 +0000
3bd2da1766Add an extended example of using the -U option to update the flash, eeprom, efuse, hfuse, and lfuse on a single command line. Much of the output had to be ommitted from the example since the texi commands for formatting the example don't allow page breaks within the example. If someone knows a better way to format it, please feel free to do so.
Brian S. Dean
2003-09-04 01:01:40 +0000
b8e9e89d07* doc/avrdude.texi: Add note about privileges needed to load the giveio driver for Windows.
arcanum
2003-09-02 16:40:06 +0000
b47fd376fa* doc/avrdude.texi: Add note about privileges needed to load the giveio driver for Windows.
Eric Weddington
2003-09-02 16:40:06 +0000
d1eb58dbde* doc/avrdude.texi: Add note about privileges needed to load the giveio driver for Windows.
Eric Weddington
2003-09-02 16:40:06 +0000
0b71c0672cRevert to honoring the return code from pgm->pgm_enable() within the stk500 initialization routine. However, allow one to use the -F option to ignore a bad return code from that function. I think this still allows what Joerg intended, i.e., providing a way to still get into terminal mode so that one can recover from setting bad STK500 values which may keep the chip from entering programming mode.
bdean
2003-08-31 15:40:59 +0000
fab896d9e4Revert to honoring the return code from pgm->pgm_enable() within the stk500 initialization routine. However, allow one to use the -F option to ignore a bad return code from that function. I think this still allows what Joerg intended, i.e., providing a way to still get into terminal mode so that one can recover from setting bad STK500 values which may keep the chip from entering programming mode.
Brian S. Dean
2003-08-31 15:40:59 +0000
ede8a48d52Revert to honoring the return code from pgm->pgm_enable() within the stk500 initialization routine. However, allow one to use the -F option to ignore a bad return code from that function. I think this still allows what Joerg intended, i.e., providing a way to still get into terminal mode so that one can recover from setting bad STK500 values which may keep the chip from entering programming mode.
Brian S. Dean
2003-08-31 15:40:59 +0000
a7075e8d21Make a note about the new auto erase default and exceptions.
bdean
2003-08-29 23:23:25 +0000
de3070f5caMake a note about the new auto erase default and exceptions.
Brian S. Dean
2003-08-29 23:23:25 +0000
6acb859507Make a note about the new auto erase default and exceptions.
Brian S. Dean
2003-08-29 23:23:25 +0000
dd38310828Document auto erase default for -U flash write requests.
bdean
2003-08-29 23:19:44 +0000
6cbe3862d6Document auto erase default for -U flash write requests.
Brian S. Dean
2003-08-29 23:19:44 +0000
698769dccaDocument auto erase default for -U flash write requests.
Brian S. Dean
2003-08-29 23:19:44 +0000
776104ea0cPerform an auto erase before programming if the flash memory is anywhere specified to be written by any of the -U requests.
bdean
2003-08-29 23:17:32 +0000
4041cfe4d2Perform an auto erase before programming if the flash memory is anywhere specified to be written by any of the -U requests.
Brian S. Dean
2003-08-29 23:17:32 +0000
1188a0313bPerform an auto erase before programming if the flash memory is anywhere specified to be written by any of the -U requests.
Brian S. Dean
2003-08-29 23:17:32 +0000
cc1bb36860Add some forgotten entries.
bdean
2003-08-29 01:47:47 +0000
f41922847cAdd some forgotten entries.
Brian S. Dean
2003-08-29 01:47:47 +0000
ae39cd7c57Add some forgotten entries.
Brian S. Dean
2003-08-29 01:47:47 +0000
1de16c56edDeclare size and vsize as 'int'. These represent the size of the AVR memory read or written (or up to where continuous 0xff begins in the case of flash memory). An 'int' should be plenty big enough for that.
bdean
2003-08-29 00:14:22 +0000
f8e3aee203Declare size and vsize as 'int'. These represent the size of the AVR memory read or written (or up to where continuous 0xff begins in the case of flash memory). An 'int' should be plenty big enough for that.
Brian S. Dean
2003-08-29 00:14:22 +0000
77bc532fd2Declare size and vsize as 'int'. These represent the size of the AVR memory read or written (or up to where continuous 0xff begins in the case of flash memory). An 'int' should be plenty big enough for that.
Brian S. Dean
2003-08-29 00:14:22 +0000
d3b2337564Add entry about "immediate mode."
bdean
2003-08-28 23:42:51 +0000
0a685d7265Add entry about "immediate mode."
Brian S. Dean
2003-08-28 23:42:51 +0000
ce6e943739Add entry about "immediate mode."
Brian S. Dean
2003-08-28 23:42:51 +0000
51a3d56245* avr910.c: * fileio.c: * main.c: * stk500.c: More code cleanup to remove warnings.
arcanum
2003-08-28 23:02:25 +0000
4f05a28329* avr910.c: * fileio.c: * main.c: * stk500.c: More code cleanup to remove warnings.
Eric Weddington
2003-08-28 23:02:25 +0000
9560dfe881* avr910.c: * fileio.c: * main.c: * stk500.c: More code cleanup to remove warnings.
Eric Weddington
2003-08-28 23:02:25 +0000
b5c352760aMake a note about -U option.
bdean
2003-08-28 18:41:43 +0000
f2474f71b3Make a note about -U option.
Brian S. Dean
2003-08-28 18:41:43 +0000
61c60d3b5bMake a note about -U option.
Brian S. Dean
2003-08-28 18:41:43 +0000
1ec1c1c2eaFix fuse bit setting example. This closes bug #4027 submitted by (unknown).
bdean
2003-08-28 14:00:07 +0000
3ce217e65eFix fuse bit setting example. This closes bug #4027 submitted by (unknown).
Brian S. Dean
2003-08-28 14:00:07 +0000
f2a77c44f0Fix fuse bit setting example. This closes bug #4027 submitted by (unknown).
Brian S. Dean
2003-08-28 14:00:07 +0000
386f8f19dbFix placement of local variable - variables must be declared before any statements within a block.
bdean
2003-08-28 13:52:52 +0000
37b213c599Fix placement of local variable - variables must be declared before any statements within a block.
Brian S. Dean
2003-08-28 13:52:52 +0000
3c507aee9eFix placement of local variable - variables must be declared before any statements within a block.
Brian S. Dean
2003-08-28 13:52:52 +0000
1abe56733f* main.c (update_progress_no_tty): Properly terminate progress. Also fixes stk500 problem where number of bytes written is less than a page.
troth
2003-08-28 05:37:57 +0000
282dfb1eac* main.c (update_progress_no_tty): Properly terminate progress. Also fixes stk500 problem where number of bytes written is less than a page.
Theodore A. Roth
2003-08-28 05:37:57 +0000
964a170f39* main.c (update_progress_no_tty): Properly terminate progress. Also fixes stk500 problem where number of bytes written is less than a page.
Theodore A. Roth
2003-08-28 05:37:57 +0000
d0506ab0f9Remove debugging printf.
Brian S. Dean
2003-08-24 18:05:46 +0000
96b8604351Remove debugging printf.
Brian S. Dean
2003-08-24 18:05:46 +0000
eecf43999dIntroduce a new option, -U, for performing memory operions. Its argument is a 4 field string (fields seperated by colons) which indicate what memory type to operate on, what operation to perform is (read, write, or verify), the filename to read from, write to, or verify against, and an optional file format field. Multple -U options can be specified to operate on more than one memory at a time with a single invocation. For example, to update both the flash and the eeprom at the same time one can now specify the following:
bdean
2003-08-21 04:52:36 +0000
87ce6adaf5Introduce a new option, -U, for performing memory operions. Its argument is a 4 field string (fields seperated by colons) which indicate what memory type to operate on, what operation to perform is (read, write, or verify), the filename to read from, write to, or verify against, and an optional file format field. Multple -U options can be specified to operate on more than one memory at a time with a single invocation. For example, to update both the flash and the eeprom at the same time one can now specify the following:
Brian S. Dean
2003-08-21 04:52:36 +0000
0d61a7e3f7Introduce a new option, -U, for performing memory operions. Its argument is a 4 field string (fields seperated by colons) which indicate what memory type to operate on, what operation to perform is (read, write, or verify), the filename to read from, write to, or verify against, and an optional file format field. Multple -U options can be specified to operate on more than one memory at a time with a single invocation. For example, to update both the flash and the eeprom at the same time one can now specify the following:
Brian S. Dean
2003-08-21 04:52:36 +0000
c5df201221Timing related fixes for the Windows platform. Several folks have reported that this patch fixes verify errors on the Windows platform that are apparently timing related. Submitted by: Alex Shepherd <ashepherd@wave.co.nz>, who indicates that this patch was based on code from the UISP project.
bdean
2003-08-20 00:16:27 +0000
8e6ff20780Timing related fixes for the Windows platform. Several folks have reported that this patch fixes verify errors on the Windows platform that are apparently timing related. Submitted by: Alex Shepherd <ashepherd@wave.co.nz>, who indicates that this patch was based on code from the UISP project.
Brian S. Dean
2003-08-20 00:16:27 +0000
b4a23dddc0Timing related fixes for the Windows platform. Several folks have reported that this patch fixes verify errors on the Windows platform that are apparently timing related. Submitted by: Alex Shepherd <ashepherd@wave.co.nz>, who indicates that this patch was based on code from the UISP project.
Brian S. Dean
2003-08-20 00:16:27 +0000
e341f7d3ec* avrdude.1: Document the -q option. * doc/avrdude.texi: Document the -q option. Fix some typos left over from pasting in man output.
troth
2003-08-01 20:11:21 +0000
7364032012* avrdude.1: Document the -q option. * doc/avrdude.texi: Document the -q option. Fix some typos left over from pasting in man output.
Theodore A. Roth
2003-08-01 20:11:21 +0000
ca01d072ab* avrdude.1: Document the -q option. * doc/avrdude.texi: Document the -q option. Fix some typos left over from pasting in man output.
Theodore A. Roth
2003-08-01 20:11:21 +0000
d6287689c1Add elapsed time information to the new progress bar.
bdean
2003-07-30 23:01:52 +0000
a255ff6ec5Add elapsed time information to the new progress bar.
Brian S. Dean
2003-07-30 23:01:52 +0000
f6a14f4c25Add elapsed time information to the new progress bar.
Brian S. Dean
2003-07-30 23:01:52 +0000
1c0432c52dAdd 'picoweb' programming cable programmer. Contributed by Rune Christensen <rune.christensen@adslhome.dk>.
Brian S. Dean
2003-07-22 01:29:19 +0000
6ff0c4a47eAdd 'picoweb' programming cable programmer. Contributed by Rune Christensen <rune.christensen@adslhome.dk>.
Brian S. Dean
2003-07-22 01:29:19 +0000
3f6564ba98Add the 'sp12' (Steve Bolt's) programmer.
bdean
2003-06-18 02:47:52 +0000
1af1e889a1Add the 'sp12' (Steve Bolt's) programmer.
Brian S. Dean
2003-06-18 02:47:52 +0000
ede6981133Add the 'sp12' (Steve Bolt's) programmer.
Brian S. Dean
2003-06-18 02:47:52 +0000
a16b1d35c0Properly identify the "ALF" programmer.
bdean
2003-06-17 21:35:39 +0000
e9b255689cProperly identify the "ALF" programmer.
Brian S. Dean
2003-06-17 21:35:39 +0000
3e70d4566fProperly identify the "ALF" programmer.
Brian S. Dean
2003-06-17 21:35:39 +0000
945358b4b3Optimize flash memory handling a little bit by ignoring 0xff data that resides above the last non-0xff data value in the address space. Only do this for flash memory since writing a 0xff to flash is a no-op. This has the affect of creating smaller output files when dumping memory contents from flash if the program in flash does not consume the whole memory space. It also results in shorter programming times when avrdude is asked to load a file into flash that has lots of 0xff filled data past the last non-0xff data value.
bdean
2003-05-22 02:33:17 +0000
b09107e9afOptimize flash memory handling a little bit by ignoring 0xff data that resides above the last non-0xff data value in the address space. Only do this for flash memory since writing a 0xff to flash is a no-op. This has the affect of creating smaller output files when dumping memory contents from flash if the program in flash does not consume the whole memory space. It also results in shorter programming times when avrdude is asked to load a file into flash that has lots of 0xff filled data past the last non-0xff data value.
Brian S. Dean
2003-05-22 02:33:17 +0000
4446ed3a7dOptimize flash memory handling a little bit by ignoring 0xff data that resides above the last non-0xff data value in the address space. Only do this for flash memory since writing a 0xff to flash is a no-op. This has the affect of creating smaller output files when dumping memory contents from flash if the program in flash does not consume the whole memory space. It also results in shorter programming times when avrdude is asked to load a file into flash that has lots of 0xff filled data past the last non-0xff data value.
Brian S. Dean
2003-05-22 02:33:17 +0000
ae435210a1Make the s-record output routine work like the raw and intel hex output routines (don't optimize away 0xff data before and after non 0xff data). Also, fix a bug where the data contents sometimes weren't written out completely.
bdean
2003-05-22 00:46:59 +0000