Document the JTAG ICE mkI support.

git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@559 81a1dc3b-b13d-400b-aceb-764788c761c2

ChangeLog

@@ -1,3 +1,8 @@
+2005-11-29  Joerg Wunsch <j@uriah.heep.sax.de>
+
+	* avrdude.1: update for JTAG ICE mkI support.
+	* doc/avrdude.texi: (Ditto.)
+
 2005-11-29  Joerg Wunsch <j@uriah.heep.sax.de>
 
 	Submitted by Galen Seitz:

NEWS

@@ -13,6 +13,11 @@ Current:
 
   * JTAG mkII support now works with libusb-win32, too
 
+  * JTAG ICE mkI support has been added
+
+  * Solaris support has been added (including ecpp(7D) parallel-port
+    bit-bang mode)
+
 
 Version 5.0:
 

avrdude.1

@@ -19,7 +19,7 @@
 .\"
 .\" $Id$
 .\"
-.Dd DATE September 18, 2005
+.Dd DATE November 29, 2005
 .Os
 .Dt AVRDUDE 1
 .Sh NAME
@@ -55,7 +55,7 @@ is a program for downloading code and data to Atmel AVR
 microcontrollers.
 .Nm Avrdude
 supports Atmel's STK500 programmer,
-Atmel's JTAG ICE mkII,
+Atmel's JTAG ICE (both mkI and mkII),
 programmers complying to AppNote AVR910 and AVR109 (including the Butterfly),
 as well as a simple hard-wired
 programmer connected directly to a
@@ -104,7 +104,7 @@ AVR910, and the bootloader described in Atmel's application note
 AVR109 (which is also used by the AVR Butterfly evaluation board), are
 supported on a serial port.
 .Pp
-Atmel's JTAG ICE mkII is supported as well to up- or download memory
+Atmel's JTAG ICE (both mkI and mkII) is supported as well to up- or download memory
 areas from/to an AVR target (no support for on-chip debugging).
 .Pp
 Input files can be provided, and output files can be written in
@@ -643,14 +643,19 @@ This man page by
 Please report bugs via
 .Dl "http://savannah.nongnu.org/bugs/?group=avrdude" .
 .Pp
-The JTAGICE mkII programmer currently cannot write to the flash ROM
+The JTAG ICE programmers currently cannot write to the flash ROM
 one byte at a time.
 For that reason, updating the flash ROM from terminal mode does not
 work.
 .Pp
+Page-mode programming the EEPROM through JTAG (i.e. through an
+.Fl U
+option) requires a prior chip erase.
+This is an inherent feature of the way JTAG EEPROM programming works.
+.Pp
 The device IDs used by AVR910 and AVR109 do not match, so the
 avr109 (aka. butterfly) programmer might report
 .Dl "selected device is not supported by programmer" .
 Use the -F option to force
 .Nm
-to contiue anway.
+to contiue anyway.

doc/avrdude.texi

@@ -136,7 +136,7 @@ exploring memory contents, modifing individual bytes of eeprom,
 programming fuse/lock bits, etc.
 
 AVRDUDE supports six basic programmer types: Atmel's STK500,
-Atmel's JTAG ICE mkII, appnote
+Atmel's JTAG ICE (both mkI and mkII), appnote
 avr910, appnote avr109 (including the AVR Butterfly),
 serial bit-bang adapters,
 and the PPI (parallel port interface). PPI represents a class
@@ -172,7 +172,7 @@ 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
 protocol is more sophisticated.
-(This protocol can also be run on top of USB.)
+(The JTAG ICE mkII protocol can also be run on top of USB.)
 Only the memory programming functionality of the JTAG ICE is supported
 by AVRDUDE.
 
@@ -444,6 +444,13 @@ Atmel Butterfly Development Board
 @itemx dt006
 Dontronics DT006
 
+@item jtagmkI
+@itemx jtag1
+Atmel JTAG ICE mkI, running at 115200 Bd
+
+@itemx jtag1slow
+Atmel JTAG ICE mkI, running at 19200 Bd
+
 @item jtagmkII
 @itemx jtag2slow
 Atmel JTAG ICE mkII (default speed 19200 Bd)
@@ -1842,11 +1849,21 @@ Use the -F option to force AVRDUDE to continue anyway.
 
 @item
 Problem: Updating the flash ROM from terminal mode does not work with the
-JTAG ICE mkII.
+JTAG ICEs.
 
-Solution: None at this time.  Currently, the JTAG ICE mkII code cannot
+Solution: None at this time.  Currently, the JTAG ICE code cannot
 write to the flash ROM one byte at a time.
 
+@item
+Problem: Page-mode programming the EEPROM (using the -U option) does
+not erase EEPROM cells before writing, and thus cannot overwrite any
+previous value != 0xff.
+
+Solution: None.  This is an inherent feature of the way JTAG EEPROM
+programming works, and is documented that way in the Atmel AVR
+datasheets.
+In order to successfully program the EEPROM that way, a prior chip
+erase (with the EESAVE fuse unprogrammed) is required.
 
 
 @end itemize