neulab/tldr huggingface dataset:
You can override default April Brother ESPea32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest espea32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading April Brother ESPea32 supports the next uploading protocols:
Debugging piodebug currently does not support April Brother ESPea32 board.
BPI-Bit Contents • BPI-Bit
┌────────────────┬──────────┐ │Microcontroller │ ESP32    │ ├────────────────┼──────────┤ │Frequency       │ 160MHz   │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 320KB    │ ├────────────────┼──────────┤ │Vendor          │ BPI Tech │ └────────────────┴──────────┘
Configuration Please use bpi-bit ID for projectconf_env_board option in projectconf:
[env:bpi-bit] platform = espressif32 board = bpi-bit
You can override default BPI-Bit settings per build environment using board_*** option, where *** is a JSON object path from board manifest bpi-bit.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change MCU frequency board_build.f_cpu = 160000000L
Uploading BPI-Bit supports the next uploading protocols:
Debugging piodebug currently does not support BPI-Bit board.
Briki ABC (MBC-WB) - ESP32 Contents • Briki ABC (MBC-WB) - ESP32
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 3.25MB │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ meteca │ └────────────────┴────────┘
Configuration Please use briki_abc_esp32 ID for projectconf_env_board option in projectconf:
[env:briki_abc_esp32] platform = espressif32 board = briki_abc_esp32
You can override default Briki ABC (MBC-WB) - ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest briki_abc_esp32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Briki ABC (MBC-WB) - ESP32 supports the next uploading protocols:
Briki ABC (MBC-WB) - 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.
Briki MBC-WB - ESP32 Contents • Briki MBC-WB - ESP32
Configuration Please use briki_mbc-wb_esp32 ID for projectconf_env_board option in projectconf:
[env:briki_mbc-wb_esp32] platform = espressif32 board = briki_mbc-wb_esp32
You can override default Briki MBC-WB - ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest briki_mbc-wb_esp32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Briki MBC-WB - ESP32 supports the next uploading protocols:
Briki MBC-WB - 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.
D-duino-32 Contents • D-duino-32
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 4MB    │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ DSTIKE │ └────────────────┴────────┘
Configuration Please use d-duino-32 ID for projectconf_env_board option in projectconf:
[env:d-duino-32] platform = espressif32 board = d-duino-32
You can override default D-duino-32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest d-duino-32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading D-duino-32 supports the next uploading protocols:
D-duino-32 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.
│Vendor          │ Dongsen Technology │ └────────────────┴────────────────────┘
Configuration Please use pocket_32 ID for projectconf_env_board option in projectconf:
[env:pocket_32] platform = espressif32 board = pocket_32
You can override default Dongsen Tech Pocket 32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest pocket_32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Dongsen Tech Pocket 32 supports the next uploading protocols:
Dongsen Tech Pocket 32 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.
ESP32 FM DevKit Contents • ESP32 FM DevKit
┌────────────────┬─────────┐ │Microcontroller │ ESP32   │ ├────────────────┼─────────┤ │Frequency       │ 240MHz  │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 320KB   │ ├────────────────┼─────────┤ │Vendor          │ Unknown │ └────────────────┴─────────┘
Configuration Please use fm-devkit ID for projectconf_env_board option in projectconf:
[env:fm-devkit] platform = espressif32 board = fm-devkit
You can override default ESP32 FM DevKit settings per build environment using board_*** option, where *** is a JSON object path from board manifest fm-devkit.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESP32 FM DevKit supports the next uploading protocols:
ESP32 FM DevKit 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.
ESP32 Pico Kit Contents • ESP32 Pico Kit
┌────────────────┬───────────┐ │Microcontroller │ ESP32     │ ├────────────────┼───────────┤ │Frequency       │ 240MHz    │ ├────────────────┼───────────┤ │Flash           │ 4MB       │ ├────────────────┼───────────┤ │RAM             │ 320KB     │ ├────────────────┼───────────┤ │Vendor          │ Espressif │ └────────────────┴───────────┘
Configuration Please use pico32 ID for projectconf_env_board option in projectconf:
[env:pico32] platform = espressif32 board = pico32
You can override default ESP32 Pico Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest pico32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESP32 Pico Kit supports the next uploading protocols:
Debugging piodebug currently does not support ESP32 Pico Kit board.
ESP32vn IoT Uno Contents • ESP32vn IoT Uno
┌────────────────┬─────────┐ │Microcontroller │ ESP32   │ ├────────────────┼─────────┤ │Frequency       │ 240MHz  │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 320KB   │ ├────────────────┼─────────┤ │Vendor          │ ESP32vn │ └────────────────┴─────────┘
Configuration Please use esp32vn-iot-uno ID for projectconf_env_board option in projectconf:
[env:esp32vn-iot-uno] platform = espressif32 board = esp32vn-iot-uno
You can override default ESP32vn IoT Uno settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32vn-iot-uno.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESP32vn IoT Uno supports the next uploading protocols:
ESP32vn IoT Uno 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.
ESPectro32 Contents • ESPectro32
┌────────────────┬─────────┐ │Microcontroller │ ESP32   │ ├────────────────┼─────────┤ │Frequency       │ 240MHz  │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 320KB   │ ├────────────────┼─────────┤ │Vendor          │ DycodeX │ └────────────────┴─────────┘
Configuration Please use espectro32 ID for projectconf_env_board option in projectconf:
[env:espectro32] platform = espressif32 board = espectro32
You can override default ESPectro32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest espectro32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESPectro32 supports the next uploading protocols:
ESPectro32 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.
ESPino32 Contents • ESPino32
┌────────────────┬──────────────┐ │Microcontroller │ ESP32        │ ├────────────────┼──────────────┤ │Frequency       │ 240MHz       │ ├────────────────┼──────────────┤ │Flash           │ 4MB          │ ├────────────────┼──────────────┤ │RAM             │ 320KB        │ ├────────────────┼──────────────┤ │Vendor          │ ThaiEasyElec │ └────────────────┴──────────────┘
Configuration Please use espino32 ID for projectconf_env_board option in projectconf:
[env:espino32] platform = espressif32 board = espino32
You can override default ESPino32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest espino32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESPino32 supports the next uploading protocols:
ESPino32 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.
│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.                      │ └──────────────────┴─────────────────────────────┘
Electronic SweetPeas ESP320 Contents • Electronic SweetPeas ESP320
┌────────────────┬──────────────────────┐ │Microcontroller │ ESP32                │ ├────────────────┼──────────────────────┤ │Frequency       │ 240MHz               │ ├────────────────┼──────────────────────┤ │Flash           │ 4MB                  │ ├────────────────┼──────────────────────┤ │RAM             │ 320KB                │ ├────────────────┼──────────────────────┤ │Vendor          │ Electronic SweetPeas │ └────────────────┴──────────────────────┘
Configuration Please use esp320 ID for projectconf_env_board option in projectconf:
[env:esp320] platform = espressif32 board = esp320
You can override default Electronic SweetPeas ESP320 settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp320.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Electronic SweetPeas ESP320 supports the next uploading protocols:
Debugging piodebug currently does not support Electronic SweetPeas ESP320 board.
Espressif ESP-WROVER-KIT Contents • Espressif ESP-WROVER-KIT
Configuration Please use esp-wrover-kit ID for projectconf_env_board option in projectconf:
[env:esp-wrover-kit] platform = espressif32 board = esp-wrover-kit
You can override default Espressif ESP-WROVER-KIT settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp-wrover-kit.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Espressif ESP-WROVER-KIT supports the next uploading protocols:
• ftdi
Espressif ESP-WROVER-KIT 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_esp-prog              │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_ftdi                  │ Yes      │ 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                 │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
Espressif ESP32 Dev Module Contents • Espressif ESP32 Dev Module
Configuration Please use esp32dev ID for projectconf_env_board option in projectconf:
[env:esp32dev] platform = espressif32 board = esp32dev
You can override default Espressif ESP32 Dev Module settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32dev.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Espressif ESP32 Dev Module supports the next uploading protocols:
Espressif ESP32 Dev Module 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.
Configuration Please use frogboard ID for projectconf_env_board option in projectconf:
[env:frogboard] platform = espressif32 board = frogboard
You can override default Frog Board ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest frogboard.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Frog Board ESP32 supports the next uploading protocols:
Frog Board 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.
Heltec WiFi Kit 32 Contents • Heltec WiFi Kit 32
┌────────────────┬───────────────────┐ │Microcontroller │ ESP32             │ ├────────────────┼───────────────────┤ │Frequency       │ 240MHz            │ ├────────────────┼───────────────────┤ │Flash           │ 4MB               │ ├────────────────┼───────────────────┤ │RAM             │ 320KB             │ ├────────────────┼───────────────────┤ │Vendor          │ Heltec Automation │ └────────────────┴───────────────────┘
Configuration Please use heltec_wifi_kit_32 ID for projectconf_env_board option in projectconf:
[env:heltec_wifi_kit_32] platform = espressif32 board = heltec_wifi_kit_32
You can override default Heltec WiFi Kit 32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest heltec_wifi_kit_32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Heltec WiFi Kit 32 supports the next uploading protocols:
Debugging piodebug currently does not support Heltec WiFi Kit 32 board.
Heltec WiFi LoRa 32 Contents • Heltec WiFi LoRa 32
Configuration Please use heltec_wifi_lora_32 ID for projectconf_env_board option in projectconf:
[env:heltec_wifi_lora_32] platform = espressif32 board = heltec_wifi_lora_32
You can override default Heltec WiFi LoRa 32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest heltec_wifi_lora_32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Heltec WiFi LoRa 32 supports the next uploading protocols:
Heltec WiFi LoRa 32 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.
Heltec WiFi LoRa 32 (V2) Contents • Heltec WiFi LoRa 32 (V2)
┌────────────────┬───────────────────┐ │Microcontroller │ ESP32             │ ├────────────────┼───────────────────┤ │Frequency       │ 240MHz            │ ├────────────────┼───────────────────┤ │Flash           │ 8MB               │ ├────────────────┼───────────────────┤ │RAM             │ 320KB             │ ├────────────────┼───────────────────┤ │Vendor          │ Heltec Automation │ └────────────────┴───────────────────┘
Configuration Please use heltec_wifi_lora_32_V2 ID for projectconf_env_board option in projectconf:
[env:heltec_wifi_lora_32_V2] platform = espressif32 board = heltec_wifi_lora_32_V2
You can override default Heltec WiFi LoRa 32 (V2) settings per build environment using board_*** option, where *** is a JSON object path from board manifest heltec_wifi_lora_32_V2.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Heltec WiFi LoRa 32 (V2) supports the next uploading protocols:
Heltec WiFi LoRa 32 (V2) 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.
Heltec Wireless Stick Contents • Heltec Wireless Stick
Configuration Please use heltec_wireless_stick ID for projectconf_env_board option in projectconf:
[env:heltec_wireless_stick] platform = espressif32 board = heltec_wireless_stick
You can override default Heltec Wireless Stick settings per build environment using board_*** option, where *** is a JSON object path from board manifest heltec_wireless_stick.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Heltec Wireless Stick supports the next uploading protocols:
Heltec Wireless Stick 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.
Hornbill ESP32 Dev Contents • Hornbill ESP32 Dev
┌────────────────┬──────────┐ │Microcontroller │ ESP32    │ ├────────────────┼──────────┤ │Frequency       │ 240MHz   │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 320KB    │ ├────────────────┼──────────┤ │Vendor          │ Hornbill │ └────────────────┴──────────┘
Configuration Please use hornbill32dev ID for projectconf_env_board option in projectconf:
[env:hornbill32dev] platform = espressif32 board = hornbill32dev
You can override default Hornbill ESP32 Dev settings per build environment using board_*** option, where *** is a JSON object path from board manifest hornbill32dev.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Hornbill ESP32 Dev supports the next uploading protocols:
Hornbill ESP32 Dev 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.
[env:intorobot] platform = espressif32 board = intorobot
You can override default IntoRobot Fig settings per build environment using board_*** option, where *** is a JSON object path from board manifest intorobot.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading IntoRobot Fig supports the next uploading protocols:
Debugging piodebug currently does not support IntoRobot Fig board.
IoTaaP Magnolia Contents • IoTaaP Magnolia
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 4MB    │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ IoTaaP │ └────────────────┴────────┘
Configuration Please use iotaap_magnolia ID for projectconf_env_board option in projectconf:
[env:iotaap_magnolia] platform = espressif32 board = iotaap_magnolia
You can override default IoTaaP Magnolia settings per build environment using board_*** option, where *** is a JSON object path from board manifest iotaap_magnolia.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading IoTaaP Magnolia supports the next uploading protocols:
IoTaaP Magnolia 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.
M5Stack Core ESP32 Contents • M5Stack Core ESP32
┌────────────────┬─────────┐ │Microcontroller │ ESP32   │ ├────────────────┼─────────┤ │Frequency       │ 240MHz  │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 320KB   │ ├────────────────┼─────────┤ │Vendor          │ M5Stack │ └────────────────┴─────────┘
Configuration Please use m5stack-core-esp32 ID for projectconf_env_board option in projectconf:
[env:m5stack-core-esp32] platform = espressif32 board = m5stack-core-esp32
You can override default M5Stack Core ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest m5stack-core-esp32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading M5Stack Core ESP32 supports the next uploading protocols:
Debugging piodebug currently does not support M5Stack Core ESP32 board.
M5Stack FIRE Contents • M5Stack FIRE
┌────────────────┬─────────┐ │Microcontroller │ ESP32   │ ├────────────────┼─────────┤ │Frequency       │ 240MHz  │ ├────────────────┼─────────┤ │Flash           │ 16MB    │ ├────────────────┼─────────┤ │RAM             │ 6.25MB  │ ├────────────────┼─────────┤ │Vendor          │ M5Stack │ └────────────────┴─────────┘
Configuration Please use m5stack-fire ID for projectconf_env_board option in projectconf:
[env:m5stack-fire] platform = espressif32 board = m5stack-fire
You can override default M5Stack FIRE settings per build environment using board_*** option, where *** is a JSON object path from board manifest m5stack-fire.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading M5Stack FIRE supports the next uploading protocols:
Debugging piodebug currently does not support M5Stack FIRE board.
│framework_espidf  │ Espressif IoT Development   │ │                  │ Framework. Official         │ │                  │ development framework for   │ │                  │ ESP32.                      │ └──────────────────┴─────────────────────────────┘
M5Stack GREY ESP32 Contents • M5Stack GREY ESP32
┌────────────────┬─────────┐ │Microcontroller │ ESP32   │ ├────────────────┼─────────┤ │Frequency       │ 240MHz  │ ├────────────────┼─────────┤ │Flash           │ 16MB    │ ├────────────────┼─────────┤ │RAM             │ 520KB   │ ├────────────────┼─────────┤ │Vendor          │ M5Stack │ └────────────────┴─────────┘
Configuration Please use m5stack-grey ID for projectconf_env_board option in projectconf:
[env:m5stack-grey] platform = espressif32 board = m5stack-grey
You can override default M5Stack GREY ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest m5stack-grey.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading M5Stack GREY ESP32 supports the next uploading protocols:
Debugging piodebug currently does not support M5Stack GREY ESP32 board.
M5Stick-C Contents • M5Stick-C
Configuration Please use m5stick-c ID for projectconf_env_board option in projectconf:
[env:m5stick-c] platform = espressif32 board = m5stick-c
You can override default M5Stick-C settings per build environment using board_*** option, where *** is a JSON object path from board manifest m5stick-c.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading M5Stick-C supports the next uploading protocols:
Debugging piodebug currently does not support M5Stick-C board.
MH ET LIVE ESP32DevKIT Contents • MH ET LIVE ESP32DevKIT
┌────────────────┬────────────┐ │Microcontroller │ ESP32      │ ├────────────────┼────────────┤ │Frequency       │ 240MHz     │ ├────────────────┼────────────┤ │Flash           │ 4MB        │ ├────────────────┼────────────┤ │RAM             │ 320KB      │ ├────────────────┼────────────┤ │Vendor          │ MH-ET Live │ └────────────────┴────────────┘
Configuration Please use mhetesp32devkit ID for projectconf_env_board option in projectconf:
[env:mhetesp32devkit] platform = espressif32 board = mhetesp32devkit
You can override default MH ET LIVE ESP32DevKIT settings per build environment using board_*** option, where *** is a JSON object path from board manifest mhetesp32devkit.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading MH ET LIVE ESP32DevKIT supports the next uploading protocols:
MH ET LIVE ESP32DevKIT 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.
MH ET LIVE ESP32MiniKit Contents • MH ET LIVE ESP32MiniKit
Configuration Please use mhetesp32minikit ID for projectconf_env_board option in projectconf:
[env:mhetesp32minikit] platform = espressif32 board = mhetesp32minikit
You can override default MH ET LIVE ESP32MiniKit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mhetesp32minikit.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading MH ET LIVE ESP32MiniKit supports the next uploading protocols:
MH ET LIVE ESP32MiniKit 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.
MagicBit Contents • MagicBit
┌────────────────┬────────────────┐ │Microcontroller │ ESP32          │ ├────────────────┼────────────────┤ │Frequency       │ 240MHz         │ ├────────────────┼────────────────┤ │Flash           │ 4MB            │ ├────────────────┼────────────────┤ │RAM             │ 320KB          │ ├────────────────┼────────────────┤ │Vendor          │ Magicblocks.io │ └────────────────┴────────────────┘
Configuration Please use magicbit ID for projectconf_env_board option in projectconf:
[env:magicbit] platform = espressif32 board = magicbit
You can override default MagicBit settings per build environment using board_*** option, where *** is a JSON object path from board manifest magicbit.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading MagicBit supports the next uploading protocols:
Debugging piodebug currently does not support MagicBit board.
MakerAsia Nano32 Contents • MakerAsia Nano32
┌────────────────┬───────────┐ │Microcontroller │ ESP32     │ ├────────────────┼───────────┤ │Frequency       │ 240MHz    │ ├────────────────┼───────────┤ │Flash           │ 4MB       │ ├────────────────┼───────────┤ │RAM             │ 320KB     │ ├────────────────┼───────────┤ │Vendor          │ MakerAsia │ └────────────────┴───────────┘
Configuration Please use nano32 ID for projectconf_env_board option in projectconf:
[env:nano32] platform = espressif32 board = nano32
You can override default MakerAsia Nano32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nano32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading MakerAsia Nano32 supports the next uploading protocols:
Debugging piodebug currently does not support MakerAsia Nano32 board.
Microduino Core ESP32 Contents • Microduino Core ESP32
┌────────────────┬────────────┐ │Microcontroller │ ESP32      │ ├────────────────┼────────────┤ │Frequency       │ 240MHz     │ ├────────────────┼────────────┤ │Flash           │ 4MB        │ ├────────────────┼────────────┤ │RAM             │ 320KB      │ ├────────────────┼────────────┤ │Vendor          │ Microduino │ └────────────────┴────────────┘
Configuration Please use microduino-core-esp32 ID for projectconf_env_board option in projectconf:
[env:microduino-core-esp32] platform = espressif32 board = microduino-core-esp32
You can override default Microduino Core ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest microduino-core-esp32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Microduino Core ESP32 supports the next uploading protocols:
Debugging piodebug currently does not support Microduino Core ESP32 board.
Node32s Contents • Node32s
┌────────────────┬───────────┐ │Microcontroller │ ESP32     │ ├────────────────┼───────────┤ │Frequency       │ 240MHz    │ ├────────────────┼───────────┤ │Flash           │ 4MB       │ ├────────────────┼───────────┤ │RAM             │ 320KB     │ ├────────────────┼───────────┤ │Vendor          │ Aiyarafun │ └────────────────┴───────────┘
Configuration Please use node32s ID for projectconf_env_board option in projectconf:
[env:node32s] platform = espressif32 board = node32s
You can override default Node32s settings per build environment using board_*** option, where *** is a JSON object path from board manifest node32s.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Node32s supports the next uploading protocols:
Node32s 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.
NodeMCU-32S Contents • NodeMCU-32S
┌────────────────┬─────────┐ │Microcontroller │ ESP32   │ ├────────────────┼─────────┤ │Frequency       │ 240MHz  │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 320KB   │ ├────────────────┼─────────┤ │Vendor          │ NodeMCU │ └────────────────┴─────────┘
Configuration Please use nodemcu-32s ID for projectconf_env_board option in projectconf:
[env:nodemcu-32s] platform = espressif32 board = nodemcu-32s
You can override default NodeMCU-32S settings per build environment using board_*** option, where *** is a JSON object path from board manifest nodemcu-32s.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading NodeMCU-32S supports the next uploading protocols:
NodeMCU-32S 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.
Noduino Quantum Contents • Noduino Quantum
┌────────────────┬─────────┐ │Microcontroller │ ESP32   │ ├────────────────┼─────────┤ │Frequency       │ 240MHz  │ ├────────────────┼─────────┤ │Flash           │ 16MB    │ ├────────────────┼─────────┤ │RAM             │ 320KB   │ ├────────────────┼─────────┤ │Vendor          │ Noduino │ └────────────────┴─────────┘
Configuration Please use quantum ID for projectconf_env_board option in projectconf:
[env:quantum] platform = espressif32 board = quantum
You can override default Noduino Quantum settings per build environment using board_*** option, where *** is a JSON object path from board manifest quantum.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Noduino Quantum supports the next uploading protocols:
Debugging piodebug currently does not support Noduino Quantum board.
ODROID-GO Contents • ODROID-GO
┌────────────────┬────────────┐ │Microcontroller │ ESP32      │ ├────────────────┼────────────┤ │Frequency       │ 240MHz     │ ├────────────────┼────────────┤ │Flash           │ 16MB       │ ├────────────────┼────────────┤ │RAM             │ 320KB      │ ├────────────────┼────────────┤ │Vendor          │ Hardkernel │ └────────────────┴────────────┘
Configuration Please use odroid_esp32 ID for projectconf_env_board option in projectconf:
[env:odroid_esp32] platform = espressif32 board = odroid_esp32
You can override default ODROID-GO settings per build environment using board_*** option, where *** is a JSON object path from board manifest odroid_esp32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ODROID-GO supports the next uploading protocols:
Debugging piodebug currently does not support ODROID-GO board.
OLIMEX ESP32-DevKit-LiPo Contents • OLIMEX ESP32-DevKit-LiPo
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 4MB    │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ OLIMEX │ └────────────────┴────────┘
Configuration Please use esp32-devkitlipo ID for projectconf_env_board option in projectconf:
[env:esp32-devkitlipo] platform = espressif32 board = esp32-devkitlipo
You can override default OLIMEX ESP32-DevKit-LiPo settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-devkitlipo.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading OLIMEX ESP32-DevKit-LiPo supports the next uploading protocols:
OLIMEX ESP32-DevKit-LiPo 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.
OLIMEX ESP32-EVB Contents • OLIMEX ESP32-EVB
Configuration Please use esp32-evb ID for projectconf_env_board option in projectconf:
[env:esp32-evb] platform = espressif32 board = esp32-evb
You can override default OLIMEX ESP32-EVB settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-evb.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading OLIMEX ESP32-EVB supports the next uploading protocols:
OLIMEX ESP32-EVB 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.
OLIMEX ESP32-GATEWAY Contents • OLIMEX ESP32-GATEWAY
Configuration Please use esp32-gateway ID for projectconf_env_board option in projectconf:
[env:esp32-gateway] platform = espressif32 board = esp32-gateway
You can override default OLIMEX ESP32-GATEWAY settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-gateway.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading OLIMEX ESP32-GATEWAY supports the next uploading protocols:
OLIMEX ESP32-GATEWAY 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.
OLIMEX ESP32-PRO Contents • OLIMEX ESP32-PRO
Configuration Please use esp32-pro ID for projectconf_env_board option in projectconf:
[env:esp32-pro] platform = espressif32 board = esp32-pro
You can override default OLIMEX ESP32-PRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-pro.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading OLIMEX ESP32-PRO supports the next uploading protocols:
Debugging piodebug currently does not support OLIMEX ESP32-PRO board.
OLIMEX ESP32-PoE Contents • OLIMEX ESP32-PoE
Configuration Please use esp32-poe ID for projectconf_env_board option in projectconf:
[env:esp32-poe] platform = espressif32 board = esp32-poe
You can override default OLIMEX ESP32-PoE settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-poe.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading OLIMEX ESP32-PoE supports the next uploading protocols:
Debugging piodebug currently does not support OLIMEX ESP32-PoE board.
OLIMEX ESP32-PoE-ISO Contents • OLIMEX ESP32-PoE-ISO
Configuration Please use esp32-poe-iso ID for projectconf_env_board option in projectconf:
[env:esp32-poe-iso] platform = espressif32 board = esp32-poe-iso
You can override default OLIMEX ESP32-PoE-ISO settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-poe-iso.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading OLIMEX ESP32-PoE-ISO supports the next uploading protocols:
Debugging piodebug currently does not support OLIMEX ESP32-PoE-ISO board.
OROCA EduBot Contents • OROCA EduBot
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 4MB    │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ OROCA  │ └────────────────┴────────┘
Configuration Please use oroca_edubot ID for projectconf_env_board option in projectconf:
[env:oroca_edubot] platform = espressif32 board = oroca_edubot
You can override default OROCA EduBot settings per build environment using board_*** option, where *** is a JSON object path from board manifest oroca_edubot.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading OROCA EduBot supports the next uploading protocols:
Debugging piodebug currently does not support OROCA EduBot board.
Onehorse ESP32 Dev Module Contents • Onehorse ESP32 Dev Module
┌────────────────┬──────────┐ │Microcontroller │ ESP32    │ ├────────────────┼──────────┤ │Frequency       │ 240MHz   │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 320KB    │ ├────────────────┼──────────┤ │Vendor          │ Onehorse │ └────────────────┴──────────┘
Configuration Please use onehorse32dev ID for projectconf_env_board option in projectconf:
[env:onehorse32dev] platform = espressif32 board = onehorse32dev
You can override default Onehorse ESP32 Dev Module settings per build environment using board_*** option, where *** is a JSON object path from board manifest onehorse32dev.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Onehorse ESP32 Dev Module supports the next uploading protocols:
Debugging piodebug currently does not support Onehorse ESP32 Dev Module board.
Pycom GPy Contents • Pycom GPy
┌────────────────┬────────────┐ │Microcontroller │ ESP32      │ ├────────────────┼────────────┤ │Frequency       │ 240MHz     │ ├────────────────┼────────────┤ │Flash           │ 4MB        │ ├────────────────┼────────────┤ │RAM             │ 320KB      │ └────────────────┴────────────┘
│Vendor          │ Pycom Ltd. │ └────────────────┴────────────┘
Configuration Please use pycom_gpy ID for projectconf_env_board option in projectconf:
[env:pycom_gpy] platform = espressif32 board = pycom_gpy
You can override default Pycom GPy settings per build environment using board_*** option, where *** is a JSON object path from board manifest pycom_gpy.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Pycom GPy supports the next uploading protocols:
Debugging piodebug currently does not support Pycom GPy board.
Pycom LoPy Contents • Pycom LoPy
┌────────────────┬────────────┐ │Microcontroller │ ESP32      │ ├────────────────┼────────────┤ │Frequency       │ 240MHz     │ ├────────────────┼────────────┤ │Flash           │ 4MB        │ ├────────────────┼────────────┤ │RAM             │ 320KB      │ ├────────────────┼────────────┤ │Vendor          │ Pycom Ltd. │ └────────────────┴────────────┘
Configuration Please use lopy ID for projectconf_env_board option in projectconf:
[env:lopy] platform = espressif32 board = lopy
You can override default Pycom LoPy settings per build environment using board_*** option, where *** is a JSON object path from board manifest lopy.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Pycom LoPy supports the next uploading protocols:
Pycom LoPy 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.
Pycom LoPy4 Contents • Pycom LoPy4
┌────────────────┬────────────┐ │Microcontroller │ ESP32      │ ├────────────────┼────────────┤ │Frequency       │ 240MHz     │ ├────────────────┼────────────┤ │Flash           │ 4MB        │ ├────────────────┼────────────┤ │RAM             │ 1.25MB     │ ├────────────────┼────────────┤ │Vendor          │ Pycom Ltd. │ └────────────────┴────────────┘
Configuration Please use lopy4 ID for projectconf_env_board option in projectconf:
[env:lopy4] platform = espressif32 board = lopy4
You can override default Pycom LoPy4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lopy4.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Pycom LoPy4 supports the next uploading protocols:
Pycom LoPy4 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.
Qchip Contents • Qchip
┌────────────────┬────────────┐ │Microcontroller │ ESP32      │ ├────────────────┼────────────┤ │Frequency       │ 240MHz     │ ├────────────────┼────────────┤ │Flash           │ 4MB        │ ├────────────────┼────────────┤ │RAM             │ 320KB      │ ├────────────────┼────────────┤ │Vendor          │ Qmobot LLP │ └────────────────┴────────────┘
Configuration Please use qchip ID for projectconf_env_board option in projectconf:
[env:qchip] platform = espressif32 board = qchip
You can override default Qchip settings per build environment using board_*** option, where *** is a JSON object path from board manifest qchip.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Qchip supports the next uploading protocols:
Debugging piodebug currently does not support Qchip board.
SG-O AirMon Contents • SG-O AirMon
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 4MB    │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ SG-O   │ └────────────────┴────────┘
Configuration Please use sg-o_airMon ID for projectconf_env_board option in projectconf:
[env:sg-o_airMon] platform = espressif32 board = sg-o_airMon
You can override default SG-O AirMon settings per build environment using board_*** option, where *** is a JSON object path from board manifest sg-o_airMon.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SG-O AirMon supports the next uploading protocols:
SG-O AirMon 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.
Silicognition wESP32 Contents • Silicognition wESP32
┌────────────────┬───────────────┐ │Microcontroller │ ESP32         │ ├────────────────┼───────────────┤ │Frequency       │ 240MHz        │ ├────────────────┼───────────────┤ │Flash           │ 4MB           │ ├────────────────┼───────────────┤ │RAM             │ 320KB         │ ├────────────────┼───────────────┤ │Vendor          │ Silicognition │ └────────────────┴───────────────┘
Configuration Please use wesp32 ID for projectconf_env_board option in projectconf:
[env:wesp32] platform = espressif32 board = wesp32
You can override default Silicognition wESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest wesp32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Silicognition wESP32 supports the next uploading protocols:
Silicognition wESP32 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 ESP32 Thing Contents • SparkFun ESP32 Thing
┌────────────────┬──────────────────────┐ │Microcontroller │ ESP32                │ ├────────────────┼──────────────────────┤ │Frequency       │ 240MHz               │ ├────────────────┼──────────────────────┤ │Flash           │ 4MB                  │ ├────────────────┼──────────────────────┤ │RAM             │ 320KB                │ ├────────────────┼──────────────────────┤ │Vendor          │ SparkFun Electronics │ └────────────────┴──────────────────────┘
Configuration Please use esp32thing ID for projectconf_env_board option in projectconf:
[env:esp32thing] platform = espressif32 board = esp32thing
You can override default SparkFun ESP32 Thing settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32thing.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun ESP32 Thing supports the next uploading protocols:
SparkFun ESP32 Thing 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 LoRa Gateway 1-Channel Contents • SparkFun LoRa Gateway 1-Channel
┌────────────────┬──────────┐ │Microcontroller │ ESP32    │ ├────────────────┼──────────┤ │Frequency       │ 240MHz   │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 320KB    │ ├────────────────┼──────────┤ │Vendor          │ SparkFun │ └────────────────┴──────────┘
Configuration Please use sparkfun_lora_gateway_1-channel ID for projectconf_env_board option in projectconf:
[env:sparkfun_lora_gateway_1-channel] platform = espressif32 board = sparkfun_lora_gateway_1-channel
You can override default SparkFun LoRa Gateway 1-Channel settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_lora_gateway_1-channel.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun LoRa Gateway 1-Channel supports the next uploading protocols:
SparkFun LoRa Gateway 1-Channel 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                 │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
TTGO LoRa32-OLED V1 Contents • TTGO LoRa32-OLED V1
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 4MB    │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ TTGO   │ └────────────────┴────────┘
Configuration Please use ttgo-lora32-v1 ID for projectconf_env_board option in projectconf:
[env:ttgo-lora32-v1] platform = espressif32 board = ttgo-lora32-v1
You can override default TTGO LoRa32-OLED V1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ttgo-lora32-v1.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading TTGO LoRa32-OLED V1 supports the next uploading protocols:
TTGO LoRa32-OLED V1 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.
TTGO LoRa32-OLED V2 Contents • TTGO LoRa32-OLED V2
Configuration Please use ttgo-lora32-v2 ID for projectconf_env_board option in projectconf:
[env:ttgo-lora32-v2] platform = espressif32 board = ttgo-lora32-v2
You can override default TTGO LoRa32-OLED V2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ttgo-lora32-v2.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading TTGO LoRa32-OLED V2 supports the next uploading protocols:
TTGO LoRa32-OLED V2 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.
TTGO T-Beam Contents • TTGO T-Beam
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 4MB    │ ├────────────────┼────────┤ │RAM             │ 1.25MB │ ├────────────────┼────────┤ │Vendor          │ TTGO   │ └────────────────┴────────┘
Configuration Please use ttgo-t-beam ID for projectconf_env_board option in projectconf:
[env:ttgo-t-beam] platform = espressif32 board = ttgo-t-beam
You can override default TTGO T-Beam settings per build environment using board_*** option, where *** is a JSON object path from board manifest ttgo-t-beam.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading TTGO T-Beam supports the next uploading protocols:
TTGO T-Beam 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.
TTGO T-Watch Contents • TTGO T-Watch
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 16MB   │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ TTGO   │ └────────────────┴────────┘