neulab/tldr huggingface dataset:
Adafruit Pro Trinket 3V/12MHz (FTDI) Contents • Adafruit Pro Trinket 3V/12MHz (FTDI)
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 12MHz      │ ├────────────────┼────────────┤ │Flash           │ 28KB       │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use protrinket3ftdi ID for projectconf_env_board option in projectconf:
[env:protrinket3ftdi] platform = atmelavr board = protrinket3ftdi
You can override default Adafruit Pro Trinket 3V/12MHz (FTDI) settings per build environment using board_*** option, where *** is a JSON object path from board manifest protrinket3ftdi.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change MCU frequency board_build.f_cpu = 12000000L
Adafruit Pro Trinket 3V/12MHz (FTDI) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Adafruit Pro Trinket 3V/12MHz (USB) Contents • Adafruit Pro Trinket 3V/12MHz (USB)
Configuration Please use protrinket3 ID for projectconf_env_board option in projectconf:
[env:protrinket3] platform = atmelavr board = protrinket3
You can override default Adafruit Pro Trinket 3V/12MHz (USB) settings per build environment using board_*** option, where *** is a JSON object path from board manifest protrinket3.json. For example, board_build.mcu, board_build.f_cpu, etc.
Adafruit Pro Trinket 3V/12MHz (USB) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Adafruit Pro Trinket 5V/16MHz (FTDI) Contents • Adafruit Pro Trinket 5V/16MHz (FTDI)
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 28KB       │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use protrinket5ftdi ID for projectconf_env_board option in projectconf:
[env:protrinket5ftdi] platform = atmelavr board = protrinket5ftdi
You can override default Adafruit Pro Trinket 5V/16MHz (FTDI) settings per build environment using board_*** option, where *** is a JSON object path from board manifest protrinket5ftdi.json. For example, board_build.mcu, board_build.f_cpu, etc.
Adafruit Pro Trinket 5V/16MHz (FTDI) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Adafruit Pro Trinket 5V/16MHz (USB) Contents • Adafruit Pro Trinket 5V/16MHz (USB)
Configuration Please use protrinket5 ID for projectconf_env_board option in projectconf:
[env:protrinket5] platform = atmelavr board = protrinket5
You can override default Adafruit Pro Trinket 5V/16MHz (USB) settings per build environment using board_*** option, where *** is a JSON object path from board manifest protrinket5.json. For example, board_build.mcu, board_build.f_cpu, etc.
Adafruit Pro Trinket 5V/16MHz (USB) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Adafruit Trinket 3V/8MHz Contents • Adafruit Trinket 3V/8MHz
Configuration Please use trinket3 ID for projectconf_env_board option in projectconf:
[env:trinket3] platform = atmelavr board = trinket3
You can override default Adafruit Trinket 3V/8MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest trinket3.json. For example, board_build.mcu, board_build.f_cpu, etc.
Adafruit Trinket 3V/8MHz has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Adafruit Trinket 5V/16MHz Contents • Adafruit Trinket 5V/16MHz
┌────────────────┬──────────┐ │Microcontroller │ ATTINY85 │ ├────────────────┼──────────┤ │Frequency       │ 16MHz    │ ├────────────────┼──────────┤ │Flash           │ 8KB      │ ├────────────────┼──────────┤ │RAM             │ 512B     │ ├────────────────┼──────────┤ │Vendor          │ Adafruit │ └────────────────┴──────────┘
Configuration Please use trinket5 ID for projectconf_env_board option in projectconf:
[env:trinket5] platform = atmelavr board = trinket5
You can override default Adafruit Trinket 5V/16MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest trinket5.json. For example, board_build.mcu, board_build.f_cpu, etc.
Adafruit Trinket 5V/16MHz has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Alorium Hinj Contents • Alorium Hinj
┌────────────────┬────────────────────┐ │Microcontroller │ ATMEGA328P         │ ├────────────────┼────────────────────┤ │Frequency       │ 16MHz              │ ├────────────────┼────────────────────┤ │Flash           │ 31.50KB            │ ├────────────────┼────────────────────┤ │RAM             │ 2KB                │ ├────────────────┼────────────────────┤ │Vendor          │ Alorium Technology │ └────────────────┴────────────────────┘
Configuration Please use alorium_hinj ID for projectconf_env_board option in projectconf:
[env:alorium_hinj] platform = atmelavr board = alorium_hinj
You can override default Alorium Hinj settings per build environment using board_*** option, where *** is a JSON object path from board manifest alorium_hinj.json. For example, board_build.mcu, board_build.f_cpu, etc.
Alorium Hinj has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Alorium Sno Contents • Alorium Sno
Configuration Please use alorium_sno ID for projectconf_env_board option in projectconf:
[env:alorium_sno] platform = atmelavr board = alorium_sno
You can override default Alorium Sno settings per build environment using board_*** option, where *** is a JSON object path from board manifest alorium_sno.json. For example, board_build.mcu, board_build.f_cpu, etc.
Alorium Sno has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Alorium XLR8 Contents • Alorium XLR8
Configuration Please use alorium_xlr8 ID for projectconf_env_board option in projectconf:
[env:alorium_xlr8] platform = atmelavr board = alorium_xlr8
You can override default Alorium XLR8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest alorium_xlr8.json. For example, board_build.mcu, board_build.f_cpu, etc.
Alorium XLR8 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Altair Contents • Altair
┌────────────────┬───────────────┐ │Microcontroller │ ATMEGA256RFR2 │ ├────────────────┼───────────────┤ │Frequency       │ 16MHz         │ ├────────────────┼───────────────┤ │Flash           │ 248KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ makerlab.mx   │ └────────────────┴───────────────┘
Configuration Please use altair ID for projectconf_env_board option in projectconf:
[env:altair] platform = atmelavr board = altair
You can override default Altair settings per build environment using board_*** option, where *** is a JSON object path from board manifest altair.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = atmega256rfr2
Debugging piodebug currently does not support Altair board.
Anarduino MiniWireless Contents • Anarduino MiniWireless
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 31.50KB    │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ Anarduino  │ └────────────────┴────────────┘
Configuration Please use miniwireless ID for projectconf_env_board option in projectconf:
[env:miniwireless] platform = atmelavr board = miniwireless
You can override default Anarduino MiniWireless settings per build environment using board_*** option, where *** is a JSON object path from board manifest miniwireless.json. For example, board_build.mcu, board_build.f_cpu, etc.
Anarduino MiniWireless has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduboy Contents • Arduboy
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA32U4 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 28KB       │ ├────────────────┼────────────┤ │RAM             │ 2.50KB     │ ├────────────────┼────────────┤ │Vendor          │ Arduboy    │ └────────────────┴────────────┘
Configuration Please use arduboy ID for projectconf_env_board option in projectconf:
[env:arduboy] platform = atmelavr board = arduboy
You can override default Arduboy settings per build environment using board_*** option, where *** is a JSON object path from board manifest arduboy.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduboy has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduboy DevKit Contents • Arduboy DevKit
Configuration Please use arduboy_devkit ID for projectconf_env_board option in projectconf:
[env:arduboy_devkit] platform = atmelavr board = arduboy_devkit
You can override default Arduboy DevKit settings per build environment using board_*** option, where *** is a JSON object path from board manifest arduboy_devkit.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduboy DevKit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino BT ATmega168 Contents • Arduino BT ATmega168
┌────────────────┬───────────┐ │Microcontroller │ ATMEGA168 │ ├────────────────┼───────────┤ │Frequency       │ 16MHz     │ ├────────────────┼───────────┤ │Flash           │ 14KB      │ ├────────────────┼───────────┤ │RAM             │ 1KB       │ ├────────────────┼───────────┤ │Vendor          │ Arduino   │ └────────────────┴───────────┘
Configuration Please use btatmega168 ID for projectconf_env_board option in projectconf:
[env:btatmega168] platform = atmelavr board = btatmega168
You can override default Arduino BT ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest btatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino BT ATmega168 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino BT ATmega328 Contents • Arduino BT ATmega328
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 28KB       │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use btatmega328 ID for projectconf_env_board option in projectconf:
[env:btatmega328] platform = atmelavr board = btatmega328
You can override default Arduino BT ATmega328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest btatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino BT ATmega328 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Duemilanove or Diecimila ATmega168 Contents • Arduino Duemilanove or Diecimila ATmega168
Configuration Please use diecimilaatmega168 ID for projectconf_env_board option in projectconf:
[env:diecimilaatmega168] platform = atmelavr board = diecimilaatmega168
You can override default Arduino Duemilanove or Diecimila ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest diecimilaatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Duemilanove or Diecimila ATmega168 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Duemilanove or Diecimila ATmega328 Contents • Arduino Duemilanove or Diecimila ATmega328
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 30KB       │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use diecimilaatmega328 ID for projectconf_env_board option in projectconf:
[env:diecimilaatmega328] platform = atmelavr board = diecimilaatmega328
You can override default Arduino Duemilanove or Diecimila ATmega328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest diecimilaatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Duemilanove or Diecimila ATmega328 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Esplora Contents • Arduino Esplora
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA32U4 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 28KB       │ ├────────────────┼────────────┤ │RAM             │ 2.50KB     │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use esplora ID for projectconf_env_board option in projectconf:
[env:esplora] platform = atmelavr board = esplora
You can override default Arduino Esplora settings per build environment using board_*** option, where *** is a JSON object path from board manifest esplora.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Esplora has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Ethernet Contents • Arduino Ethernet
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 31.50KB    │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use ethernet ID for projectconf_env_board option in projectconf:
[env:ethernet] platform = atmelavr board = ethernet
You can override default Arduino Ethernet settings per build environment using board_*** option, where *** is a JSON object path from board manifest ethernet.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Ethernet has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Fio Contents • Arduino Fio
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 8MHz       │ ├────────────────┼────────────┤ │Flash           │ 30KB       │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use fio ID for projectconf_env_board option in projectconf:
[env:fio] platform = atmelavr board = fio
You can override default Arduino Fio settings per build environment using board_*** option, where *** is a JSON object path from board manifest fio.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Fio has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Industrial 101 Contents • Arduino Industrial 101
Configuration Please use chiwawa ID for projectconf_env_board option in projectconf:
[env:chiwawa] platform = atmelavr board = chiwawa
You can override default Arduino Industrial 101 settings per build environment using board_*** option, where *** is a JSON object path from board manifest chiwawa.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Industrial 101 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Leonardo Contents • Arduino Leonardo
Configuration Please use leonardo ID for projectconf_env_board option in projectconf:
[env:leonardo] platform = atmelavr board = leonardo
You can override default Arduino Leonardo settings per build environment using board_*** option, where *** is a JSON object path from board manifest leonardo.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Leonardo has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Leonardo ETH Contents • Arduino Leonardo ETH
Configuration Please use leonardoeth ID for projectconf_env_board option in projectconf:
[env:leonardoeth] platform = atmelavr board = leonardoeth
You can override default Arduino Leonardo ETH settings per build environment using board_*** option, where *** is a JSON object path from board manifest leonardoeth.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Leonardo ETH has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino LilyPad ATmega168 Contents • Arduino LilyPad ATmega168
┌────────────────┬───────────┐ │Microcontroller │ ATMEGA168 │ ├────────────────┼───────────┤ │Frequency       │ 8MHz      │ ├────────────────┼───────────┤ │Flash           │ 14KB      │ ├────────────────┼───────────┤ │RAM             │ 1KB       │ ├────────────────┼───────────┤ │Vendor          │ Arduino   │ └────────────────┴───────────┘
Configuration Please use lilypadatmega168 ID for projectconf_env_board option in projectconf:
[env:lilypadatmega168] platform = atmelavr board = lilypadatmega168
You can override default Arduino LilyPad ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lilypadatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino LilyPad ATmega168 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino LilyPad USB has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Mega ADK Contents • Arduino Mega ADK
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA2560 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 248KB      │ ├────────────────┼────────────┤ │RAM             │ 8KB        │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use megaADK ID for projectconf_env_board option in projectconf:
[env:megaADK] platform = atmelavr board = megaADK
You can override default Arduino Mega ADK settings per build environment using board_*** option, where *** is a JSON object path from board manifest megaADK.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Mega ADK has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Mega or Mega 2560 ATmega1280 Contents • Arduino Mega or Mega 2560 ATmega1280
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA1280 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 124KB      │ ├────────────────┼────────────┤ │RAM             │ 8KB        │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use megaatmega1280 ID for projectconf_env_board option in projectconf:
[env:megaatmega1280] platform = atmelavr board = megaatmega1280
You can override default Arduino Mega or Mega 2560 ATmega1280 settings per build environment using board_*** option, where *** is a JSON object path from board manifest megaatmega1280.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Mega or Mega 2560 ATmega1280 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) Contents • Arduino Mega or Mega 2560 ATmega2560 (Mega 2560)
Configuration Please use megaatmega2560 ID for projectconf_env_board option in projectconf:
[env:megaatmega2560] platform = atmelavr board = megaatmega2560
You can override default Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) settings per build environment using board_*** option, where *** is a JSON object path from board manifest megaatmega2560.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Micro Contents • Arduino Micro
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA32U4 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ └────────────────┴────────────┘
│Flash           │ 28KB       │ ├────────────────┼────────────┤ │RAM             │ 2.50KB     │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use micro ID for projectconf_env_board option in projectconf:
[env:micro] platform = atmelavr board = micro
You can override default Arduino Micro settings per build environment using board_*** option, where *** is a JSON object path from board manifest micro.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Micro has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Mini ATmega168 Contents • Arduino Mini ATmega168
Configuration Please use miniatmega168 ID for projectconf_env_board option in projectconf:
[env:miniatmega168] platform = atmelavr board = miniatmega168
You can override default Arduino Mini ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest miniatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Mini ATmega168 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Mini ATmega328 Contents • Arduino Mini ATmega328
Configuration Please use miniatmega328 ID for projectconf_env_board option in projectconf:
[env:miniatmega328] platform = atmelavr board = miniatmega328
You can override default Arduino Mini ATmega328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest miniatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Mini ATmega328 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino NG or older ATmega168 Contents • Arduino NG or older ATmega168
Configuration Please use atmegangatmega168 ID for projectconf_env_board option in projectconf:
[env:atmegangatmega168] platform = atmelavr board = atmegangatmega168
You can override default Arduino NG or older ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest atmegangatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino NG or older ATmega168 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino NG or older ATmega8 Contents • Arduino NG or older ATmega8
┌────────────────┬─────────┐ │Microcontroller │ ATMEGA8 │ ├────────────────┼─────────┤ │Frequency       │ 16MHz   │ ├────────────────┼─────────┤ │Flash           │ 7KB     │ ├────────────────┼─────────┤ │RAM             │ 1KB     │ ├────────────────┼─────────┤ │Vendor          │ Arduino │ └────────────────┴─────────┘
Configuration Please use atmegangatmega8 ID for projectconf_env_board option in projectconf:
[env:atmegangatmega8] platform = atmelavr board = atmegangatmega8
You can override default Arduino NG or older ATmega8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest atmegangatmega8.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino NG or older ATmega8 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Nano ATmega168 Contents • Arduino Nano ATmega168
Configuration Please use nanoatmega168 ID for projectconf_env_board option in projectconf:
[env:nanoatmega168] platform = atmelavr board = nanoatmega168
You can override default Arduino Nano ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nanoatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Nano ATmega168 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Nano ATmega328 Contents • Arduino Nano ATmega328
Configuration Please use nanoatmega328 ID for projectconf_env_board option in projectconf:
[env:nanoatmega328] platform = atmelavr board = nanoatmega328
You can override default Arduino Nano ATmega328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nanoatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Nano ATmega328 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Nano ATmega328 (New Bootloader) Contents • Arduino Nano ATmega328 (New Bootloader)
Configuration Please use nanoatmega328new ID for projectconf_env_board option in projectconf:
[env:nanoatmega328new] platform = atmelavr board = nanoatmega328new
You can override default Arduino Nano ATmega328 (New Bootloader) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nanoatmega328new.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Nano ATmega328 (New Bootloader) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) Contents • Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz)
Configuration Please use pro8MHzatmega168 ID for projectconf_env_board option in projectconf:
[env:pro8MHzatmega168] platform = atmelavr board = pro8MHzatmega168
You can override default Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest pro8MHzatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) Contents • Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz)
Configuration Please use pro16MHzatmega168 ID for projectconf_env_board option in projectconf:
[env:pro16MHzatmega168] platform = atmelavr board = pro16MHzatmega168
You can override default Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest pro16MHzatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) Contents • Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz)
Configuration Please use pro8MHzatmega328 ID for projectconf_env_board option in projectconf:
[env:pro8MHzatmega328] platform = atmelavr board = pro8MHzatmega328
You can override default Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest pro8MHzatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) Contents • Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz)
Configuration Please use pro16MHzatmega328 ID for projectconf_env_board option in projectconf:
[env:pro16MHzatmega328] platform = atmelavr board = pro16MHzatmega328
You can override default Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest pro16MHzatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Robot Control Contents • Arduino Robot Control
Configuration Please use robotControl ID for projectconf_env_board option in projectconf:
[env:robotControl] platform = atmelavr board = robotControl
You can override default Arduino Robot Control settings per build environment using board_*** option, where *** is a JSON object path from board manifest robotControl.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Robot Control has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Robot Motor Contents • Arduino Robot Motor
Configuration Please use robotMotor ID for projectconf_env_board option in projectconf:
[env:robotMotor] platform = atmelavr board = robotMotor
You can override default Arduino Robot Motor settings per build environment using board_*** option, where *** is a JSON object path from board manifest robotMotor.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Robot Motor has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Uno Contents • Arduino Uno
Configuration Please use uno ID for projectconf_env_board option in projectconf:
[env:uno] platform = atmelavr board = uno
You can override default Arduino Uno settings per build environment using board_*** option, where *** is a JSON object path from board manifest uno.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Uno has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Yun Contents • Arduino Yun
Configuration Please use yun ID for projectconf_env_board option in projectconf:
[env:yun] platform = atmelavr board = yun
You can override default Arduino Yun settings per build environment using board_*** option, where *** is a JSON object path from board manifest yun.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Yun has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Yun Mini Contents • Arduino Yun Mini
Configuration Please use yunmini ID for projectconf_env_board option in projectconf:
[env:yunmini] platform = atmelavr board = yunmini
You can override default Arduino Yun Mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest yunmini.json. For example, board_build.mcu, board_build.f_cpu, etc.
Arduino Yun Mini has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Atmel AT90PWM216 Contents • Atmel AT90PWM216
┌────────────────┬────────────┐ │Microcontroller │ AT90PWM216 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 16KB       │ ├────────────────┼────────────┤ │RAM             │ 1KB        │ ├────────────────┼────────────┤ │Vendor          │ Microchip  │ └────────────────┴────────────┘
Configuration Please use at90pwm216 ID for projectconf_env_board option in projectconf:
[env:at90pwm216] platform = atmelavr board = at90pwm216
You can override default Atmel AT90PWM216 settings per build environment using board_*** option, where *** is a JSON object path from board manifest at90pwm216.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = at90pwm216
Debugging piodebug currently does not support Atmel AT90PWM216 board.
Atmel AT90PWM316 Contents • Atmel AT90PWM316
┌────────────────┬────────────┐ │Microcontroller │ AT90PWM316 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 16KB       │ ├────────────────┼────────────┤ │RAM             │ 1KB        │ ├────────────────┼────────────┤ │Vendor          │ Microchip  │ └────────────────┴────────────┘
Configuration Please use at90pwm316 ID for projectconf_env_board option in projectconf:
[env:at90pwm316] platform = atmelavr board = at90pwm316
You can override default Atmel AT90PWM316 settings per build environment using board_*** option, where *** is a JSON object path from board manifest at90pwm316.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = at90pwm316
Debugging piodebug currently does not support Atmel AT90PWM316 board.
BQ ZUM BT-328 Contents • BQ ZUM BT-328
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 28KB       │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ BQ         │ └────────────────┴────────────┘
Configuration Please use zumbt328 ID for projectconf_env_board option in projectconf:
[env:zumbt328] platform = atmelavr board = zumbt328
You can override default BQ ZUM BT-328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest zumbt328.json. For example, board_build.mcu, board_build.f_cpu, etc.
BQ ZUM BT-328 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
BitWizard Raspduino Contents • BitWizard Raspduino
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 30KB       │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ BitWizard  │ └────────────────┴────────────┘
Configuration Please use raspduino ID for projectconf_env_board option in projectconf:
[env:raspduino] platform = atmelavr board = raspduino
You can override default BitWizard Raspduino settings per build environment using board_*** option, where *** is a JSON object path from board manifest raspduino.json. For example, board_build.mcu, board_build.f_cpu, etc.
BitWizard Raspduino has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Controllino Maxi Contents • Controllino Maxi
┌────────────────┬─────────────┐ │Microcontroller │ ATMEGA2560  │ ├────────────────┼─────────────┤ │Frequency       │ 16MHz       │ ├────────────────┼─────────────┤ │Flash           │ 248KB       │ ├────────────────┼─────────────┤ │RAM             │ 8KB         │ ├────────────────┼─────────────┤ │Vendor          │ Controllino │ └────────────────┴─────────────┘
Configuration Please use controllino_maxi ID for projectconf_env_board option in projectconf:
[env:controllino_maxi] platform = atmelavr board = controllino_maxi
You can override default Controllino Maxi settings per build environment using board_*** option, where *** is a JSON object path from board manifest controllino_maxi.json. For example, board_build.mcu, board_build.f_cpu, etc.
Controllino Maxi has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Controllino Maxi Automation Contents • Controllino Maxi Automation
Configuration Please use controllino_maxi_automation ID for projectconf_env_board option in projectconf:
[env:controllino_maxi_automation] platform = atmelavr board = controllino_maxi_automation
You can override default Controllino Maxi Automation settings per build environment using board_*** option, where *** is a JSON object path from board manifest controllino_maxi_automation.json. For example, board_build.mcu, board_build.f_cpu, etc.
Controllino Maxi Automation has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Controllino Mega Contents • Controllino Mega
Configuration Please use controllino_mega ID for projectconf_env_board option in projectconf:
[env:controllino_mega] platform = atmelavr board = controllino_mega
You can override default Controllino Mega settings per build environment using board_*** option, where *** is a JSON object path from board manifest controllino_mega.json. For example, board_build.mcu, board_build.f_cpu, etc.
Controllino Mega has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Controllino Mini Contents • Controllino Mini
┌────────────────┬─────────────┐ │Microcontroller │ ATMEGA328P  │ ├────────────────┼─────────────┤ │Frequency       │ 16MHz       │ ├────────────────┼─────────────┤ │Flash           │ 31.50KB     │ ├────────────────┼─────────────┤ │RAM             │ 2KB         │ ├────────────────┼─────────────┤ │Vendor          │ Controllino │ └────────────────┴─────────────┘
Configuration Please use controllino_mini ID for projectconf_env_board option in projectconf:
[env:controllino_mini] platform = atmelavr board = controllino_mini
You can override default Controllino Mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest controllino_mini.json. For example, board_build.mcu, board_build.f_cpu, etc.
Controllino Mini has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Digispark Pro Contents • Digispark Pro
┌────────────────┬───────────┐ │Microcontroller │ ATTINY167 │ ├────────────────┼───────────┤ │Frequency       │ 16MHz     │ ├────────────────┼───────────┤ │Flash           │ 14.50KB   │ ├────────────────┼───────────┤ │RAM             │ 512B      │ ├────────────────┼───────────┤ │Vendor          │ Digistump │ └────────────────┴───────────┘
Configuration Please use digispark-pro ID for projectconf_env_board option in projectconf:
[env:digispark-pro] platform = atmelavr board = digispark-pro
You can override default Digispark Pro settings per build environment using board_*** option, where *** is a JSON object path from board manifest digispark-pro.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = attiny167
Debugging piodebug currently does not support Digispark Pro board.
Digispark Pro (16 MHz) (64 byte buffer) Contents • Digispark Pro (16 MHz) (64 byte buffer)
Configuration Please use digispark-pro64 ID for projectconf_env_board option in projectconf:
[env:digispark-pro64] platform = atmelavr board = digispark-pro64
You can override default Digispark Pro (16 MHz) (64 byte buffer) settings per build environment using board_*** option, where *** is a JSON object path from board manifest digispark-pro64.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Digispark Pro (16 MHz) (64 byte buffer) board.
Digispark Pro (32 byte buffer) Contents • Digispark Pro (32 byte buffer)
Configuration Please use digispark-pro32 ID for projectconf_env_board option in projectconf:
[env:digispark-pro32] platform = atmelavr board = digispark-pro32
You can override default Digispark Pro (32 byte buffer) settings per build environment using board_*** option, where *** is a JSON object path from board manifest digispark-pro32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Digispark Pro (32 byte buffer) board.
Digispark USB Contents • Digispark USB
┌────────────────┬───────────┐ │Microcontroller │ ATTINY85  │ ├────────────────┼───────────┤ │Frequency       │ 16MHz     │ ├────────────────┼───────────┤ │Flash           │ 5.87KB    │ ├────────────────┼───────────┤ │RAM             │ 512B      │ ├────────────────┼───────────┤ │Vendor          │ Digistump │ └────────────────┴───────────┘
Configuration Please use digispark-tiny ID for projectconf_env_board option in projectconf:
[env:digispark-tiny] platform = atmelavr board = digispark-tiny
You can override default Digispark USB settings per build environment using board_*** option, where *** is a JSON object path from board manifest digispark-tiny.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change MCU frequency board_build.f_cpu = 16500000L
Digispark USB has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Dwenguino Contents • Dwenguino
┌────────────────┬────────────┐ │Microcontroller │ AT90USB646 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 60KB       │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ Dwengo     │ └────────────────┴────────────┘
Configuration Please use dwenguino ID for projectconf_env_board option in projectconf:
[env:dwenguino] platform = atmelavr board = dwenguino
You can override default Dwenguino settings per build environment using board_*** option, where *** is a JSON object path from board manifest dwenguino.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = at90usb646
Debugging piodebug currently does not support Dwenguino board.
Elektor Uno R4 Contents • Elektor Uno R4
┌────────────────┬─────────────┐ │Microcontroller │ ATMEGA328PB │ ├────────────────┼─────────────┤ │Frequency       │ 16MHz       │ ├────────────────┼─────────────┤ │Flash           │ 31.50KB     │ ├────────────────┼─────────────┤ │RAM             │ 2KB         │ ├────────────────┼─────────────┤ │Vendor          │ Elektor     │ └────────────────┴─────────────┘
Configuration Please use elektor_uno_r4 ID for projectconf_env_board option in projectconf:
[env:elektor_uno_r4] platform = atmelavr board = elektor_uno_r4
You can override default Elektor Uno R4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest elektor_uno_r4.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Elektor Uno R4 board.
Engduino 3 Contents • Engduino 3
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA32U4 │ ├────────────────┼────────────┤ │Frequency       │ 8MHz       │ ├────────────────┼────────────┤ │Flash           │ 28KB       │ ├────────────────┼────────────┤ │RAM             │ 2.50KB     │ ├────────────────┼────────────┤ │Vendor          │ Engduino   │ └────────────────┴────────────┘
Configuration Please use engduinov3 ID for projectconf_env_board option in projectconf:
[env:engduinov3] platform = atmelavr board = engduinov3
You can override default Engduino 3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest engduinov3.json. For example, board_build.mcu, board_build.f_cpu, etc.
Engduino 3 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
EnviroDIY Mayfly Contents • EnviroDIY Mayfly
┌────────────────┬─────────────┐ │Microcontroller │ ATMEGA1284P │ ├────────────────┼─────────────┤ │Frequency       │ 8MHz        │ ├────────────────┼─────────────┤ │Flash           │ 127KB       │ ├────────────────┼─────────────┤ │RAM             │ 16KB        │ ├────────────────┼─────────────┤ │Vendor          │ EnviroDIY   │ └────────────────┴─────────────┘
Configuration Please use mayfly ID for projectconf_env_board option in projectconf:
[env:mayfly] platform = atmelavr board = mayfly
You can override default EnviroDIY Mayfly settings per build environment using board_*** option, where *** is a JSON object path from board manifest mayfly.json. For example, board_build.mcu, board_build.f_cpu, etc.
EnviroDIY Mayfly has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
FYSETC F6 V1.3 Contents • FYSETC F6 V1.3
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA2560 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 252KB      │ ├────────────────┼────────────┤ │RAM             │ 8KB        │ ├────────────────┼────────────┤ │Vendor          │ FYSETC     │ └────────────────┴────────────┘
Configuration Please use fysetc_f6_13 ID for projectconf_env_board option in projectconf:
[env:fysetc_f6_13] platform = atmelavr board = fysetc_f6_13
You can override default FYSETC F6 V1.3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest fysetc_f6_13.json. For example, board_build.mcu, board_build.f_cpu, etc.
FYSETC F6 V1.3 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Generic ATtiny13 Contents • Generic ATtiny13
┌────────────────┬──────────┐ │Microcontroller │ ATTINY13 │ ├────────────────┼──────────┤ │Frequency       │ 1MHz     │ ├────────────────┼──────────┤ │Flash           │ 1KB      │ ├────────────────┼──────────┤ │RAM             │ 64B      │ ├────────────────┼──────────┤ │Vendor          │ Atmel    │ └────────────────┴──────────┘
Configuration Please use attiny13 ID for projectconf_env_board option in projectconf:
[env:attiny13] platform = atmelavr board = attiny13
You can override default Generic ATtiny13 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny13.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = attiny13
; change MCU frequency board_build.f_cpu = 1200000L
Generic ATtiny13 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Generic ATtiny13A Contents • Generic ATtiny13A
┌────────────────┬───────────┐ │Microcontroller │ ATTINY13A │ ├────────────────┼───────────┤ │Frequency       │ 1MHz      │ ├────────────────┼───────────┤ │Flash           │ 1KB       │ ├────────────────┼───────────┤ │RAM             │ 64B       │ ├────────────────┼───────────┤ │Vendor          │ Atmel     │ └────────────────┴───────────┘
Configuration Please use attiny13a ID for projectconf_env_board option in projectconf:
[env:attiny13a] platform = atmelavr board = attiny13a
You can override default Generic ATtiny13A settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny13a.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = attiny13a
Generic ATtiny13A has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Generic ATtiny1634 Contents • Generic ATtiny1634
┌────────────────┬────────────┐ │Microcontroller │ ATTINY1634 │ ├────────────────┼────────────┤ │Frequency       │ 8MHz       │ ├────────────────┼────────────┤ │Flash           │ 16KB       │ ├────────────────┼────────────┤ │RAM             │ 1KB        │ ├────────────────┼────────────┤ │Vendor          │ Atmel      │ └────────────────┴────────────┘
Configuration Please use attiny1634 ID for projectconf_env_board option in projectconf:
[env:attiny1634] platform = atmelavr board = attiny1634
You can override default Generic ATtiny1634 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny1634.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = attiny1634
Debugging piodebug currently does not support Generic ATtiny1634 board.
Generic ATtiny167 Contents • Generic ATtiny167
┌────────────────┬───────────┐ │Microcontroller │ ATTINY167 │ ├────────────────┼───────────┤ │Frequency       │ 8MHz      │ ├────────────────┼───────────┤ │Flash           │ 16KB      │ ├────────────────┼───────────┤ │RAM             │ 512B      │ ├────────────────┼───────────┤ │Vendor          │ Atmel     │ └────────────────┴───────────┘
Configuration Please use attiny167 ID for projectconf_env_board option in projectconf:
[env:attiny167] platform = atmelavr board = attiny167
You can override default Generic ATtiny167 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny167.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Generic ATtiny167 board.
Generic ATtiny2313 Contents • Generic ATtiny2313