* configure.ac: Set version to 4.1.0.
* doc/avrdude.texi: Add note about avr910 programmer type. git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@314 81a1dc3b-b13d-400b-aceb-764788c761c2
This commit is contained in:
parent
85bc7af0cb
commit
87aa0c0daa
|
@ -1,3 +1,8 @@
|
||||||
|
2003-04-17 Theodore A. Roth <troth@openavr.org>
|
||||||
|
|
||||||
|
* configure.ac: Set version to 4.1.0.
|
||||||
|
* doc/avrdude.texi: Add note about avr910 programmer type.
|
||||||
|
|
||||||
2003-04-17 Eric B. Weddington <eric@umginc.net>
|
2003-04-17 Eric B. Weddington <eric@umginc.net>
|
||||||
|
|
||||||
* NEWS: Replace TBD with new release version.
|
* NEWS: Replace TBD with new release version.
|
||||||
|
|
|
@ -24,7 +24,7 @@
|
||||||
# Process this file with autoconf to produce a configure script.
|
# Process this file with autoconf to produce a configure script.
|
||||||
|
|
||||||
AC_PREREQ(2.57)
|
AC_PREREQ(2.57)
|
||||||
AC_INIT(avrdude, 4.0.0cvs, avrdude-dev@nongnu.org)
|
AC_INIT(avrdude, 4.1.0, avrdude-dev@nongnu.org)
|
||||||
|
|
||||||
AC_CANONICAL_BUILD
|
AC_CANONICAL_BUILD
|
||||||
AC_CANONICAL_HOST
|
AC_CANONICAL_HOST
|
||||||
|
|
|
@ -127,17 +127,24 @@ from the contents of a file, while interactive mode is useful for
|
||||||
exploring memory contents, modifing individual bytes of eeprom,
|
exploring memory contents, modifing individual bytes of eeprom,
|
||||||
programming fuse/lock bits, etc.
|
programming fuse/lock bits, etc.
|
||||||
|
|
||||||
AVRDUDE supports two basic programmer types: Atmel's STK500 and the PPI
|
AVRDUDE supports three basic programmer types: Atmel's STK500, appnote
|
||||||
(parallel port interface). PPI represents a class of simple programmers
|
avr910 and the PPI (parallel port interface). PPI represents a class
|
||||||
where the programming lines are directly connected to the PC parallel
|
of simple programmers where the programming lines are directly
|
||||||
port, while the STK500 uses the serial port to communicate with the PC
|
connected to the PC parallel port. Several pin configurations exist
|
||||||
|
for several variations of the PPI programmers, and AVRDUDE can be be
|
||||||
|
configured to work with them by either specifying the appropriate
|
||||||
|
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
|
||||||
|
tell AVRDUDE which pins to use for each programming function.
|
||||||
|
|
||||||
|
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. Several pin configurations exist for several variations of the
|
device. The fundamental difference between the two types lies in the
|
||||||
PPI programmers, and AVRDUDE can be be configured to work with them by
|
protocol used to control the programmer. The av910 protocol is very
|
||||||
either specifying the appropriate programmer on the command line or by
|
simplistic and can easily be used as the basis for a simple, home made
|
||||||
creating a new entry in its configuration file. All that's usually
|
programer since the firmware is available online. On the other hand,
|
||||||
required for a new entry is to tell AVRDUDE which pins to use for each
|
the STK500 protocol is more robust and complicated and the firmware is
|
||||||
programming function.
|
not openly available.
|
||||||
|
|
||||||
@menu
|
@menu
|
||||||
* History::
|
* History::
|
||||||
|
|
Loading…
Reference in New Issue