neulab/tldr huggingface dataset:
You can override default WiFi Slot settings per build environment using board_*** option, where *** is a JSON object path from board manifest wifi_slot.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WiFi Slot supports the next uploading protocols:
Debugging piodebug currently does not support WiFi Slot board.
WiFiduino Contents • WiFiduino
│Frequency       │ 80MHz     │ ├────────────────┼───────────┤ │Flash           │ 4MB       │ ├────────────────┼───────────┤ │RAM             │ 80KB      │ ├────────────────┼───────────┤ │Vendor          │ WifiDuino │ └────────────────┴───────────┘
Configuration Please use wifiduino ID for projectconf_env_board option in projectconf:
[env:wifiduino] platform = espressif8266 board = wifiduino
You can override default WiFiduino settings per build environment using board_*** option, where *** is a JSON object path from board manifest wifiduino.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WiFiduino supports the next uploading protocols:
Debugging piodebug currently does not support WiFiduino board.
WifInfo Contents • WifInfo
Configuration Please use wifinfo ID for projectconf_env_board option in projectconf:
[env:wifinfo] platform = espressif8266 board = wifinfo
You can override default WifInfo settings per build environment using board_*** option, where *** is a JSON object path from board manifest wifinfo.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading WifInfo supports the next uploading protocols:
Debugging piodebug currently does not support WifInfo board.
Wio Link Contents • Wio Link
┌────────────────┬─────────────┐ │Microcontroller │ ESP8266     │ ├────────────────┼─────────────┤ │Frequency       │ 80MHz       │ ├────────────────┼─────────────┤ │Flash           │ 4MB         │ ├────────────────┼─────────────┤ │RAM             │ 80KB        │ ├────────────────┼─────────────┤ │Vendor          │ SeeedStudio │ └────────────────┴─────────────┘
Configuration Please use wio_link ID for projectconf_env_board option in projectconf:
[env:wio_link] platform = espressif8266 board = wio_link
You can override default Wio Link settings per build environment using board_*** option, where *** is a JSON object path from board manifest wio_link.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Wio Link supports the next uploading protocols:
Debugging piodebug currently does not support Wio Link board.
Wio Node Contents • Wio Node
Configuration Please use wio_node ID for projectconf_env_board option in projectconf:
[env:wio_node] platform = espressif8266 board = wio_node
You can override default Wio Node settings per build environment using board_*** option, where *** is a JSON object path from board manifest wio_node.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Wio Node supports the next uploading protocols:
Debugging piodebug currently does not support Wio Node board.
XinaBox CW01 Contents • XinaBox CW01
┌────────────────┬─────────┐ │Microcontroller │ ESP8266 │ ├────────────────┼─────────┤ │Frequency       │ 80MHz   │ ├────────────────┼─────────┤ │Flash           │ 4MB     │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ XinaBox │ └────────────────┴─────────┘
Configuration Please use xinabox_cw01 ID for projectconf_env_board option in projectconf:
[env:xinabox_cw01] platform = espressif8266 board = xinabox_cw01
You can override default XinaBox CW01 settings per build environment using board_*** option, where *** is a JSON object path from board manifest xinabox_cw01.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading XinaBox CW01 supports the next uploading protocols:
Debugging piodebug currently does not support XinaBox CW01 board.
Freescale Kinetis Ethernet IoT Starter Kit Contents • Ethernet IoT Starter Kit
Hardware Platform platform_freescalekinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.
┌────────────────┬────────────────┐ │Microcontroller │ MK64FN1M0VLL12 │ ├────────────────┼────────────────┤ │Frequency       │ 120MHz         │ ├────────────────┼────────────────┤ │Flash           │ 1MB            │ ├────────────────┼────────────────┤ │RAM             │ 256KB          │ ├────────────────┼────────────────┤ │Vendor          │ Freescale      │ └────────────────┴────────────────┘
Configuration Please use IBMEthernetKit ID for projectconf_env_board option in projectconf:
[env:IBMEthernetKit] platform = freescalekinetis board = IBMEthernetKit
You can override default Ethernet IoT Starter Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest IBMEthernetKit.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mk64fn1m0vll12
Uploading Ethernet IoT Starter Kit supports the next uploading protocols:
• mbed
Default protocol is mbed
upload_protocol = mbed
Ethernet IoT Starter 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_cmsis-dap │ Yes      │ Yes     │ ├─────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink     │          │         │ └─────────────────────────┴──────────┴─────────┘
Frameworks ┌───────────────┬─────────────────────────────┐ │Name           │ Description                 │ └───────────────┴─────────────────────────────┘
│framework_mbed │ The mbed framework The mbed │ │               │ SDK has been designed to    │ │               │ provide enough hardware     │ │               │ abstraction to be intuitive │ │               │ and concise, yet powerful   │ │               │ enough to build complex     │ │               │ projects. It is built on    │ │               │ the low-level ARM CMSIS     │ │               │ APIs, allowing you to code  │ │               │ down to the metal if        │ │               │ needed. In addition to      │ │               │ RTOS, USB and Networking    │ │               │ libraries, a cookbook of    │ │               │ hundreds of reusable        │ │               │ peripheral and module       │ │               │ libraries have been built   │ │               │ on top of the SDK by the    │ │               │ mbed Developer Community.   │ └───────────────┴─────────────────────────────┘
Freescale Kinetis FRDM-K20D50M Contents • Freescale Kinetis FRDM-K20D50M
┌────────────────┬───────────────┐ │Microcontroller │ MK20DX128VLH5 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ Freescale     │ └────────────────┴───────────────┘
Configuration Please use frdm_k20d50m ID for projectconf_env_board option in projectconf:
[env:frdm_k20d50m] platform = freescalekinetis board = frdm_k20d50m
You can override default Freescale Kinetis FRDM-K20D50M settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_k20d50m.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mk20dx128vlh5
Uploading Freescale Kinetis FRDM-K20D50M supports the next uploading protocols:
Freescale Kinetis FRDM-K20D50M has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Freescale Kinetis FRDM-K22F Contents • Freescale Kinetis FRDM-K22F
┌────────────────┬────────────────┐ │Microcontroller │ MK22FN512VLH12 │ ├────────────────┼────────────────┤ │Frequency       │ 120MHz         │ ├────────────────┼────────────────┤ │Flash           │ 512KB          │ ├────────────────┼────────────────┤ │RAM             │ 128KB          │ ├────────────────┼────────────────┤ │Vendor          │ Freescale      │ └────────────────┴────────────────┘
Configuration Please use frdm_k22f ID for projectconf_env_board option in projectconf:
[env:frdm_k22f] platform = freescalekinetis board = frdm_k22f
You can override default Freescale Kinetis FRDM-K22F settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_k22f.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mk22fn512vlh12
Uploading Freescale Kinetis FRDM-K22F supports the next uploading protocols:
Freescale Kinetis FRDM-K22F has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Freescale Kinetis FRDM-K64F Contents • Freescale Kinetis FRDM-K64F
Configuration Please use frdm_k64f ID for projectconf_env_board option in projectconf:
[env:frdm_k64f] platform = freescalekinetis board = frdm_k64f
You can override default Freescale Kinetis FRDM-K64F settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_k64f.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Freescale Kinetis FRDM-K64F supports the next uploading protocols:
Freescale Kinetis FRDM-K64F has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Freescale Kinetis FRDM-K66F Contents • Freescale Kinetis FRDM-K66F
┌────────────────┬────────────────┐ │Microcontroller │ MK66FN2M0VMD18 │ ├────────────────┼────────────────┤ │Frequency       │ 180MHz         │ ├────────────────┼────────────────┤ │Flash           │ 2MB            │ ├────────────────┼────────────────┤ │RAM             │ 256KB          │ ├────────────────┼────────────────┤ │Vendor          │ Freescale      │ └────────────────┴────────────────┘
Configuration Please use frdm_k66f ID for projectconf_env_board option in projectconf:
[env:frdm_k66f] platform = freescalekinetis board = frdm_k66f
You can override default Freescale Kinetis FRDM-K66F settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_k66f.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mk66fn2m0vmd18
Uploading Freescale Kinetis FRDM-K66F supports the next uploading protocols:
Freescale Kinetis FRDM-K66F has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Freescale Kinetis FRDM-K82F Contents • Freescale Kinetis FRDM-K82F
┌────────────────┬────────────────┐ │Microcontroller │ MK82FN256VLL15 │ ├────────────────┼────────────────┤ │Frequency       │ 150MHz         │ ├────────────────┼────────────────┤ │Flash           │ 256KB          │ ├────────────────┼────────────────┤ │RAM             │ 256KB          │ ├────────────────┼────────────────┤ │Vendor          │ Freescale      │ └────────────────┴────────────────┘
Configuration Please use frdm_k82f ID for projectconf_env_board option in projectconf:
[env:frdm_k82f] platform = freescalekinetis board = frdm_k82f
You can override default Freescale Kinetis FRDM-K82F settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_k82f.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mk82fn256vll15
; change MCU frequency board_build.f_cpu = 150000000L
Uploading Freescale Kinetis FRDM-K82F supports the next uploading protocols:
Freescale Kinetis FRDM-K82F has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Frameworks ┌─────────────────┬─────────────────────────────┐ │Name             │ Description                 │ └─────────────────┴─────────────────────────────┘
│framework_mbed   │ The mbed framework The mbed │ │                 │ SDK has been designed to    │ │                 │ provide enough hardware     │ │                 │ abstraction to be intuitive │ │                 │ and concise, yet powerful   │ │                 │ enough to build complex     │ │                 │ projects. It is built on    │ │                 │ the low-level ARM CMSIS     │ │                 │ APIs, allowing you to code  │ │                 │ down to the metal if        │ │                 │ needed. In addition to      │ │                 │ RTOS, USB and Networking    │ │                 │ libraries, a cookbook of    │ │                 │ hundreds of reusable        │ │                 │ peripheral and module       │ │                 │ libraries have been built   │ │                 │ on top of the SDK by the    │ │                 │ mbed Developer Community.   │ ├─────────────────┼─────────────────────────────┤ │framework_zephyr │ The Zephyr Project is a     │ │                 │ scalable real-time          │ │                 │ operating system (RTOS)     │ │                 │ supporting multiple         │ │                 │ hardware architectures,     │ │                 │ optimized for resource      │ │                 │ constrained devices, and    │ │                 │ built with safety and       │ │                 │ security in mind.           │ └─────────────────┴─────────────────────────────┘
Freescale Kinetis FRDM-KL05Z Contents • Freescale Kinetis FRDM-KL05Z
┌────────────────┬──────────────┐ │Microcontroller │ MKL05Z32VFM4 │ ├────────────────┼──────────────┤ │Frequency       │ 48MHz        │ ├────────────────┼──────────────┤ │Flash           │ 32KB         │ ├────────────────┼──────────────┤ │RAM             │ 4KB          │ ├────────────────┼──────────────┤ │Vendor          │ Freescale    │ └────────────────┴──────────────┘
Configuration Please use frdm_kl05z ID for projectconf_env_board option in projectconf:
[env:frdm_kl05z] platform = freescalekinetis board = frdm_kl05z
You can override default Freescale Kinetis FRDM-KL05Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl05z.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mkl05z32vfm4
Uploading Freescale Kinetis FRDM-KL05Z supports the next uploading protocols:
Freescale Kinetis FRDM-KL05Z has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Freescale Kinetis FRDM-KL25Z Contents • Freescale Kinetis FRDM-KL25Z
┌────────────────┬───────────────┐ │Microcontroller │ MKL25Z128VLK4 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ Freescale     │ └────────────────┴───────────────┘
Configuration Please use frdm_kl25z ID for projectconf_env_board option in projectconf:
[env:frdm_kl25z] platform = freescalekinetis board = frdm_kl25z
You can override default Freescale Kinetis FRDM-KL25Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl25z.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mkl25z128vlk4
Uploading Freescale Kinetis FRDM-KL25Z supports the next uploading protocols:
Freescale Kinetis FRDM-KL25Z 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_blackmagic │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_cmsis-dap  │ Yes      │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ └──────────────────────────┴──────────┴─────────┘
Freescale Kinetis FRDM-KL27Z Contents • Freescale Kinetis FRDM-KL27Z
┌────────────────┬──────────────┐ │Microcontroller │ MKL27Z64VLH4 │ ├────────────────┼──────────────┤ │Frequency       │ 48MHz        │ ├────────────────┼──────────────┤ │Flash           │ 64KB         │ ├────────────────┼──────────────┤ │RAM             │ 16KB         │ ├────────────────┼──────────────┤ │Vendor          │ Freescale    │ └────────────────┴──────────────┘
Configuration Please use frdm_kl27z ID for projectconf_env_board option in projectconf:
[env:frdm_kl27z] platform = freescalekinetis board = frdm_kl27z
You can override default Freescale Kinetis FRDM-KL27Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl27z.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mkl27z64vlh4
Uploading Freescale Kinetis FRDM-KL27Z supports the next uploading protocols:
Freescale Kinetis FRDM-KL27Z has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Freescale Kinetis FRDM-KL43Z Contents • Freescale Kinetis FRDM-KL43Z
┌────────────────┬───────────────┐ │Microcontroller │ MKL43Z256VLH4 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ Freescale     │ └────────────────┴───────────────┘
Configuration Please use frdm_kl43z ID for projectconf_env_board option in projectconf:
[env:frdm_kl43z] platform = freescalekinetis board = frdm_kl43z
You can override default Freescale Kinetis FRDM-KL43Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl43z.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mkl43z256vlh4
Uploading Freescale Kinetis FRDM-KL43Z supports the next uploading protocols:
Freescale Kinetis FRDM-KL43Z has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Freescale Kinetis FRDM-KL46Z Contents • Freescale Kinetis FRDM-KL46Z
┌────────────────┬───────────────┐ │Microcontroller │ MKL46Z256VLL4 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ Freescale     │ └────────────────┴───────────────┘
Configuration Please use frdm_kl46z ID for projectconf_env_board option in projectconf:
[env:frdm_kl46z] platform = freescalekinetis board = frdm_kl46z
You can override default Freescale Kinetis FRDM-KL46Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl46z.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mkl46z256vll4
Uploading Freescale Kinetis FRDM-KL46Z supports the next uploading protocols:
Freescale Kinetis FRDM-KL46Z has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Freescale Kinetis FRDM-KL82Z Contents • Freescale Kinetis FRDM-KL82Z
┌────────────────┬───────────────┐ │Microcontroller │ MKL82Z128VLK7 │ ├────────────────┼───────────────┤ │Frequency       │ 96MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 96KB          │ ├────────────────┼───────────────┤ │Vendor          │ Freescale     │ └────────────────┴───────────────┘
Configuration Please use frdm_kl82z ID for projectconf_env_board option in projectconf:
[env:frdm_kl82z] platform = freescalekinetis board = frdm_kl82z
You can override default Freescale Kinetis FRDM-KL82Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl82z.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mkl82z128vlk7
; change MCU frequency board_build.f_cpu = 96000000L
Uploading Freescale Kinetis FRDM-KL82Z supports the next uploading protocols:
Freescale Kinetis FRDM-KL82Z 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_jlink │          │ Yes     │ └─────────────────────┴──────────┴─────────┘
Freescale Kinetis FRDM-KW24D512 Contents • Freescale Kinetis FRDM-KW24D512
┌────────────────┬───────────┐ │Microcontroller │ MKW24D512 │ ├────────────────┼───────────┤ │Frequency       │ 50MHz     │ ├────────────────┼───────────┤ │Flash           │ 512KB     │ ├────────────────┼───────────┤ │RAM             │ 64KB      │ ├────────────────┼───────────┤ │Vendor          │ Freescale │ └────────────────┴───────────┘
Configuration Please use frdm_kw24d ID for projectconf_env_board option in projectconf:
[env:frdm_kw24d] platform = freescalekinetis board = frdm_kw24d
You can override default Freescale Kinetis FRDM-KW24D512 settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kw24d.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mkw24d512
; change MCU frequency board_build.f_cpu = 50000000L
Uploading Freescale Kinetis FRDM-KW24D512 supports the next uploading protocols:
Freescale Kinetis FRDM-KW24D512 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.
Freescale Kinetis FRDM-KW41Z Contents • Freescale Kinetis FRDM-KW41Z
┌────────────────┬───────────────┐ │Microcontroller │ MKW41Z512VHT4 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ Freescale     │ └────────────────┴───────────────┘
Configuration Please use frdm_kw41z ID for projectconf_env_board option in projectconf:
[env:frdm_kw41z] platform = freescalekinetis board = frdm_kw41z
You can override default Freescale Kinetis FRDM-KW41Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kw41z.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mkw41z512vht4
Uploading Freescale Kinetis FRDM-KW41Z supports the next uploading protocols:
Freescale Kinetis FRDM-KW41Z has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Hexiwear Contents • Hexiwear
┌────────────────┬──────────────────┐ │Microcontroller │ MK64FN1M0VDC12   │ ├────────────────┼──────────────────┤ │Frequency       │ 120MHz           │ ├────────────────┼──────────────────┤ │Flash           │ 1MB              │ └────────────────┴──────────────────┘
│RAM             │ 256KB            │ ├────────────────┼──────────────────┤ │Vendor          │ MikroElektronika │ └────────────────┴──────────────────┘
Configuration Please use hexiwear ID for projectconf_env_board option in projectconf:
[env:hexiwear] platform = freescalekinetis board = hexiwear
You can override default Hexiwear settings per build environment using board_*** option, where *** is a JSON object path from board manifest hexiwear.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mk64fn1m0vdc12
Uploading Hexiwear supports the next uploading protocols:
Hexiwear 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_cmsis-dap │          │ Yes     │ ├─────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink     │          │         │ └─────────────────────────┴──────────┴─────────┘
GigaDevice GD32V GD32VF103V-EVAL Contents • GD32VF103V-EVAL
Hardware Platform platform_gd32v: The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.
┌────────────────┬───────────────┐ │Microcontroller │ GD32VF103VBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 108MHz        │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ Sipeed        │ └────────────────┴───────────────┘
Configuration Please use gd32vf103v-eval ID for projectconf_env_board option in projectconf:
[env:gd32vf103v-eval] platform = gd32v board = gd32vf103v-eval
You can override default GD32VF103V-EVAL settings per build environment using board_*** option, where *** is a JSON object path from board manifest gd32vf103v-eval.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = GD32VF103VBT6
; change MCU frequency board_build.f_cpu = 108000000L
Uploading GD32VF103V-EVAL supports the next uploading protocols:
• altera-usb-blaster
• gd-link
• rv-link
• serial
• sipeed-rv-debugger
• um232h
Default protocol is gd-link
upload_protocol = gd-link
GD32VF103V-EVAL 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_altera-usb-blaster │          │ Yes     │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_gd-link            │          │         │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink              │          │         │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_rv-link            │          │         │ └──────────────────────────────────┴──────────┴─────────┘
│debugging_tool_sipeed-rv-debugger │          │         │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_um232h             │          │         │ └──────────────────────────────────┴──────────┴─────────┘
Sipeed Longan Nano Contents • Sipeed Longan Nano
┌────────────────┬───────────────┐ │Microcontroller │ GD32VF103CBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 108MHz        │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ Sipeed        │ └────────────────┴───────────────┘
Configuration Please use sipeed-longan-nano ID for projectconf_env_board option in projectconf:
[env:sipeed-longan-nano] platform = gd32v board = sipeed-longan-nano
You can override default Sipeed Longan Nano settings per build environment using board_*** option, where *** is a JSON object path from board manifest sipeed-longan-nano.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = GD32VF103CBT6
Uploading Sipeed Longan Nano supports the next uploading protocols:
Default protocol is serial
upload_protocol = serial
Sipeed Longan Nano 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_altera-usb-blaster │          │ Yes     │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_gd-link            │          │         │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink              │          │         │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_rv-link            │          │         │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_sipeed-rv-debugger │          │         │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_um232h             │          │         │ └──────────────────────────────────┴──────────┴─────────┘
Sipeed Longan Nano Lite Contents • Sipeed Longan Nano Lite
┌────────────────┬───────────────┐ │Microcontroller │ GD32VF103C8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 108MHz        │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Sipeed        │ └────────────────┴───────────────┘
Configuration Please use sipeed-longan-nano-lite ID for projectconf_env_board option in projectconf:
[env:sipeed-longan-nano-lite] platform = gd32v board = sipeed-longan-nano-lite
You can override default Sipeed Longan Nano Lite settings per build environment using board_*** option, where *** is a JSON object path from board manifest sipeed-longan-nano-lite.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = GD32VF103C8T6
Uploading Sipeed Longan Nano Lite supports the next uploading protocols:
Sipeed Longan Nano Lite does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Wio Lite RISC-V Contents • Wio Lite RISC-V
┌────────────────┬───────────────┐ │Microcontroller │ GD32VF103CBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 108MHz        │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ SeeedStudio   │ └────────────────┴───────────────┘
Configuration Please use wio_lite_risc-v ID for projectconf_env_board option in projectconf:
[env:wio_lite_risc-v] platform = gd32v board = wio_lite_risc-v
You can override default Wio Lite RISC-V settings per build environment using board_*** option, where *** is a JSON object path from board manifest wio_lite_risc-v.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Wio Lite RISC-V supports the next uploading protocols:
Wio Lite RISC-V 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.
Infineon XMC XMC1100 Boot Kit Contents • XMC1100 Boot Kit
Hardware Platform platform_infineonxmc: Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform
┌────────────────┬──────────┐ │Microcontroller │ XMC1100  │ ├────────────────┼──────────┤ │Frequency       │ 32MHz    │ ├────────────────┼──────────┤ │Flash           │ 64KB     │ ├────────────────┼──────────┤ │RAM             │ 16KB     │ ├────────────────┼──────────┤ │Vendor          │ Infineon │ └────────────────┴──────────┘
Configuration Please use xmc1100_boot_kit ID for projectconf_env_board option in projectconf:
[env:xmc1100_boot_kit] platform = infineonxmc board = xmc1100_boot_kit
You can override default XMC1100 Boot Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1100_boot_kit.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = XMC1100
; change MCU frequency board_build.f_cpu = 32000000L
XMC1100 Boot 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_jlink │ Yes      │ Yes     │ └─────────────────────┴──────────┴─────────┘
XMC1100 H-Bridge 2Go Contents • XMC1100 H-Bridge 2Go
Configuration Please use xmc1100_h_bridge2go ID for projectconf_env_board option in projectconf:
[env:xmc1100_h_bridge2go] platform = infineonxmc board = xmc1100_h_bridge2go
You can override default XMC1100 H-Bridge 2Go settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1100_h_bridge2go.json. For example, board_build.mcu, board_build.f_cpu, etc.
XMC1100 H-Bridge 2Go has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
XMC1100 XMC2Go Contents • XMC1100 XMC2Go
Configuration Please use xmc1100_xmc2go ID for projectconf_env_board option in projectconf:
[env:xmc1100_xmc2go] platform = infineonxmc board = xmc1100_xmc2go
You can override default XMC1100 XMC2Go settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1100_xmc2go.json. For example, board_build.mcu, board_build.f_cpu, etc.
XMC1100 XMC2Go has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
XMC1300 Boot Kit Contents • XMC1300 Boot Kit
┌────────────────┬──────────┐ │Microcontroller │ XMC1300  │ ├────────────────┼──────────┤ │Frequency       │ 32MHz    │ ├────────────────┼──────────┤ │Flash           │ 64KB     │ ├────────────────┼──────────┤ │RAM             │ 16KB     │ ├────────────────┼──────────┤ │Vendor          │ Infineon │ └────────────────┴──────────┘
Configuration Please use xmc1300_boot_kit ID for projectconf_env_board option in projectconf:
[env:xmc1300_boot_kit] platform = infineonxmc board = xmc1300_boot_kit
You can override default XMC1300 Boot Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1300_boot_kit.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = XMC1300
XMC1300 Boot Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
XMC1300 Sense2GoL Contents • XMC1300 Sense2GoL
┌────────────────┬──────────┐ │Microcontroller │ XMC1300  │ ├────────────────┼──────────┤ │Frequency       │ 32MHz    │ ├────────────────┼──────────┤ │Flash           │ 32KB     │ ├────────────────┼──────────┤ │RAM             │ 16KB     │ ├────────────────┼──────────┤ │Vendor          │ Infineon │ └────────────────┴──────────┘
Configuration Please use xmc1300_sense2gol ID for projectconf_env_board option in projectconf:
[env:xmc1300_sense2gol] platform = infineonxmc board = xmc1300_sense2gol
You can override default XMC1300 Sense2GoL settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1300_sense2gol.json. For example, board_build.mcu, board_build.f_cpu, etc.
XMC1300 Sense2GoL has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
XMC1400 Boot Kit Contents • XMC1400 Boot Kit
┌────────────────┬──────────┐ │Microcontroller │ XMC1400  │ ├────────────────┼──────────┤ │Frequency       │ 48MHz    │ ├────────────────┼──────────┤ │Flash           │ 1.95MB   │ ├────────────────┼──────────┤ │RAM             │ 16KB     │ ├────────────────┼──────────┤ │Vendor          │ Infineon │ └────────────────┴──────────┘
Configuration Please use xmc1400_boot_kit ID for projectconf_env_board option in projectconf:
[env:xmc1400_boot_kit] platform = infineonxmc board = xmc1400_boot_kit
You can override default XMC1400 Boot Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1400_boot_kit.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = XMC1400
XMC1400 Boot Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
XMC4200 Distance2Go Contents • XMC4200 Distance2Go
┌────────────────┬──────────┐ │Microcontroller │ XMC4200  │ ├────────────────┼──────────┤ │Frequency       │ 80MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 40KB     │ ├────────────────┼──────────┤ │Vendor          │ Infineon │ └────────────────┴──────────┘
Configuration Please use xmc4200_distance2go ID for projectconf_env_board option in projectconf:
[env:xmc4200_distance2go] platform = infineonxmc board = xmc4200_distance2go
You can override default XMC4200 Distance2Go settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc4200_distance2go.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = XMC4200
XMC4200 Distance2Go has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
XMC4700 Relax Kit Contents • XMC4700 Relax Kit
┌────────────────┬──────────┐ │Microcontroller │ XMC4700  │ ├────────────────┼──────────┤ │Frequency       │ 144MHz   │ └────────────────┴──────────┘
│Flash           │ 2.00MB   │ ├────────────────┼──────────┤ │RAM             │ 1.95MB   │ ├────────────────┼──────────┤ │Vendor          │ Infineon │ └────────────────┴──────────┘
Configuration Please use xmc4700_relax_kit ID for projectconf_env_board option in projectconf:
[env:xmc4700_relax_kit] platform = infineonxmc board = xmc4700_relax_kit
You can override default XMC4700 Relax Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc4700_relax_kit.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = XMC4700
; change MCU frequency board_build.f_cpu = 144000000L
XMC4700 Relax Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Intel ARC32 Arduino/Genuino 101 Contents • Arduino/Genuino 101
Hardware Platform platform_intel_arc32: ARC embedded processors are a family of 32-bit CPUs that are widely used in SoC devices for storage, home, mobile, automotive, and Internet of Things applications.
┌────────────────┬─────────┐ │Microcontroller │ ARCV2EM │ ├────────────────┼─────────┤ │Frequency       │ 32MHz   │ ├────────────────┼─────────┤ │Flash           │ 152KB   │ ├────────────────┼─────────┤ │RAM             │ 80KB    │ ├────────────────┼─────────┤ │Vendor          │ Intel   │ └────────────────┴─────────┘
Configuration Please use genuino101 ID for projectconf_env_board option in projectconf:
[env:genuino101] platform = intel_arc32 board = genuino101
You can override default Arduino/Genuino 101 settings per build environment using board_*** option, where *** is a JSON object path from board manifest genuino101.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = ARCv2EM
Debugging piodebug currently does not support Arduino/Genuino 101 board.
Intel MCS-51 (8051) Generic N79E8432 Contents • Generic N79E8432
Hardware Platform platform_intel_mcs51: The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.
┌────────────────┬──────────┐ │Microcontroller │ N79E8432 │ ├────────────────┼──────────┤ │Frequency       │ 22MHz    │ ├────────────────┼──────────┤ │Flash           │ 4KB      │ ├────────────────┼──────────┤ │RAM             │ 512B     │ ├────────────────┼──────────┤ │Vendor          │ Nuvoton  │ └────────────────┴──────────┘
Configuration Please use n79e8432 ID for projectconf_env_board option in projectconf:
[env:n79e8432] platform = intel_mcs51 board = n79e8432
You can override default Generic N79E8432 settings per build environment using board_*** option, where *** is a JSON object path from board manifest n79e8432.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = n79e8432
; change MCU frequency board_build.f_cpu = 22118400L
Debugging piodebug currently does not support Generic N79E8432 board.
Generic N79E844 Contents • Generic N79E844
┌────────────────┬─────────┐ │Microcontroller │ N79E844 │ ├────────────────┼─────────┤ │Frequency       │ 22MHz   │ └────────────────┴─────────┘
│Flash           │ 8KB     │ ├────────────────┼─────────┤ │RAM             │ 512B    │ ├────────────────┼─────────┤ │Vendor          │ Nuvoton │ └────────────────┴─────────┘
Configuration Please use n79e844 ID for projectconf_env_board option in projectconf:
[env:n79e844] platform = intel_mcs51 board = n79e844
You can override default Generic N79E844 settings per build environment using board_*** option, where *** is a JSON object path from board manifest n79e844.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = n79e844
Debugging piodebug currently does not support Generic N79E844 board.
Generic N79E845 Contents • Generic N79E845
┌────────────────┬─────────┐ │Microcontroller │ N79E845 │ ├────────────────┼─────────┤ │Frequency       │ 22MHz   │ ├────────────────┼─────────┤ │Flash           │ 16KB    │ ├────────────────┼─────────┤ │RAM             │ 512B    │ ├────────────────┼─────────┤ │Vendor          │ Nuvoton │ └────────────────┴─────────┘
Configuration Please use n79e845 ID for projectconf_env_board option in projectconf:
[env:n79e845] platform = intel_mcs51 board = n79e845
You can override default Generic N79E845 settings per build environment using board_*** option, where *** is a JSON object path from board manifest n79e845.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = n79e845
Debugging piodebug currently does not support Generic N79E845 board.
Generic N79E854 Contents • Generic N79E854
┌────────────────┬─────────┐ │Microcontroller │ N79E854 │ ├────────────────┼─────────┤ │Frequency       │ 22MHz   │ ├────────────────┼─────────┤ │Flash           │ 8KB     │ ├────────────────┼─────────┤ │RAM             │ 512B    │ ├────────────────┼─────────┤ │Vendor          │ Nuvoton │ └────────────────┴─────────┘
Configuration Please use n79e854 ID for projectconf_env_board option in projectconf:
[env:n79e854] platform = intel_mcs51 board = n79e854
You can override default Generic N79E854 settings per build environment using board_*** option, where *** is a JSON object path from board manifest n79e854.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = n79e854
Debugging piodebug currently does not support Generic N79E854 board.
Generic N79E855 Contents • Generic N79E855
┌────────────────┬─────────┐ │Microcontroller │ N79E855 │ ├────────────────┼─────────┤ │Frequency       │ 22MHz   │ ├────────────────┼─────────┤ │Flash           │ 16KB    │ ├────────────────┼─────────┤ │RAM             │ 512B    │ ├────────────────┼─────────┤ │Vendor          │ Nuvoton │ └────────────────┴─────────┘
Configuration Please use n79e855 ID for projectconf_env_board option in projectconf:
[env:n79e855] platform = intel_mcs51 board = n79e855
You can override default Generic N79E855 settings per build environment using board_*** option, where *** is a JSON object path from board manifest n79e855.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = n79e855
Debugging piodebug currently does not support Generic N79E855 board.
Generic STC15F204EA Contents • Generic STC15F204EA
┌────────────────┬─────────────┐ │Microcontroller │ STC15F204EA │ └────────────────┴─────────────┘
│Frequency       │ 11MHz       │ ├────────────────┼─────────────┤ │Flash           │ 4KB         │ ├────────────────┼─────────────┤ │RAM             │ 256B        │ ├────────────────┼─────────────┤ │Vendor          │ STC         │ └────────────────┴─────────────┘
Configuration Please use stc15f204ea ID for projectconf_env_board option in projectconf:
[env:stc15f204ea] platform = intel_mcs51 board = stc15f204ea
You can override default Generic STC15F204EA settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc15f204ea.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stc15f204ea
; change MCU frequency board_build.f_cpu = 11059200L
Debugging piodebug currently does not support Generic STC15F204EA board.
Generic STC15F2K60S2 Contents • Generic STC15F2K60S2
┌────────────────┬──────────────┐ │Microcontroller │ STC15F2K60S2 │ ├────────────────┼──────────────┤ │Frequency       │ 6MHz         │ ├────────────────┼──────────────┤ │Flash           │ 60KB         │ ├────────────────┼──────────────┤ │RAM             │ 2KB          │ ├────────────────┼──────────────┤ │Vendor          │ STC          │ └────────────────┴──────────────┘
Configuration Please use stc15f2k60s2 ID for projectconf_env_board option in projectconf:
[env:stc15f2k60s2] platform = intel_mcs51 board = stc15f2k60s2
You can override default Generic STC15F2K60S2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc15f2k60s2.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stc15f2k60s2
; change MCU frequency board_build.f_cpu = 6000000L
Debugging piodebug currently does not support Generic STC15F2K60S2 board.
Generic STC15W204S Contents • Generic STC15W204S
┌────────────────┬────────────┐ │Microcontroller │ STC15W204S │ ├────────────────┼────────────┤ │Frequency       │ 11MHz      │ ├────────────────┼────────────┤ │Flash           │ 4KB        │ ├────────────────┼────────────┤ │RAM             │ 256B       │ ├────────────────┼────────────┤ │Vendor          │ STC        │ └────────────────┴────────────┘
Configuration Please use stc15w204s ID for projectconf_env_board option in projectconf:
[env:stc15w204s] platform = intel_mcs51 board = stc15w204s
You can override default Generic STC15W204S settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc15w204s.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stc15w204s
Debugging piodebug currently does not support Generic STC15W204S board.
Generic STC15W404AS Contents • Generic STC15W404AS
┌────────────────┬─────────────┐ │Microcontroller │ STC15W404AS │ ├────────────────┼─────────────┤ │Frequency       │ 11MHz       │ ├────────────────┼─────────────┤ │Flash           │ 4KB         │ ├────────────────┼─────────────┤ │RAM             │ 512B        │ ├────────────────┼─────────────┤ │Vendor          │ STC         │ └────────────────┴─────────────┘
Configuration Please use stc15w404as ID for projectconf_env_board option in projectconf:
[env:stc15w404as] platform = intel_mcs51 board = stc15w404as
You can override default Generic STC15W404AS settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc15w404as.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stc15w404as
Debugging piodebug currently does not support Generic STC15W404AS board.
Generic STC15W408AS Contents • Generic STC15W408AS
┌────────────────┬─────────────┐ │Microcontroller │ STC15W408AS │ ├────────────────┼─────────────┤ │Frequency       │ 11MHz       │ ├────────────────┼─────────────┤ │Flash           │ 8KB         │ ├────────────────┼─────────────┤ │RAM             │ 512B        │ ├────────────────┼─────────────┤ │Vendor          │ STC         │ └────────────────┴─────────────┘
Configuration Please use stc15w408as ID for projectconf_env_board option in projectconf:
[env:stc15w408as] platform = intel_mcs51 board = stc15w408as
You can override default Generic STC15W408AS settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc15w408as.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stc15w408as
Debugging piodebug currently does not support Generic STC15W408AS board.
Generic STC89C52RC Contents • Generic STC89C52RC
┌────────────────┬────────────┐ │Microcontroller │ STC89C52RC │ ├────────────────┼────────────┤ │Frequency       │ 11MHz      │ ├────────────────┼────────────┤ │Flash           │ 8KB        │ ├────────────────┼────────────┤ │RAM             │ 512B       │ ├────────────────┼────────────┤ │Vendor          │ STC        │ └────────────────┴────────────┘