neulab/tldr huggingface dataset:
Uploading Adafruit pyBadge AirLift M4 supports the next uploading protocols:
Adafruit pyBadge AirLift 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 pyBadge M4 Express Contents • Adafruit pyBadge M4 Express
Configuration Please use adafruit_pybadge_m4 ID for projectconf_env_board option in projectconf:
[env:adafruit_pybadge_m4] platform = atmelsam board = adafruit_pybadge_m4
You can override default Adafruit pyBadge M4 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pybadge_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit pyBadge M4 Express supports the next uploading protocols:
Adafruit pyBadge 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.
Arduino Due (Programming Port) Contents • Arduino Due (Programming Port)
┌────────────────┬─────────────┐ │Microcontroller │ AT91SAM3X8E │ ├────────────────┼─────────────┤ │Frequency       │ 84MHz       │ ├────────────────┼─────────────┤ │Flash           │ 512KB       │ ├────────────────┼─────────────┤ │RAM             │ 96KB        │ ├────────────────┼─────────────┤ │Vendor          │ Arduino     │ └────────────────┴─────────────┘
Configuration Please use due ID for projectconf_env_board option in projectconf:
[env:due] platform = atmelsam board = due
You can override default Arduino Due (Programming Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest due.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = at91sam3x8e
; change MCU frequency board_build.f_cpu = 84000000L
Uploading Arduino Due (Programming Port) supports the next uploading protocols:
Arduino Due (Programming Port) 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      │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_stlink     │          │         │ └──────────────────────────┴──────────┴─────────┘
│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.           │ └──────────────────┴─────────────────────────────┘
Arduino Due (USB Native Port) Contents • Arduino Due (USB Native Port)
Configuration Please use dueUSB ID for projectconf_env_board option in projectconf:
[env:dueUSB] platform = atmelsam board = dueUSB
You can override default Arduino Due (USB Native Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest dueUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino Due (USB Native Port) supports the next uploading protocols:
Arduino Due (USB Native Port) 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.
Arduino M0 Contents • Arduino M0
┌────────────────┬────────────┐ │Microcontroller │ SAMD21G18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use mzeroUSB ID for projectconf_env_board option in projectconf:
[env:mzeroUSB] platform = atmelsam board = mzeroUSB
You can override default Arduino M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mzeroUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino M0 supports the next uploading protocols:
• stk500v2
Default protocol is stk500v2
upload_protocol = stk500v2
Arduino 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.
Arduino M0 Pro (Native USB Port) Contents • Arduino M0 Pro (Native USB Port)
Configuration Please use mzeroproUSB ID for projectconf_env_board option in projectconf:
[env:mzeroproUSB] platform = atmelsam board = mzeroproUSB
You can override default Arduino M0 Pro (Native USB Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest mzeroproUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino M0 Pro (Native USB Port) supports the next uploading protocols:
Arduino M0 Pro (Native USB Port) 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.
Arduino M0 Pro (Programming/Debug Port) Contents • Arduino M0 Pro (Programming/Debug Port)
Configuration Please use mzeropro ID for projectconf_env_board option in projectconf:
[env:mzeropro] platform = atmelsam board = mzeropro
You can override default Arduino M0 Pro (Programming/Debug Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest mzeropro.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino M0 Pro (Programming/Debug Port) supports the next uploading protocols:
• cmsis-dap
Default protocol is cmsis-dap
upload_protocol = cmsis-dap
Arduino M0 Pro (Programming/Debug Port) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
┌──────────────────────────┬──────────┬─────────┐ │Compatible Tools          │ On-board │ Default │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_atmel-ice  │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_blackmagic │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_cmsis-dap  │ Yes      │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ └──────────────────────────┴──────────┴─────────┘
Arduino MKR FOX 1200 Contents • Arduino MKR FOX 1200
Configuration Please use mkrfox1200 ID for projectconf_env_board option in projectconf:
[env:mkrfox1200] platform = atmelsam board = mkrfox1200
You can override default Arduino MKR FOX 1200 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrfox1200.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino MKR FOX 1200 supports the next uploading protocols:
Arduino MKR FOX 1200 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.
Arduino MKR GSM 1400 Contents • Arduino MKR GSM 1400
Configuration Please use mkrgsm1400 ID for projectconf_env_board option in projectconf:
[env:mkrgsm1400] platform = atmelsam board = mkrgsm1400
You can override default Arduino MKR GSM 1400 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrgsm1400.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino MKR GSM 1400 supports the next uploading protocols:
Arduino MKR GSM 1400 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.
Arduino MKR NB 1500 Contents • Arduino MKR NB 1500
┌────────────────┬────────────┐ │Microcontroller │ SAMD21G18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ └────────────────┴────────────┘
│Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use mkrnb1500 ID for projectconf_env_board option in projectconf:
[env:mkrnb1500] platform = atmelsam board = mkrnb1500
You can override default Arduino MKR NB 1500 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrnb1500.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino MKR NB 1500 supports the next uploading protocols:
Arduino MKR NB 1500 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.
Arduino MKR WAN 1300 Contents • Arduino MKR WAN 1300
Configuration Please use mkrwan1300 ID for projectconf_env_board option in projectconf:
[env:mkrwan1300] platform = atmelsam board = mkrwan1300
You can override default Arduino MKR WAN 1300 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrwan1300.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino MKR WAN 1300 supports the next uploading protocols:
Arduino MKR WAN 1300 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      │          │         │ └──────────────────────────┴──────────┴─────────┘
Arduino MKR WAN 1310 Contents • Arduino MKR WAN 1310
Configuration Please use mkrwan1310 ID for projectconf_env_board option in projectconf:
[env:mkrwan1310] platform = atmelsam board = mkrwan1310
You can override default Arduino MKR WAN 1310 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrwan1310.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino MKR WAN 1310 supports the next uploading protocols:
Arduino MKR WAN 1310 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.
Arduino MKR WiFi 1010 Contents • Arduino MKR WiFi 1010
Configuration Please use mkrwifi1010 ID for projectconf_env_board option in projectconf:
[env:mkrwifi1010] platform = atmelsam board = mkrwifi1010
You can override default Arduino MKR WiFi 1010 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrwifi1010.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino MKR WiFi 1010 supports the next uploading protocols:
Arduino MKR WiFi 1010 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.
Arduino MKR1000 Contents • Arduino MKR1000
Configuration Please use mkr1000USB ID for projectconf_env_board option in projectconf:
[env:mkr1000USB] platform = atmelsam board = mkr1000USB
You can override default Arduino MKR1000 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkr1000USB.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino MKR1000 supports the next uploading protocols:
Arduino MKR1000 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.
Arduino MKRZERO Contents • Arduino MKRZERO
Configuration Please use mkrzero ID for projectconf_env_board option in projectconf:
[env:mkrzero] platform = atmelsam board = mkrzero
You can override default Arduino MKRZERO settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrzero.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino MKRZERO supports the next uploading protocols:
Arduino MKRZERO 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.
Arduino Tian Contents • Arduino Tian
Configuration Please use tian ID for projectconf_env_board option in projectconf:
[env:tian] platform = atmelsam board = tian
You can override default Arduino Tian settings per build environment using board_*** option, where *** is a JSON object path from board manifest tian.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino Tian supports the next uploading protocols:
Arduino Tian 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.
Arduino Zero (Programming/Debug Port) Contents • Arduino Zero (Programming/Debug Port)
Configuration Please use zero ID for projectconf_env_board option in projectconf:
[env:zero] platform = atmelsam board = zero
You can override default Arduino Zero (Programming/Debug Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest zero.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino Zero (Programming/Debug Port) supports the next uploading protocols:
Arduino Zero (Programming/Debug Port) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Arduino Zero (USB Native Port) Contents • Arduino Zero (USB Native Port)
┌────────────────┬────────────┐ │Microcontroller │ SAMD21G18A │ └────────────────┴────────────┘
│Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Arduino    │ └────────────────┴────────────┘
Configuration Please use zeroUSB ID for projectconf_env_board option in projectconf:
[env:zeroUSB] platform = atmelsam board = zeroUSB
You can override default Arduino Zero (USB Native Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest zeroUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino Zero (USB Native Port) supports the next uploading protocols:
Arduino Zero (USB Native Port) 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.
Atmel ATSAMR21-XPRO Contents • Atmel ATSAMR21-XPRO
┌────────────────┬────────────┐ │Microcontroller │ SAMR21G18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Atmel      │ └────────────────┴────────────┘
Configuration Please use samr21_xpro ID for projectconf_env_board option in projectconf:
[env:samr21_xpro] platform = atmelsam board = samr21_xpro
You can override default Atmel ATSAMR21-XPRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest samr21_xpro.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = samr21g18a
Uploading Atmel ATSAMR21-XPRO supports the next uploading protocols:
Atmel ATSAMR21-XPRO has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
│debugging_tool_atmel-ice  │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_blackmagic │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_cmsis-dap  │ Yes      │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ └──────────────────────────┴──────────┴─────────┘
Atmel ATSAMW25-XPRO Contents • Atmel ATSAMW25-XPRO
┌────────────────┬────────────┐ │Microcontroller │ SAMD21G18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Atmel      │ └────────────────┴────────────┘
Configuration Please use samd21g18a ID for projectconf_env_board option in projectconf:
[env:samd21g18a] platform = atmelsam board = samd21g18a
You can override default Atmel ATSAMW25-XPRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest samd21g18a.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Atmel ATSAMW25-XPRO supports the next uploading protocols:
Atmel ATSAMW25-XPRO has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Atmel SAMC21-XPRO Contents • Atmel SAMC21-XPRO
┌────────────────┬────────────┐ │Microcontroller │ SAMC21J18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Atmel      │ └────────────────┴────────────┘
Configuration Please use samc21_xpro ID for projectconf_env_board option in projectconf:
[env:samc21_xpro] platform = atmelsam board = samc21_xpro
You can override default Atmel SAMC21-XPRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest samc21_xpro.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = samc21j18a
Uploading Atmel SAMC21-XPRO supports the next uploading protocols:
Atmel SAMC21-XPRO has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Atmel SAMD21-XPRO Contents • Atmel SAMD21-XPRO
┌────────────────┬────────────┐ │Microcontroller │ SAMD21J18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Atmel      │ └────────────────┴────────────┘
Configuration Please use samd21_xpro ID for projectconf_env_board option in projectconf:
[env:samd21_xpro] platform = atmelsam board = samd21_xpro
You can override default Atmel SAMD21-XPRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest samd21_xpro.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = samd21j18a
Uploading Atmel SAMD21-XPRO supports the next uploading protocols:
Atmel SAMD21-XPRO has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
┌──────────────────────────┬──────────┬─────────┐ │Compatible Tools          │ On-board │ Default │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_atmel-ice  │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_blackmagic │          │         │ └──────────────────────────┴──────────┴─────────┘
│debugging_tool_cmsis-dap  │ Yes      │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ └──────────────────────────┴──────────┴─────────┘
Atmel SAML21-XPRO-B Contents • Atmel SAML21-XPRO-B
┌────────────────┬────────────┐ │Microcontroller │ SAML21J18B │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Atmel      │ └────────────────┴────────────┘
Configuration Please use saml21_xpro_b ID for projectconf_env_board option in projectconf:
[env:saml21_xpro_b] platform = atmelsam board = saml21_xpro_b
You can override default Atmel SAML21-XPRO-B settings per build environment using board_*** option, where *** is a JSON object path from board manifest saml21_xpro_b.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = saml21j18b
Uploading Atmel SAML21-XPRO-B supports the next uploading protocols:
Atmel SAML21-XPRO-B has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Briki ABC (MBC-WB) - Samd21 Contents • Briki ABC (MBC-WB) - Samd21
┌────────────────┬────────────┐ │Microcontroller │ SAMD21G18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ meteca     │ └────────────────┴────────────┘
Configuration Please use briki_abc_samd21 ID for projectconf_env_board option in projectconf:
[env:briki_abc_samd21] platform = atmelsam board = briki_abc_samd21
You can override default Briki ABC (MBC-WB) - Samd21 settings per build environment using board_*** option, where *** is a JSON object path from board manifest briki_abc_samd21.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Briki ABC (MBC-WB) - Samd21 supports the next uploading protocols:
• mbctool
Default protocol is mbctool
upload_protocol = mbctool
Briki ABC (MBC-WB) - Samd21 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.
Briki MBC-WB - Samd21 Contents • Briki MBC-WB - Samd21
Configuration Please use briki_mbcwb_samd21 ID for projectconf_env_board option in projectconf:
[env:briki_mbcwb_samd21] platform = atmelsam board = briki_mbcwb_samd21
You can override default Briki MBC-WB - Samd21 settings per build environment using board_*** option, where *** is a JSON object path from board manifest briki_mbcwb_samd21.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Briki MBC-WB - Samd21 supports the next uploading protocols:
Briki MBC-WB - Samd21 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.
Digistump DigiX Contents • Digistump DigiX
┌────────────────┬─────────────┐ │Microcontroller │ AT91SAM3X8E │ ├────────────────┼─────────────┤ │Frequency       │ 84MHz       │ ├────────────────┼─────────────┤ │Flash           │ 512KB       │ ├────────────────┼─────────────┤ │RAM             │ 96KB        │ ├────────────────┼─────────────┤ │Vendor          │ Digistump   │ └────────────────┴─────────────┘
Configuration Please use digix ID for projectconf_env_board option in projectconf:
[env:digix] platform = atmelsam board = digix
You can override default Digistump DigiX settings per build environment using board_*** option, where *** is a JSON object path from board manifest digix.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Digistump DigiX supports the next uploading protocols:
Digistump DigiX 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.
LowPowerLab CurrentRanger Contents • LowPowerLab CurrentRanger
┌────────────────┬─────────────┐ │Microcontroller │ SAMD21G18A  │ ├────────────────┼─────────────┤ │Frequency       │ 48MHz       │ ├────────────────┼─────────────┤ │Flash           │ 256KB       │ ├────────────────┼─────────────┤ │RAM             │ 32KB        │ ├────────────────┼─────────────┤ │Vendor          │ LowPowerLab │ └────────────────┴─────────────┘
Configuration Please use current_ranger ID for projectconf_env_board option in projectconf:
[env:current_ranger] platform = atmelsam board = current_ranger
You can override default LowPowerLab CurrentRanger settings per build environment using board_*** option, where *** is a JSON object path from board manifest current_ranger.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support LowPowerLab CurrentRanger board.
MKR Vidor 4000 Contents • MKR Vidor 4000
Configuration Please use mkrvidor4000 ID for projectconf_env_board option in projectconf:
[env:mkrvidor4000] platform = atmelsam board = mkrvidor4000
You can override default MKR Vidor 4000 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrvidor4000.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading MKR Vidor 4000 supports the next uploading protocols:
MKR Vidor 4000 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.
Minitronics v2.0 Contents • Minitronics v2.0
┌────────────────┬─────────────┐ │Microcontroller │ SAMD21J18A  │ ├────────────────┼─────────────┤ │Frequency       │ 48MHz       │ ├────────────────┼─────────────┤ │Flash           │ 256KB       │ ├────────────────┼─────────────┤ │RAM             │ 32KB        │ ├────────────────┼─────────────┤ │Vendor          │ ReprapWorld │ └────────────────┴─────────────┘
Configuration Please use minitronics20 ID for projectconf_env_board option in projectconf:
[env:minitronics20] platform = atmelsam board = minitronics20
You can override default Minitronics v2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest minitronics20.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Minitronics v2.0 supports the next uploading protocols:
Minitronics v2.0 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.
Moteino M0 Contents • Moteino M0
Configuration Please use moteino_zero ID for projectconf_env_board option in projectconf:
[env:moteino_zero] platform = atmelsam board = moteino_zero
You can override default Moteino M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest moteino_zero.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Moteino M0 supports the next uploading protocols:
Moteino 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_cmsis-dap  │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ └──────────────────────────┴──────────┴─────────┘
NANO 33 IoT Contents • NANO 33 IoT
Configuration Please use nano_33_iot ID for projectconf_env_board option in projectconf:
[env:nano_33_iot] platform = atmelsam board = nano_33_iot
You can override default NANO 33 IoT settings per build environment using board_*** option, where *** is a JSON object path from board manifest nano_33_iot.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading NANO 33 IoT supports the next uploading protocols:
NANO 33 IoT 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.
SODAQ Autonomo Contents • SODAQ Autonomo
┌────────────────┬────────────┐ │Microcontroller │ SAMD21J18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ SODAQ      │ └────────────────┴────────────┘
Configuration Please use sodaq_autonomo ID for projectconf_env_board option in projectconf:
[env:sodaq_autonomo] platform = atmelsam board = sodaq_autonomo
You can override default SODAQ Autonomo settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_autonomo.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SODAQ Autonomo supports the next uploading protocols:
SODAQ Autonomo 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.
SODAQ ExpLoRer Contents • SODAQ ExpLoRer
Configuration Please use sodaq_explorer ID for projectconf_env_board option in projectconf:
[env:sodaq_explorer] platform = atmelsam board = sodaq_explorer
You can override default SODAQ ExpLoRer settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_explorer.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SODAQ ExpLoRer supports the next uploading protocols:
SODAQ ExpLoRer 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.
SODAQ ONE Contents • SODAQ ONE
┌────────────────┬────────────┐ │Microcontroller │ SAMD21G18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ SODAQ      │ └────────────────┴────────────┘
Configuration Please use sodaq_one ID for projectconf_env_board option in projectconf:
[env:sodaq_one] platform = atmelsam board = sodaq_one
You can override default SODAQ ONE settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_one.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SODAQ ONE supports the next uploading protocols:
SODAQ ONE 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.
SODAQ SARA Contents • SODAQ SARA
Configuration Please use sodaq_sara ID for projectconf_env_board option in projectconf:
[env:sodaq_sara] platform = atmelsam board = sodaq_sara
You can override default SODAQ SARA settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_sara.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SODAQ SARA supports the next uploading protocols:
SODAQ SARA 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.
SODAQ SFF Contents • SODAQ SFF
Configuration Please use sodaq_sff ID for projectconf_env_board option in projectconf:
[env:sodaq_sff] platform = atmelsam board = sodaq_sff
You can override default SODAQ SFF settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_sff.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SODAQ SFF supports the next uploading protocols:
SODAQ SFF 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.
SainSmart Due (Programming Port) Contents • SainSmart Due (Programming Port)
┌────────────────┬─────────────┐ │Microcontroller │ AT91SAM3X8E │ ├────────────────┼─────────────┤ │Frequency       │ 84MHz       │ ├────────────────┼─────────────┤ │Flash           │ 512KB       │ ├────────────────┼─────────────┤ │RAM             │ 96KB        │ ├────────────────┼─────────────┤ │Vendor          │ SainSmart   │ └────────────────┴─────────────┘
Configuration Please use sainSmartDue ID for projectconf_env_board option in projectconf:
[env:sainSmartDue] platform = atmelsam board = sainSmartDue
You can override default SainSmart Due (Programming Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest sainSmartDue.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SainSmart Due (Programming Port) supports the next uploading protocols:
SainSmart Due (Programming Port) 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.
SainSmart Due (USB Native Port) Contents • SainSmart Due (USB Native Port)
Configuration Please use sainSmartDueUSB ID for projectconf_env_board option in projectconf:
[env:sainSmartDueUSB] platform = atmelsam board = sainSmartDueUSB
You can override default SainSmart Due (USB Native Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest sainSmartDueUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SainSmart Due (USB Native Port) supports the next uploading protocols:
SainSmart Due (USB Native Port) 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.
Seeeduino LoRaWAN Contents • Seeeduino LoRaWAN
┌────────────────┬────────────┐ │Microcontroller │ SAMD21G18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Seeed      │ └────────────────┴────────────┘
Configuration Please use seeeduino_lorawan ID for projectconf_env_board option in projectconf:
[env:seeeduino_lorawan] platform = atmelsam board = seeeduino_lorawan
You can override default Seeeduino LoRaWAN settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeeduino_lorawan.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Seeeduino LoRaWAN supports the next uploading protocols:
Seeeduino LoRaWAN 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.
SparkFun 9DoF Razor IMU M0 Contents • SparkFun 9DoF Razor IMU M0
┌────────────────┬────────────┐ │Microcontroller │ SAMD21G18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ SparkFun   │ └────────────────┴────────────┘
Configuration Please use sparkfun_samd21_9dof ID for projectconf_env_board option in projectconf:
[env:sparkfun_samd21_9dof] platform = atmelsam board = sparkfun_samd21_9dof
You can override default SparkFun 9DoF Razor IMU M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_samd21_9dof.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun 9DoF Razor IMU M0 supports the next uploading protocols:
SparkFun 9DoF Razor IMU 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.
SparkFun Qwiic Micro Contents • SparkFun Qwiic Micro
┌────────────────┬────────────┐ │Microcontroller │ SAMD21E18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ SparkFun   │ └────────────────┴────────────┘
Configuration Please use sparkfun_qwiic_micro_samd21e ID for projectconf_env_board option in projectconf:
[env:sparkfun_qwiic_micro_samd21e] platform = atmelsam board = sparkfun_qwiic_micro_samd21e
You can override default SparkFun Qwiic Micro settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_qwiic_micro_samd21e.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun Qwiic Micro supports the next uploading protocols:
SparkFun Qwiic Micro 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.
SparkFun RedBoard Turbo Contents • SparkFun RedBoard Turbo
Configuration Please use sparkfun_redboard_turbo ID for projectconf_env_board option in projectconf:
[env:sparkfun_redboard_turbo] platform = atmelsam board = sparkfun_redboard_turbo
You can override default SparkFun RedBoard Turbo settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_redboard_turbo.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun RedBoard Turbo supports the next uploading protocols:
SparkFun RedBoard Turbo 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.
SparkFun SAMD21 Dev Breakout Contents • SparkFun SAMD21 Dev Breakout
Configuration Please use sparkfun_samd21_dev_usb ID for projectconf_env_board option in projectconf:
[env:sparkfun_samd21_dev_usb] platform = atmelsam board = sparkfun_samd21_dev_usb
You can override default SparkFun SAMD21 Dev Breakout settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_samd21_dev_usb.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun SAMD21 Dev Breakout supports the next uploading protocols:
SparkFun SAMD21 Dev Breakout 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.
SparkFun SAMD21 Mini Breakout Contents • SparkFun SAMD21 Mini Breakout
Configuration Please use sparkfun_samd21_mini_usb ID for projectconf_env_board option in projectconf:
[env:sparkfun_samd21_mini_usb] platform = atmelsam board = sparkfun_samd21_mini_usb
You can override default SparkFun SAMD21 Mini Breakout settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_samd21_mini_usb.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun SAMD21 Mini Breakout supports the next uploading protocols:
SparkFun SAMD21 Mini Breakout 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.
SparkFun SAMD21 Pro RF Contents • SparkFun SAMD21 Pro RF
Configuration Please use sparkfun_samd21_proRF ID for projectconf_env_board option in projectconf:
[env:sparkfun_samd21_proRF] platform = atmelsam board = sparkfun_samd21_proRF
You can override default SparkFun SAMD21 Pro RF settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_samd21_proRF.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun SAMD21 Pro RF supports the next uploading protocols:
SparkFun SAMD21 Pro RF 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.
Tuino 096 Contents • Tuino 096
┌────────────────┬────────────┐ │Microcontroller │ SAMD21G18A │ ├────────────────┼────────────┤ │Frequency       │ 48MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ Gimasi     │ └────────────────┴────────────┘
Configuration Please use tuinozero96 ID for projectconf_env_board option in projectconf:
[env:tuinozero96] platform = atmelsam board = tuinozero96
You can override default Tuino 096 settings per build environment using board_*** option, where *** is a JSON object path from board manifest tuinozero96.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Tuino 096 supports the next uploading protocols:
Tuino 096 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.
Espressif 32 AI Thinker ESP32-CAM Contents • AI Thinker ESP32-CAM
Hardware Platform platform_espressif32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
┌────────────────┬────────────┐ │Microcontroller │ ESP32      │ └────────────────┴────────────┘
│Frequency       │ 240MHz     │ ├────────────────┼────────────┤ │Flash           │ 4MB        │ ├────────────────┼────────────┤ │RAM             │ 320KB      │ ├────────────────┼────────────┤ │Vendor          │ AI Thinker │ └────────────────┴────────────┘
Configuration Please use esp32cam ID for projectconf_env_board option in projectconf:
[env:esp32cam] platform = espressif32 board = esp32cam
You can override default AI Thinker ESP32-CAM settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32cam.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = esp32
; change MCU frequency board_build.f_cpu = 240000000L
Uploading AI Thinker ESP32-CAM supports the next uploading protocols:
• esp-prog
• espota
• esptool
• iot-bus-jtag
• minimodule
• olimex-arm-usb-ocd
• olimex-arm-usb-ocd-h
• olimex-arm-usb-tiny-h
• olimex-jtag-tiny
• tumpa
Default protocol is esptool
upload_protocol = esptool
AI Thinker ESP32-CAM 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_esp-prog              │          │ Yes     │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_iot-bus-jtag          │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink                 │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_minimodule            │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-ocd    │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-ocd-h  │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-tiny-h │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-jtag-tiny      │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_tumpa                 │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
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_espidf  │ Espressif IoT Development   │ │                  │ Framework. Official         │ │                  │ development framework for   │ │                  │ ESP32.                      │ └──────────────────┴─────────────────────────────┘
ALKS ESP32 Contents • ALKS ESP32
┌────────────────┬──────────────┐ │Microcontroller │ ESP32        │ ├────────────────┼──────────────┤ │Frequency       │ 240MHz       │ ├────────────────┼──────────────┤ │Flash           │ 4MB          │ ├────────────────┼──────────────┤ │RAM             │ 320KB        │ ├────────────────┼──────────────┤ │Vendor          │ RoboticsBrno │ └────────────────┴──────────────┘
Configuration Please use alksesp32 ID for projectconf_env_board option in projectconf:
[env:alksesp32] platform = espressif32 board = alksesp32
You can override default ALKS ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest alksesp32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ALKS ESP32 supports the next uploading protocols:
ALKS ESP32 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.
AZ-Delivery ESP-32 Dev Kit C V4 Contents • AZ-Delivery ESP-32 Dev Kit C V4
┌────────────────┬─────────────┐ │Microcontroller │ ESP32       │ ├────────────────┼─────────────┤ │Frequency       │ 240MHz      │ ├────────────────┼─────────────┤ │Flash           │ 16MB        │ ├────────────────┼─────────────┤ │RAM             │ 520KB       │ ├────────────────┼─────────────┤ │Vendor          │ AZ-Delivery │ └────────────────┴─────────────┘
Configuration Please use az-delivery-devkit-v4 ID for projectconf_env_board option in projectconf:
[env:az-delivery-devkit-v4] platform = espressif32 board = az-delivery-devkit-v4
You can override default AZ-Delivery ESP-32 Dev Kit C V4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest az-delivery-devkit-v4.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading AZ-Delivery ESP-32 Dev Kit C V4 supports the next uploading protocols:
AZ-Delivery ESP-32 Dev Kit C V4 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_esp-prog              │          │ Yes     │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_iot-bus-jtag          │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink                 │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_minimodule            │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-ocd    │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
│debugging_tool_olimex-arm-usb-ocd-h  │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-tiny-h │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-jtag-tiny      │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_tumpa                 │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
Adafruit ESP32 Feather Contents • Adafruit ESP32 Feather
┌────────────────┬──────────┐ │Microcontroller │ ESP32    │ ├────────────────┼──────────┤ │Frequency       │ 240MHz   │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 320KB    │ ├────────────────┼──────────┤ │Vendor          │ Adafruit │ └────────────────┴──────────┘
Configuration Please use featheresp32 ID for projectconf_env_board option in projectconf:
[env:featheresp32] platform = espressif32 board = featheresp32
You can override default Adafruit ESP32 Feather settings per build environment using board_*** option, where *** is a JSON object path from board manifest featheresp32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit ESP32 Feather supports the next uploading protocols:
Adafruit ESP32 Feather 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.
April Brother ESPea32 Contents • April Brother ESPea32
┌────────────────┬───────────────┐ │Microcontroller │ ESP32         │ ├────────────────┼───────────────┤ │Frequency       │ 240MHz        │ ├────────────────┼───────────────┤ │Flash           │ 4MB           │ ├────────────────┼───────────────┤ │RAM             │ 320KB         │ ├────────────────┼───────────────┤ │Vendor          │ April Brother │ └────────────────┴───────────────┘
Configuration Please use espea32 ID for projectconf_env_board option in projectconf:
[env:espea32] platform = espressif32 board = espea32