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

Documentation updates for EDBG. 

git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@1285 81a1dc3b-b13d-400b-aceb-764788c761c2
This commit is contained in:
Joerg Wunsch 2014-02-27 13:32:58 +00:00
parent 98febe591a
commit f7bb8a1c2a
3 changed files with 22 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
2014-02-27 Joerg Wunsch <j.gnu@uriah.heep.sax.de>
* avrdude.1: Documentation update for EDBG.
* doc/avrdude.texi: (Dito.)
2014-02-27 Joerg Wunsch <j.gnu@uriah.heep.sax.de> 2014-02-27 Joerg Wunsch <j.gnu@uriah.heep.sax.de>
* jtag3.c: For EDBG protocol, always use 512-byte block I/O. The * jtag3.c: For EDBG protocol, always use 512-byte block I/O. The

3
avrdude.1
View File

@ -150,6 +150,9 @@ For ATxmega devices, the JTAG ICE mkII is supported in PDI mode, provided it
has a revision 1 hardware and firmware version of at least 5.37 (decimal). has a revision 1 hardware and firmware version of at least 5.37 (decimal).
For ATxmega devices, the JTAGICE3 is supported in PDI mode. For ATxmega devices, the JTAGICE3 is supported in PDI mode.
.Pp .Pp
Atmel's XplainedPro boards, using the EDBG protocol (CMSIS-DAP compatible),
are supported using the "jtag3" programmer type.
.Pp
The AVR Dragon is supported in all modes (ISP, JTAG, HVSP, PP, debugWire). The AVR Dragon is supported in all modes (ISP, JTAG, 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
JTAG ICE mkII, so all device-specific comments for that device JTAG ICE mkII, so all device-specific comments for that device

22
doc/avrdude.texi
View File

@ -148,7 +148,7 @@ programming fuse/lock bits, etc.
AVRDUDE supports the following basic programmer types: Atmel's STK500, AVRDUDE supports the following basic programmer types: Atmel's STK500,
Atmel's AVRISP and AVRISP mkII devices, Atmel's AVRISP and AVRISP mkII devices,
Atmel's STK600, Atmel's STK600,
Atmel's JTAG ICE (both mkI and mkII, the latter also in ISP mode), appnote Atmel's JTAG ICE (the original one, mkII, and 3, the latter two also in ISP mode), appnote
avr910, appnote avr109 (including the AVR Butterfly), avr910, appnote avr109 (including the AVR Butterfly),
serial bit-bang adapters, serial bit-bang adapters,
and the PPI (parallel port interface). PPI represents a class and the PPI (parallel port interface). PPI represents a class
@ -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, AVRISP mkII, USBasp, avrftdi (and derivitives), and USBtinyISP The STK600, JTAG ICE mkII/3, AVRISP mkII, USBasp, avrftdi (and derivitives), 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
@ -207,12 +207,15 @@ protocol is more sophisticated.
(The JTAG ICE mkII 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 Only the memory programming functionality of the JTAG ICE is supported
by AVRDUDE. by AVRDUDE.
For the JTAG ICE mkII, JTAG, debugWire and ISP mode are supported, provided For the JTAG ICE mkII/3, JTAG, debugWire and ISP mode are supported, provided
it has a firmware revision of at least 4.14 (decimal). it has a firmware revision of at least 4.14 (decimal).
See below for the limitations of debugWire. See below for the limitations of debugWire.
For ATxmega devices, the JTAG ICE mkII is supported in PDI mode, provided it For ATxmega devices, the JTAG ICE mkII/3 is supported in PDI mode, provided it
has a revision 1 hardware and firmware version of at least 5.37 (decimal). has a revision 1 hardware and firmware version of at least 5.37 (decimal).
Atmel's XplainedPro boards, using EDBG protocol (CMSIS-DAP compliant), are
supported by teh ``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
JTAG ICE mkII, so all device-specific comments for that device JTAG ICE mkII, so all device-specific comments for that device
@ -743,10 +746,10 @@ accepting extended parameters.
@table @code @table @code
@item JTAG ICE mkII @item JTAG ICE mkII/3
@itemx AVR Dragon @itemx AVR Dragon
When using the JTAG ICE mkII or AVR Dragon in JTAG mode, the When using the JTAG ICE mkII/3 or AVR Dragon in JTAG mode, the
following extended parameter is accepted: following extended parameter is accepted:
@table @code @table @code
@item @samp{jtagchain=UB,UA,BB,BA} @item @samp{jtagchain=UB,UA,BB,BA}
@ -1188,7 +1191,7 @@ Set the JTAG ICE bit clock period to @var{period} microseconds.
Note that unlike STK500 settings, this setting will be reverted to Note that unlike STK500 settings, this setting will be reverted to
its default value (approximately 1 microsecond) when the programming its default value (approximately 1 microsecond) when the programming
software signs off from the JTAG ICE. software signs off from the JTAG ICE.
This parameter can also be used on the JTAG ICE mkII to specify the This parameter can also be used on the JTAG ICE mkII/3 to specify the
ISP clock period when operating the ICE in ISP mode. ISP clock period when operating the ICE in ISP mode.
@item parms @item parms
@ -1392,7 +1395,7 @@ programmer
pgmled = <num> ; # pin number pgmled = <num> ; # pin number
vfyled = <num> ; # pin number vfyled = <num> ; # pin number
usbvid = <hexnum>; # USB VID (Vendor ID) usbvid = <hexnum>; # USB VID (Vendor ID)
usbpid = <hexnum>; # USB PID (Product ID) usbpid = <hexnum> [, <hexnum> ...]; # USB PID (Product ID)
usbdev = <interface>; # USB interface or other device info usbdev = <interface>; # USB interface or other device info
usbvendor = <vendorname>; # USB Vendor Name usbvendor = <vendorname>; # USB Vendor Name
usbproduct = <productname>; # USB Product Name usbproduct = <productname>; # USB Product Name
@ -1407,6 +1410,9 @@ programmer. These values can be changed by new setting them for the new programm
@noindent @noindent
To invert a bit in the pin definitions, use @code{= ~ <num>}. To invert a bit in the pin definitions, use @code{= ~ <num>}.
@noindent
Not all programmer types can handle a list of USB PIDs.
@noindent @noindent
Following programmer types are currently implemented: Following programmer types are currently implemented: