Supported boards

Almost all boards equipped with one of the supported chips can be used in one way or another. Tested boards are marked in boldface, and those known not to work are struck out. The ones that are underlined are sitting on my desk and are waiting to be tested. If no supporting hardware package is mentioned, then there is no support through an Arduino package yet, but PyAvrOCD nevertheless supports debugging the chip. For supported boards that have been tested, possible board modifications and other information are mentioned.

Microchip boards

Most of the supported Microchip boards have an embedded debugger on board, which makes it easy to work with. You do not have to modify the boards physically or change fuses. When working with debugWIRE targets, the power cycling is done automatically.

  • ATmega328P Xplained Mini: XMiniCore; onboard debugger, no physical modifications or fuse settings necessary, power-cycling is automatic.
  • ATmega168PB Xplained Mini: XMiniCore; onboard debugger, no physical modifications or fuse settings necessary, power-cycling is automatic.
  • ATmega328PB Xplained Mini: XMiniCore; onboard debugger, no physical modifications or fuse settings necessary, power-cycling is automatic.
  • ATmega324PB Xplained Pro: MightyCore; onboard debugger, serial I/O is routed via Serial1 instead of Serial; the LED is connected to digital pin 23. No physical modifications or fuse settings necessary.
  • AT90USBKEY2 (AT90USB1287)
  • ATmega256RFR2 Xplained Pro
  • AVR Butterfly (ATmega169): MegaCore
  • MEGA-1284P Xplained: MightyCore
  • ATmega4809 Curiosity Nano: MegaCoreX; onboard debugger; choose the 48 pin standard pinout; serial I/O is routed via Serial3; the LED is connected to PF5 (digital pin 39); the programmer you have to choose is Curiosity Nano.
  • ATtiny416 Xplained Nano: megaTinyCore (Debug enabled); onboard debugger
  • ATtiny817 Xplained Pro: megaTinyCore (Debug enabled); onboard debugger
  • ATtiny817 Xplained Mini: megaTinyCore (Debug enabled); onboard debugger; LED is connected to PC0 (LED_BUILTIN); button is on PC5; programmer should be Xplained Mini; serial I/O through the debug interface works.
  • ATtiny1607 Curiosity Nano: megaTinyCore (Debug enabled); onboard debugger; LED is connected to PB7 (LED_BUILTIN); button is on PC4; programmer should be Curiosity Nano; serial I/O through the debug interface works.
  • ATtiny1627 Curiosity Nano: megaTinyCore (Debug enabled); onboard debugger; LED is connected to PB7 (LED_BUILTIN); button is on PC4; programmer should be Curiosity Nano;
  • ATtiny3217 Curiosity Nano: megaTinyCore (Debug enabled); onboard debugger; LED is connected to PB7 (LED_BUILTIN); button is on PC4; programmer should be Curiosity Nano; serial I/O through the debug interface works.
  • ATtiny3227 Curiosity Nano: megaTinyCore (Debug enabled); onboard debugger; LED is connected to PB7 (LED_BUILTIN); button is on PC4; programmer should be Curiosity Nano; serial I/O through the debug interface works.
  • AVR128DA48 Curiosity Nano: DxCore (Debug enabled); onboard debugger; LED is connected to PC6 (pin 20); button is on PC7 (pin 21); programmer should be Curiosity Nano; serial I/O is routed via Serial1 instead of Serial through the debug interface.
  • AVR128DB48 Curiosity Nano: DxCore (Debug enabled); onboard debugger; LED is connected to PB3 (pin 11); button is on PB2 (pin 10); serial I/O is routed via Serial3 instead of Serial through the debug interface.
  • AVR64DD32 Curiosity Nano: DxCore (Debug enabled); onboard debugger; LED is connected to PF5 (pin 25); button is on PF6 (pin 26, RESET); programmer should be Curiosity Nano; serial I/O through the debug interface is routed via Serial, however, you need to swap the I/O pins using Serial.swap(3).
  • AVR64DU32 Curiosity Nano: DxCore (Debug enabled); onboard debugger; LED is connected to PF2 (pin 22); button is on PF6 (pin 26, RESET); programmer should be Curiosity Nano; serial I/O is routed via Serial1 instead of Serial through the debug interface, and in addition, you need to swap the pins: Serial1.swap(2).
  • AVR64EA48 Curiosity Nano: DxCore (Debug enabled); onboard debugger; LED is connected to PB3 (pin 11); button is on PB2 (pin 10); programmer should be Curiosity Nano; serial I/O is routed via Serial1 instead of Serial through the debug interface.
  • AVR16EB32 Curiosity Nano: DxCore (Debug enabled); onboard debugger; LED is connected to PF5 (pin 25); button is on PF6 (pin 26, RESET); programmer should be Curiosity Nano; serial I/O through the debug interface is routed via Serial, however, you need to swap the I/O pins using Serial.swap(4).

Arduino boards

