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

* doc/avrdude.texi: Minor corrections. Change description of -P 

to reference platform dependencies.


git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@370 81a1dc3b-b13d-400b-aceb-764788c761c2
This commit is contained in:
arcanum 2003-09-18 18:11:25 +00:00
parent 50e6ec49ae
commit d890ae5341
2 changed files with 13 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
2003-09-18 Eric B. Weddington <eric@ecentral.com>
* doc/avrdude.texi: Minor corrections. Change description of -P
to reference platform dependencies.
2003-09-16 Eric B. Weddington <eric@ecentral.com> 2003-09-16 Eric B. Weddington <eric@ecentral.com>
* stk500.c: If writing flash, skip empty pages in paged write. * stk500.c: If writing flash, skip empty pages in paged write.

15
doc/avrdude.texi
View File

@ -140,7 +140,7 @@ tell AVRDUDE which pins to use for each programming function.
The STK500 and avr910 use the serial port to communicate with the PC The STK500 and avr910 use the serial port to communicate with the PC
and contains on-board logic to control the programming of the target and contains on-board logic to control the programming of the target
device. The fundamental difference between the two types lies in the device. The fundamental difference between the two types lies in the
protocol used to control the programmer. The av910 protocol is very 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 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, programer since the firmware is available online. On the other hand,
the STK500 protocol is more robust and complicated and the firmware is the STK500 protocol is more robust and complicated and the firmware is
@ -455,11 +455,12 @@ respective memory area to be read from the MCU. Can be specified as `-'
to write to stdout. to write to stdout.
@item -P @var{port} @item -P @var{port}
Use port to identify the device to which the programmer is attached. By Use port to identify the device to which the programmer is attached.
default the @code{/dev/ppi0} port is used, but if the programmer type Normally, the default parallel port is used, but if the programmer type
normally connects to the serial port, the @code{/dev/cuaa0} port is the normally connects to the serial port, the default serial port will be
default. If you need to use a different parallel or serial port, use used. See Appendix A, Platform Dependent Information, to find out the
this option to specify the alternate port name. 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 @item -q
Disable (or quell) output of the progress bar while reading or writing Disable (or quell) output of the progress bar while reading or writing
@ -1035,7 +1036,7 @@ write = "1 1 0 0 0 0 0 0 x x x x x x x x",
@itemize @bullet @itemize @bullet
@item @item
The @code{devicecode} parameter is the device code used by the STK500 The @code{devicecode} parameter is the device code used by the STK500
and are obtained from the software section (@code{avr061.zip} of and is obtained from the software section (@code{avr061.zip}) of
Atmel's AVR061 application note available from Atmel's AVR061 application note available from
@url{http://www.atmel.com/atmel/acrobat/doc2525.pdf}. @url{http://www.atmel.com/atmel/acrobat/doc2525.pdf}.