neulab/tldr huggingface dataset:
Configuration Please use stc89c52rc ID for projectconf_env_board option in projectconf:
[env:stc89c52rc] platform = intel_mcs51 board = stc89c52rc
You can override default Generic STC89C52RC settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc89c52rc.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stc89c52rc
Debugging piodebug currently does not support Generic STC89C52RC board.
Kendryte K210 Sipeed MAIX BiT Contents • Sipeed MAIX BiT
Hardware Platform platform_kendryte210: Kendryte K210 is an AI capable RISCV64 dual core SoC.
┌────────────────┬────────┐ │Microcontroller │ K210   │ ├────────────────┼────────┤ │Frequency       │ 400MHz │ ├────────────────┼────────┤ │Flash           │ 16MB   │ ├────────────────┼────────┤ │RAM             │ 6MB    │ ├────────────────┼────────┤ │Vendor          │ Sipeed │ └────────────────┴────────┘
Configuration Please use sipeed-maix-bit ID for projectconf_env_board option in projectconf:
[env:sipeed-maix-bit] platform = kendryte210 board = sipeed-maix-bit
You can override default Sipeed MAIX BiT settings per build environment using board_*** option, where *** is a JSON object path from board manifest sipeed-maix-bit.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = K210
; change MCU frequency board_build.f_cpu = 400000000L
Uploading Sipeed MAIX BiT supports the next uploading protocols:
• kflash
Default protocol is kflash
upload_protocol = kflash
Sipeed MAIX BiT 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_iot-bus-jtag          │          │ Yes     │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink                 │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_minimodule            │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-ocd    │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-ocd-h  │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-tiny-h │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-jtag-tiny      │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_sipeed-rv-debugger    │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
│debugging_tool_tumpa                 │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
Frameworks ┌──────────────────────────────────┬─────────────────────────────┐ │Name                              │ Description                 │ ├──────────────────────────────────┼─────────────────────────────┤ │framework_arduino                 │ Arduino Wiring-based        │ │                                  │ Framework allows writing    │ │                                  │ cross-platform software to  │ │                                  │ control devices attached to │ │                                  │ a wide range of Arduino     │ │                                  │ boards to create all kinds  │ │                                  │ of creative coding,         │ │                                  │ interactive objects, spaces │ │                                  │ or physical experiences.    │ ├──────────────────────────────────┼─────────────────────────────┤ │framework_kendryte-standalone-sdk │ Kendryte Standalone SDK     │ │                                  │ without OS support          │ ├──────────────────────────────────┼─────────────────────────────┤ │framework_kendryte-freertos-sdk   │ Kendryte SDK with FreeRTOS  │ │                                  │ support                     │ └──────────────────────────────────┴─────────────────────────────┘
Sipeed MAIX BiT with Mic Contents • Sipeed MAIX BiT with Mic
Configuration Please use sipeed-maix-bit-mic ID for projectconf_env_board option in projectconf:
[env:sipeed-maix-bit-mic] platform = kendryte210 board = sipeed-maix-bit-mic
You can override default Sipeed MAIX BiT with Mic settings per build environment using board_*** option, where *** is a JSON object path from board manifest sipeed-maix-bit-mic.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Sipeed MAIX BiT with Mic supports the next uploading protocols:
Sipeed MAIX BiT with Mic 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_iot-bus-jtag          │          │ Yes     │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink                 │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_minimodule            │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-ocd    │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-ocd-h  │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-tiny-h │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-jtag-tiny      │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_sipeed-rv-debugger    │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_tumpa                 │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
Sipeed MAIX GO Contents • Sipeed MAIX GO
Configuration Please use sipeed-maix-go ID for projectconf_env_board option in projectconf:
[env:sipeed-maix-go] platform = kendryte210 board = sipeed-maix-go
You can override default Sipeed MAIX GO settings per build environment using board_*** option, where *** is a JSON object path from board manifest sipeed-maix-go.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Sipeed MAIX GO supports the next uploading protocols:
Sipeed MAIX GO 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.
Sipeed MAIX ONE DOCK Contents • Sipeed MAIX ONE DOCK
Configuration Please use sipeed-maix-one-dock ID for projectconf_env_board option in projectconf:
[env:sipeed-maix-one-dock] platform = kendryte210 board = sipeed-maix-one-dock
You can override default Sipeed MAIX ONE DOCK settings per build environment using board_*** option, where *** is a JSON object path from board manifest sipeed-maix-one-dock.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Sipeed MAIX ONE DOCK supports the next uploading protocols:
Sipeed MAIX ONE DOCK 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_iot-bus-jtag          │          │ Yes     │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink                 │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_minimodule            │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-ocd    │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
│debugging_tool_olimex-arm-usb-ocd-h  │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-arm-usb-tiny-h │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_olimex-jtag-tiny      │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_sipeed-rv-debugger    │          │         │ ├─────────────────────────────────────┼──────────┼─────────┤ │debugging_tool_tumpa                 │          │         │ └─────────────────────────────────────┴──────────┴─────────┘
Sipeed MAIXDUINO Contents • Sipeed MAIXDUINO
Configuration Please use sipeed-maixduino ID for projectconf_env_board option in projectconf:
[env:sipeed-maixduino] platform = kendryte210 board = sipeed-maixduino
You can override default Sipeed MAIXDUINO settings per build environment using board_*** option, where *** is a JSON object path from board manifest sipeed-maixduino.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Sipeed MAIXDUINO supports the next uploading protocols:
Sipeed MAIXDUINO 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.
Sipeed MF1 MF1 Contents • Sipeed MF1 MF1
Configuration Please use sipeed-MF1 ID for projectconf_env_board option in projectconf:
[env:sipeed-MF1] platform = kendryte210 board = sipeed-MF1
You can override default Sipeed MF1 MF1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest sipeed-MF1.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Sipeed MF1 MF1 supports the next uploading protocols:
Sipeed MF1 MF1 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_kendryte-standalone-sdk │ Kendryte Standalone SDK    │ │                                  │ without OS support         │ ├──────────────────────────────────┼────────────────────────────┤ │framework_kendryte-freertos-sdk   │ Kendryte SDK with FreeRTOS │ │                                  │ support                    │ └──────────────────────────────────┴────────────────────────────┘
Lattice iCE40 IceZUM Alhambra FPGA Contents • IceZUM Alhambra FPGA
Hardware Platform platform_lattice_ice40: The iCE40 family of ultra-low power, non-volatile FPGAs has five devices with densities ranging from 384 to 7680 Look-Up Tables (LUTs). In addition to LUT-based,low-cost programmable logic, these devices feature Embedded Block RAM (EBR), Non-volatile Configuration Memory (NVCM) and Phase Locked Loops (PLLs). These features allow the devices to be used in low-cost, high-volume consumer and system applications.
┌────────────────┬──────────────────┐ │Microcontroller │ ICE40-HX1K-TQ144 │ ├────────────────┼──────────────────┤ │Frequency       │ 12MHz            │ ├────────────────┼──────────────────┤ │Flash           │ 32KB             │ ├────────────────┼──────────────────┤ │RAM             │ 32KB             │ ├────────────────┼──────────────────┤ │Vendor          │ FPGAwars         │ └────────────────┴──────────────────┘
Configuration Please use icezum ID for projectconf_env_board option in projectconf:
[env:icezum] platform = lattice_ice40 board = icezum
You can override default IceZUM Alhambra FPGA settings per build environment using board_*** option, where *** is a JSON object path from board manifest icezum.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = iCE40-HX1K-TQ144
Debugging piodebug currently does not support IceZUM Alhambra FPGA board.
Lattice iCEstick FPGA Evaluation Kit Contents • Lattice iCEstick FPGA Evaluation Kit
┌────────────────┬──────────────────┐ │Microcontroller │ ICE40-HX1K-TQ144 │ ├────────────────┼──────────────────┤ │Frequency       │ 12MHz            │ ├────────────────┼──────────────────┤ │Flash           │ 32KB             │ ├────────────────┼──────────────────┤ │RAM             │ 32KB             │ ├────────────────┼──────────────────┤ │Vendor          │ Lattice          │ └────────────────┴──────────────────┘
Configuration Please use icestick ID for projectconf_env_board option in projectconf:
[env:icestick] platform = lattice_ice40 board = icestick
You can override default Lattice iCEstick FPGA Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest icestick.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Lattice iCEstick FPGA Evaluation Kit board.
Linux ARM Raspberry Pi 1 Model B Contents • Raspberry Pi 1 Model B
Hardware Platform platform_linux_arm: Linux ARM is a Unix-like and mostly POSIX-compliant computer operating system (OS) assembled under the model of free and open-source software development and distribution. Using host OS (Mac OS X, Linux ARM) you can build native application for Linux ARM platform.
┌────────────────┬──────────────┐ │Microcontroller │ BCM2835      │ ├────────────────┼──────────────┤ │Frequency       │ 700MHz       │ ├────────────────┼──────────────┤ │Flash           │ 512MB        │ ├────────────────┼──────────────┤ │RAM             │ 512MB        │ ├────────────────┼──────────────┤ │Vendor          │ Raspberry Pi │ └────────────────┴──────────────┘
Configuration Please use raspberrypi_1b ID for projectconf_env_board option in projectconf:
[env:raspberrypi_1b] platform = linux_arm board = raspberrypi_1b
You can override default Raspberry Pi 1 Model B settings per build environment using board_*** option, where *** is a JSON object path from board manifest raspberrypi_1b.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = bcm2835
; change MCU frequency board_build.f_cpu = 700000000L
Debugging piodebug currently does not support Raspberry Pi 1 Model B board.
Frameworks ┌───────────────────┬─────────────────────────────┐ │Name               │ Description                 │ ├───────────────────┼─────────────────────────────┤ │framework_wiringpi │ WiringPi is a GPIO access   │ │                   │ library written in C for    │ │                   │ the BCM2835 used in the     │ │                   │ Raspberry Pi. It's designed │ │                   │ to be familiar to people    │ │                   │ who have used the Arduino   │ │                   │ "wiring" system.            │ └───────────────────┴─────────────────────────────┘
Raspberry Pi 2 Model B Contents • Raspberry Pi 2 Model B
┌────────────────┬──────────────┐ │Microcontroller │ BCM2836      │ ├────────────────┼──────────────┤ │Frequency       │ 900MHz       │ ├────────────────┼──────────────┤ │Flash           │ 1GB          │ ├────────────────┼──────────────┤ │RAM             │ 1GB          │ ├────────────────┼──────────────┤ │Vendor          │ Raspberry Pi │ └────────────────┴──────────────┘
Configuration Please use raspberrypi_2b ID for projectconf_env_board option in projectconf:
[env:raspberrypi_2b] platform = linux_arm board = raspberrypi_2b
You can override default Raspberry Pi 2 Model B settings per build environment using board_*** option, where *** is a JSON object path from board manifest raspberrypi_2b.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = bcm2836
; change MCU frequency board_build.f_cpu = 900000000L
Debugging piodebug currently does not support Raspberry Pi 2 Model B board.
Raspberry Pi 3 Model B Contents • Raspberry Pi 3 Model B
┌────────────────┬──────────────┐ │Microcontroller │ BCM2837      │ ├────────────────┼──────────────┤ │Frequency       │ 1200MHz      │ ├────────────────┼──────────────┤ │Flash           │ 1GB          │ ├────────────────┼──────────────┤ │RAM             │ 1GB          │ ├────────────────┼──────────────┤ │Vendor          │ Raspberry Pi │ └────────────────┴──────────────┘
Configuration Please use raspberrypi_3b ID for projectconf_env_board option in projectconf:
[env:raspberrypi_3b] platform = linux_arm board = raspberrypi_3b
You can override default Raspberry Pi 3 Model B settings per build environment using board_*** option, where *** is a JSON object path from board manifest raspberrypi_3b.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = bcm2837
; change MCU frequency board_build.f_cpu = 1200000000L
Debugging piodebug currently does not support Raspberry Pi 3 Model B board.
Raspberry Pi Zero Contents • Raspberry Pi Zero
┌────────────────┬──────────────┐ │Microcontroller │ BCM2835      │ ├────────────────┼──────────────┤ │Frequency       │ 1000MHz      │ ├────────────────┼──────────────┤ │Flash           │ 512MB        │ ├────────────────┼──────────────┤ │RAM             │ 512MB        │ ├────────────────┼──────────────┤ │Vendor          │ Raspberry Pi │ └────────────────┴──────────────┘
Configuration Please use raspberrypi_zero ID for projectconf_env_board option in projectconf:
[env:raspberrypi_zero] platform = linux_arm board = raspberrypi_zero
You can override default Raspberry Pi Zero settings per build environment using board_*** option, where *** is a JSON object path from board manifest raspberrypi_zero.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change MCU frequency board_build.f_cpu = 1000000000L
Debugging piodebug currently does not support Raspberry Pi Zero board.
Maxim 32 MAX32620FTHR Contents • MAX32620FTHR
Hardware Platform platform_maxim32: Maxim's microcontrollers provide low-power, efficient, and secure solutions for challenging embedded applications. Maxim's processors embed cutting-edge technologies to secure data and intellectual property, proven analog circuitry for real-world applications, and battery-conserving low power operation.
┌────────────────┬──────────────┐ │Microcontroller │ MAX32620FTHR │ ├────────────────┼──────────────┤ │Frequency       │ 96MHz        │ ├────────────────┼──────────────┤ │Flash           │ 2MB          │ ├────────────────┼──────────────┤ │RAM             │ 256KB        │ ├────────────────┼──────────────┤ │Vendor          │ Maxim        │ └────────────────┴──────────────┘
Configuration Please use max32620fthr ID for projectconf_env_board option in projectconf:
[env:max32620fthr] platform = maxim32 board = max32620fthr
You can override default MAX32620FTHR settings per build environment using board_*** option, where *** is a JSON object path from board manifest max32620fthr.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = max32620fthr
Uploading MAX32620FTHR supports the next uploading protocols:
MAX32620FTHR 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.
MAX32625MBED Contents • MAX32625MBED
┌────────────────┬──────────┐ │Microcontroller │ MAX32625 │ ├────────────────┼──────────┤ │Frequency       │ 96MHz    │ ├────────────────┼──────────┤ │Flash           │ 512KB    │ ├────────────────┼──────────┤ │RAM             │ 160KB    │ ├────────────────┼──────────┤ │Vendor          │ Maxim    │ └────────────────┴──────────┘
Configuration Please use max32625mbed ID for projectconf_env_board option in projectconf:
[env:max32625mbed] platform = maxim32 board = max32625mbed
You can override default MAX32625MBED settings per build environment using board_*** option, where *** is a JSON object path from board manifest max32625mbed.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = max32625
Debugging piodebug currently does not support MAX32625MBED board.
MAX32625NEXPAQ Contents • MAX32625NEXPAQ
Configuration Please use max32625nexpaq ID for projectconf_env_board option in projectconf:
[env:max32625nexpaq] platform = maxim32 board = max32625nexpaq
You can override default MAX32625NEXPAQ settings per build environment using board_*** option, where *** is a JSON object path from board manifest max32625nexpaq.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support MAX32625NEXPAQ board.
MAX32625PICO Contents • MAX32625PICO
Configuration Please use max32625pico ID for projectconf_env_board option in projectconf:
[env:max32625pico] platform = maxim32 board = max32625pico
You can override default MAX32625PICO settings per build environment using board_*** option, where *** is a JSON object path from board manifest max32625pico.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support MAX32625PICO board.
Maxim ARM mbed Enabled Development Platform for MAX32600 Contents • Maxim ARM mbed Enabled Development Platform for MAX32600
┌────────────────┬──────────┐ │Microcontroller │ MAX32600 │ ├────────────────┼──────────┤ │Frequency       │ 24MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 32KB     │ ├────────────────┼──────────┤ │Vendor          │ Maxim    │ └────────────────┴──────────┘
Configuration Please use max32600mbed ID for projectconf_env_board option in projectconf:
[env:max32600mbed] platform = maxim32 board = max32600mbed
You can override default Maxim ARM mbed Enabled Development Platform for MAX32600 settings per build environment using board_*** option, where *** is a JSON object path from board manifest max32600mbed.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = max32600
; change MCU frequency board_build.f_cpu = 24000000L
Uploading Maxim ARM mbed Enabled Development Platform for MAX32600 supports the next uploading protocols:
Maxim ARM mbed Enabled Development Platform for MAX32600 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     │ └─────────────────────────┴──────────┴─────────┘
Maxim Health Sensor Platform Contents • Maxim Health Sensor Platform
┌────────────────┬──────────┐ │Microcontroller │ MAX32620 │ ├────────────────┼──────────┤ │Frequency       │ 96MHz    │ ├────────────────┼──────────┤ │Flash           │ 2MB      │ ├────────────────┼──────────┤ │RAM             │ 256KB    │ ├────────────────┼──────────┤ │Vendor          │ Maxim    │ └────────────────┴──────────┘
Configuration Please use max32620hsp ID for projectconf_env_board option in projectconf:
[env:max32620hsp] platform = maxim32 board = max32620hsp
You can override default Maxim Health Sensor Platform settings per build environment using board_*** option, where *** is a JSON object path from board manifest max32620hsp.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = max32620
Uploading Maxim Health Sensor Platform supports the next uploading protocols:
Maxim Health Sensor Platform 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.
Maxim MAX32630FTHR Application Platform Contents • Maxim MAX32630FTHR Application Platform
┌────────────────┬──────────┐ │Microcontroller │ MAX32630 │ ├────────────────┼──────────┤ │Frequency       │ 96MHz    │ ├────────────────┼──────────┤ │Flash           │ 2MB      │ ├────────────────┼──────────┤ │RAM             │ 512KB    │ ├────────────────┼──────────┤ │Vendor          │ Maxim    │ └────────────────┴──────────┘
Configuration Please use max32630fthr ID for projectconf_env_board option in projectconf:
[env:max32630fthr] platform = maxim32 board = max32630fthr
You can override default Maxim MAX32630FTHR Application Platform settings per build environment using board_*** option, where *** is a JSON object path from board manifest max32630fthr.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = max32630
Debugging piodebug currently does not support Maxim MAX32630FTHR Application Platform board.
Maxim Wireless Sensor Node Demonstrator Contents • Maxim Wireless Sensor Node Demonstrator
┌────────────────┬──────────┐ │Microcontroller │ MAX32610 │ ├────────────────┼──────────┤ │Frequency       │ 24MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 32KB     │ ├────────────────┼──────────┤ │Vendor          │ Maxim    │ └────────────────┴──────────┘
Configuration Please use maxwsnenv ID for projectconf_env_board option in projectconf:
[env:maxwsnenv] platform = maxim32 board = maxwsnenv
You can override default Maxim Wireless Sensor Node Demonstrator settings per build environment using board_*** option, where *** is a JSON object path from board manifest maxwsnenv.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = max32610
Uploading Maxim Wireless Sensor Node Demonstrator supports the next uploading protocols:
Maxim Wireless Sensor Node Demonstrator 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     │ └─────────────────────────┴──────────┴─────────┘
SDT32620B Contents • SDT32620B
┌────────────────┬──────────────────────────┐ │Microcontroller │ MAX32620IWG              │ ├────────────────┼──────────────────────────┤ │Frequency       │ 96MHz                    │ ├────────────────┼──────────────────────────┤ │Flash           │ 2MB                      │ ├────────────────┼──────────────────────────┤ │RAM             │ 256KB                    │ ├────────────────┼──────────────────────────┤ │Vendor          │ Sigma Delta Technologies │ └────────────────┴──────────────────────────┘
Configuration Please use sdt32620b ID for projectconf_env_board option in projectconf:
[env:sdt32620b] platform = maxim32 board = sdt32620b
You can override default SDT32620B settings per build environment using board_*** option, where *** is a JSON object path from board manifest sdt32620b.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = max32620iwg
Debugging piodebug currently does not support SDT32620B board.
SDT32625B Contents • SDT32625B
┌────────────────┬──────────────────────────┐ │Microcontroller │ MAX32625ITK              │ ├────────────────┼──────────────────────────┤ │Frequency       │ 96MHz                    │ ├────────────────┼──────────────────────────┤ │Flash           │ 512KB                    │ ├────────────────┼──────────────────────────┤ │RAM             │ 160KB                    │ ├────────────────┼──────────────────────────┤ │Vendor          │ Sigma Delta Technologies │ └────────────────┴──────────────────────────┘
Configuration Please use sdt32625b ID for projectconf_env_board option in projectconf:
[env:sdt32625b] platform = maxim32 board = sdt32625b
You can override default SDT32625B settings per build environment using board_*** option, where *** is a JSON object path from board manifest sdt32625b.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = max32625itk
Debugging piodebug currently does not support SDT32625B board.
Microchip PIC32 4D Systems PICadillo 35T Contents • 4D Systems PICadillo 35T
Hardware Platform platform_microchippic32: Microchip's 32-bit portfolio with the MIPS microAptiv or M4K core offer high performance microcontrollers, and all the tools needed to develop your embedded projects. PIC32 MCUs gives your application the processing power, memory and peripherals your design needs!
┌────────────────┬──────────────┐ │Microcontroller │ 32MX795F512L │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 128KB        │ ├────────────────┼──────────────┤ │Vendor          │ 4D Systems   │ └────────────────┴──────────────┘
Configuration Please use picadillo_35t ID for projectconf_env_board option in projectconf:
[env:picadillo_35t] platform = microchippic32 board = picadillo_35t
You can override default 4D Systems PICadillo 35T settings per build environment using board_*** option, where *** is a JSON object path from board manifest picadillo_35t.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX795F512L
Debugging piodebug currently does not support 4D Systems PICadillo 35T board.
DataStation Mini Contents • DataStation Mini
┌────────────────┬──────────────┐ │Microcontroller │ 32MX150F128C │ ├────────────────┼──────────────┤ │Frequency       │ 40MHz        │ ├────────────────┼──────────────┤ │Flash           │ 120KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ Makerology   │ └────────────────┴──────────────┘
Configuration Please use dsmini ID for projectconf_env_board option in projectconf:
[env:dsmini] platform = microchippic32 board = dsmini
You can override default DataStation Mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest dsmini.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX150F128C
; change MCU frequency board_build.f_cpu = 40000000L
Debugging piodebug currently does not support DataStation Mini board.
Digilent Cerebot 32MX4 Contents • Digilent Cerebot 32MX4
┌────────────────┬──────────────┐ │Microcontroller │ 32MX460F512L │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ Digilent     │ └────────────────┴──────────────┘
Configuration Please use cerebot32mx4 ID for projectconf_env_board option in projectconf:
[env:cerebot32mx4] platform = microchippic32 board = cerebot32mx4
You can override default Digilent Cerebot 32MX4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest cerebot32mx4.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX460F512L
Debugging piodebug currently does not support Digilent Cerebot 32MX4 board.
Digilent Cerebot 32MX7 Contents • Digilent Cerebot 32MX7
┌────────────────┬──────────────┐ │Microcontroller │ 32MX795F512L │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 128KB        │ ├────────────────┼──────────────┤ │Vendor          │ Digilent     │ └────────────────┴──────────────┘
Configuration Please use cerebot32mx7 ID for projectconf_env_board option in projectconf:
[env:cerebot32mx7] platform = microchippic32 board = cerebot32mx7
You can override default Digilent Cerebot 32MX7 settings per build environment using board_*** option, where *** is a JSON object path from board manifest cerebot32mx7.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Digilent Cerebot 32MX7 board.
Digilent OpenScope Contents • Digilent OpenScope
┌────────────────┬────────────────┐ │Microcontroller │ 32MZ2048EFG124 │ ├────────────────┼────────────────┤ │Frequency       │ 200MHz         │ ├────────────────┼────────────────┤ │Flash           │ 1.98MB         │ ├────────────────┼────────────────┤ │RAM             │ 512KB          │ ├────────────────┼────────────────┤ │Vendor          │ Digilent       │ └────────────────┴────────────────┘
Configuration Please use openscope ID for projectconf_env_board option in projectconf:
[env:openscope] platform = microchippic32 board = openscope
You can override default Digilent OpenScope settings per build environment using board_*** option, where *** is a JSON object path from board manifest openscope.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MZ2048EFG124
; change MCU frequency board_build.f_cpu = 200000000L
Debugging piodebug currently does not support Digilent OpenScope board.
Digilent chipKIT Cmod Contents • Digilent chipKIT Cmod
┌────────────────┬──────────────┐ │Microcontroller │ 32MX150F128D │ ├────────────────┼──────────────┤ │Frequency       │ 40MHz        │ ├────────────────┼──────────────┤ │Flash           │ 124KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ Digilent     │ └────────────────┴──────────────┘
Configuration Please use chipkit_cmod ID for projectconf_env_board option in projectconf:
[env:chipkit_cmod] platform = microchippic32 board = chipkit_cmod
You can override default Digilent chipKIT Cmod settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_cmod.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX150F128D
Debugging piodebug currently does not support Digilent chipKIT Cmod board.
Digilent chipKIT DP32 Contents • Digilent chipKIT DP32
┌────────────────┬──────────────┐ │Microcontroller │ 32MX250F128B │ ├────────────────┼──────────────┤ │Frequency       │ 40MHz        │ ├────────────────┼──────────────┤ │Flash           │ 120KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ Digilent     │ └────────────────┴──────────────┘
Configuration Please use chipkit_dp32 ID for projectconf_env_board option in projectconf:
[env:chipkit_dp32] platform = microchippic32 board = chipkit_dp32
You can override default Digilent chipKIT DP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_dp32.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX250F128B
Debugging piodebug currently does not support Digilent chipKIT DP32 board.
Digilent chipKIT MAX32 Contents • Digilent chipKIT MAX32
Configuration Please use mega_pic32 ID for projectconf_env_board option in projectconf:
[env:mega_pic32] platform = microchippic32 board = mega_pic32
You can override default Digilent chipKIT MAX32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mega_pic32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Digilent chipKIT MAX32 board.
Digilent chipKIT MX3 Contents • Digilent chipKIT MX3
┌────────────────┬──────────────┐ │Microcontroller │ 32MX320F128H │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 124KB        │ ├────────────────┼──────────────┤ │RAM             │ 16KB         │ ├────────────────┼──────────────┤ │Vendor          │ Digilent     │ └────────────────┴──────────────┘
Configuration Please use chipkit_mx3 ID for projectconf_env_board option in projectconf:
[env:chipkit_mx3] platform = microchippic32 board = chipkit_mx3
You can override default Digilent chipKIT MX3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_mx3.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX320F128H
Debugging piodebug currently does not support Digilent chipKIT MX3 board.
Digilent chipKIT Pro MX4 Contents • Digilent chipKIT Pro MX4
Configuration Please use chipkit_pro_mx4 ID for projectconf_env_board option in projectconf:
[env:chipkit_pro_mx4] platform = microchippic32 board = chipkit_pro_mx4
You can override default Digilent chipKIT Pro MX4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_pro_mx4.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Digilent chipKIT Pro MX4 board.
Digilent chipKIT Pro MX7 Contents • Digilent chipKIT Pro MX7
Configuration Please use chipkit_pro_mx7 ID for projectconf_env_board option in projectconf:
[env:chipkit_pro_mx7] platform = microchippic32 board = chipkit_pro_mx7
You can override default Digilent chipKIT Pro MX7 settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_pro_mx7.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Digilent chipKIT Pro MX7 board.
Digilent chipKIT UNO32 Contents • Digilent chipKIT UNO32
Configuration Please use uno_pic32 ID for projectconf_env_board option in projectconf:
[env:uno_pic32] platform = microchippic32 board = uno_pic32
You can override default Digilent chipKIT UNO32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest uno_pic32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Digilent chipKIT UNO32 board.
Digilent chipKIT WF32 Contents • Digilent chipKIT WF32
┌────────────────┬──────────────┐ │Microcontroller │ 32MX695F512L │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 128KB        │ ├────────────────┼──────────────┤ │Vendor          │ Digilent     │ └────────────────┴──────────────┘
Configuration Please use chipkit_wf32 ID for projectconf_env_board option in projectconf:
[env:chipkit_wf32] platform = microchippic32 board = chipkit_wf32
You can override default Digilent chipKIT WF32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_wf32.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX695F512L
Debugging piodebug currently does not support Digilent chipKIT WF32 board.
Digilent chipKIT WiFire Contents • Digilent chipKIT WiFire
┌────────────────┬────────────────┐ │Microcontroller │ 32MZ2048ECG100 │ ├────────────────┼────────────────┤ │Frequency       │ 200MHz         │ ├────────────────┼────────────────┤ │Flash           │ 1.98MB         │ ├────────────────┼────────────────┤ │RAM             │ 512KB          │ ├────────────────┼────────────────┤ │Vendor          │ Digilent       │ └────────────────┴────────────────┘
Configuration Please use chipkit_wifire ID for projectconf_env_board option in projectconf:
[env:chipkit_wifire] platform = microchippic32 board = chipkit_wifire
You can override default Digilent chipKIT WiFire settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_wifire.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MZ2048ECG100
Debugging piodebug currently does not support Digilent chipKIT WiFire board.
Digilent chipKIT uC32 Contents • Digilent chipKIT uC32
┌────────────────┬──────────────┐ │Microcontroller │ 32MX340F512H │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ Digilent     │ └────────────────┴──────────────┘
Configuration Please use chipkit_uc32 ID for projectconf_env_board option in projectconf:
[env:chipkit_uc32] platform = microchippic32 board = chipkit_uc32
You can override default Digilent chipKIT uC32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_uc32.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX340F512H
Debugging piodebug currently does not support Digilent chipKIT uC32 board.
Element14 chipKIT Pi Contents • Element14 chipKIT Pi
┌────────────────┬──────────────┐ │Microcontroller │ 32MX250F128B │ ├────────────────┼──────────────┤ │Frequency       │ 40MHz        │ ├────────────────┼──────────────┤ │Flash           │ 120KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ element14    │ └────────────────┴──────────────┘
Configuration Please use chipkit_pi ID for projectconf_env_board option in projectconf:
[env:chipkit_pi] platform = microchippic32 board = chipkit_pi
You can override default Element14 chipKIT Pi settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_pi.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Element14 chipKIT Pi board.
Fubarino Mini Contents • Fubarino Mini
┌────────────────┬──────────────┐ │Microcontroller │ 32MX250F128D │ ├────────────────┼──────────────┤ │Frequency       │ 48MHz        │ ├────────────────┼──────────────┤ │Flash           │ 120KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ Fubarino     │ └────────────────┴──────────────┘
Configuration Please use fubarino_mini ID for projectconf_env_board option in projectconf:
[env:fubarino_mini] platform = microchippic32 board = fubarino_mini
You can override default Fubarino Mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest fubarino_mini.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX250F128D
Debugging piodebug currently does not support Fubarino Mini board.
Fubarino SD (1.5) Contents • Fubarino SD (1.5)
┌────────────────┬──────────────┐ │Microcontroller │ 32MX795F512H │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 128KB        │ ├────────────────┼──────────────┤ │Vendor          │ Fubarino     │ └────────────────┴──────────────┘
Configuration Please use fubarino_sd ID for projectconf_env_board option in projectconf:
[env:fubarino_sd] platform = microchippic32 board = fubarino_sd
You can override default Fubarino SD (1.5) settings per build environment using board_*** option, where *** is a JSON object path from board manifest fubarino_sd.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX795F512H
Debugging piodebug currently does not support Fubarino SD (1.5) board.
HelvePic32 Contents • HelvePic32
┌────────────────┬──────────────┐ │Microcontroller │ 32MX250F128B │ ├────────────────┼──────────────┤ │Frequency       │ 48MHz        │ ├────────────────┼──────────────┤ │Flash           │ 120KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ BOXTEC       │ └────────────────┴──────────────┘
Configuration Please use helvepic32 ID for projectconf_env_board option in projectconf:
[env:helvepic32] platform = microchippic32 board = helvepic32
You can override default HelvePic32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest helvepic32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support HelvePic32 board.
Configuration Please use helvepic32_breadboardside ID for projectconf_env_board option in projectconf:
[env:helvepic32_breadboardside] platform = microchippic32 board = helvepic32_breadboardside
You can override default HelvePic32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest helvepic32_breadboardside.json. For example, board_build.mcu, board_build.f_cpu, etc.
┌────────────────┬──────────────┐ │Microcontroller │ 32MX250F128D │ ├────────────────┼──────────────┤ │Frequency       │ 48MHz        │ ├────────────────┼──────────────┤ │Flash           │ 120KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ BOXTEC       │ └────────────────┴──────────────┘
Configuration Please use helvepic32_smd ID for projectconf_env_board option in projectconf:
[env:helvepic32_smd] platform = microchippic32 board = helvepic32_smd
You can override default HelvePic32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest helvepic32_smd.json. For example, board_build.mcu, board_build.f_cpu, etc.
HelvePic32 MX270 Contents • HelvePic32 MX270
┌────────────────┬──────────────┐ │Microcontroller │ 32MX270F256B │ ├────────────────┼──────────────┤ │Frequency       │ 48MHz        │ ├────────────────┼──────────────┤ │Flash           │ 244KB        │ ├────────────────┼──────────────┤ │RAM             │ 62KB         │ ├────────────────┼──────────────┤ │Vendor          │ BOXTEC       │ └────────────────┴──────────────┘
Configuration Please use helvepic32_mx270 ID for projectconf_env_board option in projectconf:
[env:helvepic32_mx270] platform = microchippic32 board = helvepic32_mx270
You can override default HelvePic32 MX270 settings per build environment using board_*** option, where *** is a JSON object path from board manifest helvepic32_mx270.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX270F256B
Debugging piodebug currently does not support HelvePic32 MX270 board.
HelvePic32 Robot Contents • HelvePic32 Robot
┌────────────────┬──────────────┐ │Microcontroller │ 32MX270F256D │ ├────────────────┼──────────────┤ │Frequency       │ 48MHz        │ ├────────────────┼──────────────┤ │Flash           │ 244KB        │ ├────────────────┼──────────────┤ │RAM             │ 62KB         │ ├────────────────┼──────────────┤ │Vendor          │ BOXTEC       │ └────────────────┴──────────────┘
Configuration Please use helvepic32_robot ID for projectconf_env_board option in projectconf:
[env:helvepic32_robot] platform = microchippic32 board = helvepic32_robot
You can override default HelvePic32 Robot settings per build environment using board_*** option, where *** is a JSON object path from board manifest helvepic32_robot.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX270F256D
Debugging piodebug currently does not support HelvePic32 Robot board.
HelvePic32 SMD MX270 Contents • HelvePic32 SMD MX270
Configuration Please use helvepic32_smd_mx270 ID for projectconf_env_board option in projectconf:
[env:helvepic32_smd_mx270] platform = microchippic32 board = helvepic32_smd_mx270
You can override default HelvePic32 SMD MX270 settings per build environment using board_*** option, where *** is a JSON object path from board manifest helvepic32_smd_mx270.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support HelvePic32 SMD MX270 board.
MikroElektronika Clicker 2 Contents • MikroElektronika Clicker 2
┌────────────────┬──────────────────┐ │Microcontroller │ 32MX460F512L     │ ├────────────────┼──────────────────┤ │Frequency       │ 80MHz            │ ├────────────────┼──────────────────┤ │Flash           │ 508KB            │ ├────────────────┼──────────────────┤ │RAM             │ 32KB             │ ├────────────────┼──────────────────┤ │Vendor          │ MikroElektronika │ └────────────────┴──────────────────┘
Configuration Please use clicker2 ID for projectconf_env_board option in projectconf:
[env:clicker2] platform = microchippic32 board = clicker2
You can override default MikroElektronika Clicker 2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest clicker2.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support MikroElektronika Clicker 2 board.
MikroElektronika Flip N Click MZ Contents • MikroElektronika Flip N Click MZ