neulab/tldr huggingface dataset:
┌────────────────┬─────────────┐ │Microcontroller │ ATMEGA328P  │ ├────────────────┼─────────────┤ │Frequency       │ 16MHz       │ ├────────────────┼─────────────┤ │Flash           │ 31.50KB     │ ├────────────────┼─────────────┤ │RAM             │ 2KB         │ ├────────────────┼─────────────┤ │Vendor          │ SeeedStudio │ └────────────────┴─────────────┘
Configuration Please use seeeduino ID for projectconf_env_board option in projectconf:
[env:seeeduino] platform = atmelavr board = seeeduino
You can override default Seeeduino settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeeduino.json. For example, board_build.mcu, board_build.f_cpu, etc.
Seeeduino has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun ATmega128RFA1 Dev Board Contents • SparkFun ATmega128RFA1 Dev Board
┌────────────────┬───────────────┐ │Microcontroller │ ATMEGA128RFA1 │ ├────────────────┼───────────────┤ │Frequency       │ 16MHz         │ ├────────────────┼───────────────┤ │Flash           │ 16KB          │ ├────────────────┼───────────────┤ │RAM             │ 124KB         │ └────────────────┴───────────────┘
│Vendor          │ SparkFun      │ └────────────────┴───────────────┘
Configuration Please use sparkfun_satmega128rfa1 ID for projectconf_env_board option in projectconf:
[env:sparkfun_satmega128rfa1] platform = atmelavr board = sparkfun_satmega128rfa1
You can override default SparkFun ATmega128RFA1 Dev Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_satmega128rfa1.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = atmega128rfa1
SparkFun ATmega128RFA1 Dev Board has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun Digital Sandbox Contents • SparkFun Digital Sandbox
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 8MHz       │ ├────────────────┼────────────┤ │Flash           │ 31.50KB    │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ SparkFun   │ └────────────────┴────────────┘
Configuration Please use sparkfun_digitalsandbox ID for projectconf_env_board option in projectconf:
[env:sparkfun_digitalsandbox] platform = atmelavr board = sparkfun_digitalsandbox
You can override default SparkFun Digital Sandbox settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_digitalsandbox.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun Digital Sandbox has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun Fio V3 3.3V/8MHz Contents • SparkFun Fio V3 3.3V/8MHz
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA32U4 │ ├────────────────┼────────────┤ │Frequency       │ 8MHz       │ ├────────────────┼────────────┤ │Flash           │ 28KB       │ ├────────────────┼────────────┤ │RAM             │ 2.50KB     │ ├────────────────┼────────────┤ │Vendor          │ SparkFun   │ └────────────────┴────────────┘
Configuration Please use sparkfun_fiov3 ID for projectconf_env_board option in projectconf:
[env:sparkfun_fiov3] platform = atmelavr board = sparkfun_fiov3
You can override default SparkFun Fio V3 3.3V/8MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_fiov3.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun Fio V3 3.3V/8MHz has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun Makey Makey Contents • SparkFun Makey Makey
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA32U4 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 28KB       │ ├────────────────┼────────────┤ │RAM             │ 2.50KB     │ ├────────────────┼────────────┤ │Vendor          │ SparkFun   │ └────────────────┴────────────┘
Configuration Please use sparkfun_makeymakey ID for projectconf_env_board option in projectconf:
[env:sparkfun_makeymakey] platform = atmelavr board = sparkfun_makeymakey
You can override default SparkFun Makey Makey settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_makeymakey.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun Makey Makey has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun Mega Pro 3.3V/8MHz Contents • SparkFun Mega Pro 3.3V/8MHz
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA2560 │ ├────────────────┼────────────┤ │Frequency       │ 8MHz       │ ├────────────────┼────────────┤ │Flash           │ 252KB      │ ├────────────────┼────────────┤ │RAM             │ 8KB        │ ├────────────────┼────────────┤ │Vendor          │ SparkFun   │ └────────────────┴────────────┘
Configuration Please use sparkfun_megapro8MHz ID for projectconf_env_board option in projectconf:
[env:sparkfun_megapro8MHz] platform = atmelavr board = sparkfun_megapro8MHz
You can override default SparkFun Mega Pro 3.3V/8MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_megapro8MHz.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun Mega Pro 3.3V/8MHz has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun Mega Pro 5V/16MHz Contents • SparkFun Mega Pro 5V/16MHz
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA2560 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 248KB      │ ├────────────────┼────────────┤ │RAM             │ 8KB        │ ├────────────────┼────────────┤ │Vendor          │ SparkFun   │ └────────────────┴────────────┘
Configuration Please use sparkfun_megapro16MHz ID for projectconf_env_board option in projectconf:
[env:sparkfun_megapro16MHz] platform = atmelavr board = sparkfun_megapro16MHz
You can override default SparkFun Mega Pro 5V/16MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_megapro16MHz.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun Mega Pro 5V/16MHz has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun Mega Pro Mini 3.3V Contents • SparkFun Mega Pro Mini 3.3V
Configuration Please use sparkfun_megamini ID for projectconf_env_board option in projectconf:
[env:sparkfun_megamini] platform = atmelavr board = sparkfun_megamini
You can override default SparkFun Mega Pro Mini 3.3V settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_megamini.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun Mega Pro Mini 3.3V has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun MicroView Contents • SparkFun MicroView
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 31.50KB    │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ SparkFun   │ └────────────────┴────────────┘
Configuration Please use uview ID for projectconf_env_board option in projectconf:
[env:uview] platform = atmelavr board = uview
You can override default SparkFun MicroView settings per build environment using board_*** option, where *** is a JSON object path from board manifest uview.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun MicroView has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun Pro Micro 3.3V/8MHz Contents • SparkFun Pro Micro 3.3V/8MHz
Configuration Please use sparkfun_promicro8 ID for projectconf_env_board option in projectconf:
[env:sparkfun_promicro8] platform = atmelavr board = sparkfun_promicro8
You can override default SparkFun Pro Micro 3.3V/8MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_promicro8.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun Pro Micro 3.3V/8MHz has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun Pro Micro 5V/16MHz Contents • SparkFun Pro Micro 5V/16MHz
Configuration Please use sparkfun_promicro16 ID for projectconf_env_board option in projectconf:
[env:sparkfun_promicro16] platform = atmelavr board = sparkfun_promicro16
You can override default SparkFun Pro Micro 5V/16MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_promicro16.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun Pro Micro 5V/16MHz has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun Qduino Mini Contents • SparkFun Qduino Mini
Configuration Please use sparkfun_qduinomini ID for projectconf_env_board option in projectconf:
[env:sparkfun_qduinomini] platform = atmelavr board = sparkfun_qduinomini
You can override default SparkFun Qduino Mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_qduinomini.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun Qduino Mini has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun RedBoard Contents • SparkFun RedBoard
Configuration Please use sparkfun_redboard ID for projectconf_env_board option in projectconf:
[env:sparkfun_redboard] platform = atmelavr board = sparkfun_redboard
You can override default SparkFun RedBoard settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_redboard.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun RedBoard has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun Serial 7-Segment Display Contents • SparkFun Serial 7-Segment Display
Configuration Please use sparkfun_serial7seg ID for projectconf_env_board option in projectconf:
[env:sparkfun_serial7seg] platform = atmelavr board = sparkfun_serial7seg
You can override default SparkFun Serial 7-Segment Display settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_serial7seg.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun Serial 7-Segment Display has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SpellFoundry Sleepy Pi 2 Contents • SpellFoundry Sleepy Pi 2
┌────────────────┬──────────────┐ │Microcontroller │ ATMEGA328P   │ ├────────────────┼──────────────┤ │Frequency       │ 8MHz         │ ├────────────────┼──────────────┤ │Flash           │ 30KB         │ ├────────────────┼──────────────┤ │RAM             │ 2KB          │ ├────────────────┼──────────────┤ │Vendor          │ SpellFoundry │ └────────────────┴──────────────┘
Configuration Please use sleepypi ID for projectconf_env_board option in projectconf:
[env:sleepypi] platform = atmelavr board = sleepypi
You can override default SpellFoundry Sleepy Pi 2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest sleepypi.json. For example, board_build.mcu, board_build.f_cpu, etc.
SpellFoundry Sleepy Pi 2 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Talk2 Whisper Node Contents • Talk2 Whisper Node
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 31.50KB    │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ Wisen      │ └────────────────┴────────────┘
Configuration Please use whispernode ID for projectconf_env_board option in projectconf:
[env:whispernode] platform = atmelavr board = whispernode
You can override default Talk2 Whisper Node settings per build environment using board_*** option, where *** is a JSON object path from board manifest whispernode.json. For example, board_build.mcu, board_build.f_cpu, etc.
Talk2 Whisper Node has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
The Things Uno Contents • The Things Uno
┌────────────────┬────────────────────┐ │Microcontroller │ ATMEGA32U4         │ ├────────────────┼────────────────────┤ │Frequency       │ 16MHz              │ ├────────────────┼────────────────────┤ │Flash           │ 28KB               │ ├────────────────┼────────────────────┤ │RAM             │ 2.50KB             │ ├────────────────┼────────────────────┤ │Vendor          │ The Things Network │ └────────────────┴────────────────────┘
Configuration Please use the_things_uno ID for projectconf_env_board option in projectconf:
[env:the_things_uno] platform = atmelavr board = the_things_uno
You can override default The Things Uno settings per build environment using board_*** option, where *** is a JSON object path from board manifest the_things_uno.json. For example, board_build.mcu, board_build.f_cpu, etc.
The Things Uno has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
TinyCircuits TinyDuino Processor Board Contents • TinyCircuits TinyDuino Processor Board
┌────────────────┬──────────────┐ │Microcontroller │ ATMEGA328P   │ ├────────────────┼──────────────┤ │Frequency       │ 8MHz         │ ├────────────────┼──────────────┤ │Flash           │ 30KB         │ ├────────────────┼──────────────┤ │RAM             │ 2KB          │ ├────────────────┼──────────────┤ │Vendor          │ TinyCircuits │ └────────────────┴──────────────┘
Configuration Please use tinyduino ID for projectconf_env_board option in projectconf:
[env:tinyduino] platform = atmelavr board = tinyduino
You can override default TinyCircuits TinyDuino Processor Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest tinyduino.json. For example, board_build.mcu, board_build.f_cpu, etc.
TinyCircuits TinyDuino Processor Board has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
TinyCircuits TinyLily Mini Processor Contents • TinyCircuits TinyLily Mini Processor
Configuration Please use tinylily ID for projectconf_env_board option in projectconf:
[env:tinylily] platform = atmelavr board = tinylily
You can override default TinyCircuits TinyLily Mini Processor settings per build environment using board_*** option, where *** is a JSON object path from board manifest tinylily.json. For example, board_build.mcu, board_build.f_cpu, etc.
TinyCircuits TinyLily Mini Processor has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
USBasp stick Contents • USBasp stick
┌────────────────┬─────────┐ │Microcontroller │ ATMEGA8 │ ├────────────────┼─────────┤ │Frequency       │ 12MHz   │ ├────────────────┼─────────┤ │Flash           │ 8KB     │ ├────────────────┼─────────┤ │RAM             │ 1KB     │ ├────────────────┼─────────┤ │Vendor          │ Atmel   │ └────────────────┴─────────┘
Configuration Please use usbasp ID for projectconf_env_board option in projectconf:
[env:usbasp] platform = atmelavr board = usbasp
You can override default USBasp stick settings per build environment using board_*** option, where *** is a JSON object path from board manifest usbasp.json. For example, board_build.mcu, board_build.f_cpu, etc.
USBasp stick has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Wicked Device WildFire V2 Contents • Wicked Device WildFire V2
┌────────────────┬───────────────┐ │Microcontroller │ ATMEGA1284P   │ ├────────────────┼───────────────┤ │Frequency       │ 16MHz         │ ├────────────────┼───────────────┤ │Flash           │ 120.00KB      │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ Wicked Device │ └────────────────┴───────────────┘
Configuration Please use wildfirev2 ID for projectconf_env_board option in projectconf:
[env:wildfirev2] platform = atmelavr board = wildfirev2
You can override default Wicked Device WildFire V2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest wildfirev2.json. For example, board_build.mcu, board_build.f_cpu, etc.
Wicked Device WildFire V2 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Wicked Device WildFire V3 Contents • Wicked Device WildFire V3
┌────────────────┬───────────────┐ │Microcontroller │ ATMEGA1284P   │ ├────────────────┼───────────────┤ │Frequency       │ 16MHz         │ ├────────────────┼───────────────┤ │Flash           │ 127KB         │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ Wicked Device │ └────────────────┴───────────────┘
Configuration Please use wildfirev3 ID for projectconf_env_board option in projectconf:
[env:wildfirev3] platform = atmelavr board = wildfirev3
You can override default Wicked Device WildFire V3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest wildfirev3.json. For example, board_build.mcu, board_build.f_cpu, etc.
Wicked Device WildFire V3 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ftDuino Contents • ftDuino
┌────────────────┬──────────────┐ │Microcontroller │ ATMEGA32U4   │ ├────────────────┼──────────────┤ │Frequency       │ 16MHz        │ ├────────────────┼──────────────┤ │Flash           │ 28KB         │ ├────────────────┼──────────────┤ │RAM             │ 2.50KB       │ ├────────────────┼──────────────┤ │Vendor          │ Till Harbaum │ └────────────────┴──────────────┘
Configuration Please use ftduino ID for projectconf_env_board option in projectconf:
[env:ftduino] platform = atmelavr board = ftduino
You can override default ftDuino settings per build environment using board_*** option, where *** is a JSON object path from board manifest ftduino.json. For example, board_build.mcu, board_build.f_cpu, etc.
ftDuino has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
nicai-systems BOB3 coding bot Contents • nicai-systems BOB3 coding bot
┌────────────────┬───────────────┐ │Microcontroller │ ATMEGA88      │ ├────────────────┼───────────────┤ │Frequency       │ 8MHz          │ ├────────────────┼───────────────┤ │Flash           │ 8KB           │ ├────────────────┼───────────────┤ │RAM             │ 1KB           │ ├────────────────┼───────────────┤ │Vendor          │ nicai-systems │ └────────────────┴───────────────┘
Configuration Please use bob3 ID for projectconf_env_board option in projectconf:
[env:bob3] platform = atmelavr board = bob3
You can override default nicai-systems BOB3 coding bot settings per build environment using board_*** option, where *** is a JSON object path from board manifest bob3.json. For example, board_build.mcu, board_build.f_cpu, etc.
nicai-systems BOB3 coding bot has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
nicai-systems NIBO 2 robot Contents • nicai-systems NIBO 2 robot
┌────────────────┬───────────────┐ │Microcontroller │ ATMEGA128     │ ├────────────────┼───────────────┤ │Frequency       │ 16MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 4KB           │ ├────────────────┼───────────────┤ │Vendor          │ nicai-systems │ └────────────────┴───────────────┘
Configuration Please use nibo2 ID for projectconf_env_board option in projectconf:
[env:nibo2] platform = atmelavr board = nibo2
You can override default nicai-systems NIBO 2 robot settings per build environment using board_*** option, where *** is a JSON object path from board manifest nibo2.json. For example, board_build.mcu, board_build.f_cpu, etc.
nicai-systems NIBO 2 robot has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
nicai-systems NIBO burger robot Contents • nicai-systems NIBO burger robot
┌────────────────┬───────────────┐ │Microcontroller │ ATMEGA16      │ └────────────────┴───────────────┘
│Frequency       │ 15MHz         │ ├────────────────┼───────────────┤ │Flash           │ 16KB          │ ├────────────────┼───────────────┤ │RAM             │ 1KB           │ ├────────────────┼───────────────┤ │Vendor          │ nicai-systems │ └────────────────┴───────────────┘
Configuration Please use niboburger ID for projectconf_env_board option in projectconf:
[env:niboburger] platform = atmelavr board = niboburger
You can override default nicai-systems NIBO burger robot settings per build environment using board_*** option, where *** is a JSON object path from board manifest niboburger.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change MCU frequency board_build.f_cpu = 15000000L
nicai-systems NIBO burger robot has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
nicai-systems NIBO burger robot with Tuning Kit Contents • nicai-systems NIBO burger robot with Tuning Kit
┌────────────────┬───────────────┐ │Microcontroller │ ATMEGA1284P   │ ├────────────────┼───────────────┤ │Frequency       │ 20MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ nicai-systems │ └────────────────┴───────────────┘
Configuration Please use niboburger_1284 ID for projectconf_env_board option in projectconf:
[env:niboburger_1284] platform = atmelavr board = niboburger_1284
You can override default nicai-systems NIBO burger robot with Tuning Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest niboburger_1284.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change MCU frequency board_build.f_cpu = 20000000L
nicai-systems NIBO burger robot with Tuning Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
nicai-systems NIBObee robot Contents • nicai-systems NIBObee robot
Configuration Please use nibobee ID for projectconf_env_board option in projectconf:
[env:nibobee] platform = atmelavr board = nibobee
You can override default nicai-systems NIBObee robot settings per build environment using board_*** option, where *** is a JSON object path from board manifest nibobee.json. For example, board_build.mcu, board_build.f_cpu, etc.
nicai-systems NIBObee robot has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
nicai-systems NIBObee robot with Tuning Kit Contents • nicai-systems NIBObee robot with Tuning Kit
Configuration Please use nibobee_1284 ID for projectconf_env_board option in projectconf:
[env:nibobee_1284] platform = atmelavr board = nibobee_1284
You can override default nicai-systems NIBObee robot with Tuning Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest nibobee_1284.json. For example, board_build.mcu, board_build.f_cpu, etc.
nicai-systems NIBObee robot with Tuning Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ubIQio Ardhat Contents • ubIQio Ardhat
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA328P │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ └────────────────┴────────────┘
│Flash           │ 31.50KB    │ ├────────────────┼────────────┤ │RAM             │ 2KB        │ ├────────────────┼────────────┤ │Vendor          │ ubIQio     │ └────────────────┴────────────┘
Configuration Please use ardhat ID for projectconf_env_board option in projectconf:
[env:ardhat] platform = atmelavr board = ardhat
You can override default ubIQio Ardhat settings per build environment using board_*** option, where *** is a JSON object path from board manifest ardhat.json. For example, board_build.mcu, board_build.f_cpu, etc.
ubIQio Ardhat has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Atmel megaAVR Arduino Nano Every Contents • Arduino Nano Every
Hardware Platform platform_atmelmegaavr: 8-bit MCUs Built for Real-time Control with Core Independent Peripherals combining intelligent hardware peripherals along with the low-power capability of an AVR core, megaAVR microcontrollers (MCUs) broaden the effectiveness of your real-time control systems.
┌────────────────┬────────────┐ │Microcontroller │ ATMEGA4809 │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 47.50KB    │ ├────────────────┼────────────┤ │RAM             │ 6KB        │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use nano_every ID for projectconf_env_board option in projectconf:
[env:nano_every] platform = atmelmegaavr board = nano_every
You can override default Arduino Nano Every settings per build environment using board_*** option, where *** is a JSON object path from board manifest nano_every.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = atmega4809
Debugging piodebug currently does not support Arduino Nano Every board.
Arduino Uno WiFi Rev2 Contents • Arduino Uno WiFi Rev2
Configuration Please use uno_wifi_rev2 ID for projectconf_env_board option in projectconf:
[env:uno_wifi_rev2] platform = atmelmegaavr board = uno_wifi_rev2
You can override default Arduino Uno WiFi Rev2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest uno_wifi_rev2.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Arduino Uno WiFi Rev2 board.
Atmel SAM Adafruit Circuit Playground Express Contents • Adafruit Circuit Playground Express
Hardware Platform platform_atmelsam: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
┌────────────────┬────────────┐ │Microcontroller │ SAMD21G18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use adafruit_circuitplayground_m0 ID for projectconf_env_board option in projectconf:
[env:adafruit_circuitplayground_m0] platform = atmelsam board = adafruit_circuitplayground_m0
You can override default Adafruit Circuit Playground Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_circuitplayground_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = samd21g18a
; change MCU frequency board_build.f_cpu = 48000000L
Uploading Adafruit Circuit Playground Express supports the next uploading protocols:
• atmel-ice
• sam-ba
Default protocol is sam-ba
upload_protocol = sam-ba
Adafruit Circuit Playground Express does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
┌──────────────────────────┬──────────┬─────────┐ │Compatible Tools          │ On-board │ Default │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_atmel-ice  │          │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_blackmagic │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ └──────────────────────────┴──────────┴─────────┘
Adafruit Crickit M0 Contents • Adafruit Crickit M0
Configuration Please use adafruit_crickit_m0 ID for projectconf_env_board option in projectconf:
[env:adafruit_crickit_m0] platform = atmelsam board = adafruit_crickit_m0
You can override default Adafruit Crickit M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_crickit_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Crickit M0 supports the next uploading protocols:
Adafruit Crickit M0 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Feather M0 Contents • Adafruit Feather M0
Configuration Please use adafruit_feather_m0 ID for projectconf_env_board option in projectconf:
[env:adafruit_feather_m0] platform = atmelsam board = adafruit_feather_m0
You can override default Adafruit Feather M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Feather M0 supports the next uploading protocols:
Adafruit Feather M0 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
┌──────────────────────────┬──────────┬─────────┐ │Compatible Tools          │ On-board │ Default │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_atmel-ice  │          │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_blackmagic │          │         │ └──────────────────────────┴──────────┴─────────┘
│debugging_tool_jlink      │          │         │ └──────────────────────────┴──────────┴─────────┘
Frameworks ┌──────────────────┬─────────────────────────────┐ │Name              │ Description                 │ ├──────────────────┼─────────────────────────────┤ │framework_arduino │ Arduino Wiring-based        │ │                  │ Framework allows writing    │ │                  │ cross-platform software to  │ │                  │ control devices attached to │ │                  │ a wide range of Arduino     │ │                  │ boards to create all kinds  │ │                  │ of creative coding,         │ │                  │ interactive objects, spaces │ │                  │ or physical experiences.    │ ├──────────────────┼─────────────────────────────┤ │framework_zephyr  │ The Zephyr Project is a     │ │                  │ scalable real-time          │ │                  │ operating system (RTOS)     │ │                  │ supporting multiple         │ │                  │ hardware architectures,     │ │                  │ optimized for resource      │ │                  │ constrained devices, and    │ │                  │ built with safety and       │ │                  │ security in mind.           │ └──────────────────┴─────────────────────────────┘
Adafruit Feather M0 Express Contents • Adafruit Feather M0 Express
Configuration Please use adafruit_feather_m0_express ID for projectconf_env_board option in projectconf:
[env:adafruit_feather_m0_express] platform = atmelsam board = adafruit_feather_m0_express
You can override default Adafruit Feather M0 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_m0_express.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Feather M0 Express supports the next uploading protocols:
Adafruit Feather M0 Express does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Feather M4 Express Contents • Adafruit Feather M4 Express
┌────────────────┬────────────┐ │Microcontroller │ SAMD51J19A │ ├────────────────┼────────────┤ │Frequency       │ 120MHz     │ ├────────────────┼────────────┤ │Flash           │ 512KB      │ ├────────────────┼────────────┤ │RAM             │ 192KB      │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use adafruit_feather_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_feather_m4] platform = atmelsam board = adafruit_feather_m4
You can override default Adafruit Feather M4 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = samd51j19a
Uploading Adafruit Feather M4 Express supports the next uploading protocols:
Adafruit Feather M4 Express does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
┌─────────────────────────┬──────────┬─────────┐ │Compatible Tools         │ On-board │ Default │ ├─────────────────────────┼──────────┼─────────┤ │debugging_tool_atmel-ice │          │ Yes     │ ├─────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink     │          │         │ └─────────────────────────┴──────────┴─────────┘
Adafruit Gemma M0 Contents • Adafruit Gemma M0
┌────────────────┬────────────┐ │Microcontroller │ SAMD21E18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use adafruit_gemma_m0 ID for projectconf_env_board option in projectconf:
[env:adafruit_gemma_m0] platform = atmelsam board = adafruit_gemma_m0
You can override default Adafruit Gemma M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_gemma_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = samd21e18a
Uploading Adafruit Gemma M0 supports the next uploading protocols:
Adafruit Gemma M0 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Grand Central M4 Contents • Adafruit Grand Central M4
┌────────────────┬────────────┐ │Microcontroller │ SAMD51P20A │ ├────────────────┼────────────┤ │Frequency       │ 120MHz     │ ├────────────────┼────────────┤ │Flash           │ 1MB        │ ├────────────────┼────────────┤ │RAM             │ 256KB      │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use adafruit_grandcentral_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_grandcentral_m4] platform = atmelsam board = adafruit_grandcentral_m4
You can override default Adafruit Grand Central M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_grandcentral_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = samd51p20a
Uploading Adafruit Grand Central M4 supports the next uploading protocols:
Adafruit Grand Central M4 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Hallowing M0 Contents • Adafruit Hallowing M0
Configuration Please use adafruit_hallowing ID for projectconf_env_board option in projectconf:
[env:adafruit_hallowing] platform = atmelsam board = adafruit_hallowing
You can override default Adafruit Hallowing M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_hallowing.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Hallowing M0 supports the next uploading protocols:
Adafruit Hallowing M0 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Hallowing M4 Contents • Adafruit Hallowing M4
┌────────────────┬────────────┐ │Microcontroller │ SAMD51J19A │ ├────────────────┼────────────┤ │Frequency       │ 120MHz     │ ├────────────────┼────────────┤ │Flash           │ 496KB      │ ├────────────────┼────────────┤ │RAM             │ 192KB      │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use adafruit_hallowing_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_hallowing_m4] platform = atmelsam board = adafruit_hallowing_m4
You can override default Adafruit Hallowing M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_hallowing_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Hallowing M4 supports the next uploading protocols:
Adafruit Hallowing M4 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit ItsyBitsy M0 Contents • Adafruit ItsyBitsy M0
Configuration Please use adafruit_itsybitsy_m0 ID for projectconf_env_board option in projectconf:
[env:adafruit_itsybitsy_m0] platform = atmelsam board = adafruit_itsybitsy_m0
You can override default Adafruit ItsyBitsy M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_itsybitsy_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit ItsyBitsy M0 supports the next uploading protocols:
Adafruit ItsyBitsy M0 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit ItsyBitsy M4 Contents • Adafruit ItsyBitsy M4
┌────────────────┬────────────┐ │Microcontroller │ SAMD51G19A │ ├────────────────┼────────────┤ │Frequency       │ 120MHz     │ ├────────────────┼────────────┤ │Flash           │ 512KB      │ ├────────────────┼────────────┤ │RAM             │ 192KB      │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use adafruit_itsybitsy_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_itsybitsy_m4] platform = atmelsam board = adafruit_itsybitsy_m4
You can override default Adafruit ItsyBitsy M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_itsybitsy_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = samd51g19a
Uploading Adafruit ItsyBitsy M4 supports the next uploading protocols:
Adafruit ItsyBitsy M4 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit MONSTER M4SK Contents • Adafruit MONSTER M4SK
┌────────────────┬────────────┐ │Microcontroller │ SAMD51G19A │ ├────────────────┼────────────┤ │Frequency       │ 120MHz     │ ├────────────────┼────────────┤ │Flash           │ 496KB      │ ├────────────────┼────────────┤ │RAM             │ 192KB      │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use adafruit_monster_m4sk ID for projectconf_env_board option in projectconf:
[env:adafruit_monster_m4sk] platform = atmelsam board = adafruit_monster_m4sk
You can override default Adafruit MONSTER M4SK settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_monster_m4sk.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit MONSTER M4SK supports the next uploading protocols:
Adafruit MONSTER M4SK does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Metro M0 Expresss Contents • Adafruit Metro M0 Expresss
Configuration Please use adafruit_metro_m0 ID for projectconf_env_board option in projectconf:
[env:adafruit_metro_m0] platform = atmelsam board = adafruit_metro_m0
You can override default Adafruit Metro M0 Expresss settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_metro_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Metro M0 Expresss supports the next uploading protocols:
Adafruit Metro M0 Expresss does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Metro M4 Contents • Adafruit Metro M4
Configuration Please use adafruit_metro_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_metro_m4] platform = atmelsam board = adafruit_metro_m4
You can override default Adafruit Metro M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_metro_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Metro M4 supports the next uploading protocols:
Adafruit Metro M4 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Metro M4 AirLift Lite Contents • Adafruit Metro M4 AirLift Lite
Configuration Please use adafruit_metro_m4_airliftlite ID for projectconf_env_board option in projectconf:
[env:adafruit_metro_m4_airliftlite] platform = atmelsam board = adafruit_metro_m4_airliftlite
You can override default Adafruit Metro M4 AirLift Lite settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_metro_m4_airliftlite.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Metro M4 AirLift Lite supports the next uploading protocols:
Adafruit Metro M4 AirLift Lite does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit PyGamer Advance M4 Contents • Adafruit PyGamer Advance M4
┌────────────────┬────────────┐ │Microcontroller │ SAMD51J20A │ ├────────────────┼────────────┤ │Frequency       │ 120MHz     │ ├────────────────┼────────────┤ │Flash           │ 1MB        │ ├────────────────┼────────────┤ │RAM             │ 256KB      │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use adafruit_pygamer_advance_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_pygamer_advance_m4] platform = atmelsam board = adafruit_pygamer_advance_m4
You can override default Adafruit PyGamer Advance M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pygamer_advance_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = samd51j20a
Uploading Adafruit PyGamer Advance M4 supports the next uploading protocols:
Adafruit PyGamer Advance M4 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit PyGamer M4 Express Contents • Adafruit PyGamer M4 Express
Configuration Please use adafruit_pygamer_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_pygamer_m4] platform = atmelsam board = adafruit_pygamer_m4
You can override default Adafruit PyGamer M4 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pygamer_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit PyGamer M4 Express supports the next uploading protocols:
Adafruit PyGamer M4 Express does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit PyPortal M4 Contents • Adafruit PyPortal M4
Configuration Please use adafruit_pyportal_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_pyportal_m4] platform = atmelsam board = adafruit_pyportal_m4
You can override default Adafruit PyPortal M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pyportal_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit PyPortal M4 supports the next uploading protocols:
Adafruit PyPortal M4 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit PyPortal M4 Titano Contents • Adafruit PyPortal M4 Titano
Configuration Please use adafruit_pyportal_m4_titano ID for projectconf_env_board option in projectconf:
[env:adafruit_pyportal_m4_titano] platform = atmelsam board = adafruit_pyportal_m4_titano
You can override default Adafruit PyPortal M4 Titano settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pyportal_m4_titano.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit PyPortal M4 Titano supports the next uploading protocols:
Adafruit PyPortal M4 Titano does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Trellis M4 Contents • Adafruit Trellis M4
Configuration Please use adafruit_trellis_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_trellis_m4] platform = atmelsam board = adafruit_trellis_m4
You can override default Adafruit Trellis M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_trellis_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Trellis M4 supports the next uploading protocols:
Adafruit Trellis M4 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Trinket M0 Contents • Adafruit Trinket M0
Configuration Please use adafruit_trinket_m0 ID for projectconf_env_board option in projectconf:
[env:adafruit_trinket_m0] platform = atmelsam board = adafruit_trinket_m0
You can override default Adafruit Trinket M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_trinket_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Trinket M0 supports the next uploading protocols:
Adafruit Trinket M0 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit pIRkey Contents • Adafruit pIRkey
Configuration Please use adafruit_pirkey ID for projectconf_env_board option in projectconf:
[env:adafruit_pirkey] platform = atmelsam board = adafruit_pirkey
You can override default Adafruit pIRkey settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pirkey.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit pIRkey supports the next uploading protocols:
Adafruit pIRkey does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit pyBadge AirLift M4 Contents • Adafruit pyBadge AirLift M4
┌────────────────┬────────────┐ │Microcontroller │ SAMD51J20A │ ├────────────────┼────────────┤ │Frequency       │ 120MHz     │ ├────────────────┼────────────┤ │Flash           │ 1008KB     │ ├────────────────┼────────────┤ │RAM             │ 192KB      │ ├────────────────┼────────────┤ │Vendor          │ Adafruit   │ └────────────────┴────────────┘
Configuration Please use adafruit_pybadge_airlift_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_pybadge_airlift_m4] platform = atmelsam board = adafruit_pybadge_airlift_m4
You can override default Adafruit pyBadge AirLift M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pybadge_airlift_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.