neulab/tldr huggingface dataset:
┌────────────────┬──────────────────┐ │Microcontroller │ LPC54114J256BD64 │ ├────────────────┼──────────────────┤ │Frequency       │ 100MHz           │ ├────────────────┼──────────────────┤ │Flash           │ 256KB            │ ├────────────────┼──────────────────┤ │RAM             │ 192KB            │ ├────────────────┼──────────────────┤ │Vendor          │ NXP              │ └────────────────┴──────────────────┘
Configuration Please use lpc54114 ID for projectconf_env_board option in projectconf:
[env:lpc54114] platform = nxplpc board = lpc54114
You can override default NXP LPCXpresso54114 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc54114.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc54114j256bd64
; change MCU frequency board_build.f_cpu = 100000000L
Uploading NXP LPCXpresso54114 supports the next uploading protocols:
NXP LPCXpresso54114 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
NXP LPCXpresso54608 Contents • NXP LPCXpresso54608
┌────────────────┬───────────────┐ │Microcontroller │ LPC54608ET512 │ ├────────────────┼───────────────┤ │Frequency       │ 180MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 200KB         │ ├────────────────┼───────────────┤ │Vendor          │ NXP           │ └────────────────┴───────────────┘
Configuration Please use lpc546xx ID for projectconf_env_board option in projectconf:
[env:lpc546xx] platform = nxplpc board = lpc546xx
You can override default NXP LPCXpresso54608 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc546xx.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc54608et512
Uploading NXP LPCXpresso54608 supports the next uploading protocols:
NXP LPCXpresso54608 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
NXP mbed LPC11U24 Contents • NXP mbed LPC11U24
Configuration Please use lpc11u24 ID for projectconf_env_board option in projectconf:
[env:lpc11u24] platform = nxplpc board = lpc11u24
You can override default NXP mbed LPC11U24 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u24.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading NXP mbed LPC11U24 supports the next uploading protocols:
NXP mbed LPC11U24 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
NXP mbed LPC1768 Contents • NXP mbed LPC1768
┌────────────────┬─────────┐ │Microcontroller │ LPC1768 │ ├────────────────┼─────────┤ │Frequency       │ 96MHz   │ ├────────────────┼─────────┤ │Flash           │ 512KB   │ ├────────────────┼─────────┤ │RAM             │ 64KB    │ ├────────────────┼─────────┤ │Vendor          │ NXP     │ └────────────────┴─────────┘
Configuration Please use lpc1768 ID for projectconf_env_board option in projectconf:
[env:lpc1768] platform = nxplpc board = lpc1768
You can override default NXP mbed LPC1768 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc1768.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc1768
Uploading NXP mbed LPC1768 supports the next uploading protocols:
NXP mbed LPC1768 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Outrageous Circuits mBuino Contents • Outrageous Circuits mBuino
┌────────────────┬─────────────────────┐ │Microcontroller │ LPC11U24            │ ├────────────────┼─────────────────────┤ │Frequency       │ 48MHz               │ ├────────────────┼─────────────────────┤ │Flash           │ 32KB                │ ├────────────────┼─────────────────────┤ │RAM             │ 8KB                 │ ├────────────────┼─────────────────────┤ │Vendor          │ Outrageous Circuits │ └────────────────┴─────────────────────┘
Configuration Please use mbuino ID for projectconf_env_board option in projectconf:
[env:mbuino] platform = nxplpc board = mbuino
You can override default Outrageous Circuits mBuino settings per build environment using board_*** option, where *** is a JSON object path from board manifest mbuino.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Outrageous Circuits mBuino board.
Seeed Arch GPRS V2 Contents • Seeed Arch GPRS V2
┌────────────────┬─────────────┐ │Microcontroller │ LPC11U37    │ ├────────────────┼─────────────┤ │Frequency       │ 48MHz       │ ├────────────────┼─────────────┤ │Flash           │ 128KB       │ ├────────────────┼─────────────┤ │RAM             │ 10KB        │ ├────────────────┼─────────────┤ │Vendor          │ SeeedStudio │ └────────────────┴─────────────┘
Configuration Please use seeedArchGPRS ID for projectconf_env_board option in projectconf:
[env:seeedArchGPRS] platform = nxplpc board = seeedArchGPRS
You can override default Seeed Arch GPRS V2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeedArchGPRS.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Seeed Arch GPRS V2 board.
Seeed Arch Pro Contents • Seeed Arch Pro
┌────────────────┬─────────────┐ │Microcontroller │ LPC1768     │ ├────────────────┼─────────────┤ │Frequency       │ 96MHz       │ ├────────────────┼─────────────┤ │Flash           │ 512KB       │ ├────────────────┼─────────────┤ │RAM             │ 64KB        │ ├────────────────┼─────────────┤ │Vendor          │ SeeedStudio │ └────────────────┴─────────────┘
Configuration Please use seeedArchPro ID for projectconf_env_board option in projectconf:
[env:seeedArchPro] platform = nxplpc board = seeedArchPro
You can override default Seeed Arch Pro settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeedArchPro.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Seeed Arch Pro supports the next uploading protocols:
Seeed Arch Pro has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Seeed Xadow M0 Contents • Seeed Xadow M0
┌────────────────┬─────────────┐ │Microcontroller │ LPC11U35    │ ├────────────────┼─────────────┤ │Frequency       │ 48MHz       │ ├────────────────┼─────────────┤ │Flash           │ 64KB        │ ├────────────────┼─────────────┤ │RAM             │ 10KB        │ ├────────────────┼─────────────┤ │Vendor          │ SeeedStudio │ └────────────────┴─────────────┘
Configuration Please use xadow_m0 ID for projectconf_env_board option in projectconf:
[env:xadow_m0] platform = nxplpc board = xadow_m0
You can override default Seeed Xadow M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest xadow_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Seeed Xadow M0 board.
Smeshlink xbed LPC1768 Contents • Smeshlink xbed LPC1768
┌────────────────┬───────────┐ │Microcontroller │ LPC1768   │ ├────────────────┼───────────┤ │Frequency       │ 96MHz     │ ├────────────────┼───────────┤ │Flash           │ 512KB     │ ├────────────────┼───────────┤ │RAM             │ 32KB      │ ├────────────────┼───────────┤ │Vendor          │ Smeshlink │ └────────────────┴───────────┘
Configuration Please use xbed_lpc1768 ID for projectconf_env_board option in projectconf:
[env:xbed_lpc1768] platform = nxplpc board = xbed_lpc1768
You can override default Smeshlink xbed LPC1768 settings per build environment using board_*** option, where *** is a JSON object path from board manifest xbed_lpc1768.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Smeshlink xbed LPC1768 board.
Solder Splash Labs DipCortex M0 Contents • Solder Splash Labs DipCortex M0
┌────────────────┬────────────────────┐ │Microcontroller │ LPC11U24           │ ├────────────────┼────────────────────┤ │Frequency       │ 50MHz              │ ├────────────────┼────────────────────┤ │Flash           │ 32KB               │ ├────────────────┼────────────────────┤ │RAM             │ 8KB                │ ├────────────────┼────────────────────┤ │Vendor          │ Solder Splash Labs │ └────────────────┴────────────────────┘
Configuration Please use dipcortexm0 ID for projectconf_env_board option in projectconf:
[env:dipcortexm0] platform = nxplpc board = dipcortexm0
You can override default Solder Splash Labs DipCortex M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest dipcortexm0.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Solder Splash Labs DipCortex M0 supports the next uploading protocols:
Solder Splash Labs DipCortex M0 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Switch Science mbed LPC1114FN28 Contents • Switch Science mbed LPC1114FN28
┌────────────────┬────────────────┐ │Microcontroller │ LPC1114FN28    │ ├────────────────┼────────────────┤ │Frequency       │ 48MHz          │ ├────────────────┼────────────────┤ │Flash           │ 32KB           │ ├────────────────┼────────────────┤ │RAM             │ 4KB            │ ├────────────────┼────────────────┤ │Vendor          │ Switch Science │ └────────────────┴────────────────┘
Configuration Please use lpc1114fn28 ID for projectconf_env_board option in projectconf:
[env:lpc1114fn28] platform = nxplpc board = lpc1114fn28
You can override default Switch Science mbed LPC1114FN28 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc1114fn28.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc1114fn28
Uploading Switch Science mbed LPC1114FN28 supports the next uploading protocols:
Switch Science mbed LPC1114FN28 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Switch Science mbed LPC824 Contents • Switch Science mbed LPC824
┌────────────────┬────────────────┐ │Microcontroller │ LPC824         │ ├────────────────┼────────────────┤ │Frequency       │ 30MHz          │ ├────────────────┼────────────────┤ │Flash           │ 32KB           │ ├────────────────┼────────────────┤ │RAM             │ 8KB            │ ├────────────────┼────────────────┤ │Vendor          │ Switch Science │ └────────────────┴────────────────┘
Configuration Please use ssci824 ID for projectconf_env_board option in projectconf:
[env:ssci824] platform = nxplpc board = ssci824
You can override default Switch Science mbed LPC824 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ssci824.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Switch Science mbed LPC824 supports the next uploading protocols:
Switch Science mbed LPC824 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
mBuino Contents • mBuino
┌────────────────┬─────────────────┐ │Microcontroller │ LPC11U24        │ ├────────────────┼─────────────────┤ │Frequency       │ 50MHz           │ ├────────────────┼─────────────────┤ │Flash           │ 32KB            │ ├────────────────┼─────────────────┤ │RAM             │ 10KB            │ ├────────────────┼─────────────────┤ │Vendor          │ GHI Electronics │ └────────────────┴─────────────────┘
Configuration Please use oc_mbuino ID for projectconf_env_board option in projectconf:
[env:oc_mbuino] platform = nxplpc board = oc_mbuino
You can override default mBuino settings per build environment using board_*** option, where *** is a JSON object path from board manifest oc_mbuino.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support mBuino board.
u-blox C027 Contents • u-blox C027
┌────────────────┬─────────┐ │Microcontroller │ LPC1768 │ ├────────────────┼─────────┤ │Frequency       │ 96MHz   │ ├────────────────┼─────────┤ │Flash           │ 512KB   │ ├────────────────┼─────────┤ │RAM             │ 64KB    │ ├────────────────┼─────────┤ │Vendor          │ u-blox  │ └────────────────┴─────────┘
Configuration Please use ubloxc027 ID for projectconf_env_board option in projectconf:
[env:ubloxc027] platform = nxplpc board = ubloxc027
You can override default u-blox C027 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ubloxc027.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading u-blox C027 supports the next uploading protocols:
u-blox C027 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
y5 LPC11U35 mbug Contents • y5 LPC11U35 mbug
┌────────────────┬───────────┐ │Microcontroller │ LPC11U35  │ ├────────────────┼───────────┤ │Frequency       │ 48MHz     │ ├────────────────┼───────────┤ │Flash           │ 64KB      │ ├────────────────┼───────────┤ │RAM             │ 10KB      │ ├────────────────┼───────────┤ │Vendor          │ y5 design │ └────────────────┴───────────┘
Configuration Please use lpc11u35_y5_mbug ID for projectconf_env_board option in projectconf:
[env:lpc11u35_y5_mbug] platform = nxplpc board = lpc11u35_y5_mbug
You can override default y5 LPC11U35 mbug settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u35_y5_mbug.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading y5 LPC11U35 mbug supports the next uploading protocols:
y5 LPC11U35 mbug 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.
RISC-V GAP GAPuino GAP8 Contents • GAPuino GAP8
Hardware Platform platform_riscv_gap: GreenWaves GAP8 IoT application processor enables the cost-effective development, deployment and autonomous operation of intelligent sensing devices that capture, analyze, classify and act on the fusion of rich data sources such as images, sounds or vibrations.
┌────────────────┬─────────────────────────┐ │Microcontroller │ GAP8                    │ ├────────────────┼─────────────────────────┤ │Frequency       │ 250MHz                  │ ├────────────────┼─────────────────────────┤ │Flash           │ 64MB                    │ ├────────────────┼─────────────────────────┤ │RAM             │ 8MB                     │ ├────────────────┼─────────────────────────┤ │Vendor          │ GreenWaves Technologies │ └────────────────┴─────────────────────────┘
Configuration Please use gapuino ID for projectconf_env_board option in projectconf:
[env:gapuino] platform = riscv_gap board = gapuino
You can override default GAPuino GAP8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest gapuino.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = gap8
; change MCU frequency board_build.f_cpu = 250000000L
GAPuino GAP8 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_ftdi │ Yes      │ Yes     │ └────────────────────┴──────────┴─────────┘
Shakti Artix-7 35T Arty FPGA Evaluation Kit Contents • Artix-7 35T Arty FPGA Evaluation Kit
Hardware Platform platform_shakti: Shakti is an open-source initiative by the RISE group at IIT-Madras, which is not only building open source, production grade processors, but also associated components like interconnect fabrics, verification tools, storage controllers, peripheral IPs and SOC tools.
┌────────────────┬─────────┐ │Microcontroller │ E-CLASS │ ├────────────────┼─────────┤ │Frequency       │ 50MHz   │ ├────────────────┼─────────┤ │Flash           │ 0B      │ ├────────────────┼─────────┤ │RAM             │ 128KB   │ ├────────────────┼─────────┤ │Vendor          │ Xilinx  │ └────────────────┴─────────┘
Configuration Please use artix7_35t ID for projectconf_env_board option in projectconf:
[env:artix7_35t] platform = shakti board = artix7_35t
You can override default Artix-7 35T Arty FPGA Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest artix7_35t.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = E-Class
Uploading Artix-7 35T Arty FPGA Evaluation Kit supports the next uploading protocols:
Default protocol is ftdi
upload_protocol = ftdi
Artix-7 35T Arty FPGA Evaluation 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_ftdi  │ Yes      │ Yes     │ ├─────────────────────┼──────────┼─────────┤ │debugging_tool_jlink │          │         │ └─────────────────────┴──────────┴─────────┘
Arty A7-100: Artix-7 FPGA Development Board Contents • Arty A7-100: Artix-7 FPGA Development Board
┌────────────────┬─────────┐ │Microcontroller │ C-CLASS │ ├────────────────┼─────────┤ │Frequency       │ 50MHz   │ ├────────────────┼─────────┤ │Flash           │ 0B      │ ├────────────────┼─────────┤ │RAM             │ 128MB   │ ├────────────────┼─────────┤ │Vendor          │ Xilinx  │ └────────────────┴─────────┘
Configuration Please use artix7_100t ID for projectconf_env_board option in projectconf:
[env:artix7_100t] platform = shakti board = artix7_100t
You can override default Arty A7-100: Artix-7 FPGA Development Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest artix7_100t.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = C-Class
Uploading Arty A7-100: Artix-7 FPGA Development Board supports the next uploading protocols:
Arty A7-100: Artix-7 FPGA Development Board has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SiFive Arty FPGA Dev Kit Contents • Arty FPGA Dev Kit
Hardware Platform platform_sifive: SiFive brings the power of open source and software automation to the semiconductor industry, making it possible to develop new hardware faster and more affordably than ever before.
┌────────────────┬────────┐ │Microcontroller │ FE310  │ ├────────────────┼────────┤ │Frequency       │ 450MHz │ ├────────────────┼────────┤ │Flash           │ 16MB   │ ├────────────────┼────────┤ │RAM             │ 256MB  │ ├────────────────┼────────┤ │Vendor          │ Xilinx │ └────────────────┴────────┘
Configuration Please use e310-arty ID for projectconf_env_board option in projectconf:
[env:e310-arty] platform = sifive board = e310-arty
You can override default Arty FPGA Dev Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest e310-arty.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = fe310
; change MCU frequency board_build.f_cpu = 450000000L
Uploading Arty FPGA Dev Kit supports the next uploading protocols:
Arty FPGA Dev 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_ftdi                  │ Yes      │ 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_qemu                  │ Yes      │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_renode                │ Yes      │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_tumpa                 │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
Frameworks ┌────────────────────────┬──────────────────────────┐ │Name                    │ Description              │ ├────────────────────────┼──────────────────────────┤ │framework_freedom-e-sdk │ Open Source Software for │ │                        │ Developing on the SiFive │ │                        │ Freedom E Platform       │ └────────────────────────┴──────────────────────────┘
HiFive Unleashed Contents • HiFive Unleashed
┌────────────────┬─────────┐ │Microcontroller │ FU540   │ ├────────────────┼─────────┤ │Frequency       │ 1500MHz │ ├────────────────┼─────────┤ │Flash           │ 32MB    │ ├────────────────┼─────────┤ │RAM             │ 8GB     │ ├────────────────┼─────────┤ │Vendor          │ SiFive  │ └────────────────┴─────────┘
Configuration Please use hifive-unleashed ID for projectconf_env_board option in projectconf:
[env:hifive-unleashed] platform = sifive board = hifive-unleashed
You can override default HiFive Unleashed settings per build environment using board_*** option, where *** is a JSON object path from board manifest hifive-unleashed.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = fu540
; change MCU frequency board_build.f_cpu = 1500000000L
HiFive Unleashed 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_ftdi   │ Yes      │ Yes     │ ├──────────────────────┼──────────┼─────────┤ │debugging_tool_qemu   │ Yes      │         │ ├──────────────────────┼──────────┼─────────┤ │debugging_tool_renode │ Yes      │         │ └──────────────────────┴──────────┴─────────┘
HiFive1 Contents • HiFive1
┌────────────────┬────────┐ │Microcontroller │ FE310  │ ├────────────────┼────────┤ │Frequency       │ 320MHz │ ├────────────────┼────────┤ │Flash           │ 16MB   │ ├────────────────┼────────┤ │RAM             │ 16KB   │ ├────────────────┼────────┤ │Vendor          │ SiFive │ └────────────────┴────────┘
Configuration Please use hifive1 ID for projectconf_env_board option in projectconf:
[env:hifive1] platform = sifive board = hifive1
You can override default HiFive1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest hifive1.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change MCU frequency board_build.f_cpu = 320000000L
HiFive1 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Frameworks ┌────────────────────────┬──────────────────────────┐ │Name                    │ Description              │ ├────────────────────────┼──────────────────────────┤ │framework_freedom-e-sdk │ Open Source Software for │ │                        │ Developing on the SiFive │ │                        │ Freedom E Platform       │ ├────────────────────────┼──────────────────────────┤ │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.        │ └────────────────────────┴──────────────────────────┘
HiFive1 Rev B Contents • HiFive1 Rev B
Configuration Please use hifive1-revb ID for projectconf_env_board option in projectconf:
[env:hifive1-revb] platform = sifive board = hifive1-revb
You can override default HiFive1 Rev B settings per build environment using board_*** option, where *** is a JSON object path from board manifest hifive1-revb.json. For example, board_build.mcu, board_build.f_cpu, etc.
HiFive1 Rev B 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     │ ├──────────────────────┼──────────┼─────────┤ │debugging_tool_renode │ Yes      │         │ └──────────────────────┴──────────┴─────────┘
Frameworks ┌────────────────────────┬──────────────────────────┐ │Name                    │ Description              │ └────────────────────────┴──────────────────────────┘
│framework_freedom-e-sdk │ Open Source Software for │ │                        │ Developing on the SiFive │ │                        │ Freedom E Platform       │ ├────────────────────────┼──────────────────────────┤ │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.        │ └────────────────────────┴──────────────────────────┘
SparkFun RED-V RedBoard Contents • SparkFun RED-V RedBoard
┌────────────────┬──────────┐ │Microcontroller │ FE310    │ ├────────────────┼──────────┤ │Frequency       │ 320MHz   │ ├────────────────┼──────────┤ │Flash           │ 16MB     │ ├────────────────┼──────────┤ │RAM             │ 16KB     │ ├────────────────┼──────────┤ │Vendor          │ SparkFun │ └────────────────┴──────────┘
Configuration Please use sparkfun_redboard_v ID for projectconf_env_board option in projectconf:
[env:sparkfun_redboard_v] platform = sifive board = sparkfun_redboard_v
You can override default SparkFun RED-V RedBoard settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_redboard_v.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun RED-V RedBoard has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SparkFun RED-V Thing Plus Contents • SparkFun RED-V Thing Plus
Configuration Please use sparkfun_thing_plus_v ID for projectconf_env_board option in projectconf:
[env:sparkfun_thing_plus_v] platform = sifive board = sparkfun_thing_plus_v
You can override default SparkFun RED-V Thing Plus settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_thing_plus_v.json. For example, board_build.mcu, board_build.f_cpu, etc.
SparkFun RED-V Thing Plus has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Silicon Labs EFM32 EFM32GG-STK3700 Giant Gecko Contents • EFM32GG-STK3700 Giant Gecko
Hardware Platform platform_siliconlabsefm32: Silicon Labs EFM32 Gecko 32-bit microcontroller (MCU) family includes devices that offer flash memory configurations up to 256 kB, 32 kB of RAM and CPU speeds up to 48 MHz. Based on the powerful ARM Cortex-M core, the Gecko family features innovative low energy techniques, short wake-up time from energy saving modes and a wide selection of peripherals, making it ideal for battery operated applications and other systems requiring high performance and low-energy consumption.
┌────────────────┬─────────────────┐ │Microcontroller │ EFM32GG990F1024 │ ├────────────────┼─────────────────┤ │Frequency       │ 48MHz           │ ├────────────────┼─────────────────┤ │Flash           │ 1MB             │ ├────────────────┼─────────────────┤ │RAM             │ 128KB           │ ├────────────────┼─────────────────┤ │Vendor          │ Silicon Labs    │ └────────────────┴─────────────────┘
Configuration Please use efm32gg_stk3700 ID for projectconf_env_board option in projectconf:
[env:efm32gg_stk3700] platform = siliconlabsefm32 board = efm32gg_stk3700
You can override default EFM32GG-STK3700 Giant Gecko settings per build environment using board_*** option, where *** is a JSON object path from board manifest efm32gg_stk3700.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = efm32gg990f1024
Uploading EFM32GG-STK3700 Giant Gecko supports the next uploading protocols:
EFM32GG-STK3700 Giant Gecko has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
EFM32LG-STK3600 Leopard Gecko Contents • EFM32LG-STK3600 Leopard Gecko
┌────────────────┬────────────────┐ │Microcontroller │ EFM32LG990F256 │ ├────────────────┼────────────────┤ │Frequency       │ 48MHz          │ ├────────────────┼────────────────┤ │Flash           │ 256KB          │ ├────────────────┼────────────────┤ │RAM             │ 32KB           │ ├────────────────┼────────────────┤ │Vendor          │ Silicon Labs   │ └────────────────┴────────────────┘
Configuration Please use efm32lg_stk3600 ID for projectconf_env_board option in projectconf:
[env:efm32lg_stk3600] platform = siliconlabsefm32 board = efm32lg_stk3600
You can override default EFM32LG-STK3600 Leopard Gecko settings per build environment using board_*** option, where *** is a JSON object path from board manifest efm32lg_stk3600.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = efm32lg990f256
Uploading EFM32LG-STK3600 Leopard Gecko supports the next uploading protocols:
EFM32LG-STK3600 Leopard Gecko has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
EFM32WG-STK3800 Wonder Gecko Contents • EFM32WG-STK3800 Wonder Gecko
┌────────────────┬────────────────┐ │Microcontroller │ EFM32WG990F256 │ ├────────────────┼────────────────┤ │Frequency       │ 48MHz          │ ├────────────────┼────────────────┤ │Flash           │ 256KB          │ ├────────────────┼────────────────┤ │RAM             │ 32KB           │ ├────────────────┼────────────────┤ │Vendor          │ Silicon Labs   │ └────────────────┴────────────────┘
Configuration Please use efm32wg_stk3800 ID for projectconf_env_board option in projectconf:
[env:efm32wg_stk3800] platform = siliconlabsefm32 board = efm32wg_stk3800
You can override default EFM32WG-STK3800 Wonder Gecko settings per build environment using board_*** option, where *** is a JSON object path from board manifest efm32wg_stk3800.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = efm32wg990f256
Uploading EFM32WG-STK3800 Wonder Gecko supports the next uploading protocols:
EFM32WG-STK3800 Wonder Gecko has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
EFM32ZG-STK3200 Zero Gecko Contents • EFM32ZG-STK3200 Zero Gecko
┌────────────────┬───────────────┐ │Microcontroller │ EFM32ZG222F32 │ ├────────────────┼───────────────┤ │Frequency       │ 24MHz         │ ├────────────────┼───────────────┤ │Flash           │ 32KB          │ ├────────────────┼───────────────┤ │RAM             │ 4KB           │ ├────────────────┼───────────────┤ │Vendor          │ Silicon Labs  │ └────────────────┴───────────────┘
Configuration Please use efm32zg_stk3200 ID for projectconf_env_board option in projectconf:
[env:efm32zg_stk3200] platform = siliconlabsefm32 board = efm32zg_stk3200
You can override default EFM32ZG-STK3200 Zero Gecko settings per build environment using board_*** option, where *** is a JSON object path from board manifest efm32zg_stk3200.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = efm32zg222f32
Uploading EFM32ZG-STK3200 Zero Gecko supports the next uploading protocols:
EFM32ZG-STK3200 Zero Gecko 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_jlink      │ Yes      │ Yes     │ └──────────────────────────┴──────────┴─────────┘
SLSTK3400A USB-enabled Happy Gecko Contents • SLSTK3400A USB-enabled Happy Gecko
┌────────────────┬───────────────┐ │Microcontroller │ EFM32HG322F64 │ ├────────────────┼───────────────┤ │Frequency       │ 25MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 8KB           │ ├────────────────┼───────────────┤ │Vendor          │ Silicon Labs  │ └────────────────┴───────────────┘
Configuration Please use efm32hg_stk3400 ID for projectconf_env_board option in projectconf:
[env:efm32hg_stk3400] platform = siliconlabsefm32 board = efm32hg_stk3400
You can override default SLSTK3400A USB-enabled Happy Gecko settings per build environment using board_*** option, where *** is a JSON object path from board manifest efm32hg_stk3400.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = efm32hg322f64
; change MCU frequency board_build.f_cpu = 25000000L
Uploading SLSTK3400A USB-enabled Happy Gecko supports the next uploading protocols:
SLSTK3400A USB-enabled Happy Gecko has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SLSTK3401A Pearl Gecko PG1 Contents • SLSTK3401A Pearl Gecko PG1
┌────────────────┬──────────────────────┐ │Microcontroller │ EFM32PG1B200F256GM48 │ ├────────────────┼──────────────────────┤ │Frequency       │ 40MHz                │ ├────────────────┼──────────────────────┤ │Flash           │ 256KB                │ ├────────────────┼──────────────────────┤ │RAM             │ 32KB                 │ ├────────────────┼──────────────────────┤ │Vendor          │ Silicon Labs         │ └────────────────┴──────────────────────┘
Configuration Please use efm32pg_stk3401 ID for projectconf_env_board option in projectconf:
[env:efm32pg_stk3401] platform = siliconlabsefm32 board = efm32pg_stk3401
You can override default SLSTK3401A Pearl Gecko PG1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest efm32pg_stk3401.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = efm32pg1b200f256gm48
Uploading SLSTK3401A Pearl Gecko PG1 supports the next uploading protocols:
SLSTK3401A Pearl Gecko PG1 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT Contents • Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT
┌────────────────┬────────────────────┐ │Microcontroller │ EFR32MG12P432F1024 │ ├────────────────┼────────────────────┤ │Frequency       │ 40MHz              │ ├────────────────┼────────────────────┤ │Flash           │ 1MB                │ ├────────────────┼────────────────────┤ │RAM             │ 256KB              │ ├────────────────┼────────────────────┤ │Vendor          │ Silicon Labs       │ └────────────────┴────────────────────┘
Configuration Please use tb_sense_12 ID for projectconf_env_board option in projectconf:
[env:tb_sense_12] platform = siliconlabsefm32 board = tb_sense_12
You can override default Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT settings per build environment using board_*** option, where *** is a JSON object path from board manifest tb_sense_12.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = EFR32MG12P432F1024
Uploading Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT supports the next uploading protocols:
Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST STM32 1Bitsy Contents • 1Bitsy
Hardware Platform platform_ststm32: The STM32 family of 32-bit Flash MCUs based on the ARM Cortex-M processor is designed to offer new degrees of freedom to MCU users. It offers a 32-bit product range that combines very high performance, real-time capabilities, digital signal processing, and low-power, low-voltage operation, while maintaining full integration and ease of development.
┌────────────────┬──────────────┐ │Microcontroller │ STM32F415RGT │ ├────────────────┼──────────────┤ │Frequency       │ 168MHz       │ ├────────────────┼──────────────┤ │Flash           │ 1MB          │ ├────────────────┼──────────────┤ │RAM             │ 128KB        │ ├────────────────┼──────────────┤ │Vendor          │ 1BitSquared  │ └────────────────┴──────────────┘
Configuration Please use 1bitsy_stm32f415rgt ID for projectconf_env_board option in projectconf:
[env:1bitsy_stm32f415rgt] platform = ststm32 board = 1bitsy_stm32f415rgt
You can override default 1Bitsy settings per build environment using board_*** option, where *** is a JSON object path from board manifest 1bitsy_stm32f415rgt.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f415rgt
; change MCU frequency board_build.f_cpu = 168000000L
Uploading 1Bitsy supports the next uploading protocols:
1Bitsy 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.
Frameworks ┌─────────────────────┬─────────────────────────────┐ │Name                 │ Description                 │ ├─────────────────────┼─────────────────────────────┤ │framework_cmsis      │ The ARM Cortex              │ │                     │ Microcontroller Software    │ │                     │ Interface Standard (CMSIS)  │ │                     │ is a vendor-independent     │ │                     │ hardware abstraction layer  │ │                     │ for the Cortex-M processor  │ │                     │ series and specifies        │ │                     │ debugger interfaces. The    │ │                     │ CMSIS enables consistent    │ │                     │ and simple software         │ │                     │ interfaces to the processor │ │                     │ for interface peripherals,  │ │                     │ real-time operating         │ │                     │ systems, and middleware. It │ │                     │ simplifies software re-use, │ │                     │ reducing the learning curve │ │                     │ for new microcontroller     │ │                     │ developers and cutting the  │ │                     │ time-to-market for devices. │ ├─────────────────────┼─────────────────────────────┤ │framework_libopencm3 │ The libOpenCM3 framework    │ │                     │ aims to create a            │ │                     │ free/libre/open-source      │ │                     │ firmware library for        │ │                     │ various ARM                 │ │                     │ Cortex-M0(+)/M3/M4          │ │                     │ microcontrollers, including │ │                     │ ST STM32, Ti Tiva and       │ │                     │ Stellaris, NXP LPC 11xx,    │ │                     │ 13xx, 15xx, 17xx parts,     │ │                     │ Atmel SAM3, Energy Micro    │ │                     │ EFM32 and others.           │ ├─────────────────────┼─────────────────────────────┤ │framework_spl        │ The ST Standard Peripheral  │ │                     │ Library provides a set of   │ │                     │ functions for handling the  │ │                     │ peripherals on the STM32    │ │                     │ Cortex-M3 family. The idea  │ │                     │ is to save the user (the    │ │                     │ new user, in particular)    │ │                     │ having to deal directly     │ │                     │ with the registers.         │ ├─────────────────────┼─────────────────────────────┤ │framework_stm32cube  │ STM32Cube embedded software │ │                     │ libraries, including: The   │ │                     │ HAL hardware abstraction    │ │                     │ layer, enabling portability │ │                     │ between different STM32     │ │                     │ devices via standardized    │ │                     │ API calls; The Low-Layer    │ │                     │ (LL) APIs, a light-weight,  │ │                     │ optimized, expert oriented  │ │                     │ set of APIs designed for    │ │                     │ both performance and        │ │                     │ runtime efficiency.         │ └─────────────────────┴─────────────────────────────┘
32F412GDISCOVERY Contents • 32F412GDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F412ZGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 100MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 256KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f412zg ID for projectconf_env_board option in projectconf:
[env:disco_f412zg] platform = ststm32 board = disco_f412zg
You can override default 32F412GDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f412zg.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f412zgt6
Uploading 32F412GDISCOVERY supports the next uploading protocols:
32F412GDISCOVERY 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_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ ├────────────────────┼─────────────────────────────┤ │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.           │ └────────────────────┴─────────────────────────────┘
32F723EDISCOVERY Contents • 32F723EDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F723IEK6 │ ├────────────────┼───────────────┤ │Frequency       │ 216MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 192KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f723ie ID for projectconf_env_board option in projectconf:
[env:disco_f723ie] platform = ststm32 board = disco_f723ie
You can override default 32F723EDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f723ie.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f723iek6
; change MCU frequency board_build.f_cpu = 216000000L
Uploading 32F723EDISCOVERY supports the next uploading protocols:
32F723EDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Frameworks ┌────────────────────┬─────────────────────────────┐ │Name                │ Description                 │ ├────────────────────┼─────────────────────────────┤ │framework_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ ├────────────────────┼─────────────────────────────┤ │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.           │ └────────────────────┴─────────────────────────────┘
3D Printer Controller Contents • 3D Printer Controller
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407VET6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 192KB         │ ├────────────────┼───────────────┤ │Vendor          │ Armed         │ └────────────────┴───────────────┘
Configuration Please use armed_v1 ID for projectconf_env_board option in projectconf:
[env:armed_v1] platform = ststm32 board = armed_v1
You can override default 3D Printer Controller settings per build environment using board_*** option, where *** is a JSON object path from board manifest armed_v1.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f407vet6
Uploading 3D Printer Controller supports the next uploading protocols:
3D Printer Controller 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.