All the Arduino boards with AVR chips are also supported by the debug-enabled forks of the Arduino (mega)AVR Boards packages.

  • Arduino Yún
  • Arduino UNO R3: MiniCore; the RESET EN solder bridge needs to be cut
  • Arduino UNO Mini: MiniCore; remove capacitor C3
  • Arduino Duemilanove: MiniCore; RESET EN needs to be cut
  • Arduino Diecimila: MiniCore; remove 100nF capacitor
  • Arduino Nano: MiniCore; 100 nF cap and 1kΩ resistor needs to be removed
  • Arduino Mega: MegaCore; JTAG pins are A4-A7, use this board adapter, RESET EN does not need to be opened
  • Arduino Mega 2560: MegaCore; JTAG pins are A4-A7, use this board adapter, RESET EN does not need to be opened
  • Arduino Mega ADK: MegaCore
  • Arduino Leonardo: JTAG pins are A0-A3, use this board adapter
  • Arduino Leonardo ETH
  • Arduino Micro
  • Arduino Esplora: JTAG pins are not accessible
  • Arduino Mini: MiniCore (if Mini 05); do not connect the DTR pin of the FTDI header
  • Arduino Ethernet: MiniCore; do not connect the DTR pin of the FTDI header
  • Arduino Fio: MiniCore; do not connect the DTR pin of the FTDI header, and do not connect an XBee
  • Arduino BT: MiniCore; remove capacitor C1 (which you do not have to resolder after debugging)
  • LilyPad Arduino USB: JTAG pins are not accessible
  • LilyPad Arduino: MiniCore; do not connect the DTR pin of the FTDI header
  • Arduino Pro: MiniCore; do not connect the DTR pin of the FTDI header
  • Arduino Pro Mini: MiniCore; do not connect the DTR pin of the FTDI header
  • Arduino NG (ATmega168): MiniCore; no modifications necessary
  • Arduino NG (ATmega8): no debugging interface
  • Arduino Robot Control
  • Arduino Robot Motor
  • Arduino Gemma: TinyCore; RESET pad on backside
  • Adafruit Circuit Playground 32u4
  • Arduino Yún Mini
  • Arduino Industrial 101
  • Arduino Linino One
  • Arduino UNO WiFi (Rev 1): MiniCore; cut RESET EN solder bridge
  • Arduino Uno WiFi (Rev 2): MegaCoreX; board has an onboard debugger; the recommended pinout is Uno Wifi; serial I/O is via Serial; LED_BUILTIN is digital pin 25 (PD6); there is no bootloader support because you can load via the onboard debugger/programmer microUPDI/Uno WiFi
  • Arduino Nano Every: MegaCoreX; UPDI pad on the backside; the only pinout is Nano Every; serial I/O is routed via Serial; LED_BUILTIN is digital pin 13 (PE2); there is no bootloader support because you can load via the onboard programmer JTAG2UPDI

Sparkfun boards

  • RedBoard (ATmega328P): MiniCore, remove C8
  • Pro Micro 3.3V (ATmega32U4)
  • Pro Micro 5V (ATmega32U4)
  • Fio v3
  • Qduino Mini (ATmega32U4)
  • Mega Pro 3.3V: MegaCore
  • Mega Pro 5V: MegaCore
  • RedBot (ATmega328P): MiniCore
  • Serial-7-Segment-Display (ATmega328P): MiniCore
  • ATmega128RFA1 Development Board
  • LilyPad USB Plus: JTAG pins are not accessible
  • SerLcd
  • Digital Sandbox (ATmega328P): MiniCore
  • Microview (ATmega328P): MiniCore; the SPI pins are not exposed, you need to solder to some vias inside the enclosure

Adafruit boards

  • Flora (ATmega32U4): JTAG pins are not accessible
  • Feather 32U4
  • Feather 328P: MiniCore
  • Gemma (ATtiny85): TinyCore; RESET pad on backside
  • Trinket 3.3V (ATtiny85): TinyCore
  • Trinket 5V (ATtiny85): TinyCore
  • Metro (ATmega328P): MiniCore, cut RESET EN solder bridge
  • Metro Mini V2: MiniCore, you have to figure out which cap to remove
  • Circuit Playground Classic (ATmega32U4)
  • Pro Trinket 5V/16MHz (USB): MiniCore
  • Pro Trinket 3V/12MHz (USB): MiniCore
  • Pro Trinket 5V/16MHz (FTDI): MiniCore
  • Pro Trinket 3V/12MHz (FTDI): MiniCore
  • ItsyBitsy 32u4 (3V)
  • ItsyBitsy 32u4 (5V)
  • Bluefruit Micro
  • ATmega32u4 Breakout Board
  • SEESAW Breakout ATtiny817: megaTinyCore (Debug enabled)
  • SEESAW Breakout ATtiny1616: megaTinyCore (Debug enabled)

Teensy boards

  • Teensy 2.0 (ATmega32U4)
  • Teensy++ (AT90USB1286)

Olimex boards

  • Olimex-328: MiniCore
  • Olimex-32u4
  • eduArdu: JTAG pins are not accessible
  • Olimex-Nano: MiniCore
  • RGB-Glasses
  • Olimexino-2560: MegaCore
  • AVR-CAN (AT90CAN128): MegaCore
  • AVR-GSM (ATMega32): MightyCore
  • AVR-IO-M16 (ATmega16): MightyCore
  • AVR-MT128 (ATmega128): MegaCore
  • AVR-USB-STK (AT90USB162)
  • AVR-USB-162 (AT90USB162)

Seeed Studio boards

  • Seeeduino V3.0: MiniCore
  • Seeeduino v4: MiniCore; remove C14 and RESET LED (next to RESET button)
  • Stalker: MiniCore; do not connect DTR
  • Seeeduino Lotus: MiniCore; remove C6 and RESET LED (next to RESET button)
  • Seeeduino Lite
  • Seeeduino Nano: MiniCore
  • Seeeduino Mega 2560: MegaCore

Azduino boards by Spence Konde

Miscellaneous boards

  • MH-ET LIVE (ATtiny88): TinyCore
  • Digispark (ATtiny85): RESET pin is set to be a GPIO; HV programming needed before the board can be debugged
  • Digispark Pro (ATtiny167): TinyCore
  • Pololu A-Star 328PB Micro: MiniCore
  • Thinary Nano Every (ATmega4808): MegaCoreX; the only supported pinout is Nano 4808; serial I/O via Serial; LED_BUILTIN is digital pin 9 (PA7); no bootloader support because there is a JTAG2UPDI programmer on board