avr/avrdude
2
0
Fork 0
mirror of https://github.com/mariusgreuel/avrdude.git synced 2025-09-27 14:35:27 +00:00
Code Issues Projects Releases Wiki Activity

* avrdude.1, doc/avrdude.texi, doc/TODO: Removed the deprecated options from documentation

Browse Source 
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@411 81a1dc3b-b13d-400b-aceb-764788c761c2
This commit is contained in:
hinni
2004-02-10 00:20:51 +00:00
parent 34c5ee9f0d
commit db1a46c6ee
4 changed files with 81 additions and 158 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/TODO
View File

@@ -4,11 +4,9 @@
- Website needs to link to docs:
http://savannah.nongnu.org/download/avrdude/doc/avrdude-html/
- Remove old options from manpage and texinfo-documentation
- [Windows Port] Use Windows API for serial port communications (ser_win32.c).
(In Progress)
- Add "skip empty pages" optimization on avr910 paged write. The stk500 has
this optimization already.

125
doc/avrdude.texi
View File

@@ -420,10 +420,60 @@ program exit.
Multiple @var{exitspec} arguments can be separated with commas.
@item -F
Normally, AVRDUDE tries to verify that the device signature read from
the part is reasonable before continuing. Since it can happen from time
to time that a device has a broken (erased or overwritten) device
signature but is otherwise operating normally, this options is provided
to override the check.
@item -f @var{format}
This option specifies the file format for the input or output files to
be processed. Format can be one of:
@item -n
No-write - disables actually writing data to the MCU (useful for
debugging AVRDUDE).
@item -P @var{port}
Use port to identify the device to which the programmer is attached.
Normally, the default parallel port is used, but if the programmer type
normally connects to the serial port, the default serial port will be
used. See Appendix A, Platform Dependent Information, to find out the
default port names for your platform. If you need to use a different
parallel or serial port, use this option to specify the alternate port name.
@item -q
Disable (or quell) output of the progress bar while reading or writing
to the device.
@item -t
Tells AVRDUDE to enter the interactive ``terminal'' mode instead of up-
or downloading files. See below for a detailed description of the
terminal mode.
@item -U @var{memtype}:@var{op}:@var{filename}[:@var{format}]
Perform a memory operation, equivalent to specifing the @option{-m},
@option{-i} or @option{-o}, and @option{-f} options, except that
multiple @option{-U} optins can be specified in order to operate on
mulitple memories on the same command-line invocation. The
@var{memtype} field specifies the memory type to operate on. Use
the @option{-v} option on the command line or the @code{part} command from
terminal mode to display all the memory types supported by a particular
device.
The @var{op} field specifies what operation to perform:
@table @code
@itemx r
read the specified device memory and write to the specified file
@itemx w
read the specified file and write it to the specified device memory
@itemx v
read the specified device memory and the specified file and perform a verify operation
@end table
The @var{filename} field indicates the name of the file to read or
write. The @var{format} field is optional and contains the format of
the file to read or write. Possible values are:
@table @code
@itemx i
@@ -454,75 +504,6 @@ at stdin.
The default is to use auto detection for input files, and raw binary
format for output files.
@item -F
Normally, AVRDUDE tries to verify that the device signature read from
the part is reasonable before continuing. Since it can happen from time
to time that a device has a broken (erased or overwritten) device
signature but is otherwise operating normally, this options is provided
to override the check.
@item -i @var{filename}
Specifies the input file to be programmed into the MCU. Can be
specified as `-' to use stdin as the input.
@item -m @var{memtype}
Specifies which program area of the MCU to read or write; allowable
values depend on the MCU being programmed, but most support at least
@code{eeprom} for the EEPROM, and @code{flash} for the flash ROM. Use
the @option{-v} option on the command line or the @code{part} command from
terminal mode to display all the memory types supported by a particular
device. The default is @code{flash}.
@item -n
No-write - disables actually writing data to the MCU (useful for
debugging AVRDUDE).
@item -o @var{filename}
Specifies the name of the output file to write, and causes the
respective memory area to be read from the MCU. Can be specified as `-'
to write to stdout.
@item -P @var{port}
Use port to identify the device to which the programmer is attached.
Normally, the default parallel port is used, but if the programmer type
normally connects to the serial port, the default serial port will be
used. See Appendix A, Platform Dependent Information, to find out the
default port names for your platform. If you need to use a different
parallel or serial port, use this option to specify the alternate port name.
@item -q
Disable (or quell) output of the progress bar while reading or writing
to the device.
@item -t
Tells AVRDUDE to enter the interactive ``terminal'' mode instead of up-
or downloading files. See below for a detailed description of the
terminal mode.
@item -U @var{memtype}:@var{op}:@var{filename}[:@var{format}]
Perform a memory operation, equivalent to specifing the @option{-m},
@option{-i} or @option{-o}, and @option{-f} options, except that
multiple @option{-U} optins can be specified in order to operate on
mulitple memories on the same command-line invocation. The
@var{memtype} field specifies the memory type to operate on. The
@var{op} field specifies what operation to perform:
@table @code
@itemx r
read the specified device memory and write to the specified file
@itemx w
read the specified file and write it to the specified device memory
@itemx v
read the specified device memory and the specified file and perform a verify operation
@end table
The @var{filename} field indicates the name of the file to read or
write. The @var{format} field is optional and contains the format of
the file to read or write. See the @option{-f} option for possible
values.
Note that if @var{filename} contains a colon, the @var{format} field is
no longer optional since the filename part following the colon would
otherwise be misinterpreted as @var{format}.