avr
/
avrdude
mirror of https://github.com/mariusgreuel/avrdude.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

patch #8895: Spelling in 6.2 code 

git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@1374 81a1dc3b-b13d-400b-aceb-764788c761c2
This commit is contained in:
Joerg Wunsch 2016-02-15 20:34:27 +00:00
parent c686946563
commit 7aa558e562
2 changed files with 17 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
2016-02-15 Joerg Wunsch <j.gnu@uriah.heep.sax.de>
patch #8894: Spelling in 6.2 doc
* doc/avrdude.texi: Various spelling fixes.
2016-02-15 Joerg Wunsch <j.gnu@uriah.heep.sax.de> 2016-02-15 Joerg Wunsch <j.gnu@uriah.heep.sax.de>
patch #8895: Spelling in 6.2 code patch #8895: Spelling in 6.2 code

20
doc/avrdude.texi
View File

@ -154,7 +154,7 @@ serial bit-bang adapters,
and the PPI (parallel port interface). PPI represents a class and the PPI (parallel port interface). PPI represents a class
of simple programmers where the programming lines are directly of simple programmers where the programming lines are directly
connected to the PC parallel port. Several pin configurations exist connected to the PC parallel port. Several pin configurations exist
for several variations of the PPI programmers, and AVRDUDE can be be for several variations of the PPI programmers, and AVRDUDE can be
configured to work with them by either specifying the appropriate configured to work with them by either specifying the appropriate
programmer on the command line or by creating a new entry in its programmer on the command line or by creating a new entry in its
configuration file. All that's usually required for a new entry is to configuration file. All that's usually required for a new entry is to
@ -173,7 +173,7 @@ available (like almost all embedded Linux boards) you can do without
any additional hardware - just connect them to the MOSI, MISO, RESET any additional hardware - just connect them to the MOSI, MISO, RESET
and SCK pins on the AVR and use the linuxgpio programmer type. It bitbangs and SCK pins on the AVR and use the linuxgpio programmer type. It bitbangs
the lines using the Linux sysfs GPIO interface. Of course, care should the lines using the Linux sysfs GPIO interface. Of course, care should
be taken about voltage level compatibility. Also, although not strictrly be taken about voltage level compatibility. Also, although not strictly
required, it is strongly advisable to protect the GPIO pins from required, it is strongly advisable to protect the GPIO pins from
overcurrent situations in some way. The simplest would be to just put overcurrent situations in some way. The simplest would be to just put
some resistors in series or better yet use a 3-state buffer driver like some resistors in series or better yet use a 3-state buffer driver like
@ -181,7 +181,7 @@ the 74HC244. Have a look at http://kolev.info/avrdude-linuxgpio for a more
detailed tutorial about using this programmer type. detailed tutorial about using this programmer type.
The STK500, JTAG ICE, avr910, and avr109/butterfly use the serial port to communicate with the PC. The STK500, JTAG ICE, avr910, and avr109/butterfly use the serial port to communicate with the PC.
The STK600, JTAG ICE mkII/3, AVRISP mkII, USBasp, avrftdi (and derivitives), and USBtinyISP The STK600, JTAG ICE mkII/3, AVRISP mkII, USBasp, avrftdi (and derivatives), and USBtinyISP
programmers communicate through the USB, using @code{libusb} as a programmers communicate through the USB, using @code{libusb} as a
platform abstraction layer. platform abstraction layer.
The avrftdi adds support for the FT2232C/D, FT2232H, and FT4232H devices. These all use The avrftdi adds support for the FT2232C/D, FT2232H, and FT4232H devices. These all use
@ -216,7 +216,7 @@ has a revision 1 hardware and firmware version of at least 5.37 (decimal).
The Atmel-ICE (ARM/AVR) is supported (JTAG, PDI for Xmega, debugWIRE, ISP modes). The Atmel-ICE (ARM/AVR) is supported (JTAG, PDI for Xmega, debugWIRE, ISP modes).
Atmel's XplainedPro boards, using EDBG protocol (CMSIS-DAP compliant), are Atmel's XplainedPro boards, using EDBG protocol (CMSIS-DAP compliant), are
supported by teh ``jtag3'' programmer type. supported by the ``jtag3'' programmer type.
The AVR Dragon is supported in all modes (ISP, JTAG, PDI, HVSP, PP, debugWire). The AVR Dragon is supported in all modes (ISP, JTAG, PDI, HVSP, PP, debugWire).
When used in JTAG and debugWire mode, the AVR Dragon behaves similar to a When used in JTAG and debugWire mode, the AVR Dragon behaves similar to a
@ -543,7 +543,7 @@ be specified as @var{avrdoper}. Libusb support is required on Unix
but not on Windows. For more information about AVR-Doper see but not on Windows. For more information about AVR-Doper see
@url{http://www.obdev.at/avrusb/avrdoper.html}. @url{http://www.obdev.at/avrusb/avrdoper.html}.
For the USBtinyISP, which is a simplicistic device not implementing For the USBtinyISP, which is a simplistic device not implementing
serial numbers, multiple devices can be distinguished by their serial numbers, multiple devices can be distinguished by their
location in the USB hierarchy. location in the USB hierarchy.
@xref{Troubleshooting}, for examples. @xref{Troubleshooting}, for examples.
@ -1329,7 +1329,7 @@ programmer work with AVRDUDE.
AVRDUDE first looks for a system wide configuration file in a platform AVRDUDE first looks for a system wide configuration file in a platform
dependent location. On Unix, this is usually 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 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 changed using the @option{-C} command line option. After the system wide
configuration file is parsed, AVRDUDE looks for a per-user configuration configuration file is parsed, AVRDUDE looks for a per-user configuration
@ -1657,7 +1657,7 @@ flash pages of the application section.
Reading fuse and lock bits is fully supported. Reading fuse and lock bits is fully supported.
Note that due to the unability to write the fuse bits, the safemode Note that due to the inability to write the fuse bits, the safemode
functionality does not make sense for these boot loaders. functionality does not make sense for these boot loaders.
@end itemize @end itemize
@ -1842,7 +1842,7 @@ The default location of the install is into @code{/usr/local} so you
will need to be sure that @code{/usr/local/bin} is in your @code{PATH} will need to be sure that @code{/usr/local/bin} is in your @code{PATH}
environment variable. environment variable.
If you do not have root access to your system, you can do the the If you do not have root access to your system, you can do the
following instead: following instead:
@example @example
@ -1892,7 +1892,7 @@ obtained.
@subsubsection Linux Installation @subsubsection Linux Installation
@noindent @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: can build and install the rpm binaries directly from the tarball:
@example @example
@ -2386,7 +2386,7 @@ be added to the @var{-P usb} option, similar to adding a serial number
on other USB-based programmers. on other USB-based programmers.
The actual naming convention for the bus and device names is The actual naming convention for the bus and device names is
operating-system dependant; AVRDUDE will print out what it found operating-system dependent; AVRDUDE will print out what it found
on the bus when running it with (at least) one @var{-v} option. on the bus when running it with (at least) one @var{-v} option.
By specifying a string that cannot match any existing device By specifying a string that cannot match any existing device
(for example, @var{-P usb:xxx}), the scan will list all possible (for example, @var{-P usb:xxx}), the scan will list all possible