2001-01-20 04:14:01 +00:00
|
|
|
.\"
|
2003-02-08 04:17:25 +00:00
|
|
|
.\" avrdude - A Downloader/Uploader for AVR device programmers
|
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
|
|
|
.\" Copyright (C) 2001, 2002, 2003, 2005 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$
|
|
|
|
.\"
|
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
|
|
|
.Dd DATE May 10, 2005
|
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
|
2001-10-15 00:00:09 +00:00
|
|
|
.Op Fl n
|
2002-12-07 15:16:24 +00:00
|
|
|
.Op Fl P Ar port
|
2003-08-01 20:11:21 +00:00
|
|
|
.Op Fl q
|
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
|
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,
|
|
|
|
Atmel's JTAG ICE mkII,
|
|
|
|
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
|
2001-01-20 04:14:01 +00:00
|
|
|
parallel 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
|
|
|
|
standalone programming device. Some status LEDs indicating the
|
|
|
|
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
|
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).
|
|
|
|
.Pp
|
|
|
|
Atmel's JTAG ICE mkII is supported as well to up- or download memory
|
|
|
|
areas from/to an AVR target (no support for on-chip debugging).
|
2001-01-20 04:14:01 +00:00
|
|
|
.Pp
|
|
|
|
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
|
|
|
|
as seperate memory types and can be programmed using data from a file
|
|
|
|
(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.
|
2003-07-24 21:26:28 +00:00
|
|
|
On the STK500 programmer, several operational parameters (target supply
|
|
|
|
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
|
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
|
|
|
c128 AT90CAN128
|
2001-01-20 04:14:01 +00:00
|
|
|
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
|
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
|
|
|
|
m16 ATmega16
|
|
|
|
m161 ATmega161
|
|
|
|
m162 ATmega162
|
|
|
|
m163 ATmega163
|
|
|
|
m169 ATmega169
|
|
|
|
m32 ATmega32
|
|
|
|
m48 ATmega48
|
|
|
|
m64 ATmega64
|
|
|
|
m8 ATmega8
|
|
|
|
m8515 ATmega8515
|
|
|
|
m8535 ATmega8535
|
|
|
|
m88 ATmega88
|
|
|
|
t12 ATtiny12
|
|
|
|
t13 ATtiny13
|
|
|
|
t15 ATtiny15
|
|
|
|
t2313 ATtiny2313
|
|
|
|
t26 ATtiny26
|
2001-01-20 04:14:01 +00:00
|
|
|
.TE
|
2003-02-19 09:01:54 +00:00
|
|
|
.Bl -tag -width "(*) "
|
|
|
|
.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.
|
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
|
|
|
|
Specify the bit clock period for the JTAG interface (JTAG ICE only).
|
|
|
|
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.
|
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 ,
|
|
|
|
and is basically a prerequisite command before the flash ROM can be
|
|
|
|
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.
|
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
|
|
|
).
|
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.
|
2003-08-01 20:11:21 +00:00
|
|
|
.It Fl q
|
|
|
|
Disable (or quell) output of the progress bar while reading or writing
|
|
|
|
to the device.
|
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
|
|
|
|
Disable safemode and allow the fuse bits to be changed. Safemode is
|
|
|
|
enabled by default and is intended to prevent unintentionally changing
|
|
|
|
the fuse bits.
|
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
|
|
|
|
field specifies the memory type to operate on. The
|
|
|
|
.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
|
|
|
|
immediate; actual byte values specified on the command line, seperated
|
|
|
|
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 .
|
|
|
|
.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 .
|
2002-10-29 01:59:02 +00:00
|
|
|
.It Fl v
|
|
|
|
Enable verbose output.
|
|
|
|
.It Fl V
|
|
|
|
Disable automatic verify check when uploading data.
|
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
|
|
|
|
does not implement the command.
|
2001-01-20 04:14:01 +00:00
|
|
|
.It Ar sig
|
|
|
|
Display the device signature bytes.
|
|
|
|
.It Ar part
|
|
|
|
Display the current part settings.
|
2003-07-24 21:26:28 +00:00
|
|
|
.It Ar vtarg voltage
|
|
|
|
Set the target's supply voltage to
|
|
|
|
.Ar voltage
|
|
|
|
Volts.
|
|
|
|
.Em Only supported on the STK500 programmer.
|
|
|
|
.It Ar varef voltage
|
|
|
|
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.
|
|
|
|
.Em Only supported on the STK500 programmer.
|
|
|
|
.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.
|
|
|
|
.Em Only supported on the STK500 programmer.
|
|
|
|
.It Ar fosc off
|
|
|
|
Turn the master oscillator off.
|
|
|
|
.Em Only supported on the STK500 programmer.
|
2004-07-07 08:59:07 +00:00
|
|
|
.It Ar sck period
|
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
|
|
|
.Em STK500 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.
|
2003-07-24 21:26:28 +00:00
|
|
|
.It Ar parms
|
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
|
|
|
.Em STK500 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
|
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
|
|
|
|
.\" .Sh DIAGNOSTICS
|
|
|
|
.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
|
2003-02-20 03:53:49 +00:00
|
|
|
Please report bugs to avrdude-dev@nongnu.org.
|