2001-01-20 04:14:01 +00:00
|
|
|
.\"
|
2003-02-08 04:17:25 +00:00
|
|
|
.\" avrdude - A Downloader/Uploader for AVR device programmers
|
2011-08-17 15:24:09 +00:00
|
|
|
.\" Copyright (C) 2001, 2002, 2003, 2005 - 2011 Joerg Wunsch
|
2001-01-20 04:14:01 +00:00
|
|
|
.\"
|
2003-02-06 22:11:20 +00:00
|
|
|
.\" This program is free software; you can redistribute it and/or modify
|
|
|
|
|
.\" it under the terms of the GNU General Public License as published by
|
|
|
|
|
.\" the Free Software Foundation; either version 2 of the License, or
|
|
|
|
|
.\" (at your option) any later version.
|
|
|
|
|
.\"
|
|
|
|
|
.\" This program is distributed in the hope that it will be useful,
|
|
|
|
|
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
.\" GNU General Public License for more details.
|
|
|
|
|
.\"
|
|
|
|
|
.\" You should have received a copy of the GNU General Public License
|
|
|
|
|
.\" along with this program; if not, write to the Free Software
|
|
|
|
|
.\" Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
2001-01-20 04:14:01 +00:00
|
|
|
.\"
|
|
|
|
|
.\"
|
|
|
|
|
.\" $Id$
|
|
|
|
|
.\"
|
2011-08-17 15:24:09 +00:00
|
|
|
.Dd DATE August 17, 2011
|
2001-01-20 04:14:01 +00:00
|
|
|
.Os
|
2003-02-06 05:13:32 +00:00
|
|
|
.Dt AVRDUDE 1
|
2001-01-20 04:14:01 +00:00
|
|
|
.Sh NAME
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm avrdude
|
2001-01-20 04:14:01 +00:00
|
|
|
.Nd driver program for ``simple'' Atmel AVR MCU programmer
|
|
|
|
|
.Sh SYNOPSIS
|
|
|
|
|
.Nm
|
|
|
|
|
.Fl p Ar partno
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
.Op Fl b Ar baudrate
|
|
|
|
|
.Op Fl B Ar bitclock
|
2001-10-15 00:00:09 +00:00
|
|
|
.Op Fl c Ar programmer-id
|
|
|
|
|
.Op Fl C Ar config-file
|
2003-08-29 23:17:32 +00:00
|
|
|
.Op Fl D
|
2001-01-20 04:14:01 +00:00
|
|
|
.Op Fl e
|
|
|
|
|
.Oo Fl E Ar exitspec Ns
|
|
|
|
|
.Op \&, Ns Ar exitspec
|
|
|
|
|
.Oc
|
|
|
|
|
.Op Fl F
|
2006-08-17 15:06:20 +00:00
|
|
|
.Op Fl i Ar delay
|
2001-10-15 00:00:09 +00:00
|
|
|
.Op Fl n
|
2006-10-09 14:34:24 +00:00
|
|
|
.Op Fl O
|
2002-12-07 15:16:24 +00:00
|
|
|
.Op Fl P Ar port
|
2003-08-01 20:11:21 +00:00
|
|
|
.Op Fl q
|
2005-09-21 02:00:58 +00:00
|
|
|
.Op Fl s
|
2001-01-20 04:14:01 +00:00
|
|
|
.Op Fl t
|
2005-02-10 18:03:32 +00:00
|
|
|
.Op Fl u
|
2003-08-29 23:17:32 +00:00
|
|
|
.Op Fl U Ar memtype:op:filename:filefmt
|
2001-10-15 00:00:09 +00:00
|
|
|
.Op Fl v
|
2007-11-06 19:42:16 +00:00
|
|
|
.Op Fl x Ar extended_param
|
2002-10-29 01:59:02 +00:00
|
|
|
.Op Fl V
|
|
|
|
|
.Op Fl y
|
|
|
|
|
.Op Fl Y
|
2001-01-20 04:14:01 +00:00
|
|
|
.Sh DESCRIPTION
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm Avrdude
|
2002-12-03 03:54:32 +00:00
|
|
|
is a program for downloading code and data to Atmel AVR
|
|
|
|
|
microcontrollers.
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm Avrdude
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
supports Atmel's STK500 programmer,
|
2006-01-12 23:13:50 +00:00
|
|
|
Atmel's AVRISP and AVRISP mkII devices,
|
2008-03-14 13:00:08 +00:00
|
|
|
Atmel's STK600,
|
2006-09-06 20:06:07 +00:00
|
|
|
Atmel's JTAG ICE (both mkI and mkII, the latter also in ISP mode),
|
2005-07-28 16:06:35 +00:00
|
|
|
programmers complying to AppNote AVR910 and AVR109 (including the Butterfly),
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
as well as a simple hard-wired
|
2002-12-03 03:54:32 +00:00
|
|
|
programmer connected directly to a
|
2001-01-20 04:14:01 +00:00
|
|
|
.Xr ppi 4
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
or
|
|
|
|
|
.Xr parport 4
|
2005-09-18 20:12:23 +00:00
|
|
|
parallel port, or to a standard serial port.
|
|
|
|
|
In the simplest case, the hardware consists just of a
|
2002-12-03 03:54:32 +00:00
|
|
|
cable connecting the respective AVR signal lines to the parallel port.
|
2001-01-20 04:14:01 +00:00
|
|
|
.Pp
|
|
|
|
|
The MCU is programmed in
|
|
|
|
|
.Em serial programming mode ,
|
2002-12-03 03:54:32 +00:00
|
|
|
so, for the
|
|
|
|
|
.Xr ppi 4
|
|
|
|
|
based programmer, the MCU signals
|
2001-01-20 04:14:01 +00:00
|
|
|
.Ql /RESET ,
|
|
|
|
|
.Ql SCK ,
|
|
|
|
|
.Ql MISO
|
|
|
|
|
and
|
|
|
|
|
.Ql MOSI
|
|
|
|
|
need to be connected to the parallel port. Optionally, some otherwise
|
2002-12-03 03:54:32 +00:00
|
|
|
unused output pins of the parallel port can be used to supply power
|
|
|
|
|
for the MCU part, so it is also possible to construct a passive
|
2006-03-24 02:49:09 +00:00
|
|
|
stand-alone programming device. Some status LEDs indicating the
|
2002-12-03 03:54:32 +00:00
|
|
|
current operating state of the programmer can be connected, and a
|
|
|
|
|
signal is available to control a buffer/driver IC 74LS367 (or
|
|
|
|
|
74HCT367). The latter can be useful to decouple the parallel port
|
|
|
|
|
from the MCU when in-system programming is used.
|
2001-04-25 22:35:14 +00:00
|
|
|
.Pp
|
2005-09-18 20:12:23 +00:00
|
|
|
A number of equally simple bit-bang programming adapters that connect
|
|
|
|
|
to a serial port are supported as well, among them the popular
|
|
|
|
|
Ponyprog serial adapter, and the DASA and DASA3 adapters that used to
|
|
|
|
|
be supported by uisp(1).
|
|
|
|
|
Note that these adapters are meant to be attached to a physical serial
|
|
|
|
|
port.
|
|
|
|
|
Connecting to a serial port emulated on top of USB is likely to not
|
|
|
|
|
work at all, or to work abysmally slow.
|
|
|
|
|
.Pp
|
2002-12-03 03:54:32 +00:00
|
|
|
Atmel's STK500 programmer is also supported and connects to a serial
|
|
|
|
|
port.
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
Both, firmware versions 1.x and 2.x can be handled, but require a
|
|
|
|
|
different programmer type specification (by now).
|
2006-07-21 21:53:49 +00:00
|
|
|
Using firmware version 2, high-voltage programming is also supported,
|
|
|
|
|
both parallel and serial
|
|
|
|
|
(programmer types stk500pp and stk500hvsp).
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
.Pp
|
2009-02-25 09:39:04 +00:00
|
|
|
The Arduino (which is very similar to the STK500 1.x) is supported via
|
|
|
|
|
its own programmer type specification ``arduino''.
|
|
|
|
|
.Pp
|
2009-11-04 03:32:55 +00:00
|
|
|
The BusPirate is a versatile tool that can also be used as an AVR programmer.
|
2009-11-09 02:18:40 +00:00
|
|
|
A single BusPirate can be connected to up to 3 independent AVRs. See
|
|
|
|
|
the section on
|
|
|
|
|
.Em extended parameters
|
|
|
|
|
below for details.
|
2009-11-04 03:32:55 +00:00
|
|
|
.Pp
|
2008-03-14 13:00:08 +00:00
|
|
|
Atmel's STK600 programmer is supported in ISP and high-voltage
|
|
|
|
|
programming modes, and connects through the USB.
|
2008-07-26 22:53:40 +00:00
|
|
|
For ATxmega devices, the STK600 is supported in PDI mode.
|
2010-01-15 16:36:13 +00:00
|
|
|
For ATtiny4/5/9/10 devices, the STK600 and AVRISP mkII are supported in TPI mode.
|
2008-03-14 13:00:08 +00:00
|
|
|
.Pp
|
2005-07-28 16:06:35 +00:00
|
|
|
The simple serial programmer described in Atmel's application note
|
|
|
|
|
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
|
2005-11-29 22:58:04 +00:00
|
|
|
Atmel's JTAG ICE (both mkI and mkII) is supported as well to up- or download memory
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
areas from/to an AVR target (no support for on-chip debugging).
|
2010-01-14 13:46:02 +00:00
|
|
|
For the JTAG ICE mkII, JTAG, debugWire and ISP mode are supported, provided
|
|
|
|
|
it has a firmware revision of at least 4.14 (decimal).
|
2006-11-20 23:23:37 +00:00
|
|
|
See below for the limitations of debugWire.
|
2010-01-14 13:46:02 +00:00
|
|
|
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).
|
2001-01-20 04:14:01 +00:00
|
|
|
.Pp
|
2006-11-20 23:23:37 +00:00
|
|
|
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
|
2006-10-26 21:14:10 +00:00
|
|
|
JTAG ICE mkII, so all device-specific comments for that device
|
|
|
|
|
will apply as well.
|
|
|
|
|
When used in ISP mode, the AVR Dragon behaves similar to an
|
|
|
|
|
AVRISP mkII (or JTAG ICE mkII in ISP mode), so all device-specific
|
|
|
|
|
comments will apply there.
|
|
|
|
|
In particular, the Dragon starts out with a rather fast ISP clock
|
|
|
|
|
frequency, so the
|
|
|
|
|
.Fl B Ar bitclock
|
|
|
|
|
option might be required to achieve a stable ISP communication.
|
2010-01-14 13:46:02 +00:00
|
|
|
For ATxmega devices, the AVR Dragon is supported in PDI mode, provided it
|
|
|
|
|
has a firmware version of at least 6.11 (decimal).
|
2006-10-26 21:14:10 +00:00
|
|
|
.Pp
|
2007-10-29 18:03:02 +00:00
|
|
|
The USBasp ISP and USBtinyISP adapters are also supported, provided
|
2006-09-10 20:41:00 +00:00
|
|
|
.Nm avrdude
|
|
|
|
|
has been compiled with libusb support.
|
2010-01-14 15:11:47 +00:00
|
|
|
They both feature simple firmware-only USB implementations, running on
|
2007-10-29 18:03:02 +00:00
|
|
|
an ATmega8 (or ATmega88), or ATtiny2313, respectively.
|
2006-09-10 20:41:00 +00:00
|
|
|
.Pp
|
2001-01-20 04:14:01 +00:00
|
|
|
Input files can be provided, and output files can be written in
|
|
|
|
|
different file formats, such as raw binary files containing the data
|
|
|
|
|
to download to the chip, Intel hex format, or Motorola S-record
|
|
|
|
|
format. There are a number of tools available to produce those files,
|
|
|
|
|
like
|
|
|
|
|
.Xr asl 1
|
|
|
|
|
as a standalone assembler, or
|
|
|
|
|
.Xr avr-objcopy 1
|
|
|
|
|
for the final stage of the GNU toolchain for the AVR microcontroller.
|
|
|
|
|
.Pp
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm Avrdude
|
2001-12-30 00:04:52 +00:00
|
|
|
can program the EEPROM and flash ROM memory cells of supported AVR
|
|
|
|
|
parts. Where supported by the serial instruction set, fuse bits and
|
|
|
|
|
lock bits can be programmed as well. These are implemented within
|
|
|
|
|
.Nm
|
2006-03-24 02:49:09 +00:00
|
|
|
as separate memory types and can be programmed using data from a file
|
2001-12-30 00:04:52 +00:00
|
|
|
(see the
|
|
|
|
|
.Fl m
|
|
|
|
|
option) or from terminal mode (see the
|
|
|
|
|
.Ar dump
|
|
|
|
|
and
|
|
|
|
|
.Ar write
|
|
|
|
|
commands). It is also possible to read the chip (provided it has not
|
|
|
|
|
been code-protected previously, of course) and store the data in a
|
|
|
|
|
file. Finally, a ``terminal'' mode is available that allows one to
|
2001-10-15 00:00:09 +00:00
|
|
|
interactively communicate with the MCU, and to display or program
|
|
|
|
|
individual memory cells.
|
2008-03-14 13:00:08 +00:00
|
|
|
On the STK500 and STK600 programmer, several operational parameters (target supply
|
2003-07-24 21:26:28 +00:00
|
|
|
voltage, target Aref voltage, master clock) can be examined and changed
|
|
|
|
|
from within terminal mode as well.
|
2001-01-20 04:14:01 +00:00
|
|
|
.Ss Options
|
|
|
|
|
In order to control all the different operation modi, a number of options
|
|
|
|
|
need to be specified to
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm avrdude .
|
2001-01-20 04:14:01 +00:00
|
|
|
.Bl -tag -offset indent -width indent
|
|
|
|
|
.It Fl p Ar partno
|
|
|
|
|
This is the only option that is mandatory for every invocation of
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm avrdude .
|
2001-10-15 00:00:09 +00:00
|
|
|
It specifies the type of the MCU connected to the programmer. These are read from the config file. If
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm avrdude
|
2001-10-15 00:00:09 +00:00
|
|
|
does not know about a part that you have, simply add it to the config
|
|
|
|
|
file (be sure and submit a patch back to the author so that it can be
|
|
|
|
|
incorporated for the next version). See the sample config file for
|
|
|
|
|
the format. Currently, the following MCU types are understood:
|
2001-01-20 04:14:01 +00:00
|
|
|
.Pp
|
|
|
|
|
.TS
|
|
|
|
|
ll.
|
|
|
|
|
\fBOption tag\fP \fBOfficial part name\fP
|
|
|
|
|
1200 AT90S1200
|
|
|
|
|
2313 AT90S2313
|
|
|
|
|
2333 AT90S2333
|
2003-02-19 09:01:54 +00:00
|
|
|
2343 AT90S2343 (*)
|
2002-10-29 01:59:02 +00:00
|
|
|
4414 AT90S4414
|
2001-01-20 04:14:01 +00:00
|
|
|
4433 AT90S4433
|
|
|
|
|
4434 AT90S4434
|
|
|
|
|
8515 AT90S8515
|
|
|
|
|
8535 AT90S8535
|
2010-01-14 13:46:02 +00:00
|
|
|
c128 AT90CAN128
|
|
|
|
|
c32 AT90CAN32
|
|
|
|
|
c64 AT90CAN64
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
m103 ATmega103
|
|
|
|
|
m128 ATmega128
|
2006-05-25 14:38:08 +00:00
|
|
|
m1280 ATmega1280
|
|
|
|
|
m1281 ATmega1281
|
2009-02-25 09:39:04 +00:00
|
|
|
m1284p ATmega1284P
|
2009-02-05 16:20:29 +00:00
|
|
|
m128rfa1 ATmega128RFA1
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
m16 ATmega16
|
|
|
|
|
m161 ATmega161
|
|
|
|
|
m162 ATmega162
|
|
|
|
|
m163 ATmega163
|
2005-08-28 19:37:59 +00:00
|
|
|
m164 ATmega164
|
2010-01-14 13:46:02 +00:00
|
|
|
m164p ATmega164P
|
|
|
|
|
m168 ATmega168
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
m169 ATmega169
|
2006-05-25 14:38:08 +00:00
|
|
|
m2560 ATmega2560 (**)
|
|
|
|
|
m2561 ATmega2561 (**)
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
m32 ATmega32
|
2010-01-14 13:46:02 +00:00
|
|
|
m324p ATmega324P
|
|
|
|
|
m325 ATmega325
|
|
|
|
|
m3250 ATmega3250
|
|
|
|
|
m328p ATmega328P
|
2005-08-28 19:37:59 +00:00
|
|
|
m329 ATmega329
|
|
|
|
|
m3290 ATmega3290
|
2010-01-14 13:46:02 +00:00
|
|
|
m329p ATmega329P
|
|
|
|
|
m3290p ATmega3290P
|
2010-01-14 15:26:09 +00:00
|
|
|
m32u4 ATmega32U4
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
m48 ATmega48
|
|
|
|
|
m64 ATmega64
|
2006-05-25 14:38:08 +00:00
|
|
|
m640 ATmega640
|
2010-01-14 13:46:02 +00:00
|
|
|
m644p ATmega644P
|
2005-08-28 19:37:59 +00:00
|
|
|
m644 ATmega644
|
2010-01-14 13:46:02 +00:00
|
|
|
m645 ATmega645
|
|
|
|
|
m6450 ATmega6450
|
2005-08-28 19:37:59 +00:00
|
|
|
m649 ATmega649
|
|
|
|
|
m6490 ATmega6490
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
m8 ATmega8
|
|
|
|
|
m8515 ATmega8515
|
|
|
|
|
m8535 ATmega8535
|
|
|
|
|
m88 ATmega88
|
2010-01-14 13:46:02 +00:00
|
|
|
pwm2 AT90PWM2
|
|
|
|
|
pwm2b AT90PWM2B
|
|
|
|
|
pwm3 AT90PWM3
|
|
|
|
|
pwm3b AT90PWM3B
|
2010-01-15 16:36:13 +00:00
|
|
|
t10 ATtiny10
|
|
|
|
|
t12 ATtiny12 (***)
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
t13 ATtiny13
|
|
|
|
|
t15 ATtiny15
|
|
|
|
|
t2313 ATtiny2313
|
2005-08-28 19:37:59 +00:00
|
|
|
t25 ATtiny25
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
t26 ATtiny26
|
2010-01-14 13:46:02 +00:00
|
|
|
t261 ATtiny261
|
2010-01-15 16:36:13 +00:00
|
|
|
t4 ATtiny4
|
2010-01-14 13:46:02 +00:00
|
|
|
t44 ATtiny44
|
2005-08-28 19:37:59 +00:00
|
|
|
t45 ATtiny45
|
2010-01-14 13:46:02 +00:00
|
|
|
t461 ATtiny461
|
2010-01-15 16:36:13 +00:00
|
|
|
t5 ATtiny5
|
2010-01-14 13:46:02 +00:00
|
|
|
t84 ATtiny84
|
2005-08-28 19:37:59 +00:00
|
|
|
t85 ATtiny85
|
2010-01-14 13:46:02 +00:00
|
|
|
t861 ATtiny861
|
|
|
|
|
t88 ATtiny88
|
2010-01-15 16:36:13 +00:00
|
|
|
t9 ATtiny9
|
2009-11-29 20:19:15 +00:00
|
|
|
ucr2 AT32uca0512
|
2010-01-14 13:46:02 +00:00
|
|
|
usb1286 ATmega1286
|
|
|
|
|
usb1287 ATmega1287
|
|
|
|
|
usb162 ATmega162
|
|
|
|
|
usb646 ATmega647
|
|
|
|
|
usb647 ATmega647
|
|
|
|
|
usb82 ATmega82
|
2008-07-26 22:53:40 +00:00
|
|
|
x128a1 ATxmega128A1
|
|
|
|
|
x128a1d ATxmega128A1revD
|
2010-01-14 13:46:02 +00:00
|
|
|
x128a3 ATxmega128A3
|
|
|
|
|
x128a4 ATxmega128A4
|
|
|
|
|
x16a4 ATxmega16A4
|
|
|
|
|
x192a1 ATxmega192A1
|
|
|
|
|
x192a3 ATxmega192A3
|
|
|
|
|
x256a1 ATxmega256A1
|
|
|
|
|
x256a3 ATxmega256A3
|
|
|
|
|
x256a3b ATxmega256A3B
|
|
|
|
|
x32a4 ATxmega32A4
|
|
|
|
|
x64a1 ATxmega64A1
|
|
|
|
|
x64a3 ATxmega64A3
|
|
|
|
|
x64a4 ATxmega64A4
|
2001-01-20 04:14:01 +00:00
|
|
|
.TE
|
2006-05-25 14:38:08 +00:00
|
|
|
.Bl -tag -width "(**) "
|
2003-02-19 09:01:54 +00:00
|
|
|
.It "(*)"
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
The AT90S2323 and ATtiny22 use the same algorithm.
|
2006-05-25 14:38:08 +00:00
|
|
|
.It "(**)"
|
|
|
|
|
Flash addressing above 128 KB is not supported by all
|
|
|
|
|
programming hardware. Known to work are jtag2, stk500v2,
|
|
|
|
|
and bit-bang programmers.
|
2010-01-15 16:36:13 +00:00
|
|
|
.It "(***)"
|
|
|
|
|
The ATtiny11 uses the same algorithm, but can only be
|
|
|
|
|
programmed in high-voltage serial mode.
|
2003-02-19 09:01:54 +00:00
|
|
|
.El
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
.It Fl b Ar baudrate
|
|
|
|
|
Override the RS-232 connection baud rate specified in the respective
|
|
|
|
|
programmer's entry of the configuration file.
|
|
|
|
|
.It Fl B Ar bitclock
|
2006-09-06 20:06:07 +00:00
|
|
|
Specify the bit clock period for the JTAG interface or the ISP clock (JTAG ICE only).
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
The value is a floating-point number in microseconds.
|
|
|
|
|
The default value of the JTAG ICE results in about 1 microsecond bit
|
|
|
|
|
clock period, suitable for target MCUs running at 4 MHz clock and
|
|
|
|
|
above.
|
|
|
|
|
Unlike certain parameters in the STK500, the JTAG ICE resets all its
|
|
|
|
|
parameters to default values when the programming software signs
|
|
|
|
|
off from the ICE, so for MCUs running at lower clock speeds, this
|
|
|
|
|
parameter must be specified on the command-line.
|
2001-10-15 00:00:09 +00:00
|
|
|
.It Fl c Ar programmer-id
|
2001-09-19 17:04:25 +00:00
|
|
|
Use the pin configuration specified by the argument. Pin
|
|
|
|
|
configurations are read from the config file (see the
|
|
|
|
|
.Fl C
|
|
|
|
|
option). New pin configurations can be easily added or modified
|
|
|
|
|
through the use of a config file to make
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm avrdude
|
2001-09-19 17:04:25 +00:00
|
|
|
work with different programmers as long as the programmer supports the
|
2003-03-10 21:51:55 +00:00
|
|
|
Atmel AVR serial program method. You can use the 'default_programmer'
|
|
|
|
|
keyword in your
|
|
|
|
|
.Pa ${HOME}/.avrduderc
|
|
|
|
|
file to assign a default programmer to keep from having to specify
|
|
|
|
|
this option on every invocation.
|
2001-10-15 00:00:09 +00:00
|
|
|
.It Fl C Ar config-file
|
|
|
|
|
Use the specified config file to load configuration data. This file
|
|
|
|
|
contains all programmer and part definitions that
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm avrdude
|
2001-10-15 00:00:09 +00:00
|
|
|
knows about. If you have a programmer or part that
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm avrdude
|
2001-10-15 00:00:09 +00:00
|
|
|
does not know about, you can add it to the config file (be sure and
|
|
|
|
|
submit a patch back to the author so that it can be incorporated for
|
2003-03-10 21:51:55 +00:00
|
|
|
the next version). See the config file, located at
|
|
|
|
|
.Pa ${PREFIX}/etc/avrdude.conf ,
|
2001-10-15 00:00:09 +00:00
|
|
|
which contains a description of the format.
|
2003-08-29 23:17:32 +00:00
|
|
|
.It Fl D
|
|
|
|
|
Disable auto erase for flash. When the
|
|
|
|
|
.Fl U
|
|
|
|
|
option with flash memory is specified,
|
|
|
|
|
.Nm
|
|
|
|
|
will perform a chip erase before starting any of the programming
|
|
|
|
|
operations, since it generally is a mistake to program the flash
|
|
|
|
|
without performing an erase first. This option disables that.
|
2008-07-26 22:53:40 +00:00
|
|
|
Auto erase is not used for ATxmega devices as these devices can
|
|
|
|
|
use page erase before writing each page so no explicit chip erase
|
|
|
|
|
is required.
|
|
|
|
|
Note however that any page not affected by the current operation
|
|
|
|
|
will retain its previous contents.
|
2001-01-20 04:14:01 +00:00
|
|
|
.It Fl e
|
|
|
|
|
Causes a chip erase to be executed. This will reset the contents of the
|
|
|
|
|
flash ROM and EEPROM to the value
|
|
|
|
|
.Ql 0xff ,
|
2008-07-26 22:53:40 +00:00
|
|
|
and clear all lock bits.
|
|
|
|
|
Except for ATxmega devices which can use page erase,
|
|
|
|
|
it is basically a prerequisite command before the flash ROM can be
|
2001-01-20 04:14:01 +00:00
|
|
|
reprogrammed again. The only exception would be if the new
|
|
|
|
|
contents would exclusively cause bits to be programmed from the value
|
|
|
|
|
.Ql 1
|
|
|
|
|
to
|
|
|
|
|
.Ql 0 .
|
|
|
|
|
Note that in order to reprogram EERPOM cells, no explicit prior chip
|
|
|
|
|
erase is required since the MCU provides an auto-erase cycle in that
|
|
|
|
|
case before programming the cell.
|
|
|
|
|
.It Xo Fl E Ar exitspec Ns
|
|
|
|
|
.Op \&, Ns Ar exitspec
|
|
|
|
|
.Xc
|
|
|
|
|
By default,
|
|
|
|
|
.Nm
|
|
|
|
|
leaves the parallel port in the same state at exit as it has been
|
|
|
|
|
found at startup. This option modifies the state of the
|
|
|
|
|
.Ql /RESET
|
|
|
|
|
and
|
|
|
|
|
.Ql Vcc
|
|
|
|
|
lines the parallel port is left at, according to the
|
|
|
|
|
.Ar exitspec
|
|
|
|
|
arguments provided, as follows:
|
|
|
|
|
.Bl -tag -width noreset
|
|
|
|
|
.It Ar reset
|
|
|
|
|
The
|
|
|
|
|
.Ql /RESET
|
|
|
|
|
signal will be left activated at program exit, that is it will be held
|
|
|
|
|
.Em low ,
|
|
|
|
|
in order to keep the MCU in reset state afterwards. Note in particular
|
|
|
|
|
that the programming algorithm for the AT90S1200 device mandates that
|
|
|
|
|
the
|
|
|
|
|
.Ql /RESET
|
|
|
|
|
signal is active
|
|
|
|
|
.Em before
|
|
|
|
|
powering up the MCU, so in case an external power supply is used for this
|
|
|
|
|
MCU type, a previous invocation of
|
|
|
|
|
.Nm
|
|
|
|
|
with this option specified is one of the possible ways to guarantee this
|
|
|
|
|
condition.
|
|
|
|
|
.It Ar noreset
|
|
|
|
|
The
|
|
|
|
|
.Ql /RESET
|
|
|
|
|
line will be deactivated at program exit, thus allowing the MCU target
|
|
|
|
|
program to run while the programming hardware remains connected.
|
|
|
|
|
.It Ar vcc
|
|
|
|
|
This option will leave those parallel port pins active
|
|
|
|
|
.Pq \&i. \&e. Em high
|
|
|
|
|
that can be used to supply
|
|
|
|
|
.Ql Vcc
|
|
|
|
|
power to the MCU.
|
|
|
|
|
.It Ar novcc
|
|
|
|
|
This option will pull the
|
|
|
|
|
.Ql Vcc
|
|
|
|
|
pins of the parallel port down at program exit.
|
|
|
|
|
.El
|
|
|
|
|
.Pp
|
|
|
|
|
Multiple
|
|
|
|
|
.Ar exitspec
|
|
|
|
|
arguments can be separated with commas.
|
|
|
|
|
.It Fl F
|
|
|
|
|
Normally,
|
|
|
|
|
.Nm
|
|
|
|
|
tries to verify that the device signature read from the part is
|
|
|
|
|
reasonable before continuing. Since it can happen from time to time
|
|
|
|
|
that a device has a broken (erased or overwritten) device signature
|
|
|
|
|
but is otherwise operating normally, this options is provided to
|
|
|
|
|
override the check.
|
2008-07-29 21:26:55 +00:00
|
|
|
Also, for programmers like the Atmel STK500 and STK600 which can
|
|
|
|
|
adjust parameters local to the programming tool (independent of an
|
|
|
|
|
actual connection to a target controller), this option can be used
|
|
|
|
|
together with
|
|
|
|
|
.Fl t
|
|
|
|
|
to continue in terminal mode.
|
2006-08-17 15:06:20 +00:00
|
|
|
.It Fl i Ar delay
|
|
|
|
|
For bitbang-type programmers, delay for approximately
|
|
|
|
|
.Ar delay
|
|
|
|
|
microseconds between each bit state change.
|
|
|
|
|
If the host system is very fast, or the target runs off a slow clock
|
|
|
|
|
(like a 32 kHz crystal, or the 128 kHz internal RC oscillator), this
|
|
|
|
|
can become necessary to satisfy the requirement that the ISP clock
|
|
|
|
|
frequency must not be higher than 1/4 of the CPU clock frequency.
|
|
|
|
|
This is implemented as a spin-loop delay to allow even for very
|
|
|
|
|
short delays.
|
|
|
|
|
On Unix-style operating systems, the spin loop is initially calibrated
|
|
|
|
|
against a system timer, so the number of microseconds might be rather
|
|
|
|
|
realistic, assuming a constant system load while
|
|
|
|
|
.Nm
|
|
|
|
|
is running.
|
|
|
|
|
On Win32 operating systems, a preconfigured number of cycles per
|
|
|
|
|
microsecond is assumed that might be off a bit for very fast or very
|
|
|
|
|
slow machines.
|
2001-10-15 00:00:09 +00:00
|
|
|
.It Fl n
|
|
|
|
|
No-write - disables actually writing data to the MCU (useful for debugging
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm avrdude
|
2001-10-15 00:00:09 +00:00
|
|
|
).
|
2006-10-09 14:34:24 +00:00
|
|
|
.It Fl O
|
|
|
|
|
Perform a RC oscillator run-time calibration according to Atmel
|
|
|
|
|
application note AVR053.
|
|
|
|
|
This is only supported on the STK500v2, AVRISP mkII, and JTAG ICE mkII
|
|
|
|
|
hardware.
|
|
|
|
|
Note that the result will be stored in the EEPROM cell at address 0.
|
2002-12-03 03:54:32 +00:00
|
|
|
.It Fl P Ar port
|
2001-01-20 04:14:01 +00:00
|
|
|
Use
|
2002-12-03 03:54:32 +00:00
|
|
|
.Ar port
|
2002-12-07 15:16:24 +00:00
|
|
|
to identify the device to which the programmer is attached. By
|
|
|
|
|
default the
|
|
|
|
|
.Pa /dev/ppi0
|
|
|
|
|
port is used, but if the programmer type normally connects to the
|
|
|
|
|
serial port, the
|
|
|
|
|
.Pa /dev/cuaa0
|
|
|
|
|
port is the default. If you need to use a different parallel or
|
|
|
|
|
serial port, use this option to specify the alternate port name.
|
2005-06-19 21:38:03 +00:00
|
|
|
.Pp
|
2008-11-05 20:53:51 +00:00
|
|
|
On Win32 operating systems, the parallel ports are referred to as lpt1
|
|
|
|
|
through lpt3, referring to the addresses 0x378, 0x278, and 0x3BC,
|
|
|
|
|
respectively. If the parallel port can be accessed through a different
|
|
|
|
|
address, this address can be specified directly, using the common C
|
|
|
|
|
language notation (i. e., hexadecimal values are prefixed by
|
|
|
|
|
.Ql 0x
|
|
|
|
|
).
|
|
|
|
|
.Pp
|
2005-06-19 21:38:03 +00:00
|
|
|
For the JTAG ICE mkII, if
|
|
|
|
|
.Nm
|
|
|
|
|
has been configured with libusb support,
|
|
|
|
|
.Ar port
|
|
|
|
|
can alternatively be specified as
|
2006-08-31 20:52:47 +00:00
|
|
|
.Pa usb Ns Op \&: Ns Ar serialno .
|
2005-06-19 21:38:03 +00:00
|
|
|
This will cause
|
|
|
|
|
.Nm
|
|
|
|
|
to search a JTAG ICE mkII on USB.
|
|
|
|
|
If
|
|
|
|
|
.Ar serialno
|
|
|
|
|
is also specified, it will be matched against the serial number read
|
|
|
|
|
from any JTAG ICE mkII found on USB.
|
|
|
|
|
The match is done after stripping any existing colons from the given
|
|
|
|
|
serial number, and right-to-left, so only the least significant bytes
|
|
|
|
|
from the serial number need to be given.
|
2006-01-12 23:13:50 +00:00
|
|
|
.Pp
|
|
|
|
|
As the AVRISP mkII device can only be talked to over USB, the very
|
|
|
|
|
same method of specifying the port is required there.
|
2006-08-31 20:52:47 +00:00
|
|
|
.Pp
|
2006-12-20 23:43:34 +00:00
|
|
|
For the USB programmer "AVR-Doper" running in HID mode, the port must
|
|
|
|
|
be specified as
|
|
|
|
|
.Ar avrdoper.
|
|
|
|
|
Libusb support is required on Unix but not on Windows. For more
|
|
|
|
|
information about AVR-Doper see http://www.obdev.at/avrusb/avrdoper.html.
|
|
|
|
|
.Pp
|
2011-08-17 15:24:09 +00:00
|
|
|
For the USBtinyISP, which is a simplicistic device not implementing
|
|
|
|
|
serial numbers, multiple devices can be distinguished by their
|
|
|
|
|
location in the USB hierarchy. See the the respective
|
|
|
|
|
.Em Troubleshooting
|
|
|
|
|
entry in the detailed documentation for examples.
|
|
|
|
|
.Pp
|
2006-08-31 20:52:47 +00:00
|
|
|
For programmers that attach to a serial port using some kind of
|
|
|
|
|
higher level protocol (as opposed to bit-bang style programmers),
|
|
|
|
|
.Ar port
|
|
|
|
|
can be specified as
|
|
|
|
|
.Pa net Ns \&: Ns Ar host Ns \&: Ns Ar port .
|
|
|
|
|
In this case, instead of trying to open a local device, a TCP
|
|
|
|
|
network connection to (TCP)
|
|
|
|
|
.Ar port
|
|
|
|
|
on
|
|
|
|
|
.Ar host
|
|
|
|
|
is established.
|
|
|
|
|
The remote endpoint is assumed to be a terminal or console server
|
|
|
|
|
that connects the network stream to a local serial port where the
|
|
|
|
|
actual programmer has been attached to.
|
|
|
|
|
The port is assumed to be properly configured, for example using a
|
|
|
|
|
transparent 8-bit data connection without parity at 115200 Baud
|
|
|
|
|
for a STK500.
|
|
|
|
|
.Em This feature is currently not implemented for Win32 systems.
|
2003-08-01 20:11:21 +00:00
|
|
|
.It Fl q
|
|
|
|
|
Disable (or quell) output of the progress bar while reading or writing
|
2005-09-17 15:23:05 +00:00
|
|
|
to the device. Specify it a second time for even quieter operation.
|
2005-09-21 02:00:58 +00:00
|
|
|
.It Fl s
|
|
|
|
|
Disable safemode prompting. When safemode discovers that one or more
|
|
|
|
|
fuse bits have unintentionally changed, it will prompt for
|
|
|
|
|
confirmation regarding whether or not it should attempt to recover the
|
|
|
|
|
fuse bit(s). Specifying this flag disables the prompt and assumes
|
|
|
|
|
that the fuse bit(s) should be recovered without asking for
|
|
|
|
|
confirmation first.
|
2001-01-20 04:14:01 +00:00
|
|
|
.It Fl t
|
|
|
|
|
Tells
|
|
|
|
|
.Nm
|
|
|
|
|
to enter the interactive ``terminal'' mode instead of up- or downloading
|
|
|
|
|
files. See below for a detailed description of the terminal mode.
|
2005-02-10 18:03:32 +00:00
|
|
|
.It Fl u
|
2005-09-21 01:54:19 +00:00
|
|
|
Disable the safemode fuse bit checks. Safemode is enabled by default
|
|
|
|
|
and is intended to prevent unintentional fuse bit changes. When
|
|
|
|
|
enabled, safemode will issue a warning if the any fuse bits are found
|
|
|
|
|
to be different at program exit than they were when
|
|
|
|
|
.Nm
|
|
|
|
|
was invoked. Safemode won't alter fuse bits itself, but rather will
|
|
|
|
|
prompt for instructions, unless the terminal is non-interactive, in
|
|
|
|
|
which case safemode is disabled. See the
|
|
|
|
|
.Fl s
|
|
|
|
|
option to disable safemode prompting.
|
Introduce a new option, -U, for performing memory operions. Its
argument is a 4 field string (fields seperated by colons) which
indicate what memory type to operate on, what operation to perform is
(read, write, or verify), the filename to read from, write to, or
verify against, and an optional file format field. Multple -U options
can be specified to operate on more than one memory at a time with a
single invocation. For example, to update both the flash and the
eeprom at the same time one can now specify the following:
avrdude -p -e -U flash:w:main.hex:i -U eeprom:w:eeprom.hex:i
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@341 81a1dc3b-b13d-400b-aceb-764788c761c2
2003-08-21 04:52:36 +00:00
|
|
|
.It Xo Fl U Ar memtype Ns
|
|
|
|
|
.Ar \&: Ns Ar op Ns
|
|
|
|
|
.Ar \&: Ns Ar filename Ns
|
|
|
|
|
.Op \&: Ns Ar format
|
|
|
|
|
.Xc
|
|
|
|
|
Perform a memory operation as indicated. The
|
|
|
|
|
.Ar memtype
|
2005-09-16 20:38:29 +00:00
|
|
|
field specifies the memory type to operate on.
|
2006-03-24 02:49:09 +00:00
|
|
|
The available memory types are device-dependent, the actual
|
2005-09-16 20:38:29 +00:00
|
|
|
configuration can be viewed with the
|
|
|
|
|
.Cm part
|
|
|
|
|
command in terminal mode.
|
|
|
|
|
Typically, a device's memory configuration at least contains
|
|
|
|
|
the memory types
|
|
|
|
|
.Ar flash
|
|
|
|
|
and
|
|
|
|
|
.Ar eeprom .
|
|
|
|
|
All memory types currently known are:
|
|
|
|
|
.Bl -tag -width "calibration" -compact
|
|
|
|
|
.It calibration
|
|
|
|
|
One or more bytes of RC oscillator calibration data.
|
|
|
|
|
.It eeprom
|
|
|
|
|
The EEPROM of the device.
|
|
|
|
|
.It efuse
|
|
|
|
|
The extended fuse byte.
|
|
|
|
|
.It flash
|
|
|
|
|
The flash ROM of the device.
|
|
|
|
|
.It fuse
|
|
|
|
|
The fuse byte in devices that have only a single fuse byte.
|
|
|
|
|
.It hfuse
|
|
|
|
|
The high fuse byte.
|
|
|
|
|
.It lfuse
|
|
|
|
|
The low fuse byte.
|
|
|
|
|
.It lock
|
|
|
|
|
The lock byte.
|
|
|
|
|
.It signature
|
|
|
|
|
The three device signature bytes (device ID).
|
2010-01-14 13:46:02 +00:00
|
|
|
.It fuse Ns Em N
|
|
|
|
|
The fuse bytes of ATxmega devices,
|
|
|
|
|
.Em N
|
|
|
|
|
is an integer number
|
|
|
|
|
for each fuse supported by the device.
|
|
|
|
|
.It application
|
|
|
|
|
The application flash area of ATxmega devices.
|
|
|
|
|
.It apptable
|
|
|
|
|
The application table flash area of ATxmega devices.
|
|
|
|
|
.It boot
|
|
|
|
|
The boot flash area of ATxmega devices.
|
|
|
|
|
.It prodsig
|
|
|
|
|
The production signature (calibration) area of ATxmega devices.
|
|
|
|
|
.It usersig
|
|
|
|
|
The user signature area of ATxmega devices.
|
2005-09-16 20:38:29 +00:00
|
|
|
.El
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
Introduce a new option, -U, for performing memory operions. Its
argument is a 4 field string (fields seperated by colons) which
indicate what memory type to operate on, what operation to perform is
(read, write, or verify), the filename to read from, write to, or
verify against, and an optional file format field. Multple -U options
can be specified to operate on more than one memory at a time with a
single invocation. For example, to update both the flash and the
eeprom at the same time one can now specify the following:
avrdude -p -e -U flash:w:main.hex:i -U eeprom:w:eeprom.hex:i
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@341 81a1dc3b-b13d-400b-aceb-764788c761c2
2003-08-21 04:52:36 +00:00
|
|
|
.Ar op
|
|
|
|
|
field specifies what operation to perform:
|
|
|
|
|
.Bl -tag -width noreset
|
|
|
|
|
.It Ar r
|
|
|
|
|
read device memory and write to the specified file
|
|
|
|
|
.It Ar w
|
|
|
|
|
read data from the specified file and write to the device memory
|
|
|
|
|
.It Ar v
|
|
|
|
|
read data from both the device and the specified file and perform a verify
|
|
|
|
|
.El
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Ar filename
|
|
|
|
|
field indicates the name of the file to read or write.
|
|
|
|
|
The
|
|
|
|
|
.Ar format
|
|
|
|
|
field is optional and contains the format of the file to read or
|
2004-02-10 00:20:51 +00:00
|
|
|
write.
|
|
|
|
|
.Ar Format
|
|
|
|
|
can be one of:
|
|
|
|
|
.Bl -tag -width sss
|
|
|
|
|
.It Ar i
|
|
|
|
|
Intel Hex
|
|
|
|
|
.It Ar s
|
|
|
|
|
Motorola S-record
|
|
|
|
|
.It Ar r
|
|
|
|
|
raw binary; little-endian byte order, in the case of the flash ROM data
|
|
|
|
|
.It Ar m
|
2006-03-24 02:49:09 +00:00
|
|
|
immediate; actual byte values specified on the command line, separated
|
2004-02-10 00:20:51 +00:00
|
|
|
by commas or spaces. This is good for programming fuse bytes without
|
|
|
|
|
having to create a single-byte file or enter terminal mode.
|
|
|
|
|
.It Ar a
|
|
|
|
|
auto detect; valid for input only, and only if the input is not
|
|
|
|
|
provided at
|
|
|
|
|
.Em stdin .
|
2006-09-08 21:28:24 +00:00
|
|
|
.It Ar d
|
|
|
|
|
decimal; this and the following formats are only valid on output.
|
|
|
|
|
They generate one line of output for the respective memory section,
|
|
|
|
|
forming a comma-separated list of the values.
|
|
|
|
|
This can be particularly useful for subsequent processing, like for
|
|
|
|
|
fuse bit settings.
|
|
|
|
|
.It Ar h
|
|
|
|
|
hexadecimal; each value will get the string
|
|
|
|
|
.Em 0x
|
|
|
|
|
prepended.
|
|
|
|
|
.It Ar o
|
|
|
|
|
octal; each value will get a
|
|
|
|
|
.Em 0
|
|
|
|
|
prepended unless it is less than 8 in which case it gets no prefix.
|
|
|
|
|
.It Ar b
|
|
|
|
|
binary; each value will get the string
|
|
|
|
|
.Em 0b
|
|
|
|
|
prepended.
|
2004-02-10 00:20:51 +00:00
|
|
|
.El
|
|
|
|
|
.Pp
|
|
|
|
|
The default is to use auto detection for input files, and raw binary
|
|
|
|
|
format for output files.
|
2003-11-26 22:05:02 +00:00
|
|
|
Note that if
|
|
|
|
|
.Ar filename
|
|
|
|
|
contains a colon, the
|
|
|
|
|
.Ar format
|
|
|
|
|
field is no longer optional since the filename part following the colon
|
|
|
|
|
would otherwise be misinterpreted as
|
|
|
|
|
.Ar format .
|
2006-09-08 21:52:45 +00:00
|
|
|
.Pp
|
|
|
|
|
As an abbreviation, the form
|
|
|
|
|
.Fl U Ar filename
|
|
|
|
|
is equivalent to specifying
|
|
|
|
|
.Fl U Em flash:w: Ns Ar filename Ns :a .
|
|
|
|
|
This will only work if
|
|
|
|
|
.Ar filename
|
|
|
|
|
does not have a colon in it.
|
2002-10-29 01:59:02 +00:00
|
|
|
.It Fl v
|
|
|
|
|
Enable verbose output.
|
|
|
|
|
.It Fl V
|
|
|
|
|
Disable automatic verify check when uploading data.
|
2007-11-06 19:42:16 +00:00
|
|
|
.It Fl x Ar extended_param
|
|
|
|
|
Pass
|
|
|
|
|
.Ar extended_param
|
|
|
|
|
to the chosen programmer implementation as an extended parameter.
|
|
|
|
|
The interpretation of the extended parameter depends on the
|
|
|
|
|
programmer itself.
|
|
|
|
|
See below for a list of programmers accepting extended parameters.
|
2002-08-01 01:00:03 +00:00
|
|
|
.It Fl y
|
|
|
|
|
Tells
|
|
|
|
|
.Nm
|
2002-10-13 04:22:59 +00:00
|
|
|
to use the last four bytes of the connected parts' EEPROM memory to
|
2002-08-01 01:00:03 +00:00
|
|
|
track the number of times the device has been erased. When this
|
|
|
|
|
option is used and the
|
|
|
|
|
.Fl e
|
|
|
|
|
flag is specified to generate a chip erase, the previous counter will
|
|
|
|
|
be saved before the chip erase, it is then incremented, and written
|
|
|
|
|
back after the erase cycle completes. Presumably, the device would
|
|
|
|
|
only be erased just before being programmed, and thus, this can be
|
2002-08-01 02:06:48 +00:00
|
|
|
utilized to give an indication of how many erase-rewrite cycles the
|
2002-08-01 01:00:03 +00:00
|
|
|
part has undergone. Since the FLASH memory can only endure a finite
|
|
|
|
|
number of erase-rewrite cycles, one can use this option to track when
|
|
|
|
|
a part is nearing the limit. The typical limit for Atmel AVR FLASH is
|
2002-10-13 04:22:59 +00:00
|
|
|
1000 cycles. Of course, if the application needs the last four bytes
|
2002-08-01 01:00:03 +00:00
|
|
|
of EEPROM memory, this option should not be used.
|
|
|
|
|
.It Fl Y Ar cycles
|
|
|
|
|
Instructs
|
|
|
|
|
.Nm
|
2002-10-13 04:22:59 +00:00
|
|
|
to initialize the erase-rewrite cycle counter residing at the last four
|
2002-08-01 01:00:03 +00:00
|
|
|
bytes of EEPROM memory to the specified value. If the application
|
2002-10-13 04:22:59 +00:00
|
|
|
needs the last four bytes of EEPROM memory, this option should not be
|
2002-08-01 01:00:03 +00:00
|
|
|
used.
|
2001-01-20 04:14:01 +00:00
|
|
|
.El
|
|
|
|
|
.Ss Terminal mode
|
|
|
|
|
In this mode,
|
|
|
|
|
.Nm
|
|
|
|
|
only initializes communication with the MCU, and then awaits user
|
|
|
|
|
commands on standard input. Commands and parameters may be
|
|
|
|
|
abbreviated to the shortest unambiguous form. Terminal mode provides
|
|
|
|
|
a command history using
|
|
|
|
|
.Xr readline 3 ,
|
|
|
|
|
so previously entered command lines can be recalled and edited. The
|
|
|
|
|
following commands are currently implemented:
|
|
|
|
|
.Bl -tag -offset indent -width indent
|
2001-12-30 00:04:52 +00:00
|
|
|
.It Ar dump memtype addr nbytes
|
2001-01-20 04:14:01 +00:00
|
|
|
Read
|
|
|
|
|
.Ar nbytes
|
|
|
|
|
bytes from the specified memory area, and display them in the usual
|
|
|
|
|
hexadecimal and ASCII form.
|
|
|
|
|
.It Ar dump
|
|
|
|
|
Continue dumping the memory contents for another
|
|
|
|
|
.Ar nbytes
|
|
|
|
|
where the previous
|
|
|
|
|
.Ar dump
|
|
|
|
|
command left off.
|
2001-12-30 00:04:52 +00:00
|
|
|
.It Ar write memtype addr byte1 ... byteN
|
2001-01-20 04:14:01 +00:00
|
|
|
Manually program the respective memory cells, starting at address
|
|
|
|
|
.Ar addr ,
|
|
|
|
|
using the values
|
|
|
|
|
.Ar byte1
|
|
|
|
|
through
|
|
|
|
|
.Ar byteN .
|
2001-10-15 00:00:09 +00:00
|
|
|
This feature is not implemented for bank-addressed memories such as
|
2001-12-30 00:04:52 +00:00
|
|
|
the flash memory of ATMega devices.
|
2001-01-20 04:14:01 +00:00
|
|
|
.It Ar erase
|
|
|
|
|
Perform a chip erase.
|
2001-12-30 00:04:52 +00:00
|
|
|
.It Ar send b1 b2 b3 b4
|
|
|
|
|
Send raw instruction codes to the AVR device. If you need access to a
|
|
|
|
|
feature of an AVR part that is not directly supported by
|
|
|
|
|
.Nm ,
|
|
|
|
|
this command allows you to use it, even though
|
|
|
|
|
.Nm
|
2009-02-17 15:31:27 +00:00
|
|
|
does not implement the command. When using direct SPI mode, up to 3 bytes
|
|
|
|
|
can be omitted.
|
2001-01-20 04:14:01 +00:00
|
|
|
.It Ar sig
|
|
|
|
|
Display the device signature bytes.
|
2009-02-17 15:31:27 +00:00
|
|
|
.It Ar spi
|
|
|
|
|
Enter direct SPI mode. The
|
|
|
|
|
.Em pgmled
|
|
|
|
|
pin acts as slave select.
|
|
|
|
|
.Em Only supported on parallel bitbang programmers.
|
2001-01-20 04:14:01 +00:00
|
|
|
.It Ar part
|
2005-09-17 15:23:05 +00:00
|
|
|
Display the current part settings and parameters. Includes chip
|
|
|
|
|
specific information including all memory types supported by the
|
|
|
|
|
device, read/write timing, etc.
|
2009-02-17 15:31:27 +00:00
|
|
|
.It Ar pgm
|
|
|
|
|
Return to programming mode (from direct SPI mode).
|
2003-07-24 21:26:28 +00:00
|
|
|
.It Ar vtarg voltage
|
|
|
|
|
Set the target's supply voltage to
|
|
|
|
|
.Ar voltage
|
|
|
|
|
Volts.
|
2008-03-14 13:00:08 +00:00
|
|
|
.Em Only supported on the STK500 and STK600 programmer.
|
2008-03-24 21:22:04 +00:00
|
|
|
.It Ar varef Oo Ar channel Oc Ar voltage
|
2003-07-24 21:26:28 +00:00
|
|
|
Set the adjustable voltage source to
|
|
|
|
|
.Ar voltage
|
|
|
|
|
Volts.
|
|
|
|
|
This voltage is normally used to drive the target's
|
|
|
|
|
.Em Aref
|
|
|
|
|
input on the STK500.
|
2008-03-14 13:00:08 +00:00
|
|
|
On the Atmel STK600, two reference voltages are available, which
|
|
|
|
|
can be selected by the optional
|
|
|
|
|
.Ar channel
|
|
|
|
|
argument (either 0 or 1).
|
|
|
|
|
.Em Only supported on the STK500 and STK600 programmer.
|
2003-07-24 21:26:28 +00:00
|
|
|
.It Ar fosc freq Ns Op M Ns \&| Ns k
|
|
|
|
|
Set the master oscillator to
|
|
|
|
|
.Ar freq
|
|
|
|
|
Hz.
|
|
|
|
|
An optional trailing letter
|
|
|
|
|
.Ar \&M
|
|
|
|
|
multiplies by 1E6, a trailing letter
|
|
|
|
|
.Ar \&k
|
|
|
|
|
by 1E3.
|
2008-03-14 13:00:08 +00:00
|
|
|
.Em Only supported on the STK500 and STK600 programmer.
|
2003-07-24 21:26:28 +00:00
|
|
|
.It Ar fosc off
|
|
|
|
|
Turn the master oscillator off.
|
2008-03-14 13:00:08 +00:00
|
|
|
.Em Only supported on the STK500 and STK600 programmer.
|
2004-07-07 08:59:07 +00:00
|
|
|
.It Ar sck period
|
2008-03-14 13:00:08 +00:00
|
|
|
.Em STK500 and STK600 programmer only:
|
2004-07-07 08:59:07 +00:00
|
|
|
Set the SCK clock period to
|
|
|
|
|
.Ar period
|
|
|
|
|
microseconds.
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
.Pp
|
|
|
|
|
.Em JTAG ICE only:
|
|
|
|
|
Set the JTAG ICE bit clock period to
|
|
|
|
|
.Ar period
|
|
|
|
|
microseconds.
|
|
|
|
|
Note that unlike STK500 settings, this setting will be reverted to
|
|
|
|
|
its default value (approximately 1 microsecond) when the programming
|
|
|
|
|
software signs off from the JTAG ICE.
|
2006-09-06 20:06:07 +00:00
|
|
|
This parameter can also be used on the JTAG ICE mkII to specify the
|
|
|
|
|
ISP clock period when operating the ICE in ISP mode.
|
2003-07-24 21:26:28 +00:00
|
|
|
.It Ar parms
|
2008-03-14 13:00:08 +00:00
|
|
|
.Em STK500 and STK600 programmer only:
|
2003-07-24 21:26:28 +00:00
|
|
|
Display the current voltage and master oscillator parameters.
|
Mega-commit to bring in both, the STK500v2 support from Erik
Walthinsen, as well as JTAG ICE mkII support (by me).
Erik's submission has been cleaned up a little bit, mostly to add his
name and the current year to the copyright of the new file, remove
trailing white space before importing the files, and fix the minor
syntax errors in his avrdude.conf.in additions (missing semicolons).
The JTAG ICE mkII support should be considered alpha to beta quality
at this point. Few things are still to be done, like defering the
hfuse (OCDEN) tweaks until they are really required. Also, for
reasons not yet known, the target MCU doesn't start to run after
signing off from the ICE, it needs a power-cycle first (at least on my
STK500).
Note that for the JTAG ICE, I did change a few things in the internal
API. Notably I made the serial receive timeout configurable by the
backends via an exported variable (done in both the Posix and the
Win32 implementation), and I made the serial_recv() function return a
-1 instead of bailing out with exit(1) upon encountering a receive
timeout (currently only done in the Posix implementation). Both
measures together allow me to receive a datastreem from the ICE at 115
kbps on a somewhat lossy PCI multi-UART card that occasionally drops a
character. The JTAG ICE mkII protocol has enough of safety layers to
allow recovering from these events, but the previous code wasn't
prepared for any kind of recovery. The Win32 change for this still
has to be done, and the traditional drivers need to be converted to
exit(1) upon encountering a timeout (as they're now getting a -1
returned they didn't see before in that case).
git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@451 81a1dc3b-b13d-400b-aceb-764788c761c2
2005-05-10 19:17:12 +00:00
|
|
|
.Pp
|
|
|
|
|
.Em JTAG ICE only:
|
|
|
|
|
Display the current target supply voltage and JTAG bit clock rate/period.
|
2001-01-20 04:14:01 +00:00
|
|
|
.It Ar \&?
|
|
|
|
|
.It Ar help
|
|
|
|
|
Give a short on-line summary of the available commands.
|
|
|
|
|
.It Ar quit
|
|
|
|
|
Leave terminal mode and thus
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm avrdude .
|
2001-01-20 04:14:01 +00:00
|
|
|
.El
|
2001-09-20 03:19:31 +00:00
|
|
|
.Ss Default Parallel port pin connections
|
|
|
|
|
(these can be changed, see the
|
|
|
|
|
.Fl c
|
|
|
|
|
option)
|
2001-04-25 22:35:14 +00:00
|
|
|
.TS
|
|
|
|
|
ll.
|
|
|
|
|
\fBPin number\fP \fBFunction\fP
|
|
|
|
|
2-5 Vcc (optional power supply to MCU)
|
|
|
|
|
7 /RESET (to MCU)
|
|
|
|
|
8 SCK (to MCU)
|
|
|
|
|
9 MOSI (to MCU)
|
|
|
|
|
10 MISO (from MCU)
|
|
|
|
|
18-25 GND
|
|
|
|
|
.TE
|
2006-11-20 23:23:37 +00:00
|
|
|
.Ss debugWire limitations
|
|
|
|
|
The debugWire protocol is Atmel's proprietary one-wire (plus ground)
|
|
|
|
|
protocol to allow an in-circuit emulation of the smaller AVR devices,
|
|
|
|
|
using the
|
|
|
|
|
.Ql /RESET
|
|
|
|
|
line.
|
|
|
|
|
DebugWire mode is initiated by activating the
|
|
|
|
|
.Ql DWEN
|
|
|
|
|
fuse, and then power-cycling the target.
|
2010-01-14 15:11:47 +00:00
|
|
|
While this mode is mainly intended for debugging/emulation, it
|
2006-11-20 23:23:37 +00:00
|
|
|
also offers limited programming capabilities.
|
2006-11-23 07:07:06 +00:00
|
|
|
Effectively, the only memory areas that can be read or programmed
|
|
|
|
|
in this mode are flash ROM and EEPROM.
|
2006-11-20 23:23:37 +00:00
|
|
|
It is also possible to read out the signature.
|
|
|
|
|
All other memory areas cannot be accessed.
|
|
|
|
|
There is no
|
|
|
|
|
.Em chip erase
|
|
|
|
|
functionality in debugWire mode; instead, while reprogramming the
|
|
|
|
|
flash ROM, each flash ROM page is erased right before updating it.
|
|
|
|
|
This is done transparently by the JTAG ICE mkII (or AVR Dragon).
|
|
|
|
|
The only way back from debugWire mode is to initiate a special
|
|
|
|
|
sequence of commands to the JTAG ICE mkII (or AVR Dragon), so the
|
|
|
|
|
debugWire mode will be temporarily disabled, and the target can
|
|
|
|
|
be accessed using normal ISP programming.
|
|
|
|
|
This sequence is automatically initiated by using the JTAG ICE mkII
|
|
|
|
|
or AVR Dragon in ISP mode, when they detect that ISP mode cannot be
|
|
|
|
|
entered.
|
2007-11-06 19:42:16 +00:00
|
|
|
.Ss Programmers accepting extended parameters
|
|
|
|
|
.Bl -tag -offset indent -width indent
|
|
|
|
|
.It Ar JTAG ICE mkII
|
|
|
|
|
.It Ar AVR Dragon
|
|
|
|
|
When using the JTAG ICE mkII or AVR Dragon in JTAG mode, the
|
|
|
|
|
following extended parameter is accepted:
|
|
|
|
|
.Bl -tag -offset indent -width indent
|
|
|
|
|
.It Ar jtagchain=UB,UA,BB,BA
|
|
|
|
|
Setup the JTAG scan chain for
|
|
|
|
|
.Ar UB
|
|
|
|
|
units before,
|
|
|
|
|
.Ar UA
|
|
|
|
|
units after,
|
|
|
|
|
.Ar BB
|
|
|
|
|
bits before, and
|
|
|
|
|
.Ar BA
|
|
|
|
|
bits after the target AVR, respectively.
|
|
|
|
|
Each AVR unit within the chain shifts by 4 bits.
|
|
|
|
|
Other JTAG units might require a different bit shift count.
|
|
|
|
|
.El
|
2008-03-24 21:22:04 +00:00
|
|
|
.It Ar AVR910
|
|
|
|
|
.Bl -tag -offset indent -width indent
|
|
|
|
|
.It Ar devcode=VALUE
|
|
|
|
|
Override the device code selection by using
|
|
|
|
|
.Ar VALUE
|
|
|
|
|
as the device code.
|
|
|
|
|
The programmer is not queried for the list of supported
|
|
|
|
|
device codes, and the specified
|
|
|
|
|
.Ar VALUE
|
|
|
|
|
is not verified but used directly within the
|
|
|
|
|
.Ql T
|
|
|
|
|
command sent to the programmer.
|
|
|
|
|
.Ar VALUE
|
|
|
|
|
can be specified using the conventional number notation of the
|
|
|
|
|
C programming language.
|
|
|
|
|
.El
|
2008-06-07 20:55:04 +00:00
|
|
|
.Bl -tag -offset indent -width indent
|
|
|
|
|
.It Ar no_blockmode
|
|
|
|
|
Disables the default checking for block transfer capability.
|
|
|
|
|
Use
|
|
|
|
|
.Ar no_blockmode
|
|
|
|
|
only if your
|
|
|
|
|
.Ar AVR910
|
|
|
|
|
programmer creates errors during initial sequence.
|
|
|
|
|
.El
|
2009-11-04 03:32:55 +00:00
|
|
|
.It Ar buspirate
|
|
|
|
|
.Bl -tag -offset indent -width indent
|
2009-11-09 02:18:40 +00:00
|
|
|
.It Ar reset={cs,aux,aux2}
|
|
|
|
|
The default setup assumes the BusPirate's CS output pin connected to
|
|
|
|
|
the RESET pin on AVR side. It is however possible to have multiple AVRs
|
|
|
|
|
connected to the same BP with MISO, MOSI and SCK lines common for all of them.
|
|
|
|
|
In such a case one AVR should have its RESET connected to BusPirate's
|
|
|
|
|
.Pa CS
|
|
|
|
|
pin, second AVR's RESET connected to BusPirate's
|
|
|
|
|
.Pa AUX
|
|
|
|
|
pin and if your BusPirate has an
|
|
|
|
|
.Pa AUX2
|
|
|
|
|
pin (only available on BusPirate version v1a with firmware 3.0 or newer)
|
|
|
|
|
use that to activate RESET on the third AVR.
|
|
|
|
|
.Pp
|
|
|
|
|
It may be a good idea to decouple the BusPirate and the AVR's SPI buses from
|
|
|
|
|
each other using a 3-state bus buffer. For example 74HC125 or 74HC244 are some
|
|
|
|
|
good candidates with the latches driven by the appropriate reset pin (cs,
|
|
|
|
|
aux or aux2). Otherwise the SPI traffic in one active circuit may interfere
|
|
|
|
|
with programming the AVR in the other design.
|
|
|
|
|
.It Ar speed=<0..7>
|
|
|
|
|
BusPirate to AVR SPI speed:
|
|
|
|
|
.Bd -literal
|
|
|
|
|
0 .. 30 kHz (default)
|
|
|
|
|
1 .. 125 kHz
|
|
|
|
|
2 .. 250 kHz
|
|
|
|
|
3 .. 1 MHz
|
|
|
|
|
4 .. 2 MHz
|
|
|
|
|
5 .. 2.6 MHz
|
|
|
|
|
6 .. 4 MHz
|
|
|
|
|
7 .. 8 MHz
|
|
|
|
|
.Ed
|
2009-11-04 03:32:55 +00:00
|
|
|
.It Ar ascii
|
|
|
|
|
Use ASCII mode even when the firmware supports BinMode (binary mode).
|
|
|
|
|
BinMode is supported in firmware 2.7 and newer, older FW's either don't
|
2009-11-09 02:18:40 +00:00
|
|
|
have BinMode or their BinMode is buggy. ASCII mode is slower and makes
|
|
|
|
|
the above
|
|
|
|
|
.Ar reset=
|
|
|
|
|
and
|
|
|
|
|
.Ar speed=
|
|
|
|
|
parameters unavailable.
|
2009-11-04 03:32:55 +00:00
|
|
|
.El
|
2007-11-06 19:42:16 +00:00
|
|
|
.El
|
2001-01-20 04:14:01 +00:00
|
|
|
.Sh FILES
|
|
|
|
|
.Bl -tag -offset indent -width /dev/ppi0XXX
|
|
|
|
|
.It Pa /dev/ppi0
|
|
|
|
|
default device to be used for communication with the programming
|
|
|
|
|
hardware
|
2003-02-06 05:13:32 +00:00
|
|
|
.It Pa ${PREFIX}/etc/avrdude.conf
|
2003-03-10 21:51:55 +00:00
|
|
|
programmer and parts configuration file
|
|
|
|
|
.It Pa ${HOME}/.avrduderc
|
|
|
|
|
programmer and parts configuration file (per-user overrides)
|
2001-01-20 04:14:01 +00:00
|
|
|
.It Pa ~/.inputrc
|
|
|
|
|
Initialization file for the
|
|
|
|
|
.Xr readline 3
|
|
|
|
|
library
|
2003-02-06 05:13:32 +00:00
|
|
|
.It Pa ${PREFIX}/share/doc/avrdude/avrdude.pdf
|
2001-04-25 22:35:14 +00:00
|
|
|
Schematic of programming hardware
|
2001-01-20 04:14:01 +00:00
|
|
|
.El
|
|
|
|
|
.\" .Sh EXAMPLES
|
2006-09-07 20:42:01 +00:00
|
|
|
.Sh DIAGNOSTICS
|
|
|
|
|
.Bd -literal
|
|
|
|
|
avrdude: jtagmkII_setparm(): bad response to set parameter command: RSP_FAILED
|
|
|
|
|
avrdude: jtagmkII_getsync(): ISP activation failed, trying debugWire
|
|
|
|
|
avrdude: Target prepared for ISP, signed off.
|
|
|
|
|
avrdude: Please restart avrdude without power-cycling the target.
|
|
|
|
|
.Ed
|
|
|
|
|
.Pp
|
|
|
|
|
If the target AVR has been set up for debugWire mode (i. e. the
|
|
|
|
|
.Em DWEN
|
|
|
|
|
fuse is programmed), normal ISP connection attempts will fail as
|
|
|
|
|
the
|
|
|
|
|
.Em /RESET
|
|
|
|
|
pin is not available.
|
|
|
|
|
When using the JTAG ICE mkII in ISP mode, the message shown indicates
|
|
|
|
|
that
|
|
|
|
|
.Nm
|
|
|
|
|
has guessed this condition, and tried to initiate a debugWire reset
|
|
|
|
|
to the target.
|
|
|
|
|
When successful, this will leave the target AVR in a state where it
|
|
|
|
|
can respond to normal ISP communication again (until the next power
|
|
|
|
|
cycle).
|
|
|
|
|
Typically, the same command is going to be retried again immediately
|
|
|
|
|
afterwards, and will then succeed connecting to the target using
|
|
|
|
|
normal ISP communication.
|
2001-01-20 04:14:01 +00:00
|
|
|
.Sh SEE ALSO
|
|
|
|
|
.Xr avr-objcopy 1 ,
|
|
|
|
|
.Xr ppi 4 ,
|
|
|
|
|
.Xr readline 3
|
|
|
|
|
.Pp
|
|
|
|
|
The AVR microcontroller product description can be found at
|
|
|
|
|
.Pp
|
2003-02-24 23:27:31 +00:00
|
|
|
.Dl "http://www.atmel.com/products/AVR/"
|
2001-01-20 04:14:01 +00:00
|
|
|
.\" .Sh HISTORY
|
|
|
|
|
.Sh AUTHORS
|
2003-02-06 05:13:32 +00:00
|
|
|
.Nm Avrdude
|
2001-11-24 01:47:10 +00:00
|
|
|
was written by Brian S. Dean <bsd@bsdhome.com>.
|
2001-01-20 04:14:01 +00:00
|
|
|
.Pp
|
|
|
|
|
This man page by
|
|
|
|
|
.ie t J\(:org Wunsch.
|
|
|
|
|
.el Joerg Wunsch.
|
|
|
|
|
.Sh BUGS
|
2005-05-19 04:49:46 +00:00
|
|
|
Please report bugs via
|
|
|
|
|
.Dl "http://savannah.nongnu.org/bugs/?group=avrdude" .
|
|
|
|
|
.Pp
|
2005-11-29 22:58:04 +00:00
|
|
|
The JTAG ICE programmers currently cannot write to the flash ROM
|
2005-05-19 04:49:46 +00:00
|
|
|
one byte at a time.
|
|
|
|
|
For that reason, updating the flash ROM from terminal mode does not
|
|
|
|
|
work.
|
2005-07-28 16:06:35 +00:00
|
|
|
.Pp
|
2005-11-29 22:58:04 +00:00
|
|
|
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.
|
2008-03-14 13:00:08 +00:00
|
|
|
This also applies to the STK500 and STK600 in parallel programming mode.
|
2006-09-10 20:41:00 +00:00
|
|
|
.Pp
|
2007-10-29 18:03:02 +00:00
|
|
|
The USBasp and USBtinyISP drivers do not offer any option to distinguish multiple
|
2006-09-10 20:41:00 +00:00
|
|
|
devices connected simultaneously, so effectively only a single device
|
|
|
|
|
is supported.
|
