I have run the avrdude manual through a aspell check and fixed some some
transposed letters.
(avrdude.texi.01.spellings.diff)
The actual reason for looking into the documentation source is patch 2. I was
puzzling about the mentioned options -i, -f, -o and -m. By examining the
getopt(3) string, it strikes me all of them are actually gone (-i being
recycled as delay option).
(avrdude.texi.02.unknown-options.diff)
Unless I have missed something, please consider those patches for inclusion in
avrdude. Both patches are against the HEAD revision (r841) in trunk and should
be applied in order.
Cheers
Thomas
Index: avrdude.texi
===================================================================
--- avrdude.texi (revision 841)
+++ avrdude.texi (working copy)
@@ -139,7 +139,7 @@
bytes) or via an interactive (terminal) mode. Using AVRDUDE from the
command line works well for programming the entire memory of the chip
from the contents of a file, while interactive mode is useful for
-exploring memory contents, modifing individual bytes of eeprom,
+exploring memory contents, modifying individual bytes of eeprom,
programming fuse/lock bits, etc.
AVRDUDE supports the following basic programmer types: Atmel's STK500,
@@ -177,12 +177,12 @@
The fundamental difference between the two types lies in the
protocol used to control the programmer. The avr910 protocol is very
simplistic and can easily be used as the basis for a simple, home made
-programer since the firmware is available online. On the other hand,
+programmer since the firmware is available online. On the other hand,
the STK500 protocol is more robust and complicated and the firmware is
not openly available.
The JTAG ICE also uses a serial communication protocol which is similar
to the STK500 firmware version 2 one. However, as the JTAG ICE is
-intented to allow on-chip debugging as well as memory programming, the
+intended to allow on-chip debugging as well as memory programming, the
protocol is more sophisticated.
(The JTAG ICE mkII protocol can also be run on top of USB.)
Only the memory programming functionality of the JTAG ICE is supported
@@ -206,7 +206,7 @@
The USBasp ISP and USBtinyISP adapters are also supported, provided AVRDUDE
has been compiled with libusb support.
-They both feature simple firwmare-only USB implementations, running on
+They both feature simple firmware-only USB implementations, running on
an ATmega8 (or ATmega88), or ATtiny2313, respectively.
@@ -661,7 +661,7 @@
programming, then verifying at the end of programming that the fuses have not
changed. If you want to change fuses you will need to specify this option,
as avrdude will see the fuses have changed (even though you wanted to) and
-will change them back for your "saftey". This option was designed to
+will change them back for your "safety". This option was designed to
prevent cases of fuse bits magically changing (usually called @emph{safemode}).
@item -t
@@ -670,10 +670,10 @@
terminal mode.
@item -U @var{memtype}:@var{op}:@var{filename}[:@var{format}]
-Perform a memory operation, equivalent to specifing the @option{-m},
+Perform a memory operation, equivalent to specifying 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
+multiple @option{-U} options can be specified in order to operate on
+multiple 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
@@ -735,7 +735,7 @@
@itemx m
immediate mode; actual byte values specified on the command line,
-seperated by commas or spaces in place of the @var{filename} field of
+separated by commas or spaces in place of the @var{filename} field of
the @option{-i}, @option{-o}, or @option{-U} options. This is useful
for programming fuse bytes without having to create a single-byte file
or enter terminal mode. If the number specified begins with @code{0x},
@@ -1273,7 +1273,7 @@
AVRDUDE first looks for a system wide configuration file in a platform
dependent location. On Unix, this is usually
-...@code{/usr/local/etc/avrdude.conf}, while on Windows it is usally in the
+...@code{/usr/local/etc/avrdude.conf}, while on Windows it is usually in the
same location as the executable file. The name of this file can be
changed using the @option{-C} command line option. After the system wide
configuration file is parsed, AVRDUDE looks for a per-user configuration
@@ -1298,15 +1298,15 @@
@table @code
@item default_parallel = "@var{default-parallel-device}";
-Assign the default parallel port device. Can be overidden using the
+Assign the default parallel port device. Can be overridden using the
@option{-P} option.
@item default_serial = "@var{default-serial-device}";
-Assign the default serial port device. Can be overidden using the
+Assign the default serial port device. Can be overridden using the
@option{-P} option.
@item default_programmer = "@var{default-programmer-id}";
-Assign the default programmer id. Can be overidden using the @option{-c}
+Assign the default programmer id. Can be overridden using the @option{-c}
option.
@end table
@@ -1392,7 +1392,7 @@
@subsection Instruction Format
@noindent
-Instruction formats are specified as a comma seperated list of string
+Instruction formats are specified as a comma separated list of string
values containing information (bit specifiers) about each of the 32 bits
of the instruction. Bit specifiers may be one of the following formats:
@@ -1671,7 +1671,7 @@
@subsubsection Linux Installation
@noindent
-On rpm based linux systems (such as RedHat, SUSE, Mandrake, etc), you
+On rpm based Linux systems (such as RedHat, SUSE, Mandrake, etc), you
can build and install the rpm binaries directly from the tarball:
@example
@@ -2055,7 +2055,7 @@
@item
-Problem: I'm using linux and my AVR910 programmer is really slow.
+Problem: I'm using Linux and my AVR910 programmer is really slow.
Solution (short): @code{setserial @var{port} low_latency}
@@ -2075,7 +2075,7 @@
@item
-Problem: I'm not using linux and my AVR910 programmer is really slow.
+Problem: I'm not using Linux and my AVR910 programmer is really slow.
Solutions: The reasons for this are the same as above.
If you know how to work around this on your OS, please let us know.
@@ -2123,7 +2123,7 @@
JTAG-to-ISP adapter, so the JTAG ICE mkII can be used as a debugWire
initiator as well as an ISP programmer. AVRDUDE will then be activated
using the @var{jtag2isp} programmer type. The initial ISP
-communication attempt will fail, but AVRDUDE then tries to iniate a
+communication attempt will fail, but AVRDUDE then tries to initiate a
debugWire reset. When successful, this will leave the target AVR in a
state where it can accept standard ISP communication. The ICE is then
signed off (which will make it signing off from the USB as well), so
@@ -2160,7 +2160,7 @@
using the @var{/RESET} line.
DebugWire mode is initiated by activating the @var{DWEN}
fuse, and then power-cycling the target.
-While this mode is mainly intented for debugging/emulation, it
+While this mode is mainly intended for debugging/emulation, it
also offers limited programming capabilities.
Effectively, the only memory areas that can be read or programmed
in this mode are flash ROM and EEPROM.
--- avrdude.texi 2009-09-21 11:50:47.000000000 +0100
+++ avrdude.texi2 2009-09-21 11:53:05.000000000 +0100
@@ -670,9 +670,8 @@
terminal mode.
@item -U @var{memtype}:@var{op}:@var{filename}[:@var{format}]
-Perform a memory operation, equivalent to specifying the @option{-m},
-...@option{-i} or @option{-o}, and @option{-f} options, except that
-multiple @option{-U} options can be specified in order to operate on
+Perform a memory operation.
+Multiple @option{-U} options can be specified in order to operate on
multiple 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
@@ -736,7 +735,7 @@
@itemx m
immediate mode; actual byte values specified on the command line,
separated by commas or spaces in place of the @var{filename} field of
-the @option{-i}, @option{-o}, or @option{-U} options. This is useful
+the @option{-U} option. This is useful
for programming fuse bytes without having to create a single-byte file
or enter terminal mode. If the number specified begins with @code{0x},
it is treated as a hex value. If the number otherwise begins with a
_______________________________________________
avrdude-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev
