neulab/tldr huggingface dataset:
Configuration Please use ttgo-t-watch ID for projectconf_env_board option in projectconf:
[env:ttgo-t-watch] platform = espressif32 board = ttgo-t-watch
You can override default TTGO T-Watch settings per build environment using board_*** option, where *** is a JSON object path from board manifest ttgo-t-watch.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading TTGO T-Watch supports the next uploading protocols:
Debugging piodebug currently does not support TTGO T-Watch board.
TTGO T1 Contents • TTGO T1
Configuration Please use ttgo-t1 ID for projectconf_env_board option in projectconf:
[env:ttgo-t1] platform = espressif32 board = ttgo-t1
You can override default TTGO T1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ttgo-t1.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading TTGO T1 supports the next uploading protocols:
TTGO T1 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.
TinyPICO Contents • TinyPICO
┌────────────────┬──────────┐ │Microcontroller │ ESP32    │ ├────────────────┼──────────┤ │Frequency       │ 240MHz   │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 320KB    │ ├────────────────┼──────────┤ │Vendor          │ TinyPICO │ └────────────────┴──────────┘
Configuration Please use tinypico ID for projectconf_env_board option in projectconf:
[env:tinypico] platform = espressif32 board = tinypico
You can override default TinyPICO settings per build environment using board_*** option, where *** is a JSON object path from board manifest tinypico.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading TinyPICO supports the next uploading protocols:
Debugging piodebug currently does not support TinyPICO board.
Turta IoT Node Contents • Turta IoT Node
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 4MB    │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ Turta  │ └────────────────┴────────┘
Configuration Please use turta_iot_node ID for projectconf_env_board option in projectconf:
[env:turta_iot_node] platform = espressif32 board = turta_iot_node
You can override default Turta IoT Node settings per build environment using board_*** option, where *** is a JSON object path from board manifest turta_iot_node.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Turta IoT Node supports the next uploading protocols:
Debugging piodebug currently does not support Turta IoT Node board.
VintLabs ESP32 Devkit Contents • VintLabs ESP32 Devkit
┌────────────────┬──────────┐ │Microcontroller │ ESP32    │ ├────────────────┼──────────┤ │Frequency       │ 240MHz   │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 320KB    │ ├────────────────┼──────────┤ │Vendor          │ VintLabs │ └────────────────┴──────────┘
Configuration Please use vintlabs-devkit-v1 ID for projectconf_env_board option in projectconf:
[env:vintlabs-devkit-v1] platform = espressif32 board = vintlabs-devkit-v1
You can override default VintLabs ESP32 Devkit settings per build environment using board_*** option, where *** is a JSON object path from board manifest vintlabs-devkit-v1.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading VintLabs ESP32 Devkit supports the next uploading protocols:
VintLabs ESP32 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.
WEMOS LOLIN D32 Contents • WEMOS LOLIN D32
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 4MB    │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ WEMOS  │ └────────────────┴────────┘
Configuration Please use lolin_d32 ID for projectconf_env_board option in projectconf:
[env:lolin_d32] platform = espressif32 board = lolin_d32
You can override default WEMOS LOLIN D32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lolin_d32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WEMOS LOLIN D32 supports the next uploading protocols:
WEMOS LOLIN D32 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.
WEMOS LOLIN D32 PRO Contents • WEMOS LOLIN D32 PRO
Configuration Please use lolin_d32_pro ID for projectconf_env_board option in projectconf:
[env:lolin_d32_pro] platform = espressif32 board = lolin_d32_pro
You can override default WEMOS LOLIN D32 PRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest lolin_d32_pro.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WEMOS LOLIN D32 PRO supports the next uploading protocols:
WEMOS LOLIN D32 PRO 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.
WEMOS LOLIN32 Contents • WEMOS LOLIN32
Configuration Please use lolin32 ID for projectconf_env_board option in projectconf:
[env:lolin32] platform = espressif32 board = lolin32
You can override default WEMOS LOLIN32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lolin32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WEMOS LOLIN32 supports the next uploading protocols:
WEMOS LOLIN32 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.
WeMos D1 MINI ESP32 Contents • WeMos D1 MINI ESP32
Configuration Please use wemos_d1_mini32 ID for projectconf_env_board option in projectconf:
[env:wemos_d1_mini32] platform = espressif32 board = wemos_d1_mini32
You can override default WeMos D1 MINI ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest wemos_d1_mini32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WeMos D1 MINI ESP32 supports the next uploading protocols:
WeMos D1 MINI 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.
WeMos WiFi and Bluetooth Battery Contents • WeMos WiFi and Bluetooth Battery
Configuration Please use wemosbat ID for projectconf_env_board option in projectconf:
[env:wemosbat] platform = espressif32 board = wemosbat
You can override default WeMos WiFi and Bluetooth Battery settings per build environment using board_*** option, where *** is a JSON object path from board manifest wemosbat.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WeMos WiFi and Bluetooth Battery supports the next uploading protocols:
WeMos WiFi and Bluetooth Battery 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.
Widora AIR Contents • Widora AIR
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 16MB   │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ Widora │ └────────────────┴────────┘
Configuration Please use widora-air ID for projectconf_env_board option in projectconf:
[env:widora-air] platform = espressif32 board = widora-air
You can override default Widora AIR settings per build environment using board_*** option, where *** is a JSON object path from board manifest widora-air.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Widora AIR supports the next uploading protocols:
Debugging piodebug currently does not support Widora AIR board.
XinaBox CW02 Contents • XinaBox CW02
┌────────────────┬─────────┐ │Microcontroller │ ESP32   │ ├────────────────┼─────────┤ │Frequency       │ 240MHz  │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 320KB   │ ├────────────────┼─────────┤ │Vendor          │ XinaBox │ └────────────────┴─────────┘
Configuration Please use xinabox_cw02 ID for projectconf_env_board option in projectconf:
[env:xinabox_cw02] platform = espressif32 board = xinabox_cw02
You can override default XinaBox CW02 settings per build environment using board_*** option, where *** is a JSON object path from board manifest xinabox_cw02.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading XinaBox CW02 supports the next uploading protocols:
XinaBox CW02 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.
oddWires IoT-Bus Io Contents • oddWires IoT-Bus Io
┌────────────────┬──────────┐ │Microcontroller │ ESP32    │ ├────────────────┼──────────┤ │Frequency       │ 240MHz   │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 320KB    │ ├────────────────┼──────────┤ │Vendor          │ oddWires │ └────────────────┴──────────┘
Configuration Please use iotbusio ID for projectconf_env_board option in projectconf:
[env:iotbusio] platform = espressif32 board = iotbusio
You can override default oddWires IoT-Bus Io settings per build environment using board_*** option, where *** is a JSON object path from board manifest iotbusio.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading oddWires IoT-Bus Io supports the next uploading protocols:
oddWires IoT-Bus Io 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              │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_iot-bus-jtag          │          │ Yes     │ ├─────────────────────────────────────┼──────────┼─────────┤ │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                 │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
oddWires IoT-Bus Proteus Contents • oddWires IoT-Bus Proteus
Configuration Please use iotbusproteus ID for projectconf_env_board option in projectconf:
[env:iotbusproteus] platform = espressif32 board = iotbusproteus
You can override default oddWires IoT-Bus Proteus settings per build environment using board_*** option, where *** is a JSON object path from board manifest iotbusproteus.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading oddWires IoT-Bus Proteus supports the next uploading protocols:
oddWires IoT-Bus Proteus 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.
u-blox NINA-W10 series Contents • u-blox NINA-W10 series
┌────────────────┬────────┐ │Microcontroller │ ESP32  │ ├────────────────┼────────┤ │Frequency       │ 240MHz │ ├────────────────┼────────┤ │Flash           │ 2MB    │ ├────────────────┼────────┤ │RAM             │ 320KB  │ ├────────────────┼────────┤ │Vendor          │ u-blox │ └────────────────┴────────┘
Configuration Please use nina_w10 ID for projectconf_env_board option in projectconf:
[env:nina_w10] platform = espressif32 board = nina_w10
You can override default u-blox NINA-W10 series settings per build environment using board_*** option, where *** is a JSON object path from board manifest nina_w10.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading u-blox NINA-W10 series supports the next uploading protocols:
Debugging piodebug currently does not support u-blox NINA-W10 series board.
Espressif 8266 4D Systems gen4 IoD Range Contents • 4D Systems gen4 IoD Range
Hardware Platform platform_espressif8266: 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 │ ESP8266    │ ├────────────────┼────────────┤ │Frequency       │ 80MHz      │ ├────────────────┼────────────┤ │Flash           │ 512KB      │ ├────────────────┼────────────┤ │RAM             │ 80KB       │ ├────────────────┼────────────┤ │Vendor          │ 4D Systems │ └────────────────┴────────────┘
Configuration Please use gen4iod ID for projectconf_env_board option in projectconf:
[env:gen4iod] platform = espressif8266 board = gen4iod
You can override default 4D Systems gen4 IoD Range settings per build environment using board_*** option, where *** is a JSON object path from board manifest gen4iod.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = esp8266
Uploading 4D Systems gen4 IoD Range supports the next uploading protocols:
Debugging piodebug currently does not support 4D Systems gen4 IoD Range board.
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_esp8266-nonos-sdk │ The non-OS SDK provides a   │ │                            │ set of application          │ │                            │ programming interfaces      │ │                            │ (APIs) for core ESP8266     │ │                            │ functionalities such as     │ │                            │ data reception/transmission │ │                            │ over Wi-Fi, TCP/IP stack    │ │                            │ functions, hardware         │ │                            │ interface functions and     │ │                            │ basic system management     │ │                            │ functions.                  │ ├────────────────────────────┼─────────────────────────────┤ │framework_esp8266-rtos-sdk  │ ESP8266 SDK based on        │ │                            │ FreeRTOS, a truly free      │ │                            │ professional grade RTOS for │ │                            │ microcontrollers            │ └────────────────────────────┴─────────────────────────────┘
Adafruit HUZZAH ESP8266 Contents • Adafruit HUZZAH ESP8266
┌────────────────┬──────────┐ │Microcontroller │ ESP8266  │ ├────────────────┼──────────┤ │Frequency       │ 80MHz    │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 80KB     │ ├────────────────┼──────────┤ │Vendor          │ Adafruit │ └────────────────┴──────────┘
Configuration Please use huzzah ID for projectconf_env_board option in projectconf:
[env:huzzah] platform = espressif8266 board = huzzah
You can override default Adafruit HUZZAH ESP8266 settings per build environment using board_*** option, where *** is a JSON object path from board manifest huzzah.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit HUZZAH ESP8266 supports the next uploading protocols:
Debugging piodebug currently does not support Adafruit HUZZAH ESP8266 board.
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_esp8266-nonos-sdk │ The non-OS SDK provides a   │ │                            │ set of application          │ │                            │ programming interfaces      │ │                            │ (APIs) for core ESP8266     │ │                            │ functionalities such as     │ │                            │ data reception/transmission │ │                            │ over Wi-Fi, TCP/IP stack    │ │                            │ functions, hardware         │ │                            │ interface functions and     │ │                            │ basic system management     │ │                            │ functions.                  │ ├────────────────────────────┼─────────────────────────────┤ │framework_esp8266-rtos-sdk  │ ESP8266 SDK based on        │ │                            │ FreeRTOS, a truly free      │ │                            │ professional grade RTOS for │ │                            │ microcontrollers            │ ├────────────────────────────┼─────────────────────────────┤ │framework_simba             │ Simba is an RTOS and build  │ │                            │ framework. It aims to make  │ │                            │ embedded programming easy   │ │                            │ and portable.               │ └────────────────────────────┴─────────────────────────────┘
DigiStump Oak Contents • DigiStump Oak
┌────────────────┬───────────┐ │Microcontroller │ ESP8266   │ └────────────────┴───────────┘
│Frequency       │ 80MHz     │ ├────────────────┼───────────┤ │Flash           │ 4MB       │ ├────────────────┼───────────┤ │RAM             │ 80KB      │ ├────────────────┼───────────┤ │Vendor          │ DigiStump │ └────────────────┴───────────┘
Configuration Please use oak ID for projectconf_env_board option in projectconf:
[env:oak] platform = espressif8266 board = oak
You can override default DigiStump Oak settings per build environment using board_*** option, where *** is a JSON object path from board manifest oak.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading DigiStump Oak supports the next uploading protocols:
Debugging piodebug currently does not support DigiStump Oak board.
ESP-Mx DevKit (ESP8285) Contents • ESP-Mx DevKit (ESP8285)
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 1MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ Doit    │ └────────────────┴─────────┘
Configuration Please use espmxdevkit ID for projectconf_env_board option in projectconf:
[env:espmxdevkit] platform = espressif8266 board = espmxdevkit
You can override default ESP-Mx DevKit (ESP8285) settings per build environment using board_*** option, where *** is a JSON object path from board manifest espmxdevkit.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESP-Mx DevKit (ESP8285) supports the next uploading protocols:
Debugging piodebug currently does not support ESP-Mx DevKit (ESP8285) board.
ESP-WROOM-02 Contents • ESP-WROOM-02
┌────────────────┬───────────┐ │Microcontroller │ ESP8266   │ ├────────────────┼───────────┤ │Frequency       │ 80MHz     │ ├────────────────┼───────────┤ │Flash           │ 2MB       │ ├────────────────┼───────────┤ │RAM             │ 80KB      │ ├────────────────┼───────────┤ │Vendor          │ Espressif │ └────────────────┴───────────┘
Configuration Please use esp_wroom_02 ID for projectconf_env_board option in projectconf:
[env:esp_wroom_02] platform = espressif8266 board = esp_wroom_02
You can override default ESP-WROOM-02 settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp_wroom_02.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESP-WROOM-02 supports the next uploading protocols:
Debugging piodebug currently does not support ESP-WROOM-02 board.
ESPDuino (ESP-13 Module) Contents • ESPDuino (ESP-13 Module)
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ Doit    │ └────────────────┴─────────┘
Configuration Please use espduino ID for projectconf_env_board option in projectconf:
[env:espduino] platform = espressif8266 board = espduino
You can override default ESPDuino (ESP-13 Module) settings per build environment using board_*** option, where *** is a JSON object path from board manifest espduino.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESPDuino (ESP-13 Module) supports the next uploading protocols:
Debugging piodebug currently does not support ESPDuino (ESP-13 Module) board.
ESPectro Core Contents • ESPectro Core
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ └────────────────┴─────────┘
│Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ DycodeX │ └────────────────┴─────────┘
Configuration Please use espectro ID for projectconf_env_board option in projectconf:
[env:espectro] platform = espressif8266 board = espectro
You can override default ESPectro Core settings per build environment using board_*** option, where *** is a JSON object path from board manifest espectro.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESPectro Core supports the next uploading protocols:
Debugging piodebug currently does not support ESPectro Core board.
ESPino Contents • ESPino
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ ESPino  │ └────────────────┴─────────┘
Configuration Please use espino ID for projectconf_env_board option in projectconf:
[env:espino] platform = espressif8266 board = espino
You can override default ESPino settings per build environment using board_*** option, where *** is a JSON object path from board manifest espino.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESPino supports the next uploading protocols:
Debugging piodebug currently does not support ESPino board.
ESPresso Lite 1.0 Contents • ESPresso Lite 1.0
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ ESPert  │ └────────────────┴─────────┘
Configuration Please use espresso_lite_v1 ID for projectconf_env_board option in projectconf:
[env:espresso_lite_v1] platform = espressif8266 board = espresso_lite_v1
You can override default ESPresso Lite 1.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest espresso_lite_v1.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESPresso Lite 1.0 supports the next uploading protocols:
Debugging piodebug currently does not support ESPresso Lite 1.0 board.
ESPresso Lite 2.0 Contents • ESPresso Lite 2.0
Configuration Please use espresso_lite_v2 ID for projectconf_env_board option in projectconf:
[env:espresso_lite_v2] platform = espressif8266 board = espresso_lite_v2
You can override default ESPresso Lite 2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest espresso_lite_v2.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ESPresso Lite 2.0 supports the next uploading protocols:
Debugging piodebug currently does not support ESPresso Lite 2.0 board.
Espressif ESP8266 ESP-12E Contents • Espressif ESP8266 ESP-12E
┌────────────────┬───────────┐ │Microcontroller │ ESP8266   │ ├────────────────┼───────────┤ │Frequency       │ 80MHz     │ ├────────────────┼───────────┤ │Flash           │ 4MB       │ ├────────────────┼───────────┤ │RAM             │ 80KB      │ ├────────────────┼───────────┤ │Vendor          │ Espressif │ └────────────────┴───────────┘
Configuration Please use esp12e ID for projectconf_env_board option in projectconf:
[env:esp12e] platform = espressif8266 board = esp12e
You can override default Espressif ESP8266 ESP-12E settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp12e.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Espressif ESP8266 ESP-12E supports the next uploading protocols:
Debugging piodebug currently does not support Espressif ESP8266 ESP-12E board.
Espressif Generic ESP8266 ESP-01 1M Contents • Espressif Generic ESP8266 ESP-01 1M
┌────────────────┬───────────┐ │Microcontroller │ ESP8266   │ ├────────────────┼───────────┤ │Frequency       │ 80MHz     │ ├────────────────┼───────────┤ │Flash           │ 1MB       │ ├────────────────┼───────────┤ │RAM             │ 80KB      │ ├────────────────┼───────────┤ │Vendor          │ Espressif │ └────────────────┴───────────┘
Configuration Please use esp01_1m ID for projectconf_env_board option in projectconf:
[env:esp01_1m] platform = espressif8266 board = esp01_1m
You can override default Espressif Generic ESP8266 ESP-01 1M settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp01_1m.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Espressif Generic ESP8266 ESP-01 1M supports the next uploading protocols:
Debugging piodebug currently does not support Espressif Generic ESP8266 ESP-01 1M board.
Espressif Generic ESP8266 ESP-01 512k Contents • Espressif Generic ESP8266 ESP-01 512k
┌────────────────┬───────────┐ │Microcontroller │ ESP8266   │ ├────────────────┼───────────┤ │Frequency       │ 80MHz     │ ├────────────────┼───────────┤ │Flash           │ 512KB     │ ├────────────────┼───────────┤ │RAM             │ 80KB      │ ├────────────────┼───────────┤ │Vendor          │ Espressif │ └────────────────┴───────────┘
Configuration Please use esp01 ID for projectconf_env_board option in projectconf:
[env:esp01] platform = espressif8266 board = esp01
You can override default Espressif Generic ESP8266 ESP-01 512k settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp01.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Espressif Generic ESP8266 ESP-01 512k supports the next uploading protocols:
Debugging piodebug currently does not support Espressif Generic ESP8266 ESP-01 512k board.
Espressif Generic ESP8266 ESP-07 Contents • Espressif Generic ESP8266 ESP-07
Configuration Please use esp07 ID for projectconf_env_board option in projectconf:
[env:esp07] platform = espressif8266 board = esp07
You can override default Espressif Generic ESP8266 ESP-07 settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp07.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Espressif Generic ESP8266 ESP-07 supports the next uploading protocols:
Debugging piodebug currently does not support Espressif Generic ESP8266 ESP-07 board.
│framework_esp8266-nonos-sdk │ The non-OS SDK provides a   │ │                            │ set of application          │ │                            │ programming interfaces      │ │                            │ (APIs) for core ESP8266     │ │                            │ functionalities such as     │ │                            │ data reception/transmission │ │                            │ over Wi-Fi, TCP/IP stack    │ │                            │ functions, hardware         │ │                            │ interface functions and     │ │                            │ basic system management     │ │                            │ functions.                  │ ├────────────────────────────┼─────────────────────────────┤ │framework_esp8266-rtos-sdk  │ ESP8266 SDK based on        │ │                            │ FreeRTOS, a truly free      │ │                            │ professional grade RTOS for │ │                            │ microcontrollers            │ └────────────────────────────┴─────────────────────────────┘
Generic ESP8285 Module Contents • Generic ESP8285 Module
Configuration Please use esp8285 ID for projectconf_env_board option in projectconf:
[env:esp8285] platform = espressif8266 board = esp8285
You can override default Generic ESP8285 Module settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp8285.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Generic ESP8285 Module supports the next uploading protocols:
Debugging piodebug currently does not support Generic ESP8285 Module board.
Heltec Wifi kit 8 Contents • Heltec Wifi kit 8
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ Heltec  │ └────────────────┴─────────┘
Configuration Please use heltec_wifi_kit_8 ID for projectconf_env_board option in projectconf:
[env:heltec_wifi_kit_8] platform = espressif8266 board = heltec_wifi_kit_8
You can override default Heltec Wifi kit 8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest heltec_wifi_kit_8.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Heltec Wifi kit 8 supports the next uploading protocols:
Debugging piodebug currently does not support Heltec Wifi kit 8 board.
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_esp8266-nonos-sdk │ The non-OS SDK provides a   │ │                            │ set of application          │ │                            │ programming interfaces      │ │                            │ (APIs) for core ESP8266     │ │                            │ functionalities such as     │ │                            │ data reception/transmission │ │                            │ over Wi-Fi, TCP/IP stack    │ │                            │ functions, hardware         │ │                            │ interface functions and     │ │                            │ basic system management     │ │                            │ functions.                  │ ├────────────────────────────┼─────────────────────────────┤ │framework_esp8266-rtos-sdk  │ ESP8266 SDK based on        │ │                            │ FreeRTOS, a truly free      │ │                            │ professional grade RTOS for │ │                            │ microcontrollers            │ └────────────────────────────┴─────────────────────────────┘
Invent One Contents • Invent One
┌────────────────┬────────────┐ │Microcontroller │ ESP8266    │ ├────────────────┼────────────┤ │Frequency       │ 80MHz      │ ├────────────────┼────────────┤ │Flash           │ 4MB        │ ├────────────────┼────────────┤ │RAM             │ 80KB       │ ├────────────────┼────────────┤ │Vendor          │ Invent One │ └────────────────┴────────────┘
Configuration Please use inventone ID for projectconf_env_board option in projectconf:
[env:inventone] platform = espressif8266 board = inventone
You can override default Invent One settings per build environment using board_*** option, where *** is a JSON object path from board manifest inventone.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Invent One supports the next uploading protocols:
Debugging piodebug currently does not support Invent One board.
NodeMCU 0.9 (ESP-12 Module) Contents • NodeMCU 0.9 (ESP-12 Module)
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ NodeMCU │ └────────────────┴─────────┘
Configuration Please use nodemcu ID for projectconf_env_board option in projectconf:
[env:nodemcu] platform = espressif8266 board = nodemcu
You can override default NodeMCU 0.9 (ESP-12 Module) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nodemcu.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading NodeMCU 0.9 (ESP-12 Module) supports the next uploading protocols:
Debugging piodebug currently does not support NodeMCU 0.9 (ESP-12 Module) board.
NodeMCU 1.0 (ESP-12E Module) Contents • NodeMCU 1.0 (ESP-12E Module)
Configuration Please use nodemcuv2 ID for projectconf_env_board option in projectconf:
[env:nodemcuv2] platform = espressif8266 board = nodemcuv2
You can override default NodeMCU 1.0 (ESP-12E Module) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nodemcuv2.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading NodeMCU 1.0 (ESP-12E Module) supports the next uploading protocols:
Debugging piodebug currently does not support NodeMCU 1.0 (ESP-12E Module) board.
Olimex MOD-WIFI-ESP8266(-DEV) Contents • Olimex MOD-WIFI-ESP8266(-DEV)
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 2MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ Olimex  │ └────────────────┴─────────┘
Configuration Please use modwifi ID for projectconf_env_board option in projectconf:
[env:modwifi] platform = espressif8266 board = modwifi
You can override default Olimex MOD-WIFI-ESP8266(-DEV) settings per build environment using board_*** option, where *** is a JSON object path from board manifest modwifi.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Olimex MOD-WIFI-ESP8266(-DEV) supports the next uploading protocols:
Debugging piodebug currently does not support Olimex MOD-WIFI-ESP8266(-DEV) board.
Phoenix 1.0 Contents • Phoenix 1.0
Configuration Please use phoenix_v1 ID for projectconf_env_board option in projectconf:
[env:phoenix_v1] platform = espressif8266 board = phoenix_v1
You can override default Phoenix 1.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest phoenix_v1.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Phoenix 1.0 supports the next uploading protocols:
Debugging piodebug currently does not support Phoenix 1.0 board.
Phoenix 2.0 Contents • Phoenix 2.0
Configuration Please use phoenix_v2 ID for projectconf_env_board option in projectconf:
[env:phoenix_v2] platform = espressif8266 board = phoenix_v2
You can override default Phoenix 2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest phoenix_v2.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Phoenix 2.0 supports the next uploading protocols:
Debugging piodebug currently does not support Phoenix 2.0 board.
Schirmilabs Eduino WiFi Contents • Schirmilabs Eduino WiFi
┌────────────────┬─────────────┐ │Microcontroller │ ESP8266     │ ├────────────────┼─────────────┤ │Frequency       │ 80MHz       │ ├────────────────┼─────────────┤ │Flash           │ 4MB         │ ├────────────────┼─────────────┤ │RAM             │ 80KB        │ ├────────────────┼─────────────┤ │Vendor          │ Schirmilabs │ └────────────────┴─────────────┘
Configuration Please use eduinowifi ID for projectconf_env_board option in projectconf:
[env:eduinowifi] platform = espressif8266 board = eduinowifi
You can override default Schirmilabs Eduino WiFi settings per build environment using board_*** option, where *** is a JSON object path from board manifest eduinowifi.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Schirmilabs Eduino WiFi supports the next uploading protocols:
Debugging piodebug currently does not support Schirmilabs Eduino WiFi board.
Sonoff Basic Contents • Sonoff Basic
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 1MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ ITEAD   │ └────────────────┴─────────┘
Configuration Please use sonoff_basic ID for projectconf_env_board option in projectconf:
[env:sonoff_basic] platform = espressif8266 board = sonoff_basic
You can override default Sonoff Basic settings per build environment using board_*** option, where *** is a JSON object path from board manifest sonoff_basic.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Sonoff Basic supports the next uploading protocols:
Debugging piodebug currently does not support Sonoff Basic board.
Sonoff S20 Contents • Sonoff S20
Configuration Please use sonoff_s20 ID for projectconf_env_board option in projectconf:
[env:sonoff_s20] platform = espressif8266 board = sonoff_s20
You can override default Sonoff S20 settings per build environment using board_*** option, where *** is a JSON object path from board manifest sonoff_s20.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Sonoff S20 supports the next uploading protocols:
Debugging piodebug currently does not support Sonoff S20 board.
Sonoff SV Contents • Sonoff SV
Configuration Please use sonoff_sv ID for projectconf_env_board option in projectconf:
[env:sonoff_sv] platform = espressif8266 board = sonoff_sv
You can override default Sonoff SV settings per build environment using board_*** option, where *** is a JSON object path from board manifest sonoff_sv.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Sonoff SV supports the next uploading protocols:
Debugging piodebug currently does not support Sonoff SV board.
Sonoff TH Contents • Sonoff TH
Configuration Please use sonoff_th ID for projectconf_env_board option in projectconf:
[env:sonoff_th] platform = espressif8266 board = sonoff_th
You can override default Sonoff TH settings per build environment using board_*** option, where *** is a JSON object path from board manifest sonoff_th.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Sonoff TH supports the next uploading protocols:
Debugging piodebug currently does not support Sonoff TH board.
SparkFun Blynk Board Contents • SparkFun Blynk Board
┌────────────────┬──────────┐ │Microcontroller │ ESP8266  │ ├────────────────┼──────────┤ │Frequency       │ 80MHz    │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 80KB     │ ├────────────────┼──────────┤ │Vendor          │ SparkFun │ └────────────────┴──────────┘
Configuration Please use sparkfunBlynk ID for projectconf_env_board option in projectconf:
[env:sparkfunBlynk] platform = espressif8266 board = sparkfunBlynk
You can override default SparkFun Blynk Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfunBlynk.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun Blynk Board supports the next uploading protocols:
Debugging piodebug currently does not support SparkFun Blynk Board board.
SparkFun ESP8266 Thing Contents • SparkFun ESP8266 Thing
┌────────────────┬──────────┐ │Microcontroller │ ESP8266  │ ├────────────────┼──────────┤ │Frequency       │ 80MHz    │ ├────────────────┼──────────┤ │Flash           │ 512KB    │ ├────────────────┼──────────┤ │RAM             │ 80KB     │ ├────────────────┼──────────┤ │Vendor          │ SparkFun │ └────────────────┴──────────┘
Configuration Please use thing ID for projectconf_env_board option in projectconf:
[env:thing] platform = espressif8266 board = thing
You can override default SparkFun ESP8266 Thing settings per build environment using board_*** option, where *** is a JSON object path from board manifest thing.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun ESP8266 Thing supports the next uploading protocols:
Debugging piodebug currently does not support SparkFun ESP8266 Thing board.
SparkFun ESP8266 Thing Dev Contents • SparkFun ESP8266 Thing Dev
Configuration Please use thingdev ID for projectconf_env_board option in projectconf:
[env:thingdev] platform = espressif8266 board = thingdev
You can override default SparkFun ESP8266 Thing Dev settings per build environment using board_*** option, where *** is a JSON object path from board manifest thingdev.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SparkFun ESP8266 Thing Dev supports the next uploading protocols:
Debugging piodebug currently does not support SparkFun ESP8266 Thing Dev board.
SweetPea ESP-210 Contents • SweetPea ESP-210
┌────────────────┬──────────┐ │Microcontroller │ ESP8266  │ ├────────────────┼──────────┤ │Frequency       │ 80MHz    │ ├────────────────┼──────────┤ │Flash           │ 4MB      │ ├────────────────┼──────────┤ │RAM             │ 80KB     │ ├────────────────┼──────────┤ │Vendor          │ SweetPea │ └────────────────┴──────────┘
Configuration Please use esp210 ID for projectconf_env_board option in projectconf:
[env:esp210] platform = espressif8266 board = esp210
You can override default SweetPea ESP-210 settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp210.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SweetPea ESP-210 supports the next uploading protocols:
Debugging piodebug currently does not support SweetPea ESP-210 board.
ThaiEasyElec ESPino Contents • ThaiEasyElec ESPino
┌────────────────┬──────────────┐ │Microcontroller │ ESP8266      │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ └────────────────┴──────────────┘
│Flash           │ 4MB          │ ├────────────────┼──────────────┤ │RAM             │ 80KB         │ ├────────────────┼──────────────┤ │Vendor          │ ThaiEasyElec │ └────────────────┴──────────────┘
Configuration Please use espinotee ID for projectconf_env_board option in projectconf:
[env:espinotee] platform = espressif8266 board = espinotee
You can override default ThaiEasyElec ESPino settings per build environment using board_*** option, where *** is a JSON object path from board manifest espinotee.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ThaiEasyElec ESPino supports the next uploading protocols:
Debugging piodebug currently does not support ThaiEasyElec ESPino board.
WEMOS D1 R1 Contents • WEMOS D1 R1
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ WEMOS   │ └────────────────┴─────────┘
Configuration Please use d1 ID for projectconf_env_board option in projectconf:
[env:d1] platform = espressif8266 board = d1
You can override default WEMOS D1 R1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest d1.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WEMOS D1 R1 supports the next uploading protocols:
Debugging piodebug currently does not support WEMOS D1 R1 board.
WeMos D1 R2 and mini Contents • WeMos D1 R2 and mini
Configuration Please use d1_mini ID for projectconf_env_board option in projectconf:
[env:d1_mini] platform = espressif8266 board = d1_mini
You can override default WeMos D1 R2 and mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest d1_mini.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WeMos D1 R2 and mini supports the next uploading protocols:
Debugging piodebug currently does not support WeMos D1 R2 and mini board.
WeMos D1 mini Lite Contents • WeMos D1 mini Lite
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 1MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ WEMOS   │ └────────────────┴─────────┘
Configuration Please use d1_mini_lite ID for projectconf_env_board option in projectconf:
[env:d1_mini_lite] platform = espressif8266 board = d1_mini_lite
You can override default WeMos D1 mini Lite settings per build environment using board_*** option, where *** is a JSON object path from board manifest d1_mini_lite.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WeMos D1 mini Lite supports the next uploading protocols:
Debugging piodebug currently does not support WeMos D1 mini Lite board.
WeMos D1 mini Pro Contents • WeMos D1 mini Pro
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 16MB    │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ └────────────────┴─────────┘
│Vendor          │ WEMOS   │ └────────────────┴─────────┘
Configuration Please use d1_mini_pro ID for projectconf_env_board option in projectconf:
[env:d1_mini_pro] platform = espressif8266 board = d1_mini_pro
You can override default WeMos D1 mini Pro settings per build environment using board_*** option, where *** is a JSON object path from board manifest d1_mini_pro.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WeMos D1 mini Pro supports the next uploading protocols:
Debugging piodebug currently does not support WeMos D1 mini Pro board.
WiFi Slot Contents • WiFi Slot
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ Amperka │ └────────────────┴─────────┘
Configuration Please use wifi_slot ID for projectconf_env_board option in projectconf:
[env:wifi_slot] platform = espressif8266 board = wifi_slot