[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

4.2 Programmer Definitions

The format of the programmer definition is as follows:

 
programmer
    parent <id>                                 # <id> is a quoted string
    id       = <id1> [, <id2> [, <id3>] ...] ;  # <idN> are quoted strings
    desc     = <description> ;                  # quoted string
    type     = "par" | "stk500" | ... ;         # programmer type (see below for a list)
    baudrate = <num> ;                          # baudrate for serial ports
    vcc      = <num1> [, <num2> ... ] ;         # pin number(s)
    buff     = <num1> [, <num2> ... ] ;         # pin number(s)
    reset    = <num> ;                          # pin number
    sck      = <num> ;                          # pin number
    mosi     = <num> ;                          # pin number
    miso     = <num> ;                          # pin number
    errled   = <num> ;                          # pin number
    rdyled   = <num> ;                          # pin number
    pgmled   = <num> ;                          # pin number
    vfyled   = <num> ;                          # pin number
    usbvid   = <hexnum>;                        # USB VID (Vendor ID)
    usbpid   = <hexnum>;                        # USB PID (Product ID)
    usbdev   = <interface>;                     # USB interface or other device info 
    usbvendor = <vendorname>;                   # USB Vendor Name
    usbproduct = <productname>;                 # USB Product Name
    usbsn    = <serialno>;                      # USB Serial Number
  ;

If a parent is specified, all settings of it (except its ids) are used for the new programmer. These values can be changed by new setting them for the new programmer.

To invert a bit in the pin definitions, use = ~ <num>.

Following programmer types are currently implemented:

arduinoArduino programmer
avr910Serial programmers using protocol described in application note AVR910
avrftdiInterface to the MPSSE Engine of FTDI Chips using libftdi.
buspirateUsing the Bus Pirate’s SPI interface for programming
buspirate_bbUsing the Bus Pirate’s bitbang interface for programming
butterflyAtmel Butterfly evaluation board; Atmel AppNotes AVR109, AVR911
butterfly_mkMikrokopter.de Butterfly
dragon_dwAtmel AVR Dragon in debugWire mode
dragon_hvspAtmel AVR Dragon in HVSP mode
dragon_ispAtmel AVR Dragon in ISP mode
dragon_jtagAtmel AVR Dragon in JTAG mode
dragon_pdiAtmel AVR Dragon in PDI mode
dragon_ppAtmel AVR Dragon in PP mode
ftdi_syncbbFT245R/FT232R Synchronous BitBangMode Programmer
jtagmkiAtmel JTAG ICE mkI
jtagmkiiAtmel JTAG ICE mkII
jtagmkii_avr32Atmel JTAG ICE mkII in AVR32 mode
jtagmkii_dwAtmel JTAG ICE mkII in debugWire mode
jtagmkii_ispAtmel JTAG ICE mkII in ISP mode
jtagmkii_pdiAtmel JTAG ICE mkII in PDI mode
jtagice3Atmel JTAGICE3
jtagice3_pdiAtmel JTAGICE3 in PDI mode
jtagice3_dwAtmel JTAGICE3 in debugWire mode
jtagice3_ispAtmel JTAGICE3 in ISP mode
linuxgpioGPIO bitbanging using the Linux sysfs interface (not available)
parParallel port bitbanging
pickit2Microchip’s PICkit2 Programmer
serbbSerial port bitbanging
stk500Atmel STK500 Version 1.x firmware
stk500genericAtmel STK500, autodetect firmware version
stk500v2Atmel STK500 Version 2.x firmware
stk500hvspAtmel STK500 V2 in high-voltage serial programming mode
stk500ppAtmel STK500 V2 in parallel programming mode
stk600Atmel STK600
stk600hvspAtmel STK600 in high-voltage serial programming mode
stk600ppAtmel STK600 in parallel programming mode
usbaspUSBasp programmer, see http://www.fischl.de/usbasp/
usbtinyDriver for "usbtiny"-type programmers
wiringhttp://wiring.org.co/, Basically STK500v2 protocol, with some glue to trigger the bootloader.

[ < ] [ > ]   [ << ] [ Up ] [ >> ]

This document was generated by Joerg Wunsch on September 17, 2013 using texi2html 1.82.