pinner:sd8psrc matt$ avrdude -c stk500hvsp -p t85 -P /dev/cu.usbserial-FTCAKAH8 -U flash:w:sd8p_hr.hex:a
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.05s
avrdude: Device signature = 0x1e930b
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "sd8p_hr.hex"
avrdude: input file sd8p_hr.hex auto detected as Intel Hex
avrdude: ERROR: address 0x820003 out of range at line 406 of sd8p_hr.hex
avrdude: write to file 'sd8p_hr.hex' failed
avrdude: safemode: Fuses OK
avrdude done. Thank you.
Wednesday, November 24, 2010
Tuesday, November 02, 2010
Seattle HackerSpaces
I'm on a trip in Seattle for friends, family, Halloween, and to checkout some local hackerspaces.
Coming from LA where we have just a handful I was excited to see the hackerspaces.org listing 7 in Seattle. The Los Angeles spaces vary immensely and I'm most curious to see how the spaces in Seattle differ.
My first pass of comparison is of course web-based.
* 911 Media Arts Center: "making media matters"
* Hackerbot Labs: "Like prom night for your warranty" (and many many more)
* Hazard Factory: "Flaming tetherball: not just a state of mind, it's this scar right here."
Fun fun fun huge industrial art space. lots of welding and risky projects
* Jigsaw Renaissance: "At any moment we are free to act toward the future we desire." --Heinz von Foerster
* Metrix Create:Space: "$1 coffee, fast free Internet, open until midnight"
* Saturday House
looked more or less like a floating hacker community without a space. there were several good links and resources from their site which led to some great current events listings.
* Weird Science Salon
started in 1984 as local tesla-coilers meeting. they seems to be still meeting regularly in a very cool museum nearby Metrix. Also, they've got write-up of soem dangerous experiments.
take aways thus far:
slogans are great. rotating slogans are better
logos, you ain't a hackerspace without one.
calendar and flickr stream work nicely together to show activity and followthrough
I'm on a trip in Seattle for friends, family, Halloween, and to checkout some local hackerspaces.
Coming from LA where we have just a handful I was excited to see the hackerspaces.org listing 7 in Seattle. The Los Angeles spaces vary immensely and I'm most curious to see how the spaces in Seattle differ.
My first pass of comparison is of course web-based.
* 911 Media Arts Center: "making media matters"
* Hackerbot Labs: "Like prom night for your warranty" (and many many more)
* Hazard Factory: "Flaming tetherball: not just a state of mind, it's this scar right here."
Fun fun fun huge industrial art space. lots of welding and risky projects
* Jigsaw Renaissance: "At any moment we are free to act toward the future we desire." --Heinz von Foerster
* Metrix Create:Space: "$1 coffee, fast free Internet, open until midnight"
* Saturday House
looked more or less like a floating hacker community without a space. there were several good links and resources from their site which led to some great current events listings.
* Weird Science Salon
started in 1984 as local tesla-coilers meeting. they seems to be still meeting regularly in a very cool museum nearby Metrix. Also, they've got write-up of soem dangerous experiments.
take aways thus far:
slogans are great. rotating slogans are better
logos, you ain't a hackerspace without one.
calendar and flickr stream work nicely together to show activity and followthrough
Wednesday, August 04, 2010
FAIL, FAIL, FAIL, WIN. in
this case i won big. photo
missing.
FAIL: needs more diffusion:
I'm planning for the next MinM project and keeping this one in original condition. Something more finished would likely have a dab of hot glue to affix the MinM and provide additional diffusion for the led.
This MinM was recovered from another wearable project because I was in the flow:
FAIL: programming is troublesome:
FAIL: ugly, inflexible, and fragile.
WIN: the magnetic switch:
Often form and function are tackles separately with wearables, in this case a simple knot secured and electrically connected the 26 gauge copper wire to the magnetic switch. This makes possible all kinds of field repair and artistry.
I surveyed a dancer, fashionetasas, musician, and handie some very handie folks . There was a consensus that deemed this production ready with preliminary cost estimates ranging from $25-$75.
Up Next:
Animatred Ears!
and My Avr-Gcc Is Working!
http://spacehippy.blogspot.com/2010/08/my-avr-gcc-is-working-avrdude1-bsd.html
this case i won big. photo
missing.
FAIL: needs more diffusion:
I'm planning for the next MinM project and keeping this one in original condition. Something more finished would likely have a dab of hot glue to affix the MinM and provide additional diffusion for the led.
This MinM was recovered from another wearable project because I was in the flow:
FAIL: programming is troublesome:
FAIL: ugly, inflexible, and fragile.
WIN: the magnetic switch:
Often form and function are tackles separately with wearables, in this case a simple knot secured and electrically connected the 26 gauge copper wire to the magnetic switch. This makes possible all kinds of field repair and artistry.
I surveyed a dancer, fashionetasas, musician, and handie some very handie folks . There was a consensus that deemed this production ready with preliminary cost estimates ranging from $25-$75.
Up Next:
Animatred Ears!
and My Avr-Gcc Is Working!
http://spacehippy.blogspot.com/2010/08/my-avr-gcc-is-working-avrdude1-bsd.html
My Avr-Gcc is working!
AVRDUDE(1) BSD General Commands Manual AVRDUDE(1)
NAME
avrdude -- driver program for ``simple'' Atmel AVR MCU programmer
SYNOPSIS
avrdude -p partno [-b baudrate] [-B bitclock] [-c programmer-id] [-C config-file] [-D] [-e] [-E exitspec[,exitspec]] [-F] [-i delay] [-n] [-O] [-P port] [-q] [-s]
[-t] [-u] [-U memtype:op:filename:filefmt] [-v] [-x extended_param] [-V] [-y] [-Y]
DESCRIPTION
Avrdude is a program for downloading code and data to Atmel AVR microcontrollers. Avrdude supports Atmel's STK500 programmer, Atmel's AVRISP and AVRISP mkII
devices, Atmel's STK600, Atmel's JTAG ICE (both mkI and mkII, the latter also in ISP mode), programmers complying to AppNote AVR910 and AVR109 (including the But-
terfly), as well as a simple hard-wired programmer connected directly to a ppi(4) or parport(4) parallel port, or to a standard serial port. In the simplest case,
the hardware consists just of a cable connecting the respective AVR signal lines to the parallel port.
The MCU is programmed in serial programming mode, so, for the ppi(4) based programmer, the MCU signals `/RESET', `SCK', `MISO' and `MOSI' need to be connected to
the parallel port. Optionally, some otherwise unused output pins of the parallel port can be used to supply power for the MCU part, so it is also possible to con-
struct a passive stand-alone programming device. Some status LEDs indicating the current operating state of the programmer can be connected, and a signal is avail-
able 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.
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.
Atmel's STK500 programmer is also supported and connects to a serial port. Both, firmware versions 1.x and 2.x can be handled, but require a different programmer
type specification (by now). Using firmware version 2, high-voltage programming is also supported, both parallel and serial (programmer types stk500pp and
stk500hvsp).
The Arduino (which is very similar to the STK500 1.x) is supported via its own programmer type specification ``arduino''.
The BusPirate is a versatile tool that can also be used as an AVR programmer. A single BusPirate can be connected to up to 3 independent AVRs. See the section on
extended parameters below for details.
...skipping...
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 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 -B bitclock option
might be required to achieve a stable ISP communication.
The USBasp ISP and USBtinyISP adapters are also supported, provided avrdude has been compiled with libusb support. They both feature simple firwmare-only USB
implementations, running on an ATmega8 (or ATmega88), or ATtiny2313, respectively.
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 asl(1) as a standalone assembler, or avr-objcopy(1) for
the final stage of the GNU toolchain for the AVR microcontroller.
Avrdude 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 avrdude as separate memory types and can be programmed using data from a file (see the -m option) or from terminal
mode (see the dump and 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 interactively communicate with the MCU, and to display or program individual memory cells. On
the STK500 and STK600 programmer, several operational parameters (target supply voltage, target Aref voltage, master clock) can be examined and changed from within
terminal mode as well.
Options
In order to control all the different operation modi, a number of options need to be specified to avrdude.
-p partno
This is the only option that is mandatory for every invocation of avrdude. It specifies the type of the MCU connected to the programmer. These are
read from the config file. If avrdude 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:
Option tag Official part name
c128 AT90CAN128
pwm2 AT90PWM2
pwm3 AT90PWM3
1200 AT90S1200
2313 AT90S2313
2333 AT90S2333
...skipping...
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 tar-
get 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.
Programmers accepting extended parameters
JTAG ICE mkII
AVR Dragon
When using the JTAG ICE mkII or AVR Dragon in JTAG mode, the following extended parameter is accepted:
jtagchain=UB,UA,BB,BA
Setup the JTAG scan chain for UB units before, UA units after, BB bits before, and 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.
AVR910
devcode=VALUE
Override the device code selection by using VALUE as the device code. The programmer is not queried for the list of supported device
codes, and the specified VALUE is not verified but used directly within the `T' command sent to the programmer. VALUE can be specified
using the conventional number notation of the C programming language.
no_blockmode
Disables the default checking for block transfer capability. Use no_blockmode only if your AVR910 programmer creates errors during ini-
tial sequence.
buspirate
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 con-
nected to BusPirate's CS pin, second AVR's RESET connected to BusPirate's AUX pin and if your BusPirate has an AUX2 pin (only available
on BusPirate version v1a with firmware 3.0 or newer) use that to activate RESET on the third AVR.
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.
speed=<0..7>
BusPirate to AVR SPI speed:
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
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 have BinMode or their BinMode is buggy. ASCII mode is slower and makes the above reset= and speed= parameters unavailable.
FILES
/dev/ppi0 default device to be used for communication with the programming hardware
${PREFIX}/etc/avrdude.conf
programmer and parts configuration file
${HOME}/.avrduderc
programmer and parts configuration file (per-user overrides)
~/.inputrc Initialization file for the readline(3) library
${PREFIX}/share/doc/avrdude/avrdude.pdf
Schematic of programming hardware
DIAGNOSTICS
avrdude: jtagmkII_setparm(): bad response to set parameter command: RSP_FAILED
avrdude: jtagmkII_getsync(): ISP activation failed, trying debugWire
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.
Atmel's STK500 programmer is also supported and connects to a serial port. Both, firmware versions 1.x and 2.x can be handled, but require a different programmer
type specification (by now). Using firmware version 2, high-voltage programming is also supported, both parallel and serial (programmer types stk500pp and
stk500hvsp).
The Arduino (which is very similar to the STK500 1.x) is supported via its own programmer type specification ``arduino''.
The BusPirate is a versatile tool that can also be used as an AVR programmer. A single BusPirate can be connected to up to 3 independent AVRs. See the section on
extended parameters below for details.
Atmel's STK600 programmer is supported in ISP and high-voltage programming modes, and connects through the USB. For ATxmega devices, the STK600 is supported in PDI
mode.
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.
Atmel's JTAG ICE (both mkI and mkII) is supported as well to up- or download memory areas from/to an AVR target (no support for on-chip debugging). For the JTAG
ICE mkII, JTAG, debugWire and ISP mode are supported. See below for the limitations of debugWire.
The AVR Dragon is supported in all modes (ISP, JTAG, HVSP, PP, debugWire). When used in JTAG and debugWire mode, the AVR Dragon behaves similar to a 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 -B bitclock option
might be required to achieve a stable ISP communication.
The USBasp ISP and USBtinyISP adapters are also supported, provided avrdude has been compiled with libusb support. They both feature simple firwmare-only USB
implementations, running on an ATmega8 (or ATmega88), or ATtiny2313, respectively.
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 asl(1) as a standalone assembler, or avr-objcopy(1) for
the final stage of the GNU toolchain for the AVR microcontroller.
Avrdude 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 avrdude as separate memory types and can be programmed using data from a file (see the -m option) or from terminal
mode (see the dump and 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 interactively communicate with the MCU, and to display or program individual memory cells. On
the STK500 and STK600 programmer, several operational parameters (target supply voltage, target Aref voltage, master clock) can be examined and changed from within
terminal mode as well.
Options
In order to control all the different operation modi, a number of options need to be specified to avrdude.
-p partno
This is the only option that is mandatory for every invocation of avrdude. It specifies the type of the MCU connected to the programmer. These are
read from the config file. If avrdude 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:
Option tag Official part name
c128 AT90CAN128
pwm2 AT90PWM2
pwm3 AT90PWM3
1200 AT90S1200
2313 AT90S2313
2333 AT90S2333
2343 AT90S2343 (*)
4414 AT90S4414
4433 AT90S4433
4434 AT90S4434
8515 AT90S8515
8535 AT90S8535
m103 ATmega103
m128 ATmega128
m1280 ATmega1280
m1281 ATmega1281
m1284p ATmega1284P
m128rfa1 ATmega128RFA1
m16 ATmega16
m161 ATmega161
m162 ATmega162
m163 ATmega163
m164 ATmega164
m169 ATmega169
m2560 ATmega2560 (**)
m2561 ATmega2561 (**)
m32 ATmega32
m324 ATmega324
m329 ATmega329
m3290 ATmega3290
m48 ATmega48
m64 ATmega64
m640 ATmega640
m644 ATmega644
m649 ATmega649
m6490 ATmega6490
m8 ATmega8
m8515 ATmega8515
m8535 ATmega8535
m88 ATmega88
t12 ATtiny12
t13 ATtiny13
t15 ATtiny15
t2313 ATtiny2313
t25 ATtiny25
t26 ATtiny26
t45 ATtiny45
t85 ATtiny85
ucr2 AT32uca0512
x128a1 ATxmega128A1
x128a1d ATxmega128A1revD
(*) The AT90S2323 and ATtiny22 use the same algorithm.
(**) Flash addressing above 128 KB is not supported by all programming hardware. Known to work are jtag2, stk500v2, and bit-bang programmers.
-b baudrate
Override the RS-232 connection baud rate specified in the respective programmer's entry of the configuration file.
-B bitclock
Specify the bit clock period for the JTAG interface or the ISP clock (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 cer-
tain 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.
-c programmer-id
Use the pin configuration specified by the argument. Pin configurations are read from the config file (see the -C option). New pin configurations
can be easily added or modified through the use of a config file to make avrdude work with different programmers as long as the programmer supports
the Atmel AVR serial program method. You can use the 'default_programmer' keyword in your ${HOME}/.avrduderc file to assign a default programmer to
keep from having to specify this option on every invocation.
-C config-file
Use the specified config file to load configuration data. This file contains all programmer and part definitions that avrdude knows about. If you
have a programmer or part that avrdude 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 the next version). See the config file, located at ${PREFIX}/etc/avrdude.conf, which contains a description of the format.
-D Disable auto erase for flash. When the -U option with flash memory is specified, avrdude will perform a chip erase before starting any of the pro-
gramming operations, since it generally is a mistake to program the flash without performing an erase first. This option disables that. 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.
-e Causes a chip erase to be executed. This will reset the contents of the flash ROM and EEPROM to the value `0xff', 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 reprogrammed again. The only excep-
tion would be if the new contents would exclusively cause bits to be programmed from the value `1' to `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.
-E exitspec[,exitspec]
By default, avrdude leaves the parallel port in the same state at exit as it has been found at startup. This option modifies the state of the
`/RESET' and `Vcc' lines the parallel port is left at, according to the exitspec arguments provided, as follows:
reset The `/RESET' signal will be left activated at program exit, that is it will be held 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 `/RESET' signal is active before powering up the
MCU, so in case an external power supply is used for this MCU type, a previous invocation of avrdude with this option specified is one of the
possible ways to guarantee this condition.
noreset The `/RESET' line will be deactivated at program exit, thus allowing the MCU target program to run while the programming hardware remains
connected.
vcc This option will leave those parallel port pins active (i. e. high) that can be used to supply `Vcc' power to the MCU.
novcc This option will pull the `Vcc' pins of the parallel port down at program exit.
Multiple exitspec arguments can be separated with commas.
-F Normally, avrdude 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. 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 -t to continue in terminal mode.
-i delay
For bitbang-type programmers, delay for approximately delay microseconds between each bit state change. If the host system is very fast, or the tar-
get 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
pinner:freem_a2 matt$ ls -last
total 296
0 drwxr-xr-x 14 matt staff 476 Aug 3 22:00 .
8 -rw-r--r-- 1 matt staff 13 Aug 3 22:00 freem_a2.eep
40 -rwxr-xr-x 1 matt staff 17633 Aug 3 21:57 freem_a2.elf
16 -rw-r--r-- 1 matt staff 6874 Aug 3 21:57 freem_a2.hex
120 -rw-r--r-- 1 matt staff 59931 Aug 3 21:57 freem_a2.lss
32 -rw-r--r-- 1 matt staff 13603 Aug 3 21:57 freem_a2.map
0 drwxr-xr-x 5 matt staff 170 Jul 13 16:41 ..
0 drwxr-xr-x 8 matt staff 272 Jul 13 16:41 .svn
8 -rw-r--r-- 1 matt staff 3250 Jul 13 16:41 Makefile
32 -rw-r--r-- 1 matt staff 13212 Jul 13 16:41 freem_a2.c
16 -rw-r--r-- 1 matt staff 7029 Jul 13 16:41 freem_a2_20100527.hex
8 -rw-r--r-- 1 matt staff 2708 Jul 13 16:41 i2cmaster_bitbang.c
8 -rw-r--r-- 1 matt staff 3738 Jul 13 16:41 irsony.c
8 -rw-r--r-- 1 matt staff 1807 Jul 13 16:41 softuart.h
pinner:freem_a2 matt$ make program
avrdude -p attiny45 -P usb -c avrispmkII -v -v -e -U flash:w:freem_a2.hex -U eeprom:w:freem_a2.eep
avrdude: Version 5.8cvs, compiled on Jan 15 2010 at 17:27:01
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is "/usr/local/CrossPack-AVR-20100115/etc/avrdude.conf"
User configuration file is "/Users/matt/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
Using Port : usb
Using Programmer : avrispmkII
avrdude: usbdev_open(): did not find any USB device "usb"
make: *** [program] Error 1
pinner:freem_a2 matt$ man avrdude
pinner:freem_a2 matt$ man avrdudecÇ
pinner:freem_a2 matt$ avrdude --help
avrdude: illegal option -- -
Usage: avrdude [options]
Options:
-p Required. Specify AVR device.
-b Override RS-232 baud rate.
-B Specify JTAG/STK500v2 bit clock period (us).
-C Specify location of configuration file.
-c Specify programmer type.
-D Disable auto erase for flash memory
-i ISP Clock Delay [in microseconds]
-P Specify connection port.
-F Override invalid signature check.
-e Perform a chip erase.
-O Perform RC oscillator calibration (see AVR053).
-U:r|w|v:[:format]
Memory operation specification.
Multiple -U options are allowed, each request
is performed in the order specified.
-n Do not write anything to the device.
-V Do not verify.
-u Disable safemode, default when running from a script.
-s Silent safemode operation, will not ask you if
fuses should be changed back.
-t Enter terminal mode.
-E[,] List programmer exit specifications.
-x Pass to programmer.
-y Count # erase cycles in EEPROM.
-Y Initialize erase cycle # in EEPROM.
-v Verbose output. -v -v for more.
-q Quell progress output. -q -q for less.
-? Display this usage.
avrdude version 5.8cvs, URL:
pinner:freem_a2 matt$ avrdude --list-programmers
avrdude: illegal option -- -
AVRDUDE(1) BSD General Commands Manual AVRDUDE(1)
NAME
avrdude -- driver program for ``simple'' Atmel AVR MCU programmer
SYNOPSIS
avrdude -p partno [-b baudrate] [-B bitclock] [-c programmer-id] [-C config-file] [-D] [-e] [-E exitspec[,exitspec]] [-F] [-i delay] [-n] [-O] [-P port] [-q] [-s]
[-t] [-u] [-U memtype:op:filename:filefmt] [-v] [-x extended_param] [-V] [-y] [-Y]
DESCRIPTION
Avrdude is a program for downloading code and data to Atmel AVR microcontrollers. Avrdude supports Atmel's STK500 programmer, Atmel's AVRISP and AVRISP mkII
devices, Atmel's STK600, Atmel's JTAG ICE (both mkI and mkII, the latter also in ISP mode), programmers complying to AppNote AVR910 and AVR109 (including the But-
terfly), as well as a simple hard-wired programmer connected directly to a ppi(4) or parport(4) parallel port, or to a standard serial port. In the simplest case,
the hardware consists just of a cable connecting the respective AVR signal lines to the parallel port.
The MCU is programmed in serial programming mode, so, for the ppi(4) based programmer, the MCU signals `/RESET', `SCK', `MISO' and `MOSI' need to be connected to
the parallel port. Optionally, some otherwise unused output pins of the parallel port can be used to supply power for the MCU part, so it is also possible to con-
struct a passive stand-alone programming device. Some status LEDs indicating the current operating state of the programmer can be connected, and a signal is avail-
able 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.
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.
Atmel's STK500 programmer is also supported and connects to a serial port. Both, firmware versions 1.x and 2.x can be handled, but require a different programmer
type specification (by now). Using firmware version 2, high-voltage programming is also supported, both parallel and serial (programmer types stk500pp and
stk500hvsp).
The Arduino (which is very similar to the STK500 1.x) is supported via its own programmer type specification ``arduino''.
The BusPirate is a versatile tool that can also be used as an AVR programmer. A single BusPirate can be connected to up to 3 independent AVRs. See the section on
extended parameters below for details.
...skipping...
realistic, assuming a constant system load while avrdude 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.
-n No-write - disables actually writing data to the MCU (useful for debugging avrdude ).
-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.
-P port
Use port to identify the device to which the programmer is attached. By default the /dev/ppi0 port is used, but if the programmer type normally con-
nects to the serial port, the /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.
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 `0x' ).
For the JTAG ICE mkII, if avrdude has been configured with libusb support, port can alternatively be specified as usb[:serialno]. This will cause
avrdude to search a JTAG ICE mkII on USB. If 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.
As the AVRISP mkII device can only be talked to over USB, the very same method of specifying the port is required there.
For the USB programmer "AVR-Doper" running in HID mode, the port must be specified as 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.
For programmers that attach to a serial port using some kind of higher level protocol (as opposed to bit-bang style programmers), port can be speci-
fied as net:host:port. In this case, instead of trying to open a local device, a TCP network connection to (TCP) port on 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. This feature is currently not implemented for Win32 systems.
...skipping...
comma-separated list of the values. This can be particularly useful for subsequent processing, like for fuse bit settings.
h hexadecimal; each value will get the string 0x prepended.
o octal; each value will get a 0 prepended unless it is less than 8 in which case it gets no prefix.
b binary; each value will get the string 0b prepended.
The default is to use auto detection for input files, and raw binary format for output files. Note that if filename contains a colon, the format
field is no longer optional since the filename part following the colon would otherwise be misinterpreted as format.
As an abbreviation, the form -U filename is equivalent to specifying -U flash:w:filename:a. This will only work if filename does not have a colon in
it.
-v Enable verbose output.
-V Disable automatic verify check when uploading data.
-x extended_param
Pass 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.
-y Tells avrdude to use the last four bytes of the connected parts' EEPROM memory to track the number of times the device has been erased. When this
option is used and the -e flag is specified to generate a chip erase, the previous counter will be saved before the chip erase, it is then incre-
mented, and written back after the erase cycle completes. Presumably, the device would only be erased just before being programmed, and thus, this
can be utilized to give an indication of how many erase-rewrite cycles the 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 1000 cycles. Of
course, if the application needs the last four bytes of EEPROM memory, this option should not be used.
-Y cycles
Instructs avrdude to initialize the erase-rewrite cycle counter residing at the last four bytes of EEPROM memory to the specified value. If the
application needs the last four bytes of EEPROM memory, this option should not be used.
Terminal mode
In this mode, avrdude 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 readline(3), so previously entered command lines can be recalled and edited. The
following commands are currently implemented:
dump memtype addr nbytes
Read nbytes bytes from the specified memory area, and display them in the usual hexadecimal and ASCII form.
dump Continue dumping the memory contents for another nbytes where the previous dump command left off.
write memtype addr byte1 ... byteN
Manually program the respective memory cells, starting at address addr, using the values byte1 through byteN. This feature is not implemented for
bank-addressed memories such as the flash memory of ATMega devices.
erase Perform a chip erase.
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 avrdude, this command
allows you to use it, even though avrdude does not implement the command. When using direct SPI mode, up to 3 bytes can be omitted.
...skipping...
Usage: avrdude [options]
# $Id: avrdude.conf.in 912 2010-01-13 17:34:18Z joerg_wunsch $
#
# AVRDUDE Configuration File
#
# This file contains configuration data used by AVRDUDE which describes
# the programming hardware pinouts and also provides part definitions.
# AVRDUDE's "-C" command line option specifies the location of the
# configuration file. The "-c" option names the programmer configuration
# which must match one of the entry's "id" parameter. The "-p" option
# identifies which part AVRDUDE is going to be programming and must match
# one of the parts' "id" parameter.
#
# Possible entry formats are:
#
# programmer
# id = [, [, ] ...] ; # are quoted strings
# desc = ; # quoted string
# type = par | stk500 | stk500v2 | stk500pp | stk500hvsp | stk500generic |
# stk600 | stk600pp | stk600hvsp |
# avr910 | butterfly | usbasp |
# jtagmki | jtagmkii | jtagmkii_isp | jtagmkii_dw |
# jtagmkII_avr32 | jtagmkii_pdi |
# dragon_dw | dragon_jtag | dragon_isp | dragon_pp |
# dragon_hvsp | dragon_pdi | arduino; # programmer type
# baudrate = ; # baudrate for avr910-programmer
# vcc = [, ... ] ; # pin number(s)
# reset = ; # pin number
# sck = ; # pin number
# mosi = ; # pin number
# miso = ; # pin number
# errled = ; # pin number
# rdyled = ; # pin number
# pgmled = ; # pin number
# vfyled = ; # pin number
# ;
#
# part
# id = ; # quoted string
# desc = ; # quoted string
# has_jtag = ; # part has JTAG i/f
# has_debugwire = ; # part has debugWire i/f
# devicecode = ; # deprecated, use stk500_devcode
# stk500_devcode = ; # numeric
# avr910_devcode = ; # numeric
# signature = ; # signature bytes
# chip_erase_delay = ; # micro-seconds
# reset = dedicated | io;
# retry_pulse = reset | sck;
# pgm_enable = ;
# chip_erase = ;
# chip_erase_delay = ; # chip erase delay (us)
# # STK500 parameters (parallel programming IO lines)
# pagel = ; # pin name in hex, i.e., 0xD7
# bs2 = ; # pin name in hex, i.e., 0xA0
# serial = ; # can use serial downloading
# parallel =; # can use par. programming
# # STK500v2 parameters, to be taken from Atmel's XML files
# timeout = ;
# stabdelay = ;
# cmdexedelay = ;
# synchloops = ;
# bytedelay = ;
# pollvalue = ;
# pollindex = ;
# predelay = ;
# postdelay = ;
# pollmethod = ;
# mode = ;
# delay = ;
# blocksize = ;
# readsize = ;
# hvspcmdexedelay = ;
# # STK500v2 HV programming parameters, from XML
# pp_controlstack =, , ...; # PP only
# hvsp_controlstack =, , ...; # HVSP only
# hventerstabdelay =;
# progmodedelay =; # PP only
# latchcycles =;
# togglevtg =;
# poweroffdelay =;
# resetdelayms =;
# resetdelayus =;
# hvleavestabdelay =;
# resetdelay =;
# synchcycles =; # HVSP only
# chiperasepulsewidth =; # PP only
# chiperasepolltimeout =;
# chiperasetime =; # HVSP only
# programfusepulsewidth =; # PP only
# programfusepolltimeout =;
# programlockpulsewidth =; # PP only
# programlockpolltimeout =;
# # JTAG ICE mkII parameters, also from XML files
# allowfullpagebitstream = ;
# enablepageprogramming = ;
# idr = ; # IO addr of IDR (OCD) reg.
# rampz = ; # IO addr of RAMPZ reg.
# spmcr = ; # mem addr of SPMC[S]R reg.
# eecr = ; # mem addr of EECR reg.
# # (only when != 0x3c)
# is_avr32 = ; # AVR32 part
#
# memory
# paged = ; # yes / no
# size = ; # bytes
# page_size = ; # bytes
# num_pages = ; # numeric
# min_write_delay = ; # micro-seconds
# max_write_delay = ; # micro-seconds
# readback_p1 = ; # byte value
# readback_p2 = ; # byte value
# pwroff_after_write = ; # yes / no
# read = ;
# write = ;
# read_lo = ;
# read_hi = ;
# write_lo = ;
# write_hi = ;
# loadpage_lo = ;
# loadpage_hi = ;
# writepage = ;
# ;
# ;
#
# If any of the above parameters are not specified, the default value
# of 0 is used for numerics or the empty string ("") for string
# values. If a required parameter is left empty, AVRDUDE will
# complain.
#
# NOTES:
# * 'devicecode' is the device code used by the STK500 (see codes
# listed below)
# * Not all memory types will implement all instructions.
# * AVR Fuse bits and Lock bits are implemented as a type of memory.
# * Example memory types are:
# "flash", "eeprom", "fuse", "lfuse" (low fuse), "hfuse" (high
# fuse), "signature", "calibration", "lock"
# * The memory type specified on the avrdude command line must match
# one of the memory types defined for the specified chip.
# * The pwroff_after_write flag causes avrdude to attempt to
# power the device off and back on after an unsuccessful write to
# the affected memory area if VCC programmer pins are defined. If
# VCC pins are not defined for the programmer, a message
# indicating that the device needs a power-cycle is printed out.
# This flag was added to work around a problem with the
# at90s4433/2333's; see the at90s4433 errata at:
#
# http://www.atmel.com/atmel/acrobat/doc1280.pdf
#
# INSTRUCTION FORMATS
#
# Instruction formats are specified as a comma seperated list of
# string values containing information (bit specifiers) about each
# of the 32 bits of the instruction. Bit specifiers may be one of
# the following formats:
#
# '1' = the bit is always set on input as well as output
#
# '0' = the bit is always clear on input as well as output
#
# 'x' = the bit is ignored on input and output
#
# 'a' = the bit is an address bit, the bit-number matches this bit
# specifier's position within the current instruction byte
#
# 'aN' = the bit is the Nth address bit, bit-number = N, i.e., a12
# is address bit 12 on input, a0 is address bit 0.
#
# 'i' = the bit is an input data bit
#
# 'o' = the bit is an output data bit
#
# Each instruction must be composed of 32 bit specifiers. The
# instruction specification closely follows the instruction data
# provided in Atmel's data sheets for their parts.
#
# See below for some examples.
#
#
# The following are STK500 part device codes to use for the
# "devicecode" field of the part. These came from Atmel's software
# section avr061.zip which accompanies the application note
# AVR061 available from:
#
# http://www.atmel.com/atmel/acrobat/doc2525.pdf
#
#define ATTINY10 0x10
#define ATTINY11 0x11
#define ATTINY12 0x12
#define ATTINY15 0x13
#define ATTINY13 0x14
#define ATTINY22 0x20
#define ATTINY26 0x21
#define ATTINY28 0x22
#define ATTINY2313 0x23
#define AT90S1200 0x33
#define AT90S2313 0x40
#define AT90S2323 0x41
#define AT90S2333 0x42
#define AT90S2343 0x43
#define AT90S4414 0x50
#define AT90S4433 0x51
#define AT90S4434 0x52
#define ATMEGA48 0x59
#define AT90S8515 0x60
#define AT90S8535 0x61
#define AT90C8534 0x62
#define ATMEGA8515 0x63
#define ATMEGA8535 0x64
#define ATMEGA8 0x70
#define ATMEGA88 0x73
#define ATMEGA168 0x86
#define ATMEGA161 0x80
#define ATMEGA163 0x81
#define ATMEGA16 0x82
#define ATMEGA162 0x83
#define ATMEGA169 0x84
#define ATMEGA323 0x90
#define ATMEGA32 0x91
#define ATMEGA64 0xA0
#define ATMEGA103 0xB1
#define ATMEGA128 0xB2
#define AT90CAN128 0xB3
#define AT90CAN64 0xB3
#define AT90CAN32 0xB3
#define AT86RF401 0xD0
#define AT89START 0xE0
#define AT89S51 0xE0
#define AT89S52 0xE1
# The following table lists the devices in the original AVR910
# appnote:
# |Device |Signature | Code |
# +-------+----------+------+
# |tiny12 | 1E 90 05 | 0x55 |
# |tiny15 | 1E 90 06 | 0x56 |
# | | | |
# | S1200 | 1E 90 01 | 0x13 |
# | | | |
# | S2313 | 1E 91 01 | 0x20 |
# | S2323 | 1E 91 02 | 0x48 |
# | S2333 | 1E 91 05 | 0x34 |
# | S2343 | 1E 91 03 | 0x4C |
# | | | |
# | S4414 | 1E 92 01 | 0x28 |
# | S4433 | 1E 92 03 | 0x30 |
# | S4434 | 1E 92 02 | 0x6C |
# | | | |
# | S8515 | 1E 93 01 | 0x38 |
# | S8535 | 1E 93 03 | 0x68 |
# | | | |
# |mega32 | 1E 95 01 | 0x72 |
# |mega83 | 1E 93 05 | 0x65 |
# |mega103| 1E 97 01 | 0x41 |
# |mega161| 1E 94 01 | 0x60 |
# |mega163| 1E 94 02 | 0x64 |
# Appnote AVR109 also has a table of AVR910 device codes, which
# lists:
# dev avr910 signature
# ATmega8 0x77 0x1E 0x93 0x07
# ATmega8515 0x3B 0x1E 0x93 0x06
# ATmega8535 0x6A 0x1E 0x93 0x08
# ATmega16 0x75 0x1E 0x94 0x03
# ATmega162 0x63 0x1E 0x94 0x04
# ATmega163 0x66 0x1E 0x94 0x02
# ATmega169 0x79 0x1E 0x94 0x05
# ATmega32 0x7F 0x1E 0x95 0x02
# ATmega323 0x73 0x1E 0x95 0x01
# ATmega64 0x46 0x1E 0x96 0x02
# ATmega128 0x44 0x1E 0x97 0x02
#
# These codes refer to "BOOT" device codes which are apparently
# different than standard device codes, for whatever reasons
# (often one above the standard code).
# There are several extended versions of AVR910 implementations around
# in the Internet. These add the following codes (only devices that
# actually exist are listed):
# ATmega8515 0x3A
# ATmega128 0x43
# ATmega64 0x45
# ATtiny26 0x5E
# ATmega8535 0x69
# ATmega32 0x72
# ATmega16 0x74
# ATmega8 0x76
# ATmega169 0x78
#
# Overall avrdude defaults
#
default_parallel = "unknown";
default_serial = "unknown";
#
# PROGRAMMER DEFINITIONS
#
programmer
id = "arduino";
desc = "Arduino";
type = arduino;
;
programmer
id = "avrisp";
desc = "Atmel AVR ISP";
type = stk500;
;
programmer
id = "avrispv2";
desc = "Atmel AVR ISP V2";
type = stk500v2;
...skipping...
id = "dragon_jtag";
desc = "Atmel AVR Dragon in JTAG mode";
baudrate = 115200;
type = dragon_jtag;
;
# AVR Dragon in ISP mode
programmer
id = "dragon_isp";
desc = "Atmel AVR Dragon in ISP mode";
baudrate = 115200;
type = dragon_isp;
;
# AVR Dragon in PP mode
programmer
id = "dragon_pp";
desc = "Atmel AVR Dragon in PP mode";
baudrate = 115200;
type = dragon_pp;
;
# AVR Dragon in HVSP mode
programmer
id = "dragon_hvsp";
desc = "Atmel AVR Dragon in HVSP mode";
baudrate = 115200;
type = dragon_hvsp;
;
# AVR Dragon in debugWire mode
programmer
id = "dragon_dw";
desc = "Atmel AVR Dragon in debugWire mode";
baudrate = 115200;
type = dragon_dw;
;
# AVR Dragon in PDI mode
programmer
id = "dragon_pdi";
desc = "Atmel AVR Dragon in PDI mode";
baudrate = 115200;
#define ATMEGA161 0x80
#define ATMEGA163 0x81
#define ATMEGA16 0x82
#define ATMEGA162 0x83
#define ATMEGA169 0x84
#define ATMEGA323 0x90
#define ATMEGA32 0x91
#define ATMEGA64 0xA0
#define ATMEGA103 0xB1
#define ATMEGA128 0xB2
#define AT90CAN128 0xB3
#define AT90CAN64 0xB3
#define AT90CAN32 0xB3
#define AT86RF401 0xD0
#define AT89START 0xE0
#define AT89S51 0xE0
#define AT89S52 0xE1
# The following table lists the devices in the original AVR910
# appnote:
# |Device |Signature | Code |
# +-------+----------+------+
# |tiny12 | 1E 90 05 | 0x55 |
# |tiny15 | 1E 90 06 | 0x56 |
# | | | |
# | S1200 | 1E 90 01 | 0x13 |
# | | | |
# | S2313 | 1E 91 01 | 0x20 |
...skipping...
id = "dragon_jtag";
desc = "Atmel AVR Dragon in JTAG mode";
baudrate = 115200;
baudrate = 115200;
type = jtagmkii_dw;
;
# JTAG ICE mkII in AVR32 mode
programmer
id = "jtagmkII_avr32";
desc = "Atmel JTAG ICE mkII im AVR32 mode";
baudrate = 115200;
type = jtagmkii_avr32;
;
# JTAG ICE mkII in AVR32 mode
programmer
id = "jtag2avr32";
desc = "Atmel JTAG ICE mkII im AVR32 mode";
baudrate = 115200;
Options:
-p Required. Specify AVR device.
-b Override RS-232 baud rate.
-B Specify JTAG/STK500v2 bit clock period (us).
-C Specify location of configuration file.
-c Specify programmer type.
-D Disable auto erase for flash memory
-i ISP Clock Delay [in microseconds]
-P Specify connection port.
-F Override invalid signature check.
-e Perform a chip erase.
-O Perform RC oscillator calibration (see AVR053).
-U:r|w|v:[:format]
Memory operation specification.
Multiple -U options are allowed, each request
is performed in the order specified.
-n Do not write anything to the device.
-V Do not verify.
-u Disable safemode, default when running from a script.
-s Silent safemode operation, will not ask you if
fuses should be changed back.
-t Enter terminal mode.
-E[,] List programmer exit specifications.
-x Pass to programmer.
-y Count # erase cycles in EEPROM.
-Y Initialize erase cycle # in EEPROM.
-v Verbose output. -v -v for more.
-q Quell progress output. -q -q for less.
-? Display this usage.
avrdude version 5.8cvs, URL:
pinner:freem_a2 matt$ man avrdude
pinner:freem_a2 matt$ less /usr/local/CrossPack-AVR/etc/avrdude.conf
pinner:freem_a2 matt$ ls
Makefile freem_a2.eep freem_a2.hex freem_a2.map i2cmaster_bitbang.c softuart.h
freem_a2.c freem_a2.elf freem_a2.lss freem_a2_20100527.hex irsony.c
pinner:freem_a2 matt$ emacs Makawk: can't open file /opt/local/etc/bash_completion
source line number 1
efile
pinner:freem_a2 matt$ man avrdude
pinner:freem_a2 matt$ emacs Makefile
[2]+ Stopped emacs Makefile
pinner:freem_a2 matt$ make program
avrdude -p attiny45 -P usb -c dragon_isp -v -v -e -U flash:w:freem_a2.hex -U eeprom:w:freem_a2.eep
avrdude: Version 5.8cvs, compiled on Jan 15 2010 at 17:27:01
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is "/usr/local/CrossPack-AVR-20100115/etc/avrdude.conf"
User configuration file is "/Users/matt/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
Using Port : usb
Using Programmer : dragon_isp
avrdude: stk500v2_dragon_isp_open()
avrdude: usbdev_open(): did not find any USB device "usb"
make: *** [program] Error 1
pinner:freem_a2 matt$ make program
avrdude -p attiny45 -P usb -c dragon_isp -v -v -e -U flash:w:freem_a2.hex -U eeprom:w:freem_a2.eep
avrdude: Version 5.8cvs, compiled on Jan 15 2010 at 17:27:01
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is "/usr/local/CrossPack-AVR-20100115/etc/avrdude.conf"
User configuration file is "/Users/matt/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
Using Port : usb
Using Programmer : dragon_isp
avrdude: stk500v2_dragon_isp_open()
avrdude: usbdev_open(): did not find any USB device "usb"
make: *** [program] Error 1
pinner:freem_a2 matt$
pinner:freem_a2 matt$
pinner:freem_a2 matt$
AVRDUDE(1) BSD General Commands Manual AVRDUDE(1)
NAME
avrdude -- driver program for ``simple'' Atmel AVR MCU programmer
SYNOPSIS
avrdude -p partno [-b baudrate] [-B bitclock] [-c programmer-id] [-C config-file] [-D] [-e] [-E exitspec[,exitspec]] [-F] [-i delay] [-n] [-O] [-P port] [-q] [-s]
[-t] [-u] [-U memtype:op:filename:filefmt] [-v] [-x extended_param] [-V] [-y] [-Y]
DESCRIPTION
Avrdude is a program for downloading code and data to Atmel AVR microcontrollers. Avrdude supports Atmel's STK500 programmer, Atmel's AVRISP and AVRISP mkII
devices, Atmel's STK600, Atmel's JTAG ICE (both mkI and mkII, the latter also in ISP mode), programmers complying to AppNote AVR910 and AVR109 (including the But-
terfly), as well as a simple hard-wired programmer connected directly to a ppi(4) or parport(4) parallel port, or to a standard serial port. In the simplest case,
the hardware consists just of a cable connecting the respective AVR signal lines to the parallel port.
The MCU is programmed in serial programming mode, so, for the ppi(4) based programmer, the MCU signals `/RESET', `SCK', `MISO' and `MOSI' need to be connected to
the parallel port. Optionally, some otherwise unused output pins of the parallel port can be used to supply power for the MCU part, so it is also possible to con-
struct a passive stand-alone programming device. Some status LEDs indicating the current operating state of the programmer can be connected, and a signal is avail-
able 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.
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.
Atmel's STK500 programmer is also supported and connects to a serial port. Both, firmware versions 1.x and 2.x can be handled, but require a different programmer
type specification (by now). Using firmware version 2, high-voltage programming is also supported, both parallel and serial (programmer types stk500pp and
stk500hvsp).
The Arduino (which is very similar to the STK500 1.x) is supported via its own programmer type specification ``arduino''.
The BusPirate is a versatile tool that can also be used as an AVR programmer. A single BusPirate can be connected to up to 3 independent AVRs. See the section on
extended parameters below for details.
...skipping...
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 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 -B bitclock option
might be required to achieve a stable ISP communication.
The USBasp ISP and USBtinyISP adapters are also supported, provided avrdude has been compiled with libusb support. They both feature simple firwmare-only USB
implementations, running on an ATmega8 (or ATmega88), or ATtiny2313, respectively.
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 asl(1) as a standalone assembler, or avr-objcopy(1) for
the final stage of the GNU toolchain for the AVR microcontroller.
Avrdude 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 avrdude as separate memory types and can be programmed using data from a file (see the -m option) or from terminal
mode (see the dump and 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 interactively communicate with the MCU, and to display or program individual memory cells. On
the STK500 and STK600 programmer, several operational parameters (target supply voltage, target Aref voltage, master clock) can be examined and changed from within
terminal mode as well.
Options
In order to control all the different operation modi, a number of options need to be specified to avrdude.
-p partno
This is the only option that is mandatory for every invocation of avrdude. It specifies the type of the MCU connected to the programmer. These are
read from the config file. If avrdude 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:
Option tag Official part name
c128 AT90CAN128
pwm2 AT90PWM2
pwm3 AT90PWM3
1200 AT90S1200
2313 AT90S2313
2333 AT90S2333
...skipping...
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 tar-
get 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.
Programmers accepting extended parameters
JTAG ICE mkII
AVR Dragon
When using the JTAG ICE mkII or AVR Dragon in JTAG mode, the following extended parameter is accepted:
jtagchain=UB,UA,BB,BA
Setup the JTAG scan chain for UB units before, UA units after, BB bits before, and 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.
AVR910
devcode=VALUE
Override the device code selection by using VALUE as the device code. The programmer is not queried for the list of supported device
codes, and the specified VALUE is not verified but used directly within the `T' command sent to the programmer. VALUE can be specified
using the conventional number notation of the C programming language.
no_blockmode
Disables the default checking for block transfer capability. Use no_blockmode only if your AVR910 programmer creates errors during ini-
tial sequence.
buspirate
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 con-
nected to BusPirate's CS pin, second AVR's RESET connected to BusPirate's AUX pin and if your BusPirate has an AUX2 pin (only available
on BusPirate version v1a with firmware 3.0 or newer) use that to activate RESET on the third AVR.
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.
speed=<0..7>
BusPirate to AVR SPI speed:
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
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 have BinMode or their BinMode is buggy. ASCII mode is slower and makes the above reset= and speed= parameters unavailable.
FILES
/dev/ppi0 default device to be used for communication with the programming hardware
${PREFIX}/etc/avrdude.conf
programmer and parts configuration file
${HOME}/.avrduderc
programmer and parts configuration file (per-user overrides)
~/.inputrc Initialization file for the readline(3) library
${PREFIX}/share/doc/avrdude/avrdude.pdf
Schematic of programming hardware
DIAGNOSTICS
avrdude: jtagmkII_setparm(): bad response to set parameter command: RSP_FAILED
avrdude: jtagmkII_getsync(): ISP activation failed, trying debugWire
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.
Atmel's STK500 programmer is also supported and connects to a serial port. Both, firmware versions 1.x and 2.x can be handled, but require a different programmer
type specification (by now). Using firmware version 2, high-voltage programming is also supported, both parallel and serial (programmer types stk500pp and
stk500hvsp).
The Arduino (which is very similar to the STK500 1.x) is supported via its own programmer type specification ``arduino''.
The BusPirate is a versatile tool that can also be used as an AVR programmer. A single BusPirate can be connected to up to 3 independent AVRs. See the section on
extended parameters below for details.
Atmel's STK600 programmer is supported in ISP and high-voltage programming modes, and connects through the USB. For ATxmega devices, the STK600 is supported in PDI
mode.
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.
Atmel's JTAG ICE (both mkI and mkII) is supported as well to up- or download memory areas from/to an AVR target (no support for on-chip debugging). For the JTAG
ICE mkII, JTAG, debugWire and ISP mode are supported. See below for the limitations of debugWire.
The AVR Dragon is supported in all modes (ISP, JTAG, HVSP, PP, debugWire). When used in JTAG and debugWire mode, the AVR Dragon behaves similar to a 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 -B bitclock option
might be required to achieve a stable ISP communication.
The USBasp ISP and USBtinyISP adapters are also supported, provided avrdude has been compiled with libusb support. They both feature simple firwmare-only USB
implementations, running on an ATmega8 (or ATmega88), or ATtiny2313, respectively.
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 asl(1) as a standalone assembler, or avr-objcopy(1) for
the final stage of the GNU toolchain for the AVR microcontroller.
Avrdude 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 avrdude as separate memory types and can be programmed using data from a file (see the -m option) or from terminal
mode (see the dump and 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 interactively communicate with the MCU, and to display or program individual memory cells. On
the STK500 and STK600 programmer, several operational parameters (target supply voltage, target Aref voltage, master clock) can be examined and changed from within
terminal mode as well.
Options
In order to control all the different operation modi, a number of options need to be specified to avrdude.
-p partno
This is the only option that is mandatory for every invocation of avrdude. It specifies the type of the MCU connected to the programmer. These are
read from the config file. If avrdude 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:
Option tag Official part name
c128 AT90CAN128
pwm2 AT90PWM2
pwm3 AT90PWM3
1200 AT90S1200
2313 AT90S2313
2333 AT90S2333
2343 AT90S2343 (*)
4414 AT90S4414
4433 AT90S4433
4434 AT90S4434
8515 AT90S8515
8535 AT90S8535
m103 ATmega103
m128 ATmega128
m1280 ATmega1280
m1281 ATmega1281
m1284p ATmega1284P
m128rfa1 ATmega128RFA1
m16 ATmega16
m161 ATmega161
m162 ATmega162
m163 ATmega163
m164 ATmega164
m169 ATmega169
m2560 ATmega2560 (**)
m2561 ATmega2561 (**)
m32 ATmega32
m324 ATmega324
m329 ATmega329
m3290 ATmega3290
m48 ATmega48
m64 ATmega64
m640 ATmega640
m644 ATmega644
m649 ATmega649
m6490 ATmega6490
m8 ATmega8
m8515 ATmega8515
m8535 ATmega8535
m88 ATmega88
t12 ATtiny12
t13 ATtiny13
t15 ATtiny15
t2313 ATtiny2313
t25 ATtiny25
t26 ATtiny26
t45 ATtiny45
t85 ATtiny85
ucr2 AT32uca0512
x128a1 ATxmega128A1
x128a1d ATxmega128A1revD
(*) The AT90S2323 and ATtiny22 use the same algorithm.
(**) Flash addressing above 128 KB is not supported by all programming hardware. Known to work are jtag2, stk500v2, and bit-bang programmers.
-b baudrate
Override the RS-232 connection baud rate specified in the respective programmer's entry of the configuration file.
-B bitclock
Specify the bit clock period for the JTAG interface or the ISP clock (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 cer-
tain 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.
-c programmer-id
Use the pin configuration specified by the argument. Pin configurations are read from the config file (see the -C option). New pin configurations
can be easily added or modified through the use of a config file to make avrdude work with different programmers as long as the programmer supports
the Atmel AVR serial program method. You can use the 'default_programmer' keyword in your ${HOME}/.avrduderc file to assign a default programmer to
keep from having to specify this option on every invocation.
-C config-file
Use the specified config file to load configuration data. This file contains all programmer and part definitions that avrdude knows about. If you
have a programmer or part that avrdude 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 the next version). See the config file, located at ${PREFIX}/etc/avrdude.conf, which contains a description of the format.
-D Disable auto erase for flash. When the -U option with flash memory is specified, avrdude will perform a chip erase before starting any of the pro-
gramming operations, since it generally is a mistake to program the flash without performing an erase first. This option disables that. 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.
-e Causes a chip erase to be executed. This will reset the contents of the flash ROM and EEPROM to the value `0xff', 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 reprogrammed again. The only excep-
tion would be if the new contents would exclusively cause bits to be programmed from the value `1' to `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.
-E exitspec[,exitspec]
By default, avrdude leaves the parallel port in the same state at exit as it has been found at startup. This option modifies the state of the
`/RESET' and `Vcc' lines the parallel port is left at, according to the exitspec arguments provided, as follows:
reset The `/RESET' signal will be left activated at program exit, that is it will be held 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 `/RESET' signal is active before powering up the
MCU, so in case an external power supply is used for this MCU type, a previous invocation of avrdude with this option specified is one of the
possible ways to guarantee this condition.
noreset The `/RESET' line will be deactivated at program exit, thus allowing the MCU target program to run while the programming hardware remains
connected.
vcc This option will leave those parallel port pins active (i. e. high) that can be used to supply `Vcc' power to the MCU.
novcc This option will pull the `Vcc' pins of the parallel port down at program exit.
Multiple exitspec arguments can be separated with commas.
-F Normally, avrdude 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. 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 -t to continue in terminal mode.
-i delay
For bitbang-type programmers, delay for approximately delay microseconds between each bit state change. If the host system is very fast, or the tar-
get 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
pinner:freem_a2 matt$ ls -last
total 296
0 drwxr-xr-x 14 matt staff 476 Aug 3 22:00 .
8 -rw-r--r-- 1 matt staff 13 Aug 3 22:00 freem_a2.eep
40 -rwxr-xr-x 1 matt staff 17633 Aug 3 21:57 freem_a2.elf
16 -rw-r--r-- 1 matt staff 6874 Aug 3 21:57 freem_a2.hex
120 -rw-r--r-- 1 matt staff 59931 Aug 3 21:57 freem_a2.lss
32 -rw-r--r-- 1 matt staff 13603 Aug 3 21:57 freem_a2.map
0 drwxr-xr-x 5 matt staff 170 Jul 13 16:41 ..
0 drwxr-xr-x 8 matt staff 272 Jul 13 16:41 .svn
8 -rw-r--r-- 1 matt staff 3250 Jul 13 16:41 Makefile
32 -rw-r--r-- 1 matt staff 13212 Jul 13 16:41 freem_a2.c
16 -rw-r--r-- 1 matt staff 7029 Jul 13 16:41 freem_a2_20100527.hex
8 -rw-r--r-- 1 matt staff 2708 Jul 13 16:41 i2cmaster_bitbang.c
8 -rw-r--r-- 1 matt staff 3738 Jul 13 16:41 irsony.c
8 -rw-r--r-- 1 matt staff 1807 Jul 13 16:41 softuart.h
pinner:freem_a2 matt$ make program
avrdude -p attiny45 -P usb -c avrispmkII -v -v -e -U flash:w:freem_a2.hex -U eeprom:w:freem_a2.eep
avrdude: Version 5.8cvs, compiled on Jan 15 2010 at 17:27:01
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is "/usr/local/CrossPack-AVR-20100115/etc/avrdude.conf"
User configuration file is "/Users/matt/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
Using Port : usb
Using Programmer : avrispmkII
avrdude: usbdev_open(): did not find any USB device "usb"
make: *** [program] Error 1
pinner:freem_a2 matt$ man avrdude
pinner:freem_a2 matt$ man avrdudecÇ
pinner:freem_a2 matt$ avrdude --help
avrdude: illegal option -- -
Usage: avrdude [options]
Options:
-p
-b
-B
-C
-c
-D Disable auto erase for flash memory
-i
-P
-F Override invalid signature check.
-e Perform a chip erase.
-O Perform RC oscillator calibration (see AVR053).
-U
Memory operation specification.
Multiple -U options are allowed, each request
is performed in the order specified.
-n Do not write anything to the device.
-V Do not verify.
-u Disable safemode, default when running from a script.
-s Silent safemode operation, will not ask you if
fuses should be changed back.
-t Enter terminal mode.
-E
-x
-y Count # erase cycles in EEPROM.
-Y
-v Verbose output. -v -v for more.
-q Quell progress output. -q -q for less.
-? Display this usage.
avrdude version 5.8cvs, URL:
pinner:freem_a2 matt$ avrdude --list-programmers
avrdude: illegal option -- -
AVRDUDE(1) BSD General Commands Manual AVRDUDE(1)
NAME
avrdude -- driver program for ``simple'' Atmel AVR MCU programmer
SYNOPSIS
avrdude -p partno [-b baudrate] [-B bitclock] [-c programmer-id] [-C config-file] [-D] [-e] [-E exitspec[,exitspec]] [-F] [-i delay] [-n] [-O] [-P port] [-q] [-s]
[-t] [-u] [-U memtype:op:filename:filefmt] [-v] [-x extended_param] [-V] [-y] [-Y]
DESCRIPTION
Avrdude is a program for downloading code and data to Atmel AVR microcontrollers. Avrdude supports Atmel's STK500 programmer, Atmel's AVRISP and AVRISP mkII
devices, Atmel's STK600, Atmel's JTAG ICE (both mkI and mkII, the latter also in ISP mode), programmers complying to AppNote AVR910 and AVR109 (including the But-
terfly), as well as a simple hard-wired programmer connected directly to a ppi(4) or parport(4) parallel port, or to a standard serial port. In the simplest case,
the hardware consists just of a cable connecting the respective AVR signal lines to the parallel port.
The MCU is programmed in serial programming mode, so, for the ppi(4) based programmer, the MCU signals `/RESET', `SCK', `MISO' and `MOSI' need to be connected to
the parallel port. Optionally, some otherwise unused output pins of the parallel port can be used to supply power for the MCU part, so it is also possible to con-
struct a passive stand-alone programming device. Some status LEDs indicating the current operating state of the programmer can be connected, and a signal is avail-
able 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.
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.
Atmel's STK500 programmer is also supported and connects to a serial port. Both, firmware versions 1.x and 2.x can be handled, but require a different programmer
type specification (by now). Using firmware version 2, high-voltage programming is also supported, both parallel and serial (programmer types stk500pp and
stk500hvsp).
The Arduino (which is very similar to the STK500 1.x) is supported via its own programmer type specification ``arduino''.
The BusPirate is a versatile tool that can also be used as an AVR programmer. A single BusPirate can be connected to up to 3 independent AVRs. See the section on
extended parameters below for details.
...skipping...
realistic, assuming a constant system load while avrdude 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.
-n No-write - disables actually writing data to the MCU (useful for debugging avrdude ).
-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.
-P port
Use port to identify the device to which the programmer is attached. By default the /dev/ppi0 port is used, but if the programmer type normally con-
nects to the serial port, the /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.
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 `0x' ).
For the JTAG ICE mkII, if avrdude has been configured with libusb support, port can alternatively be specified as usb[:serialno]. This will cause
avrdude to search a JTAG ICE mkII on USB. If 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.
As the AVRISP mkII device can only be talked to over USB, the very same method of specifying the port is required there.
For the USB programmer "AVR-Doper" running in HID mode, the port must be specified as 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.
For programmers that attach to a serial port using some kind of higher level protocol (as opposed to bit-bang style programmers), port can be speci-
fied as net:host:port. In this case, instead of trying to open a local device, a TCP network connection to (TCP) port on 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. This feature is currently not implemented for Win32 systems.
...skipping...
comma-separated list of the values. This can be particularly useful for subsequent processing, like for fuse bit settings.
h hexadecimal; each value will get the string 0x prepended.
o octal; each value will get a 0 prepended unless it is less than 8 in which case it gets no prefix.
b binary; each value will get the string 0b prepended.
The default is to use auto detection for input files, and raw binary format for output files. Note that if filename contains a colon, the format
field is no longer optional since the filename part following the colon would otherwise be misinterpreted as format.
As an abbreviation, the form -U filename is equivalent to specifying -U flash:w:filename:a. This will only work if filename does not have a colon in
it.
-v Enable verbose output.
-V Disable automatic verify check when uploading data.
-x extended_param
Pass 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.
-y Tells avrdude to use the last four bytes of the connected parts' EEPROM memory to track the number of times the device has been erased. When this
option is used and the -e flag is specified to generate a chip erase, the previous counter will be saved before the chip erase, it is then incre-
mented, and written back after the erase cycle completes. Presumably, the device would only be erased just before being programmed, and thus, this
can be utilized to give an indication of how many erase-rewrite cycles the 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 1000 cycles. Of
course, if the application needs the last four bytes of EEPROM memory, this option should not be used.
-Y cycles
Instructs avrdude to initialize the erase-rewrite cycle counter residing at the last four bytes of EEPROM memory to the specified value. If the
application needs the last four bytes of EEPROM memory, this option should not be used.
Terminal mode
In this mode, avrdude 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 readline(3), so previously entered command lines can be recalled and edited. The
following commands are currently implemented:
dump memtype addr nbytes
Read nbytes bytes from the specified memory area, and display them in the usual hexadecimal and ASCII form.
dump Continue dumping the memory contents for another nbytes where the previous dump command left off.
write memtype addr byte1 ... byteN
Manually program the respective memory cells, starting at address addr, using the values byte1 through byteN. This feature is not implemented for
bank-addressed memories such as the flash memory of ATMega devices.
erase Perform a chip erase.
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 avrdude, this command
allows you to use it, even though avrdude does not implement the command. When using direct SPI mode, up to 3 bytes can be omitted.
...skipping...
Usage: avrdude [options]
# $Id: avrdude.conf.in 912 2010-01-13 17:34:18Z joerg_wunsch $
#
# AVRDUDE Configuration File
#
# This file contains configuration data used by AVRDUDE which describes
# the programming hardware pinouts and also provides part definitions.
# AVRDUDE's "-C" command line option specifies the location of the
# configuration file. The "-c" option names the programmer configuration
# which must match one of the entry's "id" parameter. The "-p" option
# identifies which part AVRDUDE is going to be programming and must match
# one of the parts' "id" parameter.
#
# Possible entry formats are:
#
# programmer
# id =
# desc =
# type = par | stk500 | stk500v2 | stk500pp | stk500hvsp | stk500generic |
# stk600 | stk600pp | stk600hvsp |
# avr910 | butterfly | usbasp |
# jtagmki | jtagmkii | jtagmkii_isp | jtagmkii_dw |
# jtagmkII_avr32 | jtagmkii_pdi |
# dragon_dw | dragon_jtag | dragon_isp | dragon_pp |
# dragon_hvsp | dragon_pdi | arduino; # programmer type
# baudrate =
# vcc =
# reset =
# sck =
# mosi =
# miso =
# errled =
# rdyled =
# pgmled =
# vfyled =
# ;
#
# part
# id =
# desc =
# has_jtag =
# has_debugwire =
# devicecode =
# stk500_devcode =
# avr910_devcode =
# signature =
# chip_erase_delay =
# reset = dedicated | io;
# retry_pulse = reset | sck;
# pgm_enable =
# chip_erase =
# chip_erase_delay =
# # STK500 parameters (parallel programming IO lines)
# pagel =
# bs2 =
# serial =
# parallel =
# # STK500v2 parameters, to be taken from Atmel's XML files
# timeout =
# stabdelay =
# cmdexedelay =
# synchloops =
# bytedelay =
# pollvalue =
# pollindex =
# predelay =
# postdelay =
# pollmethod =
# mode =
# delay =
# blocksize =
# readsize =
# hvspcmdexedelay =
# # STK500v2 HV programming parameters, from XML
# pp_controlstack =
# hvsp_controlstack =
# hventerstabdelay =
# progmodedelay =
# latchcycles =
# togglevtg =
# poweroffdelay =
# resetdelayms =
# resetdelayus =
# hvleavestabdelay =
# resetdelay =
# synchcycles =
# chiperasepulsewidth =
# chiperasepolltimeout =
# chiperasetime =
# programfusepulsewidth =
# programfusepolltimeout =
# programlockpulsewidth =
# programlockpolltimeout =
# # JTAG ICE mkII parameters, also from XML files
# allowfullpagebitstream =
# enablepageprogramming =
# idr =
# rampz =
# spmcr =
# eecr =
# # (only when != 0x3c)
# is_avr32 =
#
# memory
# paged =
# size =
# page_size =
# num_pages =
# min_write_delay =
# max_write_delay =
# readback_p1 =
# readback_p2 =
# pwroff_after_write =
# read =
# write =
# read_lo =
# read_hi =
# write_lo =
# write_hi =
# loadpage_lo =
# loadpage_hi =
# writepage =
# ;
# ;
#
# If any of the above parameters are not specified, the default value
# of 0 is used for numerics or the empty string ("") for string
# values. If a required parameter is left empty, AVRDUDE will
# complain.
#
# NOTES:
# * 'devicecode' is the device code used by the STK500 (see codes
# listed below)
# * Not all memory types will implement all instructions.
# * AVR Fuse bits and Lock bits are implemented as a type of memory.
# * Example memory types are:
# "flash", "eeprom", "fuse", "lfuse" (low fuse), "hfuse" (high
# fuse), "signature", "calibration", "lock"
# * The memory type specified on the avrdude command line must match
# one of the memory types defined for the specified chip.
# * The pwroff_after_write flag causes avrdude to attempt to
# power the device off and back on after an unsuccessful write to
# the affected memory area if VCC programmer pins are defined. If
# VCC pins are not defined for the programmer, a message
# indicating that the device needs a power-cycle is printed out.
# This flag was added to work around a problem with the
# at90s4433/2333's; see the at90s4433 errata at:
#
# http://www.atmel.com/atmel/acrobat/doc1280.pdf
#
# INSTRUCTION FORMATS
#
# Instruction formats are specified as a comma seperated list of
# string values containing information (bit specifiers) about each
# of the 32 bits of the instruction. Bit specifiers may be one of
# the following formats:
#
# '1' = the bit is always set on input as well as output
#
# '0' = the bit is always clear on input as well as output
#
# 'x' = the bit is ignored on input and output
#
# 'a' = the bit is an address bit, the bit-number matches this bit
# specifier's position within the current instruction byte
#
# 'aN' = the bit is the Nth address bit, bit-number = N, i.e., a12
# is address bit 12 on input, a0 is address bit 0.
#
# 'i' = the bit is an input data bit
#
# 'o' = the bit is an output data bit
#
# Each instruction must be composed of 32 bit specifiers. The
# instruction specification closely follows the instruction data
# provided in Atmel's data sheets for their parts.
#
# See below for some examples.
#
#
# The following are STK500 part device codes to use for the
# "devicecode" field of the part. These came from Atmel's software
# section avr061.zip which accompanies the application note
# AVR061 available from:
#
# http://www.atmel.com/atmel/acrobat/doc2525.pdf
#
#define ATTINY10 0x10
#define ATTINY11 0x11
#define ATTINY12 0x12
#define ATTINY15 0x13
#define ATTINY13 0x14
#define ATTINY22 0x20
#define ATTINY26 0x21
#define ATTINY28 0x22
#define ATTINY2313 0x23
#define AT90S1200 0x33
#define AT90S2313 0x40
#define AT90S2323 0x41
#define AT90S2333 0x42
#define AT90S2343 0x43
#define AT90S4414 0x50
#define AT90S4433 0x51
#define AT90S4434 0x52
#define ATMEGA48 0x59
#define AT90S8515 0x60
#define AT90S8535 0x61
#define AT90C8534 0x62
#define ATMEGA8515 0x63
#define ATMEGA8535 0x64
#define ATMEGA8 0x70
#define ATMEGA88 0x73
#define ATMEGA168 0x86
#define ATMEGA161 0x80
#define ATMEGA163 0x81
#define ATMEGA16 0x82
#define ATMEGA162 0x83
#define ATMEGA169 0x84
#define ATMEGA323 0x90
#define ATMEGA32 0x91
#define ATMEGA64 0xA0
#define ATMEGA103 0xB1
#define ATMEGA128 0xB2
#define AT90CAN128 0xB3
#define AT90CAN64 0xB3
#define AT90CAN32 0xB3
#define AT86RF401 0xD0
#define AT89START 0xE0
#define AT89S51 0xE0
#define AT89S52 0xE1
# The following table lists the devices in the original AVR910
# appnote:
# |Device |Signature | Code |
# +-------+----------+------+
# |tiny12 | 1E 90 05 | 0x55 |
# |tiny15 | 1E 90 06 | 0x56 |
# | | | |
# | S1200 | 1E 90 01 | 0x13 |
# | | | |
# | S2313 | 1E 91 01 | 0x20 |
# | S2323 | 1E 91 02 | 0x48 |
# | S2333 | 1E 91 05 | 0x34 |
# | S2343 | 1E 91 03 | 0x4C |
# | | | |
# | S4414 | 1E 92 01 | 0x28 |
# | S4433 | 1E 92 03 | 0x30 |
# | S4434 | 1E 92 02 | 0x6C |
# | | | |
# | S8515 | 1E 93 01 | 0x38 |
# | S8535 | 1E 93 03 | 0x68 |
# | | | |
# |mega32 | 1E 95 01 | 0x72 |
# |mega83 | 1E 93 05 | 0x65 |
# |mega103| 1E 97 01 | 0x41 |
# |mega161| 1E 94 01 | 0x60 |
# |mega163| 1E 94 02 | 0x64 |
# Appnote AVR109 also has a table of AVR910 device codes, which
# lists:
# dev avr910 signature
# ATmega8 0x77 0x1E 0x93 0x07
# ATmega8515 0x3B 0x1E 0x93 0x06
# ATmega8535 0x6A 0x1E 0x93 0x08
# ATmega16 0x75 0x1E 0x94 0x03
# ATmega162 0x63 0x1E 0x94 0x04
# ATmega163 0x66 0x1E 0x94 0x02
# ATmega169 0x79 0x1E 0x94 0x05
# ATmega32 0x7F 0x1E 0x95 0x02
# ATmega323 0x73 0x1E 0x95 0x01
# ATmega64 0x46 0x1E 0x96 0x02
# ATmega128 0x44 0x1E 0x97 0x02
#
# These codes refer to "BOOT" device codes which are apparently
# different than standard device codes, for whatever reasons
# (often one above the standard code).
# There are several extended versions of AVR910 implementations around
# in the Internet. These add the following codes (only devices that
# actually exist are listed):
# ATmega8515 0x3A
# ATmega128 0x43
# ATmega64 0x45
# ATtiny26 0x5E
# ATmega8535 0x69
# ATmega32 0x72
# ATmega16 0x74
# ATmega8 0x76
# ATmega169 0x78
#
# Overall avrdude defaults
#
default_parallel = "unknown";
default_serial = "unknown";
#
# PROGRAMMER DEFINITIONS
#
programmer
id = "arduino";
desc = "Arduino";
type = arduino;
;
programmer
id = "avrisp";
desc = "Atmel AVR ISP";
type = stk500;
;
programmer
id = "avrispv2";
desc = "Atmel AVR ISP V2";
type = stk500v2;
...skipping...
id = "dragon_jtag";
desc = "Atmel AVR Dragon in JTAG mode";
baudrate = 115200;
type = dragon_jtag;
;
# AVR Dragon in ISP mode
programmer
id = "dragon_isp";
desc = "Atmel AVR Dragon in ISP mode";
baudrate = 115200;
type = dragon_isp;
;
# AVR Dragon in PP mode
programmer
id = "dragon_pp";
desc = "Atmel AVR Dragon in PP mode";
baudrate = 115200;
type = dragon_pp;
;
# AVR Dragon in HVSP mode
programmer
id = "dragon_hvsp";
desc = "Atmel AVR Dragon in HVSP mode";
baudrate = 115200;
type = dragon_hvsp;
;
# AVR Dragon in debugWire mode
programmer
id = "dragon_dw";
desc = "Atmel AVR Dragon in debugWire mode";
baudrate = 115200;
type = dragon_dw;
;
# AVR Dragon in PDI mode
programmer
id = "dragon_pdi";
desc = "Atmel AVR Dragon in PDI mode";
baudrate = 115200;
#define ATMEGA161 0x80
#define ATMEGA163 0x81
#define ATMEGA16 0x82
#define ATMEGA162 0x83
#define ATMEGA169 0x84
#define ATMEGA323 0x90
#define ATMEGA32 0x91
#define ATMEGA64 0xA0
#define ATMEGA103 0xB1
#define ATMEGA128 0xB2
#define AT90CAN128 0xB3
#define AT90CAN64 0xB3
#define AT90CAN32 0xB3
#define AT86RF401 0xD0
#define AT89START 0xE0
#define AT89S51 0xE0
#define AT89S52 0xE1
# The following table lists the devices in the original AVR910
# appnote:
# |Device |Signature | Code |
# +-------+----------+------+
# |tiny12 | 1E 90 05 | 0x55 |
# |tiny15 | 1E 90 06 | 0x56 |
# | | | |
# | S1200 | 1E 90 01 | 0x13 |
# | | | |
# | S2313 | 1E 91 01 | 0x20 |
...skipping...
id = "dragon_jtag";
desc = "Atmel AVR Dragon in JTAG mode";
baudrate = 115200;
baudrate = 115200;
type = jtagmkii_dw;
;
# JTAG ICE mkII in AVR32 mode
programmer
id = "jtagmkII_avr32";
desc = "Atmel JTAG ICE mkII im AVR32 mode";
baudrate = 115200;
type = jtagmkii_avr32;
;
# JTAG ICE mkII in AVR32 mode
programmer
id = "jtag2avr32";
desc = "Atmel JTAG ICE mkII im AVR32 mode";
baudrate = 115200;
Options:
-p
-b
-B
-C
-c
-D Disable auto erase for flash memory
-i
-P
-F Override invalid signature check.
-e Perform a chip erase.
-O Perform RC oscillator calibration (see AVR053).
-U
Memory operation specification.
Multiple -U options are allowed, each request
is performed in the order specified.
-n Do not write anything to the device.
-V Do not verify.
-u Disable safemode, default when running from a script.
-s Silent safemode operation, will not ask you if
fuses should be changed back.
-t Enter terminal mode.
-E
-x
-y Count # erase cycles in EEPROM.
-Y
-v Verbose output. -v -v for more.
-q Quell progress output. -q -q for less.
-? Display this usage.
avrdude version 5.8cvs, URL:
pinner:freem_a2 matt$ man avrdude
pinner:freem_a2 matt$ less /usr/local/CrossPack-AVR/etc/avrdude.conf
pinner:freem_a2 matt$ ls
Makefile freem_a2.eep freem_a2.hex freem_a2.map i2cmaster_bitbang.c softuart.h
freem_a2.c freem_a2.elf freem_a2.lss freem_a2_20100527.hex irsony.c
pinner:freem_a2 matt$ emacs Makawk: can't open file /opt/local/etc/bash_completion
source line number 1
efile
pinner:freem_a2 matt$ man avrdude
pinner:freem_a2 matt$ emacs Makefile
[2]+ Stopped emacs Makefile
pinner:freem_a2 matt$ make program
avrdude -p attiny45 -P usb -c dragon_isp -v -v -e -U flash:w:freem_a2.hex -U eeprom:w:freem_a2.eep
avrdude: Version 5.8cvs, compiled on Jan 15 2010 at 17:27:01
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is "/usr/local/CrossPack-AVR-20100115/etc/avrdude.conf"
User configuration file is "/Users/matt/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
Using Port : usb
Using Programmer : dragon_isp
avrdude: stk500v2_dragon_isp_open()
avrdude: usbdev_open(): did not find any USB device "usb"
make: *** [program] Error 1
pinner:freem_a2 matt$ make program
avrdude -p attiny45 -P usb -c dragon_isp -v -v -e -U flash:w:freem_a2.hex -U eeprom:w:freem_a2.eep
avrdude: Version 5.8cvs, compiled on Jan 15 2010 at 17:27:01
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is "/usr/local/CrossPack-AVR-20100115/etc/avrdude.conf"
User configuration file is "/Users/matt/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
Using Port : usb
Using Programmer : dragon_isp
avrdude: stk500v2_dragon_isp_open()
avrdude: usbdev_open(): did not find any USB device "usb"
make: *** [program] Error 1
pinner:freem_a2 matt$
pinner:freem_a2 matt$
pinner:freem_a2 matt$
Sunday, August 01, 2010
HowTo make Yerba Mate in bulk
Inspiration : less mess
Yerba Maté (aka. mate or maté) is way better than coffee in taste, cost, and effects. Don't believe me, try it my way. Conventional brewing techniques will ruin maté.
The pre-made commercially available jars of maté can be quite good, but tend to be costly, weak, and grossly sweetened. The loose tea maté is very inexpensive, but when made wrong can be very messy, taste like sneakers, and have all the caffenine crashing effect of coffees drinks.
Tools :
The key to getting a good "creamy" mate taste is to minimize the steep time and temperature. I've found 75C to be ideal with at most a 5 minute steep. I use a basic dilution to achieve this by adding 1L of room temp water (20C) to 2 liters of boiling water (100C). If you have the good thermometer
that's likely your best bet.
The extra sediment will continue to flavor the mate, so for each straining cycle be prepared to discard the silty bits on the bottom. Anyone tried a centrifuge ?
Deviations: DIY Beverage Bubbles
Club-Mate and makezine.com: Hacking Club-Mate have carbonate varieties which are super delightful on a summers day. I'll have some to share on the playa.
I cannot decide whether to go cheap with this janky looking thing: Beer Carbonator
Or do I go wild with the think geek carbonator caps.
Or does dry ice do the trick. You gotta be brave to do this math.
Sources
Inspiration : less mess
Yerba Maté (aka. mate or maté) is way better than coffee in taste, cost, and effects. Don't believe me, try it my way. Conventional brewing techniques will ruin maté.
The pre-made commercially available jars of maté can be quite good, but tend to be costly, weak, and grossly sweetened. The loose tea maté is very inexpensive, but when made wrong can be very messy, taste like sneakers, and have all the caffenine crashing effect of coffees drinks.
Tools :
- big pot
- Nalgene water bottle
or any way to measure 1 liter of water
- fine mesh strainer
- big jug for storage
- 1 gal clean water
- 2 cups loose maté : I prefer the locally available Yerba Mate Cruz de Malta
for $12 per kg bag. Check your neighborhood markets. I've seen this stuff in everything from Italian, Persian, Indian, to Chinese markets.
- optional: your favorite natural sweetener
- optional: lemon juice
The key to getting a good "creamy" mate taste is to minimize the steep time and temperature. I've found 75C to be ideal with at most a 5 minute steep. I use a basic dilution to achieve this by adding 1L of room temp water (20C) to 2 liters of boiling water (100C). If you have the good thermometer
that's likely your best bet. - boil 2L of water
- mix with 1L room temp water
- add loose mate
- wait no more than 5 minutes
- strain
- discard mate
- strain
- discard mate
- strain
- discard mate
- strain into final jug
- optional: add sweatener and lemon to taste
The extra sediment will continue to flavor the mate, so for each straining cycle be prepared to discard the silty bits on the bottom. Anyone tried a centrifuge ?
Deviations: DIY Beverage Bubbles
Club-Mate and makezine.com: Hacking Club-Mate have carbonate varieties which are super delightful on a summers day. I'll have some to share on the playa.
I cannot decide whether to go cheap with this janky looking thing: Beer Carbonator
Or do I go wild with the think geek carbonator caps.
Or does dry ice do the trick. You gotta be brave to do this math.
Sources
Yerba maté - Wikipedia, the free encyclopedia
Guayaki Organic Yerba Mate
Yerba Mate Information and Shopping - EcoTeas
makezine.com: Hacking Club-Mate
http://www.kk.org/cooltools/archives/001818.php
Wednesday, April 21, 2010
RESOLVING “LOCAL DELETE, INCOMING DELETE UPON UPDATE” SUBVERSION TREE CONFLICTS
NOTE: I’ve noticed a lot of traffic to this page for “local edit incoming delete on update” errors, which are not what this article is about (the solution below may or may not work for that — I have no idea). This article is about “local delete, incoming delete on update” errors. Always back up your work before you muck around with something like this, but that goes doubly if you’re going to try to use these instructions for the “local edit” error.
For reason I’m still trying to untangle, I encountered some really terrible conflicts this afternoon with an SVN checkin that didn’t complete properly, leaving me with a few locked directories that wouldn’t respond to “svn cleanup”.
Using these instructions, I was able to get the directories sorted out:
Move offending directories out of working copy and to a safe place (e.g. desktop)
Run svn cleanup
Run svn up
This actually restored the messed-up directories. Some files were reverted and some deleted files restored; once the entire working copy is cleaned up, you can use the backup copies of the directories to copy back in your changes.
But before I could do that, I was left with a half-dozen individual file conflicts with the following messages:
$ svn st
? C some_file.php
> local delete, incoming delete upon update
? C some_other_file.php
> local delete, incoming delete upon update
... etc.
Thankfully, these were files that I did want to delete, so even without instructions I wasn’t afraid to trial-and-error my way to the following fix:
$ touch some_file.php some_other_file.php
$ svn revert some_file.php some_other_file.php
Once you’ve created the files, SVN can revert them, which leaves them in unversioned status:
$ svn st
? some_file.php
? some_other_file.php
And then you can just delete them from the command line or whatever file manager you use.
*Phew*
Once that was done I redid some deletions that had been overwritten by the update that cleaned up the directories, and all was right in the world.
Usual disclaimers, YMMV, etc.
Posted: Monday, March 8th, 2010
Filed under: subversion
source: http://triopter.com/archive/resolving-local-delete-incoming-delete-upon-update-subversion-tree-conflicts/
NOTE: I’ve noticed a lot of traffic to this page for “local edit incoming delete on update” errors, which are not what this article is about (the solution below may or may not work for that — I have no idea). This article is about “local delete, incoming delete on update” errors. Always back up your work before you muck around with something like this, but that goes doubly if you’re going to try to use these instructions for the “local edit” error.
For reason I’m still trying to untangle, I encountered some really terrible conflicts this afternoon with an SVN checkin that didn’t complete properly, leaving me with a few locked directories that wouldn’t respond to “svn cleanup”.
Using these instructions, I was able to get the directories sorted out:
Move offending directories out of working copy and to a safe place (e.g. desktop)
Run svn cleanup
Run svn up
This actually restored the messed-up directories. Some files were reverted and some deleted files restored; once the entire working copy is cleaned up, you can use the backup copies of the directories to copy back in your changes.
But before I could do that, I was left with a half-dozen individual file conflicts with the following messages:
$ svn st
? C some_file.php
> local delete, incoming delete upon update
? C some_other_file.php
> local delete, incoming delete upon update
... etc.
Thankfully, these were files that I did want to delete, so even without instructions I wasn’t afraid to trial-and-error my way to the following fix:
$ touch some_file.php some_other_file.php
$ svn revert some_file.php some_other_file.php
Once you’ve created the files, SVN can revert them, which leaves them in unversioned status:
$ svn st
? some_file.php
? some_other_file.php
And then you can just delete them from the command line or whatever file manager you use.
*Phew*
Once that was done I redid some deletions that had been overwritten by the update that cleaned up the directories, and all was right in the world.
Usual disclaimers, YMMV, etc.
Posted: Monday, March 8th, 2010
Filed under: subversion
source: http://triopter.com/archive/resolving-local-delete-incoming-delete-upon-update-subversion-tree-conflicts/
I just found two new *nix commands that i've been missing:
- cut
- uniq
CUT to print second column
old:
cat $FILE | awk -f"$DELIMITOR" '{print $2}'
new:
cat $FILE | cut -d"$DELIMITOR" -f2
UNIQ to find dups
old:
traditionally to find dup is a file one might imploy some bash looping tricker:
for i in `cat $FILE | cut -d"." -f1,2 | uniq`
do
num=`cat $FILE | grep $i | wc -l`
if (( $num > 1 ))
then
echo $num $i
fi
done
now:
cat $FILE|sort |uniq -c |sort
sources:
- cut
- uniq
CUT to print second column
old:
cat $FILE | awk -f"$DELIMITOR" '{print $2}'
new:
cat $FILE | cut -d"$DELIMITOR" -f2
UNIQ to find dups
old:
traditionally to find dup is a file one might imploy some bash looping tricker:
for i in `cat $FILE | cut -d"." -f1,2 | uniq`
do
num=`cat $FILE | grep $i | wc -l`
if (( $num > 1 ))
then
echo $num $i
fi
done
now:
cat $FILE|sort |uniq -c |sort
sources:
Subscribe to:
Posts (Atom)