PLATFORMIO(1) PlatformIO PLATFORMIO(1)

platformio - PlatformIO Documentation

A place where Developers and Teams have true Freedom! No more hardware or software lock-ins!

  • Open source, maximum permissive Apache 2.0 license
  • Cross-platform IDE and Unified Debugger
  • Static Code Analyzer and Remote Unit Testing
  • Multi-platform and Multi-architecture Build System
  • Firmware File Explorer and Memory Inspection.

Social: Twitter | LinkedIn | Facebook | Bintray | Community

What is PlatformIO?

A place where Developers and Teams have true Freedom! No more hardware or software lock-ins!

  • Awards
  • Philosophy
  • Technologies
  • Problematic
  • How does it work?

PlatformIO is a cross-platform, cross-architecture, multiple framework, professional tool for embedded systems engineers and for software developers who write applications for embedded products.

PlatformIO was nominated for the year's best Software and Tools in the 2015/16 IoT Awards.

A native PlatformIO IDE extension for Microsoft VSCode editor is the most rated/reviewed extension with over 800 five-star reviews in the whole Microsoft Marketplace. It also was installed by over 750,000 unique developers around the world.

PlatformIO's unique philosophy in the embedded market provides developers with a modern integrated development environment (Cloud & Desktop IDE) that works cross-platform, supports many different software development kits (SDKs) or Frameworks, and includes sophisticated debugging (PIO Unified Debugger), unit testing (PIO Unit Testing), automated code analysis (PIO Check), and remote management (PIO Remote). It is architected to maximize flexibility and choice by developers, who can use either graphical or command line editors (PlatformIO Core (CLI)), or both.

PlatformIO is a must-have tool for professional embedded systems engineers who develop solutions on more than one specific platform. In addition, by having a decentralized architecture, PlatformIO offers both new and existing developers a quick integration path for developing commercial-ready products, and reduces the overall time-to-market.

And it runs on any one of your favorite modern operating systems (macOS, MS Windows, Linux, FreeBSD).

PlatformIO applies the latest scalable and flexible software technology to the embedded market – an area traditionally served by complex software tools that experienced hardware engineers have learned over time (often painfully so). Instead, with PlatformIO, users can be hobbyists or professionals. They can import the classic Arduino "Blink" sketch or develop a sophisticated low-level embedded C program for a commercial product. Example code for any supported framework can be compiled and uploaded to a target platform in minutes.

The build system structure automatically tags software dependencies and applies them using a modular hierarchy that takes away the usual complexity and pain. Developers no longer have to manually find and assemble an environment of toolchains, compilers, and library dependencies to develop applications for a specific target. With PlatformIO, clicking the compile button will bring in all necessary dependencies automatically. It's analogous to if you were a furniture designer, and your CAD program had a "build" button that caused a robot to fetch all the necessary pieces and fasteners and correctly assemble them.

PlatformIO Core (CLI) is a unique, developed-from-scratch build system that removes the usual pain of software integration, packaging, and library dependencies that developers encounter when they move beyond the bounds of a specific SDK or example embedded application. It can be used with a variety of code development environments and allows easy integration with numerous cloud platforms and web services feeds. The user experiences no barriers to getting started quickly: no license fees, no legal contracts. The user maintains full flexibility of the build environment because the tools are open source and permissively licensed (no permission needed to modify them, and no requirement to share changes.)

  • The main problem which repulses people from the embedded world is a complicated process to setup development software for a specific MCU/board: toolchains, proprietary vendor's IDE (which sometimes isn't free) and what is more, to get a computer with OS where that software is supported.
  • Multiple hardware platforms (MCUs, boards) require different toolchains, IDEs, etc, and, respectively, spending time on learning new development environments.
  • Finding proper libraries and code samples showing how to use popular sensors, actuators, etc.
  • Sharing embedded projects between team members, regardless of an operating system they prefer to work with.

Without going too deep into PlatformIO implementation details, work cycle of the project developed using PlatformIO is as follows:

  • Users choose board(s) interested in "platformio.ini" (Project Configuration File)
  • Based on this list of boards, PlatformIO downloads required toolchains and installs them automatically.
  • Users develop code and PlatformIO makes sure that it is compiled, prepared and uploaded to all the boards of interest.

PlatformIO IDE

PlatformIO IDE is the next-generation integrated development environment for IoT.

•
Cross-platform build system without external dependencies to the OS software:
  • 800+ Boards
  • 35+ Development Platforms
  • 20+ Frameworks



  • PIO Unified Debugger
  • PIO Remote
  • PIO Unit Testing
  • C/C++ Intelligent Code Completion
  • C/C++ Smart Code Linter for rapid professional development
  • Library Manager for the hundreds popular libraries
  • Multi-projects workflow with multiple panes
  • Themes support with dark and light colors
  • Serial Port Monitor
  • Built-in Terminal with PlatformIO Core (CLI) and CLI tool (pio, platformio)
  • Built-in PlatformIO Home.


----



We provide official packages (plugins, extensions) for the most popular IDEs and text editors.

NOTE:

In our experience, VSCode offers better system performance, and users have found it easier to get started


Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. It comes with built-in support for JavaScript, TypeScript and Node.js and has a rich ecosystem of extensions for other languages (such as C++, C#, Python, PHP, Go) and runtimes (such as .NET and Unity).

Install PlatformIO for VSCode / Get started .SS PlatformIO for CLion

The CLion is a cross-platform C/C++ IDE for Linux, OS X, and Windows. CLion includes such features as a smart editor, code generation, code quality assurance, automated refactorings, on-the-fly code analysis, project manager, integrated version control systems and debugger.

Install PlatformIO for CLion / Get started .SS PlatformIO Core (CLI)

PlatformIO Core (CLI tool) is a heart of whole PlatformIO ecosystem and consists of

  • Multi-platform Build System
  • Development platform and package managers
  • Library Manager
  • Library Dependency Finder (LDF)
  • Serial Port Monitor
  • Integration components (Cloud & Desktop IDE and Continuous Integration).

PlatformIO Core is written in Python and works on Windows, macOS, Linux, FreeBSD and ARM-based credit-card sized computers (Raspberry Pi, BeagleBone, CubieBoard, Samsung ARTIK, etc.).

PlatformIO Core provides a rich and documented Command Line Interface (CLI). The other PlatformIO-based software and IDEs are based on PlatformIO Core CLI, such as PlatformIO IDE. In other words, they wrap PlatformIO Core with own GUI.

NOTE:

Please note that you do not need to install PlatformIO Core if you are going to use PlatformIO IDE. PlatformIO Core is built into PlatformIO IDE and you will be able to use it within PlatformIO IDE Terminal.

If you need PlatformIO Core commands outside PlatformIO IDE, please Install Shell Commands.



•
"Blink Project"
•
Used in demo

•
Platform Manager
•
Used in demo

•
Library Manager
•
Used in demo

•
Over-the-Air update for ESP8266
•
Used in demo


[image]

Used in demo

1.
Source code of Wiring Blink Example
2.
platformio run command
3.
platformio run -t upload command.

[image]

Used in demo

1.
Platform Manager CLI
2.
platformio platform list command
3.
platformio platform search avr command
4.
platformio platform show teensy command
5.
platformio platform update command.

Library Manager

[image]

Used in demo

1.
Library Manager CLI
2.
platformio lib search 1-wire command
3.
platformio lib install 54 command
4.
platformio lib search -f mbed command
5.
platformio lib search -k rf command
6.
platformio lib search radiohead command
7.
platformio lib install 124 --version "1.40" command
8.
platformio lib show 124 command
9.
platformio lib update command.

Over-the-Air update for ESP8266

.SS Used in demo

1.
platformio run command
2.
platformio run -t upload command.

NOTE:

Please note that you do not need to install PlatformIO Core (CLI) if you are going to use PlatformIO IDE. PlatformIO Core (CLI) is built into PlatformIO IDE and you will be able to use it within PlatformIO IDE Terminal.

If you need PlatformIO Core (CLI) outside PlatformIO IDE, please Install Shell Commands.



PlatformIO Core is written in Python and works on Windows, macOS, Linux, FreeBSD and ARM-based credit-card sized computers (Raspberry Pi, BeagleBone, CubieBoard, Samsung ARTIK, etc.).

  • System requirements
  • Installation Methods
•
Installer Script
  • Super-Quick (Mac / Linux)
  • Local Download (Mac / Linux / Windows)

  • Python Package Manager
  • macOS Homebrew
  • Virtual Environment
  • Prerequisites
  • Creating


  • Development Version
  • Install Shell Commands
•
Unix and Unix-like
  • Method 1
  • Method 2

•
Windows

  • Uninstall PIO Core and dependent packages
  • Integration with custom applications (extensions, plugins)
•
Prerequisite
  • Python Interpreter
  • Installer Script

•
Workflow
  • Step 1. Where is PlatformIO Core installed?
  • Step 2. Install PlatformIO Core


•
Troubleshooting

Windows, macOS, Linux, FreeBSD, Linux ARMv6+
Python 3.5+ (Python 2.7 is not recommended, support for it will be removed in the next releases). See detailed instruction on how to Install Python Interpreter for Windows.
All commands below should be executed in Command-line application (Terminal). For macOS and Linux OS - Terminal application, for Windows OS – cmd.exe application.
Windows Users: Please check that you have correctly installed USB driver from board manufacturer

Linux Users:

  • Please install 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.


Please choose ONE of the following methods:

•
Installer Script
  • Super-Quick (Mac / Linux)
  • Local Download (Mac / Linux / Windows)

  • Python Package Manager
  • macOS Homebrew
  • Virtual Environment
  • Prerequisites
  • Creating


Installer Script

WARNING:

PlatformIO DOES NOT require administrative/sudo permissions. Please install using default user account WITHOUT EXTRA PERMISSIONS.


To install or upgrade PlatformIO Core paste that at a Terminal prompt:

python3 -c "$(curl -fsSL https://raw.githubusercontent.com/platformio/platformio/develop/scripts/get-platformio.py)"
# or using `curl`
curl -fsSL https://raw.githubusercontent.com/platformio/platformio-core-installer/master/get-platformio.py -o get-platformio.py
python3 get-platformio.py
# or using `wget`
wget https://raw.githubusercontent.com/platformio/platformio-core-installer/master/get-platformio.py -O get-platformio.py
python3 get-platformio.py


To install or upgrade PlatformIO Core, download (save as...) get-platformio.py script. Then run the following:

# change directory to folder where is located downloaded "get-platformio.py"
cd /path/to/dir/where/is/located/get-platformio.py/script
# run it
python get-platformio.py


On Windows OS it may look like:

# change directory to folder where is located downloaded "get-platformio.py"
cd C:\path\to\dir\where\is\located\script\get-platformio.py
# run it
python.exe get-platformio.py


NOTE:

If you need to have access to platformio or platformio.exe commands from other applications or terminal in your OS, please Install Shell Commands.


WARNING:

We recommend using this method ONLY FOR Continuous Integration use cases or where your have full permissions to install PlatformIO Core into the global scope of your OS.

For personal using, and avoiding maintenance and upgrade issues, we HIGHLY RECOMMEND using Installer Script which installs PlatformIO Core into an isolated virtual environment and does not affect your OS.



The latest stable version of PlatformIO Core may be installed or upgraded via Python Package Manager (pip) as follows:

pip install -U platformio


The latest stable version of PlatformIO may be installed or upgraded via macOS Homebrew Packages Manager (brew) as follows:

brew install platformio


PlatformIO Core may be installed into isolated Python environment. This method is very good if you don't want to install PlatformIO Core Python's dependencies (packages) into your global system scope. PlatformIO IDE uses this method to install PlatformIO Core.

Default and recommended environment folder is "core_dir/penv". You can print environment folder path using the next command in your system terminal:

python -c "import os; print(os.path.join(os.getenv('PLATFORMIO_CORE_DIR', os.path.join(os.path.expanduser('~'), '.platformio')), 'penv'))"
######################## Examples
# Windows
# C:\Users\UserName\.platformio\penv
# Linux
# ~/.platformio/penv
# /home/username/.platformio/penv
# macOS
# ~/.platformio/penv
# /Users/username/.platformio/penv


1.
Please remove existing PlatformIO Core environment folder if exists. See above command how to get path to environment folder.
2.
Please check that you have a valid Python interpreter running a next command in system terminal. Python 2.7.9+ or Python 3.5+ is recommended.

python --version
# or, for Unix (Linux, Mac), you can use `python2` or `python3` aliases
python2 --version
python3 --version


WARNING:

Windows Users: If you already tried to install PlatformIO IDE and did not get success, please open system's Control Panel > Installed Programs, and check if PlatformIO IDE tried to install an own isolated Python 2.7 version. Please uninstall it. Also is good to uninstall all Python interpreters from a system and install manually the latest Python using Install Python Interpreter guide.


3.
Make sure virtualenv --help command exists in a system, otherwise, please install it manually using pip install virtualenv or pip2 install virtualenv command.

If pip (Python Package Manager) does not exists, you have to install it manually. See https://pip.pypa.io/en/stable/installing/


1.
Create a folder which contains all the necessary executables to use the packages that PIO Core would need using virtualenv command:

virtualenv /path/to/.platformio/penv
# If you want to use a custom Python interpreter
virtualenv --python=/path/to/custom/python /path/to/.platformio/penv
# EXAMPLES
# Windows
virtualenv C:\Users\UserName\.platformio\penv
virtualenv --python=C:\Python27\python.exe  C:\Users\UserName\.platformio\penv
# Unix (Linux, Mac)
virtualenv ~/.platformio/penv
virtualenv -p python3 ~/.platformio/penv


2.
Activate virtual environment

# Windows
C:\Users\UserName\.platformio\penv\Scripts\activate
# Unix (Linux, Mac)
source /path/to/.platformio/penv/bin/activate
# or
. /path/to/.platformio/penv/bin/activate


3.
Install PIO Core into virtual environment

pip install -U platformio



If you plan to use PIO Core commands outside virtual environment, please Install Shell Commands.

WARNING:

If you use PlatformIO IDE, please enable development version:
  • PlatformIO IDE for Atom: "Menu PlatformIO: Settings > PlatformIO IDE > Use development version of PlatformIO Core"
  • VSCode: Set platformio-ide.useDevelopmentPIOCore to true in Settings.



Install the latest PlatformIO from the develop branch:

# uninstall existing version
pip uninstall platformio
# install the latest development version of PlatformIO
pip install -U https://github.com/platformio/platformio-core/archive/develop.zip


If you want to be up-to-date with the latest develop version of PlatformIO, then you need to re-install PlatformIO each time you see a new commits in PlatformIO GitHub repository (branch: develop) like so:

pip install -U https://github.com/platformio/platformio-core/archive/develop.zip


Or:

pio upgrade --dev


To revert to the latest stable version:

pip uninstall platformio
pip install -U platformio


Install Shell Commands

PlatformIO Core (CLI) consists of 2 standalone tools in a system:

  • platformio or pio (short alias) - CLI Guide
  • piodebuggdb - alias of platformio debug

If you have PlatformIO IDE already installed, you do not need to install PlatformIO Core (CLI) separately. Just link these tools with your shell:

•
Unix and Unix-like
  • Method 1
  • Method 2

•
Windows

In Unix and Unix-like systems, there are multiple ways to achieve this.

You can export PlatformIO executables' directory to the PATH environmental variable. This method will allow you to execute platformio commands from any terminal emulator as long as you're logged in as the user PlatformIO is installed and configured for.

If you use Bash as your default shell, you can do it by editing either ~/.profile or ~/.bash_profile and adding the following line:

export PATH=$PATH:~/.platformio/penv/bin


If you use Zsh, you can either edit ~/.zprofile and add the code above, or for supporting both, Bash and Zsh, you can first edit ~/.profile and add the code above, then edit ~/.zprofile and add the following line:

emulate sh -c '. ~/.profile'


After everything's done, just restart your session (log out and log back in) and you're good to go.

If you don't know the difference between the two, check out this page.

You can create system-wide symlinks. This method is not recommended if you have multiple users on your computer because the symlinks will be broken for other users and they will get errors while executing PlatformIO commands. If that's not a problem, open your system terminal app and paste these commands (MAY require administrator access sudo):

ln -s ~/.platformio/penv/bin/platformio /usr/local/bin/platformio
ln -s ~/.platformio/penv/bin/pio /usr/local/bin/pio
ln -s ~/.platformio/penv/bin/piodebuggdb /usr/local/bin/piodebuggdb


After that, you should be able to run PlatformIO from terminal. No restart is required.

Please read one of these instructions How do I set or change the PATH system variable?

You need to edit system environment variable called Path and append C:\Users\UserName\.platformio\penv\Scripts; path in the beginning of a list (please replace UserName with your account name).

•
Uninstall PIO Core tool

# uninstall standalone PIO Core installed via `pip`
pip uninstall platformio
# uninstall Homebrew's PIO Core (only macOS users if you installed it via Homebrew before)
brew uninstall platformio




•
Dependent packages, global libraries are installed to core_dir folder (in user's HOME directory). Just remove it.

We recommend using PlatformIO Core Installer Script when you integrate PlatformIO Core into an application, such as extension or plugin for IDE. Examples that use this installer are:

•
platformio-node-helpers, is used by PlatformIO IDE for VSCode and PlatformIO IDE for Atom

PlatformIO Core Installer Script is written in Python and is compatible with Python 2.7+ and Python 3.5+. We highly recommend using Python 3.

Python is installed by default on the most popular Unix OS (macOS, Linux, FreeBSD). If there is no Python on a user machine (you can check running python --version), we have 2 options:

1.
Ask the user to install Python 3 using our guide Install Python Interpreter
2.
You can automatically Download Portable Python 3 and unpack it in a cache folder of your application. Later, you can use unpacked_protable_python_dir/python.exe for the installer script.

Installer Script

There are 2 options on how to work with PlatformIO Core Installer Script:

1.
Bundle get-platformio.py file into your application
2.
Download get-platformio.py file on demand.

In both cases, you will need to have get-platformio.py script on the end-user machine. You can copy or download it to a cache/temporary folder.

A list of arguments and options for the installer script is available via

python get-platformio.py --help


We will describe a simple workflow on how to automatically install PlatformIO Core (CLI) for end-user of your application/extension. We assume that get-platformio.py script is already copied/downloaded and exists on the end-user machine. See above how to get it.

You should check the PlatformIO Core installation state each time when the user starts your application. You need to call the Installer Script with check core arguments:

python get-platformio.py check core


This command returns 0 "exit code" when PlatformIO Core is already installed and is ready for use, otherwise, the non-zero code of subprocess will be returned and you need to install PlatformIO Core (see Step #2 below).

If you need to have full information about PlatformIO Core installation state, please run with --dump-state option and specify a folder or a full path where to save data in JSON format:

get-platformio.py check core --dump-state tmpdir/pioinstaller-state.json


Now, read JSON file and use platformio_exe binary to call PlatforIO Core using CLI (see CLI Guide). You can also export penv_bin_dir into system environment PATH variable and platformio command will be available without a full path.

Example of pioinstaller-state.json run on macOS:

{
  "cache_dir": "/Users/Freedom/.platformio/.cache",
  "core_dir": "/Users/Freedom/.platformio",
  "core_version": "4.3.1",
  "installer_version": "0.2.0",
  "is_develop_core": false,
  "penv_bin_dir": "/Users/Freedom/.platformio/penv/bin",
  "penv_dir": "/Users/Freedom/.platformio/penv",
  "platformio_exe": "/Users/Freedom/.platformio/penv/bin/platformio",
  "python_exe": "/Users/Freedom/.platformio/penv/bin/python",
  "system": "darwin_x86_64"
}


To install PlatformIO Core into the virtual environment in an automatic mode, please call installer script without any arguments:

python get-platformio.py


Available options:

  • --verbose, verbose output
  • --dev, install the latest development version of PlatformIO Core
  • --ignore-python, a path to Python to be ignored (multiple options and unix wildcards are allowed)

More options are available at python get-platformio.py --help.

Installer Script will return exit code 0 on success, otherwise non-zero code and error explanation.

Next time just use again python get-platformio.py check core as described in Step #1 (see above).

NOTE:

Linux OS: Don't forget to install "udev" rules file 99-platformio-udev.rules (an instruction is located in the file).

Windows OS: Please check that you have correctly installed USB driver from board manufacturer



For further details, frequently questions, known issues, please refer to Frequently Asked Questions.

If you find any issues with PlatformIO Core Installer Script, please report to https://github.com/platformio/platformio-core-installer/issues

Quick Start

This tutorial introduces you to the basics of PlatformIO Core (CLI) Command Line Interface (CLI) workflow and shows you a creation process of a simple cross-platform “Blink” Project. After finishing you will have a general understanding of how to work with the multiple development platforms and embedded boards.

Setting Up the Project

PlatformIO Core (CLI) provides special platformio project init command for configuring your projects. It allows one to initialize new empty project or update existing with the new data.

What is more, platformio project init can be used for Cloud & Desktop IDE. It means that you will be able to import pre-generated PlatformIO project using favorite IDE and extend it with the professional instruments for IoT development.

This tutorial is based on the next popular embedded boards and development platforms using Arduino:

Platform Board Framework
Atmel AVR Arduino Uno Arduino
Espressif 8266 NodeMCU 1.0 (ESP-12E Module) Arduino
Teensy Teensy 3.1 / 3.2 Arduino

platformio project init command requires to specify board identifier ID. It can be found using Boards catalog, Boards Explorer or platformio boards command. For example, using platformio boards let's try to find Teensy boards:

> platformio boards teensy
Platform: teensy
---------------------------------------------------------------------------
ID                    MCU            Frequency  Flash   RAM    Name
---------------------------------------------------------------------------
teensy20              atmega32u4     16MHz     31K    2.5K  Teensy 2.0
teensy30              mk20dx128      48MHz     128K   16K   Teensy 3.0
teensy31              mk20dx256      72MHz     256K   64K   Teensy 3.1 / 3.2
teensylc              mkl26z64       48MHz     62K    8K    Teensy LC
teensy20pp            at90usb1286    16MHz     127K   8K    Teensy++ 2.0


According to the table above the ID for Teensy 3.1 / 3.2 is teensy31. Also, the ID for Arduino Uno is uno and for NodeMCU 1.0 (ESP-12E Module) is nodemcuv2.

PlatformIO ecosystem contains big database with pre-configured settings for the most popular embedded boards. It helps you to forget about installing toolchains, writing build scripts or configuring uploading process. Just tell PlatformIO the Board ID and you will receive full working project with pre-installed instruments for the professional development.

1.
Create empty folder where you are going to initialize new PlatformIO project. Then open system Terminal and change directory to it:

# create new directory
> mkdir path_to_the_new_directory
# go to it
> cd path_to_the_new_directory


2.
Initialize project for the boards mentioned above (you can specify more than one board at time):

> platformio project init --board uno --board nodemcuv2 --board teensy31
The current working directory *** will be used for the new project.
You can specify another project directory via
`platformio project init -d %PATH_TO_THE_PROJECT_DIR%` command.
The next files/directories will be created in ***
platformio.ini - Project Configuration File. |-> PLEASE EDIT ME <-|
src - Put your source files here
lib - Put here project specific (private) libraries
Do you want to continue? [y/N]: y
Project has been successfully initialized!
Useful commands:
`platformio run` - process/build project from the current directory
`platformio run --target upload` or `platformio run -t upload` - upload firmware to embedded board
`platformio run --target clean` - clean project (remove compiled files)



Congrats! You have just created the first PlatformIO based Project with the next structure:

  • "platformio.ini" (Project Configuration File)
  • src directory where you should place source code (*.h, *.c, *.cpp, *.S, *.ino, etc.)
  • lib directory can be used for the project specific (private) libraries. More details are located in lib/README file.
  • Miscellaneous files for VCS and Continuous Integration support.

NOTE:

If you need to add new board to the existing project please use platformio project init again.


The result of just generated platformio.ini:

; PlatformIO Project Configuration File
;
;   Build options: build flags, source filter, extra scripting
;   Upload options: custom port, speed and extra flags
;   Library options: dependencies, extra library storages
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
[env:uno]
platform = atmelavr
framework = arduino
board = uno
[env:nodemcuv2]
platform = espressif8266
framework = arduino
board = nodemcuv2
[env:teensy31]
platform = teensy
framework = arduino
board = teensy31


Now, we need to create main.cpp file and place it to src folder of our newly created project. The contents of src/main.cpp:

/**
 * Blink
 *
 * Turns on an LED on for one second,
 * then off for one second, repeatedly.
 */
#include "Arduino.h"
#ifndef LED_BUILTIN
#define LED_BUILTIN 13
#endif
void setup()
{
  // initialize LED digital pin as an output.
  pinMode(LED_BUILTIN, OUTPUT);
}
void loop()
{
  // turn the LED on (HIGH is the voltage level)
  digitalWrite(LED_BUILTIN, HIGH);
  // wait for a second
  delay(1000);
  // turn the LED off by making the voltage LOW
  digitalWrite(LED_BUILTIN, LOW);
   // wait for a second
  delay(1000);
}


The final Project structure:

project_dir
├── lib
│   └── README
├── platformio.ini
└── src
    └── main.cpp


Process Project

PlatformIO Core (CLI) provides special platformio run command to process project. If you call it without any arguments, PlatformIO Build System will process all project environments (which were created per each board specified above). Here are a few useful commands:

  • platformio run. Process (build) all environments specified in "platformio.ini" (Project Configuration File)
  • platformio run --target upload. Build project and upload firmware to the all devices specified in "platformio.ini" (Project Configuration File)
  • platformio run --target clean. Clean project (delete compiled objects)
  • platformio run -e uno. Process only uno environment
  • platformio run -e uno -t upload. Build project only for uno and upload firmware.

Please follow to platformio run --target documentation for the other targets.

Finally, demo which demonstrates building project and uploading firmware to Arduino Uno: [image]

  • Project examples
  • CLI Guide for PlatformIO Core (CLI) commands

CLI Guide

•
CLI Guide
  • Usage
  • Options
  • Commands


pio [OPTIONS] COMMAND
platformio [OPTIONS] COMMAND
# "pio" is the alias of "platformio" command



Do not print ANSI control characters.

See also PLATFORMIO_NO_ANSI and PLATFORMIO_FORCE_ANSI environment variables.


Show the version of PlatformIO


Show help for the available options and commands

$ platformio --help
$ platformio COMMAND --help


CLI helper command for PIO Account.

To print all available commands and options use:

pio account --help
platformio account --help
platformio account COMMAND --help


•
platformio account forgot
  • Usage
  • Description
•
Options



platformio account forgot [OPTIONS]
pio account forgot [OPTIONS]


Allows you to reset password for PIO Account using username or email which were specified for registration.


Username or email. You can omit this option and enter username or email in Forgot Wizard later.

•
platformio account login
  • Usage
  • Description
•
Options



platformio account login [OPTIONS]
pio account login [OPTIONS]


Log in to PIO Account. If you are not able to provide authentication credentials manually you can use PLATFORMIO_AUTH_TOKEN. This is very useful for Continuous Integration systems and PIO Remote operations.


Username or email. You can omit this option and enter username or email in Login Wizard later.


You can omit this option and enter securely password in Login Wizard later.

•
platformio account logout
  • Usage
  • Description


platformio account logout
pio account logout


Log out of PIO Account.

•
platformio account password
  • Usage
  • Description


platformio account password
pio account password


Change password for PIO Account.

•
platformio account register
  • Usage
  • Description
•
Options



platformio account register [OPTIONS]
pio account register [OPTIONS]


Create a new PIO Account.

You can omit these options and enter them later in Register Wizard.


A username. You can use it later for platformio account login, platformio account update, and platformio account forgot commands.

The username must contain at least 4 characters including single hyphens, and cannot begin or end with a hyphen.


An email. Please enter existing email, you will receive a confirmation letter.


A password. You will need it for platformio account login, platformio account password, platformio account token, and platformio account update commands.


A first name.


A last name.

•
platformio account show
  • Usage
  • Description
•
Options



platformio account show
pio account show


Show detailed information about PIO Account:

  • Active subscriptions
  • Available packages and services


Return the output in JSON format

•
platformio account token
  • Usage
  • Description
•
Options



platformio account token
pio account token


Get or regenerate Personal Authentication Token. It is very useful for Continuous Integration systems, PIO Remote operations where you are not able to authorize manually.

PlatformIO handles Personal Authentication Token from environment variable PLATFORMIO_AUTH_TOKEN.

If this option is specified a new authentication token will be generated.


Return the output in JSON format

•
platformio account update
  • Usage
  • Description
•
Options



platformio account update [OPTIONS]
pio account update [OPTIONS]


Update PIO Account profile.

You can omit these options and enter them later in update Wizard.


A username that must contain at least 4 characters including single hyphens, and cannot begin or end with a hyphen.


An email. Please enter existing email, you will receive a confirmation letter.


A first name.


A last name.


A current password to confirm this operation.

•
platformio boards
  • Usage
  • Description
•
Options

•
Examples


platformio boards [OPTIONS] [FILTER]
pio boards [OPTIONS] [FILTER]


List pre-configured Embedded Boards


List boards only from the installed platforms


Return the output in JSON format

1.
Show all available pre-configured embedded boards

$ platformio boards
Platform: atmelavr
---------------------------------------------------------------------------
ID                    MCU           Frequency  Flash   RAM    Name
---------------------------------------------------------------------------
btatmega168           atmega168     16MHz     14K    1K    Arduino BT ATmega168
btatmega328           atmega328p    16MHz     28K    2K    Arduino BT ATmega328
diecimilaatmega168    atmega168     16MHz     14K    1K    Arduino Duemilanove or Diecimila ATmega168
diecimilaatmega328    atmega328p    16MHz     30K    2K    Arduino Duemilanove or Diecimila ATmega328
esplora               atmega32u4    16MHz     28K    2K    Arduino Esplora
ethernet              atmega328p    16MHz     31K    2K    Arduino Ethernet
...


2.
Filter Arduino-based boards

$ platformio boards arduino
Platform: atmelavr
---------------------------------------------------------------------------
ID                    MCU           Frequency  Flash   RAM    Name
---------------------------------------------------------------------------
btatmega168           atmega168     16MHz     14K    1K    Arduino BT ATmega168
btatmega328           atmega328p    16MHz     28K    2K    Arduino BT ATmega328
diecimilaatmega168    atmega168     16MHz     14K    1K    Arduino Duemilanove or Diecimila ATmega168
diecimilaatmega328    atmega328p    16MHz     30K    2K    Arduino Duemilanove or Diecimila ATmega328
esplora               atmega32u4    16MHz     28K    2K    Arduino Esplora
ethernet              atmega328p    16MHz     31K    2K    Arduino Ethernet
...


3.
Filter mbed-enabled boards

$ platformio boards mbed
Platform: freescalekinetis
---------------------------------------------------------------------------
ID                    MCU            Frequency  Flash   RAM    Name
---------------------------------------------------------------------------
frdm_k20d50m          mk20dx128vlh5  48MHz     128K   16K   Freescale Kinetis FRDM-K20D50M
frdm_k22f             mk22fn512vlh12 120MHz    512K   128K  Freescale Kinetis FRDM-K22F
...
Platform: nordicnrf51
---------------------------------------------------------------------------
ID                    MCU            Frequency  Flash   RAM    Name
---------------------------------------------------------------------------
wallBotBLE            nrf51822       16MHz     128K   16K   JKSoft Wallbot BLE
nrf51_dk              nrf51822       32MHz     256K   32K   Nordic nRF51-DK
...
Platform: nxplpc
---------------------------------------------------------------------------
ID                    MCU            Frequency  Flash   RAM    Name
---------------------------------------------------------------------------
blueboard_lpc11u24    lpc11u24       48MHz     32K    8K    BlueBoard-LPC11U24
dipcortexm0           lpc11u24       50MHz     32K    8K    DipCortex M0
lpc11u35              lpc11u35       48MHz     64K    10K   EA LPC11U35 QuickStart Board
...
Platform: ststm32
---------------------------------------------------------------------------
ID                    MCU            Frequency  Flash   RAM    Name
---------------------------------------------------------------------------
disco_f401vc          stm32f401vct6  84MHz     256K   64K   32F401CDISCOVERY
nucleo_f030r8         stm32f030r8t6  48MHz     64K    8K    ST Nucleo F030R8
...


4.
Filter boards which are based on ATmega168 MCU

$ platformio boards atmega168
Platform: atmelavr
---------------------------------------------------------------------------
ID                    MCU           Frequency  Flash   RAM    Name
---------------------------------------------------------------------------
btatmega168           atmega168     16MHz     14K    1K    Arduino BT ATmega168
diecimilaatmega168    atmega168     16MHz     14K    1K    Arduino Duemilanove or Diecimila ATmega168
miniatmega168         atmega168     16MHz     14K    1K    Arduino Mini ATmega168
atmegangatmega168     atmega168     16MHz     14K    1K    Arduino NG or older ATmega168
nanoatmega168         atmega168     16MHz     14K    1K    Arduino Nano ATmega168
pro8MHzatmega168      atmega168     8MHz      14K    1K    Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz)
pro16MHzatmega168     atmega168     16MHz     14K    1K    Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz)
lilypadatmega168      atmega168     8MHz      14K    1K    LilyPad Arduino ATmega168
168pa16m              atmega168p    16MHz     15K    1K    Microduino Core (Atmega168PA@16M,5V)
168pa8m               atmega168p    8MHz      15K    1K    Microduino Core (Atmega168PA@8M,3.3V)


5.
Show boards by TI MSP430

$ platformio boards timsp430
Platform: timsp430
---------------------------------------------------------------------------
ID                    MCU           Frequency  Flash   RAM    Name
---------------------------------------------------------------------------
lpmsp430fr5739        msp430fr5739  16MHz     15K    1K    FraunchPad w/ msp430fr5739
lpmsp430f5529         msp430f5529   16MHz     128K   1K    LaunchPad w/ msp430f5529 (16MHz)
lpmsp430f5529_25      msp430f5529   25MHz     128K   1K    LaunchPad w/ msp430f5529 (25MHz)
lpmsp430fr5969        msp430fr5969  8MHz      64K    1K    LaunchPad w/ msp430fr5969
lpmsp430g2231         msp430g2231   1MHz      2K     128B   LaunchPad w/ msp430g2231 (1MHz)
lpmsp430g2452         msp430g2452   16MHz     8K     256B   LaunchPad w/ msp430g2452 (16MHz)
lpmsp430g2553         msp430g2553   16MHz     16K    512B   LaunchPad w/ msp430g2553 (16MHz)


Helper command for PIO Check.

•
platformio check
  • Usage
  • Description
  • Options
  • Examples


platformio check [OPTIONS]
pio check [OPTIONS]


Perform static analysis check on PlatformIO based project. By default Cppcheck analysis tool is used.

More details about PlatformIO PIO Check.


Process specified environments.


You can specify which source files or folders should be included/excluded from check process. By default only src_dir and include_dir are checked. Multiple --pattern options and GLOB Patterns are allowed.

Example: platformio check --pattern="tests" --pattern="src/*.cpp"


Specify additional flags that need to be passed to the analysis tool. If multiple tools set in check_tool option, the flags are passed to all of them. Individual flags for each tool can be added using a special suffix with the tool name.

Flag Meaning
--addon=<addon> Execute addon. i.e. cert.
-D<ID> Define preprocessor symbol.

Multiple --flags options are allowed.

Example: platformio check --flags "-DDEBUG cppcheck: --std=c++11 --platform=avr8"


Specify the Defect severity types which will be reported by the Check tools. Possible values described in Defect severity section. Multiple --severity options are allowed.

Example: platformio check --severity=high


Specify the path to project directory. By default, --project-dir is equal to the current working directory (CWD).


Process project with a custom "platformio.ini" (Project Configuration File).


Return the output in JSON format.


Fail (exit with non-zero code) if there is a defect found with specified severity. By default exit code is the same as the exit code returned by a tool selected for performing check. Possible values described in Defect severity section. Multiple --fail-on-defect options are allowed.

Example: platformio check --fail-on-defect=low --fail-on-defect=medium


Suppress progress reporting and show only defects with high severity. See Defect severity.


Show detailed information when processing environments.

This option can also be set globally using force_verbose setting or by environment variable PLATFORMIO_SETTING_FORCE_VERBOSE.

For the examples please follow to PIO Check page.

•
platformio ci
  • Usage
  • Description
  • Options
  • Examples


platformio ci [OPTIONS] [SRC]
pio ci [OPTIONS] [SRC]


platformio ci command is conceived of as "hot key" for building project with arbitrary source code structure. In a nutshell, using SRC and platformio ci --lib contents PlatformIO initializes via platformio project init new project in platformio ci --build-dir with the build environments (using platformio ci --board or platformio ci --project-conf) and processes them via platformio run command.

platformio ci command accepts multiple SRC arguments, platformio ci --lib and platformio ci --exclude options which can be a path to directory, file or Glob Pattern. Also, you can omit SRC argument and set path (multiple paths are allowed denoting with :) to PLATFORMIO_CI_SRC Environment variable

For more details as for integration with the popular Continuous Integration Systems please follow to Continuous Integration page.

NOTE:

platformio ci command is useful for library developers. It allows one to build different examples without creating own project per them. Also, is possible to upload firmware to the target device. In this case, you need to pass additional option --project-option="targets=upload". What is more, you can specify custom upload port using --project-option="upload_port=<port>" option. See platformio ci --project-option for details.



Source code which will be copied to <BUILD_DIR>/lib directly.

If platformio ci --lib is a path to file (not to directory), then PlatformIO will create temporary directory within <BUILD_DIR>/lib and copy the rest files into it.


Exclude directories and/-or files from platformio ci --build-dir. The path must be relative to PlatformIO project within platformio ci --build-dir.

For example, exclude from project src directory:

  • examples folder
  • *.h files from foo folder

platformio ci --exclude=src/examples --exclude=src/foo/*.h [SRC]



Build project with automatically pre-generated environments based on board settings.

For more details please look into platformio project init --board.


Path to directory where PlatformIO will initialise new project. By default it's temporary directory within your operating system.

NOTE:

This directory will be removed at the end of build process. If you want to keep it, please use platformio ci --keep-build-dir.



Don't remove platformio ci --build-dir after build process.


Build project using pre-configured "platformio.ini" (Project Configuration File).


Pass additional options from "platformio.ini" (Project Configuration File) to platformio project init command. For example, automatically install dependent libraries platformio ci --project-option="lib_deps=ArduinoJSON" or ignore specific library platformio ci --project-option="lib_ignore=SomeLib".

NOTE:

Use multiple --project-option to pass multiple options to "platformio.ini" (Project Configuration File). One option per one argument. For example, platformio ci --project-option="build_unflags = -std=gnu++11" --project-option="build_flags = -std=c++14"



Shows detailed information when processing environments.

This option can also be set globally using force_verbose setting or by environment variable PLATFORMIO_SETTING_FORCE_VERBOSE.

For the others examples please follow to Continuous Integration page.

Helper command for PIO Unified Debugger.

•
platformio debug
  • Usage
  • Description
  • Options
  • Examples


platformio debug [OPTIONS]
pio debug [OPTIONS]
# A binary shortcut for "platformio debug --interface=gdb" command
piodebuggdb [GDB OPTIONS]


Prepare PlatformIO project for debugging or launch debug server.


Debug specified environments.

You can also specify which environments should be used for debugging by default using default_envs option from "platformio.ini" (Project Configuration File).


Specify the path to a project directory. By default, --project-dir is equal to a current working directory (CWD).


New in version 4.0.

Process project with a custom "platformio.ini" (Project Configuration File).


PIO Debugging Interface. Valid values:

•
gdb - GDB: The GNU Project Debugger


Shows detailed information when processing environments.

This option can also be set globally using force_verbose setting or by environment variable PLATFORMIO_SETTING_FORCE_VERBOSE.

1.
Prepare a project for debugging

> platformio debug
[Sun Apr 30 01:34:01 2017] Processing mzeropro (platform: atmelsam; debug_extra_cmds: b main.cpp:26; board: mzeropro; framework: arduino)
-----------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
Collected 26 compatible libraries
Looking for dependencies...
Project does not have dependencies
Compiling .pio/build/mzeropro/src/main.o
Compiling .pio/build/mzeropro/FrameworkArduinoVariant/variant.o
Compiling .pio/build/mzeropro/FrameworkArduino/IPAddress.o
Compiling .pio/build/mzeropro/FrameworkArduino/Print.o
Archiving .pio/build/mzeropro/libFrameworkArduinoVariant.a
Indexing .pio/build/mzeropro/libFrameworkArduinoVariant.a
...
Compiling .pio/build/mzeropro/FrameworkArduino/wiring_analog.o
Compiling .pio/build/mzeropro/FrameworkArduino/wiring_digital.o
Compiling .pio/build/mzeropro/FrameworkArduino/wiring_private.o
Compiling .pio/build/mzeropro/FrameworkArduino/wiring_shift.o
Archiving .pio/build/mzeropro/libFrameworkArduino.a
Indexing .pio/build/mzeropro/libFrameworkArduino.a
Linking .pio/build/mzeropro/firmware.elf
Calculating size .pio/build/mzeropro/firmware.elf
Building .pio/build/mzeropro/firmware.bin
text       data     bss     dec     hex filename
11512       256    1788   13556    34f4 .pio/build/mzeropro/firmware.elf
=========================== [SUCCESS] Took 7.82 seconds ===========================


2.
Launch GDB instance and load initial configuration per a project

> platformio debug --interface=gdb -x .pioinit
...
Loading section .text, size 0x2c98 lma 0x4000
Loading section .ramfunc, size 0x60 lma 0x6c98
Loading section .data, size 0x100 lma 0x6cf8
Start address 0x47b0, load size 11768
Transfer rate: 4 KB/sec, 3922 bytes/write.
target halted due to debug-request, current mode: Thread
xPSR: 0x81000000 pc: 0x000028f4 msp: 0x20002c00
target halted due to debug-request, current mode: Thread
xPSR: 0x81000000 pc: 0x000028f4 msp: 0x20002c00
Breakpoint 2 at 0x413a: file src/main.cpp, line 26.


To print all available commands and options use:

pio device --help
platformio device --help
platformio device COMMAND --help


•
platformio device list
  • Usage
  • Description
  • Options
  • Examples


platformio device list [OPTIONS]
pio device list [OPTIONS]


List available devices. Default is set to --serial and all available Serial Ports will be shown.


List available Serial Ports, default.


List available logical devices.


List multicast DNS services.


Return the output in JSON format.

1.
Unix OS

$ platformio device list
/dev/cu.SLAB_USBtoUART
----------
Hardware ID: USB VID:PID=10c4:ea60 SNR=0001
Description: CP2102 USB to UART Bridge Controller
/dev/cu.uart-1CFF4676258F4543
----------
Hardware ID: USB VID:PID=451:f432 SNR=1CFF4676258F4543
Description: Texas Instruments MSP-FET430UIF


2.
Windows OS

$ platformio device list
COM4
----------
Hardware ID: USB VID:PID=0451:F432
Description: MSP430 Application UART (COM4)
COM3
----------
Hardware ID: USB VID:PID=10C4:EA60 SNR=0001
Description: Silicon Labs CP210x USB to UART Bridge (COM3)


3.
List multicast DNS services and logical devices

$ platformio device list --mdns --logical
Multicast DNS Services
======================
PlatformIO._bttremote._tcp.local.
------------------------------
Type: _bttremote._tcp.local.
IP: ...
Port: 62941
Properties: ...
Time for PlatformIO._adisk._tcp.local.
---------------------------------
Type: _adisk._tcp.local.
IP: 192.168.0.1
Port: 9
Properties: ...
PlatformIO._ssh._tcp.local.
------------------------
Type: _ssh._tcp.local.
IP: ...
Port: 22
PlatformIO._sftp-ssh._tcp.local.
-----------------------------
Type: _sftp-ssh._tcp.local.
IP: ...
Port: 22
Logical Devices
===============
/
-
Name:
/Volumes/PIO
-------------
Name: PIO
/Volumes/PLUS
--------------
Name: PLUS


•
platformio device monitor
  • Usage
  • Description
  • Options
  • Filters
  • Capture output to a file
  • Device Monitor Filter API
  • Examples


platformio device monitor [OPTIONS]


This is a console application that provides a small terminal application. It is based on Miniterm and itself does not implement any terminal features such as VT102 compatibility. However it inherits these features from the terminal it is run. For example on GNU/Linux running from an xterm it will support the escape sequences of the xterm. On Windows the typical console window is dumb and does not support any escapes. When ANSI.sys is loaded it supports some escapes.

Miniterm supports RFC 2217 remote serial ports and raw sockets using URL Handlers such as rfc2217://<host>:<port> respectively socket://<host>:<port> as port argument when invoking.

To control monitor please use these "hot keys":

  • Ctrl+C Quit
  • Ctrl+T Menu
  • Ctrl+T followed by Ctrl+H Help


Port, a number or a device name, or valid URL Handlers.

Can be customized in "platformio.ini" (Project Configuration File) using monitor_port option.

URL Handlers

  • rfc2217://<host>:<port>[?<option>[&<option>...]]
  • socket://<host>:<port>[?logging={debug|info|warning|error}]
  • loop://[?logging={debug|info|warning|error}]
  • hwgrep://<regexp>[&skip_busy][&n=N]
  • spy://port[?option[=value][&option[=value]]]
  • alt://port?class=<classname>


Set baud rate, default 9600.

Can be customized in "platformio.ini" (Project Configuration File) using monitor_speed option.


Set parity (None, Even, Odd, Space, Mark), one of [N, E, O, S, M], default N


Enable RTS/CTS flow control, default Off


Enable software flow control, default Off


Set initial RTS line state (0 or 1).

Can be customized in "platformio.ini" (Project Configuration File) using monitor_rts option.


Set initial DTR line state (0 or 1).

Can be customized in "platformio.ini" (Project Configuration File) using monitor_dtr option.


Enable local echo, default Off


Set the encoding for the serial port (e.g. hexlify, Latin1, UTF-8), default UTF-8.


Add text transformation. See available filters at Filters.


End of line mode (CR, LF or CRLF), default CRLF

NEW: Available in Miniterm/PySerial 3.0


Do not apply any encodings/transformations


ASCII code of special character that is used to exit the application, default 3 (DEC, Ctrl+C).

For example, to use Ctrl+] run platformio device monitor --exit-char 29.


ASCII code of special character that is used to control miniterm (menu), default 20 (DEC)


Diagnostics: suppress non-error messages, default Off


Specify the path to project directory. By default, --project-dir is equal to current working directory (CWD).


Process specified environments.

You can also specify which environments should be processed by default using default_envs option from "platformio.ini" (Project Configuration File).

New in version 4.3.

A list of filters that can be applied for monitor output using platformio device monitor --filter or "platformio.ini" (Project Configuration File) and monitor_filters options. option.

Name Description
default Remove typical terminal control codes from input
colorize Apply different colors for received and echo
debug Print what is sent and received
direct Do-nothing: forward all data unchanged
hexlify Show a hexadecimal representation of the data (code point of each character)
log2file Log data to a file "platformio-device-monitor-%date%.log" located in the current working directory
nocontrol Remove all control codes, incl. CR+LF
printable Show decimal code for all non-ASCII characters and replace most control codes
time Add timestamp with milliseconds for each new line
send_on_enter Send a text to device on ENTER
esp32_exception_decoder Custom filter for Espressif 32 which decodes crash exception
esp8266_exception_decoder Custom filter for Espressif 8266 which decodes crash exception

New in version 4.3.

You need to use a log2file filter from Filters:

$ platformio device monitor -f log2file -f default


or using "platformio.ini" (Project Configuration File) and monitor_filters

[env:log_output_to_file]
...
platform = ...
monitor_filters = log2file, default


PlatformIO Core (CLI) provides an API to extend device monitor with a custom filter declared in "monitor" folder of Development Platforms. See examples:

  • https://github.com/platformio/platform-espressif32/tree/develop/monitor
  • https://github.com/platformio/platform-espressif8266/tree/develop/monitor

1.
Show available options for monitor

$ platformio device monitor --help
Usage: platformio device monitor [OPTIONS]
Options:
  -p, --port TEXT       Port, a number or a device name
  -b, --baud INTEGER    Set baud rate, default=9600
  --parity [N|E|O|S|M]  Set parity, default=N
  --rtscts              Enable RTS/CTS flow control, default=Off
  --xonxoff             Enable software flow control, default=Off
  --rts [0|1]           Set initial RTS line state, default=0
  --dtr [0|1]           Set initial DTR line state, default=0
  --echo                Enable local echo, default=Off
  --encoding TEXT       Set the encoding for the serial port (e.g. hexlify,
                        Latin1, UTF-8), default: UTF-8
  -f, --filter TEXT     Add filters / text transformation
  --eol [CR|LF|CRLF]    End of line mode, default=CRLF
  --raw                 Do not apply any encodings/transformations
  --exit-char INTEGER   ASCII code of special character that is used to exit
                        the application, default=29 (DEC)
  --menu-char INTEGER   ASCII code of special character that is used to
                        control miniterm (menu), default=20 (DEC)
  --quiet               Diagnostics: suppress non-error messages, default=Off
  -h, --help            Show this message and exit.


2.
Communicate with serial device and print help inside terminal

$ platformio device monitor
--- Available ports:
--- /dev/cu.Bluetooth-Incoming-Port n/a
--- /dev/cu.Bluetooth-Modem n/a
--- /dev/cu.SLAB_USBtoUART CP2102 USB to UART Bridge Controller
--- /dev/cu.obd2ecu-SPPDev n/a
Enter port name:/dev/cu.SLAB_USBtoUART
--- Miniterm on /dev/cu.SLAB_USBtoUART: 9600,8,N,1 ---
--- Quit: Ctrl+C  |  Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
Hello PlatformIO!
---
--- Ctrl+]   Exit program
--- Ctrl+T   Menu escape key, followed by:
--- Menu keys:
---    Ctrl+T  Send the menu character itself to remote
---    Ctrl+]  Send the exit character itself to remote
---    Ctrl+I  Show info
---    Ctrl+U  Upload file (prompt will be shown)
--- Toggles:
---    Ctrl+R  RTS          Ctrl+E  local echo
---    Ctrl+D  DTR          Ctrl+B  BREAK
---    Ctrl+L  line feed    Ctrl+A  Cycle repr mode
---
--- Port settings (Ctrl+T followed by the following):
---    p          change port
---    7 8        set data bits
---    n e o s m  change parity (None, Even, Odd, Space, Mark)
---    1 2 3      set stop bits (1, 2, 1.5)
---    b          change baud rate
---    x X        disable/enable software flow control
---    r R        disable/enable hardware flow control
--- exit ---


Helper command for PlatformIO Home.

•
platformio home
  • Usage
  • Description
  • Options
  • Examples


platformio home
pio home


Launch PlatformIO Home Web-server.


Web-server HTTP port, default is 8008.


Web-server HTTP host, default is 127.0.0.1. You can open PIO Home for inbound connections using host 0.0.0.0.


Do not automatically open PIO Home in a system Web-browser.


Automatically shutdown server on timeout (in seconds) when no clients are connected. Default is 0 which means never auto shutdown.

> platformio home
  ___I_
 /\-_--\   PlatformIO Home
/  \_-__\
|[]| [] |  http://127.0.0.1:8008
|__|____|_______________________
Open PIO Home in your browser by this URL => http://127.0.0.1:8008
PIO Home has been started. Press Ctrl+C to shutdown.



platformio lib [OPTIONS] COMMAND
# To print all available commands and options use
platformio lib --help
platformio lib COMMAND --help



Manage custom library storage. It can be used later for the lib_extra_dirs option from "platformio.ini" (Project Configuration File). Multiple options are allowed.


Manage global PlatformIO's library storage ( "core_dir/lib") where Library Dependency Finder (LDF) will look for dependencies by default.


Manage libraries for the specific project build environments declared in "platformio.ini" (Project Configuration File). Works for --storage-dir which is valid PlatformIO project.

[image]

•
platformio lib builtin
  • Usage
  • Description
  • Options
  • Examples


platformio lib builtin [OPTIONS]
pio lib builtin [OPTIONS]


List built-in libraries based on installed Development Platforms and their frameworks, SDKs, etc.


List libraries from specified storages. For example, framework-arduinoavr.


Return the output in JSON format

> platformio lib builtin
framework-arduinoavr
********************
Bridge
======
Enables the communication between the Linux processor and the microcontroller. For Arduino/Genuino Yún, Yún Shield and TRE only.
Version: 1.6.1
Homepage: http://www.arduino.cc/en/Reference/YunBridgeLibrary
Keywords: communication
Compatible frameworks: arduino
Compatible platforms: *
Authors: Arduino
EEPROM
======
Enables reading and writing to the permanent board storage.
Version: 2.0
Homepage: http://www.arduino.cc/en/Reference/EEPROM
Keywords: data, storage
Compatible frameworks: arduino
Compatible platforms: atmelavr
Authors: Arduino, Christopher Andrews
...
framework-arduinosam
********************
Audio
=====
Allows playing audio files from an SD card. For Arduino DUE only.
Version: 1.0
Homepage: http://arduino.cc/en/Reference/Audio
Keywords: signal, input, output
Compatible frameworks: arduino
Compatible platforms: atmelsam
Authors: Arduino
...
framework-arduinoespressif32
****************************
SPI
===
Enables the communication with devices that use the Serial Peripheral Interface (SPI) Bus. For all Arduino boards, BUT Arduino DUE.
Version: 1.0
Homepage: http://arduino.cc/en/Reference/SPI
Keywords: signal, input, output
Compatible frameworks: arduino
Compatible platforms:
Authors: Hristo Gochkov
...
framework-arduinoespressif8266
******************************
ArduinoOTA
==========
Enables Over The Air upgrades, via wifi and espota.py UDP request/TCP download.
Version: 1.0
Keywords: communication
Compatible frameworks: arduino
Compatible platforms: espressif8266
Authors: Ivan Grokhotkov and Miguel Angel Ajo
DNSServer
=========
A simple DNS server for ESP8266.
Version: 1.1.0
Keywords: communication
Compatible frameworks: arduino
Compatible platforms: espressif8266
Authors: Kristijan Novoselić
...
framework-arduinointel
**********************
Adafruit NeoPixel
=================
Arduino library for controlling single-wire-based LED pixels and strip.
Version: 1.0.3
Homepage: https://github.com/adafruit/Adafruit_NeoPixel
Keywords: display
Compatible frameworks: arduino
Compatible platforms: *
Authors: Adafruit
CurieBLE
========
Library to manage the Bluetooth Low Energy module with Curie Core boards.
Version: 1.0
Keywords: communication
Compatible frameworks: arduino
Compatible platforms: intel_arc32
Authors: Emutex
CurieEEPROM
===========
Enables reading and writing to OTP flash area of Curie
Version: 1.0
Homepage: http://www.arduino.cc/en/Reference/EEPROM
Keywords: data, storage
Compatible frameworks: arduino
Compatible platforms: intel_arc32
Authors: Intel
...
framework-arduinomicrochippic32
*******************************
Firmata
=======
Enables the communication with computer apps using a standard serial protocol. For all Arduino boards.
Version: 2.4.4
Homepage: https://github.com/firmata/arduino
Keywords: device, control
Compatible frameworks: arduino
Compatible platforms: *
Authors: Firmata Developers
framework-arduinoteensy
***********************
Adafruit CC3000 Library
=======================
Library code for Adafruit's CC3000 WiFi breakouts.
Version: 1.0.1
Homepage: https://github.com/adafruit/Adafruit_CC3000_Library
Keywords: communication
Compatible frameworks: arduino
Compatible platforms: *
Authors: Adafruit
...
framework-energiamsp430
***********************
AIR430BoostEuropeETSI
=====================
Library for the CC110L Sub-1GHz radio BoosterPack for use in Europe
Version: 1.0.0
Homepage: http://energia.nu/reference/libraries/
Keywords: communication
Compatible frameworks: arduino
Compatible platforms:
Authors: Energia
...
framework-energiativa
*********************
aJson
=====
An Arduino library to enable JSON processing with Arduino
Keywords: json, rest, http, web
Compatible frameworks: arduino
Compatible platforms: atmelavr


•
platformio lib install
  • Usage
  • Description
  • Storage Options
  • Options
  • Version control
  • Git
  • Mercurial
  • Subversion

•
Examples


platformio lib [STORAGE_OPTIONS] install [OPTIONS] [LIBRARY...]
pio lib [STORAGE_OPTIONS] install [OPTIONS] [LIBRARY...]
# install all project dependencies declared via "lib_deps"
# (run it from a project root where is located "platformio.ini")
platformio lib install [OPTIONS]
# install project dependent library
# (run it from a project root where is located "platformio.ini")
platformio lib install [OPTIONS] [LIBRARY...]
# install dependencies for the specific project build environment
# (run it from a project root where is located "platformio.ini")
platformio lib -e myenv install [OPTIONS] [LIBRARY...]
platformio lib -d /path/to/platformio/project -e myenv install [OPTIONS] [LIBRARY...]
# install to global storage
platformio lib --global install [OPTIONS] [LIBRARY...]
platformio lib -g install [OPTIONS] [LIBRARY...]
# install to custom storage
platformio lib --storage-dir /path/to/dir install [OPTIONS] [LIBRARY...]
platformio lib -d /path/to/dir1 -d /path/to/dir2 install [OPTIONS] [LIBRARY...]
# [LIBRARY...] forms
platformio lib [STORAGE_OPTIONS] install (with no args, project dependencies)
platformio lib [STORAGE_OPTIONS] install <id>
platformio lib [STORAGE_OPTIONS] install id=<id>
platformio lib [STORAGE_OPTIONS] install <id>@<version>
platformio lib [STORAGE_OPTIONS] install <id>@<version range>
platformio lib [STORAGE_OPTIONS] install <name>
platformio lib [STORAGE_OPTIONS] install <name>@<version>
platformio lib [STORAGE_OPTIONS] install <name>@<version range>
platformio lib [STORAGE_OPTIONS] install <zip or tarball url>
platformio lib [STORAGE_OPTIONS] install file://<zip or tarball file>
platformio lib [STORAGE_OPTIONS] install file://<folder>
platformio lib [STORAGE_OPTIONS] install <repository>
platformio lib [STORAGE_OPTIONS] install <name>=<repository> (name it should have locally)
platformio lib [STORAGE_OPTIONS] install <repository#tag> ("tag" can be commit, branch or tag)


WARNING:

If some libraries are not visible in PlatformIO IDE and Code Completion or Code Linting does not work properly, please perform
  • Atom: "Menu: PlatformIO > Rebuild C/C++ Project Index (Autocomplete, Linter)"
  • VSCode: "Menu: View > Command Palette... > PlatformIO: Rebuild C/C++ Project Index"



Install a library, and any libraries that it depends on using:

1.
Library id or name from PlatformIO Library Registry
2.
Custom folder, repository or archive.

The version supports Semantic Versioning ( <major>.<minor>.<patch>) and can take any of the following forms:

  • 1.2.3 - an exact version number. Use only this exact version
  • ^1.2.3 - any compatible version (exact version for 1.x.x versions)
  • ~1.2.3 - any version with the same major and minor versions, and an equal or greater patch version
  • >1.2.3 - any version greater than 1.2.3. >=, <, and <= are also possible
  • >0.1.0,!=0.2.0,<0.3.0 - any version greater than 0.1.0, not equal to 0.2.0 and less than 0.3.0

PlatformIO supports installing from local directory or archive. Need to use file:// prefix before local path. Also, directory or archive should contain .library.json manifest (see library.json).

  • file:///local/path/to/the/platform/dir
  • file:///local/path/to/the/platform.zip
  • file:///local/path/to/the/platform.tar.gz

Storage Options

See base options for Library Manager CLI.


Save installed libraries into the "platformio.ini" (Project Configuration File) dependency list (lib_deps).

You can save libraries for the specific project environment using -e, --environment option from platformio lib command. For example, platformio lib -e myenv install [LIBRARY...].


Suppress progress reporting


Allow one to make a choice for all prompts


Reinstall/redownload library if it exists

Version control

PlatformIO supports installing from Git, Mercurial and Subversion, and detects the type of VCS using url prefixes: "git+", "hg+", or "svn+".

NOTE:

PlatformIO requires a working VCS command on your path: git, hg or svn.


The supported schemes are: git, git+https and git+ssh. Here are the supported forms:

  • user/library (short version for GitHub repository)
  • https://github.com/user/library.git
  • git+git://git.server.org/my-library
  • git+https://git.server.org/my-library
  • git+ssh://git.server.org/my-library
  • git+ssh://user@git.server.org/my-library
  • [user@]host.xz:path/to/repo.git

Passing branch names, a commit hash or a tag name is possible like so:

  • https://github.com/user/library.git#master
  • git+git://git.server.org/my-library#master
  • git+https://git.server.org/my-library#v1.0
  • git+ssh://git.server.org/my-library#7846d8ad52f983f2f2887bdc0f073fe9755a806d

The supported schemes are: hg+http, hg+https and hg+ssh. Here are the supported forms:

  • https://developer.mbed.org/users/user/code/library/ (install ARM mbed library)
  • hg+hg://hg.server.org/my-library
  • hg+https://hg.server.org/my-library
  • hg+ssh://hg.server.org/my-library

Passing branch names, a commit hash or a tag name is possible like so:

  • hg+hg://hg.server.org/my-library#master
  • hg+https://hg.server.org/my-library#v1.0
  • hg+ssh://hg.server.org/my-library#4cfe2fa00668

The supported schemes are: svn, svn+svn, svn+http, svn+https and svn+ssh. Here are the supported forms:

  • svn+svn://svn.server.org/my-library
  • svn+https://svn.server.org/my-library
  • svn+ssh://svn.server.org/my-library

You can also give specific revisions to an SVN URL, like so:

•
svn+svn://svn.server.org/my-library#13

1.
Install the latest version of library to a global storage using ID or NAME

> platformio lib -g install 4
Library Storage: /storage/dir/...
LibraryManager: Installing id=4
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
IRremote @ 2.2.1 has been successfully installed!
# repeat command with name
> platformio lib -g install IRRemote
Library Storage: /storage/dir/...
Looking for IRRemote library in registry
Found: https://platformio.org/lib/show/4/IRremote
LibraryManager: Installing id=4
IRremote @ 2.2.1 is already installed


2.
Install specified version of a library to a global storage

> platformio lib -g install ArduinoJson@5.6.7
Library Storage: /storage/dir/...
Looking for ArduinoJson library in registry
Found: https://platformio.org/lib/show/64/ArduinoJson
LibraryManager: Installing id=64 @ 5.6.7
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
ArduinoJson @ 5.6.7 has been successfully installed!


3.
Install library with dependencies to custom storage

> platformio lib --storage-dir /my/storage/dir install DallasTemperature
Library Storage: /my/storage/dir
Looking for DallasTemperature library in registry
Found: https://platformio.org/lib/show/54/DallasTemperature
LibraryManager: Installing id=54
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
DallasTemperature @ 3.7.7 has been successfully installed!
Installing dependencies
Looking for OneWire library in registry
Found: https://platformio.org/lib/show/1/OneWire
LibraryManager: Installing id=1
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
OneWire @ 8fd2ebfec7 has been successfully installed!


4.
Install ARM mbed library to the global storage

> platformio lib -g install https://developer.mbed.org/users/simon/code/TextLCD/
Library Storage: /storage/dir/...
LibraryManager: Installing TextLCD
Mercurial Distributed SCM (version 3.8.4)
(see https://mercurial-scm.org for more information)
Copyright (C) 2005-2016 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
requesting all changes
adding changesets
adding manifests
adding file changes
added 9 changesets with 18 changes to 6 files
updating to branch default
2 files updated, 0 files merged, 0 files removed, 0 files unresolved
TextLCD @ 308d188a2d3a has been successfully installed!


5.
Install from archive using URL

> platformio lib -g install  https://github.com/adafruit/DHT-sensor-library/archive/master.zip
Library Storage: /storage/dir/...
LibraryManager: Installing master
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
DHT sensor library @ 1.2.3 has been successfully installed!


•
platformio lib list
  • Usage
  • Description
  • Storage Options
  • Options
  • Examples


platformio lib [STORAGE_OPTIONS] list [OPTIONS]
pio lib [STORAGE_OPTIONS] list [OPTIONS]
# list project dependent libraries
# (run it from a project root where is located "platformio.ini")
platformio lib list [OPTIONS]
# list libraries from global storage
platformio lib --global list [OPTIONS]
platformio lib -g list [OPTIONS]
# list libraries from custom storage
platformio lib --storage-dir /path/to/dir list [OPTIONS]
platformio lib -d /path/to/dir list [OPTIONS]


List installed libraries

Storage Options

See base options for Library Manager CLI.


Return the output in JSON format

> platformio lib -g list
Library Storage: /storage/dir/...
Adafruit Unified Sensor
=======================
#ID: 31
Required for all Adafruit Unified Sensor based libraries.
Version: 1.0.2
Keywords: sensors
Compatible frameworks: arduino
Compatible platforms: atmelavr, atmelsam, espressif8266, intel_arc32, microchippic32, nordicnrf51, teensy, timsp430
Authors: Adafruit
ArduinoJson
===========
#ID: 64
An elegant and efficient JSON library for embedded systems
Version: 5.8.0
Keywords: web, json, http, rest
Compatible frameworks: arduino
Compatible platforms: atmelavr, atmelsam, espressif8266, intel_arc32, microchippic32, nordicnrf51, teensy, timsp430
Authors: Benoit Blanchon
ArduinoJson
===========
#ID: 64
An elegant and efficient JSON library for embedded systems
Version: 5.6.7
Keywords: web, json, http, rest
Compatible frameworks: arduino
Compatible platforms: atmelavr, atmelsam, espressif8266, intel_arc32, microchippic32, nordicnrf51, teensy, timsp430
Authors: Benoit Blanchon
ArduinoJson
===========
#ID: 64
An elegant and efficient JSON library for embedded systems
Version: 5.7.2
Keywords: web, json, http, rest
Compatible frameworks: arduino
Compatible platforms: atmelavr, atmelsam, espressif8266, intel_arc32, microchippic32, nordicnrf51, teensy, timsp430
Authors: Benoit Blanchon
Blynk
=====
#ID: 415
Build a smartphone app for your project in minutes. Blynk allows creating IoT solutions easily. It supports  WiFi, BLE, Bluetooth, Ethernet, GSM, USB, Serial. Works with many boards like ESP8266, ESP32, Arduino UNO, Nano, Due, Mega, Zero, MKR100, Yun, Raspberry Pi, Particle, Energia, ARM mbed, Intel Edison/Galileo/Joule, BBC micro:bit, DFRobot, RedBearLab, Microduino, LinkIt ONE ...
Version: 0.4.3
Homepage: http://blynk.cc
Keywords: control, gprs, protocol, communication, app, bluetooth, serial, cloud, web, usb, m2m, ble, 3g, smartphone, http, iot, device, sensors, data, esp8266, mobile, wifi, ethernet, gsm
Compatible frameworks: energia, wiringpi, arduino
Compatible platforms: atmelavr, atmelsam, espressif8266, intel_arc32, linux_arm, microchippic32, nordicnrf51, teensy, timsp430, titiva
Authors: Volodymyr Shymanskyy
Bounce2
=======
#ID: 1106
Debouncing library for Arduino or Wiring
Version: 2.1
Keywords: input, signal, output, bounce
Compatible frameworks: arduino
Compatible platforms: atmelavr, atmelsam, espressif8266, intel_arc32, microchippic32, nordicnrf51, teensy, timsp430
Authors: Thomas O Fredericks
Homie
=====
#ID: 555
ESP8266 framework for Homie, a lightweight MQTT convention for the IoT
Version: 1.5.0
Keywords: home, mqtt, iot, esp8266, automation
Compatible frameworks: arduino
Compatible platforms: espressif8266
Authors: Marvin Roger
JustWifi
========
#ID: 1282
Wifi Manager for ESP8266 that supports multiple wifi networks and scan for strongest signal
Version: 1.1.1
License: GPL-3.0
Keywords: manager, wifi, scan
Compatible frameworks: arduino
Compatible platforms: espressif8266
Authors: Xose Perez
LiquidCrystal
=============
#ID: 136
LiquidCrystal Library is faster and extensable, compatible with the original LiquidCrystal library
Version: 1.3.4
Keywords: lcd, hd44780
Compatible frameworks: arduino
Compatible platforms: atmelavr
Authors: F Malpartida
TextLCD
=======
hg+https://developer.mbed.org/users/simon/code/TextLCD/
Version: 308d188a2d3a
Keywords: uncategorized
Time
====
#ID: 44
Time keeping library
Version: 1.5
Homepage: http://playground.arduino.cc/Code/Time
Keywords: week, rtc, hour, year, month, second, time, date, day, minute
Compatible frameworks: arduino
Compatible platforms:
Authors: Michael Margolis, Paul Stoffregen
Timezone
========
#ID: 76
Arduino library to facilitate time zone conversions and automatic daylight saving (summer) time adjustments
Version: 510ae2f6b6
Keywords: zone, time
Compatible frameworks: arduino
Compatible platforms: atmelavr
Authors: Jack Christensen
U8g2
====
#ID: 942
Monochrome LCD, OLED and eInk Library. Display controller: SSD1305, SSD1306, SSD1322, SSD1325, SSD1327, SSD1606, SH1106, T6963, RA8835, LC7981, PCD8544, PCF8812, UC1604, UC1608, UC1610, UC1611, UC1701, ST7565, ST7567, NT7534, ST7920, LD7032, KS0108. Interfaces: I2C, SPI, Parallel.
Version: 2.11.4
Homepage: https://github.com/olikraus/u8g2
Keywords: display
Compatible frameworks: arduino
Compatible platforms: atmelavr, atmelsam, espressif8266, intel_arc32, microchippic32, nordicnrf51, teensy, timsp430
Authors: oliver
USB-Host-Shield-20
==================
#ID: 59
Revision 2.0 of MAX3421E-based USB Host Shield Library
Version: 1.2.1
License: GPL-2.0
Keywords: usb, spp, mass storage, pl2303, acm, ftdi, xbox, host, hid, wii, buzz, ps3, bluetooth, adk, ps4
Compatible frameworks: spl, arduino
Compatible platforms: atmelavr, atmelsam, teensy, nordicnrf51, ststm32
Authors: Oleg Mazurov, Alexei Glushchenko, Kristian Lauszus, Andrew Kroll


•
platformio lib register
  • Usage
  • Description
  • Examples


platformio lib register [MANIFEST_URL]
pio lib register [MANIFEST_URL]


Register new library in PlatformIO Library Registry.

PlatformIO Library Registry supports the next library manifests:

  • PlatformIO library.json
  • Arduino library.properties
  • ARM mbed yotta module.json.

platformio lib register https://raw.githubusercontent.com/bblanchon/ArduinoJson/master/library.json
platformio lib register https://raw.githubusercontent.com/adafruit/DHT-sensor-library/master/library.properties
platformio lib register https://raw.githubusercontent.com/ARMmbed/ble/master/module.json


•
platformio lib search
  • Usage
  • Description
  • Options
  • Examples


platformio lib search [OPTIONS] [QUERY]
pio lib search [OPTIONS] [QUERY]


Search for library in PlatformIO Library Registry by library.json fields in the boolean mode.

The boolean search capability supports the following operators:

Operator Description
+ A leading or trailing plus sign indicates that this word must be present in library fields (see above) that is returned.
- A leading or trailing minus sign indicates that this word must not be present in any of the libraries that are returned.
(no operator) By default (when neither + nor - is specified), the word is optional, but the libraries that contain it are rated higher.
> < These two operators are used to change a word's contribution to the relevance value that is assigned to a library. The > operator increases the contribution and the < operator decreases it.
( ) Parentheses group words into subexpressions. Parenthesized groups can be nested.
~ A leading tilde acts as a negation operator, causing the word's contribution to the library's relevance to be negative. This is useful for marking "noise" words. A library containing such a word is rated lower than others, but is not excluded altogether, as it would be with the - operator.
* The asterisk serves as the truncation (or wildcard) operator. Unlike the other operators, it is appended to the word to be affected. Words match if they begin with the word preceding the * operator.
" A phrase that is enclosed within double quote (") characters matches only libraries that contain the phrase literally, as it was typed.

For more detail information please go to MySQL Boolean Full-Text Searches.


Filter libraries by registry ID


Filter libraries by specified name (strict search)


Filter libraries by specified author


Filter libraries by specified keyword


Filter libraries by specified framework


Filter libraries by specified keyword


Filter libraries by header file (include)

For example, platformio lib search --header "OneWire.h"


Return the output in JSON format


Manually paginate through search results. This option is useful in pair with --json-output.

1.
List all libraries

> platformio lib search
Found N libraries:
ArduinoJson
===========
#ID: 64
An elegant and efficient JSON library for embedded systems
Keywords: web, json, http, rest
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR, Atmel SAM, Espressif 8266, Intel ARC32, Microchip PIC32, Nordic nRF51, Teensy, TI MSP430
Authors: Benoit Blanchon
DHT sensor library
==================
#ID: 19
Arduino library for DHT11, DHT22, etc Temp & Humidity Sensors
Keywords: unified, dht, sensor, temperature, humidity
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR
Authors: Adafruit Industries
PubSubClient
============
#ID: 89
A client library for MQTT messaging. MQTT is a lightweight messaging protocol ideal for small devices. This library allows you to send and receive MQTT messages. It supports the latest MQTT 3.1.1 protocol and can be configured to use the older MQTT 3.1...
Keywords: ethernet, mqtt, iot, m2m
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR, Atmel SAM, Espressif 8266, Intel ARC32, Microchip PIC32, Nordic nRF51, Teensy, TI MSP430
Authors: Nick O'Leary
...
ESPAsyncWebServer
=================
#ID: 306
Asynchronous HTTP and WebSocket Server Library for ESP8266 and ESP32
Keywords: async, websocket, http, webserver
Compatible frameworks: Arduino
Compatible platforms: Espressif 8266
Authors: Hristo Gochkov
Show next libraries? [y/N]:
...


2.
Search for 1-Wire libraries

> platformio lib search "1-wire"
Found N libraries:
DS1820
======
#ID: 196
Dallas / Maxim DS1820 1-Wire library. For communication with multiple DS1820 on a single 1-Wire bus. Also supports DS18S20 and DS18B20.
Keywords: ds18s20, 1-wire, ds1820, ds18b20
Compatible frameworks: mbed
Compatible platforms: Freescale Kinetis, Nordic nRF51, NXP LPC, ST STM32, Teensy
Authors: Michael Hagberg
OneWire
=======
#ID: 1
Control 1-Wire protocol (DS18S20, DS18B20, DS2408 and etc)
Keywords: onewire, temperature, bus, 1-wire, ibutton, sensor
Compatible frameworks: Arduino
Compatible platforms:
Authors: Paul Stoffregen, Jim Studt, Tom Pollard, Derek Yerger, Josh Larios, Robin James, Glenn Trewitt, Jason Dangel, Guillermo Lovato, Ken Butcher, Mark Tillotson, Bertrik Sikken, Scott Roberts
Show next libraries? [y/N]:
...


3.
Search for Arduino-based "I2C" libraries

> platformio lib search "i2c" --framework="arduino"
Found N libraries:
I2Cdevlib-AK8975
================
#ID: 10
AK8975 is 3-axis electronic compass IC with high sensitive Hall sensor technology
Keywords: i2c, i2cdevlib, sensor, compass
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR
Authors: Jeff Rowberg
I2Cdevlib-Core
==============
#ID: 11
The I2C Device Library (I2Cdevlib) is a collection of uniform and well-documented classes to provide simple and intuitive interfaces to I2C devices.
Keywords: i2cdevlib, i2c
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR
Authors: Jeff Rowberg
Adafruit 9DOF Library
=====================
#ID: 14
Unified sensor driver for the Adafruit 9DOF Breakout (L3GD20 / LSM303)
Keywords: magnetometer, unified, accelerometer, spi, compass, i2c, sensor, gyroscope
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR
Authors: Adafruit Industries
Show next libraries? [y/N]:
...


4.
Search for libraries by "web" and "http" keywords.

> platformio lib search --keyword="web" --keyword="http"
Found N libraries:
ArduinoJson
===========
#ID: 64
An elegant and efficient JSON library for embedded systems
Keywords: web, json, http, rest
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR, Atmel SAM, Espressif 8266, Intel ARC32, Microchip PIC32, Nordic nRF51, Teensy, TI MSP430
Authors: Benoit Blanchon
ESPAsyncWebServer
=================
#ID: 306
Asynchronous HTTP and WebSocket Server Library for ESP8266 and ESP32
Keywords: async, websocket, http, webserver
Compatible frameworks: Arduino
Compatible platforms: Espressif 8266
Authors: Hristo Gochkov
ESP8266wifi
===========
#ID: 1101
ESP8266 Arduino library with built in reconnect functionality
Keywords: web, http, wifi, server, client, wi-fi
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR
Authors: Jonas Ekstrand
Blynk
=====
#ID: 415
Build a smartphone app for your project in minutes. Blynk allows creating IoT solutions easily. It supports  WiFi, BLE, Bluetooth, Ethernet, GSM, USB, Serial. Works with many boards like ESP8266, ESP32, Arduino UNO, Nano, Due, Mega, Zero, MKR100, Yun,...
Keywords: control, gprs, protocol, communication, app, bluetooth, serial, cloud, web, usb, m2m, ble, 3g, smartphone, http, iot, device, sensors, data, esp8266, mobile, wifi, ethernet, gsm
Compatible frameworks: Arduino, Energia, WiringPi
Compatible platforms: Atmel AVR, Atmel SAM, Espressif 8266, Intel ARC32, Linux ARM, Microchip PIC32, Nordic nRF51, Teensy, TI MSP430, TI Tiva
Authors: Volodymyr Shymanskyy
Show next libraries? [y/N]:
...


5.
Search for libraries by "Adafruit Industries" author

> platformio lib search --author="Adafruit Industries"
Found N libraries:
DHT sensor library
==================
#ID: 19
Arduino library for DHT11, DHT22, etc Temp & Humidity Sensors
Keywords: unified, dht, sensor, temperature, humidity
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR
Authors: Adafruit Industries
Adafruit DHT Unified
====================
#ID: 18
Unified sensor library for DHT (DHT11, DHT22 and etc) temperature and humidity sensors
Keywords: unified, dht, sensor, temperature, humidity
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR
Authors: Adafruit Industries
Show next libraries? [y/N]:
...


6.
Search for libraries which are compatible with Dallas temperature sensors like DS18B20, DS18S20 and etc.

> platformio lib search "DS*"
Found N libraries:
DS1820
======
#ID: 196
Dallas / Maxim DS1820 1-Wire library. For communication with multiple DS1820 on a single 1-Wire bus. Also supports DS18S20 and DS18B20.
Keywords: ds18s20, 1-wire, ds1820, ds18b20
Compatible frameworks: mbed
Compatible platforms: Freescale Kinetis, Nordic nRF51, NXP LPC, ST STM32, Teensy
Authors: Michael Hagberg
I2Cdevlib-DS1307
================
#ID: 99
The DS1307 serial real-time clock (RTC) is a low-power, full binary-coded decimal (BCD) clock/calendar plus 56 bytes of NV SRAM
Keywords: i2cdevlib, clock, i2c, rtc, time
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR
Authors: Jeff Rowberg
Show next libraries? [y/N]:
...


7.
Search for Energia-based *nRF24* or *HttpClient* libraries. The search query that is described below can be interpreted like energia nRF24 OR energia HttpClient

> platformio lib search "+(nRF24 HttpClient)" --framework="arduino"
Found N libraries:
RadioHead
=========
#ID: 124
The RadioHead Packet Radio library which provides a complete object-oriented library for sending and receiving packetized messages via RF22/24/26/27/69, Si4460/4461/4463/4464, nRF24/nRF905, SX1276/77/78, RFM95/96/97/98 and etc.
Keywords: rf, radio, wireless
Compatible frameworks: Arduino, Energia
Compatible platforms: Atmel AVR, Atmel SAM, Espressif 32, Espressif 8266, Infineon XMC, Intel ARC32, Kendryte K210, Microchip PIC32, Nordic nRF51, Nordic nRF52, ST STM32, ST STM8, Teensy, TI MSP430, TI Tiva
Authors: Mike McCauley
ArduinoHttpClient
=================
#ID: 798
[EXPERIMENTAL] Easily interact with web servers from Arduino, using HTTP and WebSocket's.
Keywords: communication
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR, Atmel SAM, Espressif 32, Espressif 8266, Intel ARC32, Microchip PIC32, Nordic nRF51, Nordic nRF52, ST STM32, ST STM8, Teensy, TI MSP430
Authors: Arduino
HttpClient
==========
#ID: 66
Library to easily make HTTP GET, POST and PUT requests to a web server.
Keywords: communication
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR, Atmel SAM, Espressif 32, Espressif 8266, Intel ARC32, Microchip PIC32, Nordic nRF51, Nordic nRF52, ST STM32, Teensy, TI MSP430
Authors: Adrian McEwen
Show next libraries? [y/N]:
...


8.
Search for the all sensor libraries excluding temperature.

> platformio lib search "sensor -temperature"
Found N libraries:
SparkFun VL6180 Sensor
======================
#ID: 407
The VL6180 combines an IR emitter, a range sensor, and an ambient light sensor together for you to easily use and communicate with via an I2C interface.
Keywords: sensors
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR, Atmel SAM, Espressif 8266, Intel ARC32, Microchip PIC32, Nordic nRF51, Teensy, TI MSP430
Authors: Casey Kuhns@SparkFun, SparkFun Electronics
I2Cdevlib-AK8975
================
#ID: 10
AK8975 is 3-axis electronic compass IC with high sensitive Hall sensor technology
Keywords: i2c, i2cdevlib, sensor, compass
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR
Authors: Jeff Rowberg
Adafruit 9DOF Library
=====================
#ID: 14
Unified sensor driver for the Adafruit 9DOF Breakout (L3GD20 / LSM303)
Keywords: magnetometer, unified, accelerometer, spi, compass, i2c, sensor, gyroscope
Compatible frameworks: Arduino
Compatible platforms: Atmel AVR
Authors: Adafruit Industries
Show next libraries? [y/N]:
...


•
platformio lib show
  • Usage
  • Description
  • Options
  • Examples


platformio lib show [LIBRARY]
pio lib show [LIBRARY]


Show detailed info about a library using PlatformIO Library Registry.

The possible values for [LIBRARY]:

  • Library ID from Registry (preferred)
  • Library Name


Return the output in JSON format

> platformio lib show OneWire
PubSubClient
============
#ID: 89
A client library for MQTT messaging. MQTT is a lightweight messaging protocol ideal for small devices. This library allows you to send and receive MQTT messages. It supports the latest MQTT 3.1.1 protocol and can be configured to use the older MQTT 3.1...
Version: 2.6, released 10 months ago
Manifest: https://raw.githubusercontent.com/ivankravets/pubsubclient/patch-2/library.json
Homepage: http://pubsubclient.knolleary.net
Repository: https://github.com/knolleary/pubsubclient.git
Authors
-------
Nick O'Leary https://github.com/knolleary
Keywords
--------
ethernet
mqtt
iot
m2m
Compatible frameworks
---------------------
Arduino
Compatible platforms
--------------------
Atmel AVR
Atmel SAM
Espressif 8266
Intel ARC32
Microchip PIC32
Nordic nRF51
Teensy
TI MSP430
Headers
-------
PubSubClient.h
Examples
--------
http://dl.platformio.org/libraries/examples/0/89/mqtt_auth.ino
http://dl.platformio.org/libraries/examples/0/89/mqtt_basic.ino
http://dl.platformio.org/libraries/examples/0/89/mqtt_esp8266.ino
http://dl.platformio.org/libraries/examples/0/89/mqtt_publish_in_callback.ino
http://dl.platformio.org/libraries/examples/0/89/mqtt_reconnect_nonblocking.ino
http://dl.platformio.org/libraries/examples/0/89/mqtt_stream.ino
Versions
--------
2.6, released 10 months ago
Downloads
---------
Today: 25
Week: 120
Month: 462


•
platformio lib stats
  • Usage
  • Description
  • Options
  • Examples


platformio lib stats
pio lib stats


Show PlatformIO Library Registry statistics:

  • Recently updated
  • Recently added
  • Recent keywords
  • Popular keywords
  • Featured: Today
  • Featured: Week
  • Featured: Month

This information is the same that is shown on this page:

•
https://platformio.org/lib


Return the output in JSON format

RECENTLY UPDATED
****************
Name                     Date                    Url
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
GroveEncoder             12 hours ago            https://platformio.org/lib/show/1382/GroveEncoder
RF24G                    12 hours ago            https://platformio.org/lib/show/1381/RF24G
Sim800L Library Revised  12 hours ago            https://platformio.org/lib/show/1380/Sim800L%20Library%20Revised
ArduinoSTL               12 hours ago            https://platformio.org/lib/show/750/ArduinoSTL
hd44780                  13 hours ago            https://platformio.org/lib/show/738/hd44780
RECENTLY ADDED
**************
Name                     Date                    Url
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
GroveEncoder             12 hours ago            https://platformio.org/lib/show/1382/GroveEncoder
RF24G                    12 hours ago            https://platformio.org/lib/show/1381/RF24G
Sim800L Library Revised  12 hours ago            https://platformio.org/lib/show/1380/Sim800L%20Library%20Revised
DS3231                   a day ago               https://platformio.org/lib/show/1379/DS3231
ArduboyPlaytune          4 days ago              https://platformio.org/lib/show/1378/ArduboyPlaytune
RECENT KEYWORDS
***************
Name                     Url
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
cobs                     https://platformio.org/lib/search?query=keyword%3Acobs
packet                   https://platformio.org/lib/search?query=keyword%3Apacket
framing                  https://platformio.org/lib/search?query=keyword%3Aframing
3g                       https://platformio.org/lib/search?query=keyword%3A3g
tdd                      https://platformio.org/lib/search?query=keyword%3Atdd
POPULAR KEYWORDS
****************
Name                     Url
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
display                  https://platformio.org/lib/search?query=keyword%3Adisplay
lcd                      https://platformio.org/lib/search?query=keyword%3Alcd
sensors                  https://platformio.org/lib/search?query=keyword%3Asensors
graphics                 https://platformio.org/lib/search?query=keyword%3Agraphics
communication            https://platformio.org/lib/search?query=keyword%3Acommunication
oled                     https://platformio.org/lib/search?query=keyword%3Aoled
tft                      https://platformio.org/lib/search?query=keyword%3Atft
control                  https://platformio.org/lib/search?query=keyword%3Acontrol
device                   https://platformio.org/lib/search?query=keyword%3Adevice
glcd                     https://platformio.org/lib/search?query=keyword%3Aglcd
displaycore              https://platformio.org/lib/search?query=keyword%3Adisplaycore
font                     https://platformio.org/lib/search?query=keyword%3Afont
other                    https://platformio.org/lib/search?query=keyword%3Aother
i2c                      https://platformio.org/lib/search?query=keyword%3Ai2c
input                    https://platformio.org/lib/search?query=keyword%3Ainput
signal                   https://platformio.org/lib/search?query=keyword%3Asignal
sensor                   https://platformio.org/lib/search?query=keyword%3Asensor
output                   https://platformio.org/lib/search?query=keyword%3Aoutput
spi                      https://platformio.org/lib/search?query=keyword%3Aspi
data                     https://platformio.org/lib/search?query=keyword%3Adata
timing                   https://platformio.org/lib/search?query=keyword%3Atiming
serial                   https://platformio.org/lib/search?query=keyword%3Aserial
temperature              https://platformio.org/lib/search?query=keyword%3Atemperature
http                     https://platformio.org/lib/search?query=keyword%3Ahttp
wifi                     https://platformio.org/lib/search?query=keyword%3Awifi
rf                       https://platformio.org/lib/search?query=keyword%3Arf
i2cdevlib                https://platformio.org/lib/search?query=keyword%3Ai2cdevlib
processing               https://platformio.org/lib/search?query=keyword%3Aprocessing
storage                  https://platformio.org/lib/search?query=keyword%3Astorage
radio                    https://platformio.org/lib/search?query=keyword%3Aradio
web                      https://platformio.org/lib/search?query=keyword%3Aweb
accelerometer            https://platformio.org/lib/search?query=keyword%3Aaccelerometer
wireless                 https://platformio.org/lib/search?query=keyword%3Awireless
protocol                 https://platformio.org/lib/search?query=keyword%3Aprotocol
server                   https://platformio.org/lib/search?query=keyword%3Aserver
wi-fi                    https://platformio.org/lib/search?query=keyword%3Awi-fi
ethernet                 https://platformio.org/lib/search?query=keyword%3Aethernet
mbed                     https://platformio.org/lib/search?query=keyword%3Ambed
openag                   https://platformio.org/lib/search?query=keyword%3Aopenag
led                      https://platformio.org/lib/search?query=keyword%3Aled
esp8266                  https://platformio.org/lib/search?query=keyword%3Aesp8266
humidity                 https://platformio.org/lib/search?query=keyword%3Ahumidity
time                     https://platformio.org/lib/search?query=keyword%3Atime
iot                      https://platformio.org/lib/search?query=keyword%3Aiot
json                     https://platformio.org/lib/search?query=keyword%3Ajson
timer                    https://platformio.org/lib/search?query=keyword%3Atimer
client                   https://platformio.org/lib/search?query=keyword%3Aclient
driver                   https://platformio.org/lib/search?query=keyword%3Adriver
button                   https://platformio.org/lib/search?query=keyword%3Abutton
mbed-official            https://platformio.org/lib/search?query=keyword%3Ambed-official
FEATURED: TODAY
***************
Name                     Url
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PubSubClient             https://platformio.org/lib/show/89/PubSubClient
Adafruit Unified Sensor  https://platformio.org/lib/show/31/Adafruit%20Unified%20Sensor
DHT sensor library       https://platformio.org/lib/show/19/DHT%20sensor%20library
ESPAsyncUDP              https://platformio.org/lib/show/359/ESPAsyncUDP
NtpClientLib             https://platformio.org/lib/show/727/NtpClientLib
Embedis                  https://platformio.org/lib/show/408/Embedis
Blynk                    https://platformio.org/lib/show/415/Blynk
SimpleTimer              https://platformio.org/lib/show/419/SimpleTimer
Adafruit DHT Unified     https://platformio.org/lib/show/18/Adafruit%20DHT%20Unified
RTClib                   https://platformio.org/lib/show/83/RTClib
FEATURED: WEEK
**************
Name                     Url
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
DHT sensor library       https://platformio.org/lib/show/19/DHT%20sensor%20library
Adafruit Unified Sensor  https://platformio.org/lib/show/31/Adafruit%20Unified%20Sensor
Blynk                    https://platformio.org/lib/show/415/Blynk
ESPAsyncWebServer        https://platformio.org/lib/show/306/ESPAsyncWebServer
Adafruit GFX Library     https://platformio.org/lib/show/13/Adafruit%20GFX%20Library
I2Cdevlib-Core           https://platformio.org/lib/show/11/I2Cdevlib-Core
TimeAlarms               https://platformio.org/lib/show/68/TimeAlarms
PubSubClient             https://platformio.org/lib/show/89/PubSubClient
Timer                    https://platformio.org/lib/show/75/Timer
esp8266_mdns             https://platformio.org/lib/show/1091/esp8266_mdns
FEATURED: MONTH
***************
Name                     Url
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ArduinoJson              https://platformio.org/lib/show/64/ArduinoJson
DHT sensor library       https://platformio.org/lib/show/19/DHT%20sensor%20library
Adafruit Unified Sensor  https://platformio.org/lib/show/31/Adafruit%20Unified%20Sensor
PubSubClient             https://platformio.org/lib/show/89/PubSubClient
OneWire                  https://platformio.org/lib/show/1/OneWire
ESPAsyncTCP              https://platformio.org/lib/show/305/ESPAsyncTCP
Time                     https://platformio.org/lib/show/44/Time
DallasTemperature        https://platformio.org/lib/show/54/DallasTemperature
ESPAsyncWebServer        https://platformio.org/lib/show/306/ESPAsyncWebServer
WifiManager              https://platformio.org/lib/show/567/WifiManager


•
platformio lib uninstall
  • Usage
  • Description
  • Storage Options
  • Examples


platformio lib [STORAGE_OPTIONS] uninstall [LIBRARY...]
pio lib [STORAGE_OPTIONS] uninstall [LIBRARY...]
# uninstall project dependent library
# (run it from a project root where is located "platformio.ini")
platformio lib uninstall [LIBRARY...]
# uninstall library from global storage
platformio lib --global uninstall [LIBRARY...]
platformio lib -g uninstall [LIBRARY...]
# uninstall library from custom storage
platformio lib --storage-dir /path/to/dir uninstall [LIBRARY...]
platformio lib -d /path/to/dir uninstall [LIBRARY...]
# [LIBRARY...] forms
platformio lib [STORAGE_OPTIONS] uninstall <id>
platformio lib [STORAGE_OPTIONS] uninstall <id>@<version>
platformio lib [STORAGE_OPTIONS] uninstall <id>@<version range>
platformio lib [STORAGE_OPTIONS] uninstall <name>
platformio lib [STORAGE_OPTIONS] uninstall <name>@<version>
platformio lib [STORAGE_OPTIONS] uninstall <name>@<version range>


Uninstall specified library

The version supports Semantic Versioning ( <major>.<minor>.<patch>) and can take any of the following forms:

  • 1.2.3 - an exact version number. Use only this exact version
  • ^1.2.3 - any compatible version (exact version for 1.x.x versions)
  • ~1.2.3 - any version with the same major and minor versions, and an equal or greater patch version
  • >1.2.3 - any version greater than 1.2.3. >=, <, and <= are also possible
  • >0.1.0,!=0.2.0,<0.3.0 - any version greater than 0.1.0, not equal to 0.2.0 and less than 0.3.0

Storage Options

See base options for Library Manager CLI.

> platformio lib -g uninstall AsyncMqttClient
Library Storage: /storage/dir/...
Uninstalling AsyncMqttClient @ 0.2.0:   [OK]


•
platformio lib update
  • Usage
  • Description
  • Storage Options
  • Options
  • Examples


platformio lib [STORAGE_OPTIONS] update [OPTIONS]
pio lib [STORAGE_OPTIONS] update [OPTIONS]
# update all project libraries
# (run it from a project root where is located "platformio.ini")
platformio lib update [OPTIONS]
# update project dependent library
platformio lib [STORAGE_OPTIONS] update [OPTIONS] [LIBRARY...]
# update library in global storage
platformio lib --global update [OPTIONS] [LIBRARY...]
platformio lib -g update [OPTIONS] [LIBRARY...]
# update library in custom storage
platformio lib --storage-dir /path/to/dir update [OPTIONS] [LIBRARY...]
platformio lib -d /path/to/dir update [OPTIONS] [LIBRARY...]
# [LIBRARY...] forms
platformio lib [STORAGE_OPTIONS] update <id>
platformio lib [STORAGE_OPTIONS] update <id>@<version>
platformio lib [STORAGE_OPTIONS] update <id>@<version range>
platformio lib [STORAGE_OPTIONS] update <name>
platformio lib [STORAGE_OPTIONS] update <name>@<version>
platformio lib [STORAGE_OPTIONS] update <name>@<version range>


Check or update installed libraries.

The version supports Semantic Versioning ( <major>.<minor>.<patch>) and can take any of the following forms:

  • 1.2.3 - an exact version number. Use only this exact version
  • ^1.2.3 - any compatible version (exact version for 1.x.x versions)
  • ~1.2.3 - any version with the same major and minor versions, and an equal or greater patch version
  • >1.2.3 - any version greater than 1.2.3. >=, <, and <= are also possible
  • >0.1.0,!=0.2.0,<0.3.0 - any version greater than 0.1.0, not equal to 0.2.0 and less than 0.3.0

Storage Options

See base options for Library Manager CLI.


DEPRECATED. Please use --dry-run instead.


Do not update, only check for the new versions


Return the output in JSON format

1.
Update all installed libraries in global storage

> platformio lib -g update
Library Storage: /storage/dir/...
Updating ESP8266_SSD1306 @ 3.2.3:   [Up-to-date]
Updating EngduinoMagnetometer @ 3.1.0:  [Up-to-date]
Updating IRremote @ 2.2.1:  [Up-to-date]
Updating Json @ 5.4.0:  [Out-of-date]
LibraryManager: Installing id=64 @ 5.6.4
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
Json @ 5.6.4 has been successfully installed!
Updating PJON @ 1fb26fd:    [Checking]
git version 2.7.4 (Apple Git-66)
Already up-to-date.
Updating TextLCD @ 308d188a2d3a:    [Checking]
Mercurial Distributed SCM (version 3.8.4)
(see https://mercurial-scm.org for more information)
Copyright (C) 2005-2016 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
pulling from https://developer.mbed.org/users/simon/code/TextLCD/
searching for changes
no changes found


2.
Update specified libraries in global storage

> platformio lib -g update Json 4
Library Storage: /storage/dir/...
Updating Json @ 5.6.4:  [Up-to-date]
Updating IRremote @ 2.2.1:  [Up-to-date]


To print all available commands and options use:

platformio project --help
platformio project COMMAND --help


•
platformio project config
  • Usage
  • Description
•
Options

•
Examples


platformio project config [OPTIONS]
pio project config [OPTIONS]


Show project computed configuration based on "platformio.ini" (Project Configuration File). The extra configuration files and dynamic variables will be expanded.

This command is useful for developers to check how PlatformIO computes configuration from "platformio.ini" (Project Configuration File).


Specify the path to project directory. By default, --project-dir is equal to current working directory (CWD).


Return the output in JSON format.

> pio platformio config
Computed project configuration for Tasmota Project
platformio
----------
src_dir          =  tasmota
build_dir        =  .pioenvs
build_cache_dir  =  .cache
extra_configs    =  platformio_tasmota_env.ini
                    platformio_override.ini
default_envs     =  tasmota
common
------
framework               =  arduino
board                   =  esp01_1m
board_build.flash_mode  =  dout
platform                =  espressif8266
build_flags             =  -D NDEBUG
                           -mtarget-align
                           -Wl,-Map,firmware.map
                           -Wl,-Teagle.flash.1m.ld
                           -DBEARSSL_SSL_BASIC
                           -DPIO_FRAMEWORK_ARDUINO_ESPRESSIF_SDK22x_190703
                           -DPIO_FRAMEWORK_ARDUINO_LWIP2_HIGHER_BANDWIDTH_LOW_FLASH
                           -DVTABLES_IN_FLASH
                           -fno-exceptions
                           -lstdc++
build_unflags           =  -Wall
board_build.f_cpu       =  80000000L
monitor_speed           =  115200
upload_speed            =  115200
upload_resetmethod      =  nodemcu
upload_port             =  COM5
extra_scripts           =  pio/strip-floats.py
                           pio/name-firmware.py
scripts_defaults
----------------
extra_scripts  =  pio/strip-floats.py
                  pio/name-firmware.py
...


•
platformio project init
  • Usage
  • Description
  • Options
  • Examples


platformio project init [OPTIONS]
pio project init [OPTIONS]


Initialize a new PlatformIO based project or update existing with new data.

This command will create:

  • "platformio.ini" (Project Configuration File)
  • include_dir, put project header files here
  • src_dir, put project source files here (*.h, *.c, *.cpp, *.S, *.ino, etc.)
  • lib_dir, put project specific (private) libraries here. See also Library Dependency Finder (LDF)
  • test_dir, put project tests here. More details PIO Unit Testing
  • Miscellaneous files for VCS and Continuous Integration support.


A path to a directory where PlatformIO will initialize new project.


If you specify board ID (you can pass multiple --board options), then PlatformIO will automatically generate environment for "platformio.ini" (Project Configuration File) and pre-fill these data:

  • platform
  • framework
  • board

The full list with pre-configured boards is available here Development Platforms.


Initialize PlatformIO project for the specified IDE which can be imported later via "Import Project" functionality.

A list with supported IDE is available within platformio project init --help command. Also, please take a look at Cloud & Desktop IDE page.


Initialize project with additional options from "platformio.ini" (Project Configuration File). For example, platformio project init --project-option="lib_deps=ArduinoJSON". Multiple options are allowed.


An environment prefix which will be used with pair in board ID. For example, the default environment name for Teensy 3.1 / 3.2 board will be [env:teensy31].


Suppress progress reporting

1.
Initialize new project in a current working directory

> platformio project init
The current working directory *** will be used for the new project.
You can specify another project directory via
`platformio project init -d %PATH_TO_THE_PROJECT_DIR%` command.
The next files/directories will be created in ***
platformio.ini - Project Configuration File. |-> PLEASE EDIT ME <-|
src - Put your source files here
lib - Put here project specific (private) libraries
Project has been successfully initialized!
Useful commands:
`platformio run` - process/build project from the current directory
`platformio run --target upload` or `platformio run -t upload` - upload firmware to embedded board
`platformio run --target clean` - clean project (remove compiled files)


2.
Initialize new project in a specified directory

> platformio project init -d %PATH_TO_DIR%
The next files/directories will be created in ***
 platformio.ini - Project Configuration File. |-> PLEASE EDIT ME <-|
...


3.
Initialize project for Arduino Uno

> platformio project init --board uno
The current working directory *** will be used for the new project.
You can specify another project directory via
`platformio project init -d %PATH_TO_THE_PROJECT_DIR%` command.
...


4.
Initialize project for Teensy 3.1 board with custom Mbed

> platformio project init --board teensy31 --project-option "framework=mbed"
The current working directory *** will be used for the new project.
You can specify another project directory via
`platformio project init -d %PATH_TO_THE_PROJECT_DIR%` command.
...


To print all available commands and options use:

platformio platform --help
platformio platform COMMAND --help


[image]

•
platformio platform frameworks
  • Usage
  • Description
•
Options

•
Examples


platformio platform frameworks QUERY [OPTIONS]
pio platform frameworks QUERY [OPTIONS]


List supported Frameworks (SDKs, etc).


Return the output in JSON format

Print all supported frameworks, SDKs, etc.

> platformio platform frameworks
arduino ~ 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.
Home: https://platformio.org/frameworks/arduino
artik-sdk ~ ARTIK SDK
=====================
ARTIK SDK is a C/C++ SDK targeting Samsung ARTIK platforms. It exposes a set of APIs to ease up development of applications. These APIs cover hardware buses such as GPIO, SPI, I2C, UART, connectivity links like Wi-Fi, Bluetooth, Zigbee, and network protocols such as HTTP, Websockets, MQTT, and others.
Home: https://platformio.org/frameworks/artik-sdk
cmsis ~ 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.
Home: https://platformio.org/frameworks/cmsis
espidf ~ ESP-IDF
================
Espressif IoT Development Framework. Official development framework for ESP32.
Home: https://platformio.org/frameworks/espidf
libopencm3 ~ 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.
Home: https://platformio.org/frameworks/libopencm3
mbed ~ 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.
Home: https://platformio.org/frameworks/mbed
pumbaa ~ Pumbaa
===============
Pumbaa is Python on top of Simba. The implementation is a port of MicroPython, designed for embedded devices with limited amount of RAM and code memory.
Home: https://platformio.org/frameworks/pumbaa
simba ~ Simba
=============
Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
Home: https://platformio.org/frameworks/simba
spl ~ 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.
Home: https://platformio.org/frameworks/spl
wiringpi ~ 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.
Home: https://platformio.org/frameworks/wiringpi


•
platformio platform install
  • Usage
  • Options
  • Description
  • Version control
  • Git
  • Mercurial
  • Subversion

•
Examples


platformio platform install [OPTIONS] [PLATFORM...]
pio platform install [OPTIONS] [PLATFORM...]
# [PLATFORM...] forms
platformio platform install <name>
platformio platform install <name>@<version>
platformio platform install <name>@<version range>
platformio platform install <zip or tarball url>
platformio platform install file://<zip or tarball file>
platformio platform install file://<folder>
platformio platform install <repository>
platformio platform install <name=repository> (name it should have locally)
platformio platform install <repository#tag> ("tag" can be commit, branch or tag)



Install specified package (or alias)


Do not install specified package (or alias)


Skip default packages


Install all declared packages in platform.json


Reinstall/redownload development platform and its packages if they exist

Install Development Platforms and dependent packages.

The version supports Semantic Versioning ( <major>.<minor>.<patch>) and can take any of the following forms:

  • 1.2.3 - an exact version number. Use only this exact version
  • ^1.2.3 - any compatible version (exact version for 1.x.x versions)
  • ~1.2.3 - any version with the same major and minor versions, and an equal or greater patch version
  • >1.2.3 - any version greater than 1.2.3. >=, <, and <= are also possible
  • >0.1.0,!=0.2.0,<0.3.0 - any version greater than 0.1.0, not equal to 0.2.0 and less than 0.3.0

Also, PlatformIO supports installing from local directory or archive. Need to use file:// prefix before local path. Also, directory or archive should contain platform.json manifest.

  • file:///local/path/to/the/platform/dir
  • file:///local/path/to/the/platform.zip
  • file:///local/path/to/the/platform.tar.gz

Version control

PlatformIO supports installing from Git, Mercurial and Subversion, and detects the type of VCS using url prefixes: "git+", "hg+", or "svn+".

NOTE:

PlatformIO requires a working VCS command on your path: git, hg or svn.


The supported schemes are: git, git+https and git+ssh. Here are the supported forms:

  • platformio/platform-NAME (short version for GitHub repository)
  • https://github.com/platformio/platform-NAME.git
  • git+git://git.server.org/my-platform
  • git+https://git.server.org/my-platform
  • git+ssh://git.server.org/my-platform
  • git+ssh://user@git.server.org/my-platform
  • [user@]host.xz:path/to/repo.git

Passing branch names, a commit hash or a tag name is possible like so:

  • https://github.com/platformio/platform-name.git#master
  • git+git://git.server.org/my-platform#master
  • git+https://git.server.org/my-platform#v1.0
  • git+ssh://git.server.org/my-platform#7846d8ad52f983f2f2887bdc0f073fe9755a806d

The supported schemes are: hg+http, hg+https and hg+ssh. Here are the supported forms:

  • hg+hg://hg.server.org/my-platform
  • hg+https://hg.server.org/my-platform
  • hg+ssh://hg.server.org/my-platform

Passing branch names, a commit hash or a tag name is possible like so:

  • hg+hg://hg.server.org/my-platform#master
  • hg+https://hg.server.org/my-platform#v1.0
  • hg+ssh://hg.server.org/my-platform#4cfe2fa00668

The supported schemes are: svn, svn+svn, svn+http, svn+https and svn+ssh. Here are the supported forms:

  • svn+svn://svn.server.org/my-platform
  • svn+https://svn.server.org/my-platform
  • svn+ssh://svn.server.org/my-platform

You can also give specific revisions to an SVN URL, like so:

•
svn+svn://svn.server.org/my-platform#13

1.
Install Atmel AVR with default packages

> platformio platform install atmelavr
PlatformManager: Installing atmelavr
Downloading...
Unpacking  [####################################]  100%
atmelavr @ 0.0.0 has been successfully installed!
PackageManager: Installing tool-scons @ >=2.3.0,<2.6.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
tool-scons @ 2.4.1 has been successfully installed!
PackageManager: Installing toolchain-atmelavr @ ~1.40801.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
toolchain-atmelavr @ 1.40801.0 has been successfully installed!
The platform 'atmelavr' has been successfully installed!
The rest of packages will be installed automatically depending on your build environment.


2.
Install Atmel AVR with uploader utility only and skip default packages

> platformio platform install atmelavr --skip-default-package --with-package=uploader
PlatformManager: Installing atmelavr
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
atmelavr @ 0.0.0 has been successfully installed!
PackageManager: Installing tool-micronucleus @ ~1.200.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
tool-micronucleus @ 1.200.0 has been successfully installed!
PackageManager: Installing tool-avrdude @ ~1.60001.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
tool-avrdude @ 1.60001.1 has been successfully installed!
The platform 'atmelavr' has been successfully installed!
The rest of packages will be installed automatically depending on your build environment.


3.
Install the latest development Atmel AVR from Git repository

> platformio platform install https://github.com/platformio/platform-atmelavr.git
PlatformManager: Installing platform-atmelavr
git version 2.7.4 (Apple Git-66)
Cloning into '/Volumes/MEDIA/tmp/pio3_test_projects/arduino-digihead-master/home_dir/platforms/installing-U3ucN0-package'...
remote: Counting objects: 176, done.
remote: Compressing objects: 100% (55/55), done.
remote: Total 176 (delta 114), reused 164 (delta 109), pack-reused 0
Receiving objects: 100% (176/176), 38.86 KiB | 0 bytes/s, done.
Resolving deltas: 100% (114/114), done.
Checking connectivity... done.
Submodule 'examples/arduino-external-libs/lib/OneWire' (https://github.com/PaulStoffregen/OneWire.git) registered for path 'examples/arduino-external-libs/lib/OneWire'
Cloning into 'examples/arduino-external-libs/lib/OneWire'...
remote: Counting objects: 91, done.
remote: Total 91 (delta 0), reused 0 (delta 0), pack-reused 91
Unpacking objects: 100% (91/91), done.
Checking connectivity... done.
Submodule path 'examples/arduino-external-libs/lib/OneWire': checked out '57c18c6de80c13429275f70875c7c341f1719201'
atmelavr @ 0.0.0 has been successfully installed!
PackageManager: Installing tool-scons @ >=2.3.0,<2.6.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
tool-scons @ 2.4.1 has been successfully installed!
PackageManager: Installing toolchain-atmelavr @ ~1.40801.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
toolchain-atmelavr @ 1.40801.0 has been successfully installed!
The platform 'https://github.com/platformio/platform-atmelavr.git' has been successfully installed!
The rest of packages will be installed automatically depending on your build environment.


•
platformio platform list
  • Usage
  • Description
•
Options

•
Examples


platformio platform list [OPTIONS]
pio platform list [OPTIONS]


List installed Development Platforms


Return the output in JSON format.

> platformio platform list
atmelavr ~ Atmel AVR
====================
Atmel AVR 8- and 32-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industrys most code-efficient architecture for C and assembly programming.
Home: https://platformio.org/platforms/atmelavr
Packages: toolchain-atmelavr, framework-simba
Version: 0.0.0
atmelsam ~ Atmel SAM
====================
Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Home: https://platformio.org/platforms/atmelsam
Packages: framework-arduinosam, framework-mbed, framework-simba, toolchain-gccarmnoneeabi, tool-bossac
Version: 0.0.0
espressif8266 ~ Espressif 8266
==============================
Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Home: https://platformio.org/platforms/espressif8266
Packages: framework-simba, tool-esptool, framework-arduinoespressif8266, sdk-esp8266, toolchain-xtensa
Version: 0.0.0
...


•
platformio platform search
  • Usage
  • Description
•
Options

•
Examples


platformio platform search QUERY [OPTIONS]
pio platform search QUERY [OPTIONS]


Search for development Development Platforms


Return the output in JSON format

1.
Print all available development platforms

> platformio platform search
atmelavr ~ Atmel AVR
====================
Atmel AVR 8- and 32-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industrys most code-efficient architecture for C and assembly programming.
Home: https://platformio.org/platforms/atmelavr
Packages: toolchain-atmelavr, framework-arduinoavr, framework-simba, tool-avrdude, tool-micronucleus
atmelsam ~ Atmel SAM
====================
Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Home: https://platformio.org/platforms/atmelsam
Packages: toolchain-gccarmnoneeabi, framework-arduinosam, framework-simba, tool-openocd, framework-mbed, tool-avrdude, tool-bossac
espressif32 ~ Espressif 32
==========================
Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Home: https://platformio.org/platforms/espressif32
Packages: toolchain-xtensa32, framework-simba, framework-arduinoespressif32, framework-pumbaa, framework-espidf, tool-esptoolpy
espressif8266 ~ Espressif 8266
==============================
Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Home: https://platformio.org/platforms/espressif8266
Packages: toolchain-xtensa, framework-simba, tool-esptool, tool-mkspiffs, tool-espotapy, framework-arduinoespressif8266, sdk-esp8266
freescalekinetis ~ Freescale Kinetis
====================================
Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.
...


2.
Search for TI development platforms

> platformio platform search texas
timsp430 ~ TI MSP430
====================
MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.
Home: https://platformio.org/platforms/timsp430
Packages: toolchain-timsp430, tool-mspdebug, framework-energiamsp430, framework-arduinomsp430
titiva ~ TI TIVA
================
Texas Instruments TM4C12x MCUs offer the industrys most popular ARM Cortex-M4 core with scalable memory and package options, unparalleled connectivity peripherals, advanced application functions, industry-leading analog integration, and extensive software solutions.
Home: https://platformio.org/platforms/titiva
Packages: ldscripts, framework-libopencm3, toolchain-gccarmnoneeabi, tool-lm4flash, framework-energiativa



> platformio platform search framework-mbed
atmelsam ~ Atmel SAM
====================
Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Home: https://platformio.org/platforms/atmelsam
Packages: toolchain-gccarmnoneeabi, framework-arduinosam, framework-simba, tool-openocd, framework-mbed, ldscripts, tool-bossac
freescalekinetis ~ Freescale Kinetis
====================================
Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.
Home: https://platformio.org/platforms/freescalekinetis
Packages: framework-mbed, toolchain-gccarmnoneeabi
nordicnrf51 ~ Nordic nRF51
==========================
The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.
Home: https://platformio.org/platforms/nordicnrf51
Packages: framework-mbed, tool-rfdloader, toolchain-gccarmnoneeabi, framework-arduinonordicnrf51
nxplpc ~ NXP LPC
================
The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.
Home: https://platformio.org/platforms/nxplpc
Packages: framework-mbed, toolchain-gccarmnoneeabi
siliconlabsefm32 ~ Silicon Labs EFM32
=====================================
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.
Home: https://platformio.org/platforms/siliconlabsefm32
Packages: framework-mbed, toolchain-gccarmnoneeabi
ststm32 ~ ST STM32
==================
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.
Home: https://platformio.org/platforms/ststm32
Packages: framework-libopencm3, toolchain-gccarmnoneeabi, tool-stlink, framework-spl, framework-cmsis, framework-mbed, ldscripts
teensy ~ Teensy
===============
Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.
Home: https://platformio.org/platforms/teensy
Packages: framework-arduinoteensy, tool-teensy, toolchain-gccarmnoneeabi, framework-mbed, toolchain-atmelavr, ldscripts
...


•
platformio platform show
  • Usage
  • Description
  • Examples


platformio platform show PLATFORM
pio platform show PLATFORM


Show details about Development Platforms

> platformio platform show atmelavr
atmelavr ~ Atmel AVR
====================
Atmel AVR 8- and 32-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industrys most code-efficient architecture for C and assembly programming.
Version: 1.2.1
Home: https://platformio.org/platforms/atmelavr
License: Apache-2.0
Frameworks: simba, arduino
Package toolchain-atmelavr
--------------------------
Type: toolchain
Requirements: ~1.40902.0
Installed: Yes
Description: avr-gcc
Url: http://www.atmel.com/products/microcontrollers/avr/32-bitavruc3.aspx?tab=tools
Version: 1.40902.0 (4.9.2)
Package framework-arduinoavr
----------------------------
Type: framework
Requirements: ~1.10612.1
Installed: Yes
Url: https://www.arduino.cc/en/Main/Software
Version: 1.10612.1 (1.6.12)
Description: Arduino Wiring-based Framework (AVR Core, 1.6)
Package framework-simba
-----------------------
Type: framework
Requirements: >=7.0.0
Installed: Yes
Url: https://github.com/eerimoq/simba
Version: 11.0.0
Description: Simba Embedded Programming Platform
Package tool-avrdude
--------------------
Type: uploader
Requirements: ~1.60300.0
Installed: Yes
Description: AVRDUDE
Url: http://www.nongnu.org/avrdude/
Version: 1.60300.0 (6.3.0)
Package tool-micronucleus
-------------------------
Type: uploader
Requirements: ~1.200.0
Installed: No (optional)


•
platformio platform uninstall
  • Usage
  • Description
  • Examples


platformio platform uninstall [PLATFORM...]
pio platform uninstall [PLATFORM...]
# uninstall specific platform version using Semantic Versioning
platformio platform uninstall PLATFORM@X.Y.Z


Uninstall specified Development Platforms

> platformio platform uninstall atmelavr
Uninstalling platform atmelavr @ 0.0.0:    [OK]
Uninstalling package tool-scons @ 2.4.1:    [OK]
Uninstalling package toolchain-atmelavr @ 1.40801.0:    [OK]
The platform 'atmelavr' has been successfully uninstalled!


•
platformio platform update
  • Usage
  • Description
  • Options
  • Examples


platformio platform update [OPTIONS] [PLATFORM...]
pio platform update [OPTIONS] [PLATFORM...]
# update specific platform version using Semantic Versioning
platformio platform update PLATFORM@X.Y.Z


Check or update installed Development Platforms


Update only the platform related packages. Do not update development platform build scripts, board configs and etc.


DEPRECATED. Please use --dry-run instead.


Do not update, only check for the new versions


Return the output in JSON format

> platformio platform update
Platform atmelavr
--------
Updating atmelavr @ 0.0.0:  [Up-to-date]
Updating framework-arduinoavr @ 1.10608.1:  [Up-to-date]
Updating tool-avrdude @ 1.60001.1:  [Up-to-date]
Updating toolchain-atmelavr @ 1.40801.0:    [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform espressif8266
--------
Updating espressif @ 0.0.0:     [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Updating toolchain-xtensa @ 1.40802.0:  [Up-to-date]
Updating tool-esptool @ 1.409.0:    [Up-to-date]
Updating tool-mkspiffs @ 1.102.0:   [Up-to-date]
Updating framework-arduinoespressif8266 @ 1.20300.0:    [Up-to-date]
Updating sdk-esp8266 @ 1.10502.0:   [Up-to-date]
Platform teensy
--------
Updating teensy @ 0.0.0:    [Up-to-date]
Updating framework-arduinoteensy @ 1.128.0:     [Up-to-date]
Updating tool-teensy @ 1.1.0:   [Up-to-date]
Updating framework-mbed @ 1.121.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Updating toolchain-atmelavr @ 1.40801.0:    [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
...


Helper command for PIO Remote.

To print all available commands and options use:

pio remote --help
platformio remote --help
platformio remote COMMAND --help
# run command on the specified PIO Remote Agents
platformio remote --agent NAME_1 --agent NAME_N COMMAND


Start PIO Remote Agent on a host machine and work remotely with your devices WITHOUT extra software, services, SSH, VPN, tunneling or opening incoming network ports.

PIO Remote supports wired and wireless devices. Wired devices should be connected physically to host machine where PIO Remote Agent is started, where wireless devices should be visible for PIO Remote Agent to provide network operations Over-The-Air (OTA).

•
PIO Remote Agent
•
platformio remote agent list
  • Usage
  • Description
  • Example

•
platformio remote agent start
  • Usage
  • Description
  • Options



platformio remote agent list
pio remote agent list


List active PIO Remote Agent s started using own PIO Account or shared with you by other PlatformIO developers.

> platformio remote agent list
innomac.local
-------------
ID: 98853d930......788d77375e7
Started: 2016-10-26 16:32:56



----



platformio remote agent start [OPTIONS]
pio remote agent start [OPTIONS]


Start PIO Remote Agent and work remotely with your devices from anywhere in the world. This command can be run as daemon or added to autostart list of your OS.


Agent name/alias. By default, machine's hostname will be used. You can use this name later for platformio remote device and platformio remote run commands. Good names are home, office, lab or etc.


Share your agent/devices with other PlatformIO developers who have PIO Account: friends, co-workers, team, etc.

The valid value for --share option is email address that was used for platformio account register command.


A working directory where PIO Remote Agent stores projects data for incremental synchronization and embedded programs for PIO Process Supervisor.

Remote Device: monitor remote device or list existing.

•
platformio remote device
•
platformio remote device list
  • Usage
  • Description
  • Options
  • Example

•
platformio remote device monitor
  • Usage
  • Description
  • Options
  • Examples



platformio remote device list [OPTIONS]
pio remote device list [OPTIONS]
# List devices from the specified agents. Multiple agents are allowed.
platformio remote --agent NAME device list [OPTIONS]


List Serial Ports on remote machines where PIO Remote Agent is started.

You can list devices from the specified remote machines using --agent NAME option between "remote" & "device" sub-commands. For example, you have run platformio remote agent start --name command with "home" and "office" options:

  • platformio remote agent start --name home
  • platformio remote agent start --name office

Now, to list devices from office machine please use platformio remote --agent office device list.

Multiple agents are allowed ( platformio remote --agent lab1 --agent lab3 device ...).


Return the output in JSON format

> platformio remote device list
Agent innomac.local
===================
/dev/cu.Bluetooth-Incoming-Port
-------------------------------
Hardware ID: n/a
Description: n/a
/dev/cu.obd2ecu-SPPDev
----------------------
Hardware ID: n/a
Description: n/a
/dev/cu.usbmodemFA1431
----------------------
Hardware ID: USB VID:PID=2A03:0043 SER=75435353038351015271 LOCATION=250-1.4.3
Description: Arduino Uno
/dev/cu.usbserial-A6004003
--------------------------
Hardware ID: USB VID:PID=0403:6001 SER=A6004003 LOCATION=253-1.3.1
Description: FT232R USB UART - FT232R USB UART
/dev/cu.SLAB_USBtoUART
----------------------
Hardware ID: USB VID:PID=10C4:EA60 SER=0001 LOCATION=253-1.3.2
Description: CP2102 USB to UART Bridge Controller - CP2102 USB to UART Bridge Controller
/dev/cu.usbmodem589561
----------------------
Hardware ID: USB VID:PID=16C0:0483 SER=589560 LOCATION=250-1.4.1
Description: USB Serial


Remote Serial Port Monitor

platformio remote device monitor [OPTIONS]
pio remote device monitor [OPTIONS]
# Connect to a specified agent
platformio remote --agent NAME device monitor [OPTIONS]
platformio remote -a NAME device monitor [OPTIONS]


Connect to Serial Port of remote device and receive or send data in real time. PIO Remote Agent should be started before on a remote machine.

To control monitor please use these "hot keys":

  • Ctrl+C Quit
  • Ctrl+T Menu
  • Ctrl+T followed by Ctrl+H Help


Port, a number or a device name


Set baud rate, default 9600


Set parity (None, Even, Odd, Space, Mark), one of [N, E, O, S, M], default N


Enable RTS/CTS flow control, default Off


Enable software flow control, default Off


Set initial RTS line state, default 0


Set initial DTR line state, default 0


Enable local echo, default Off


Set the encoding for the serial port (e.g. hexlify, Latin1, UTF-8), default UTF-8.


Add text transformation. Available filters:

  • colorize Apply different colors for received and echo
  • debug Print what is sent and received
  • default Remove typical terminal control codes from input
  • direct Do-nothing: forward all data unchanged
  • nocontrol Remove all control codes, incl. CR+LF
  • printable Show decimal code for all non-ASCII characters and replace most control codes


End of line mode (CR, LF or CRLF), default CRLF


Do not apply any encodings/transformations


ASCII code of special character that is used to exit the application, default 3 (DEC, Ctrl+C).

For example, to use Ctrl+] run platformio remote device monitor --exit-char 29.


ASCII code of special character that is used to control miniterm (menu), default 20 (DEC)


Diagnostics: suppress non-error messages, default Off


Specify the path to project directory. By default, --project-dir is equal to current working directory (CWD).


Process specified environments.

You can also specify which environments should be processed by default using default_envs option from "platformio.ini" (Project Configuration File).

1.
Show available options for monitor

> platformio remote device monitor --help
Usage: platformio remote device monitor [OPTIONS]
Options:
  -p, --port TEXT       Port, a number or a device name
  -b, --baud INTEGER    Set baud rate, default=9600
  --parity [N|E|O|S|M]  Set parity, default=N
  --rtscts              Enable RTS/CTS flow control, default=Off
  --xonxoff             Enable software flow control, default=Off
  --rts [0|1]           Set initial RTS line state, default=0
  --dtr [0|1]           Set initial DTR line state, default=0
  --echo                Enable local echo, default=Off
  --encoding TEXT       Set the encoding for the serial port (e.g. hexlify,
                        Latin1, UTF-8), default: UTF-8
  -f, --filter TEXT     Add text transformation
  --eol [CR|LF|CRLF]    End of line mode, default=CRLF
  --raw                 Do not apply any encodings/transformations
  --exit-char INTEGER   ASCII code of special character that is used to exit
                        the application, default=29 (DEC)
  --menu-char INTEGER   ASCII code of special character that is used to
                        control miniterm (menu), default=20 (DEC)
  --quiet               Diagnostics: suppress non-error messages, default=Off
  -h, --help            Show this message and exit.


2.
Communicate with serial device and print help inside terminal

> platformio remote device monitor
--- Available ports:
--- /dev/cu.Bluetooth-Incoming-Port n/a
--- /dev/cu.Bluetooth-Modem n/a
--- /dev/cu.SLAB_USBtoUART CP2102 USB to UART Bridge Controller
--- /dev/cu.obd2ecu-SPPDev n/a
Enter port name:/dev/cu.SLAB_USBtoUART
--- Miniterm on /dev/cu.SLAB_USBtoUART: 9600,8,N,1 ---
--- Quit: Ctrl+C  |  Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
Hello PlatformIO!
---
--- Ctrl+]   Exit program
--- Ctrl+T   Menu escape key, followed by:
--- Menu keys:
---    Ctrl+T  Send the menu character itself to remote
---    Ctrl+]  Send the exit character itself to remote
---    Ctrl+I  Show info
---    Ctrl+U  Upload file (prompt will be shown)
--- Toggles:
---    Ctrl+R  RTS          Ctrl+E  local echo
---    Ctrl+D  DTR          Ctrl+B  BREAK
---    Ctrl+L  line feed    Ctrl+A  Cycle repr mode
---
--- Port settings (Ctrl+T followed by the following):
---    p          change port
---    7 8        set data bits
---    n e o s m  change parity (None, Even, Odd, Space, Mark)
---    1 2 3      set stop bits (1, 2, 1.5)
---    b          change baud rate
---    x X        disable/enable software flow control
---    r R        disable/enable hardware flow control
--- exit ---


Remote Firmware Updates

•
platformio remote run
  • Usage
  • Description
  • Options
  • Example


platformio remote run [OPTIONS]
pio remote run [OPTIONS]
# process environments using specified PIO Remote Agent
platformio remote --agent NAME run [OPTIONS]


Process remotely environments which are defined in "platformio.ini" (Project Configuration File) file. By default, PIO Remote builds project on a host machine and deploy final firmware (program) to a remote device (embedded board).

If you need to process project on a remote machine, please use platformio remote run --force-remote option. In this case, PIO Remote will automatically synchronize your project with remote machine, install required toolchains, frameworks, SDKs, etc., and process project.


Process specified environments.

You can also specify which environments should be processed by default using default_envs option from "platformio.ini" (Project Configuration File).


Process specified targets.

Built-in targets:

  • clean delete compiled object files, libraries and firmware/program binaries
  • upload firmware "auto-uploading" for embedded platforms
  • program firmware "auto-uploading" for embedded platforms using external programmer (available only for Atmel AVR)
  • buildfs Uploading files to file system SPIFFS
  • uploadfs Uploading files to file system SPIFFS
  • envdump dump current build environment
  • size print the size of the sections in a firmware/program


Custom upload port of embedded board. To print all available ports use platformio remote device command.

If upload port is not specified, PlatformIO will try to detect it automatically.


Specify the path to project directory. By default, --project-dir is equal to current working directory (CWD).


Shows detailed information when processing environments.

This option can also be set globally using force_verbose setting or by environment variable PLATFORMIO_SETTING_FORCE_VERBOSE.


Disable auto-clean of build_dir when "platformio.ini" (Project Configuration File) or src_dir (project structure) have been modified.


By default, PIO Remote builds project on a host machine and deploy final firmware (program) to remote device (embedded board).

If you need to process project on remote machine, please use platformio remote run --force-remote option. In this case, PIO Remote will automatically synchronize your project with remote machine, install required toolchains, frameworks, SDKs, etc., and process project.

> platformio remote run --environment uno --target upload
Building project locally
[Wed Oct 26 16:35:09 2016] Processing uno (platform: atmelavr, board: uno, framework: arduino)
--------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
Collected 25 compatible libraries
Looking for dependencies...
Project does not have dependencies
Compiling .pio/build/uno/src/main.o
Archiving .pio/build/uno/libFrameworkArduinoVariant.a
Indexing .pio/build/uno/libFrameworkArduinoVariant.a
Compiling .pio/build/uno/FrameworkArduino/CDC.o
Compiling .pio/build/uno/FrameworkArduino/HardwareSerial.o
Compiling .pio/build/uno/FrameworkArduino/HardwareSerial0.o
Compiling .pio/build/uno/FrameworkArduino/HardwareSerial1.o
Compiling .pio/build/uno/FrameworkArduino/HardwareSerial2.o
Compiling .pio/build/uno/FrameworkArduino/HardwareSerial3.o
Compiling .pio/build/uno/FrameworkArduino/IPAddress.o
Compiling .pio/build/uno/FrameworkArduino/PluggableUSB.o
Compiling .pio/build/uno/FrameworkArduino/Print.o
Compiling .pio/build/uno/FrameworkArduino/Stream.o
Compiling .pio/build/uno/FrameworkArduino/Tone.o
Compiling .pio/build/uno/FrameworkArduino/USBCore.o
Compiling .pio/build/uno/FrameworkArduino/WInterrupts.o
Compiling .pio/build/uno/FrameworkArduino/WMath.o
Compiling .pio/build/uno/FrameworkArduino/WString.o
Compiling .pio/build/uno/FrameworkArduino/_wiring_pulse.o
Compiling .pio/build/uno/FrameworkArduino/abi.o
Compiling .pio/build/uno/FrameworkArduino/hooks.o
Compiling .pio/build/uno/FrameworkArduino/main.o
Compiling .pio/build/uno/FrameworkArduino/new.o
Compiling .pio/build/uno/FrameworkArduino/wiring.o
Compiling .pio/build/uno/FrameworkArduino/wiring_analog.o
Compiling .pio/build/uno/FrameworkArduino/wiring_digital.o
Compiling .pio/build/uno/FrameworkArduino/wiring_pulse.o
Compiling .pio/build/uno/FrameworkArduino/wiring_shift.o
Archiving .pio/build/uno/libFrameworkArduino.a
Indexing .pio/build/uno/libFrameworkArduino.a
Linking .pio/build/uno/firmware.elf
Checking program size
Building .pio/build/uno/firmware.hex
text       data     bss     dec     hex filename
2574         48     168    2790     ae6 .pio/build/uno/firmware.elf
========================= [SUCCESS] Took 10.01 seconds =======================
================================== [SUMMARY] =================================
Environment nodemcuv2   [SKIP]
Environment uno_pic32   [SKIP]
Environment teensy31    [SKIP]
Environment uno         [SUCCESS]
========================= [SUCCESS] Took 10.01 seconds ========================
Uploading firmware remotely
[Wed Oct 26 19:35:20 2016] Processing uno (platform: atmelavr, board: uno, framework: arduino)
----------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
Looking for upload port...
Auto-detected: /dev/cu.usbmodemFA1431
Uploading .pio/build/uno/firmware.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
avrdude: Device signature = 0x1e950f
avrdude: reading input file ".pio/build/uno/firmware.hex"
avrdude: writing flash (2622 bytes):
Writing | ################################################## | 100% 0.43s
avrdude: 2622 bytes of flash written
avrdude: verifying flash memory against .pio/build/uno/firmware.hex:
avrdude: load data flash data from input file .pio/build/uno/firmware.hex:
avrdude: input file .pio/build/uno/firmware.hex contains 2622 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 0.34s
avrdude: verifying ...
avrdude: 2622 bytes of flash verified
avrdude done.  Thank you.
========================= [SUCCESS] Took 3.04 seconds =======================
========================= [SUMMARY] =========================================
Environment nodemcuv2   [SKIP]
Environment uno_pic32   [SKIP]
Environment teensy31    [SKIP]
Environment uno         [SUCCESS]
========================= [SUCCESS] Took 3.04 seconds ========================


Helper command for remote PIO Unit Testing.

•
platformio remote test
  • Usage
  • Description
  • Options
  • Examples


platformio remote test [OPTIONS]
pio remote test [OPTIONS]
# run tests on specified PIO Remote Agent
platformio remote --agent NAME test [OPTIONS]


Run remotely tests from PlatformIO based project. More details about PlatformIO PIO Unit Testing.

This command allows you to apply the tests for the environments specified in "platformio.ini" (Project Configuration File).


Process specified environments. More details platformio run --environment


Ignore tests where the name matches specified patterns. More than one pattern is allowed. If you need to ignore some tests for the specific environment, please take a look at test_ignore option from "platformio.ini" (Project Configuration File).

Pattern Meaning
* matches everything
? matches any single character
[seq] matches any character in seq
[!seq] matches any character not in seq

For example, platformio remote test --ignore "mytest*" -i "test[13]"


A port that is intended for firmware uploading. To list available ports please use platformio device list command.

If upload port is not specified, PlatformIO will try to detect it automatically.


A Serial/UART port that PlatformIO uses as communication interface between PlatformIO Unit Test Engine and target device. To list available ports please use platformio device list command.

If test port is not specified, PlatformIO will try to detect it automatically.


Specify the path to project directory. By default, --project-dir is equal to current working directory (CWD).


By default, PIO Remote processes project on a host machine and deploy final testing firmware (program) to remote device (embedded board).

If you need to process project on remote machine, please use platformio remote test --force-remote option. In this case, PIO Remote will automatically synchronize your project with remote machine, install required toolchains, frameworks, SDKs, etc., and process project.


Skip building stage.


Skip uploading stage


Shows detailed information when processing environments.

This option can also be set globally using force_verbose setting or by environment variable PLATFORMIO_SETTING_FORCE_VERBOSE.

For the examples please follow to PIO Unit Testing page.

•
platformio remote update
  • Usage
  • Description
  • Options
  • Examples


platformio remote update [OPTIONS]
pio remote update [OPTIONS]
# start update process on the specified agents/machines
platformio remote --agent NAME update [OPTIONS]


Check or update installed Development Platforms and global Libraries on the remote machine.


DEPRECATED. Please use --dry-run instead.


Do not update, only check for the new versions

> platformio remote update
Platform Manager
================
Platform timsp430
--------
Updating timsp430 @ 0.0.0:  [Up-to-date]
Updating toolchain-timsp430 @ 1.40603.0:    [Up-to-date]
Updating framework-energiamsp430 @ 1.17.0:  [Up-to-date]
Updating framework-arduinomsp430 @ 1.10601.0:   [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform freescalekinetis
--------
Updating freescalekinetis @ 0.0.0:  [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform ststm32
--------
Updating ststm32 @ 0.0.0:   [Up-to-date]
Updating framework-libopencm3 @ 1.1.0:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating tool-stlink @ 1.10200.0:   [Up-to-date]
Updating framework-spl @ 1.10201.0:     [Up-to-date]
Updating framework-cmsis @ 1.40300.0:   [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform lattice_ice40
--------
Updating lattice_ice40 @ 0.0.0:     [Up-to-date]
Updating toolchain-icestorm @ 1.7.0:    [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform atmelavr
--------
Updating atmelavr @ 0.0.0:  [Up-to-date]
Updating framework-arduinoavr @ 1.10608.1:  [Up-to-date]
Updating tool-avrdude @ 1.60001.1:  [Up-to-date]
Updating toolchain-atmelavr @ 1.40801.0:    [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform espressif8266
--------
Updating espressif8266 @ 0.0.0:     [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Updating toolchain-xtensa @ 1.40802.0:  [Up-to-date]
Updating tool-esptool @ 1.409.0:    [Up-to-date]
Updating tool-mkspiffs @ 1.102.0:   [Up-to-date]
Updating framework-arduinoespressif8266 @ 1.20300.0:    [Up-to-date]
Updating sdk-esp8266 @ 1.10502.0:   [Up-to-date]
Platform linux_x86_64
--------
Updating linux_x86_64 @ 0.0.0:  [Up-to-date]
Updating toolchain-gcclinux64 @ 1.40801.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform windows_x86
--------
Updating windows_x86 @ 0.0.0:   [Up-to-date]
Updating toolchain-gccmingw32 @ 1.40800.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform teensy
--------
Updating teensy @ 0.0.0:    [Up-to-date]
Updating framework-arduinoteensy @ 1.128.0:     [Up-to-date]
Updating tool-teensy @ 1.1.0:   [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Updating toolchain-atmelavr @ 1.40801.0:    [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Platform nordicnrf51
--------
Updating nordicnrf51 @ 0.0.0:   [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating framework-arduinonordicnrf51 @ 1.20302.0:  [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform titiva
--------
Updating titiva @ 0.0.0:    [Up-to-date]
Updating framework-libopencm3 @ 1.1.0:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating framework-energiativa @ 1.17.0:    [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform atmelsam
--------
Updating atmelsam @ 0.0.0:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating tool-openocd @ 1.900.0:    [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Updating tool-avrdude @ 1.60001.1:  [Up-to-date]
Updating tool-bossac @ 1.10601.0:   [Up-to-date]
Platform siliconlabsefm32
--------
Updating siliconlabsefm32 @ 0.0.0:  [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform microchippic32
--------
Updating microchippic32 @ 0.0.0:    [Up-to-date]
Updating framework-arduinomicrochippic32 @ 1.10201.0:   [Up-to-date]
Updating toolchain-microchippic32 @ 1.40803.0:  [Up-to-date]
Updating tool-pic32prog @ 1.200200.0:   [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform linux_i686
--------
Updating linux_i686 @ 0.0.0:    [Up-to-date]
Updating toolchain-gcclinux32 @ 1.40801.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform intel_arc32
--------
Updating intel_arc32 @ 0.0.0:   [Up-to-date]
Updating framework-arduinointel @ 1.10006.0:    [Up-to-date]
Updating tool-arduino101load @ 1.124.0:     [Up-to-date]
Updating toolchain-intelarc32 @ 1.40805.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform nxplpc
--------
Updating nxplpc @ 0.0.0:    [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform linux_arm
--------
Updating linux_arm @ 0.0.0:     [Up-to-date]
Updating toolchain-gccarmlinuxgnueabi @ 1.40802.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform native
--------
Updating native @ 0.0.0:    [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Library Manager
===============
Updating Adafruit-GFX @ 334e815bc1:     [Up-to-date]
Updating Adafruit-ST7735 @ d53d4bf03a:  [Up-to-date]
Updating Adafruit-DHT @ 09344416d2:     [Up-to-date]
Updating Adafruit-Unified-Sensor @ f2af6f4efc:  [Up-to-date]
Updating ESP8266_SSD1306 @ 3.2.3:   [Up-to-date]
Updating EngduinoMagnetometer @ 3.1.0:  [Up-to-date]
Updating IRremote @ 2.2.1:  [Up-to-date]
Updating Json @ 5.6.4:  [Up-to-date]
Updating MODSERIAL @ d8422efe47:    [Up-to-date]
Updating PJON @ 1fb26fd:    [Checking]
git version 2.7.4 (Apple Git-66)
Already up-to-date.
Updating Servo @ 36b69a7ced07:  [Checking]
Mercurial Distributed SCM (version 3.8.4)
(see https://mercurial-scm.org for more information)
Copyright (C) 2005-2016 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
pulling from https://developer.mbed.org/users/simon/code/Servo/
searching for changes
no changes found
Updating TextLCD @ 308d188a2d3a:    [Checking]
Mercurial Distributed SCM (version 3.8.4)
(see https://mercurial-scm.org for more information)
Copyright (C) 2005-2016 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
pulling from https://developer.mbed.org/users/simon/code/TextLCD/
searching for changes
no changes found


•
platformio run
  • Usage
  • Description
  • Options
  • Examples


platformio run [OPTIONS]
pio run [OPTIONS]


Process environments which are defined in "platformio.ini" (Project Configuration File) file


Process specified environments.

You can also specify which environments should be processed by default using default_envs option from "platformio.ini" (Project Configuration File).


Process specified targets.

NOTE:

You can configure default targets per project environment using targets option in "platformio.ini" (Project Configuration File).


Built-in targets:

•
Processing
  • clean delete compiled object files, libraries and firmware/program binaries
  • upload firmware "auto-uploading" for embedded platforms
  • debug build using Debug Configuration
  • program firmware "auto-uploading" for embedded platforms using external programmer (available only for Atmel AVR)
  • fuses set fuse bits (available only for Atmel AVR)
  • buildfs Uploading files to file system SPIFFS
  • uploadfs Uploading files to file system SPIFFS
  • size print the size of the sections in a firmware/program
  • checkprogsize check maximum allowed firmware size for uploading
  • erase erase device flash (not available on the all Development Platforms)
  • compiledb build Compilation database compile_commands.json



•
Device
•
monitor automatically start platformio device monitor after success build operation. You can configure monitor using Monitor options.



•
Service
  • envdump dump current build environment
  • idedata export build environment for IDE (defines, build flags, CPPPATH, etc.)





Custom upload port of embedded board. To print all available ports use platformio device list command.

If upload port is not specified, PlatformIO will try to detect it automatically.


Specify the path to project directory. By default, --project-dir is equal to current working directory (CWD).


New in version 4.0.

Process project with a custom "platformio.ini" (Project Configuration File).


New in version 4.0.

Control a number of parallel build jobs. Default is a number of CPUs in a system.


Suppress progress reporting


Shows detailed information when processing environments.

This option can also be set globally using force_verbose setting or by environment variable PLATFORMIO_SETTING_FORCE_VERBOSE.


Disable auto-clean of build_dir when "platformio.ini" (Project Configuration File) or src_dir (project structure) have been modified.

1.
Process Wiring Blink Example

> platformio run
[Wed Sep  7 15:48:58 2016] Processing uno (platform: atmelavr, board: uno, framework: arduino)
-----------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
Collected 36 compatible libraries
Looking for dependencies...
Project does not have dependencies
Compiling .pio/build/uno/src/main.o
Archiving .pio/build/uno/libFrameworkArduinoVariant.a
Indexing .pio/build/uno/libFrameworkArduinoVariant.a
Compiling .pio/build/uno/FrameworkArduino/CDC.o
...
Compiling .pio/build/uno/FrameworkArduino/wiring_shift.o
Archiving .pio/build/uno/libFrameworkArduino.a
Indexing .pio/build/uno/libFrameworkArduino.a
Linking .pio/build/uno/firmware.elf
Building .pio/build/uno/firmware.hex
Calculating size .pio/build/uno/firmware.elf
AVR Memory Usage
----------------
Device: atmega328p
Program:    1034 bytes (3.2% Full)
(.text + .data + .bootloader)
Data:          9 bytes (0.4% Full)
(.data + .bss + .noinit)
=========================== [SUCCESS] Took 2.47 seconds ===========================
[Wed Sep  7 15:49:01 2016] Processing nodemcu (platform: espressif8266, board: nodemcu, framework: arduino)
-----------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
Collected 34 compatible libraries
Looking for dependencies...
Project does not have dependencies
Compiling .pio/build/nodemcu/src/main.o
Archiving .pio/build/nodemcu/libFrameworkArduinoVariant.a
Indexing .pio/build/nodemcu/libFrameworkArduinoVariant.a
Compiling .pio/build/nodemcu/FrameworkArduino/Esp.o
Compiling .pio/build/nodemcu/FrameworkArduino/FS.o
Compiling .pio/build/nodemcu/FrameworkArduino/HardwareSerial.o
...
Archiving .pio/build/nodemcu/libFrameworkArduino.a
Indexing .pio/build/nodemcu/libFrameworkArduino.a
Linking .pio/build/nodemcu/firmware.elf
Calculating size .pio/build/nodemcu/firmware.elf
text       data     bss     dec     hex filename
221240      888   29400  251528   3d688 .pio/build/nodemcu/firmware.elf
Building .pio/build/nodemcu/firmware.bin
=========================== [SUCCESS] Took 6.43 seconds ===========================
[Wed Sep  7 15:49:07 2016] Processing teensy31 (platform: teensy, board: teensy31, framework: arduino)
-----------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
Collected 96 compatible libraries
Looking for dependencies...
Project does not have dependencies
Compiling .pio/build/teensy31/src/main.o
Compiling .pio/build/teensy31/FrameworkArduino/AudioStream.o
Compiling .pio/build/teensy31/FrameworkArduino/DMAChannel.o
...
Compiling .pio/build/teensy31/FrameworkArduino/yield.o
Archiving .pio/build/teensy31/libFrameworkArduino.a
Indexing .pio/build/teensy31/libFrameworkArduino.a
Linking .pio/build/teensy31/firmware.elf
Calculating size .pio/build/teensy31/firmware.elf
text       data     bss     dec     hex filename
11288       168    2288   13744    35b0 .pio/build/teensy31/firmware.elf
Building .pio/build/teensy31/firmware.hex
=========================== [SUCCESS] Took 5.36 seconds ===========================
[Wed Sep  7 15:49:12 2016] Processing lpmsp430g2553 (platform: timsp430, build_flags: -D LED_BUILTIN=RED_LED, board: lpmsp430g2553, framework: arduino)
-----------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
Collected 29 compatible libraries
Looking for dependencies...
Project does not have dependencies
Compiling .pio/build/lpmsp430g2553/src/main.o
Compiling .pio/build/lpmsp430g2553/FrameworkAnergia/HardwareSerial.o
Compiling .pio/build/lpmsp430g2553/FrameworkAnergia/IPAddress.o
...
Compiling .pio/build/lpmsp430g2553/FrameworkAnergia/wiring_digital.o
Compiling .pio/build/lpmsp430g2553/FrameworkAnergia/wiring_pulse.o
Compiling .pio/build/lpmsp430g2553/FrameworkAnergia/wiring_shift.o
Archiving .pio/build/lpmsp430g2553/libFrameworkAnergia.a
Indexing .pio/build/lpmsp430g2553/libFrameworkAnergia.a
Linking .pio/build/lpmsp430g2553/firmware.elf
Calculating size .pio/build/lpmsp430g2553/firmware.elf
text       data     bss     dec     hex filename
820           0      20     840     348 .pio/build/lpmsp430g2553/firmware.elf
Building .pio/build/lpmsp430g2553/firmware.hex
=========================== [SUCCESS] Took 2.34 seconds ===========================


2.
Process specific environment

> platformio run -e nodemcu -e teensy31
[Wed Sep  7 15:49:01 2016] Processing nodemcu (platform: espressif8266, board: nodemcu, framework: arduino)
-----------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
Collected 34 compatible libraries
Looking for dependencies...
Project does not have dependencies
Compiling .pio/build/nodemcu/src/main.o
Archiving .pio/build/nodemcu/libFrameworkArduinoVariant.a
Indexing .pio/build/nodemcu/libFrameworkArduinoVariant.a
Compiling .pio/build/nodemcu/FrameworkArduino/Esp.o
Compiling .pio/build/nodemcu/FrameworkArduino/FS.o
Compiling .pio/build/nodemcu/FrameworkArduino/HardwareSerial.o
...
Archiving .pio/build/nodemcu/libFrameworkArduino.a
Indexing .pio/build/nodemcu/libFrameworkArduino.a
Linking .pio/build/nodemcu/firmware.elf
Calculating size .pio/build/nodemcu/firmware.elf
text       data     bss     dec     hex filename
221240      888   29400  251528   3d688 .pio/build/nodemcu/firmware.elf
Building .pio/build/nodemcu/firmware.bin
=========================== [SUCCESS] Took 6.43 seconds ===========================
[Wed Sep  7 15:49:07 2016] Processing teensy31 (platform: teensy, board: teensy31, framework: arduino)
-----------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
Collected 96 compatible libraries
Looking for dependencies...
Project does not have dependencies
Compiling .pio/build/teensy31/src/main.o
Compiling .pio/build/teensy31/FrameworkArduino/AudioStream.o
Compiling .pio/build/teensy31/FrameworkArduino/DMAChannel.o
...
Compiling .pio/build/teensy31/FrameworkArduino/yield.o
Archiving .pio/build/teensy31/libFrameworkArduino.a
Indexing .pio/build/teensy31/libFrameworkArduino.a
Linking .pio/build/teensy31/firmware.elf
Calculating size .pio/build/teensy31/firmware.elf
text       data     bss     dec     hex filename
11288       168    2288   13744    35b0 .pio/build/teensy31/firmware.elf
Building .pio/build/teensy31/firmware.hex
=========================== [SUCCESS] Took 5.36 seconds ===========================


3.
Process specific target (clean project)

> platformio run -t clean
[Wed Sep  7 15:53:26 2016] Processing uno (platform: atmelavr, board: uno, framework: arduino)
-----------------------------------------------------------------------------------------------------
Removed .pio/build/uno/firmware.elf
Removed .pio/build/uno/firmware.hex
Removed .pio/build/uno/libFrameworkArduino.a
Removed .pio/build/uno/libFrameworkArduinoVariant.a
Removed .pio/build/uno/FrameworkArduino/_wiring_pulse.o
Removed .pio/build/uno/FrameworkArduino/abi.o
Removed .pio/build/uno/FrameworkArduino/CDC.o
Removed .pio/build/uno/FrameworkArduino/HardwareSerial.o
Removed .pio/build/uno/FrameworkArduino/HardwareSerial0.o
Removed .pio/build/uno/FrameworkArduino/HardwareSerial1.o
Removed .pio/build/uno/FrameworkArduino/HardwareSerial2.o
Removed .pio/build/uno/FrameworkArduino/HardwareSerial3.o
Removed .pio/build/uno/FrameworkArduino/hooks.o
Removed .pio/build/uno/FrameworkArduino/IPAddress.o
Removed .pio/build/uno/FrameworkArduino/main.o
Removed .pio/build/uno/FrameworkArduino/new.o
Removed .pio/build/uno/FrameworkArduino/PluggableUSB.o
Removed .pio/build/uno/FrameworkArduino/Print.o
Removed .pio/build/uno/FrameworkArduino/Stream.o
Removed .pio/build/uno/FrameworkArduino/Tone.o
Removed .pio/build/uno/FrameworkArduino/USBCore.o
Removed .pio/build/uno/FrameworkArduino/WInterrupts.o
Removed .pio/build/uno/FrameworkArduino/wiring.o
Removed .pio/build/uno/FrameworkArduino/wiring_analog.o
Removed .pio/build/uno/FrameworkArduino/wiring_digital.o
Removed .pio/build/uno/FrameworkArduino/wiring_pulse.o
Removed .pio/build/uno/FrameworkArduino/wiring_shift.o
Removed .pio/build/uno/FrameworkArduino/WMath.o
Removed .pio/build/uno/FrameworkArduino/WString.o
Removed .pio/build/uno/src/main.o
Done cleaning
======================= [SUCCESS] Took 0.49 seconds =======================
[Wed Sep  7 15:53:27 2016] Processing nodemcu (platform: espressif8266, board: nodemcu, framework: arduino)
-----------------------------------------------------------------------------------------------------
Removed .pio/build/nodemcu/firmware.bin
Removed .pio/build/nodemcu/firmware.elf
Removed .pio/build/nodemcu/libFrameworkArduino.a
Removed .pio/build/nodemcu/libFrameworkArduinoVariant.a
...
Removed .pio/build/nodemcu/FrameworkArduino/spiffs/spiffs_nucleus.o
Removed .pio/build/nodemcu/FrameworkArduino/umm_malloc/umm_malloc.o
Removed .pio/build/nodemcu/src/main.o
Done cleaning
======================= [SUCCESS] Took 0.50 seconds =======================
[Wed Sep  7 15:53:27 2016] Processing teensy31 (platform: teensy, board: teensy31, framework: arduino)
-----------------------------------------------------------------------------------------------------
Removed .pio/build/teensy31/firmware.elf
Removed .pio/build/teensy31/firmware.hex
Removed .pio/build/teensy31/libFrameworkArduino.a
Removed .pio/build/teensy31/FrameworkArduino/analog.o
Removed .pio/build/teensy31/FrameworkArduino/AudioStream.o
...
Removed .pio/build/teensy31/FrameworkArduino/WString.o
Removed .pio/build/teensy31/FrameworkArduino/yield.o
Removed .pio/build/teensy31/src/main.o
Done cleaning
======================= [SUCCESS] Took 0.50 seconds =======================
[Wed Sep  7 15:53:28 2016] Processing lpmsp430g2553 (platform: timsp430, build_flags: -D LED_BUILTIN=RED_LED, board: lpmsp430g2553, framework: energia)
-----------------------------------------------------------------------------------------------------
Removed .pio/build/lpmsp430g2553/firmware.elf
Removed .pio/build/lpmsp430g2553/firmware.hex
Removed .pio/build/lpmsp430g2553/libFrameworkAnergia.a
Removed .pio/build/lpmsp430g2553/FrameworkAnergia/atof.o
...
Removed .pio/build/lpmsp430g2553/FrameworkAnergia/avr/dtostrf.o
Removed .pio/build/lpmsp430g2553/src/main.o
Done cleaning
======================= [SUCCESS] Took 0.49 seconds =======================


4.
Mix environments and targets

> platformio run -e uno -t upload
[Wed Sep  7 15:55:11 2016] Processing uno (platform: atmelavr, board: uno, framework: arduino)
--------------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
Collected 36 compatible libraries
Looking for dependencies...
Project does not have dependencies
Compiling .pio/build/uno/src/main.o
Archiving .pio/build/uno/libFrameworkArduinoVariant.a
Indexing .pio/build/uno/libFrameworkArduinoVariant.a
Compiling .pio/build/uno/FrameworkArduino/CDC.o
...
Compiling .pio/build/uno/FrameworkArduino/wiring_shift.o
Archiving .pio/build/uno/libFrameworkArduino.a
Indexing .pio/build/uno/libFrameworkArduino.a
Linking .pio/build/uno/firmware.elf
Checking program size .pio/build/uno/firmware.elf
text       data     bss     dec     hex filename
1034          0       9    1043     413 .pio/build/uno/firmware.elf
Building .pio/build/uno/firmware.hex
Looking for upload port...
Auto-detected: /dev/cu.usbmodemFA141
Uploading .pio/build/uno/firmware.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.01s
avrdude: Device signature = 0x1e950f
avrdude: reading input file ".pio/build/uno/firmware.hex"
avrdude: writing flash (1034 bytes):
Writing | ################################################## | 100% 0.18s
avrdude: 1034 bytes of flash written
avrdude: verifying flash memory against .pio/build/uno/firmware.hex:
avrdude: load data flash data from input file .pio/build/uno/firmware.hex:
avrdude: input file .pio/build/uno/firmware.hex contains 1034 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 0.15s
avrdude: verifying ...
avrdude: 1034 bytes of flash verified
avrdude: safemode: Fuses OK (H:00, E:00, L:00)
avrdude done.  Thank you.
======================== [SUCCESS] Took 4.14 seconds ========================


Manage PlatformIO settings

•
platformio settings
•
platformio settings get
  • Usage
  • Description
  • Settings
  • auto_update_libraries
  • auto_update_platforms
  • check_libraries_interval
  • check_platformio_interval
  • check_platforms_interval
  • enable_cache
  • strict_ssl
  • enable_telemetry
  • force_verbose
  • projects_dir

•
Examples

•
platformio settings set
  • Usage
  • Description
  • Examples

•
platformio settings reset
  • Usage
  • Description
  • Examples



platformio settings get [NAME]
pio settings get [NAME]


NOTE:

  • The Yes value is equal to: True, Y, 1 and is not case sensitive.
  • You can override these settings using Environment variables.



Get/List existing settings

auto_update_libraries

No
Yes/No

Automatically update libraries.

auto_update_platforms

No
Yes/No

Automatically update platforms.

check_libraries_interval

7
Days (Number)

Check for the library updates interval.

check_platformio_interval

3
Days (Number)

Check for the new PlatformIO interval.

check_platforms_interval

7
Days (Number)

Check for the platform updates interval.

enable_cache

Yes
Yes/No

Enable caching for API requests and Library Manager

strict_ssl

No
Yes/No

Strict SSL for PlatformIO Services

enable_telemetry

Yes
Yes/No

Share minimal diagnostics and usage information to help us make PlatformIO better.

The source code of telemetry service is open source. You can make sure that we DO NOT SHARE PRIVATE information or source code of your project. All information shares ANONYMOUSLY.

Which data do we collect and why?

  • A version of Python Interpreter. PlatformIO Core (CLI) is written in Python language, including development Development Platforms. We need to know which Python version produces such type of exceptions (see below), which is more popular, which version we should drop and focus on a new one
  • PlatformIO Core (CLI) errors/exceptions. We report automatically fatal exceptions raised by PlatformIO Core source code but NOT by your project
  • The name of the used platform, board, framework. We collect this type of information to have a clear picture which software products are the most widely used by our Community and for the which we should provide frequent updates and add new features ( for example, "atmelavr", "arduino", "uno", etc.)
  • The name of CLI command. It helps us to improve our CLI. For example, "run", "lib list")
  • The name of Cloud & Desktop IDE. This is very important information for us. We create native extensions based on the popularity of IDEs (for example, VSCode, CLion)

Thanks a lot that you keep this setting enabled!

force_verbose

No
Yes/No

Force verbose output when processing environments. This setting overrides

  • platformio run --verbose
  • platformio ci --verbose
  • platformio test --verbose

projects_dir

~/Documents/PlatformIO/Projects
Path to folder

Default location for PlatformIO projects (PIO Home)

1.
List all settings and theirs current values

> platformio settings get
Name                            Value [Default]   Description
------------------------------------------------------------------------------------------
auto_update_libraries           No                Automatically update libraries (Yes/No)
auto_update_platforms           No                Automatically update platforms (Yes/No)
check_libraries_interval        7                 Check for the library updates interval (days)
check_platformio_interval       3                 Check for the new PlatformIO interval (days)
check_platforms_interval        7                 Check for the platform updates interval (days)
enable_cache                    Yes               Enable caching for API requests and Library Manager
strict_ssl                      No                Strict SSL for PlatformIO Services
enable_telemetry                Yes               Telemetry service?#enable-telemetry> (Yes/No)
force_verbose                   No                Force verbose output when processing environments
projects_dir                    ~/Documents/PlatformIO/Projects Default location for PlatformIO projects (PIO Home)


2.
Show specified setting

$ platformio settings get auto_update_platforms
Name                            Value [Default]   Description
------------------------------------------------------------------------------------------
auto_update_platforms           Yes               Automatically update platforms (Yes/No)



platformio settings set NAME VALUE


Set new value for the setting

Change to check for the new PlatformIO each day

$ platformio settings set check_platformio_interval 1
The new value for the setting has been set!
Name                            Value [Default]   Description
------------------------------------------------------------------------------------------
check_platformio_interval       1 [3]             Check for the new PlatformIO interval (days)



platformio settings reset


Reset settings to default

$ platformio settings reset
The settings have been reset!
Name                            Value [Default]   Description
------------------------------------------------------------------------------------------
auto_update_libraries           No                Automatically update libraries (Yes/No)
auto_update_platforms           No                Automatically update platforms (Yes/No)
check_libraries_interval        7                 Check for the library updates interval (days)
check_platformio_interval       3                 Check for the new PlatformIO interval (days)
check_platforms_interval        7                 Check for the platform updates interval (days)
enable_cache                    Yes               Enable caching for API requests and Library Manager
strict_ssl                      No                Enable SSL for PlatformIO Services
enable_telemetry                Yes               Telemetry service?#enable-telemetry> (Yes/No)
force_verbose                   No                Force verbose output when processing environments
projects_dir                    ~/Documents/PlatformIO/Projects Default location for PlatformIO projects (PIO Home)


Miscellaneous system commands.

To print all available commands and options use:

platformio system --help
platformio system COMMAND --help
pio system --help


Shell completion support for

  • Fish
  • Zsh
  • Bash
  • PowerShell

To print all available commands and options use:

platformio misc completion --help
platformio misc completion COMMAND --help
pio misc completion --help


•
platformio misc completion install
  • Usage
  • Description
•
Options

•
Examples


platformio misc completion install [OPTIONS]
pio misc completion install [OPTIONS]


Install shell completion files or code.


The shell type, default is auto and will be detected from a current shell session.

Supported shells are:

  • fish
  • zsh
  • bash
  • powershell


Custom installation path of the code to be evaluated by the shell. The standard installation path is used by default.

> pio misc completion install
PlatformIO CLI completion has been installed for fish shell to ~/.config/fish/completions/pio.fish
Please restart a current shell session


•
platformio misc completion uninstall
  • Usage
  • Description
•
Options

•
Examples


platformio misc completion uninstall [OPTIONS]
pio misc completion uninstall [OPTIONS]


Uninstall shell completion files or code.


The shell type, default is auto and will be detected from a current shell session.

Supported shells are:

  • fish
  • zsh
  • bash
  • powershell


Custom installation path of the code to be evaluated by the shell. The standard installation path is used by default.

> pio misc completion uninstall
PlatformIO CLI completion has been uninstalled for fish shell from ~/.config/fish/completions/pio.fish
Please restart a current shell session.


Helper command for local PIO Unit Testing.

•
platformio test
  • Usage
  • Description
  • Options
  • Examples


platformio test [OPTIONS]
pio test [OPTIONS]


Run locally tests from PlatformIO based project. More details about PlatformIO PIO Unit Testing.

This command allows you to apply the tests for the environments specified in "platformio.ini" (Project Configuration File).


Process specified environments. More details platformio run --environment


Process only the tests where the name matches specified patterns. More than one pattern is allowed. If you need to filter some tests for a specific environment, please take a look at test_filter option from "platformio.ini" (Project Configuration File).

Pattern Meaning
* matches everything
? matches any single character
[seq] matches any character in seq
[!seq] matches any character not in seq

For example, platformio test --filter "mytest*" -i "test[13]"


Ignore tests where the name matches specified patterns. More than one pattern is allowed. If you need to ignore some tests for a specific environment, please take a look at test_ignore option from "platformio.ini" (Project Configuration File).

Pattern Meaning
* matches everything
? matches any single character
[seq] matches any character in seq
[!seq] matches any character not in seq

For example, platformio test --ignore "mytest*" -i "test[13]"


A port that is intended for firmware uploading. To list available ports please use platformio device list command.

If upload port is not specified, PlatformIO will try to detect it automatically.


A Serial/UART port that PlatformIO uses as communication interface between PlatformIO Unit Test Engine and target device. To list available ports please use platformio device list command.

If test port is not specified, PlatformIO will try to detect it automatically.


Specify the path to project directory. By default, --project-dir is equal to current working directory (CWD).


New in version 4.0.

Process project with a custom "platformio.ini" (Project Configuration File).


Skip building stage.


Skip uploading stage


Disable software reset via Serial.DTR/RST before test running. In this case, need to press "reset" button manually after firmware uploading.

WARNING:

If board does not support software reset via Serial.DTR/RTS you should add >2 seconds delay before UNITY_BEGIN()`. We need that time to establish a ``Serial communication between host machine and target device. See PIO Unit Testing.



Set initial RTS line state for Serial Monitor (0 or 1), default 1. We use it to gather test results via Serial connection.


Set initial DTR line state for Serial Monitor (0 or 1), default 1. We use it to gather test results via Serial connection.


Shows detailed information when processing environments.

This option can also be set globally using force_verbose setting or by environment variable PLATFORMIO_SETTING_FORCE_VERBOSE.

For the examples please follow to PIO Unit Testing page.

•
platformio update
  • Usage
  • Description
  • Options
  • Examples


platformio update [OPTIONS]
pio update [OPTIONS]


Check or update installed PIO Core packages, Development Platforms and global Libraries. This command is combination of 2 sub-commands:

  • platformio platform update
  • platformio lib update


Update only the core packages


DEPRECATED. Please use --dry-run instead.


Do not update, only check for the new versions

> platformio update
Platform Manager
================
Platform timsp430
--------
Updating timsp430 @ 0.0.0:  [Up-to-date]
Updating toolchain-timsp430 @ 1.40603.0:    [Up-to-date]
Updating framework-energiamsp430 @ 1.17.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform freescalekinetis
--------
Updating freescalekinetis @ 0.0.0:  [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform ststm32
--------
Updating ststm32 @ 0.0.0:   [Up-to-date]
Updating framework-libopencm3 @ 1.1.0:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating tool-stlink @ 1.10200.0:   [Up-to-date]
Updating framework-spl @ 1.10201.0:     [Up-to-date]
Updating framework-cmsis @ 1.40300.0:   [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform lattice_ice40
--------
Updating lattice_ice40 @ 0.0.0:     [Up-to-date]
Updating toolchain-icestorm @ 1.7.0:    [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform atmelavr
--------
Updating atmelavr @ 0.0.0:  [Up-to-date]
Updating framework-arduinoavr @ 1.10608.1:  [Up-to-date]
Updating tool-avrdude @ 1.60001.1:  [Up-to-date]
Updating toolchain-atmelavr @ 1.40801.0:    [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform espressif8266
--------
Updating espressif8266 @ 0.0.0:     [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Updating toolchain-xtensa @ 1.40802.0:  [Up-to-date]
Updating tool-esptool @ 1.409.0:    [Up-to-date]
Updating tool-mkspiffs @ 1.102.0:   [Up-to-date]
Updating framework-arduinoespressif8266 @ 1.20300.0:    [Up-to-date]
Updating sdk-esp8266 @ 1.10502.0:   [Up-to-date]
Platform linux_x86_64
--------
Updating linux_x86_64 @ 0.0.0:  [Up-to-date]
Updating toolchain-gcclinux64 @ 1.40801.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform windows_x86
--------
Updating windows_x86 @ 0.0.0:   [Up-to-date]
Updating toolchain-gccmingw32 @ 1.40800.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform teensy
--------
Updating teensy @ 0.0.0:    [Up-to-date]
Updating framework-arduinoteensy @ 1.128.0:     [Up-to-date]
Updating tool-teensy @ 1.1.0:   [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Updating toolchain-atmelavr @ 1.40801.0:    [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Platform nordicnrf51
--------
Updating nordicnrf51 @ 0.0.0:   [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating framework-arduinonordicnrf51 @ 1.20302.0:  [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform titiva
--------
Updating titiva @ 0.0.0:    [Up-to-date]
Updating framework-libopencm3 @ 1.1.0:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating framework-energiativa @ 1.17.0:    [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform atmelsam
--------
Updating atmelsam @ 0.0.0:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating tool-openocd @ 1.900.0:    [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Updating tool-avrdude @ 1.60001.1:  [Up-to-date]
Updating tool-bossac @ 1.10601.0:   [Up-to-date]
Platform siliconlabsefm32
--------
Updating siliconlabsefm32 @ 0.0.0:  [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform microchippic32
--------
Updating microchippic32 @ 0.0.0:    [Up-to-date]
Updating framework-arduinomicrochippic32 @ 1.10201.0:   [Up-to-date]
Updating toolchain-microchippic32 @ 1.40803.0:  [Up-to-date]
Updating tool-pic32prog @ 1.200200.0:   [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform linux_i686
--------
Updating linux_i686 @ 0.0.0:    [Up-to-date]
Updating toolchain-gcclinux32 @ 1.40801.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform intel_arc32
--------
Updating intel_arc32 @ 0.0.0:   [Up-to-date]
Updating framework-arduinointel @ 1.10006.0:    [Up-to-date]
Updating tool-arduino101load @ 1.124.0:     [Up-to-date]
Updating toolchain-intelarc32 @ 1.40805.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform nxplpc
--------
Updating nxplpc @ 0.0.0:    [Up-to-date]
Updating framework-mbed @ 1.121.1:  [Up-to-date]
Updating toolchain-gccarmnoneeabi @ 1.40804.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform linux_arm
--------
Updating linux_arm @ 0.0.0:     [Up-to-date]
Updating toolchain-gccarmlinuxgnueabi @ 1.40802.0:  [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Platform native
--------
Updating native @ 0.0.0:    [Up-to-date]
Updating tool-scons @ 2.4.1:    [Up-to-date]
Library Manager
===============
Updating Adafruit-GFX @ 334e815bc1:     [Up-to-date]
Updating Adafruit-ST7735 @ d53d4bf03a:  [Up-to-date]
Updating Adafruit-DHT @ 09344416d2:     [Up-to-date]
Updating Adafruit-Unified-Sensor @ f2af6f4efc:  [Up-to-date]
Updating ESP8266_SSD1306 @ 3.2.3:   [Up-to-date]
Updating EngduinoMagnetometer @ 3.1.0:  [Up-to-date]
Updating IRremote @ 2.2.1:  [Up-to-date]
Updating Json @ 5.6.4:  [Up-to-date]
Updating MODSERIAL @ d8422efe47:    [Up-to-date]
Updating PJON @ 1fb26fd:    [Checking]
git version 2.7.4 (Apple Git-66)
Already up-to-date.
Updating Servo @ 36b69a7ced07:  [Checking]
Mercurial Distributed SCM (version 3.8.4)
(see https://mercurial-scm.org for more information)
Copyright (C) 2005-2016 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
pulling from https://developer.mbed.org/users/simon/code/Servo/
searching for changes
no changes found
Updating TextLCD @ 308d188a2d3a:    [Checking]
Mercurial Distributed SCM (version 3.8.4)
(see https://mercurial-scm.org for more information)
Copyright (C) 2005-2016 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
pulling from https://developer.mbed.org/users/simon/code/TextLCD/
searching for changes
no changes found


•
platformio upgrade
  • Usage
  • Description
  • Options
  • Examples


platformio upgrade
pio upgrade


Check or upgrade PlatformIO to the latest version


Use development branch.

> platformio upgrade
You are up-to-date!
PlatformIO x.x.x is currently the newest version available.
# If you have problem with permissions try:
> sudo platformio upgrade


PlatformIO Home

PlatformIO Home allows you to interact with PlatformIO ecosystem using modern and cross-platform GUI:

  • Project Manager
  • PIO Account
  • Library Manager
  • Development Platforms
  • Library and development platform updates
  • Frameworks
  • Boards
  • Device Manager: serial, logical, and multicast DNS services
  • Static Code Analysis
  • Firmware File Explorer
  • Firmware Memory Inspection
  • Firmware Sections & Symbols Viewer.

  • Installation
  • Quick Start
  • PlatformIO IDE
  • PlatformIO Core

•
Demo
  • Welcome & Project Manager
  • Project Inspect
  • Statistics
  • Firmware File Explorer
  • Firmware Symbols
  • Firmware Sections
  • Static Code Analysis

  • Library Manager
  • Board Explorer


You do not need to install PlatformIO Home separately, it's already built-in in PlatformIO IDE and PlatformIO Core (CLI).

Quick Start

PlatformIO IDE

Please open PlatformIO Home using (HOME) button on PIO Toolbar:

  • Atom: PlatformIO Toolbar
  • VSCode: PlatformIO Toolbar

PlatformIO Core

Please launch PlatformIO Home Web-server using platformio home command and open in your browser http://127.0.0.1:8008.

You can change host and port. Please check platformio home command for details.

[image]

[image]

Only code analysis (PIO Check) [image]

[image]

File Symbols [image]

[image]

[image]

[image]

Library Manager

[image]

[image]

The goal of this tutorial is to demonstrate how simple it is to use PIO Unit Testing.

  • Level: Beginner
  • Platforms: Windows, macOS, Linux

  • Setting Up the Project
  • Project structure
  • Source files
  • Test results

Setting Up the Project

1.
Please navigate to the Quick Start section and create the "Blink Project".
2.
Create a test directory in the project (on the same level as src) and place a test_main.cpp file in it (the source code is located below).
3.
Run tests using the platformio test command.

project_dir
├── lib
│   └── README
├── platformio.ini
├── src
│   └── ...
└── test
    └── test_main.cpp


•
platformio.ini

; PlatformIO Project Configuration File
;
;   Build options: build flags, source filter, extra scripting
;   Upload options: custom port, speed and extra flags
;   Library options: dependencies, extra library storages
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
[env:uno]
platform = atmelavr
framework = arduino
board = uno
[env:teensy31]
platform = teensy
framework = arduino
board = teensy31


•
test/test_main.cpp

#include <Arduino.h>
#include <unity.h>
// void setUp(void) {
// // set stuff up here
// }
// void tearDown(void) {
// // clean stuff up here
// }
void test_led_builtin_pin_number(void) {
    TEST_ASSERT_EQUAL(13, LED_BUILTIN);
}
void test_led_state_high(void) {
    digitalWrite(LED_BUILTIN, HIGH);
    TEST_ASSERT_EQUAL(HIGH, digitalRead(LED_BUILTIN));
}
void test_led_state_low(void) {
    digitalWrite(LED_BUILTIN, LOW);
    TEST_ASSERT_EQUAL(LOW, digitalRead(LED_BUILTIN));
}
void setup() {
    // NOTE!!! Wait for >2 secs
    // if board doesn't support software reset via Serial.DTR/RTS
    delay(2000);
    UNITY_BEGIN();    // IMPORTANT LINE!
    RUN_TEST(test_led_builtin_pin_number);
    pinMode(LED_BUILTIN, OUTPUT);
}
uint8_t i = 0;
uint8_t max_blinks = 5;
void loop() {
    if (i < max_blinks)
    {
        RUN_TEST(test_led_state_high);
        delay(500);
        RUN_TEST(test_led_state_low);
        delay(500);
        i++;
    }
    else if (i == max_blinks) {
      UNITY_END(); // stop unit testing
    }
}




> platformio test -e uno --verbose
Verbose mode can be enabled via `-v, --verbose` option
Collected 1 items
===================== [test/*] Building... (1/3) =======================
Processing uno (platform: atmelavr; board: uno; framework: arduino)
-------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
PLATFORM: Atmel AVR > Arduino Uno
SYSTEM: ATMEGA328P 16MHz 2KB RAM (31.50KB Flash)
Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF MODES: FINDER(chain) COMPATIBILITY(soft)
Collected 24 compatible libraries
Scanning dependencies...
No dependencies
Compiling .pio\build\uno\test\output_export.cpp.o
Compiling .pio\build\uno\test\test_main.cpp.o
Archiving .pio\build\uno\libFrameworkArduinoVariant.a
Compiling .pio\build\uno\FrameworkArduino\CDC.cpp.o
Indexing .pio\build\uno\libFrameworkArduinoVariant.a
Compiling .pio\build\uno\FrameworkArduino\HardwareSerial.cpp.o
Compiling .pio\build\uno\FrameworkArduino\HardwareSerial0.cpp.o
Compiling .pio\build\uno\FrameworkArduino\HardwareSerial1.cpp.o
Compiling .pio\build\uno\FrameworkArduino\HardwareSerial2.cpp.o
Compiling .pio\build\uno\FrameworkArduino\HardwareSerial3.cpp.o
Compiling .pio\build\uno\FrameworkArduino\IPAddress.cpp.o
Compiling .pio\build\uno\FrameworkArduino\PluggableUSB.cpp.o
Compiling .pio\build\uno\FrameworkArduino\Print.cpp.o
Compiling .pio\build\uno\FrameworkArduino\Stream.cpp.o
Compiling .pio\build\uno\FrameworkArduino\Tone.cpp.o
Compiling .pio\build\uno\FrameworkArduino\USBCore.cpp.o
Compiling .pio\build\uno\FrameworkArduino\WInterrupts.c.o
Compiling .pio\build\uno\FrameworkArduino\WMath.cpp.o
Compiling .pio\build\uno\FrameworkArduino\WString.cpp.o
Compiling .pio\build\uno\FrameworkArduino\abi.cpp.o
Compiling .pio\build\uno\FrameworkArduino\hooks.c.o
Compiling .pio\build\uno\FrameworkArduino\main.cpp.o
Compiling .pio\build\uno\FrameworkArduino\new.cpp.o
Compiling .pio\build\uno\FrameworkArduino\wiring.c.o
Compiling .pio\build\uno\FrameworkArduino\wiring_analog.c.o
Compiling .pio\build\uno\FrameworkArduino\wiring_digital.c.o
Compiling .pio\build\uno\FrameworkArduino\wiring_pulse.S.o
Compiling .pio\build\uno\FrameworkArduino\wiring_pulse.c.o
Compiling .pio\build\uno\FrameworkArduino\wiring_shift.c.o
Compiling .pio\build\uno\UnityTestLib\unity.o
Archiving .pio\build\uno\libFrameworkArduino.a
Indexing .pio\build\uno\libFrameworkArduino.a
Archiving .pio\build\uno\libUnityTestLib.a
Indexing .pio\build\uno\libUnityTestLib.a
Linking .pio\build\uno\firmware.elf
Checking size .pio\build\uno\firmware.elf
Building .pio\build\uno\firmware.hex
Memory Usage -> http://bit.ly/pio-memory-usage
DATA:    [==        ]  20.0% (used 410 bytes from 2048 bytes)
PROGRAM: [=         ]  12.6% (used 4060 bytes from 32256 bytes)
========================================== [SUMMARY] ==========================================
Environment uno                 [SUCCESS]
Environment teensy31            [SKIP]
================================= [SUCCESS] Took 2.54 seconds =================================
================================= [test/*] Uploading... (2/3) =================================
Processing uno (platform: atmelavr; board: uno; framework: arduino)
-------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
PLATFORM: Atmel AVR > Arduino Uno
SYSTEM: ATMEGA328P 16MHz 2KB RAM (31.50KB Flash)
Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF MODES: FINDER(chain) COMPATIBILITY(soft)
Collected 24 compatible libraries
Scanning dependencies...
No dependencies
Checking size .pio\build\uno\firmware.elf
Memory Usage -> http://bit.ly/pio-memory-usage
DATA:    [==        ]  20.0% (used 410 bytes from 2048 bytes)
PROGRAM: [=         ]  12.6% (used 4060 bytes from 32256 bytes)
Configuring upload protocol...
AVAILABLE: arduino
CURRENT: upload_protocol = arduino
Looking for upload port...
Auto-detected: COM18
Uploading .pio\build\uno\firmware.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
avrdude: Device signature = 0x1e950f (probably m328p)
avrdude: reading input file ".pio\build\uno\firmware.hex"
avrdude: writing flash (4060 bytes):
Writing | ################################################## | 100% 0.76s
avrdude: 4060 bytes of flash written
avrdude: verifying flash memory against .pio\build\uno\firmware.hex:
avrdude: load data flash data from input file .pio\build\uno\firmware.hex:
avrdude: input file .pio\build\uno\firmware.hex contains 4060 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 0.48s
avrdude: verifying ...
avrdude: 4060 bytes of flash verified
avrdude: safemode: Fuses OK (E:00, H:00, L:00)
avrdude done.  Thank you.
=============================== [SUMMARY] ================================
Environment uno                 [SUCCESS]
Environment teensy31            [SKIP]
 ====================== [SUCCESS] Took 4.45 seconds ======================
================================== [test/*] Testing... (3/3) ==================================
If you don't see any output for the first 10 secs, please reset board (press reset button)
test\test_main.cpp:30:test_led_builtin_pin_number       [PASSED]
test\test_main.cpp:41:test_led_state_high       [PASSED]
test\test_main.cpp:43:test_led_state_low        [PASSED]
test\test_main.cpp:41:test_led_state_high       [PASSED]
test\test_main.cpp:43:test_led_state_low        [PASSED]
test\test_main.cpp:41:test_led_state_high       [PASSED]
test\test_main.cpp:43:test_led_state_low        [PASSED]
test\test_main.cpp:41:test_led_state_high       [PASSED]
test\test_main.cpp:43:test_led_state_low        [PASSED]
test\test_main.cpp:41:test_led_state_high       [PASSED]
test\test_main.cpp:43:test_led_state_low        [PASSED]
-----------------------
11 Tests 0 Failures 0 Ignored
============================ [TEST SUMMARY] ==============================
test/*/env:uno  [PASSED]
test/*/env:teensy31     [IGNORED]
==================== [PASSED] Took 12.99 seconds =========================


The goal of this tutorial is to demonstrate how simple it is to use VSCode to develop, run and debug a simple project with the Arduino framework for the ESP32-DevKitC board.

  • Level: Beginner
  • Platforms: Windows, Mac OS X, Linux

  • Downloaded and installed VSCode
  • ESP32-DevKitC development board
  • Olimex ARM-USB-OCD or Olimex ARM-USB-TINY adapter for debugging


  • Setting Up the Project
  • Adding Code to the Generated Project
  • Compiling and Uploading the Firmware
  • Debugging the Firmware
•
Setting Up the Hardware

  • Writing Unit Tests
  • Adding Bluetooth LE features
  • Conclusion

Setting Up the Project

First, we need to create a new project using the PlatformIO Home Page (to open this page, just press the Home icon on the toolbar): [image]

Next, we need to select ESP32-DevKitC as a development board, Arduino as a framework and a path to the project location (or use the default one): [image]

Processing the selected project may take some time (PlatformIO will download and install all required packages). After that, we have a fully configured project that is ready for developing code with the Arduino framework.

Adding Code to the Generated Project

Let's add some actual code to the project. Firstly, we open a default main file named main.cpp in the src_dir folder and replace its content with following:

#include <Arduino.h>
void setup()
{
    Serial.begin(9600);
}
void loop()
{
    Serial.println("Hello world!");
    delay(1000);
}


[image]

We have now created a basic project ready for compiling and uploading.

Compiling and Uploading the Firmware

Now we can build the project. There are several ways to compile firmware:

  • Build option in the Project Tasks menu,
  • Build button in PlatformIO Toolbar,
  • Task Menu: Tasks: Run Task... > PlatformIO: Build, or in the PlatformIO Toolbar,
  • Command Palette: View: Command Palette > PlatformIO: Build, or
  • via hotkeys cmd-alt-b / ctrl-alt-b

Marked in red: [image]

If everything went well, we should see a Success message in the terminal window: [image]

There are also several ways to upload the firmware to the board:

  • Upload option in the Project Tasks menu,
  • Upload button in PlatformIO Toolbar,
  • Command Palette: View: Command Palette > PlatformIO: Upload,
  • using the Task Menu: Tasks: Run Task... > PlatformIO: Upload, or
  • via hotkeys: cmd-alt-u / ctrl-alt-u:

[image]

After uploading, we need to check if the firmware is uploaded correctly. To do this, open the serial monitor and check that the message from the board is received. To open the serial monitor, we can use the following options:

  • Monitor option in the Project Tasks menu,
  • Serial Monitor button in the PlatformIO Toolbar,
  • Command Palette: View: Command Palette > PlatformIO: Monitor, or
  • Task Menu: Tasks: Run Task... > PlatformIO: Monitor:

[image]

If the firmware works as expected, the message from the board can be observed in the terminal window: [image]

Debugging the Firmware

Setting Up the Hardware

In order to use a JTAG probe with an ESP32, we need to connect the following pins:

ESP32 pin JTAG probe pin
3.3V Pin 1(VTref)
GPIO 9 (EN) Pin 3 (nTRST)
GND Pin 4 (GND)
GPIO 12 (TDI) Pin 5 (TDI)
GPIO 14 (TMS) Pin 7 (TMS)
GPIO 13 (TCK) Pin 9 (TCK)
GPIO 15 (TDO) Pin 13 (TDO)

PIO Unified Debugger offers the easiest way to debug the board. Firstly, we need to specify debug_tool in "platformio.ini" (Project Configuration File). In this tutorial, an Olimex ARM-USB-OCD-H debug probe is used:

[env:esp32dev]
platform = espressif32
board = esp32dev
framework = arduino
debug_tool = olimex-arm-usb-ocd-h


To start the debug session we can use the following methods:

  • Debug: Start debugging in the top menu,
  • Start Debugging option in the Quick Access menu, or
  • hotkey button F5:

[image]

We need to wait some time while PlatformIO initializes the debug session, and are ready to debug when the first line after the main function is highlighted.

1.
Please wait when debugging session is stopped at the first line of app_main() function
2.
WARNING! Please set a breakpoint at void loopTask(void *pvParameters) (line 13 in the screenshot below - this line can change between releases)
3.
Now, please press CONTINUE/RUN button on debugging toolbar (right arrow icon)
4.
The debugging session should stop at the first line of the void loopTask(void *pvParameters) function
5.
Now, navigate to your Arduino setup/loop code and do classic debugging.

[image]

We can walk through the code using control buttons, set breakpoints, and add variables to the Watch window: [image]

Writing Unit Tests

Test cases can be added to a single file that may include multiple tests. First of all, in this file, we need to add four default functions: setUp, tearDown, setup and loop. Functions setUp and tearDown are used to initialize and finalize test conditions. Implementations of these functions are not required for running tests, but if you need to initialize some variables before you run a test, use the setUp function. Likewise, if you need to clean up variables, use tearDown function. In our example we will use these functions to respectively initialize and deinitialize LED states. The setup and loop functions act as a simple Arduino program where we describe our test plan.

Let's create a test folder in the root of the project and add a new file, test_main.cpp, to this folder. Next, basic tests for String class will be implemented in this file:

  • test_string_concat tests the concatenation of two strings
  • test_string_substring tests the correctness of the substring extraction
  • test_string_index_of ensures that the string returns the correct index of the specified symbol
  • test_string_equal_ignore_case tests case-insensitive comparison of two strings
  • test_string_to_upper_case tests conversion of the string to upper-case
  • test_string_replace tests the correctness of the replacing operation

#include <Arduino.h>
#include <unity.h>
String STR_TO_TEST;
void setUp(void) {
    // set stuff up here
    STR_TO_TEST = "Hello, world!";
}
void tearDown(void) {
    // clean stuff up here
    STR_TO_TEST = "";
}
void test_string_concat(void) {
    String hello = "Hello, ";
    String world = "world!";
    TEST_ASSERT_EQUAL_STRING(STR_TO_TEST.c_str(), (hello + world).c_str());
}
void test_string_substring(void) {
    TEST_ASSERT_EQUAL_STRING("Hello", STR_TO_TEST.substring(0, 5).c_str());
}
void test_string_index_of(void) {
    TEST_ASSERT_EQUAL(7, STR_TO_TEST.indexOf('w'));
}
void test_string_equal_ignore_case(void) {
    TEST_ASSERT_TRUE(STR_TO_TEST.equalsIgnoreCase("HELLO, WORLD!"));
}
void test_string_to_upper_case(void) {
    STR_TO_TEST.toUpperCase();
    TEST_ASSERT_EQUAL_STRING("HELLO, WORLD!", STR_TO_TEST.c_str());
}
void test_string_replace(void) {
    STR_TO_TEST.replace('!', '?');
    TEST_ASSERT_EQUAL_STRING("Hello, world?", STR_TO_TEST.c_str());
}
void setup()
{
    delay(2000); // service delay
    UNITY_BEGIN();
    RUN_TEST(test_string_concat);
    RUN_TEST(test_string_substring);
    RUN_TEST(test_string_index_of);
    RUN_TEST(test_string_equal_ignore_case);
    RUN_TEST(test_string_to_upper_case);
    RUN_TEST(test_string_replace);
    UNITY_END(); // stop unit testing
}
void loop()
{
}


Now we are ready to upload tests to the board. To do this we can use the following:

  • Test button on PlatformIO Toolbar,
  • Test option in the Project Tasks menu, or
  • Tasks: Run Task... > PlatformIO Test in the top menu:

[image]

After processing, we should see a detailed report about the testing results: [image]

As we can see from the report, all our tests were successful!

Adding Bluetooth LE features

Now let's create a basic application that can interact with other BLE devices (e.g phones). For example, the following code declares a BLE characteristic whose value can be printed to the serial port:

#include <Arduino.h>
#include <BLEDevice.h>
#include <BLEUtils.h>
#include <BLEServer.h>
#define SERVICE_UUID        "4fafc201-1fb5-459e-8fcc-c5c9c331914b"
#define CHARACTERISTIC_UUID "beb5483e-36e1-4688-b7f5-ea07361b26a8"
class MyCallbacks: public BLECharacteristicCallbacks {
    void onWrite(BLECharacteristic *pCharacteristic) {
      std::string value = pCharacteristic->getValue();
      if (value.length() > 0) {
        Serial.print("\r\nNew value: ");
        for (int i = 0; i < value.length(); i++)
          Serial.print(value[i]);
        Serial.println();
      }
    }
};
void setup() {
  Serial.begin(9600);
  BLEDevice::init("ESP32 BLE example");
  BLEServer *pServer = BLEDevice::createServer();
  BLEService *pService = pServer->createService(SERVICE_UUID);
  BLECharacteristic *pCharacteristic = pService->createCharacteristic(
                                         CHARACTERISTIC_UUID,
                                         BLECharacteristic::PROPERTY_READ |
                                         BLECharacteristic::PROPERTY_WRITE
                                       );
  pCharacteristic->setCallbacks(new MyCallbacks());
  pCharacteristic->setValue("Hello World");
  pService->start();
  BLEAdvertising *pAdvertising = pServer->getAdvertising();
  pAdvertising->start();
}
void loop() {
  delay(2000);
}


Now we can compile and upload this program to the board as described in the previous sections. To verify that our application works as expected, we can use any Android smartphone with the BLE feature and Nordic nRF Connect tool.

At first, we need to scan all advertising BLE devices and connect to the device called ESP32 BLE example. After successful connection to the board, we should see one "Unknown Service" with one "Unknown Characteristic" field: [image]

To set the value, we need to send new text to the BLE characteristic: [image]

The change of the value is printed to the serial monitor: [image]

Now we have a project template for the ESP32-DevKitC board that we can use as boilerplate for later projects.

The goal of this tutorial is to demonstrate how simple it is to use VSCode to develop, run and debug a simple Wi-Fi project with the ESP-IDF framework for the ESP32-DevKitC board.

  • Level: Intermediate
  • Platforms: Windows, Mac OS X, Linux

  • Downloaded and installed VSCode
  • ESP32-DevKitC development board
  • An external debug adapter (e.g. Olimex ARM-USB-OCD)


  • Setting Up the Project
  • Adding Code to the Generated Project
  • Debugging the Firmware
•
Setting Up the Hardware

  • Writing Unit Tests
  • Project Inspection
  • Conclusion

Setting Up the Project

1.
Click on "PlatformIO Home" button on the bottom PlatformIO Toolbar:
[image]


2.
Click on "New Project", select ESP32-DevKitC as the development board, ESP-IDF as the framework and a path to the project location (or use the default one):
[image]



Adding Code to the Generated Project

1.
Create a new file main.c in src_dir folder and add the following code:

/* WiFi softAP Example
   This example code is in the Public Domain (or CC0 licensed, at your option.)
   Unless required by applicable law or agreed to in writing, this
   software is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
   CONDITIONS OF ANY KIND, either express or implied.
*/
#include <string.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "esp_system.h"
#include "esp_wifi.h"
#include "esp_event.h"
#include "esp_log.h"
#include "nvs_flash.h"
#include "lwip/err.h"
#include "lwip/sys.h"
#define EXAMPLE_ESP_WIFI_SSID      "mywifissid"
#define EXAMPLE_ESP_WIFI_PASS      "mywifipass"
#define EXAMPLE_MAX_STA_CONN       (3)
static const char *TAG = "wifi softAP";
static void wifi_event_handler(void* arg, esp_event_base_t event_base,
                                    int32_t event_id, void* event_data)
{
    if (event_id == WIFI_EVENT_AP_STACONNECTED) {
        wifi_event_ap_staconnected_t* event = (wifi_event_ap_staconnected_t*) event_data;
        ESP_LOGI(TAG, "station "MACSTR" join, AID=%d",
                 MAC2STR(event->mac), event->aid);
    } else if (event_id == WIFI_EVENT_AP_STADISCONNECTED) {
        wifi_event_ap_stadisconnected_t* event = (wifi_event_ap_stadisconnected_t*) event_data;
        ESP_LOGI(TAG, "station "MACSTR" leave, AID=%d",
                 MAC2STR(event->mac), event->aid);
    }
}
void wifi_init_softap()
{
    tcpip_adapter_init();
    ESP_ERROR_CHECK(esp_event_loop_create_default());
    wifi_init_config_t cfg = WIFI_INIT_CONFIG_DEFAULT();
    ESP_ERROR_CHECK(esp_wifi_init(&cfg));
    ESP_ERROR_CHECK(esp_event_handler_register(WIFI_EVENT, ESP_EVENT_ANY_ID, &wifi_event_handler, NULL));
    wifi_config_t wifi_config = {
        .ap = {
            .ssid = EXAMPLE_ESP_WIFI_SSID,
            .ssid_len = strlen(EXAMPLE_ESP_WIFI_SSID),
            .password = EXAMPLE_ESP_WIFI_PASS,
            .max_connection = EXAMPLE_MAX_STA_CONN,
            .authmode = WIFI_AUTH_WPA_WPA2_PSK
        },
    };
    if (strlen(EXAMPLE_ESP_WIFI_PASS) == 0) {
        wifi_config.ap.authmode = WIFI_AUTH_OPEN;
    }
    ESP_ERROR_CHECK(esp_wifi_set_mode(WIFI_MODE_AP));
    ESP_ERROR_CHECK(esp_wifi_set_config(ESP_IF_WIFI_AP, &wifi_config));
    ESP_ERROR_CHECK(esp_wifi_start());
    ESP_LOGI(TAG, "wifi_init_softap finished. SSID:%s password:%s",
             EXAMPLE_ESP_WIFI_SSID, EXAMPLE_ESP_WIFI_PASS);
}
void app_main()
{
    //Initialize NVS
    esp_err_t ret = nvs_flash_init();
    if (ret == ESP_ERR_NVS_NO_FREE_PAGES || ret == ESP_ERR_NVS_NEW_VERSION_FOUND) {
      ESP_ERROR_CHECK(nvs_flash_erase());
      ret = nvs_flash_init();
    }
    ESP_ERROR_CHECK(ret);
    ESP_LOGI(TAG, "ESP_WIFI_MODE_AP");
    wifi_init_softap();
}


WARNING:

Make sure this new file main.c is registered as source file using idf_component_register function in src/CMakeLists.txt file: 

idf_component_register(SRCS "main.c")






2.
To compile the project use one of the following options:
  • Build option from the Project Tasks menu
  • Build button in PlatformIO Toolbar
  • Task Menu Tasks: Run Task... > PlatformIO: Build or in PlatformIO Toolbar
  • Command Palette View: Command Palette > PlatformIO: Build
  • Hotkeys cmd-alt-b / ctrl-alt-b:

[image]


3.
If everything went well, we should see a successful result message in the terminal window:
[image]


4.
To upload the firmware to the board we can use the following options:
  • Upload option from the Project Tasks menu
  • Upload button in PlatformIO Toolbar
  • Command Palette View: Command Palette > PlatformIO: Upload
  • Task Menu Tasks: Run Task... > PlatformIO: Upload
  • Hotkeys cmd-alt-u / ctrl-alt-u:

[image]


5.
Connect the board to your computer and update the default monitor speed to 115200 in platformio.ini file:

[env:esp32dev]
platform = espressif32
board = esp32dev
framework = espidf
monitor_speed = 115200




6.
Open Serial Monitor to observe the output from the board:
[image]


7.
If everything went well, the board should be visible as a WiFi access point:
[image]



Debugging the Firmware

Setting Up the Hardware

In order to use PIO Unified Debugger, we need to connect an external JTAG probe and the board using the following pins:

ESP32 pin JTAG probe pin
3.3V Pin 1(VTref)
GPIO 9 (EN) Pin 3 (nTRST)
GND Pin 4 (GND)
GPIO 12 (TDI) Pin 5 (TDI)
GPIO 14 (TMS) Pin 7 (TMS)
GPIO 13 (TCK) Pin 9 (TCK)
GPIO 15 (TDO) Pin 13 (TDO)
1.
Specify debug_tool in "platformio.ini" (Project Configuration File). In this tutorial, Olimex ARM-USB-OCD-H debug probe is used:

[env:esp32dev]
platform = espressif32
board = esp32dev
framework = espidf
monitor_speed = 115200
debug_tool = olimex-arm-usb-ocd-h




2.
To start the debug session we can use the following methods:
  • Debug: Start debugging in the top menu
  • Start Debugging option in the Quick Access menu
  • Hotkey button F5:

[image]


3.
Walk through the code using control buttons, set breakpoints, and add variables to the Watch window:
[image]



Writing Unit Tests

NOTE:

Functions setUp and tearDown are used to initialize and finalize test conditions. Implementations of these functions are not required for running tests but if you need to initialize some variables before you run a test, you use the setUp function and if you need to clean up variables you use tearDown function.


For the sake of simplicity, let's create a small library called calculator, implement several basic functions addition, subtraction, multiplication, division and test them using PIO Unit Testing engine.

1.
Create a new folder calculator in the lib_dir folder and add two new files calculator.h and calculator.c with the following contents:
calculator.h: 

#ifndef _CALCULATOR_H_
#define _CALCULATOR_H_
#ifdef __cplusplus
extern "C" {
#endif
int addition (int a, int b);
int subtraction (int a, int b);
int multiplication (int a, int b);
int division (int a, int b);
#ifdef __cplusplus
}
#endif
#endif // _CALCULATOR_H_


calculator.c:

#include "calculator.h"
int addition(int a, int b)
{
    return a + b;
}
int subtraction(int a, int b)
{
    return a - b;
}
int multiplication(int a, int b)
{
    return a * b;
}
int division(int a, int b)
{
    return a / b;
}




2.
Create a new file test_calc.c to the folder test_dir and add basic tests for the calculator library:

#include <calculator.h>
#include <unity.h>
void test_function_calculator_addition(void) {
    TEST_ASSERT_EQUAL(32, addition(25, 7));
}
void test_function_calculator_subtraction(void) {
    TEST_ASSERT_EQUAL(20, subtraction(23, 3));
}
void test_function_calculator_multiplication(void) {
    TEST_ASSERT_EQUAL(50, multiplication(25, 2));
}
void test_function_calculator_division(void) {
    TEST_ASSERT_EQUAL(32, division(100, 3));
}
void main() {
    UNITY_BEGIN();
    RUN_TEST(test_function_calculator_addition);
    RUN_TEST(test_function_calculator_subtraction);
    RUN_TEST(test_function_calculator_multiplication);
    RUN_TEST(test_function_calculator_division);
    UNITY_END();
}




3.
Let's run tests on the board and check the results. There should be a problem with test_function_calculator_division test:
[image]


4.
Let's fix the incorrect expected value and run tests again. After processing the results should be correct:
[image]



Project Inspection

For illustrative purposes, let's imagine we need to find a function with the biggest memory footprint. Also, let's introduce a bug to our project so PIO Check can report it.

1.
Open PlatformIO Home and navigate to Inspect section, select the current project and press Inspect button:
[image]


2.
Project statistics:
[image]


3.
The biggest function:
[image]


4.
Possible bugs:
[image]



Now we have a project template for the ESP32-DevKitC board that we can use as boilerplate for later projects.

The goal of this tutorial is to demonstrate how simple it is to use PlatformIO IDE for Atom to develop, run and debug a basic blink project with STM32Cube framework for STM32 Nucleo-F401RE board.

  • Level: Intermediate
  • Platforms: Windows, Mac OS X, Linux

  • Downloaded and installed PlatformIO IDE for Atom
  • Install drivers for ST-LINK debug tool
  • Nucleo-F401RE development board


  • Setting Up the Project
  • Adding Code to the Generated Project
  • Compiling and Uploading the Firmware
  • Debugging the Firmware
  • Writing Unit Tests
  • Conclusion
  • Project Source Code

Setting Up the Project

At first step, we need to create a new project using PlatformIO Home Page (to open this page just press Home icon on the toolbar): [image]

On the next step, we need to select ST Nucleo-F401RE as a development board, STM32Cube as a framework and a path to the project location (or use the default one): [image]

Processing the selected project may take some amount of time (PlatformIO will download and install all required packages) and after these steps, we have a fully configured project that is ready for developing code with STM32Cube framework.

Adding Code to the Generated Project

Let's add some actual code to the project. Firstly, we create two main files main.c and main.h in the src_dir folder. Right click on the src in the project window: [image]

Add next content to main.h:

#ifndef MAIN_H
#define MAIN_H
#include "stm32f4xx_hal.h"
#define LED_PIN                                GPIO_PIN_5
#define LED_GPIO_PORT                          GPIOA
#define LED_GPIO_CLK_ENABLE()                  __HAL_RCC_GPIOA_CLK_ENABLE()
#endif // MAIN_H


Add this code to main.c:

#include "main.h"
void LED_Init();
int main(void) {
  HAL_Init();
  LED_Init();
  while (1)
  {
    HAL_GPIO_TogglePin(LED_GPIO_PORT, LED_PIN);
    HAL_Delay(1000);
  }
}
void LED_Init() {
  LED_GPIO_CLK_ENABLE();
  GPIO_InitTypeDef GPIO_InitStruct;
  GPIO_InitStruct.Pin = LED_PIN;
  GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP;
  GPIO_InitStruct.Pull = GPIO_PULLUP;
  GPIO_InitStruct.Speed = GPIO_SPEED_HIGH;
  HAL_GPIO_Init(LED_GPIO_PORT, &GPIO_InitStruct);
}
void SysTick_Handler(void) {
  HAL_IncTick();
}


After this step, we created a basic blink project that is ready for compiling and uploading.

Compiling and Uploading the Firmware

Now we can build the project. To compile firmware we can use next options: Build option on the Project Tasks menu, Build button on PlatformIO Toolbar, using Command Palette View: Command Palette > PlatformIO: Build, using Task Menu Tasks: Run Task... > PlatformIO: Build or via hotkeys cmd-alt-b / ctrl-alt-b: [image]

If everything went well, we should see the successful result in the terminal window: [image]

To upload the firmware to the board we can use next options: Upload option on the Project Tasks menu, Upload button on PlatformIO Toolbar, using Command Palette View: Command Palette > PlatformIO: Upload, using Task Menu Tasks: Run Task... > PlatformIO: Upload or via hotkeys cmd-alt-u / ctrl-alt-u: [image]

After successful uploading, the green LED2 should start blinking.

Debugging the Firmware

PIO Unified Debugger offers the easiest way to debug your board. To start debugging session you can use Start debugging option in PlatformIO Quick Access menu, Debug: Start debugging from the top menu or hotkey button F5: [image]

We need to wait some time while PlatformIO is initializing debug session and when the first line after the main function is highlighted we are ready to debug: [image]

We can walk through the code using control buttons, set breakpoints, see peripheral registers, add variables to Watch window: [image]

Writing Unit Tests

Now let’s write some tests using PIO Unit Testing feature that can help us test code directly on the target board. PIO Unit Testing engine by default supports only three frameworks: Arduino, ESP-IDF, Mbed, and Mbed. Since we decided to use STM32Cube we need to implement a custom test_transport to print testing results and specify that condition in "platformio.ini" (Project Configuration File):

[env:nucleo_f401re]
platform = ststm32
board = nucleo_f401re
framework = stm32cube
test_transport = custom


Also, we need to create a new folder test where the tests and custom test_transport implementation (described next) will be located: [image]

We will use USART2 on ST Nucleo-F401RE board because it's directly connected to the STLink debug interface and in OS it can be visible as a Virtual Com Port, so we don't need any additional USB-UART converter. To implement the custom test_transport we need to create two files unittest_transport.h and unittest_transport.c and put them in the test_dir in the root folder of our project. In these files we need to implement the next four functions:

void unittest_uart_begin();
void unittest_uart_putchar(char c);
void unittest_uart_flush();
void unittest_uart_end();


Implementation of unittest_transport.h:

#ifndef UNITEST_TRANSPORT_H
#define UNITEST_TRANSPORT_H
#ifdef __cplusplus
extern "C" {
#endif
void unittest_uart_begin();
void unittest_uart_putchar(char c);
void unittest_uart_flush();
void unittest_uart_end();
#ifdef __cplusplus
}
#endif
#endif // UNITEST_TRANSPORT_H


Implementation of unittest_transport.c:

#include "unittest_transport.h"
#include "stm32f4xx_hal.h"
#define USARTx                           USART2
#define USARTx_CLK_ENABLE()              __HAL_RCC_USART2_CLK_ENABLE()
#define USARTx_CLK_DISABLE()             __HAL_RCC_USART2_CLK_DISABLE()
#define USARTx_RX_GPIO_CLK_ENABLE()      __HAL_RCC_GPIOA_CLK_ENABLE()
#define USARTx_TX_GPIO_CLK_ENABLE()      __HAL_RCC_GPIOA_CLK_ENABLE()
#define USARTx_RX_GPIO_CLK_DISABLE()     __HAL_RCC_GPIOA_CLK_DISABLE()
#define USARTx_TX_GPIO_CLK_DISABLE()     __HAL_RCC_GPIOA_CLK_DISABLE()
#define USARTx_FORCE_RESET()             __HAL_RCC_USART2_FORCE_RESET()
#define USARTx_RELEASE_RESET()           __HAL_RCC_USART2_RELEASE_RESET()
#define USARTx_TX_PIN                    GPIO_PIN_2
#define USARTx_TX_GPIO_PORT              GPIOA
#define USARTx_TX_AF                     GPIO_AF7_USART2
#define USARTx_RX_PIN                    GPIO_PIN_3
#define USARTx_RX_GPIO_PORT              GPIOA
#define USARTx_RX_AF                     GPIO_AF7_USART2
static UART_HandleTypeDef UartHandle;
void unittest_uart_begin()
{
   GPIO_InitTypeDef  GPIO_InitStruct;
  USARTx_TX_GPIO_CLK_ENABLE();
  USARTx_RX_GPIO_CLK_ENABLE();
  USARTx_CLK_ENABLE();
  GPIO_InitStruct.Pin       = USARTx_TX_PIN;
  GPIO_InitStruct.Mode      = GPIO_MODE_AF_PP;
  GPIO_InitStruct.Pull      = GPIO_PULLUP;
  GPIO_InitStruct.Speed     = GPIO_SPEED_FAST;
  GPIO_InitStruct.Alternate = USARTx_TX_AF;
  HAL_GPIO_Init(USARTx_TX_GPIO_PORT, &GPIO_InitStruct);
  GPIO_InitStruct.Pin = USARTx_RX_PIN;
  GPIO_InitStruct.Alternate = USARTx_RX_AF;
  HAL_GPIO_Init(USARTx_RX_GPIO_PORT, &GPIO_InitStruct);
  UartHandle.Instance          = USARTx;
  UartHandle.Init.BaudRate     = 115200;
  UartHandle.Init.WordLength   = UART_WORDLENGTH_8B;
  UartHandle.Init.StopBits     = UART_STOPBITS_1;
  UartHandle.Init.Parity       = UART_PARITY_NONE;
  UartHandle.Init.HwFlowCtl    = UART_HWCONTROL_NONE;
  UartHandle.Init.Mode         = UART_MODE_TX_RX;
  UartHandle.Init.OverSampling = UART_OVERSAMPLING_16;
  if(HAL_UART_Init(&UartHandle) != HAL_OK) {
    while(1){}
  }
}
void unittest_uart_putchar(char c)
{
    HAL_UART_Transmit(&UartHandle, (uint8_t*)(&c), 1, 1000);
}
void unittest_uart_flush(){}
void unittest_uart_end() {
  USARTx_CLK_DISABLE();
  USARTx_RX_GPIO_CLK_DISABLE();
  USARTx_TX_GPIO_CLK_DISABLE();
}


Now we need to add some test cases. Tests can be added to a single C file that may include multiple tests. First of all, we need to add three default functions: setUp, tearDown and main. setUp and tearDown are used to initialize and finalize test conditions. Implementations of these functions are not required for running tests but if you need to initialize some variables before you run a test, you use the setUp function and if you need to clean up variables you use tearDown function. In our example, we will use these functions to accordingly initialize and deinitialize LED. main function acts as a simple program where we describe our test plan.

Let's add a new file test_main.c to the folder test. Next basic tests for blinking routine will be implemented in this file:

  • test_led_builtin_pin_number ensures that LED_PIN has the correct value
  • test_led_state_high tests functions HAL_GPIO_WritePin and HAL_GPIO_ReadPin with GPIO_PIN_SET value
  • test_led_state_low tests functions HAL_GPIO_WritePin and HAL_GPIO_ReadPin with GPIO_PIN_RESET value

NOTE:

•
2 sec delay is required since the board doesn't support software resetting via Serial.DTR/RTS



#include "../src/main.h"
#include <unity.h>
void setUp(void) {
    LED_GPIO_CLK_ENABLE();
    GPIO_InitTypeDef GPIO_InitStruct;
    GPIO_InitStruct.Pin = LED_PIN;
    GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP;
    GPIO_InitStruct.Pull = GPIO_PULLUP;
    GPIO_InitStruct.Speed = GPIO_SPEED_HIGH;
    HAL_GPIO_Init(LED_GPIO_PORT, &GPIO_InitStruct);
}
void tearDown(void) {
    HAL_GPIO_DeInit(LED_GPIO_PORT, LED_PIN);
}
void test_led_builtin_pin_number(void) {
    TEST_ASSERT_EQUAL(GPIO_PIN_5, LED_PIN);
}
void test_led_state_high(void) {
    HAL_GPIO_WritePin(LED_GPIO_PORT, LED_PIN, GPIO_PIN_SET);
    TEST_ASSERT_EQUAL(GPIO_PIN_SET, HAL_GPIO_ReadPin(LED_GPIO_PORT, LED_PIN));
}
void test_led_state_low(void) {
    HAL_GPIO_WritePin(LED_GPIO_PORT, LED_PIN, GPIO_PIN_RESET);
    TEST_ASSERT_EQUAL(GPIO_PIN_RESET, HAL_GPIO_ReadPin(LED_GPIO_PORT, LED_PIN));
}
int main() {
    HAL_Init();         // initialize the HAL library
    HAL_Delay(2000);    // service delay
    UNITY_BEGIN();
    RUN_TEST(test_led_builtin_pin_number);
    for (unsigned int i = 0; i < 5; i++)
    {
        RUN_TEST(test_led_state_high);
        HAL_Delay(500);
        RUN_TEST(test_led_state_low);
        HAL_Delay(500);
    }
    UNITY_END(); // stop unit testing
    while(1){}
}
void SysTick_Handler(void) {
    HAL_IncTick();
}


Now we are ready to upload tests to the board. To do this we can use Test option from the Project Tasks menu, Tasks: Run Task... > PlatformIO Test option from the top menu or Test button on PlatformIO Toolbar: [image]

After processing we should see a detailed report about the testing results: [image]

Congratulations! As we can see from the report, all our tests went successfully!

Now we have a decent template that we can improve for our next more complex projects.

The source code of this tutorial is available at https://github.com/platformio/platformio-examples/tree/develop/unit-testing/stm32cube

The goal of this tutorial is to demonstrate how simple it is to use VSCode to develop, run and debug a simple project with Arduino framework for Nordic nRF52-DK board.

  • Level: Beginner
  • Platforms: Windows, Mac OS X, Linux

  • Downloaded and installed VSCode
  • Install drivers for J-LINK debug tool
  • Nordic nRF52-DK development board


  • Setting Up the Project
  • Adding Code to the Generated Project
  • Compiling and Uploading the Firmware
  • Debugging the Firmware
  • Writing Unit Tests
  • Adding Bluetooth LE features
  • Conclusion

Setting Up the Project

At first step, we need to create a new project using PlatformIO Home Page (to open this page just press Home icon on the toolbar): [image]

On the next step we need to select Nordic nRF52-DK as a development board, Arduino as a framework and a path to the project location (or use the default one): [image]

Processing the selected project may take some amount of time (PlatformIO will download and install all required packages) and after these steps, we have a fully configured project that is ready for developing code with Arduino framework.

Adding Code to the Generated Project

Let's add some actual code to the project. Firstly, we open a default main file main.cpp in the src_dir folder and replace its contents with the following:

#include <Arduino.h>
void setup()
{
    pinMode(LED_BUILTIN, OUTPUT);
}
void loop()
{
    digitalWrite(LED_BUILTIN, HIGH);
    delay(100);
    digitalWrite(LED_BUILTIN, LOW);
    delay(100);
}


[image]

After this step, we created a basic blink project ready for compiling and uploading.

Compiling and Uploading the Firmware

Now we can build the project. To compile firmware we can use next options: Build option from the Project Tasks menu, Build button in PlatformIO Toolbar, Task Menu Tasks: Run Task... > PlatformIO: Build or in PlatformIO Toolbar, Command Palette View: Command Palette > PlatformIO: Build or via hotkeys cmd-alt-b / ctrl-alt-b: [image]

If everything went well, we should see a successful result message in the terminal window: [image]

To upload the firmware to the board we can use next options: Upload option from the Project Tasks menu, Upload button in PlatformIO Toolbar, Command Palette View: Command Palette > PlatformIO: Upload, using Task Menu Tasks: Run Task... > PlatformIO: Upload or via hotkeys cmd-alt-u / ctrl-alt-u: [image]

After successful uploading, the green LED1 should start blinking.

Debugging the Firmware

PIO Unified Debugger offers the easiest way to debug the board. Firstly, we need to specify debug_tool in "platformio.ini" (Project Configuration File). Since the board has an on-board JLink debug probe we can directly declare it in "platformio.ini" (Project Configuration File):

[env:nrf52_dk]
platform = nordicnrf52
board = nrf52_dk
framework = arduino
debug_tool = jlink


To start the debug session we can use next options: Debug: Start debugging from the top menu, Start Debugging option from Quick Access menu or hotkey button F5: [image]

We need to wait some time while PlatformIO is initializing the debug session and when the first line after the main function is highlighted we are ready to debug: [image]

We can walk through the code using control buttons, set breakpoints, add variables to Watch window: [image]

Writing Unit Tests

Test cases can be added to a single file that may include multiple tests. First of all, in this file, we need to add four default functions: setUp, tearDown, setup and loop. Functions setUp and tearDown are used to initialize and finalize test conditions. Implementations of these functions are not required for running tests but if you need to initialize some variables before you run a test, you use the setUp function and if you need to clean up variables you use tearDown function. In our example we will use these functions to accordingly initialize and deinitialize LED. setup and loop functions act as a simple Arduino program where we describe our test plan.

Let's create test folder in the root of the project and add a new file test_main.cpp to this folder. Next basic tests for String class will be implemented in this file:

  • test_string_concat tests the concatenation of two strings
  • test_string_substring tests the correctness of the substring extraction
  • test_string_index_of ensures that the string returns the correct index of the specified symbol
  • test_string_equal_ignore_case tests case-insensitive comparison of two strings
  • test_string_to_upper_case tests upper-case conversion of the string
  • test_string_replace tests the correctness of the replacing operation

NOTE:

•
2 sec delay is required since the board doesn't support software resetting via Serial.DTR/RTS



#include <Arduino.h>
#include <unity.h>
String STR_TO_TEST;
void setUp(void) {
    // set stuff up here
    STR_TO_TEST = "Hello, world!";
}
void tearDown(void) {
    // clean stuff up here
    STR_TO_TEST = "";
}
void test_string_concat(void) {
    String hello = "Hello, ";
    String world = "world!";
    TEST_ASSERT_EQUAL_STRING(STR_TO_TEST.c_str(), (hello + world).c_str());
}
void test_string_substring(void) {
    TEST_ASSERT_EQUAL_STRING("Hello", STR_TO_TEST.substring(0, 5).c_str());
}
void test_string_index_of(void) {
    TEST_ASSERT_EQUAL(7, STR_TO_TEST.indexOf('w'));
}
void test_string_equal_ignore_case(void) {
    TEST_ASSERT_TRUE(STR_TO_TEST.equalsIgnoreCase("HELLO, WORLD!"));
}
void test_string_to_upper_case(void) {
    STR_TO_TEST.toUpperCase();
    TEST_ASSERT_EQUAL_STRING("HELLO, WORLD!", STR_TO_TEST.c_str());
}
void test_string_replace(void) {
    STR_TO_TEST.replace('!', '?');
    TEST_ASSERT_EQUAL_STRING("Hello, world?", STR_TO_TEST.c_str());
}
void setup()
{
    delay(2000); // service delay
    UNITY_BEGIN();
    RUN_TEST(test_string_concat);
    RUN_TEST(test_string_substring);
    RUN_TEST(test_string_index_of);
    RUN_TEST(test_string_equal_ignore_case);
    RUN_TEST(test_string_to_upper_case);
    RUN_TEST(test_string_replace);
    UNITY_END(); // stop unit testing
}
void loop()
{
}


Now we are ready to upload tests to the board. To do this we can use next options: Test button on PlatformIO Toolbar, Test option from the Project Tasks menu or Tasks: Run Task... > PlatformIO Test from the top menu: [image]

After processing we should see a detailed report about the testing results: [image]

As we can see from the report, all our tests were successful!

Adding Bluetooth LE features

To add the basic BLE functionality to our project we need to define the SoftDevice version and install a library called BLEPeripheral. Both these modifications can be specified in "platformio.ini" (Project Configuration File):

[env:nrf52_dk]
platform = nordicnrf52
board = nrf52_dk
framework = arduino
debug_tool = jlink
; SoftDevice version
build_flags = -DNRF52_S132
lib_deps =
  BLEPeripheral


Now let's create a basic application that can interact with other BLE devices (e.g phone) For example, next code declares a BLE characteristic that controls the state of the LED1.

#include <Arduino.h>
#include <SPI.h>
#include <BLEPeripheral.h>
BLEPeripheral ledPeripheral = BLEPeripheral();
BLEService ledService = BLEService("19b10000e8f2537e4f6cd104768a1214");
BLECharCharacteristic ledCharacteristic = BLECharCharacteristic("19b10001e8f2537e4f6cd104768a1214", BLERead | BLEWrite);
void setup()
{
  pinMode(LED_BUILTIN, OUTPUT);
  ledPeripheral.setAdvertisedServiceUuid(ledService.uuid());
  ledPeripheral.addAttribute(ledService);
  ledPeripheral.addAttribute(ledCharacteristic);
  ledPeripheral.setLocalName("Nordic NRF52 DK");
  ledPeripheral.begin();
}
void loop()
{
  BLECentral central = ledPeripheral.central();
  if (central) {
    while (central.connected()) {
      if (ledCharacteristic.written()) {
        if (ledCharacteristic.value()) {
          digitalWrite(LED_BUILTIN, HIGH);
        }
        else{
          digitalWrite(LED_BUILTIN, LOW);
        }
      }
    }
  }
}


Now we can compile and upload this program to the board as described in previous sections. To verify that our application works as expected, we can use any Android smartphone with BLE feature and Nordic nRF Connect tool.

At first, we need to scan all advertising BLE devices and connect to the device called Nordic NRF52 DK. After a successful connection to the board, we should see one "Unknown Service" with one "Unknown Characteristic" fields: [image]

To switch the LED on or off we just need write 0 or 1 as UINT8 to the BLE characteristic: [image]

Now we have a project template for Nordic nRF52-DK board that we can use as a boilerplate for the next projects.

The goal of this tutorial is to demonstrate how simple it is to use VSCode to develop, run and debug a simple Bluetooth project using Zephyr framework for the Nordic nRF52-DK board.

  • Level: Intermediate
  • Platforms: Windows, Mac OS X, Linux

  • Downloaded and installed VSCode
  • Install drivers for J-LINK debug tool
  • Nordic nRF52-DK development board


  • Setting Up the Project
  • Adding Code to the Generated Project
  • Compiling and Uploading the Firmware
  • Debugging the Firmware
  • Writing Unit Tests
  • Project Inspection
  • Conclusion

Setting Up the Project

1.
Click on "PlatformIO Home" button on the bottom PlatformIO Toolbar:
[image]


2.
Click on "New Project", select Nordic nRF52-DK as the development board, Zephyr as the framework and a path to the project location (or use the default one):
[image]



Adding Code to the Generated Project

1.
Create a new file main.c in src_dir folder and add the following code:

//
// Copyright (c) 2015-2016 Intel Corporation
//
// SPDX-License-Identifier: Apache-2.0
//
#include <zephyr/types.h>
#include <stddef.h>
#include <sys/printk.h>
#include <sys/util.h>
#include <bluetooth/bluetooth.h>
#include <bluetooth/hci.h>
#define DEVICE_NAME CONFIG_BT_DEVICE_NAME
#define DEVICE_NAME_LEN (sizeof(DEVICE_NAME) - 1)
// Set Advertisement data. Based on the Eddystone specification:
// https://github.com/google/eddystone/blob/master/protocol-specification.md
// https://github.com/google/eddystone/tree/master/eddystone-url
static const struct bt_data ad[] = {
    BT_DATA_BYTES(BT_DATA_FLAGS, BT_LE_AD_NO_BREDR),
    BT_DATA_BYTES(BT_DATA_UUID16_ALL, 0xaa, 0xfe),
    BT_DATA_BYTES(BT_DATA_SVC_DATA16,
              0xaa, 0xfe,
              0x10, // Eddystone-URL frame type
              0x00, // Calibrated Tx power at 0m
              0x00, // URL Scheme Prefix http://www.
              'z', 'e', 'p', 'h', 'y', 'r',
              'p', 'r', 'o', 'j', 'e', 'c', 't',
              0x08) // .org
};
// Set Scan Response data
static const struct bt_data sd[] = {
    BT_DATA(BT_DATA_NAME_COMPLETE, DEVICE_NAME, DEVICE_NAME_LEN),
};
static void bt_ready(int err)
{
    if (err) {
        printk("Bluetooth init failed (err %d)\n", err);
        return;
    }
    printk("Bluetooth initialized\n");
    // Start advertising
    err = bt_le_adv_start(BT_LE_ADV_NCONN, ad, ARRAY_SIZE(ad),
                  sd, ARRAY_SIZE(sd));
    if (err) {
        printk("Advertising failed to start (err %d)\n", err);
        return;
    }
    printk("Beacon started\n");
  }
void main(void)
{
    int err;
    printk("Starting Beacon Demo\n");
    // Initialize the Bluetooth Subsystem
    err = bt_enable(bt_ready);
    if (err) {
        printk("Bluetooth init failed (err %d)\n", err);
    }
}




2.
By default Bluetooth feature is disabled, we can enable it by creating a new file prj.conf in zephyr folder and adding the following lines:

CONFIG_BT=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_DEVICE_NAME="Test beacon"





Compiling and Uploading the Firmware

1.
To compile the project use one of the following options:
  • Build option from the Project Tasks menu
  • Build button in PlatformIO Toolbar
  • Task Menu Tasks: Run Task... > PlatformIO: Build or in PlatformIO Toolbar
  • Command Palette View: Command Palette > PlatformIO: Build
  • Hotkeys cmd-alt-b / ctrl-alt-b:

[image]


2.
If everything went well, we should see a successful result message in the terminal window:
[image]


3.
To upload the firmware to the board we can use the following options:
  • Upload option from the Project Tasks menu
  • Upload button in PlatformIO Toolbar
  • Command Palette View: Command Palette > PlatformIO: Upload
  • Task Menu Tasks: Run Task... > PlatformIO: Upload
  • Hotkeys cmd-alt-u / ctrl-alt-u:

[image]


4.
Connect the board to your computer and update the default monitor speed to 115200 in platformio.ini file:

[env:hifive1-revb]
platform = sifive
board = hifive1-revb
framework = zephyr
monitor_speed = 115200




5.
Open Serial Monitor to observe the output from the board:
[image]


6.
If everything went well, the board should be visible as a beacon:
[image]



Debugging the Firmware

Since Nordic nRF52-DK includes an onboard debug probe we can use PIO Unified Debugger without any configuration.

1.
To start a debug session we can use the following options:
  • Debug: Start debugging from the top menu
  • Start Debugging option from Quick Access menu
  • Hotkey button F5:

[image]


2.
We can walk through the code using control buttons, set breakpoints, add variables to Watch window:
[image]



Writing Unit Tests

NOTE:

Functions setUp and tearDown are used to initialize and finalize test conditions. Implementations of these functions are not required for running tests but if you need to initialize some variables before you run a test, you use the setUp function and if you need to clean up variables you use tearDown function.


For the sake of simplicity, let's create a small library called calculator, implement several basic functions add, sub, mul, div and test them using PIO Unit Testing engine.

1.
PlatformIO uses a unit testing framework called Unity. Unity is not compatible with C library implemented in the framework. Let's enable standard version of newlib C library in prj.conf file using the following config:

CONFIG_NEWLIB_LIBC=y




2.
Create a new folder calculator in the lib folder and add two new files calculator.h and calculator.c with the following contents:
calculator.h: 

#ifndef _CALCULATOR_H_
#define _CALCULATOR_H_
#ifdef __cplusplus
extern "C" {
#endif
int add (int a, int b);
int sub (int a, int b);
int mul (int a, int b);
int div (int a, int b);
#ifdef __cplusplus
}
#endif
#endif // _CALCULATOR_H_


calculator.c:

#include "calculator.h"
int add(int a, int b)
{
    return a + b;
}
int sub(int a, int b)
{
    return a - b;
}
int mul(int a, int b)
{
    return a * b;
}




3.
Create a new file `test_calc.c to the folder test and add basic tests for calculator library:

#include <calculator.h>
#include <unity.h>
void test_function_calculator_addition(void) {
    TEST_ASSERT_EQUAL(32, add(25, 7));
}
void test_function_calculator_subtraction(void) {
    TEST_ASSERT_EQUAL(20, sub(23, 3));
}
void test_function_calculator_multiplication(void) {
    TEST_ASSERT_EQUAL(50, mul(25, 2));
}
void test_function_calculator_division(void) {
    TEST_ASSERT_EQUAL(32, div(100, 3));
}
void main() {
    UNITY_BEGIN();
    RUN_TEST(test_function_calculator_addition);
    RUN_TEST(test_function_calculator_subtraction);
    RUN_TEST(test_function_calculator_multiplication);
    RUN_TEST(test_function_calculator_division);
    UNITY_END();
}




4.
Let's run tests on the board and check the results. There should be a problem with test_function_calculator_division test:
[image]


5.
Let's fix the incorrect expected value, run tests again. After processing the results should be correct:
[image]



Project Inspection

For illustrative purposes, let's imagine we need to find a function with the biggest memory footprint. Also, let's introduce a bug to our project so PIO Check can report it.

1.
Open PlatformIO Home and navigate to Inspect section, select the current project and press Inspect button:
[image]


2.
Project statistics:
[image]


3.
The biggest function:
[image]


4.
Possible bugs:
[image]



Now we have a project template for Nordic Nordic nRF52-DK board that we can use as a boilerplate for the next projects.

RISC-V ASM Video Tutorial

An introduction to using SiFive and Assembly language on the SiFive HiFive1 by Martin Fink, Chief Technology Officer at Western Digital.

A demo source code is published on Github: https://github.com/martin-robert-fink/superBlink.git

It is already pre-configured PlatformIO project:

  • Clone it or download
  • Open in VSCode
  • Happy coding and debugging!

.INDENT 0.0

  • Part 1 of 12 | Introduction
  • Part 2 of 12 | Setting Up
  • Part 3 of 12 | Tour PlatformIO
  • Part 4 of 12 | C Code Wrapper
  • Part 5 of 12 | HiFive Docs
  • Part 6 of 12 | Understanding GPIO
  • Part 7 of 12 | setupGPIO
  • Part 8 of 12 | Debug setupGPIO
  • Part 9 of 12 | setLED
  • Part 10 of 12 | Debug setLED
  • Part 11 of 12 | Delay
  • Part 12 of 12 | Final and Conclusion


Project Examples

Pre-configured projects with source code are located in PlatformIO Examples repository.

•
PlatformIO DIY Projects & Tutorials at Hackster.io

  • PlatformIO Video Collection on YouTube
  • Next-generation IDE for your RISC-V Product in 20 Minutes by CEO of PlatformIO
  • Use the PlatformIO Debugger on the ESP32 Using an ESP-prog
  • RISC-V ASM Tutorial
  • PlatformIO for Arduino, ESP8266, and ESP32 Tutorial
  • Free Inline Debugging for ESP32 and Arduino Sketches
  • PlatformIO или прощай, Arduino IDE
  • Отладка ESP32 в PlatformIO
  • A Better Arduino IDE - Getting Started with PlatformIO
  • PlatformIO - Using External Libraries

Each PlatformIO project has a configuration file named platformio.ini in the root directory for the project. This is a INI-style file.

platformio.ini has sections (each denoted by a [header]) and key / value pairs within the sections. Lines beginning with ; are ignored and may be used to provide comments.

Multiple value options can be specified in two ways:

1.
Split values with ", " (comma + space)
2.
Multi-line format, where each new line starts with at least two spaces

There are two required sections:

  • PlatformIO Core (CLI) settings: Section [platformio]
  • Environment settings: Section [env]

The other sections are optional to include. Here are the allowed sections and their allowed contents:

Section [platformio]

•
Generic options
  • description
  • default_envs
  • extra_configs

•
Directory options
  • core_dir
  • globallib_dir
  • platforms_dir
  • packages_dir
  • cache_dir
  • build_cache_dir
  • workspace_dir
  • build_dir
  • libdeps_dir
  • include_dir
  • src_dir
  • lib_dir
  • data_dir
  • test_dir
  • boards_dir
  • shared_dir


The platform.ini platformio section is used for overriding the default configuration options for PlatformIO Core (CLI).

NOTE:

Relative path is allowed for directory option:
  • ~ will be expanded to user's home directory
  • ../ or ..\ go up to one folder

There is a $PROJECT_HASH template variable. You can use it in a directory path. It will by replaced by a SHA1[0:10] hash of the full project path. This is very useful to declare a global storage for project workspaces. For example, /tmp/pio-workspaces/$PROJECT_HASH (Unix) or $[sysenv.TEMP}/pio-workspaces/$PROJECT_HASH (Windows). You can set a global workspace directory using the system environment variable PLATFORMIO_WORKSPACE_DIR.

See the available directory ***_dir options below.



description

Type: String | Multiple: No

Short description of the project. PlatformIO uses it for PlatformIO Home in the multiple places.

default_envs

Type: String | Multiple: Yes

The platformio run command processes all environments [env:***] by default if the platformio run --environment option is not specified. default_envs allows one to define which environments that should be processed by default.

Also, PIO Unified Debugger checks this option when looking for debug environment.

This option can also be configured by the global environment variable PLATFORMIO_DEFAULT_ENVS.

Example:

[platformio]
default_envs = uno, nodemcu
[env:uno]
platform = atmelavr
framework = arduino
board = uno
[env:nodemcu]
platform = espressif8266
framework = arduino
board = nodemcu
[env:teensy31]
platform = teensy
framework = arduino
board = teensy31
[env:lpmsp430g2553]
platform = timsp430
framework = arduino
board = lpmsp430g2553
build_flags = -D LED_BUILTIN=RED_LED


extra_configs

New in version 4.0.

Type: String (Pattern) | Multiple: Yes

This option allows extending a base "platformio.ini" (Project Configuration File) with extra configuration files. The format and rules are the same as for the "platformio.ini" (Project Configuration File). A name of the configuration file can be any.

extra_configs can be a single path to an extra configuration file or a list of them. Please note that you can use Unix shell-style wildcards:

Pattern Meaning
* matches everything
? matches any single character
[seq] matches any character in seq
[!seq] matches any character not in seq

NOTE:

If you declare the same pair of "group" + "option" in an extra configuration file which was previously declared in a base "platformio.ini" (Project Configuration File), it will be overwritten with a value from extra configuration.


Example

Base "platformio.ini"

[platformio]
extra_configs =
  extra_envs.ini
  extra_debug.ini
; Global data for all [env:***]
[env]
platform = espressif32
framework = espidf
; Custom data group
; can be use in [env:***] via ${common.***}
[common]
debug_flags = -D RELEASE
lib_flags = -lc -lm
[env:esp-wrover-kit]
board = esp-wrover-kit
build_flags = ${common.debug_flags}


"extra_envs.ini"

[env:esp32dev]
board = esp32dev
build_flags = ${common.lib_flags} ${common.debug_flags}
[env:lolin32]
platform = espressif32
framework = espidf
board = lolin32
build_flags = ${common.debug_flags}


"extra_debug.ini"

# Override base "common.debug_flags"
[common]
debug_flags = -D DEBUG=1
[env:lolin32]
build_flags = -Og


After a parsing process, configuration state will be the next:

[common]
debug_flags = -D DEBUG=1
lib_flags = -lc -lm
[env:esp-wrover-kit]
platform = espressif32
framework = espidf
board = esp-wrover-kit
build_flags = ${common.debug_flags}
[env:esp32dev]
platform = espressif32
framework = espidf
board = esp32dev
build_flags = ${common.lib_flags} ${common.debug_flags}
[env:lolin32]
platform = espressif32
framework = espidf
board = lolin32
build_flags = -Og


core_dir

New in version 4.0.

Type: DirPath | Multiple: No

The core_dir variable points out the directory used for all development platform packages (toolchains, frameworks, SDKs, upload and debug tools), global libraries for Library Dependency Finder (LDF), and other PlatformIO Core service data. The size of this folder will depend on the number of installed development platforms.

The default value is the user's home directory:

  • Unix ~/.platformio
  • Windows %HOMEPATH%\.platformio

This option can also be configured by the global environment variable PLATFORMIO_CORE_DIR.

Example:

[platformio]
core_dir = /path/to/custom/pio-core/storage


globallib_dir

New in version 4.0.

Type: DirPath | Multiple: No | Default: "core_dir/lib"

Global library storage for PlatfrmIO projects and Library Manager where Library Dependency Finder (LDF) looks for dependencies.

This option can also be configured by the global environment variable PLATFORMIO_GLOBALLIB_DIR.

platforms_dir

New in version 4.0.

Type: DirPath | Multiple: No | Default: "core_dir/platforms"

Global storage where PlatformIO Package Manager installs Development Platforms.

This option can also be configured by the global environment variable PLATFORMIO_PLATFORMS_DIR.

packages_dir

New in version 4.0.

Type: DirPath | Multiple: No | Default: "core_dir/packages"

Global storage where PlatformIO Package Manager installs Development Platforms dependencies (toolchains, Frameworks, SDKs, upload and debug tools).

This option can also be configured by the global environment variable PLATFORMIO_PACKAGES_DIR.

cache_dir

New in version 4.0.

Type: DirPath | Multiple: No | Default: "core_dir/cache"

PlatformIO Core (CLI) uses this folder to store caching information (requests to PlatformIO Registry, downloaded packages and other service information).

To reset a cache, please run platformio update command.

This option can also be configured by the global environment variable PLATFORMIO_CACHE_DIR.

build_cache_dir

New in version 4.0.

Type: DirPath | Multiple: No | Default: None (Disabled)

PlatformIO Core (CLI) uses this folder to store derived files from a build system (objects, firmwares, ELFs). These files are shared between all build environments. To speed up a build process, you can use the same cache folder between different projects if they depend on the same development platform and framework.

This option can also be configured by the global environment variable PLATFORMIO_BUILD_CACHE_DIR.

The example of "platformio.ini" (Project Configuration File) below instructs PlatformIO Build System to check build_cache_dir for already compiled objects for STM32Cube and project source files. The cached object will not be used if the original source file was modified or build environment has a different configuration (new build flags, etc):

[platformio]
; Set a path to a cache folder
build_cache_dir =
; Examples:
; (Unix) build_cache_dir = /path/to/cache/folder
; (Windows) build_cache_dir = C:/path/to/cache/folder
[env:bluepill_f103c6]
platform = ststm32
framework = stm32cube
board = bluepill_f103c6
[env:nucleo_f411re]
platform = ststm32
framework = stm32cube
board = nucleo_f411re


workspace_dir

New in version 4.0.

Type: DirPath | Multiple: No | Default: "Project/.pio"

The path to a project workspace directory where PlatformIO keeps by default compiled objects, static libraries, firmwares, and external library dependencies. It is used by these options:

  • build_dir
  • libdeps_dir.

The default value is .pio and means that folder is located in the root of project.

This option can also be configured by the global environment variable PLATFORMIO_WORKSPACE_DIR.

build_dir

WARNING:

PLEASE DO NOT EDIT FILES IN THIS FOLDER. PlatformIO will overwrite your changes on the next build. THIS IS A CACHE DIRECTORY.


Type: DirPath | Multiple: No | Default: "workspace_dir/build"

PlatformIO Build System uses this folder for project environments to store compiled object files, static libraries, firmwares and other cached information. It allows PlatformIO to build source code extremely fast!

You can delete this folder without any risk! If you modify "platformio.ini" (Project Configuration File), then PlatformIO will remove this folder automatically. It will be created on the next build operation.

This option can also be configured by the global environment variable PLATFORMIO_BUILD_DIR.

NOTE:

If you have any problems with building your project environments which are defined in "platformio.ini" (Project Configuration File), then TRY TO DELETE this folder. In this situation you will remove all cached files without any risk. Also, you can use "clean" target for platformio run --target command.


libdeps_dir

Type: DirPath | Multiple: No | Default: "workspace_dir/libdeps"

Internal storage where Library Manager will install project dependencies (lib_deps).

This option can also be configured by the global environment variable PLATFORMIO_LIBDEPS_DIR.

include_dir

Type: DirPath | Multiple: No | Default: "Project/include"

The path to project's default header files. PlatformIO uses it for the platformio run command. The default value is include meaning an include directory located under the root directory of the project. This path will be added to CPPPATH of the build environment.

If you need to add extra include directories to CPPPATH scope, please use build_flags with -I /path/to/extra/dir option.

This option can also be configured by the global environment variable PLATFORMIO_INCLUDE_DIR.

src_dir

Type: DirPath | Multiple: No | Default: "Project/src"

The path to the project's directory with source code. PlatformIO uses it for the platformio run command. The default value is src meaning a src directory located in the root directory of the project.

This option can also be configured by the global environment variable PLATFORMIO_SRC_DIR.

NOTE:

This option is useful for people who migrate from Arduino IDE where the source directory should have the same name as the main source file. See example project with own source directory.


lib_dir

Type: DirPath | Multiple: No | Default: "Project/lib"

You can put your own/private libraries here. The source code of each library should be placed in separate directory, like lib/private_lib/[here are source files]. This directory has the highest priority for Library Dependency Finder (LDF).

The default value is lib, meaning a lib directory located in the root of the project.

This option can also be configured by the global environment variable PLATFORMIO_LIB_DIR.

For example, see how the Foo and Bar libraries are organized:

|--lib
|  |--Bar
|  |  |--docs
|  |  |--examples
|  |  |--src
|  |     |- Bar.c
|  |     |- Bar.h
|  |--Foo
|  |  |- Foo.c
|  |  |- Foo.h
|- platformio.ini
|--src
   |- main.c


Then in src/main.c you should use:

#include <Foo.h>
#include <Bar.h>
// rest of H/C/CPP code


PlatformIO will find your libraries automatically, configure the preprocessor's include paths and build them.

data_dir

Type: DirPath | Multiple: No | Default: "Project/data"

Data directory to store contents and Uploading files to file system SPIFFS. The default value is data that means that folder is located in the root of the project.

This option can also be configured by the global environment variable PLATFORMIO_DATA_DIR.

test_dir

Type: DirPath | Multiple: No | Default: "Project/test"

The directory where PIO Unit Testing engine will look for the tests. The default value is test, meaning a test directory located in the root of the project.

This option can also be configured by the global environment variable PLATFORMIO_TEST_DIR.

boards_dir

Type: DirPath | Multiple: No | Default: "Project/boards"

The location of project-specific board definitions. Each project may choose a suitable directory name. The default value is boards, meaning a "boards" directory located in the root of the project.

By default, PlatformIO looks for boards in this order:

1.
Project boards_dir (as defined by this setting)
2.
Global core_dir/boards
3.
Development platform core_dir/platforms/*/boards.

This option can also be configured by the global environment variable PLATFORMIO_BOARDS_DIR.

shared_dir

New in version 4.0.

Type: DirPath | Multiple: No | Default: "Project/shared"

PIO Remote uses this folder to synchronize extra files between remote machine. For example, you can share extra_scripts.

Please note that these folders are automatically shared between remote machine with platformio remote run --force-remote or platformio remote test --force-remote commands:

  • lib_dir
  • include_dir
  • src_dir
  • boards_dir
  • data_dir
  • test_dir

The default value is shared, meaning a directory named "shared" located in the root of the project.

This option can also be configured by the global environment variable PLATFORMIO_SHARED_DIR.

Section [env]

  • Common [env]
  • Environment [env:NAME]
  • Options

Each project may have multiple configuration environments defining the available project tasks for building, programming, debugging, unit testing, device monitoring, library dependencies, etc. The configuration environments are declared using [env] sections in "platformio.ini" (Project Configuration File).

The allowed options are listed under Options.

New in version 4.0.

An optional configuration environment with common options that will be shared between all [env:NAME] environments in the platform.ini file. It is very useful if the configuration file has a lot of environments [env:NAME] and they share common settings.

For example:

[env]
platform = ststm32
framework = stm32cube
board = nucleo_l152re
lib_deps = Dep1, Dep2
[env:release]
build_flags = -D RELEASE
lib_deps =
    ${env.lib_deps}
    Dep3
[env:debug]
build_type = debug
build_flags = -D DEBUG
lib_deps = DepCustom


In this example we have two configuration environments release and debug. This is equivalent to duplicating all options as shown below:

[env:release]
platform = ststm32
framework = stm32cube
board = nucleo_l152re
build_flags = -D RELEASE
lib_deps = Dep1, Dep2, Dep3
[env:debug]
platform = ststm32
framework = stm32cube
board = nucleo_l152re
build_type = debug
build_flags = -D DEBUG
lib_deps = DepCustom


A section with an env: prefix defines a working environment for platformio run, platformio test, platformio check, platformio debug and other commands. Multiple [env:NAME] environments with different NAME are allowed. Every project must define at least one working environment.

Each environment must have a unique NAME. The valid chars for NAME are letters a-z, numbers 0-9, special char _ (underscore). For example, [env:hello_world].

If you have multiple working environments and you need to process only a few of them, the commands mentioned above accept the -e, --environment option to select a subset of the working environments to process. The [platformio] default_envs option can be used to define a default set of working environments for the commands to process.

  • platform
  • platform_packages
  • framework
  • board
  • board_build.mcu
  • board_build.f_cpu
  • board_build.ldscript
  • More options

platform

Type: String | Multiple: No

Development Platforms name.

PlatformIO allows one to use specific version of platform using Semantic Versioning (X.Y.Z=MAJOR.MINOR.PATCH) or VCS (Git, Mercurial and Subversion).

Version specifications can take any of the following forms:

  • 1.2.3: an exact version number. Use only this exact version
  • ^1.2.3: any compatible version (exact version for 1.x.x versions)
  • ~1.2.3: any version with the same major and minor versions, and an equal or greater patch version
  • >1.2.3: any version greater than 1.2.3. >=, <, and <= are also possible
  • >0.1.0,!=0.2.0,<0.3.0: any version greater than 0.1.0, not equal to 0.2.0 and less than 0.3.0

Other forms are the same as for the platformio platform install command.

Examples:

[env:the_latest_version]
platform = atmelavr
[env:exact_version]
platform = atmelavr@1.2.3
[env:specific_major_version]
platform = atmelavr@^1.2.3
[env:specific_major_and_minor_version]
platform = atmelavr@~1.2.3
[env:development_verion_by_git]
platform = https://github.com/platformio/platform-ststm32.git
[env:custom_git_branch]
platform = https://github.com/platformio/platform-espressif8266.git#feature/stage
[env:specific_git_commit]
platform = https://github.com/platformio/platform-espressif8266.git#921855a9c530082efddb5d48b44c3f4be0e2dfa2


platform_packages

New in version 4.0.

Type: String | Multiple: Yes

Configure custom packages per a build environment. You can also override default packages by Development Platforms using the same name. Packages will be installed in packages_dir.

Examples:

[env:override_default_toolchain]
platform = atmelavr
platform_packages =
  ; use GCC AVR 5.0+
  toolchain-gccarmnoneeabi@>1.50000.0
[env:override_framework]
platform = espressif8266
platform_packages =
  ; use upstream Git version
  framework-arduinoespressif8266 @ https://github.com/esp8266/Arduino.git
[env:external_package]
platform = ststm32
platform_packages =
  ; latest openOCD from PlatformIO Package Registry
  tool-openocd
  ; source code of ST-Link
  tool-stlink-source @ https://github.com/texane/stlink.git


framework

Type: String | Multiple: Yes

Frameworks name.

board

Type: String (ID) | Multiple: No

PlatformIO has pre-configured settings for the most popular boards:

  • build configuration
  • upload configuration
  • debugging configuration
  • connectivity information, etc.

You can find a valid board ID in Boards catalog, Boards Explorer or platformio boards command.

board_build.mcu

Type: String | Multiple: No

board_build.mcu is a microcontroller(MCU) type that is used by compiler to recognize MCU architecture. The correct type of board_build.mcu depends on platform library. For example, the list of board_build.mcu for "megaAVR Devices" is described here.

The full list of board_build.mcu for the popular embedded platforms you can find in Boards section of Development Platforms. See "Microcontroller" column.

board_build.f_cpu

Type: Integer | Multiple: No

The option board_build.f_cpu is used to define MCU frequency (Hertz, Clock). A format of this option is C-like long integer value with L suffix. The 1 Hertz is equal to 1L, then 16 MHz (Mega Hertz) is equal to 16000000L.

The full list of board_build.f_cpu for the popular embedded platforms you can find in Boards section of Development Platforms. See "Frequency" column. You can overclock a board by specifying a board_build.f_cpu value other than the default.

board_build.ldscript

Type: String | Multiple: No

Path to the linker script to be used instead of the one defined by a framework. This is useful for specifying a modified linker script, for example, when an application requires a special memory section for a bootloader.

You can override any board option declared in manifest file using the next format board_{OBJECT.PATH}, where {OBJECT.PATH} is an object path in JSON manifest. Please navigate to "boards" folder of PlatfomIO development platforms and open JSON file to list all available options.

For example, Manifest: Espressif ESP32 Dev Module:

[env:custom_board_options]
; Custom CPU Frequency
board_build.f_cpu = 160000000L
; Custom FLASH Frequency
board_build.f_flash = 80000000L
; Custom FLASH Mode
board_build.flash_mode = qio
; Custom linker script
board_build.ldscript = /path/to/ldscript.ld
; Custom maximum program size
board_upload.maximum_size = 1310720


  • build_type
  • build_flags
  • Built-in Variables
  • Dynamic build flags

  • src_build_flags
  • build_unflags
  • src_filter
  • targets

build_type

New in version 4.0.

Type: String | Multiple: No | Default: release

See extended documentation for Build Configurations.

build_flags

Type: String | Multiple: Yes

These flags/options affect the preprocessing, compilation, assembly and linking processes for C and C++ code. All compiler and linker flags can be used. Here is a list of some common options.

In spite of the name, CPPDEFINES rows also applies to the C compiler.

Format Affects build variable Description
-D name CPPDEFINES Predefine name as a macro, with definition 1.
-D name=definition CPPDEFINES The contents of definition are tokenized and processed as if they appeared during translation phase three in a #define directive.
-U name CPPDEFINES Cancel any previous definition of name, either built in or provided with a -D option.
-Wp,option CPPFLAGS Bypass the compiler driver and pass option directly through to the preprocessor
-Wall CCFLAGS Turn on all optional warnings which are desirable for normal code.
-Werror CCFLAGS Make all warnings into hard errors. With this option, if any source code triggers warnings, the compilation will be aborted.
-w CCFLAGS Suppress all warnings, including those which GNU CPP issues by default.
-include file CCFLAGS Process file as if #include "file" appeared as the first line of the primary source file.
-Idir CPPPATH Add the directory dir to the list of directories to be searched for header files.
-Wa,option ASFLAGS, CCFLAGS Pass option as an option to the assembler. If option contains commas, it is split into multiple options at the commas.
-Wl,option LINKFLAGS Pass option as an option to the linker. If option contains commas, it is split into multiple options at the commas.
-llibrary LIBS Search the library named library when linking
-Ldir LIBPATH Add directory dir to the list of directories to be searched for -l.

This option can also be set by global environment variable PLATFORMIO_BUILD_FLAGS.

For more detailed information about available flags/options go to:

  • Options to Request or Suppress Warnings
  • Options for Debugging Your Program
  • Options That Control Optimization
  • Options Controlling the Preprocessor
  • Passing Options to the Assembler
  • Options for Linking
  • Options for Directory Search

Examples:

[env:specific_defines]
build_flags =
  -DFOO -DBAR=1
  -D BUILD_ENV_NAME=$PIOENV
  -D CURRENT_TIME=$UNIX_TIME
  -DFLOAT_VALUE=1.23457e+07
[env:string_defines]
build_flags =
  -DHELLO="World!"
  '-DWIFI_PASS="My password"'
  ; Password with special chars: My pass'word
  -DWIFI_PASS=\"My\ pass\'word\"
[env:specific_inclibs]
build_flags =
  -I/opt/include
  -L/opt/lib
  -lfoo
[env:ignore_incremental_builds]
; We dynamically change the value of "LAST_BUILD_TIME" macro,
; PlatformIO will not cache objects
build_flags = -DLAST_BUILD_TIME=$UNIX_TIME


NOTE:

If you need to control build flags that are specific for debug configuration please refer to debug_build_flags.


You can inject the built-in variables into your build flags, such as:

  • $PYTHONEXE, full path to current Python interpreter
  • $UNIX_TIME, current time in Unix format
  • $PIOENV, name of build environment from "platformio.ini" (Project Configuration File)
  • $PIOPLATFORM, name of development platform
  • $PIOFRAMEWORK, a list of frameworks
  • $PROJECT_DIR, project directory
  • $PROJECT_CORE_DIR, PlatformIO Core directory, see core_dir
  • $PROJECT_BUILD_DIR, project build directory per all environments
  • $BUILD_DIR, build directory per current environment

See the full list of PlatformIO variables.

Please use target envdump for the platformio run --target command to see ALL variable values for a build environment.

PlatformIO allows users to run an external command/script which outputs build flags into STDOUT by prepending the shell command with a ! character. PlatformIO will automatically replace commands with their output when appending flags to build environments.

You can use any shell or programming language.

This external command will be called on each platformio run command before building/uploading process.

Use cases:

  • Macro with the latest VCS revision/tag "on-the-fly"
  • Generate dynamic headers (*.h)
  • Process media content before generating SPIFFS image
  • Make some changes to source code or related libraries



NOTE:

If you need more advanced control and would like to apply changes to a PlatformIO Build System environment, please refer to Advanced Scripting.


Example:

[env:generate_flags_with_external_command]
build_flags = !cmd_or_path_to_script
; Unix only, get output from internal command
build_flags = !echo "-DSOME_MACRO="$(some_cmd arg1 --option1)


Use Case: Create a "PIO_SRC_REV" macro with the latest Git revision

This example includes a separate file named git_rev_macro.py, to be placed in the same directory as platformio.ini.

platformio.ini:

[env:git_revision_macro]
build_flags = !python git_rev_macro.py


git_rev_macro.py:

import subprocess
revision = subprocess.check_output(["git", "rev-parse", "HEAD"]).strip()
print("-DPIO_SRC_REV=%s" % revision)


src_build_flags

Type: String | Multiple: Yes

An option src_build_flags has the same behavior as build_flags but will be applied only for project source files in the src_dir directory.

This option can also be set by the global environment variable PLATFORMIO_SRC_BUILD_FLAGS.

build_unflags

Type: String | Multiple: Yes

Selectively remove base/initial flags that were set by the development platform.

[env:unflags]
build_unflags = -Os -std=gnu++11
build_flags = -O2


src_filter

Type: String (Templates) | Multiple: Yes

This option allows one to specify which source files should be included or excluded from src_dir for a build process. Filter supports two templates:

  • +<PATH> include template
  • -<PATH> exclude template

PATH is relative to src_dir. All patterns will be applied in their order of definition. GLOB Patterns are allowed.

By default, src_filter is predefined to +<*> -<.git/> -<.svn/> -<example/> -<examples/> -<test/> -<tests/>, meaning "include ALL files, then exclude the .git and svn repository folders and the example ... folder.

This option can also be set by the global environment variable PLATFORMIO_SRC_FILTER.

targets

Type: String | Multiple: Yes

A list of targets which will be processed by the platformio run command by default. You can enter more than one target, if separated by comma+space ", ".

The list with available targets is located in platformio run --target.

Examples

1.
Build a project using Release Configuration, upload the firmware, and start Serial Monitor automatically:

[env:upload_and_monitor]
targets = upload, monitor




2.
Build a project using Debug Configuration.

Tip! You can use these targets like an option to platformio run --target command. For example:

# clean project
platformio run -t clean
# dump current build environment
platformio run --target envdump


When no targets are defined, PlatformIO will build only sources by default.

SEE ALSO:

Please make sure to read Library Dependency Finder (LDF) guide first.


  • lib_deps
  • lib_ignore
  • lib_extra_dirs
  • lib_ldf_mode
  • lib_compat_mode
  • lib_archive

lib_deps

SEE ALSO:

Please make sure to read Library Dependency Finder (LDF) guide first.


Type: String | Multiple: Yes

Specify project dependencies that should be installed automatically to libdeps_dir before environment processing.

If you have multiple build environments that depend on the same libraries, you can use Dynamic variables to use common configuration.

Valid forms

; one line definition (comma + space)
[env:myenv]
lib_deps = LIBRARY_1, LIBRARY_2, LIBRARY_N
; multi-line definition
[env:myenv2]
lib_deps =
  LIBRARY_1
  LIBRARY_2
  LIBRARY_N


The each line with LIBRARY_1... LIBRARY_N will be passed automatically to platformio lib install command. Please follow to platformio lib install for detailed documentation about possible values.

Example:

[env:myenv]
lib_deps =
  13
  PubSubClient
  ArduinoJson@~5.6,!=5.4
  https://github.com/gioblu/PJON.git#v2.0
  me-no-dev/ESPAsyncTCP
  IRremoteESP8266=https://github.com/markszabo/IRremoteESP8266/archive/master.zip


lib_ignore

SEE ALSO:

Please make sure to read Library Dependency Finder (LDF) guide first.


Type: String | Multiple: Yes

Specify libraries which should be ignored by Library Dependency Finder.

The correct value for this option is a library name (not folder name). You will see these names in "Library Dependency Graph" when building a project between < and > symbols.

Example:

Build output

...
Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF MODES: FINDER(chain+) COMPATIBILITY(soft)
Collected 54 compatible libraries
Scanning dependencies...
Dependency Graph
|-- <Hash> v1.0
|-- <AsyncMqttClient> v0.8.2
|   |-- <ESPAsyncTCP> v1.1.3
|-- <ESP8266WiFi> v1.0
|-- <ESP Async WebServer> v1.1.1
|   |-- <ESPAsyncTCP> v1.1.3
|   |-- <ESP8266WiFi> v1.0
|   |-- <Hash> v1.0
|   |-- <ArduinoJson> v5.13.1
|-- <ArduinoJson> v5.13.1
|-- <DNSServer> v1.1.0
|   |-- <ESP8266WiFi> v1.0
|-- <Ticker> v1.0
....


platformio.ini

[env:myenv]
; Single line
lib_ignore = AsyncMqttClient, DNSServer
; Multi-line
lib_ignore =
  AsyncMqttClient
  ESP Async WebServer


lib_extra_dirs

SEE ALSO:

Please make sure to read Library Dependency Finder (LDF) guide first.


Type: DirPath | Multiple: Yes

A list with extra directories/storages where Library Dependency Finder (LDF) will look for dependencies.

This option can also be set by global environment variable PLATFORMIO_LIB_EXTRA_DIRS.

WARNING:

This is a not direct path to a library with source code. It should be a path to storage that contains libraries grouped by folders. For example, D:\PlatformIO\extra\libraries but not D:\PlatformIO\extra\libraries\FooLibrary.


Example:

[env:myenv]
lib_extra_dirs =
    /common/libraries
    /iot/libraries


lib_ldf_mode

SEE ALSO:

Please make sure to read Library Dependency Finder (LDF) guide first.


Type: String | Multiple: No | Default: chain

This option specifies how does Library Dependency Finder should analyze dependencies (#include directives). See Dependency Finder Mode for details and available options.

Example:

[env:myenv]
; evaluate C/C++ Preprocessor conditional syntax
lib_ldf_mode = chain+


lib_compat_mode

SEE ALSO:

Please make sure to read Library Dependency Finder (LDF) guide first.


Type: String | Multiple: No | Default: soft

Library compatibility mode allows one to control strictness of Library Dependency Finder. See Compatibility Mode for details and available options..

By default, this value is set to lib_compat_mode = soft and means that LDF will check only for framework compatibility.

Example:

[env:myenv]
; Checks for the compatibility with frameworks and dev/platforms
lib_compat_mode = strict


lib_archive

Type: Bool (yes or no) | Multiple: No | Default: yes

Create an archive (*.a, static library) from the object files and link it into a firmware (program). This is default behavior of PlatformIO Build System (lib_archive = yes).

Setting lib_archive = no will instruct PIO Build System to link object files directly (in-line). This could be useful if you need to override weak symbols defined in framework or other libraries.

You can disable library archiving per a custom library using libArchive field in library.json manifest.

Example:

[env:myenv]
lib_archive = no


  • upload_port
  • upload_protocol
  • upload_speed
  • upload_flags
  • upload_resetmethod
  • upload_command

upload_port

Type: String (Pattern) | Multiple: No

This option is used by "uploader" tool when sending firmware to board via upload_port. For example,

  • /dev/ttyUSB0 - Serial port (Unix-based OS)
  • COM3 - Serial port (Windows OS)
  • 192.168.0.13 - IP address when using OTA
  • /media/disk - physical path to media disk/flash drive (Mbed enabled boards)
  • D: - physical path to media disk/flash drive (Windows OS).

If upload_port isn't specified, then PlatformIO will try to detect it automatically.

To print all available serial ports please use platformio device list command.

This option can also be set by global environment variable PLATFORMIO_UPLOAD_PORT.

Please note that you can use Unix shell-style wildcards:

Pattern Meaning
* matches everything
? matches any single character
[seq] matches any character in seq
[!seq] matches any character not in seq

Example

[env:uno]
platform = atmelavr
framework = arduino
; any port that starts with /dev/ttyUSB
upload_port = /dev/ttyUSB*
; COM1 or COM3
upload_port = COM[13]


upload_protocol

Type: String | Multiple: No

A protocol that "uploader" tool uses to talk to a board. Please check Boards for supported uploading protocols by your board.

upload_speed

Type: Integer | Multiple: No

A connection speed (baud rate) which "uploader" tool uses when sending firmware to board.

upload_flags

Type: String | Multiple: Yes

Extra flags for uploader. Will be added to the end of uploader command. If you need to override uploader command or base flags please use extra_scripts.

This option can also be set by global environment variable PLATFORMIO_UPLOAD_FLAGS.

Example

Please specify each flag/option in a new line starting with minimum 2 spaces.

[env:atmega328pb]
platform = atmelavr
board = atmega328pb
framework = arduino
upload_flags =
  -P$UPLOAD_PORT
  -b$UPLOAD_SPEED
  -u
  -Ulock:w:0xCF:m
  -Uhfuse:w:0xD7:m
  -Uefuse:w:0xF6:m
  -Ulfuse:w:0xE2:m


upload_resetmethod

Type: String | Multiple: No

Specify reset method for "uploader" tool. This option isn't available for all development platforms. The only Espressif 8266 supports it.

upload_command

New in version 4.0.

Type: String | Multiple: No

Override default Development Platforms upload command with a custom. You can pass a full upload command with arguments and options or mix with upload_flags.

Default upload commands are declared in build/main.py script file of Development Platforms. See a list with open source Development Platforms => https://github.com/topics/platformio-platform

NOTE:

Please note that you can use build variables in upload_command, such as PlatformIO project folders and other runtime configuration. A list with build variables are available by running platformio run --target envdump command.


Examples

1.
Override default upload command but handle pre-uploading actions (looking for serial port, extra image preparation, etc.). Normally, the pre-configured upload options will be stored in $UPLOADERFLAGS build variable. A classic default upload command for Development Platforms may look as some-flash-bin-tool $UPLOADERFLAGS $SOURCE, where $SOURCE will be replaced by a real program/firmware binary.

$PROJECT_PACKAGES_DIR build variable points to packages_dir.

[env:program_via_AVR_ISP]
platform = atmelavr
framework = arduino
board = uno
upload_flags =
    -C
    $PROJECT_PACKAGES_DIR/tool-avrdude/avrdude.conf
    -p
    atmega328p
    -P
    $UPLOAD_PORT
    -b
    115200
    -c
    stk500v1
upload_command = avrdude $UPLOAD_FLAGS -U flash:w:$SOURCE:i


2.
Override default upload command and skip pre-uploading actions.

[env:program_via_usbasp]
platform = atmelavr
framework = arduino
board = uno
upload_flags =
    -C
    $PROJECT_PACKAGES_DIR/tool-avrdude/avrdude.conf
    -p
    atmega328p
    -Pusb
    -c
    stk500v1
upload_command = avrdude $UPLOAD_FLAGS -U flash:w:$SOURCE:i
; Use ST-util for flashing
; https://github.com/texane/stlink
[env:custom_st_flash]
platform = ststm32
framework = stm32cube
board = bluepill_f103c6
upload_command = $PROJECT_PACKAGES_DIR/tool-stlink/st-flash write $SOURCE 0x8000000



  • monitor_port
  • monitor_speed
  • monitor_filters
  • monitor_rts
  • monitor_dtr
  • monitor_flags

Custom options for platformio device monitor command.

monitor_port

Type: String | Multiple: No

Port, a number or a device name, or valid URL Handlers. See platformio device monitor --port. To print all available serial ports please use platformio device list command.

Please note that you can use Unix shell-style wildcards:

Pattern Meaning
* matches everything
? matches any single character
[seq] matches any character in seq
[!seq] matches any character not in seq

Example:

[env:custom_monitor_port]
...
; Unix
monitor_port = /dev/ttyUSB1
; Windows, COM1 or COM3
monitor_port = COM[13]
; Socket
monitor_port = socket://localhost:4444


monitor_speed

Type: Integer | Multiple: No | Default: 9600

A monitor speed (baud rate). See platformio device monitor --baud.

Example:

[env:custom_monitor_speedrate]
...
monitor_speed = 115200


monitor_filters

New in version 4.3.

Type: String | Multiple: Yes

Apply filters and text transformation for device output. See available filters at Filters.

Example:

[env:log_output_to_file_with_timestamp]
...
platform = ...
monitor_filters = log2file, time, default


monitor_rts

Type: Integer (0 or 1) | Multiple: No

A monitor initial RTS line state. See platformio device monitor --rts.

monitor_dtr

Type: Integer (0 or 1) | Multiple: No

A monitor initial DTR line state. See platformio device monitor --dtr.

monitor_flags

New in version 4.0.

Type: String | Multiple: Yes

Pass extra flags and options to platformio device monitor command. Please note that each flag, option or its value should be passed in a new line. See example below.

Available flags and options are the same which are documented for platformio device monitor command.

Example:

[env:extra_monitor_flags]
platform = ...
board = ...
monitor_flags=
    --parity
    N
    --encoding
    hexlify


SEE ALSO:

Please make sure to read PIO Check guide first.


  • check_tool
  • check_patterns
  • check_flags
  • check_severity

check_tool

Type: String | Multiple: Yes | Default: cppcheck

A name of the check tool used for analysis. This option is useful when you want to check source code with two or more tools.

See available tools in Check tools.

Example

[env:myenv]
platform = ...
board = ...
check_tool = cppcheck, clangtidy


check_patterns

Type: String (Pattern) | Multiple: Yes

This option allows specifying which source files or folders should be included/excluded from the check process. GLOB Patterns are allowed. src_dir and include_dir folders are checked by default.

Another option for filtering source files is platformio check --pattern command.

Example

[env:custom_check_patterns]
platform = ...
board = ...
check_tool = clangtidy
check_patterns =
  app/sources
  tests/hardware/*.c


check_flags

Type: String | Multiple: Yes

Additional flags to be passed to the tool command line. This option is useful when you want to adjust the check process to fit your project requirements. By default, the flags are passed to all tools specified in check_tool section. To set individual flags, define tool name at the beginning of the line.

Another option for adding flags is platformio check --flags command.

Example

[env:extra_check_flags]
platform = ...
board = ...
check_tool = cppcheck, clangtidy
check_flags =
  --common-flag
  cppcheck: --enable=performance --inline-suppr
  clangtidy: -fix-errors -format-style=mozilla


check_severity

Type: String | Multiple: Yes | Default: low, medium, high

This option allows specifying the Defect severity types which will be reported by the Check tools.

Another option for filtering source files is platformio check --severity command.

Example

[env:detect_only_medium_or_high_defects]
platform = ...
board = ...
check_severity = medium, high


SEE ALSO:

Please make sure to read PIO Unit Testing guide first.


  • test_filter
  • test_ignore
  • test_port
  • test_speed
  • test_transport
  • test_build_project_src

test_filter

Type: String (Pattern) | Multiple: Yes

Process only the PIO Unit Testing tests where the name matches specified patterns.

Also, you can filter some tests using platformio test --filter command.

Pattern Meaning
* matches everything
? matches any single character
[seq] matches any character in seq
[!seq] matches any character not in seq

Example

[env:myenv]
test_filter = footest, bartest_*, test[13]


test_ignore

Type: String (Pattern) | Multiple: Yes

Ignore PIO Unit Testing tests where the name matches specified patterns.

Also, you can ignore some tests using platformio test --ignore command.

Pattern Meaning
* matches everything
? matches any single character
[seq] matches any character in seq
[!seq] matches any character not in seq

Example

[env:myenv]
test_ignore =
  footest
  bartest_*
  test[13]


test_port

Type: String (Pattern) | Multiple: No

This option specifies communication interface (Serial/UART) between PlatformIO PIO Unit Testing Engine and target device. For example,

  • /dev/ttyUSB0 - Unix-based OS
  • COM3 - Windows OS

If test_port isn't specified, then PlatformIO will try to detect it automatically.

To print all available serial ports use platformio device list command.

test_speed

Type: Integer | Multiple: No | Default: 115200

A connection speed (baud rate) to communicate with a target device.

test_transport

Type: String | Multiple: No

A transport type which will be used to read test results from a target device. See more details at Test Transport.

test_build_project_src

Type: Bool (yes or no) | Multiple: No | Default: no

Force PIO Unit Testing engine to build project source code from src_dir setting test_build_project_src to yes. More detail about Shared Code.

Example

[env:myenv]
platform = ...
test_build_project_src = yes


SEE ALSO:

Please make sure to read PIO Unified Debugger guide first.


  • debug_tool
  • debug_build_flags
  • debug_init_break
  • debug_init_cmds
  • debug_extra_cmds
  • debug_load_cmds
  • debug_load_mode
  • debug_server
  • debug_port
  • debug_svd_path

debug_tool

Type: String | Multiple: No

A name of debugging tool. This option is useful when board supports more than one debugging tool (adapter, probe) or you want to create Custom debugging configuration.

See available tools in Tools & Debug Probes.

Example

[env:debug]
platform = ...
board = ...
debug_tool = custom


debug_build_flags

New in version 4.2.0.

Type: String | Multiple: Yes | Default: -Og -g2 -ggdb2

These flags/options affect the preprocessing, compilation, assembly and linking processes for C and C++ code.

NOTE:

This option might be helpful to adjust the optimization level if firmware with debug information is too big to be uploaded to a target


Example

[env:debug]
platform = ...
board = ...
; Set optimization level and amount of debug information generated by the compiler
debug_build_flags = -O0 -ggdb3 -g3


Other possible flags that might be useful for debugging your application.

debug_init_break

Type: String | Multiple: No | Default: tbreak main

An initial breakpoint that makes your program stop whenever a certain point in the program is reached. Default value is set to tbreak main and means creating a temporary breakpoint at int main(...) function and automatically delete it after the first time a program stops there.

  • GDB Setting Breakpoints
  • GDB Breakpoint Locations

NOTE:

Please note that each debugging tool (adapter, probe) has limited number of hardware breakpoints.

If you need more Project Initial Breakpoints, please place them in debug_extra_cmds.



Examples

[env:debug]
platform = ...
board = ...
; Examples 1: disable initial breakpoint
debug_init_break =
; Examples 2: temporary stop at ``void loop()`` function
debug_init_break = tbreak loop
; Examples 3: stop in main.cpp at line 13
debug_init_break = break main.cpp:13
; Examples 4: temporary stop at ``void Reset_Handler(void)``
debug_init_break = tbreak Reset_Handler


debug_init_cmds

Type: String | Multiple: Yes | Default: See details...

Initial commands that will be passed to back-end debugger.

PlatformIO dynamically configures back-end debugger depending on a debug environment. Here is a list with default initial commands for the popular Tools & Debug Probes.

For example, the custom initial commands for GDB:

[env:debug]
platform = ...
board = ...
debug_init_cmds =
  target extended-remote $DEBUG_PORT
  $INIT_BREAK
  monitor reset halt
  $LOAD_CMDS
  monitor init
  monitor reset halt


debug_extra_cmds

Type: String | Multiple: Yes

Extra commands that will be passed to back-end debugger after debug_init_cmds. For example, add custom breakpoint and load .gdbinit from a project directory for GDB:

[env:debug]
platform = ...
board = ...
debug_extra_cmds =
  break main.cpp:13
  break foo.cpp:100
  source .gdbinit


NOTE:

Initial Project Breakpoints: Use break path/to/file:LINE_NUMBER to define initial breakpoints for debug environment. Multiple breakpoints are allowed.

To save session breakpoints, please use save breakpoints [filename] command in Debug Console. For example, save breakpoints .gdbinit. Later, this file could be loaded via source [filename] command. See above.



debug_load_cmds

New in version 4.0.

Type: String | Multiple: Yes | Default: load

Specify a command which will be used to load program/firmware to a target device. Possible options:

  • load - default option
  • load [address] - load program at specified address, where "[address]" should be a valid number
  • preload - some embedded devices have locked Flash Memory (a few Freescale Kinetis and NXP LPC boards). In this case, firmware loading using debugging client is disabled. preload command instructs PlatformIO Core (CLI) to load program/firmware using development platform "upload" method (via bootloader, media disk, etc)
  • (empty value, debug_load_cmds =), disables program loading at all.
  • custom commands - pass any debugging client command (GDB, etc.)

Sometimes you need to run extra monitor commands (on debug server side) before program/firmware loading, such as flash unlocking or erasing. In this case we can combine service commands with loading and run them before. See example:

[env:debug]
platform = ...
board = ...
debug_load_cmds =
  monitor flash erase_sector 0 0 11
  load


debug_load_mode

Type: String | Multiple: No | Default: always

Allows one to control when PlatformIO should load debugging firmware to the end target. Possible options:

  • always - load for the each debugging session, default
  • modified - load only when firmware was modified
  • manual - do not load firmware automatically. You are responsible to pre-flash target with debugging firmware in this case.

debug_server

Type: String | Multiple: Yes

Allows one to setup a custom debugging server. By default, boards are pre-configured with a debugging server that is compatible with "on-board" debugging tool (adapter, probe). Also, this option is useful for a Custom debugging tool.

Option format (multi-line):

  • First line is an executable path of debugging server
  • 2-nd and the next lines are arguments for executable file

Example:

[env:debug]
platform = ...
board = ...
debug_server =
  /path/to/debugging/server
  arg1
  arg2
  ...
  argN


debug_port

Type: String | Multiple: No

A debugging port of a remote target. Could be a serial device or network address. PlatformIO detects it automatically if is not specified.

For example:

  • /dev/ttyUSB0 - Unix-based OS
  • COM3 - Windows OS
  • localhost:3333

debug_svd_path

Type: FilePath | Multiple: No

A custom path to SVD file which contains information about device peripherals.

extends

New in version 4.1.

Type: String | Multiple: Yes

This option allows one to inherit configuration from other sections or build environments in "platformio.ini" (Project Configuration File). Multiple items are allowed, split them with , or with a new line.

If you need to extend only a few options from some section, please take a look at Dynamic variables.

Example:

[strict_ldf]
lib_ldf_mode = chain+
lib_compat_mode = strict
[espressi32_base]
platform = espressif32
framework = arduino
[env:release]
extends = espressi32_base, strict_ldf
board = esp32dev
build_flags = -D RELEASE
[env:debug]
extends = env:release
build_type = debug
build_flags = -D DEBUG


extra_scripts

Type: FilePath | Multiple: Yes

A list of PRE and POST extra scripts.

See details and examples in Advanced Scripting section.

If you plan to share these scripts with PIO Remote machine, please put them to shared_dir.

New in version 4.0.0.

There are 2 types (build_type) of build configuration in PlatformIO:

Default configuration. A "release" configuration of your firmware/program does not contain symbolic debug information and is optimized for the firmware size or speed (depending on Development Platforms)
A "debug" configuration of your firmware/program is compiled with full symbolic debug information and no optimization. Optimization complicates debugging, because the relationship between source code and generated instructions is more complex.

NOTE:

If you need to control build flags that are specific for debug configuration please refer to debug_build_flags.


If you need to build a project in debug configuration, please use one of these options:

  • Add build_type with debug value to "platformio.ini" (Project Configuration File)
  • Use target debug for the platformio run --target command.

NOTE:

PIO Unified Debugger automatically switches to debug configuration when you do project debugging from PlatformIO IDE or use the platformio debug command.

To avoid having PIO Unified Debugger rebuild the project, please create a separate build environment that defines build_type = debug. See the example below where the mydebug build environment will be used automatically by PIO Unified Debugger:

[env]
platform = ...
board = ...
framework = ...
... other common configuration
[env:myrelease]
some_extra_options = ...
[env:mydebug]
build_type = debug
some_extra_options = ...




Please note that you can set a default build environment per a project using the default_envs option in Section [platformio].

Dynamic variables (interpolations) are useful when you have a custom configuration data between build environments. For examples, extra build_flags or project dependencies lib_deps.

Each variable should have a next format: ${<section>.<option>}, where <section> is a value from [<section>] group, and <option> is a first item from pair <option> = value.

You can inject system environment variable using sysenv as a section. For example, ${sysenv.HOME}.

  • Variable can be applied only for the option's value
  • Multiple variables are allowed
  • The Section [platformio] and Section [env] sections are reserved and could not be used as a custom section. Some good section names might be extra or custom.

NOTE:

If you need to share common configuration options between build environments, please take a look at "Global scope" in Section [env] or extends option which allows extending of other sections.


Example:

[env]
; Unix
lib_extra_dirs = ${sysenv.HOME}/Documents/Arduino/libraries
; Windows
lib_extra_dirs = ${sysenv.HOMEDRIVE}${sysenv.HOMEPATH}\Documents\Arduino\libraries
; You MUST inject these options into [env:] section
; using ${extra.***} (see below)
[extra]
build_flags = -D VERSION=1.2.3 -D DEBUG=1
lib_deps_builtin =
  SPI
  Wire
lib_deps_external = ArduinoJson@>5.6.0
[env:uno]
platform = atmelavr
framework = arduino
board = uno
build_flags = ${extra.build_flags}
lib_deps =
  ${extra.lib_deps_builtin}
  ${extra.lib_deps_external}
[env:nodemcuv2]
platform = espressif8266
framework = arduino
board = nodemcuv2
build_flags = ${extra.build_flags} -Wall
lib_deps =
  ${extra.lib_deps_builtin}
  ${extra.lib_deps_external}
  PubSubClient@2.6
  OneWire
; Keep sensitive data in environment variables
;
; Unix
; export WIFI_SSID='\"my\ ssid\ name\"'
; export WIFI_PASS='\"my\ password\"'
;
; Windows
; set WIFI_SSID='"my ssid name"'
; set WIFI_PASS='"my password"'
[env:esp32dev]
extends = env:nodemcuv2
platform = espressif32
board = esp32dev
build_flags =
  -DWIFI_SSID=${sysenv.WIFI_SSID}
  -DWIFI_PASS=${sysenv.WIFI_PASS}


WARNING:

Be careful with special characters in system environment variables on Unix systems, especially when they are used as the value for preprocessor directives. Symbols like $, &, ~, etc must be explicitly escaped, for example: 

export WIFI_PASS='\"my\~p\&a\\\$\$\$\$word\"'




NOTE:

A full list with project examples can be found in PlatformIO Repository.


Community project examples with platformio.ini:

  • MarlinFirmware/Marlin
  • xoseperez/espurna
  • esphome/esphome
  • cyberman54/ESP32-Paxcounter

Example

For more examples, see Examples.

[platformio]
default_envs = nodemcuv2
; You MUST inject these options into [env:] section
; using ${common_env_data.***} (see below)
[common_env_data]
build_flags =
    -D VERSION=1.2.3
    -D DEBUG=1
lib_deps_builtin =
    SPI
    Wire
lib_deps_external =
    ArduinoJson@~5.6,!=5.4
    https://github.com/gioblu/PJON.git#v2.0
    IRremoteESP8266=https://github.com/markszabo/IRremoteESP8266/archive/master.zip
[env:nodemcuv2]
platform = espressif8266
framework = arduino
board = nodemcuv2
; Build options
build_flags =
    ${common_env_data.build_flags}
    -DSSID_NAME=HELLO
    -DSSID_PASWORD=WORLD
; Library options
lib_deps =
    ${common_env_data.lib_deps_builtin}
    ${common_env_data.lib_deps_external}
    https://github.com/me-no-dev/ESPAsyncTCP.git
    PubSubClient@2.6
    OneWire
; Serial Monitor options
monitor_speed = 115200
monitor_flags =
    --encoding
    hexlify
; Unit Testing options
test_ignore = test_desktop
[env:bluepill_f103c8]
platform = ststm32
framework = arduino
board = bluepill_f103c8
; Build options
build_flags = ${common_env_data.build_flags}
; Library options
lib_deps =
    ${common_env_data.lib_deps_external}
; Debug options
debug_tool = custom
debug_server =
    JLinkGDBServer
    -singlerun
    -if
    SWD
    -select
    USB
    -port
    2331
    -device
    STM32F103C8
; Unit Testing options
test_ignore = test_desktop


Environment variables are a set of dynamic named values that can affect the way running processes will behave on a computer. PlatformIO handles variables which start with PLATFORMIO_ prefix.

How to set environment variable?

# Windows
set VARIABLE_NAME=VALUE
# Windows GUI -> https://www.youtube.com/watch?v=bEroNNzqlF4
# Unix (bash, zsh)
export VARIABLE_NAME=VALUE
# Unix (fish)
set -x VARIABLE_NAME VALUE


  • General
  • Directories
  • Building
  • Uploading
  • Settings

PlatformIO uses General environment variables for the common operations/commands.


PlatformIO handles CI variable which is setup by Continuous Integration (Travis, Circle and etc.) systems. PlatformIO uses it to disable prompts and progress bars. In other words, CI=true automatically setup PLATFORMIO_DISABLE_PROGRESSBAR to true.


Allows one to specify Personal Authentication Token that could be used for automatic login in to PIO Account. It is very useful for Continuous Integration systems and PIO Remote operations where you are not able manually authorize.

You can get own Personal Authentication Token using platformio account token command.


Force to output ANSI control character even if the output is a pipe (not a tty). The possible values are true and false. Default is PLATFORMIO_FORCE_ANSI=false.


Do not print ANSI control characters. The possible values are true and false. Default is PLATFORMIO_NO_ANSI=false.

You can also use platformio --no-ansi flag for PlatformIO Core (CLI).


Disable progress bar for package/library downloader and uploader. This is useful when calling PlatformIO from subprocess and output is a pipe (not a tty). The possible values are true and false. Default is PLATFORMIO_DISABLE_PROGRESSBAR=false.


Allows one to override "platformio.ini" (Project Configuration File) option core_dir.


Allows one to override "platformio.ini" (Project Configuration File) option globallib_dir.


Allows one to override "platformio.ini" (Project Configuration File) option platforms_dir.


Allows one to override "platformio.ini" (Project Configuration File) option packages_dir.


Allows one to override "platformio.ini" (Project Configuration File) option cache_dir.


Allows one to override "platformio.ini" (Project Configuration File) option build_cache_dir.


Allows one to override "platformio.ini" (Project Configuration File) option workspace_dir.


Allows one to override "platformio.ini" (Project Configuration File) option include_dir.


Allows one to override "platformio.ini" (Project Configuration File) option src_dir.


Allows one to override "platformio.ini" (Project Configuration File) option lib_dir.


Allows one to override "platformio.ini" (Project Configuration File) option libdeps_dir.


Allows one to override "platformio.ini" (Project Configuration File) option build_dir.


Allows one to override "platformio.ini" (Project Configuration File) option data_dir.


Allows one to override "platformio.ini" (Project Configuration File) option test_dir.


Allows one to override "platformio.ini" (Project Configuration File) option boards_dir.


Allows one to override "platformio.ini" (Project Configuration File) option shared_dir.


Allows one to override platformio remote agent start --working-dir.


Allows one to set "platformio.ini" (Project Configuration File) option lib_extra_dirs.


Allows one to set "platformio.ini" (Project Configuration File) option build_flags.

Examples:

# Unix:
export PLATFORMIO_BUILD_FLAGS=-DFOO
export PLATFORMIO_BUILD_FLAGS=-DFOO -DBAR=1 -Wall
# Windows:
SET PLATFORMIO_BUILD_FLAGS=-DFOO
SET PLATFORMIO_BUILD_FLAGS=-DFOO -DBAR=1 -Wall


WARNING:

Consider using Dynamic variables instead of PLATFORMIO_BUILD_FLAGS environment variable if additional build flags contain preprocessor directive with special characters ($, &, ~, etc) in its value.



Allows one to set "platformio.ini" (Project Configuration File) option src_build_flags.


Allows one to set "platformio.ini" (Project Configuration File) option src_filter.


Allows one to set "platformio.ini" (Project Configuration File) option extra_scripts.


Allows one to set "platformio.ini" (Project Configuration File) option default_envs.


Allows one to set "platformio.ini" (Project Configuration File) option upload_port.


Allows one to set "platformio.ini" (Project Configuration File) option upload_flags.

Allows one to override PlatformIO settings. You can manage them via platformio settings command.


Allows one to override setting auto_update_libraries.


Allows one to override setting auto_update_platforms.


Allows one to override setting check_libraries_interval.


Allows one to override setting check_platformio_interval.


Allows one to override setting check_platforms_interval.


Allows one to override setting enable_cache.


Allows one to override setting strict_ssl.


Allows one to override setting enable_telemetry.


Allows one to override setting force_verbose.


Allows one to override setting projects_dir.

WARNING:

Advanced Scripting is recommended for Advanced Users and requires knowledge of the Python language.


WARNING:

Dynamic build flags is a highly recommended alternative to advanced scripting, where you can use any programming language. Also, that option is useful if you need to apply changes to the project before the building/uploading process, such as:
  • Macro with the latest VCS revision/tag "on-the-fly"
  • Generate dynamic headers (*.h)
  • Process media content before generating SPIFFS image
  • Make some changes to source code or related libraries



•
Advanced Scripting
  • Launch types
  • Construction Environments
  • Before/Pre and After/Post actions
  • Build Middlewares
  • Custom target
  • Command shortcut
  • Dependent target
  • Target with options

•
Examples
  • Custom options in platformio.ini
  • Split C/C++ build flags
  • Extra Linker Flags without -Wl, prefix
  • Custom upload tool
  • Upload to Cloud (OTA)
  • Custom firmware/program name
  • Override package files
  • Override Board Configuration
  • Custom debug flags



The PlatformIO Build System allows the user to extend the build process with custom scripts using the Python interpreter and the SCons construction tool. Build flags, upload flags, targets, toolchains data and other information are available for modification as SCons Construction Environments. Custom scripts are included with extra_scripts

WARNING:

You can not run or debug these scripts manually with a Python interpreter. They will be loaded automatically when the platformio run command processes the project environment.


There are two execution orders for extra scripts:

1.
PRE - executes before the main script of Development Platforms
2.
POST - executes after the main script of Development Platforms

Multiple extra scripts are allowed. Please split them via ", " (comma + space) in the same line or use multi-line values.

For example, in "platformio.ini" (Project Configuration File):

[env:my_env_1]
platform = ...
; Defaults to POST script since no prefix is used
extra_scripts = post_extra_script.py
[env:my_env_2]
platform = ...
extra_scripts =
  pre:pre_extra_script.py
  post:post_extra_script1.py
  post_extra_script2.py


This option can also be set by the global environment variable PLATFORMIO_EXTRA_SCRIPTS.

The PlatformIO Build System uses two built-in construction environments to process each project:

  • env, Import("env") - the global construction environment used for the Development Platforms and Frameworks build scripts, upload tools, Library Dependency Finder (LDF), and other internal operations
  • projenv, Import("projenv") - the isolated construction environment used for processing the project source code in src_dir. Please note that any src_build_flags specified in "platformio.ini" (Project Configuration File) will be passed to projenv and not to env.

WARNING:

1.
projenv is available only for POST-type scripts
2.
Flags passed to env using PRE-type script will affect projenv too.



my_pre_extra_script.py:

Import("env")
# access to global construction environment
print(env)
# Dump construction environment (for debug purpose)
print(env.Dump())
# append extra flags to global build environment
# which later will be used to build:
# - project source code
# - frameworks
# - dependent libraries
env.Append(CPPDEFINES=[
  "MACRO_1_NAME",
  ("MACRO_2_NAME", "MACRO_2_VALUE")
])


my_post_extra_script.py:

Import("env", "projenv")
# access to global construction environment
print(env)
# access to project construction environment
print(projenv)
# Dump construction environments (for debug purpose)
print(env.Dump())
print(projenv.Dump())
# append extra flags to global build environment
# which later will be used to build:
# - frameworks
# - dependent libraries
env.Append(CPPDEFINES=[
  "MACRO_1_NAME",
  ("MACRO_2_NAME", "MACRO_2_VALUE")
])
# append extra flags to only project build environment
projenv.Append(CPPDEFINES=[
  "PROJECT_EXTRA_MACRO_1_NAME",
  ("ROJECT_EXTRA_MACRO_2_NAME", "ROJECT_EXTRA_MACRO_2_VALUE")
])


See examples below how to import construction environments and modify existing data or add new.

The PlatformIO Build System has a rich API that allows one to attach different pre-/post actions (hooks) using env.AddPreAction(target, callback) or env.AddPreAction(target, [callback1, callback2, ...]) function. The first argument target can be the name of a target that is passed using the platformio run --target command, the name of a built-in target (buildprog, size, upload, program, buildfs, uploadfs, uploadfsota) or the path to a file which PlatformIO processes (ELF, HEX, BIN, OBJ, etc.).

Examples

The extra_script.py file is located in the same directory as platformio.ini.

platformio.ini:

[env:pre_and_post_hooks]
extra_scripts = post:extra_script.py


extra_script.py:

Import("env", "projenv")
# access to global build environment
print(env)
# access to project build environment (is used source files in "src" folder)
print(projenv)
#
# Dump build environment (for debug purpose)
# print(env.Dump())
#
#
# Change build flags in runtime
#
env.ProcessUnFlags("-DVECT_TAB_ADDR")
env.Append(CPPDEFINES=("VECT_TAB_ADDR", 0x123456789))
#
# Upload actions
#
def before_upload(source, target, env):
    print("before_upload")
    # do some actions
    # call Node.JS or other script
    env.Execute("node --version")
def after_upload(source, target, env):
    print("after_upload")
    # do some actions
print("Current build targets", map(str, BUILD_TARGETS))
env.AddPreAction("upload", before_upload)
env.AddPostAction("upload", after_upload)
#
# Custom actions when building program/firmware
#
env.AddPreAction("buildprog", callback...)
env.AddPostAction("buildprog", callback...)
#
# Custom actions for specific files/objects
#
env.AddPreAction("$BUILD_DIR/${PROGNAME}.elf", [callback1, callback2,...])
env.AddPostAction("$BUILD_DIR/${PROGNAME}.hex", callback...)
# custom action before building SPIFFS image. For example, compress HTML, etc.
env.AddPreAction("$BUILD_DIR/spiffs.bin", callback...)
# custom action for project's main.cpp
env.AddPostAction("$BUILD_DIR/src/main.cpp.o", callback...)
# Custom HEX from ELF
env.AddPostAction(
    "$BUILD_DIR/${PROGNAME}.elf",
    env.VerboseAction(" ".join([
        "$OBJCOPY", "-O", "ihex", "-R", ".eeprom",
        "$BUILD_DIR/${PROGNAME}.elf", "$BUILD_DIR/${PROGNAME}.hex"
    ]), "Building $BUILD_DIR/${PROGNAME}.hex")
)


New in version 4.1.

PlatformIO Build System allows you to add middleware functions that can be used for Build Node(Object) construction. This is very useful if you need to add custom flags for the specific file nodes or exclude them from a build process.

There is env.AddBuildMiddleware(callback, pattern) helper which instructs PlatformIO Build System to call callback for each SCons File System Node whose path matches with Unix shell-style "pattern" (wildcards).

If a pattern is omitted, the callback will be called for each File System Node which is added for the build process.

You can add an unlimited number of build middlewares. They will be called in order of registration. Please note, if the first middleware ignores some File Nodes, they will not be passed to the next middleware in chain.

Examples

platformio.ini:

[env:build_middleware]
extra_scripts = pre:extra_script.py


extra_script.py:

Import("env")
# --- Add custom macros for the ALL files which name contains "http"
def extra_http_configuration(node):
    """
    `node.name` - a name of File System Node
    `node.get_path()` - a relative path
    `node.get_abspath()` - an absolute path
    """
    # do not modify node if file name does not contain "http"
    if "http" not in node.name:
        return node
    # now, we can override ANY SCons variables (CPPDEFINES, CCFLAGS, etc.,) for the specific file
    # pass SCons variables as extra keyword arguments to `env.Object()` function
    # p.s: run `pio run -t envdump` to see a list with SCons variables
    return env.Object(
        node,
        CPPDEFINES=env["CPPDEFINES"]
        + [("HTTP_HOST", "device.local"), ("HTTP_PORT", 8080)],
        CCFLAGS=env["CCFLAGS"] + ["-fno-builtin-printf"]
    )
env.AddBuildMiddleware(extra_http_configuration)
# --- Replace some file from a build process with another
def replace_node_with_another(node):
    return env.File("path/to/patched/RtosTimer.cpp")
env.AddBuildMiddleware(
    replace_node_with_another,
    "framework-mbed/rtos/RtosTimer.cpp"
)
# --- Skip assembly *.S files from build process
def skip_asm_from_build(node):
    # to ignore file from a build process, just return None
    return None
env.AddBuildMiddleware(skip_asm_from_build, "*.S")


There is a list with built-in targets which could be processed using platformio run --target option. You can create unlimited number of the own targets and declare custom handlers for them.

We will use SCons's Alias(alias, [targets, [action]]) , env.Alias(alias, [targets, [action]]) function to declare a custom target/alias.

Create a custom node target (alias) which will print a NodeJS version

platformio.ini:

[env:myenv]
platform = ...
...
extra_scripts = extra_script.py


extra_script.py:

Import("env")
env.AlwaysBuild(env.Alias("node", None, ["node --version"]))


Now, run pio run -t node.

Sometimes you need to run a command which depends on another target (file, firmware, etc). Let's create an ota target and declare command which will depend on a project firmware. If a build process successes, declared command will be run.

platformio.ini:

[env:myenv]
platform = ...
...
extra_scripts = extra_script.py


extra_script.py:

Import("env")
env.AlwaysBuild(env.Alias("ota",
    "$BUILD_DIR/${PROGNAME}.elf",
    ["ota_script --firmware-path $SOURCE"]))


Now, run pio run -t ota.

Let's create a simple ping target and process it with platformio run --target ping command:

platformio.ini:

[env:env_custom_target]
platform = ...
...
extra_scripts = extra_script.py
custom_ping_host = google.com


extra_script.py:

try:
    import configparser
except ImportError:
    import ConfigParser as configparser
Import("env")
config = configparser.ConfigParser()
config.read("platformio.ini")
host = config.get("env_custom_target", "custom_ping_host")
def mytarget_callback(*args, **kwargs):
    print("Hello PlatformIO!")
    env.Execute("ping " + host)
env.AlwaysBuild(env.Alias("ping", None, mytarget_callback))


The best examples are PlatformIO development platforms. Please check builder folder for the main and framework scripts.

platformio.ini:

[env:my_env]
platform = ...
extra_scripts = extra_script.py
custom_option1 = value1
custom_option2 = value2


extra_script.py:

try:
    import configparser
except ImportError:
    import ConfigParser as configparser
config = configparser.ConfigParser()
config.read("platformio.ini")
value1 = config.get("my_env", "custom_option1")
value2 = config.get("my_env", "custom_option2")


platformio.ini:

[env:my_env]
platform = ...
extra_scripts = extra_script.py


extra_script.py (place it near platformio.ini):

Import("env")
# General options that are passed to the C and C++ compilers
env.Append(CCFLAGS=["flag1", "flag2"])
# General options that are passed to the C compiler (C only; not C++).
env.Append(CFLAGS=["flag1", "flag2"])
# General options that are passed to the C++ compiler
env.Append(CXXFLAGS=["flag1", "flag2"])


Sometimes you need to pass extra flags to GCC linker without Wl,. You could use build_flags option but it will not work. PlatformIO will not parse these flags to LINKFLAGS scope. In this case, simple extra script will help:

platformio.ini:

[env:env_extra_link_flags]
platform = windows_x86
extra_scripts = extra_script.py


extra_script.py (place it near platformio.ini):

Import("env")
#
# Dump build environment (for debug)
# print(env.Dump())
#
env.Append(
  LINKFLAGS=[
      "-static",
      "-static-libgcc",
      "-static-libstdc++"
  ]
)


You can override default upload command of development platform using extra script. There is the common environment variable UPLOADCMD which PlatformIO Build System will handle when you platformio run -t upload.

Please note that some development platforms can have more than 1 upload command. For example, Atmel AVR has UPLOADHEXCMD (firmware) and UPLOADEEPCMD (EEPROM data).

See examples below:

Template

platformio.ini:

[env:my_custom_upload_tool]
platform = ...
; place it into the root of project or use full path
extra_scripts = extra_script.py
upload_protocol = custom
; each flag in a new line
upload_flags =
  -arg1
  -arg2
  -argN


extra_script.py (place it near platformio.ini):

Import("env")
# please keep $SOURCE variable, it will be replaced with a path to firmware
# Generic
env.Replace(
    UPLOADER="executable or path to executable",
    UPLOADCMD="$UPLOADER $UPLOADERFLAGS $SOURCE"
)
# In-line command with arguments
env.Replace(
    UPLOADCMD="executable -arg1 -arg2 $SOURCE"
)
# Python callback
def on_upload(source, target, env):
    print(source, target)
    firmware_path = str(source[0])
    # do something
    env.Execute("executable arg1 arg2")
env.Replace(UPLOADCMD=on_upload)


Custom openOCD command

platformio.ini:

[env:disco_f407vg]
platform = ststm32
board = disco_f407vg
framework = mbed
extra_scripts = extra_script.py
upload_protocol = custom
; each flag in a new line
upload_flags =
    -f
    scripts/interface/stlink.cfg
    -f
    scripts/target/stm32f4x.cfg


extra_script.py (place it near platformio.ini):

Import("env")
platform = env.PioPlatform()
env.Prepend(
    UPLOADERFLAGS=["-s", platform.get_package_dir("tool-openocd") or ""]
)
env.Append(
    UPLOADERFLAGS=["-c", "program {{$SOURCE}} verify reset; shutdown"]
)
env.Replace(
    UPLOADER="openocd",
    UPLOADCMD="$UPLOADER $UPLOADERFLAGS"
)


See project example https://github.com/platformio/bintray-secure-ota

Sometimes is useful to have a different firmware/program name in build_dir.

platformio.ini:

[env:env_custom_prog_name]
platform = espressif8266
board = nodemcuv2
framework = arduino
build_flags = -D VERSION=13
extra_scripts = pre:extra_script.py


extra_script.py:

Import("env")
my_flags = env.ParseFlags(env['BUILD_FLAGS'])
defines = {k: v for (k, v) in my_flags.get("CPPDEFINES")}
# print(defines)
env.Replace(PROGNAME="firmware_%s" % defines.get("VERSION"))


PlatformIO Package Manager automatically installs pre-built packages (Frameworks, toolchains, libraries) required by development Development Platforms and build process. Sometimes you need to override original files with own versions: configure custom GPIO, do changes to built-in LD scripts, or some patching to installed library dependency.

The simplest way is using Diff and Patch technique. How does it work?

1.
Modify original source files
2.
Generate patches
3.
Apply patches via PlatformIO extra script before build process.

Example

We need to patch the original standard/pins_arduino.h variant from Arduino framework and add extra macro #define PIN_A8 (99). Let's duplicate standard/pins_arduino.h and apply changes. Generate a patch file and place it into patches folder located in the root of a project:

diff ~/.platformio/packages/framework-arduinoavr/variants/standard/pins_arduino.h /tmp/pins_arduino_modified.h > /path/to/platformio/project/patches/1-framework-arduinoavr-add-pin-a8.patch


The result of 1-framework-arduinoavr-add-pin-a8.patch:

63a64
> #define PIN_A8   (99)
112c113
< // 14-21 PA0-PA7 works
---
> // 14-21 PA0-PA7 works


Using extra scripting we can apply patching before a build process. The final result of "platformio.ini" (Project Configuration File) and "PRE" extra script named apply_patches.py:

platformio.ini:

[env:uno]
platform = atmelavr
board = uno
framework = arduino
extra_scripts = pre:apply_patches.py


apply_patches.py:

from os.path import join, isfile
Import("env")
FRAMEWORK_DIR = env.PioPlatform().get_package_dir("framework-arduinoavr")
patchflag_path = join(FRAMEWORK_DIR, ".patching-done")
# patch file only if we didn't do it before
if not isfile(join(FRAMEWORK_DIR, ".patching-done")):
    original_file = join(FRAMEWORK_DIR, "variants", "standard", "pins_arduino.h")
    patched_file = join("patches", "1-framework-arduinoavr-add-pin-a8.patch")
    assert isfile(original_file) and isfile(patched_file)
    env.Execute("patch %s %s" % (original_file, patched_file))
    # env.Execute("touch " + patchflag_path)
    def _touch(path):
        with open(path, "w") as fp:
            fp.write("")
    env.Execute(lambda *args, **kwargs: _touch(patchflag_path))


Please note that this example will work on a system where a patch tool is available. For Windows OS, you can use patch and diff tools provided by Git client utility (located inside installation directory).

If you need to make it more independent to the operating system, please replace the patch with a multi-platform python-patch script.

PlatformIO allows one to override some basic options (integer or string values) using More options in "platformio.ini" (Project Configuration File). Sometimes you need to do complex changes to default board manifest and extra PRE scripting work well here. See example below how to override default hardware VID/PIDs.

WARNING:

Due to a technical limitation these board changes will not work for platformio device monitor command.


platformio.ini:

[env:uno]
platform = atmelavr
board = uno
framework = arduino
extra_scripts = pre:custon_hwids.py


custon_hwids.py:

Import("env")
board_config = env.BoardConfig()
# should be array of VID:PID pairs
board_config.update("build.hwids", [
  ["0x2341", "0x0243"],  # 1st pair
  ["0x2A03", "0x0043"].  # 2nd pair, etc.
])


PlatformIO removes all debug/optimization flags before a debug session or when Build Configurations is set to debug and overrides them with -0g -g2 -ggdb2 for ASFLAGS, CCFLAGS, and LINKFLAGS build scopes.

An extra script allows us to override PlatformIO's default behavior and declare custom flags. See example below where we override -Og with -O0:

platformio.ini:

[env:teensy31]
platform = teensy
board = teensy31
framework = arduino
extra_scripts = custom_debug_flags.py


custom_debug_flags.py:

Import("env")
if env.GetBuildType() == "debug":
   for scope in ("ASFLAGS", "CCFLAGS", "LINKFLAGS"):
      for i, flag in enumerate(env[scope]):
         if flag == "-Og":
            env[scope][i] = "-O0"


Library Manager

PlatformIO Library Manager is a tool for managing libraries of PlatformIO Registry and VCS repositories (Git, Hg, SVN). It makes it exceedingly simple to find, install and keep libraries up-to-date. PlatformIO Library Manager supports Semantic Versioning and its rules.


----



PlatformIO IDE has built-in PlatformIO Home with a modern GUI which allows:

  • Search for new libraries in PlatformIO Registry
  • "1-click" library installation, per-project libraries, extra storages
  • List installed libraries in multiple storages
  • List built-in libraries (by frameworks)
  • Updates for installed libraries
  • Multiple examples, trending libraries, and more.

[image]

Quick Start

PlatformIO Library Manager is a tool for managing libraries of PlatformIO Registry and VCS repositories (Git, Hg, SVN). It makes it exceedingly simple to find, install and keep libraries up-to-date. PlatformIO Library Manager supports Semantic Versioning and its rules.

There are 3 options how to find/manage libraries:

  • PlatformIO Home
  • Web Library Search
  • PIO Core Command Line Interface

You can manage different library storages using platformio lib --global or platformio lib --storage-dir options. If you change current working directory in terminal to project folder, then platformio lib command will manage automatically dependency storage in libdeps_dir.

PlatformIO Library Manager allows one to specify project dependencies (lib_deps) that will be installed automatically per project before environment processing. You do not need to install libraries manually. The only one simple step is to define dependencies in "platformio.ini" (Project Configuration File). You can use library ID, Name or even repository URL. For example,

[env:myenv]
platform = ...
framework = ...
board = ...
lib_deps =
  13
  PubSubClient
  ArduinoJson@~5.6,!=5.4
  https://github.com/gioblu/PJON.git#v2.0
  https://github.com/me-no-dev/ESPAsyncTCP.git
  https://github.com/adafruit/DHT-sensor-library/archive/master.zip


Please follow to platformio lib install for detailed documentation about possible values.

WARNING:

If some libraries are not visible in PlatformIO IDE and Code Completion or Code Linting does not work properly, please perform
  • Atom: "Menu: PlatformIO > Rebuild C/C++ Project Index (Autocomplete, Linter)"
  • VSCode: "Menu: View > Command Palette... > PlatformIO: Rebuild C/C++ Project Index"



PlatformIO IDE

PlatformIO IDE has built-in PlatformIO Home with a modern GUI which allows:

  • Search for new libraries in PlatformIO Registry
  • "1-click" library installation, per-project libraries, extra storages
  • List installed libraries in multiple storages
  • List built-in libraries (by frameworks)
  • Updates for installed libraries
  • Multiple examples, trending libraries, and more.

[image]

PlatformIO Core

[image]

CLI Guide

Library Dependency Finder is a core part of PlatformIO Build System that operates with the C/C++ source files and looks for #include ... directives to know what header directories to include for the compiler.

In spite of the fact that Library Dependency Finder is written in pure Python, it evaluates C/C++ Preprocessor conditional syntax (#ifdef, if, defined, else, and elif) without calling gcc -E. This approach allows to significantly reduce the total compilation time. See Dependency Finder Mode for more details.

•
Library Dependency Finder (LDF)
  • Configuration
  • Storage
  • Dependency Finder Mode
  • Compatibility Mode
  • C/C++ Preprocessor conditional syntax


Library Dependency Finder can be configured from "platformio.ini" (Project Configuration File):

There are different storages where Library Dependency Finder looks for libraries. These storages (folders) have priority and LDF operates in the next order:

1.
lib_extra_dirs - extra storages per build environment
2.
lib_dir - own/private library storage per project
3.
libdeps_dir - project dependency storage used by Library Manager
4.
"core_dir/lib" - global storage per all projects.
5.
Library storages built into frameworks, SDKs.

Library Dependency Finder starts work from analyzing source files of the project (src_dir) and can work in the next modes:

"Manual mode", does not process source files of a project and dependencies. Builds only the libraries that are specified in manifests (library.json, module.json) or using lib_deps option.
[DEFAULT] Parses ALL C/C++ source files of the project and follows only by nested includes (#include ..., chain...) from the libraries. It also parses C, CC, CPP files from libraries which have the same name as included header file. Does not evaluate C/C++ Preprocessor conditional syntax.
Parses ALL C/C++ source files of the project and parses ALL C/C++ source files of the each found dependency (recursively). Does not evaluate C/C++ Preprocessor conditional syntax.
The same behavior as for the chain but evaluates C/C++ Preprocessor conditional syntax.
The same behavior as for the deep but evaluates C/C++ Preprocessor conditional syntax.

The mode can be changed using lib_ldf_mode option in "platformio.ini" (Project Configuration File). Default value is set to chain.

NOTE:

Usually, when the LDF appears to fail to identify a dependency of a library, it is because the dependency is only referenced from a library source file, and not a library header file (see example below). In this case, it is necessary to either explicitly reference the dependency from the project source or "platformio.ini" (Project Configuration File) (lib_deps option), or change the LDF mode to "deep" (not generally recommended).


A difference between chain/chain+ and deep/deep+ modes. For example, there are 2 libraries:

•
Library Foo with files:
  • Foo/foo.h
  • Foo/foo.cpp
  • Foo/extra.cpp

•
Library Bar with files:
  • Bar/bar.h
  • Bar/bar.cpp


  • lib_ldf_mode = chain
  • Foo/foo.h depends on the Bar library (contains #include <bar.h>)
  • #include <foo.h> is located in one of the project source files

Here the nested includes (project file > foo.h > bar.h) and LDF will find both libraries "Foo`` and Bar.

  • lib_ldf_mode = chain
  • Foo/extra.cpp depends on the Bar library (contains #include <bar.h>)
  • #include <foo.h> is located in one of the project source files

In this case, LDF will not find the Bar library because it doesn't know about the CPP file (Foo/extra.cpp).

  • lib_ldf_mode = deep
  • Foo/extra.cpp depends on Bar library (contains #include <bar.h>)
  • #include <foo.h> is located in one of the project source files

Firstly, LDF finds the Foo library, then it parses all sources from the Foo library and finds Foo/extra.cpp that depends on #include <bar.h>. Secondly, it will parse all sources from the Bar library. This operation continues until all dependencies will not be parsed.


Compatibility mode allows one to control strictness of Library Dependency Finder. If library contains one of manifest file (library.json, library.properties, module.json), then LDF check compatibility of this library with real build environment. Available compatibility modes:

Does not check for compatibility (is not recommended)
[DEFAULT] Checks for the compatibility with framework from build environment
Checks for the compatibility with framework and platform from build environment.

This mode can be changed using lib_compat_mode option in "platformio.ini" (Project Configuration File). Default value is set to soft.

In spite of the fact that Library Dependency Finder is written in pure Python, it evaluates C/C++ Preprocessor conditional syntax (#ifdef, if, defined, else, and elif) without calling gcc -E. For example,

platformio.ini

[env:myenv]
lib_ldf_mode = chain+
build_flags = -D MY_PROJECT_VERSION=13


mylib.h

#ifdef MY_PROJECT_VERSION
// include common file for the project
#include "my_common.h"
#endif
#if MY_PROJECT_VERSION < 10
// this include will be ignored because does not satisfy condition above
#include "my_old.h"
#endif


library.json is a manifest file of development library. It allows developers to keep project in own structure and define:

  • location of source code
  • examples list
  • compatible frameworks and platforms
  • library dependencies
  • advanced build settings

PlatformIO Library Crawler uses library.json manifest to extract source code from developer's location and keeps a cleaned library in own Library Registry.

A data in library.json should be represented in JSON-style via associative array (name/value pairs). An order doesn't matter. The allowable fields (names from pairs) are described below.

  • name
  • version
  • description
  • keywords
  • authors
  • repository
  • license
  • downloadUrl
  • homepage
  • export
  • include
  • exclude

  • frameworks
  • platforms
  • dependencies
  • examples
  • build
  • flags
  • unflags
  • includeDir
  • srcDir
  • srcFilter
  • extraScript
  • libArchive
  • libLDFMode
  • libCompatMode

•
Examples

name

Required | Type: String | Max. Length: 50

A name of the library.

  • Must be unique.
  • Should be slug style for simplicity, consistency and compatibility. Example: Arduino-SPI
  • Title Case, Aa-z, can contain digits and dashes (but not start/end with them).
  • Consecutive dashes are not allowed.

version

Required | Type: String | Max. Length: 20

A version of the current library source code. Can contain a-z, digits, dots or dash and should be Semantic Versioning <http://semver.org> compatible.

Example:

"name": "Bar",
"version": "1.0.0",
"repository":
{
    "type": "git",
    "url": "https://github.com/foo/bar.git"
}


description

Required | Type: String | Max. Length: 255

The field helps users to identify and search for your library with a brief description. Describe the hardware devices (sensors, boards and etc.) which are suitable with it.

keywords

Required | Type: String | Max. Length: 255

Used for search by keyword. Helps to make your library easier to discover without people needing to know its name.

The keyword should be lowercased, can contain a-z, digits and dash (but not start/end with them). A list from the keywords can be specified with separator ,

authors

Required if repository field is not defined | Type: Object or Array

An author contact information

  • name Full name (Required)
  • email
  • url An author's contact page
  • maintainer Specify "maintainer" status

Examples:

"authors":
{
    "name": "John Smith",
    "email": "me@john-smith.com",
    "url": "http://www.john-smith/contact"
}
...
"authors":
[
    {
        "name": "John Smith",
        "email": "me@john-smith.com",
        "url": "http://www.john-smith/contact"
    },
    {
        "name": "Andrew Smith",
        "email": "me@andrew-smith.com",
        "url": "http://www.andrew-smith/contact",
        "maintainer": true
    }
]


NOTE:

You can omit authors field and define repository field. Only GitHub-based repository is supported now. In this case PlatformIO Library Registry Crawler will use information from GitHub API Users.


repository

Required if downloadUrl field is not defined | Type: Object

The repository in which the source code can be found. The field consists of the next items:

  • type the only "git", "hg" or "svn" are supported
  • url
  • branch if is not specified, default branch will be used. This field will be ignored if tag/release exists with the value of version.

Example:

"repository":
{
    "type": "git",
    "url": "https://github.com/foo/bar.git"
}


license

Optional | Type: String

A license of the library. You can check the full list of SPDX license IDs. Ideally you should pick one that is OSI approved.

"license": "Apache-2.0"


downloadUrl

Required if repository field is not defined | Type: String

It is the HTTP URL to the archived source code of library. It should end with the type of archive (.zip or .tar.gz).

NOTE:

downloadUrl has higher priority than repository.


Example with detached release/tag on GitHub:

"version": "1.0.0",
"downloadUrl": "https://github.com/foo/bar/archive/v1.0.0.tar.gz",
"include": "bar-1.0.0"


See more library.json Examples.

homepage

Optional | Type: String | Max. Length: 255

Home page of library (if is different from repository url).

export

Optional | Type: Object

Explain PlatformIO Library Crawler which content from the repository/archive should be exported as "source code" of the library. This option is useful if need to exclude extra data (test code, docs, images, PDFs, etc). It allows one to reduce size of the final archive.

Possible options:

  • include
  • exclude

include

Optional | Type: String or Array | Glob Pattern

If include field is a type of String, then PlatformIO Library Registry Crawler will recognize it like a "relative path inside repository/archive to library source code". See example below where the only source code from the relative directory LibrarySourceCodeHere will be included.

"include": "some/child/dir/LibrarySourceCodeHere"


If include field is a type of Array, then PlatformIO Library Registry Crawler will include only directories/files which match with include patterns.

Example:

"export": {
    "include":
    [
        "dir/*.[ch]pp",
        "dir/examples/*",
        "*/*/*.h"
    ]
}


Pattern Meaning

Pattern Meaning
* matches everything
? matches any single character
[seq] matches any character in seq
[!seq] matches any character not in seq

See more library.json Examples.

exclude

Optional | Type: String or Array | Glob Pattern

Exclude the directories and files which match with exclude patterns.

frameworks

Optional | Type: String or Array

A list with compatible frameworks. The available framework types are defined in the Frameworks section.

If the library is compatible with the all frameworks, then you can use * symbol:

"frameworks": "*"


platforms

Optional | Type: String or Array

A list with compatible platforms. The available platform types are defined in Development Platforms section.

If the library is compatible with the all platforms, then you can use * symbol:

"platforms": "*"


dependencies

Optional | Type: Array or Object

A list of dependent libraries. They will be installed automatically with platformio lib install command.

Allowed requirements for dependent library:

  • name | Type: String
  • version | Type: String
  • authors | Type: String or Array
  • frameworks | Type: String or Array
  • platforms | Type: String or Array

The version supports Semantic Versioning ( <major>.<minor>.<patch>) and can take any of the following forms:

  • 1.2.3 - an exact version number. Use only this exact version
  • ^1.2.3 - any compatible version (exact version for 1.x.x versions
  • ~1.2.3 - any version with the same major and minor versions, and an equal or greater patch version
  • >1.2.3 - any version greater than 1.2.3. >=, <, and <= are also possible
  • >0.1.0,!=0.2.0,<0.3.0 - any version greater than 0.1.0, not equal to 0.2.0 and less than 0.3.0

The rest possible values including VCS repository URLs are documented in platformio lib install command.

Example:

"dependencies":
[
    {
        "name": "Library-Foo",
        "authors":
        [
            "Jhon Smith",
            "Andrew Smith"
        ]
    },
    {
        "name": "Library-Bar",
        "version": "~1.2.3"
    },
    {
        "name": "lib-from-repo",
        "version": "https://github.com/user/package.git#1.2.3"
    }
]


A short definition of dependencies is allowed:

"dependencies": {
    "mylib": "1.2.3",
    "lib-from-repo": "githubuser/package"
}


See more library.json Examples.

examples

Optional | Type: String or Array | Glob Pattern

A list of example patterns. This field is predefined with default value:

"examples": [
    "[Ee]xamples/*.c",
    "[Ee]xamples/*.cpp",
    "[Ee]xamples/*.ino",
    "[Ee]xamples/*.pde",
    "[Ee]xamples/*/*.c",
    "[Ee]xamples/*/*.cpp",
    "[Ee]xamples/*/*.ino",
    "[Ee]xamples/*/*.pde",
    "[Ee]xamples/*/*/*.c",
    "[Ee]xamples/*/*/*.cpp",
    "[Ee]xamples/*/*/*.ino",
    "[Ee]xamples/*/*/*.pde"
]


build

Optional | Type: Object

Specify advanced settings, options and flags for the build system. Possible options:

  • flags
  • unflags
  • includeDir
  • srcDir
  • srcFilter
  • extraScript
  • libArchive
  • libLDFMode
  • libCompatMode

flags

Optional | Type: String or Array

Extra flags to control preprocessing, compilation, assembly and linking processes. More details build_flags.

unflags

Optional | Type: String or Array

Remove base/initial flags which were set by development platform. More details build_unflags.

includeDir

Optional | Type: String

New in version 4.0.

Custom location of library header files. A default value is include and means that folder is located in the root of a library.

srcDir

Optional | Type: String

New in version 4.0.

Custom location of library source code. A default value is src and means that folder is located in the root of a library.

srcFilter

Optional | Type: String or Array

Specify which source files should be included/excluded from build process. The path in filter should be relative from a root of library.

See syntax in src_filter.

Please note that you can generate source filter "on-the-fly" using extraScript (see below)

extraScript

Optional | Type: String

Launch extra script before build process. More details extra_scripts.

Example (HAL-based library)

This example demonstrates how to build HAL-dependent source files and exclude other source files from a build process.

Project structure

├── lib
│   ├── README
│   └── SomeLib
│       ├── extra_script.py
│       ├── hal
│       │   ├── bar
│       │   │   ├── hal.c
│       │   │   └── hal.h
│       │   ├── foo
│       │       ├── hal.c
│       │       └── hal.h
│       ├── library.json
│       ├── SomeLib.c
│       └── SomeLib.h
├── platformio.ini
└── src
    └── test.c


platformio.ini

[env:foo]
platform = native
build_flags = -DHAL=foo
[env:bar]
platform = native
build_flags = -DHAL=bar


library.json

{
    "name": "SomeLib",
    "version": "0.0.0",
    "build": {
        "extraScript": "extra_script.py"
    }
}


extra_script.py

Import('env')
from os.path import join, realpath
# private library flags
for item in env.get("CPPDEFINES", []):
    if isinstance(item, tuple) and item[0] == "HAL":
        env.Append(CPPPATH=[realpath(join("hal", item[1]))])
        env.Replace(SRC_FILTER=["+<*>", "-<hal>", "+<%s>" % join("hal", item[1])])
        break
# pass flags to a global build environment (for all libraries, etc)
global_env = DefaultEnvironment()
global_env.Append(
    CPPDEFINES=[
        ("MQTT_MAX_PACKET_SIZE", 512),
        "ARDUINOJSON_ENABLE_STD_STRING",
        ("BUFFER_LENGTH", 32)
    ]
)


libArchive

Optional | Type: Boolean

Create an archive (*.a, static library) from the object files and link it into a firmware (program). This is default behavior of PlatformIO Build System ("libArchive": true).

Setting "libArchive": false will instruct PIO Build System to link object files directly (in-line). This could be useful if you need to override weak symbols defined in framework or other libraries.

You can disable library archiving globally using lib_archive option in "platformio.ini" (Project Configuration File).

libLDFMode

Optional | Type: String

Specify Library Dependency Finder Mode. See Dependency Finder Mode for details.

libCompatMode

Optional | Type: String

Specify Library Compatibility Mode. See Compatibility Mode for details.

1.
Custom macros/defines

"build": {
    "flags": "-D MYLIB_REV=1.2.3 -DRELEASE"
}


2.
Extra includes for C preprocessor

"build": {
    "flags": [
        "-I inc",
        "-I inc/target_x13"
    ]
}


3.
Force to use C99 standard instead of C11

"build": {
    "unflags": "-std=gnu++11",
    "flags": "-std=c99"
}


4.
Build source files (c, cpp, h) at the top level of the library

"build": {
    "srcFilter": [
        "+<*.c>",
        "+<*.cpp>",
        "+<*.h>"
    ]
}


5.
Extend PlatformIO Build System with own extra script

"build": {
    "extraScript": "generate_headers.py"
}


generate_headers.py

Import('env')
# print(env.Dump())
env.Append(
    CPPDEFINES=["HELLO=WORLD", "TAG=1.2.3", "DEBUG"],
    CPPPATH=["inc", "inc/devices"]
)
# some python code that generates header files "on-the-fly"


PlatformIO Library Manager doesn't have any requirements to a library source code structure. The only one requirement is library's manifest file - library.json, library.properties or module.json. It can be located inside your library or in the another location where PlatformIO Library Registry Crawler will have HTTP access.

Updates to existing libraries are done every 24 hours. In case a more urgent update is required, you can post a request on PlatformIO community.

•
Source Code Location
  • At GitHub
  • Under VCS (SVN/GIT)
  • Self-hosted

  • Register
  • Examples

There are a several ways how to share your library with the whole world (see examples).

You can hold a lot of libraries (split into separated folders) inside one of the repository/archive. In this case, you need to specify include option of export field to relative path to your library's source code.

Recommended

If a library source code is located at GitHub, then you need to specify only these fields in the library.json:

  • name
  • version (is not required, but highly recommended for new Library Manager)
  • keywords
  • description
  • repository

PlatformIO Library Registry Crawler will populate the rest fields, like authors with an actual information from GitHub.

Example, DallasTemperature:

{
  "name": "DallasTemperature",
  "keywords": "onewire, 1-wire, bus, sensor, temperature",
  "description": "Arduino Library for Dallas Temperature ICs (DS18B20, DS18S20, DS1822, DS1820)",
  "repository":
  {
    "type": "git",
    "url": "https://github.com/milesburton/Arduino-Temperature-Control-Library.git"
  },
  "authors":
  [
    {
      "name": "Miles Burton",
      "email": "miles@mnetcs.com",
      "url": "http://www.milesburton.com",
      "maintainer": true
    },
    {
      "name": "Tim Newsome",
      "email": "nuisance@casualhacker.net"
    },
    {
      "name": "Guil Barros",
      "email": "gfbarros@bappos.com"
    },
    {
      "name": "Rob Tillaart",
      "email": "rob.tillaart@gmail.com"
    }
  ],
  "dependencies": [
    {
      "name": "OneWire",
      "authors": "Paul Stoffregen",
      "frameworks": "arduino"
    }
  ],
  "version": "3.7.7",
  "frameworks": "arduino",
  "platforms": "*"
}


PlatformIO Library Registry Crawler can operate with a library source code that is under VCS control. The list of required fields in the library.json will look like:

  • name
  • keywords
  • description
  • authors
  • repository

Example:

{
    "name": "XBee",
    "keywords": "xbee, protocol, radio",
    "description": "Arduino library for communicating with XBees in API mode",
    "authors":
    {
        "name": "Andrew Rapp",
        "email": "andrew.rapp@gmail.com",
        "url": "https://code.google.com/u/andrew.rapp@gmail.com/"
    },
    "repository":
    {
        "type": "git",
        "url": "https://code.google.com/p/xbee-arduino/"
    },
    "frameworks": "arduino",
    "platforms": "atmelavr"
}


You can manually archive (Zip, Tar.Gz) your library source code and host it in the Internet. Then you should specify the additional fields, like version and downloadUrl. The final list of required fields in the library.json will look like:

  • name
  • keywords
  • description
  • authors
  • version
  • downloadUrl

{
    "name": "OneWire",
    "keywords": "onewire, 1-wire, bus, sensor, temperature, ibutton",
    "description": "Control devices (from Dallas Semiconductor) that use the One Wire protocol (DS18S20, DS18B20, DS2408 and etc)",
    "authors":
    {
        "name": "Paul Stoffregen",
        "url": "http://www.pjrc.com/teensy/td_libs_OneWire.html"
    },
    "version": "2.2",
    "downloadUrl": "http://www.pjrc.com/teensy/arduino_libraries/OneWire.zip",
    "export": {
        "include": "OneWire"
    },
    "frameworks": "arduino",
    "platforms": "atmelavr"
}


The registration requirements:

  • A library must adhere to the library manifest specification - library.json, library.properties or module.json.
  • There must be public HTTP access to the library manifest file.

Now, you can register your library and allow others to install it.

Command:

$ platformio lib register http://my.example.com/library.json
$ platformio lib register http://my.example.com/library.properties
$ platformio lib register http://my.example.com/module.json


  • GitHub + detached release
  • Dependencies by author and framework
  • Multiple libraries in the one repository

The PlatformIO ecosystem has a decentralized architecture, allowing development for a range of development platforms. A development platform (or just "platform" for short) is usually a particular microcontroller or processor architecture that PlatformIO projects can be compiled to run on. (A few platforms, for example Teensy, use different target architectures for different boards.)

Each of the three supported host systems Mac OS X, Linux and Windows support compiling for all platforms listed below. Some platforms are also supported under ARM Linux hosts such as Raspberry Pi. For each development platform, PlatformIO defines:

  • The PlatformIO Build System build scripts for the supported frameworks and SDKs
  • Pre-configured presets for embedded circuit boards
  • Pre-compiled toolchains and related tools for the architechture(s)

Each project must specify the platform name using the platform option in "platformio.ini" (Project Configuration File). A specific platform version can optionally be specified as well. As embedded boards are equipped with a particular microcontroller, each embedded board specifies what development platform it uses and this can not be changed.

If a new board uses an architecture not in this list, a custom development platform can be created; see Custom Development Platforms.

Aceinna IMU

platform = aceinna_imu

Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Boards

Examples are listed from Aceinna IMU development platform repository:

  • OpenIMU300RI
  • OpenIMU330BI
  • OpenRTK330LI
  • OpenIMU300ZI

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
Aceinna Low Cost RTK STM32F469NIH6 180MHz 1MB 384KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
Aceinna OpenIMU 300 STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 300ZA STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 330 STM32L431CB 80MHz 128KB 64KB
Aceinna OpenIMU 330ZA STM32F469IG 180MHz 1MB 384KB
Aceinna OpenRTK330L STM32F469IG 180MHz 1MB 384KB

Stable and upstream versions

You can switch between stable releases of Aceinna IMU development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = aceinna_imu
board = ...
; Custom stable version
[env:custom_stable]
platform = aceinna_imu@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/aceinna/platform-aceinna_imu.git
board = ...


Name Description
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-openocd OpenOCD
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Aceinna Low Cost RTK On-board STM32F469NIH6 180MHz 1MB 384KB
Aceinna OpenIMU 300 External STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 300ZA External STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 330 External STM32L431CB 80MHz 128KB 64KB
Aceinna OpenIMU 330ZA External STM32F469IG 180MHz 1MB 384KB
Aceinna OpenRTK330L External STM32F469IG 180MHz 1MB 384KB

Atmel AVR

platform = atmelavr

Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

For more detailed information please visit vendor site.

  • Configuration
  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

  • Upload using Programmer
  • Upload EEPROM data
  • Fuses programming
  • Custom fuses
  • MiniCore, MegaCore and MightyCore

•
Bootloader programming
•
Custom bootloader


To upload firmware using programmer you need to use program target instead of upload for platformio run --target command. For example, platformio run -t program.

WARNING:

Upload options like upload_port don't work as expected with platformio run -t program. You need to use upload_flags if you want to specify custom port or speed (see examples below).


NOTE:

List of avrdude supported programmers are accessible with avrdude -c ?


Configuration for the programmers:

•
AVR ISP

[env:myenv]
platform = atmelavr
framework = arduino
upload_protocol = stk500v1
; each flag in a new line
upload_flags =
    -P$UPLOAD_PORT
; edit this line with valid upload port
upload_port = SERIAL_PORT_HERE


•
AVRISP mkII

[env:myenv]
platform = atmelavr
framework = arduino
upload_protocol = stk500v2
; each flag in a new line
upload_flags =
    -Pusb


•
USBtinyISP

[env:myenv]
platform = atmelavr
framework = arduino
upload_protocol = usbtiny


•
ArduinoISP

[env:myenv]
platform = atmelavr
framework = arduino
upload_protocol = arduinoisp


•
USBasp

[env:myenv]
platform = atmelavr
framework = arduino
upload_protocol = usbasp
; each flag in a new line
upload_flags =
    -Pusb


•
Parallel Programmer

[env:myenv]
platform = atmelavr
framework = arduino
upload_protocol = dapa
; each flag in a new line
upload_flags =
    -F


•
Arduino as ISP

[env:myenv]
platform = atmelavr
framework = arduino
upload_protocol = stk500v1
; each flag in a new line
upload_flags =
    -P$UPLOAD_PORT
    -b$UPLOAD_SPEED
; edit these lines
upload_port = SERIAL_PORT_HERE
upload_speed = 19200


•
Bus Pirate as ISP

[env:myenv]
platform = atmelavr
framework = arduino
upload_protocol = buspirate
; each flag in a new line
upload_flags =
    -P$UPLOAD_PORT
    -b$UPLOAD_SPEED
; edit these lines
upload_port = SERIAL_PORT_HERE
upload_speed = 115200



To upload EEPROM data (from EEMEM directive) you need to use uploadeep target instead upload for platformio run --target command. For example, platformio run -t uploadeep.

PlatformIO has a built-in target named fuses for setting fuse bits. The default fuse bits are predefined in board manifest file in fuses section. For example, fuses section for Arduino Uno board. To set fuse bits you need to use target fuses with platformio run --target command.

Custom fuse values and upload flags (based on upload protocol) should be specified in "platformio.ini" (Project Configuration File). lfuse and hfuse bits are mandatory, efuse is optional and not supported by all targets. An example of setting custom fuses for uno board:

[env:custom_fuses]
platform = atmelavr
framework = arduino
board = uno
upload_protocol = stk500v1
upload_speed = 19200
board_fuses.lfuse = 0xAA
board_fuses.hfuse = 0xBB
board_fuses.efuse = 0xCC
upload_flags =
    -PCOM15
    -b$UPLOAD_SPEED
    -e


MiniCore, MegaCore and MightyCore support dynamic fuses generation. Generated values are based on the next parameters:

Parameter Description Default value
f_cpu Specifies the clock frequencies in Hz. Used to determine what oscillator option to choose. A capital L has to be added to the end of the frequency number. 16000000L
oscillator Specifies which oscillator is used internal or external. Internal oscillator only works with f_cpu values 8000000L and 1000000L external
uart Specifies the hardware UART port used for serial upload. can be uart0, uart1, uart2 or uart3 depending on the target. Use no_bootloader if you're not using a bootloader for serial upload. uart0
bod Specifies the hardware brown-out detection. Use disabled to disable brown-out detection. 2.7v
eesave Specifies if the EEPROM memory should be retained when uploading using a programmer. Use no to disable yes


Valid BOD values:

ATmega8, ATmega8535/16/32, ATmega64/128 AT90CAN32/64/128 Other targets
4.0v 4.1v 4.3v
2.7v 4.0v 2.7v
disabled 3.9v 1.8v
3.8v disabled
2.7v
2.6v
2.5v
disabled


Hardware configuration example:

[env:custom_fuses]
platform = atmelavr
framework = arduino
board = ATmega32
board_build.f_cpu = 1000000L
board_hardware.uart = uart0
board_hardware.oscillator = internal
board_hardware.bod = 2.7v
board_hardware.eesave = no
upload_protocol = usbasp
upload_flags =
  -Pusb


PlatformIO has a built-in target named bootloader for flashing bootloaders. The default bootloader image and corresponding fuse bits are predefined in board manifest file in bootloader section, for example, Arduino Uno. To upload bootloader image you need to use target bootloader with platformio run --target command.

Custom bootloader and corresponding fuses should be specified in "platformio.ini" (Project Configuration File). If lock_bits and unlock_bits are not set then the default values 0x0F and 0x3F are used accordingly. An example of setting custom bootloader for uno board:

[env:uno]
platform = atmelavr
framework = arduino
board = uno
board_bootloader.file = /path/to/custom/bootloader.hex
board_bootloader.lfuse = 0xFF
board_bootloader.hfuse = 0xDE
board_bootloader.efuse = 0xFD
board_bootloader.lock_bits = 0x0F
board_bootloader.unlock_bits = 0x3F


MiniCore, MegaCore and MightyCore have a wide variety of precompiled bootloaders. Bootloader binary is dynamically selected according to the hardware parameters: f_cpu, oscillator, upload_speed:

Frequency Oscillator Upload Speed
20000000L external 115200
18432000L external 115200
16000000L external 115200
14745600L external 115200
12000000L external 57600
11059200L external 115200
8000000L external/internal 57600/38400
7372800L external 115200
3686400L external 115200
1843200L external 115200
1000000L external/internal 9600


Examples are listed from Atmel AVR development platform repository:

  • arduino-blink
  • simba-blink
  • native-blink
  • arduino-own-src_dir
  • engduino-magnetometer
  • digitstump-mouse
  • arduino-internal-libs
  • arduino-external-libs

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
ATmega128/A ATMEGA128 16MHz 127KB 4KB
ATmega1280 ATMEGA1280 16MHz 127KB 8KB
ATmega1281 ATMEGA1281 16MHz 127KB 8KB
ATmega1284 ATMEGA1284 16MHz 127KB 16KB
ATmega1284P ATMEGA1284P 16MHz 127KB 16KB
ATmega16 ATMEGA16 16MHz 15.50KB 1KB
ATmega164P/PA ATMEGA164P 16MHz 15.50KB 1KB
ATmega168/A ATMEGA168 16MHz 15.50KB 1KB
ATmega168P/PA ATMEGA168P 16MHz 15.50KB 1KB
ATmega2560 ATMEGA2560 16MHz 255KB 8KB
ATmega324A ATMEGA324A 16MHz 31.50KB 2KB
ATmega324P ATMEGA324P 16MHz 31.50KB 2KB
ATmega324PA ATMEGA324PA 16MHz 31.50KB 2KB
ATmega328 ATMEGA328 16MHz 31.50KB 2KB
ATmega328P/PA ATMEGA328P 16MHz 31.50KB 2KB
ATmega48/A ATMEGA48 16MHz 4KB 512B
ATmega644P/PA ATMEGA644P 16MHz 63KB 4KB
ATmega8/A ATMEGA8 16MHz 7.50KB 1KB
ATmega88/A ATMEGA88 16MHz 7.50KB 1KB
ATmega88P/PA ATMEGA88P 16MHz 7.50KB 1KB
ATmega8P/PA ATMEGA48P 16MHz 4KB 512B
Adafruit Bluefruit Micro ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Circuit Playground Classic ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Feather 328P ATMEGA328P 8MHz 31.50KB 2KB
Adafruit Feather 32u4 ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Flora ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Gemma ATTINY85 8MHz 8KB 512B
Adafruit ItsyBitsy 3V/8MHz ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit ItsyBitsy 5V/16MHz ATMEGA32U4 16MHz 28KB 2.50KB
Adafruit Metro ATMEGA328P 16MHz 31.50KB 2KB
Adafruit Pro Trinket 3V/12MHz (FTDI) ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 3V/12MHz (USB) ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (FTDI) ATMEGA328P 16MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (USB) ATMEGA328P 16MHz 28KB 2KB
Adafruit Trinket 3V/8MHz ATTINY85 8MHz 8KB 512B
Adafruit Trinket 5V/16MHz ATTINY85 16MHz 8KB 512B
Alorium Hinj ATMEGA328P 16MHz 31.50KB 2KB
Alorium Sno ATMEGA328P 16MHz 31.50KB 2KB
Alorium XLR8 ATMEGA328P 16MHz 31.50KB 2KB
Anarduino MiniWireless ATMEGA328P 16MHz 31.50KB 2KB
Arduboy ATMEGA32U4 16MHz 28KB 2.50KB
Arduboy DevKit ATMEGA32U4 16MHz 28KB 2.50KB
Arduino BT ATmega168 ATMEGA168 16MHz 14KB 1KB
Arduino BT ATmega328 ATMEGA328P 16MHz 28KB 2KB
Arduino Duemilanove or Diecimila ATmega168 ATMEGA168 16MHz 14KB 1KB
Arduino Duemilanove or Diecimila ATmega328 ATMEGA328P 16MHz 30KB 2KB
Arduino Esplora ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Ethernet ATMEGA328P 16MHz 31.50KB 2KB
Arduino Fio ATMEGA328P 8MHz 30KB 2KB
Arduino Industrial 101 ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo ETH ATMEGA32U4 16MHz 28KB 2.50KB
Arduino LilyPad ATmega168 ATMEGA168 8MHz 14KB 1KB
Arduino LilyPad ATmega328 ATMEGA328P 8MHz 30KB 2KB
Arduino LilyPad USB ATMEGA32U4 8MHz 28KB 2.50KB
Arduino Mega ADK ATMEGA2560 16MHz 248KB 8KB
Arduino Mega or Mega 2560 ATmega1280 ATMEGA1280 16MHz 124KB 8KB
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) ATMEGA2560 16MHz 248KB 8KB
Arduino Micro ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Mini ATmega168 ATMEGA168 16MHz 14KB 1KB
Arduino Mini ATmega328 ATMEGA328P 16MHz 28KB 2KB
Arduino NG or older ATmega168 ATMEGA168 16MHz 14KB 1KB
Arduino NG or older ATmega8 ATMEGA8 16MHz 7KB 1KB
Arduino Nano ATmega168 ATMEGA168 16MHz 14KB 1KB
Arduino Nano ATmega328 ATMEGA328P 16MHz 30KB 2KB
Arduino Nano ATmega328 (New Bootloader) ATMEGA328P 16MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) ATMEGA168 8MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) ATMEGA168 16MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) ATMEGA328P 8MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) ATMEGA328P 16MHz 30KB 2KB
Arduino Robot Control ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Robot Motor ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Uno ATMEGA328P 16MHz 31.50KB 2KB
Arduino Yun ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Yun Mini ATMEGA32U4 16MHz 28KB 2.50KB
BQ ZUM BT-328 ATMEGA328P 16MHz 28KB 2KB
BitWizard Raspduino ATMEGA328P 16MHz 30KB 2KB
Controllino Maxi ATMEGA2560 16MHz 248KB 8KB
Controllino Maxi Automation ATMEGA2560 16MHz 248KB 8KB
Controllino Mega ATMEGA2560 16MHz 248KB 8KB
Controllino Mini ATMEGA328P 16MHz 31.50KB 2KB
Digispark USB ATTINY85 16MHz 5.87KB 512B
Engduino 3 ATMEGA32U4 8MHz 28KB 2.50KB
EnviroDIY Mayfly ATMEGA1284P 8MHz 127KB 16KB
FYSETC F6 V1.3 ATMEGA2560 16MHz 252KB 8KB
Generic ATtiny13 ATTINY13 1MHz 1KB 64B
Generic ATtiny13A ATTINY13A 1MHz 1KB 64B
Generic ATtiny2313 ATTINY2313 8MHz 2KB 128B
Generic ATtiny24 ATTINY24 8MHz 2KB 128B
Generic ATtiny25 ATTINY25 8MHz 2KB 128B
Generic ATtiny4313 ATTINY4313 8MHz 4KB 256B
Generic ATtiny44 ATTINY44 8MHz 4KB 256B
Generic ATtiny45 ATTINY45 8MHz 4KB 256B
Generic ATtiny84 ATTINY84 8MHz 8KB 512B
Generic ATtiny85 ATTINY85 8MHz 8KB 512B
LightBlue Bean ATMEGA328P 8MHz 31.50KB 2KB
LightBlue Bean+ ATMEGA328P 16MHz 31.50KB 2KB
LightUp ATMEGA32U4 8MHz 28KB 2.50KB
Linino One ATMEGA32U4 16MHz 28KB 2.50KB
LinkIt Smart 7688 Duo ATMEGA32U4 8MHz 28KB 2.50KB
LoRa32u4II (868-915MHz) ATMEGA32U4 8MHz 28KB 2.50KB
LowPowerLab MightyHat ATMEGA328P 16MHz 31KB 2KB
LowPowerLab Moteino ATMEGA328P 16MHz 31.50KB 2KB
LowPowerLab Moteino (8Mhz) ATMEGA328P 8MHz 31.50KB 2KB
LowPowerLab MoteinoMEGA ATMEGA1284P 16MHz 127KB 16KB
Microduino Core (Atmega168PA@16M,5V) ATMEGA168P 16MHz 15.50KB 1KB
Microduino Core (Atmega168PA@8M,3.3V) ATMEGA168P 8MHz 15.50KB 1KB
Microduino Core (Atmega328P@16M,5V) ATMEGA328P 16MHz 31.50KB 2KB
Microduino Core (Atmega328P@8M,3.3V) ATMEGA328P 8MHz 31.50KB 2KB
Microduino Core USB (ATmega32U4@16M,5V) ATMEGA32U4 16MHz 28KB 2.50KB
Microduino Core+ (ATmega1284P@16M,5V) ATMEGA1284P 16MHz 127KB 16KB
Microduino Core+ (ATmega1284P@8M,3.3V) ATMEGA1284P 8MHz 127KB 16KB
Microduino Core+ (Atmega644PA@16M,5V) ATMEGA644P 16MHz 63KB 4KB
Microduino Core+ (Atmega644PA@8M,3.3V) ATMEGA644P 8MHz 63KB 4KB
OpenEnergyMonitor emonPi ATMEGA328P 16MHz 30KB 2KB
Original Prusa i3 MK3 Multi Material 2.0 Upgrade ATMEGA32U4 16MHz 28KB 2.50KB
PanStamp AVR ATMEGA328P 8MHz 31.50KB 2KB
Pololu A-Star 32U4 ATMEGA32U4 16MHz 28KB 2.50KB
Prusa RAMBo ATMEGA2560 16MHz 252KB 8KB
Quirkbot ATMEGA32U4 8MHz 28KB 2.50KB
RedBearLab Blend ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend Micro 3.3V/16MHz (overclock) ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend Micro 3.3V/8MHz ATMEGA32U4 8MHz 28KB 2.50KB
RepRap RAMBo ATMEGA2560 16MHz 252KB 8KB
SODAQ GaLoRa ATMEGA1284P 8MHz 127KB 16KB
SODAQ Mbili ATMEGA1284P 8MHz 127KB 16KB
SODAQ Moja ATMEGA328P 8MHz 31.50KB 2KB
SODAQ Ndogo ATMEGA1284P 8MHz 127KB 16KB
SODAQ Tatu ATMEGA1284P 8MHz 127KB 16KB
Sanguino ATmega1284p (16MHz) ATMEGA1284P 16MHz 127KB 16KB
Sanguino ATmega1284p (8MHz) ATMEGA1284P 8MHz 127KB 16KB
Sanguino ATmega644 or ATmega644A (16 MHz) ATMEGA644 16MHz 63KB 4KB
Sanguino ATmega644 or ATmega644A (8 MHz) ATMEGA644 8MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (16 MHz) ATMEGA644P 16MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (8 MHz) ATMEGA644P 8MHz 63KB 4KB
Seeeduino ATMEGA328P 16MHz 31.50KB 2KB
SparkFun ATmega128RFA1 Dev Board ATMEGA128RFA1 16MHz 16KB 124KB
SparkFun Digital Sandbox ATMEGA328P 8MHz 31.50KB 2KB
SparkFun Fio V3 3.3V/8MHz ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Makey Makey ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Mega Pro 3.3V/8MHz ATMEGA2560 8MHz 252KB 8KB
SparkFun Mega Pro 5V/16MHz ATMEGA2560 16MHz 248KB 8KB
SparkFun Mega Pro Mini 3.3V ATMEGA2560 8MHz 252KB 8KB
SparkFun MicroView ATMEGA328P 16MHz 31.50KB 2KB
SparkFun Pro Micro 3.3V/8MHz ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Pro Micro 5V/16MHz ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Qduino Mini ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun RedBoard ATMEGA328P 16MHz 31.50KB 2KB
SparkFun Serial 7-Segment Display ATMEGA328P 8MHz 31.50KB 2KB
SpellFoundry Sleepy Pi 2 ATMEGA328P 8MHz 30KB 2KB
Talk2 Whisper Node ATMEGA328P 16MHz 31.50KB 2KB
The Things Uno ATMEGA32U4 16MHz 28KB 2.50KB
TinyCircuits TinyDuino Processor Board ATMEGA328P 8MHz 30KB 2KB
TinyCircuits TinyLily Mini Processor ATMEGA328P 8MHz 30KB 2KB
USBasp stick ATMEGA8 12MHz 8KB 1KB
Wicked Device WildFire V2 ATMEGA1284P 16MHz 120.00KB 16KB
Wicked Device WildFire V3 ATMEGA1284P 16MHz 127KB 16KB
ftDuino ATMEGA32U4 16MHz 28KB 2.50KB
nicai-systems BOB3 coding bot ATMEGA88 8MHz 8KB 1KB
nicai-systems NIBO 2 robot ATMEGA128 16MHz 128KB 4KB
nicai-systems NIBO burger robot ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBO burger robot with Tuning Kit ATMEGA1284P 20MHz 128KB 16KB
nicai-systems NIBObee robot ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBObee robot with Tuning Kit ATMEGA1284P 20MHz 128KB 16KB
ubIQio Ardhat ATMEGA328P 16MHz 31.50KB 2KB

Stable and upstream versions

You can switch between stable releases of Atmel AVR development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = atmelavr
board = ...
; Custom stable version
[env:custom_stable]
platform = atmelavr@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-atmelavr.git
board = ...


Name Description
framework-arduino-avr Arduino Wiring-based Framework (AVR Core)
framework-arduino-avr-attiny Arduino Wiring-based Framework (ATTiny Core)
framework-arduino-avr-bean Arduino Wiring-based Framework (Bean Core)
framework-arduino-avr-core13 Arduino Wiring-based Framework (Core13)
framework-arduino-avr-digistump Arduino Wiring-based Framework (Digistump Core)
framework-arduino-avr-dwenguino Arduino Wiring-based Framework (Dwenguino Core)
framework-arduino-avr-majorcore Arduino Wiring-based Framework (Major Core)
framework-arduino-avr-megacore Arduino Wiring-based Framework (MegaCore)
framework-arduino-avr-mightycore Arduino Wiring-based Framework (MightyCore)
framework-arduino-avr-minicore Arduino Wiring-based Framework (MiniCore)
framework-arduino-avr-nicai Arduino Wiring-based Framework (Nicai Core)
framework-arduino-avr-panstamp Arduino Wiring-based Framework (Panstamp Core)
framework-arduino-avr-prusa_rambo Arduino Wiring-based Framework (Prusa Rambo Core)
framework-simba Simba Framework
tool-avrdude AVRDUDE
tool-micronucleus Micronucleus
tool-simavr simavr is a lean, mean and hackable AVR simulator
toolchain-atmelavr avr-gcc

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Adafruit Bluefruit Micro On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Circuit Playground Classic On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Feather 328P On-board ATMEGA328P 8MHz 31.50KB 2KB
Adafruit Feather 32u4 On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Flora On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Gemma On-board ATTINY85 8MHz 8KB 512B
Adafruit ItsyBitsy 3V/8MHz On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit ItsyBitsy 5V/16MHz On-board ATMEGA32U4 16MHz 28KB 2.50KB
Adafruit Metro On-board ATMEGA328P 16MHz 31.50KB 2KB
Adafruit Pro Trinket 3V/12MHz (FTDI) On-board ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 3V/12MHz (USB) On-board ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (FTDI) On-board ATMEGA328P 16MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (USB) On-board ATMEGA328P 16MHz 28KB 2KB
Adafruit Trinket 3V/8MHz On-board ATTINY85 8MHz 8KB 512B
Adafruit Trinket 5V/16MHz On-board ATTINY85 16MHz 8KB 512B

Alorium Technology

Name Debug MCU Frequency Flash RAM
Alorium Hinj On-board ATMEGA328P 16MHz 31.50KB 2KB
Alorium Sno On-board ATMEGA328P 16MHz 31.50KB 2KB
Alorium XLR8 On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Debug MCU Frequency Flash RAM
Anarduino MiniWireless On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Debug MCU Frequency Flash RAM
Arduboy On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduboy DevKit On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Debug MCU Frequency Flash RAM
Arduino BT ATmega168 On-board ATMEGA168 16MHz 14KB 1KB
Arduino BT ATmega328 On-board ATMEGA328P 16MHz 28KB 2KB
Arduino Duemilanove or Diecimila ATmega168 On-board ATMEGA168 16MHz 14KB 1KB
Arduino Duemilanove or Diecimila ATmega328 On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Esplora On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Ethernet On-board ATMEGA328P 16MHz 31.50KB 2KB
Arduino Fio On-board ATMEGA328P 8MHz 30KB 2KB
Arduino Industrial 101 On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo ETH On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino LilyPad ATmega168 On-board ATMEGA168 8MHz 14KB 1KB
Arduino LilyPad ATmega328 On-board ATMEGA328P 8MHz 30KB 2KB
Arduino LilyPad USB On-board ATMEGA32U4 8MHz 28KB 2.50KB
Arduino Mega ADK On-board ATMEGA2560 16MHz 248KB 8KB
Arduino Mega or Mega 2560 ATmega1280 On-board ATMEGA1280 16MHz 124KB 8KB
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) On-board ATMEGA2560 16MHz 248KB 8KB
Arduino Micro On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Mini ATmega168 On-board ATMEGA168 16MHz 14KB 1KB
Arduino Mini ATmega328 On-board ATMEGA328P 16MHz 28KB 2KB
Arduino NG or older ATmega168 On-board ATMEGA168 16MHz 14KB 1KB
Arduino NG or older ATmega8 On-board ATMEGA8 16MHz 7KB 1KB
Arduino Nano ATmega168 On-board ATMEGA168 16MHz 14KB 1KB
Arduino Nano ATmega328 On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Nano ATmega328 (New Bootloader) On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) On-board ATMEGA168 8MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) On-board ATMEGA168 16MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) On-board ATMEGA328P 8MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Robot Control On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Robot Motor On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Uno On-board ATMEGA328P 16MHz 31.50KB 2KB
Arduino Yun On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Yun Mini On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Debug MCU Frequency Flash RAM
Generic ATtiny13 On-board ATTINY13 1MHz 1KB 64B
Generic ATtiny13A On-board ATTINY13A 1MHz 1KB 64B
Generic ATtiny1634 No ATTINY1634 8MHz 16KB 1KB
Generic ATtiny167 No ATTINY167 8MHz 16KB 512B
Generic ATtiny2313 On-board ATTINY2313 8MHz 2KB 128B
Generic ATtiny24 On-board ATTINY24 8MHz 2KB 128B
Generic ATtiny25 On-board ATTINY25 8MHz 2KB 128B
Generic ATtiny261 No ATTINY261 8MHz 2KB 128B
Generic ATtiny4313 On-board ATTINY4313 8MHz 4KB 256B
Generic ATtiny43U No ATTINY43U 8MHz 4KB 256B
Generic ATtiny44 On-board ATTINY44 8MHz 4KB 256B
Generic ATtiny441 No ATTINY441 8MHz 4KB 256B
Generic ATtiny45 On-board ATTINY45 8MHz 4KB 256B
Generic ATtiny461 No ATTINY461 8MHz 4KB 256B
Generic ATtiny48 No ATTINY48 8MHz 4KB 256B
Generic ATtiny828 No ATTINY828 8MHz 8KB 512B
Generic ATtiny84 On-board ATTINY84 8MHz 8KB 512B
Generic ATtiny841 No ATTINY841 8MHz 8KB 512B
Generic ATtiny85 On-board ATTINY85 8MHz 8KB 512B
Generic ATtiny861 No ATTINY861 8MHz 8KB 512B
Generic ATtiny87 No ATTINY87 8MHz 8KB 512B
Generic ATtiny88 No ATTINY88 8MHz 8KB 512B
USBasp stick On-board ATMEGA8 12MHz 8KB 1KB

Name Debug MCU Frequency Flash RAM
BQ ZUM BT-328 On-board ATMEGA328P 16MHz 28KB 2KB

Name Debug MCU Frequency Flash RAM
LoRa32u4II (868-915MHz) On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Debug MCU Frequency Flash RAM
BitWizard Raspduino On-board ATMEGA328P 16MHz 30KB 2KB

Name Debug MCU Frequency Flash RAM
Controllino Maxi On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Maxi Automation On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Mega On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Mini On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Debug MCU Frequency Flash RAM
Digispark Pro No ATTINY167 16MHz 14.50KB 512B
Digispark Pro (16 MHz) (64 byte buffer) No ATTINY167 16MHz 14.50KB 512B
Digispark Pro (32 byte buffer) No ATTINY167 16MHz 14.50KB 512B
Digispark USB On-board ATTINY85 16MHz 5.87KB 512B

Name Debug MCU Frequency Flash RAM
Dwenguino No AT90USB646 16MHz 60KB 2KB

Name Debug MCU Frequency Flash RAM
Elektor Uno R4 No ATMEGA328PB 16MHz 31.50KB 2KB

Name Debug MCU Frequency Flash RAM
Engduino 3 On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Debug MCU Frequency Flash RAM
EnviroDIY Mayfly On-board ATMEGA1284P 8MHz 127KB 16KB

Name Debug MCU Frequency Flash RAM
FYSETC F6 V1.3 On-board ATMEGA2560 16MHz 252KB 8KB

Name Debug MCU Frequency Flash RAM
LightUp On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Debug MCU Frequency Flash RAM
Linino One On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Debug MCU Frequency Flash RAM
LowPowerLab MightyHat On-board ATMEGA328P 16MHz 31KB 2KB
LowPowerLab Moteino On-board ATMEGA328P 16MHz 31.50KB 2KB
LowPowerLab Moteino (8Mhz) On-board ATMEGA328P 8MHz 31.50KB 2KB
LowPowerLab MoteinoMEGA On-board ATMEGA1284P 16MHz 127KB 16KB

MediaTek Labs

Name Debug MCU Frequency Flash RAM
LinkIt Smart 7688 Duo On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Debug MCU Frequency Flash RAM
AT90CAN128 No AT90CAN128 16MHz 127KB 4KB
AT90CAN32 No AT90CAN32 16MHz 31KB 2KB
AT90CAN64 No AT90CAN64 16MHz 63KB 4KB
ATmega128/A On-board ATMEGA128 16MHz 127KB 4KB
ATmega1280 On-board ATMEGA1280 16MHz 127KB 8KB
ATmega1281 On-board ATMEGA1281 16MHz 127KB 8KB
ATmega1284 On-board ATMEGA1284 16MHz 127KB 16KB
ATmega1284P On-board ATMEGA1284P 16MHz 127KB 16KB
ATmega16 On-board ATMEGA16 16MHz 15.50KB 1KB
ATmega162 No ATMEGA162 16MHz 15.50KB 1KB
ATmega164A No ATMEGA164A 16MHz 15.50KB 1KB
ATmega164P/PA On-board ATMEGA164P 16MHz 15.50KB 1KB
ATmega168/A On-board ATMEGA168 16MHz 15.50KB 1KB
ATmega168P/PA On-board ATMEGA168P 16MHz 15.50KB 1KB
ATmega168PB No ATMEGA168PB 16MHz 15.50KB 1KB
ATmega2560 On-board ATMEGA2560 16MHz 255KB 8KB
ATmega2561 No ATMEGA2561 16MHz 255KB 8KB
ATmega32 No ATMEGA32 16MHz 31.50KB 2KB
ATmega324A On-board ATMEGA324A 16MHz 31.50KB 2KB
ATmega324P On-board ATMEGA324P 16MHz 31.50KB 2KB
ATmega324PA On-board ATMEGA324PA 16MHz 31.50KB 2KB
ATmega324PB No ATMEGA324PB 16MHz 31.50KB 2KB
ATmega328 On-board ATMEGA328 16MHz 31.50KB 2KB
ATmega328P/PA On-board ATMEGA328P 16MHz 31.50KB 2KB
ATmega328PB No ATMEGA328PB 16MHz 31.50KB 2KB
ATmega48/A On-board ATMEGA48 16MHz 4KB 512B
ATmega48PB No ATMEGA48PB 16MHz 4KB 512B
ATmega64/A No ATMEGA64 16MHz 63KB 4KB
ATmega640 No ATMEGA640 16MHz 63KB 8KB
ATmega644/A No ATMEGA644A 16MHz 63KB 4KB
ATmega644P/PA On-board ATMEGA644P 16MHz 63KB 4KB
ATmega8/A On-board ATMEGA8 16MHz 7.50KB 1KB
ATmega8515 No ATMEGA8515 16MHz 7.50KB 512B
ATmega8535 No ATMEGA8535 16MHz 7.50KB 512B
ATmega88/A On-board ATMEGA88 16MHz 7.50KB 1KB
ATmega88P/PA On-board ATMEGA88P 16MHz 7.50KB 1KB
ATmega88PB No ATMEGA88PB 16MHz 7.50KB 1KB
ATmega8P/PA On-board ATMEGA48P 16MHz 4KB 512B
Atmel AT90PWM216 No AT90PWM216 16MHz 16KB 1KB
Atmel AT90PWM316 No AT90PWM316 16MHz 16KB 1KB

Name Debug MCU Frequency Flash RAM
Microduino Core (Atmega168PA@16M,5V) On-board ATMEGA168P 16MHz 15.50KB 1KB
Microduino Core (Atmega168PA@8M,3.3V) On-board ATMEGA168P 8MHz 15.50KB 1KB
Microduino Core (Atmega328P@16M,5V) On-board ATMEGA328P 16MHz 31.50KB 2KB
Microduino Core (Atmega328P@8M,3.3V) On-board ATMEGA328P 8MHz 31.50KB 2KB
Microduino Core USB (ATmega32U4@16M,5V) On-board ATMEGA32U4 16MHz 28KB 2.50KB
Microduino Core+ (ATmega1284P@16M,5V) On-board ATMEGA1284P 16MHz 127KB 16KB
Microduino Core+ (ATmega1284P@8M,3.3V) On-board ATMEGA1284P 8MHz 127KB 16KB
Microduino Core+ (Atmega644PA@16M,5V) On-board ATMEGA644P 16MHz 63KB 4KB
Microduino Core+ (Atmega644PA@8M,3.3V) On-board ATMEGA644P 8MHz 63KB 4KB

Name Debug MCU Frequency Flash RAM
OpenEnergyMonitor emonPi On-board ATMEGA328P 16MHz 30KB 2KB

Name Debug MCU Frequency Flash RAM
PanStamp AVR On-board ATMEGA328P 8MHz 31.50KB 2KB

Name Debug MCU Frequency Flash RAM
Pinoccio Scout No ATMEGA256RFR2 16MHz 248KB 32KB

Pololu Corporation

Name Debug MCU Frequency Flash RAM
Pololu A-Star 32U4 On-board ATMEGA32U4 16MHz 28KB 2.50KB

Prusa 3D

Name Debug MCU Frequency Flash RAM
Original Prusa i3 MK3 Multi Material 2.0 Upgrade On-board ATMEGA32U4 16MHz 28KB 2.50KB
Prusa RAMBo On-board ATMEGA2560 16MHz 252KB 8KB

Punch Through

Name Debug MCU Frequency Flash RAM
LightBlue Bean On-board ATMEGA328P 8MHz 31.50KB 2KB
LightBlue Bean+ On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Debug MCU Frequency Flash RAM
Quirkbot On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Debug MCU Frequency Flash RAM
RedBearLab Blend On-board ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend Micro 3.3V/16MHz (overclock) On-board ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend Micro 3.3V/8MHz On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Debug MCU Frequency Flash RAM
RepRap RAMBo On-board ATMEGA2560 16MHz 252KB 8KB

Name Debug MCU Frequency Flash RAM
SODAQ GaLoRa On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ Mbili On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ Moja On-board ATMEGA328P 8MHz 31.50KB 2KB
SODAQ Ndogo On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ Tatu On-board ATMEGA1284P 8MHz 127KB 16KB

Name Debug MCU Frequency Flash RAM
Sanguino ATmega1284p (16MHz) On-board ATMEGA1284P 16MHz 127KB 16KB
Sanguino ATmega1284p (8MHz) On-board ATMEGA1284P 8MHz 127KB 16KB
Sanguino ATmega644 or ATmega644A (16 MHz) On-board ATMEGA644 16MHz 63KB 4KB
Sanguino ATmega644 or ATmega644A (8 MHz) On-board ATMEGA644 8MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (16 MHz) On-board ATMEGA644P 16MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (8 MHz) On-board ATMEGA644P 8MHz 63KB 4KB

Name Debug MCU Frequency Flash RAM
Seeeduino On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Debug MCU Frequency Flash RAM
SparkFun ATmega128RFA1 Dev Board On-board ATMEGA128RFA1 16MHz 16KB 124KB
SparkFun Digital Sandbox On-board ATMEGA328P 8MHz 31.50KB 2KB
SparkFun Fio V3 3.3V/8MHz On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Makey Makey On-board ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Mega Pro 3.3V/8MHz On-board ATMEGA2560 8MHz 252KB 8KB
SparkFun Mega Pro 5V/16MHz On-board ATMEGA2560 16MHz 248KB 8KB
SparkFun Mega Pro Mini 3.3V On-board ATMEGA2560 8MHz 252KB 8KB
SparkFun MicroView On-board ATMEGA328P 16MHz 31.50KB 2KB
SparkFun Pro Micro 3.3V/8MHz On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Pro Micro 5V/16MHz On-board ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Qduino Mini On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun RedBoard On-board ATMEGA328P 16MHz 31.50KB 2KB
SparkFun Serial 7-Segment Display On-board ATMEGA328P 8MHz 31.50KB 2KB

Name Debug MCU Frequency Flash RAM
SpellFoundry Sleepy Pi 2 On-board ATMEGA328P 8MHz 30KB 2KB

The Things Network

Name Debug MCU Frequency Flash RAM
The Things Uno On-board ATMEGA32U4 16MHz 28KB 2.50KB

Till Harbaum

Name Debug MCU Frequency Flash RAM
ftDuino On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Debug MCU Frequency Flash RAM
TinyCircuits TinyDuino Processor Board On-board ATMEGA328P 8MHz 30KB 2KB
TinyCircuits TinyLily Mini Processor On-board ATMEGA328P 8MHz 30KB 2KB

Wicked Device

Name Debug MCU Frequency Flash RAM
Wicked Device WildFire V2 On-board ATMEGA1284P 16MHz 120.00KB 16KB
Wicked Device WildFire V3 On-board ATMEGA1284P 16MHz 127KB 16KB

Name Debug MCU Frequency Flash RAM
Talk2 Whisper Node On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Debug MCU Frequency Flash RAM
Altair No ATMEGA256RFR2 16MHz 248KB 32KB

Name Debug MCU Frequency Flash RAM
nicai-systems BOB3 coding bot On-board ATMEGA88 8MHz 8KB 1KB
nicai-systems NIBO 2 robot On-board ATMEGA128 16MHz 128KB 4KB
nicai-systems NIBO burger robot On-board ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBO burger robot with Tuning Kit On-board ATMEGA1284P 20MHz 128KB 16KB
nicai-systems NIBObee robot On-board ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBObee robot with Tuning Kit On-board ATMEGA1284P 20MHz 128KB 16KB

Name Debug MCU Frequency Flash RAM
ubIQio Ardhat On-board ATMEGA328P 16MHz 31.50KB 2KB

Atmel megaAVR

platform = atmelmegaavr

8-bit MCUs Built for Real-time Control with Core Independent Peripherals combining intelligent hardware peripherals along with the low-power capability of an AVR core, megaAVR microcontrollers (MCUs) broaden the effectiveness of your real-time control systems.

For more detailed information please visit vendor site.

  • Examples
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Atmel megaAVR development platform repository:

  • arduino-blink
  • native-blink
  • arduino-internal-libs
  • arduino-external-libs

Stable and upstream versions

You can switch between stable releases of Atmel megaAVR development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = atmelmegaavr
board = ...
; Custom stable version
[env:custom_stable]
platform = atmelmegaavr@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-atmelmegaavr.git
board = ...


Name Description
framework-arduino-megaavr Arduino Wiring-based Framework (megaAVR Core)
tool-avrdude-megaavr AVRDUDE for megaAVR
toolchain-atmelavr avr-gcc

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Arduino Nano Every No ATMEGA4809 16MHz 47.50KB 6KB
Arduino Uno WiFi Rev2 No ATMEGA4809 16MHz 47.50KB 6KB

Atmel SAM

platform = atmelsam

Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Atmel SAM development platform repository:

  • mbed-blink
  • mbed-serial
  • zephyr-blink
  • zephyr-drivers-i2c-scanner
  • zephyr-subsys-logger
  • mbed-events
  • arduino-blink
  • simba-blink
  • arduino-internal-libs
  • arduino-external-libs
  • mbed-dsp
  • arduino-web-thing-led
  • arduino-briki-internal-libs

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
Arduino M0 Pro (Programming/Debug Port) SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (Programming/Debug Port) SAMD21G18A 48MHz 256KB 32KB
Atmel ATSAMR21-XPRO SAMR21G18A 48MHz 256KB 32KB
Atmel ATSAMW25-XPRO SAMD21G18A 48MHz 256KB 32KB
Atmel SAMC21-XPRO SAMC21J18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO SAMD21J18A 48MHz 256KB 32KB
Atmel SAML21-XPRO-B SAML21J18B 48MHz 256KB 32KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
Adafruit Circuit Playground Express SAMD21G18A 48MHz 256KB 32KB
Adafruit Crickit M0 SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 Express SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M4 Express SAMD51J19A 120MHz 512KB 192KB
Adafruit Gemma M0 SAMD21E18A 48MHz 256KB 32KB
Adafruit Grand Central M4 SAMD51P20A 120MHz 1MB 256KB
Adafruit Hallowing M0 SAMD21G18A 48MHz 256KB 32KB
Adafruit Hallowing M4 SAMD51J19A 120MHz 496KB 192KB
Adafruit ItsyBitsy M0 SAMD21G18A 48MHz 256KB 32KB
Adafruit ItsyBitsy M4 SAMD51G19A 120MHz 512KB 192KB
Adafruit MONSTER M4SK SAMD51G19A 120MHz 496KB 192KB
Adafruit Metro M0 Expresss SAMD21G18A 48MHz 256KB 32KB
Adafruit Metro M4 SAMD51J19A 120MHz 512KB 192KB
Adafruit Metro M4 AirLift Lite SAMD51J19A 120MHz 512KB 192KB
Adafruit PyGamer Advance M4 SAMD51J20A 120MHz 1MB 256KB
Adafruit PyGamer M4 Express SAMD51J19A 120MHz 512KB 192KB
Adafruit PyPortal M4 SAMD51J20A 120MHz 1MB 256KB
Adafruit PyPortal M4 Titano SAMD51J20A 120MHz 1MB 256KB
Adafruit Trellis M4 SAMD51J19A 120MHz 512KB 192KB
Adafruit Trinket M0 SAMD21E18A 48MHz 256KB 32KB
Adafruit pIRkey SAMD21E18A 48MHz 256KB 32KB
Adafruit pyBadge AirLift M4 SAMD51J20A 120MHz 1008KB 192KB
Adafruit pyBadge M4 Express SAMD51J19A 120MHz 512KB 192KB
Arduino Due (Programming Port) AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) AT91SAM3X8E 84MHz 512KB 96KB
Arduino M0 SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Native USB Port) SAMD21G18A 48MHz 256KB 32KB
Arduino MKR FOX 1200 SAMD21G18A 48MHz 256KB 32KB
Arduino MKR GSM 1400 SAMD21G18A 48MHz 256KB 32KB
Arduino MKR NB 1500 SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1300 SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1310 SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WiFi 1010 SAMD21G18A 48MHz 256KB 32KB
Arduino MKR1000 SAMD21G18A 48MHz 256KB 32KB
Arduino MKRZERO SAMD21G18A 48MHz 256KB 32KB
Arduino Tian SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (USB Native Port) SAMD21G18A 48MHz 256KB 32KB
Briki ABC (MBC-WB) - Samd21 SAMD21G18A 48MHz 256KB 32KB
Briki MBC-WB - Samd21 SAMD21G18A 48MHz 256KB 32KB
Digistump DigiX AT91SAM3X8E 84MHz 512KB 96KB
MKR Vidor 4000 SAMD21G18A 48MHz 256KB 32KB
Minitronics v2.0 SAMD21J18A 48MHz 256KB 32KB
Moteino M0 SAMD21G18A 48MHz 256KB 32KB
NANO 33 IoT SAMD21G18A 48MHz 256KB 32KB
SODAQ Autonomo SAMD21J18A 48MHz 256KB 32KB
SODAQ ExpLoRer SAMD21J18A 48MHz 256KB 32KB
SODAQ ONE SAMD21G18A 48MHz 256KB 32KB
SODAQ SARA SAMD21J18A 48MHz 256KB 32KB
SODAQ SFF SAMD21G18A 48MHz 256KB 32KB
SainSmart Due (Programming Port) AT91SAM3X8E 84MHz 512KB 96KB
SainSmart Due (USB Native Port) AT91SAM3X8E 84MHz 512KB 96KB
Seeeduino LoRaWAN SAMD21G18A 48MHz 256KB 32KB
SparkFun 9DoF Razor IMU M0 SAMD21G18A 48MHz 256KB 32KB
SparkFun Qwiic Micro SAMD21E18A 48MHz 256KB 32KB
SparkFun RedBoard Turbo SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Dev Breakout SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Mini Breakout SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Pro RF SAMD21G18A 48MHz 256KB 32KB
Tuino 096 SAMD21G18A 48MHz 256KB 32KB

Stable and upstream versions

You can switch between stable releases of Atmel SAM development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = atmelsam
board = ...
; Custom stable version
[env:custom_stable]
platform = atmelsam@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-atmelsam.git
board = ...


Name Description
framework-arduino-mbcwb Fork of Arduino framework for briki MBC-WB boards
framework-arduino-sam Arduino Wiring-based Framework (SAM Core)
framework-arduino-samd Arduino Wiring-based Framework (SAMD Core)
framework-arduino-samd-adafruit Arduino Wiring-based Framework (Adafruit SAMD Core)
framework-arduino-samd-moteino Arduino Wiring-based Framework (Moteino SAMD Core)
framework-arduino-samd-reprap Arduino Wiring-based Framework (RepRap SAMD Core)
framework-arduino-samd-sodaq Arduino Wiring-based Framework (SODAQ SAMD Core)
framework-arduino-samd-sparkfun Arduino Wiring-based Framework (SparkFun SAMD Core)
framework-arduino-samd-tuino0 Arduino Wiring-based Framework (Tuino0 SAMD Core)
framework-cmsis Vendor-independent hardware abstraction layer for the Cortex-M processor series
framework-cmsis-atmel Atmel Smart ARM devices CMSIS module
framework-mbed mbed Framework
framework-simba Simba Framework
framework-zephyr Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
framework-zephyr-canopennode Zephyr module for CANopenNode - a free and open source CANopen Stack
framework-zephyr-civetweb Zephyr module CivetWeb Embedded C/C++ web server
framework-zephyr-fatfs Zephyr module for FATFS filesystem
framework-zephyr-hal-atmel Atmel SAM HAL for Zephyr framework
framework-zephyr-libmetal Zephyr module for HAL abstraction layer used by open-amp
framework-zephyr-littlefs Zephyr module for littlefs filesystem
framework-zephyr-loramac-node Zephyr module for LoRaWAN endpoint stack implementation
framework-zephyr-lvgl Zephyr module for LittlevGL - an Open-source Embedded GUI Library
framework-zephyr-mbedtls mbedTLS module for Zephyr
framework-zephyr-mcuboot Zephyr module for MCUboot - a secure bootloader for 32-bit MCUs
framework-zephyr-mcumgr Zephyr module for mcumgr management library for 32-bit MCUs
framework-zephyr-mipi-sys-t Zephyr module for MIPI System Software Trace
framework-zephyr-open-amp Zephyr module for Open Asymmetric Multi Processing (OpenAMP) framework
framework-zephyr-openthread OpenThread module for Zephyr
framework-zephyr-segger Zephyr module for Segger RTT
framework-zephyr-tinycbor Zephyr module for Concise Binary Object Representation Library
tool-avrdude AVRDUDE
tool-bossac BOSSA CLI
tool-cmake CMake is an open-source, cross-platform family of tools designed to build, test and package software.
tool-dtc Device tree compiler
tool-gperf GNU gperf is a perfect hash function generator.
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-mbctool MBC-WB Uploader Application
tool-ninja Ninja is a small build system with a focus on speed.
tool-openocd OpenOCD
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Adafruit Circuit Playground Express External SAMD21G18A 48MHz 256KB 32KB
Adafruit Crickit M0 External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 Express External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M4 Express External SAMD51J19A 120MHz 512KB 192KB
Adafruit Gemma M0 External SAMD21E18A 48MHz 256KB 32KB
Adafruit Grand Central M4 External SAMD51P20A 120MHz 1MB 256KB
Adafruit Hallowing M0 External SAMD21G18A 48MHz 256KB 32KB
Adafruit Hallowing M4 External SAMD51J19A 120MHz 496KB 192KB
Adafruit ItsyBitsy M0 External SAMD21G18A 48MHz 256KB 32KB
Adafruit ItsyBitsy M4 External SAMD51G19A 120MHz 512KB 192KB
Adafruit MONSTER M4SK External SAMD51G19A 120MHz 496KB 192KB
Adafruit Metro M0 Expresss External SAMD21G18A 48MHz 256KB 32KB
Adafruit Metro M4 External SAMD51J19A 120MHz 512KB 192KB
Adafruit Metro M4 AirLift Lite External SAMD51J19A 120MHz 512KB 192KB
Adafruit PyGamer Advance M4 External SAMD51J20A 120MHz 1MB 256KB
Adafruit PyGamer M4 Express External SAMD51J19A 120MHz 512KB 192KB
Adafruit PyPortal M4 External SAMD51J20A 120MHz 1MB 256KB
Adafruit PyPortal M4 Titano External SAMD51J20A 120MHz 1MB 256KB
Adafruit Trellis M4 External SAMD51J19A 120MHz 512KB 192KB
Adafruit Trinket M0 External SAMD21E18A 48MHz 256KB 32KB
Adafruit pIRkey External SAMD21E18A 48MHz 256KB 32KB
Adafruit pyBadge AirLift M4 External SAMD51J20A 120MHz 1008KB 192KB
Adafruit pyBadge M4 Express External SAMD51J19A 120MHz 512KB 192KB

Name Debug MCU Frequency Flash RAM
Arduino Due (Programming Port) External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) External AT91SAM3X8E 84MHz 512KB 96KB
Arduino M0 External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Native USB Port) External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Programming/Debug Port) On-board SAMD21G18A 48MHz 256KB 32KB
Arduino MKR FOX 1200 External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR GSM 1400 External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR NB 1500 External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1300 External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1310 External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WiFi 1010 External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR1000 External SAMD21G18A 48MHz 256KB 32KB
Arduino MKRZERO External SAMD21G18A 48MHz 256KB 32KB
Arduino Tian External SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (Programming/Debug Port) On-board SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (USB Native Port) External SAMD21G18A 48MHz 256KB 32KB
MKR Vidor 4000 External SAMD21G18A 48MHz 256KB 32KB
NANO 33 IoT External SAMD21G18A 48MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
Atmel ATSAMR21-XPRO On-board SAMR21G18A 48MHz 256KB 32KB
Atmel ATSAMW25-XPRO On-board SAMD21G18A 48MHz 256KB 32KB
Atmel SAMC21-XPRO On-board SAMC21J18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO On-board SAMD21J18A 48MHz 256KB 32KB
Atmel SAML21-XPRO-B On-board SAML21J18B 48MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
Digistump DigiX External AT91SAM3X8E 84MHz 512KB 96KB

Name Debug MCU Frequency Flash RAM
Tuino 096 External SAMD21G18A 48MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
LowPowerLab CurrentRanger No SAMD21G18A 48MHz 256KB 32KB
Moteino M0 External SAMD21G18A 48MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
Minitronics v2.0 External SAMD21J18A 48MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
SODAQ Autonomo External SAMD21J18A 48MHz 256KB 32KB
SODAQ ExpLoRer External SAMD21J18A 48MHz 256KB 32KB
SODAQ ONE External SAMD21G18A 48MHz 256KB 32KB
SODAQ SARA External SAMD21J18A 48MHz 256KB 32KB
SODAQ SFF External SAMD21G18A 48MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
SainSmart Due (Programming Port) External AT91SAM3X8E 84MHz 512KB 96KB
SainSmart Due (USB Native Port) External AT91SAM3X8E 84MHz 512KB 96KB

Name Debug MCU Frequency Flash RAM
Seeeduino LoRaWAN External SAMD21G18A 48MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
SparkFun 9DoF Razor IMU M0 External SAMD21G18A 48MHz 256KB 32KB
SparkFun Qwiic Micro External SAMD21E18A 48MHz 256KB 32KB
SparkFun RedBoard Turbo External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Dev Breakout External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Mini Breakout External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Pro RF External SAMD21G18A 48MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
Briki ABC (MBC-WB) - Samd21 External SAMD21G18A 48MHz 256KB 32KB
Briki MBC-WB - Samd21 External SAMD21G18A 48MHz 256KB 32KB

Espressif 32

platform = espressif32

Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

For more detailed information please visit vendor site.

  • Tutorials
  • Configuration
  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

  • Get started with Arduino and ESP32-DevKitC: debugging and unit testing
  • Get started with ESP-IDF and ESP32-DevKitC: debugging, unit testing, project analysis
  • Video: Free Inline Debugging for ESP32 and Arduino Sketches

  • CPU Frequency
  • FLASH Frequency
  • FLASH Mode
  • External RAM (PSRAM)
  • Debug Level
  • Upload Speed
  • Erase Flash
  • Partition Tables
  • Embedding Binary Data
  • Uploading files to file system SPIFFS
  • Over-the-Air (OTA) update
  • Using JFrog Bintray (free and secure Cloud solution)
  • Using built-in Local solution
•
Authentication and upload options


  • Using Arduino Framework with Staging version
  • Arduino Core Wiki

CPU Frequency

See board_build.f_cpu option from "platformio.ini" (Project Configuration File)

[env:myenv]
; set frequency to 160MHz
board_build.f_cpu = 160000000L


FLASH Frequency

Please use board_build.f_flash option from "platformio.ini" (Project Configuration File) to change a value. Possible values:

  • 40000000L (default)
  • 80000000L

[env:myenv]
; set frequency to 80MHz
board_build.f_flash = 80000000L


FLASH Mode

Flash chip interface mode. This parameter is stored in the binary image header, along with the flash size and flash frequency. The ROM bootloader in the ESP chip uses the value of these parameters in order to know how to talk to the flash chip.

Please use board_build.flash_mode option from "platformio.ini" (Project Configuration File) to change a value. Possible values:

  • qio
  • qout
  • dio
  • dout

[env:myenv]
board_build.flash_mode = qio


You can enable external RAM using the next extra build_flags in "platformio.ini" (Project Configuration File) depending on a framework type.

Framework Arduino:

[env:myenv]
platform = espressif32
framework = arduino
board = ...
build_flags =
    -DBOARD_HAS_PSRAM
    -mfix-esp32-psram-cache-issue


Framework ESP-IDF:

[env:myenv]
platform = espressif32
framework = espidf
board = ...
build_flags =
    -DCONFIG_SPIRAM_CACHE_WORKAROUND


More details are located in the official ESP-IDF documentation - Support for external RAM.

Debug Level

Please use one of the next build_flags to change debug level. A build_flags option could be used only the one time per build environment. If you need to specify more flags, please separate them with a new line or space.

Actual information is available in Arduino for ESP32 Board Manifest. Please scroll to esp32.menu.DebugLevel section.

[env:myenv]
platform = ...
board = ...
framework = arduino
;;;;; Possible options ;;;;;;
; None
build_flags = -DCORE_DEBUG_LEVEL=0
; Error
build_flags = -DCORE_DEBUG_LEVEL=1
; Warn
build_flags = -DCORE_DEBUG_LEVEL=2
; Info
build_flags = -DCORE_DEBUG_LEVEL=3
; Debug
build_flags = -DCORE_DEBUG_LEVEL=4
; Verbose
build_flags = -DCORE_DEBUG_LEVEL=5


Upload Speed

You can set custom upload speed using upload_speed option from "platformio.ini" (Project Configuration File)

[env:myenv]
upload_speed = 9600


Please platformio run --target the next command to erase the entire flash chip (all data replaced with 0xFF bytes):

> platformio run --target erase
# or short version
> pio run -t erase


You can create a custom partitions table (CSV) following ESP32 Partition Tables documentation. PlatformIO uses default partition tables depending on a framework type:

  • default.csv for Arduino (show pre-configured partition tables)
  • partitions_singleapp.csv for ESP-IDF (show pre-configured partition tables)

To override default table please use board_build.partitions option in "platformio.ini" (Project Configuration File).

WARNING:

SPIFFS partition MUST have configured "Type" as "data" and "SubType" as "spiffs". For example, spiffs, data, spiffs, 0x291000, 1M,


Examples:

; 1) A "partitions_custom.csv" in the root of project directory
[env:custom_table]
board_build.partitions = partitions_custom.csv
; 2) Switch between built-in tables
; https://github.com/espressif/arduino-esp32/tree/master/tools/partitions
; https://github.com/espressif/esp-idf/tree/master/components/partition_table
[env:custom_builtin_table]
board_build.partitions = no_ota.csv


Sometimes you have a file with some binary or text data that you’d like to make available to your program - but you don’t want to reformat the file as C source.

There are two options board_build.embed_txtfiles and board_build.embed_files which can be used for embedding data. The only difference is that files specified in board_build.embed_txtfiles option are null-terminated in the final binary.

[env:myenv]
platform = espressif32
board = ...
board_build.embed_txtfiles =
  src/private.pem.key
  src/certificate.pem.crt
  src/aws-root-ca.pem


The file contents will be added to the .rodata section in flash, and are available via symbol names as follows:

extern const uint8_t aws_root_ca_pem_start[] asm("_binary_src_aws_root_ca_pem_start");
extern const uint8_t aws_root_ca_pem_end[] asm("_binary_src_aws_root_ca_pem_end");
extern const uint8_t certificate_pem_crt_start[] asm("_binary_src_certificate_pem_crt_start");
extern const uint8_t certificate_pem_crt_end[] asm("_binary_src_certificate_pem_crt_end");
extern const uint8_t private_pem_key_start[] asm("_binary_src_private_pem_key_start");
extern const uint8_t private_pem_key_end[] asm("_binary_src_private_pem_key_end");


The names are generated from the full name of the file. Characters /, ., etc. are replaced with underscores. The _binary + _nested_folder prefix in the symbol name is added by "objcopy" and is the same for both text and binary files.

NOTE:

With the ESP-IDF framework symbol names should not contain path to the files, for example _binary_private_pem_key_start instead of _binary_src_private_pem_key_start.


See full example with embedding Amazon AWS certificates:

•
https://github.com/platformio/platform-espressif32/tree/develop/examples/espidf-aws-iot

Uploading files to file system SPIFFS

1.
Create new project using PlatformIO IDE or initialize project using PlatformIO Core (CLI) and platformio project init (if you have not initialized it yet)
2.
Create data folder (it should be on the same level as src folder) and put files here. Also, you can specify own location for data_dir
3.
Run "Upload File System image" task in PlatformIO IDE or use PlatformIO Core (CLI) and platformio run --target command with uploadfs target.

To upload SPIFFS image using OTA update please specify upload_port / --upload-port as IP address or mDNS host name (ending with the *.local).

Examples:

  • SPIFFS for Arduino
  • SPIFFS for ESP-IDF

Over-the-Air (OTA) update

  • Video and presentation - swampUP: Over-The-Air (OTA) firmware upgrades for Internet of Things devices with PlatformIO and JFrog Bintray
  • Demo source code: https://github.com/platformio/bintray-secure-ota

Demo code for:

  • Arduino
  • ESP-IDF

There are 2 options:

•
Directly specify platformio run --upload-port in command line

platformio run --target upload --upload-port IP_ADDRESS_HERE or mDNS_NAME.local


•
Specify upload_port option in "platformio.ini" (Project Configuration File)

You also need to set upload_protocol to espota.

[env:myenv]
upload_protocol = espota
upload_port = IP_ADDRESS_HERE or mDNS_NAME.local


For example,

  • platformio run -t upload --upload-port 192.168.0.255
  • platformio run -t upload --upload-port myesp8266.local

Authentication and upload options

You can pass additional options/flags to OTA uploader using upload_flags option in "platformio.ini" (Project Configuration File)

[env:myenv]
upload_protocol = espota
; each flag in a new line
upload_flags =
    --port=3232


Available flags

  • --port=ESP_PORT ESP32 OTA Port. Default 8266
  • --auth=AUTH Set authentication password
  • --spiffs Use this option to transmit a SPIFFS image and do not flash the module

For the full list with available options please run

~/.platformio/packages/framework-arduinoespressif32/tools/espota.py --help
Usage: espota.py [options]
Transmit image over the air to the esp32 module with OTA support.
Options:
  -h, --help            show this help message and exit
  Destination:
    -i ESP_IP, --ip=ESP_IP
                        ESP32 IP Address.
    -I HOST_IP, --host_ip=HOST_IP
                        Host IP Address.
    -p ESP_PORT, --port=ESP_PORT
                        ESP32 ota Port. Default 3232
    -P HOST_PORT, --host_port=HOST_PORT
                        Host server ota Port. Default random 10000-60000
  Authentication:
    -a AUTH, --auth=AUTH
                        Set authentication password.
  Image:
    -f FILE, --file=FILE
                        Image file.
    -s, --spiffs        Use this option to transmit a SPIFFS image and do not
                        flash the module.
  Output:
    -d, --debug         Show debug output. And override loglevel with debug.
    -r, --progress      Show progress output. Does not work for ArduinoIDE
    -t TIMEOUT, --timeout=TIMEOUT
                        Timeout to wait for the ESP32 to accept invitation


WARNING:

For windows users. To manage OTA check the ESP wifi network profile isn't checked on public be sure it's on private mode``


PlatformIO will install the latest Arduino Core for ESP32 from https://github.com/espressif/arduino-esp32. The Git should be installed in a system. To update Arduino Core to the latest revision, please open PlatformIO IDE and navigate to PIO Home > Platforms > Updates.

1.
Please install PlatformIO IDE
2.
Initialize a new project, open "platformio.ini" (Project Configuration File) and specify the link to the framework repository in platform_packages section. For example,

[env:esp32dev]
platform = espressif32
board = esp32dev
framework = arduino
platform_packages =
    framework-arduinoespressif32 @ https://github.com/espressif/arduino-esp32.git


3.
Try to build the project
4.
If you see build errors, then try to build this project using the same stage with Arduino IDE
5.
If it works with Arduino IDE but doesn't work with PlatformIO, then please file a new issue with attached information:
  • test project/files
  • detailed log of build process from Arduino IDE (please copy it from console to https://hastebin.com)
  • detailed log of build process from PlatformIO Build System (please copy it from console to https://hastebin.com)


Tips, tricks and common problems: http://desire.giesecke.tk/index.php/2018/01/30/esp32-wiki-entries/

Examples are listed from Espressif 32 development platform repository:

  • espidf-storage-sdcard
  • espidf-blink
  • espidf-coap-server
  • espidf-exceptions
  • arduino-blink
  • simba-blink
  • espidf-ble-eddystone
  • espidf-ulp-adc
  • espidf-ulp-pulse
  • espidf-arduino-wifiscan
  • espidf-http-request
  • espidf-arduino-blink
  • pumbaa-blink
  • espidf-hello-world
  • espidf-aws-iot
  • arduino-briki-internal-libs
  • espidf-peripherals-uart
  • arduino-wifiscan

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

  • Pinout Diagram
  • Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


JTAG Wiring Connections

[image]
Board Pin JTAG Tool Pin
IO13 TCK
IO12 TDI
IO15 TDO
IO14 TMS
EN RST
GND GND

Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
Espressif ESP-WROVER-KIT ESP32 240MHz 4MB 320KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
AI Thinker ESP32-CAM ESP32 240MHz 4MB 320KB
ALKS ESP32 ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 ESP32 240MHz 16MB 520KB
Adafruit ESP32 Feather ESP32 240MHz 4MB 320KB
Briki ABC (MBC-WB) - ESP32 ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - ESP32 ESP32 240MHz 3.25MB 320KB
D-duino-32 ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 ESP32 240MHz 4MB 320KB
Dongsen Tech Pocket 32 ESP32 240MHz 4MB 320KB
ESP32 FM DevKit ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno ESP32 240MHz 4MB 320KB
ESPectro32 ESP32 240MHz 4MB 320KB
ESPino32 ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module ESP32 240MHz 4MB 320KB
FireBeetle-ESP32 ESP32 240MHz 4MB 320KB
Frog Board ESP32 ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) ESP32 240MHz 8MB 320KB
Heltec Wireless Stick ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima ESP32 240MHz 4MB 320KB
IoTaaP Magnolia ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32DevKIT ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit ESP32 240MHz 4MB 320KB
Node32s ESP32 240MHz 4MB 320KB
NodeMCU-32S ESP32 240MHz 4MB 320KB
OLIMEX ESP32-DevKit-LiPo ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY ESP32 240MHz 4MB 320KB
Pycom LoPy ESP32 240MHz 4MB 320KB
Pycom LoPy4 ESP32 240MHz 4MB 1.25MB
SG-O AirMon ESP32 240MHz 4MB 320KB
Silicognition wESP32 ESP32 240MHz 4MB 320KB
SparkFun ESP32 Thing ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V1 ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 ESP32 240MHz 4MB 320KB
TTGO T-Beam ESP32 240MHz 4MB 1.25MB
TTGO T1 ESP32 240MHz 4MB 320KB
VintLabs ESP32 Devkit ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery ESP32 240MHz 4MB 320KB
XinaBox CW02 ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Io ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus ESP32 240MHz 4MB 320KB

Stable and upstream versions

You can switch between stable releases of Espressif 32 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = espressif32
board = ...
; Custom stable version
[env:custom_stable]
platform = espressif32@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-espressif32.git
board = ...


Name Description
framework-arduino-mbcwb Fork of Arduino framework for briki MBC-WB boards
framework-arduinoespressif32 Arduino Wiring-based Framework (ESP32 Core)
framework-espidf Espressif IoT Development Framework
framework-pumbaa Pumbaa Framework
framework-simba Simba Framework
tool-cmake CMake is an open-source, cross-platform family of tools designed to build, test and package software.
tool-esptoolpy ESP8266 and ESP32 serial bootloader utility
tool-idf Python idf.py binary
tool-mbctool MBC-WB Uploader Application
tool-mconf Kconfig frontends and parser
tool-mkspiffs Tool to build and unpack SPIFFS images
tool-ninja Ninja is a small build system with a focus on speed.
tool-openocd-esp32 OpenOCD for Espressif 32
toolchain-esp32ulp Binutils fork with support for the ESP32 ULP co-processor
toolchain-xtensa32 xtensa32-gcc

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Pumbaa Pumbaa is Python on top of Simba. The implementation is a port of MicroPython, designed for embedded devices with limited amount of RAM and code memory.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



AI Thinker

Name Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
AZ-Delivery ESP-32 Dev Kit C V4 External ESP32 240MHz 16MB 520KB

Name Debug MCU Frequency Flash RAM
Adafruit ESP32 Feather External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
Node32s External ESP32 240MHz 4MB 320KB

April Brother

Name Debug MCU Frequency Flash RAM
April Brother ESPea32 No ESP32 240MHz 4MB 320KB

BPI Tech

Name Debug MCU Frequency Flash RAM
BPI-Bit No ESP32 160MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
FireBeetle-ESP32 External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
DOIT ESP32 DEVKIT V1 External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
D-duino-32 External ESP32 240MHz 4MB 320KB

Dongsen Technology

Name Debug MCU Frequency Flash RAM
Dongsen Tech Pocket 32 External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
ESPectro32 External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
ESP32vn IoT Uno External ESP32 240MHz 4MB 320KB

Electronic SweetPeas

Name Debug MCU Frequency Flash RAM
Electronic SweetPeas ESP320 No ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
ESP32 Pico Kit No ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
Frog Board ESP32 External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
ODROID-GO No ESP32 240MHz 16MB 320KB

Heltec Automation

Name Debug MCU Frequency Flash RAM
Heltec WiFi Kit 32 No ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick External ESP32 240MHz 8MB 320KB

Name Debug MCU Frequency Flash RAM
Hornbill ESP32 Dev External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
IntoRobot Fig No ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
IoTaaP Magnolia External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
M5Stack Core ESP32 No ESP32 240MHz 4MB 320KB
M5Stack FIRE No ESP32 240MHz 16MB 6.25MB
M5Stack GREY ESP32 No ESP32 240MHz 16MB 520KB
M5Stick-C No ESP32 240MHz 4MB 320KB

MH-ET Live

Name Debug MCU Frequency Flash RAM
MH ET LIVE ESP32DevKIT External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
MagicBit No ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
MakerAsia Nano32 No ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
Microduino Core ESP32 No ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
NodeMCU-32S External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
Noduino Quantum No ESP32 240MHz 16MB 320KB

Name Debug MCU Frequency Flash RAM
OLIMEX ESP32-DevKit-LiPo External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-PRO No ESP32 240MHz 4MB 320KB
OLIMEX ESP32-PoE No ESP32 240MHz 4MB 320KB
OLIMEX ESP32-PoE-ISO No ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
OROCA EduBot No ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
Onehorse ESP32 Dev Module No ESP32 240MHz 4MB 320KB

Pycom Ltd.

Name Debug MCU Frequency Flash RAM
Pycom GPy No ESP32 240MHz 4MB 320KB
Pycom LoPy External ESP32 240MHz 4MB 320KB
Pycom LoPy4 External ESP32 240MHz 4MB 1.25MB

Qmobot LLP

Name Debug MCU Frequency Flash RAM
Qchip No ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
ALKS ESP32 External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
SG-O AirMon External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
Silicognition wESP32 External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
SparkFun LoRa Gateway 1-Channel External ESP32 240MHz 4MB 320KB

SparkFun Electronics

Name Debug MCU Frequency Flash RAM
SparkFun ESP32 Thing External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
TTGO LoRa32-OLED V1 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 External ESP32 240MHz 4MB 320KB
TTGO T-Beam External ESP32 240MHz 4MB 1.25MB
TTGO T-Watch No ESP32 240MHz 16MB 320KB
TTGO T1 External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
ESPino32 External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
TinyPICO No ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
Turta IoT Node No ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
ESP32 FM DevKit External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
VintLabs ESP32 Devkit External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
WEMOS LOLIN D32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
Widora AIR No ESP32 240MHz 16MB 320KB

Name Debug MCU Frequency Flash RAM
XinaBox CW02 External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
Briki ABC (MBC-WB) - ESP32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - ESP32 External ESP32 240MHz 3.25MB 320KB

Name Debug MCU Frequency Flash RAM
oddWires IoT-Bus Io External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus External ESP32 240MHz 4MB 320KB

Name Debug MCU Frequency Flash RAM
u-blox NINA-W10 series No ESP32 240MHz 2MB 320KB

Espressif 8266

platform = espressif8266

Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

For more detailed information please visit vendor site.

  • Configuration
  • Examples
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

  • CPU Frequency
  • FLASH Frequency
  • FLASH Mode
  • Reset Method
  • Flash Size
  • Upload Speed
  • lwIP Variant
  • SDK Version
  • SSL Support
  • Serial Debug
  • Debug Level
  • VTables
  • Exceptions
  • Uploading files to file system SPIFFS
  • Over-the-Air (OTA) update
•
Authentication and upload options

  • Demo
  • Using Arduino Framework with Staging version

CPU Frequency

See board_build.f_cpu option from "platformio.ini" (Project Configuration File)

[env:myenv]
; set frequency to 160MHz
board_build.f_cpu = 160000000L


FLASH Frequency

Please use board_build.f_flash option from "platformio.ini" (Project Configuration File) to change a value. Possible values:

  • 20000000L
  • 26000000L
  • 40000000L (default)
  • 80000000L

[env:myenv]
; set frequency to 80MHz
board_build.f_flash = 80000000L


FLASH Mode

Flash chip interface mode. This parameter is stored in the binary image header, along with the flash size and flash frequency. The ROM bootloader in the ESP chip uses the value of these parameters in order to know how to talk to the flash chip.

Please use board_build.flash_mode option from "platformio.ini" (Project Configuration File) to change a value. Possible values:

  • qio
  • qout
  • dio
  • dout

[env:myenv]
board_build.flash_mode = qio


You can set custom reset method using upload_resetmethod option from "platformio.ini" (Project Configuration File).

The possible values are:

  • ck - RTS controls RESET or CH_PD, DTR controls GPIO0
  • wifio - TXD controls GPIO0 via PNP transistor and DTR controls RESET via a capacitor
  • nodemcu - GPIO0 and RESET controlled using two NPN transistors as in NodeMCU devkit.

See default reset methods per board.

[env:myenv]
upload_resetmethod = ck


WARNING:

Please make sure to read ESP8266 Flash layout information first.


Available LD-scripts: https://github.com/esp8266/Arduino/tree/master/tools/sdk/ld

Please open eagle.flash.***.ld file to check how flash is split.

To override default LD script please use board_build.ldscript option from "platformio.ini" (Project Configuration File).

[env:myenv]
board_build.ldscript = eagle.flash.4m.ld


Upload Speed

You can set custom upload speed using upload_speed option from "platformio.ini" (Project Configuration File)

[env:myenv]
upload_speed = 9600


Available variants (macros):

  • -D PIO_FRAMEWORK_ARDUINO_LWIP2_LOW_MEMORY v2 Lower Memory (default)
  • -D PIO_FRAMEWORK_ARDUINO_LWIP2_HIGHER_BANDWIDTH v2 Higher Bandwidth
  • -D PIO_FRAMEWORK_ARDUINO_LWIP2_LOW_MEMORY_LOW_FLASH v2 Lower Memory (no features)
  • -D PIO_FRAMEWORK_ARDUINO_LWIP2_HIGHER_BANDWIDTH_LOW_FLASH v2 Higher Bandwidth (no features)
  • -D PIO_FRAMEWORK_ARDUINO_LWIP2_IPV6_LOW_MEMORY v2 IPv6 Lower Memory
  • -D PIO_FRAMEWORK_ARDUINO_LWIP2_IPV6_HIGHER_BANDWIDTH v2 IPv6 Higher Bandwidth
  • -D PIO_FRAMEWORK_ARDUINO_LWIP_HIGHER_BANDWIDTH v1.4 Higher Bandwidth

You can change lwIP Variant by passing a custom macro using project build_flags.

For example, to switch to lwIP v1.4

[env:myenv]
...
build_flags = -D PIO_FRAMEWORK_ARDUINO_LWIP_HIGHER_BANDWIDTH


Available versions (macros):

  • -D PIO_FRAMEWORK_ARDUINO_ESPRESSIF_SDK3 NonOS SDK-pre-3.0 as of Jun 26, 2018
  • -D PIO_FRAMEWORK_ARDUINO_ESPRESSIF_SDK221 NonOS SDK v2.2.1 (legacy) as of Jun 8, 2018
  • -D PIO_FRAMEWORK_ARDUINO_ESPRESSIF_SDK22x_190313 NonOS SDK v2.2.x branch as of Mar 13, 2019
  • -D PIO_FRAMEWORK_ARDUINO_ESPRESSIF_SDK22x_190703 NonOS SDK v2.2.x branch as of Jul 03, 2019 (default)
  • -D PIO_FRAMEWORK_ARDUINO_ESPRESSIF_SDK22x_191024 NonOS SDK v2.2.x branch as of Oct 24, 2019
  • -D PIO_FRAMEWORK_ARDUINO_ESPRESSIF_SDK22x_191105 NonOS SDK v2.2.x branch as of to Nov 05, 2019
  • -D PIO_FRAMEWORK_ARDUINO_ESPRESSIF_SDK22x_191122 NonOS SDK v2.2.x branch as of to Nov 22, 2019

You can change SDK version by passing a custom macro using project build_flags.

For example, to switch to SDK-pre-3.0:

[env:myenv]
...
build_flags = -D PIO_FRAMEWORK_ARDUINO_ESPRESSIF_SDK3


By default, all SSL ciphers (most compatible) are supported.

You can control SSL support passing a custom macro using project build_flags.

For example, use basic SSL ciphers (lower ROM use):

[env:myenv]
...
build_flags = -D BEARSSL_SSL_BASIC


Please use the next build_flags to enable Serial debug:

[env:myenv]
...
build_flags = -DDEBUG_ESP_PORT=Serial
; or for Serial1
build_flags = -DDEBUG_ESP_PORT=Serial1


Debug Level

Please use one of the next build_flags to change debug level. A build_flags option could be used only the one time per build environment. If you need to specify more flags, please separate them with a new line or space.

Also, please note that you will need to extend build_flags with Serial Debug macro. For example, build_flags = -DDEBUG_ESP_PORT=Serial -DDEBUG_ESP_SSL ....

Actual information is available in Arduino for ESP8266 Board Manifest. Please scroll to generic.menu.lvl section.

[env:myenv]
platform = ...
board = ...
framework = arduino
;;;;; Possible options ;;;;;;
; SSL
build_flags = -DDEBUG_ESP_SSL
; TLS_MEM
build_flags = -DDEBUG_ESP_TLS_MEM
; HTTP_CLIENT
build_flags = -DDEBUG_ESP_HTTP_CLIENT
; HTTP_SERVER
build_flags = -DDEBUG_ESP_HTTP_SERVER
; SSL+TLS_MEM
build_flags =
  -DDEBUG_ESP_SSL
  -DDEBUG_ESP_TLS_MEM
; SSL+HTTP_CLIENT
build_flags =
  -DDEBUG_ESP_SSL
  -DDEBUG_ESP_HTTP_CLIENT
; SSL+HTTP_SERVER
build_flags =
  -DDEBUG_ESP_SSL
  -DDEBUG_ESP_HTTP_SERVER
; TLS_MEM+HTTP_CLIENT
build_flags =
  -DDEBUG_ESP_TLS_MEM
  -DDEBUG_ESP_HTTP_CLIENT
; TLS_MEM+HTTP_SERVER
build_flags =
  -DDEBUG_ESP_TLS_MEM
  -DDEBUG_ESP_HTTP_SERVER
; HTTP_CLIENT+HTTP_SERVER
build_flags =
  -DDEBUG_ESP_HTTP_CLIENT
  -DDEBUG_ESP_HTTP_SERVER
; SSL+TLS_MEM+HTTP_CLIENT
build_flags =
  -DDEBUG_ESP_SSL
  -DDEBUG_ESP_TLS_MEM
  -DDEBUG_ESP_HTTP_CLIENT
; SSL+TLS_MEM+HTTP_SERVER
build_flags =
  -DDEBUG_ESP_SSL
  -DDEBUG_ESP_TLS_MEM
  -DDEBUG_ESP_HTTP_SERVER
; SSL+HTTP_CLIENT+HTTP_SERVER
build_flags =
  -DDEBUG_ESP_SSL
  -DDEBUG_ESP_HTTP_CLIENT
  -DDEBUG_ESP_HTTP_SERVER
; TLS_MEM+HTTP_CLIENT+HTTP_SERVER
build_flags =
  -DDEBUG_ESP_TLS_MEM
  -DDEBUG_ESP_HTTP_CLIENT
  -DDEBUG_ESP_HTTP_SERVER
; SSL+TLS_MEM+HTTP_CLIENT+HTTP_SERVER
build_flags =
  -DDEBUG_ESP_SSL
  -DDEBUG_ESP_TLS_MEM
  -DDEBUG_ESP_HTTP_CLIENT
  -DDEBUG_ESP_HTTP_SERVER
; CORE
build_flags = -DDEBUG_ESP_CORE
; WIFI
build_flags = -DDEBUG_ESP_WIFI
; HTTP_UPDATE
build_flags = -DDEBUG_ESP_HTTP_UPDATE
; UPDATER
build_flags = -DDEBUG_ESP_UPDATER
; OTA
build_flags = -DDEBUG_ESP_OTA
; OOM
build_flags =
  -DDEBUG_ESP_OOM
  -include "umm_malloc/umm_malloc_cfg.h"
; CORE+WIFI+HTTP_UPDATE+UPDATER+OTA+OOM
build_flags =
  -DDEBUG_ESP_CORE
  -DDEBUG_ESP_WIFI
  -DDEBUG_ESP_HTTP_UPDATE
  -DDEBUG_ESP_UPDATER
  -DDEBUG_ESP_OTA
  -DDEBUG_ESP_OOM -include "umm_malloc/umm_malloc_cfg.h"
; SSL+TLS_MEM+HTTP_CLIENT+HTTP_SERVER+CORE+WIFI+HTTP_UPDATE+UPDATER+OTA+OOM
build_flags =
  -DDEBUG_ESP_SSL
  -DDEBUG_ESP_TLS_MEM
  -DDEBUG_ESP_HTTP_CLIENT
  -DDEBUG_ESP_HTTP_SERVER
  -DDEBUG_ESP_CORE
  -DDEBUG_ESP_WIFI
  -DDEBUG_ESP_HTTP_UPDATE
  -DDEBUG_ESP_UPDATER
  -DDEBUG_ESP_OTA
  -DDEBUG_ESP_OOM -include "umm_malloc/umm_malloc_cfg.h"
; NoAssert-NDEBUG
build_flags = -DNDEBUG


Please use one of the next build_flags:

[env:myenv]
...
; Flash (default)
build_flags = -DVTABLES_IN_FLASH
; Heap
build_flags = -DVTABLES_IN_DRAM
; IRAM
build_flags = -DVTABLES_IN_IRAM


Exceptions are disabled by default. To enable exceptions, use the following build_flags and build_unflags:

[env:myenv]
...
; Remove default exceptions disabled flag
build_unflags = -fno-exceptions
; Enable exceptions
build_flags = -fexceptions


Uploading files to file system SPIFFS

WARNING:

Please make sure to read ESP8266 Flash layout information first.


1.
Create new project using PlatformIO IDE or initialize project using PlatformIO Core (CLI) and platformio project init (if you have not initialized it yet)
2.
Create data folder (it should be on the same level as src folder) and put files here. Also, you can specify own location for data_dir
3.
Run "Upload File System image" task in PlatformIO IDE or use PlatformIO Core (CLI) and platformio run --target command with uploadfs target.

To upload SPIFFS image using OTA update please specify upload_port / --upload-port as IP address or mDNS host name (ending with the *.local). For the details please follow to Over-the-Air (OTA) update.

By default, will be used default LD Script for the board where is specified SPIFFS offsets (start, end, page, block). You can override it using Flash Size.

Active discussion is located in issue #382.

Over-the-Air (OTA) update

Firstly, please read What is OTA? How to use it?

There are 2 options:

•
Directly specify platformio run --upload-port in command line

platformio run --target upload --upload-port IP_ADDRESS_HERE or mDNS_NAME.local


•
Specify upload_port option in "platformio.ini" (Project Configuration File)

You also need to set upload_protocol to espota.

[env:myenv]
upload_protocol = espota
upload_port = IP_ADDRESS_HERE or mDNS_NAME.local


For example,

  • platformio run -t upload --upload-port 192.168.0.255
  • platformio run -t upload --upload-port myesp8266.local

Authentication and upload options

You can pass additional options/flags to OTA uploader using upload_flags option in "platformio.ini" (Project Configuration File)

[env:myenv]
upload_protocol = espota
; each flag in a new line
upload_flags =
  --port=8266


Available flags

  • --port=ESP_PORT ESP8266 OTA Port. Default 8266
  • --auth=AUTH Set authentication password
  • --spiffs Use this option to transmit a SPIFFS image and do not flash the module

For the full list with available options please run

~/.platformio/packages/framework-arduinoespressif8266/tools/espota.py --help
Usage: espota.py [options]
Transmit image over the air to the esp8266 module with OTA support.
Options:
  -h, --help            show this help message and exit
  Destination:
    -i ESP_IP, --ip=ESP_IP
                        ESP8266 IP Address.
    -I HOST_IP, --host_ip=HOST_IP
                        Host IP Address.
    -p ESP_PORT, --port=ESP_PORT
                        ESP8266 ota Port. Default 8266
    -P HOST_PORT, --host_port=HOST_PORT
                        Host server ota Port. Default random 10000-60000
  Authentication:
    -a AUTH, --auth=AUTH
                        Set authentication password.
  Image:
    -f FILE, --file=FILE
                        Image file.
    -s, --spiffs        Use this option to transmit a SPIFFS image and do not
                        flash the module.
  Output:
    -d, --debug         Show debug output. And override loglevel with debug.
    -r, --progress      Show progress output. Does not work for ArduinoIDE


.SS Using Arduino Framework with Staging version

PlatformIO will install the latest Arduino Core for ESP8266 from https://github.com/esp8266/Arduino. The Git should be installed in a system. To update Arduino Core to the latest revision, please open PlatformIO IDE and navigate to PIO Home > Platforms > Updates.

1.
Please install PlatformIO IDE
2.
Initialize a new project, open "platformio.ini" (Project Configuration File) and specify the link to the framework repository in platform_packages section. For example,

[env:nodemcuv2]
platform = espressif8266
board = nodemcuv2
framework = arduino
platform_packages =
    framework-arduinoespressif8266 @ https://github.com/esp8266/Arduino.git


3.
Try to build the project
4.
If you see build errors, then try to build this project using the same stage with Arduino IDE
5.
If it works with Arduino IDE but doesn't work with PlatformIO, then please file a new issue with attached information:
  • test project/files
  • detailed log of build process from Arduino IDE (please copy it from console to https://hastebin.com)
  • detailed log of build process from PlatformIO Build System (please copy it from console to https://hastebin.com)


Examples are listed from Espressif 8266 development platform repository:

  • arduino-webserver
  • arduino-asyncudp
  • arduino-blink
  • simba-blink
  • esp8266-rtos-sdk-blink
  • esp8266-nonos-sdk-blink
  • arduino-wifiscan

Stable and upstream versions

You can switch between stable releases of Espressif 8266 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = espressif8266
board = ...
; Custom stable version
[env:custom_stable]
platform = espressif8266@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-espressif8266.git
board = ...


Name Description
framework-arduinoespressif8266 Arduino Wiring-based Framework (ESP8266 Core)
framework-esp8266-nonos-sdk ESP8266 Non-OS SDK
framework-esp8266-rtos-sdk ESP8266 SDK based on FreeRTOS
framework-simba Simba Framework
tool-esptool esptool-ck
tool-esptoolpy ESP8266 and ESP32 serial bootloader utility
tool-mkspiffs Tool to build and unpack SPIFFS images
toolchain-xtensa xtensa-gcc

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



4D Systems

Name Debug MCU Frequency Flash RAM
4D Systems gen4 IoD Range No ESP8266 80MHz 512KB 80KB

Name Debug MCU Frequency Flash RAM
Adafruit HUZZAH ESP8266 No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
WiFi Slot No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
DigiStump Oak No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
ESP-Mx DevKit (ESP8285) No ESP8266 80MHz 1MB 80KB
ESPDuino (ESP-13 Module) No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
ESPectro Core No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
ESPresso Lite 1.0 No ESP8266 80MHz 4MB 80KB
ESPresso Lite 2.0 No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
ESPino No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
ESP-WROOM-02 No ESP8266 80MHz 2MB 80KB
Espressif ESP8266 ESP-12E No ESP8266 80MHz 4MB 80KB
Espressif Generic ESP8266 ESP-01 1M No ESP8266 80MHz 1MB 80KB
Espressif Generic ESP8266 ESP-01 512k No ESP8266 80MHz 512KB 80KB
Espressif Generic ESP8266 ESP-07 No ESP8266 80MHz 4MB 80KB
Generic ESP8285 Module No ESP8266 80MHz 1MB 80KB
Phoenix 1.0 No ESP8266 80MHz 4MB 80KB
Phoenix 2.0 No ESP8266 80MHz 4MB 80KB
WifInfo No ESP8266 80MHz 1MB 80KB

Name Debug MCU Frequency Flash RAM
Heltec Wifi kit 8 No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
Sonoff Basic No ESP8266 80MHz 1MB 80KB
Sonoff S20 No ESP8266 80MHz 1MB 80KB
Sonoff SV No ESP8266 80MHz 1MB 80KB
Sonoff TH No ESP8266 80MHz 1MB 80KB

Invent One

Name Debug MCU Frequency Flash RAM
Invent One No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
NodeMCU 0.9 (ESP-12 Module) No ESP8266 80MHz 4MB 80KB
NodeMCU 1.0 (ESP-12E Module) No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
Olimex MOD-WIFI-ESP8266(-DEV) No ESP8266 80MHz 2MB 80KB

Name Debug MCU Frequency Flash RAM
Schirmilabs Eduino WiFi No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
Wio Link No ESP8266 80MHz 4MB 80KB
Wio Node No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
SparkFun Blynk Board No ESP8266 80MHz 4MB 80KB
SparkFun ESP8266 Thing No ESP8266 80MHz 512KB 80KB
SparkFun ESP8266 Thing Dev No ESP8266 80MHz 512KB 80KB

Name Debug MCU Frequency Flash RAM
SweetPea ESP-210 No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
ThaiEasyElec ESPino No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
WEMOS D1 R1 No ESP8266 80MHz 4MB 80KB
WeMos D1 R2 and mini No ESP8266 80MHz 4MB 80KB
WeMos D1 mini Lite No ESP8266 80MHz 1MB 80KB
WeMos D1 mini Pro No ESP8266 80MHz 16MB 80KB

Name Debug MCU Frequency Flash RAM
WiFiduino No ESP8266 80MHz 4MB 80KB

Name Debug MCU Frequency Flash RAM
XinaBox CW01 No ESP8266 80MHz 4MB 80KB

Freescale Kinetis

platform = freescalekinetis

Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Freescale Kinetis development platform repository:

  • mbed-blink
  • mbed-serial
  • zephyr-blink
  • zephyr-net-telnet
  • mbed-rtos
  • mbed-events
  • zephyr-sensor-sx9500
  • mbed-rtos-tls-client
  • mbed-rtos-ethernet
  • mbed-dsp

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
Ethernet IoT Starter Kit MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K20D50M MK20DX128VLH5 48MHz 128KB 16KB
Freescale Kinetis FRDM-K22F MK22FN512VLH12 120MHz 512KB 128KB
Freescale Kinetis FRDM-K64F MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K66F MK66FN2M0VMD18 180MHz 2MB 256KB
Freescale Kinetis FRDM-K82F MK82FN256VLL15 150MHz 256KB 256KB
Freescale Kinetis FRDM-KL05Z MKL05Z32VFM4 48MHz 32KB 4KB
Freescale Kinetis FRDM-KL25Z MKL25Z128VLK4 48MHz 128KB 16KB
Freescale Kinetis FRDM-KL27Z MKL27Z64VLH4 48MHz 64KB 16KB
Freescale Kinetis FRDM-KL43Z MKL43Z256VLH4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL46Z MKL46Z256VLL4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KW41Z MKW41Z512VHT4 48MHz 512KB 128KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
Freescale Kinetis FRDM-KL82Z MKL82Z128VLK7 96MHz 128KB 96KB
Freescale Kinetis FRDM-KW24D512 MKW24D512 50MHz 512KB 64KB
Hexiwear MK64FN1M0VDC12 120MHz 1MB 256KB

Stable and upstream versions

You can switch between stable releases of Freescale Kinetis development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = freescalekinetis
board = ...
; Custom stable version
[env:custom_stable]
platform = freescalekinetis@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-freescalekinetis.git
board = ...


Name Description
framework-mbed mbed Framework
framework-zephyr Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
framework-zephyr-canopennode Zephyr module for CANopenNode - a free and open source CANopen Stack
framework-zephyr-civetweb Zephyr module CivetWeb Embedded C/C++ web server
framework-zephyr-fatfs Zephyr module for FATFS filesystem
framework-zephyr-hal-nxp NXP HAL for Zephyr framework
framework-zephyr-libmetal Zephyr module for HAL abstraction layer used by open-amp
framework-zephyr-littlefs Zephyr module for littlefs filesystem
framework-zephyr-loramac-node Zephyr module for LoRaWAN endpoint stack implementation
framework-zephyr-lvgl Zephyr module for LittlevGL - an Open-source Embedded GUI Library
framework-zephyr-mbedtls mbedTLS module for Zephyr
framework-zephyr-mcuboot Zephyr module for MCUboot - a secure bootloader for 32-bit MCUs
framework-zephyr-mcumgr Zephyr module for mcumgr management library for 32-bit MCUs
framework-zephyr-mipi-sys-t Zephyr module for MIPI System Software Trace
framework-zephyr-open-amp Zephyr module for Open Asymmetric Multi Processing (OpenAMP) framework
framework-zephyr-openthread OpenThread module for Zephyr
framework-zephyr-segger Zephyr module for Segger RTT
framework-zephyr-tinycbor Zephyr module for Concise Binary Object Representation Library
tool-cmake CMake is an open-source, cross-platform family of tools designed to build, test and package software.
tool-dtc Device tree compiler
tool-gperf GNU gperf is a perfect hash function generator.
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-ninja Ninja is a small build system with a focus on speed.
tool-pyocd Open source python library for programming and debugging ARM Cortex-M microcontrollers using CMSIS-DAP
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Ethernet IoT Starter Kit On-board MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K20D50M On-board MK20DX128VLH5 48MHz 128KB 16KB
Freescale Kinetis FRDM-K22F On-board MK22FN512VLH12 120MHz 512KB 128KB
Freescale Kinetis FRDM-K64F On-board MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K66F On-board MK66FN2M0VMD18 180MHz 2MB 256KB
Freescale Kinetis FRDM-K82F On-board MK82FN256VLL15 150MHz 256KB 256KB
Freescale Kinetis FRDM-KL05Z On-board MKL05Z32VFM4 48MHz 32KB 4KB
Freescale Kinetis FRDM-KL25Z On-board MKL25Z128VLK4 48MHz 128KB 16KB
Freescale Kinetis FRDM-KL27Z On-board MKL27Z64VLH4 48MHz 64KB 16KB
Freescale Kinetis FRDM-KL43Z On-board MKL43Z256VLH4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL46Z On-board MKL46Z256VLL4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL82Z External MKL82Z128VLK7 96MHz 128KB 96KB
Freescale Kinetis FRDM-KW24D512 External MKW24D512 50MHz 512KB 64KB
Freescale Kinetis FRDM-KW41Z On-board MKW41Z512VHT4 48MHz 512KB 128KB

Name Debug MCU Frequency Flash RAM
Hexiwear External MK64FN1M0VDC12 120MHz 1MB 256KB

GigaDevice GD32V

platform = gd32v

The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from GigaDevice GD32V development platform repository:

  • eval-blink
  • arduino-blink
  • longan-nano-blink

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
GD32VF103V-EVAL GD32VF103VBT6 108MHz 128KB 32KB
Sipeed Longan Nano GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GD32VF103C8T6 108MHz 64KB 20KB
Wio Lite RISC-V GD32VF103CBT6 108MHz 128KB 32KB

Stable and upstream versions

You can switch between stable releases of GigaDevice GD32V development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = gd32v
board = ...
; Custom stable version
[env:custom_stable]
platform = gd32v@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/sipeed/platform-gd32v.git
board = ...


Name Description
framework-arduino-gd32v Arduino Wiring-based Framework (GigaDevice GD32V Core)
framework-gd32vf103-sdk GigaDevice GD32V SDK
tool-gd32vflash GD32V FLASH TOOLS
tool-openocd-gd32v OpenOCD for RISC-V GigaDevice GD32V
toolchain-gd32v GCC for GigaDevice GD32V

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Wio Lite RISC-V External GD32VF103CBT6 108MHz 128KB 32KB

Name Debug MCU Frequency Flash RAM
GD32VF103V-EVAL External GD32VF103VBT6 108MHz 128KB 32KB
Sipeed Longan Nano External GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite External GD32VF103C8T6 108MHz 64KB 20KB

Infineon XMC

platform = infineonxmc

Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Infineon XMC development platform repository:

  • ifx9201
  • device-control
  • arduino-blink
  • spi
  • ultrasonic
  • rtc
  • radar
  • arduino-wire

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
XMC1100 Boot Kit XMC1100 32MHz 64KB 16KB
XMC1100 H-Bridge 2Go XMC1100 32MHz 64KB 16KB
XMC1100 XMC2Go XMC1100 32MHz 64KB 16KB
XMC1300 Boot Kit XMC1300 32MHz 64KB 16KB
XMC1300 Sense2GoL XMC1300 32MHz 32KB 16KB
XMC1400 Boot Kit XMC1400 48MHz 1.95MB 16KB
XMC4200 Distance2Go XMC4200 80MHz 256KB 40KB
XMC4700 Relax Kit XMC4700 144MHz 2.00MB 1.95MB

Stable and upstream versions

You can switch between stable releases of Infineon XMC development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = infineonxmc
board = ...
; Custom stable version
[env:custom_stable]
platform = infineonxmc@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/Infineon/platformio-infineonxmc.git
board = ...


Name Description
framework-arduinoxmc Arduino Wiring-based Framework (Infineon XMC Core)
tool-jlink SEGGER J-Link Software and Documentation Pack
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
XMC1100 Boot Kit On-board XMC1100 32MHz 64KB 16KB
XMC1100 H-Bridge 2Go On-board XMC1100 32MHz 64KB 16KB
XMC1100 XMC2Go On-board XMC1100 32MHz 64KB 16KB
XMC1300 Boot Kit On-board XMC1300 32MHz 64KB 16KB
XMC1300 Sense2GoL On-board XMC1300 32MHz 32KB 16KB
XMC1400 Boot Kit On-board XMC1400 48MHz 1.95MB 16KB
XMC4200 Distance2Go On-board XMC4200 80MHz 256KB 40KB
XMC4700 Relax Kit On-board XMC4700 144MHz 2.00MB 1.95MB

Intel ARC32

platform = intel_arc32

ARC embedded processors are a family of 32-bit CPUs that are widely used in SoC devices for storage, home, mobile, automotive, and Internet of Things applications.

For more detailed information please visit vendor site.

  • Examples
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Intel ARC32 development platform repository:

  • arduino-curie-imu
  • arduino-blink
  • arduino-internal-libs

Stable and upstream versions

You can switch between stable releases of Intel ARC32 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = intel_arc32
board = ...
; Custom stable version
[env:custom_stable]
platform = intel_arc32@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-intel_arc32.git
board = ...


Name Description
framework-arduinointel Arduino Wiring-based Framework (Intel ARC Core)
tool-arduino101load Genuino101 uploader
toolchain-intelarc32 GCC for Intel ARC

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Arduino/Genuino 101 No ARCV2EM 32MHz 152KB 80KB

Intel MCS-51 (8051)

platform = intel_mcs51

The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

For more detailed information please visit vendor site.

  • Examples
  • Stable and upstream versions
  • Packages
  • Boards

Examples are listed from Intel MCS-51 (8051) development platform repository:

  • stc-header
  • native-blink
  • stc-blink

Stable and upstream versions

You can switch between stable releases of Intel MCS-51 (8051) development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = intel_mcs51
board = ...
; Custom stable version
[env:custom_stable]
platform = intel_mcs51@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-intel_mcs51.git
board = ...


Name Description
tool-stcgal Open Source STC MCU ISP flash tool
toolchain-sdcc Small Device C Compiler

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Generic N79E8432 No N79E8432 22MHz 4KB 512B
Generic N79E844 No N79E844 22MHz 8KB 512B
Generic N79E845 No N79E845 22MHz 16KB 512B
Generic N79E854 No N79E854 22MHz 8KB 512B
Generic N79E855 No N79E855 22MHz 16KB 512B

Name Debug MCU Frequency Flash RAM
Generic STC15F204EA No STC15F204EA 11MHz 4KB 256B
Generic STC15F2K60S2 No STC15F2K60S2 6MHz 60KB 2KB
Generic STC15W204S No STC15W204S 11MHz 4KB 256B
Generic STC15W404AS No STC15W404AS 11MHz 4KB 512B
Generic STC15W408AS No STC15W408AS 11MHz 8KB 512B
Generic STC89C52RC No STC89C52RC 11MHz 8KB 512B

Kendryte K210

platform = kendryte210

Kendryte K210 is an AI capable RISCV64 dual core SoC.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Kendryte K210 development platform repository:

  • arduino-blink
  • kendryte-standalone-sdk_hello
  • kendryte-freertos-sdk_hello

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
Sipeed MAIX BiT K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic K210 400MHz 16MB 6MB
Sipeed MAIX GO K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK K210 400MHz 16MB 6MB
Sipeed MAIXDUINO K210 400MHz 16MB 6MB
Sipeed MF1 MF1 K210 400MHz 16MB 6MB

Stable and upstream versions

You can switch between stable releases of Kendryte K210 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = kendryte210
board = ...
; Custom stable version
[env:custom_stable]
platform = kendryte210@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/sipeed/platform-kendryte210.git
board = ...


Name Description
framework-kendryte-freertos-sdk Kendryte SDK with FreeRTOS support
framework-kendryte-standalone-sdk Kendryte standalone SDK without OS support
framework-maixduino Arduino Wiring-based Framework (K210 Core)
tool-kflash-kendryte210 kflash, A Python-based Kendryte K210 UART ISP Utility
tool-openocd-kendryte OpenOCD for RISC-V Kendryte
toolchain-kendryte210 RISC-V GCC toolchain for Kendryte 210

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Sipeed MAIX BiT External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic External K210 400MHz 16MB 6MB
Sipeed MAIX GO External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 External K210 400MHz 16MB 6MB

Lattice iCE40

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.

For more detailed information please visit vendor site.

  • Examples
  • Stable and upstream versions
  • Packages
  • Boards

Examples are listed from Lattice iCE40 development platform repository:

  • leds
  • counter

Stable and upstream versions

You can switch between stable releases of Lattice iCE40 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = lattice_ice40
board = ...
; Custom stable version
[env:custom_stable]
platform = lattice_ice40@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-lattice_ice40.git
board = ...


Name Description
toolchain-icestorm Tools for analyzing and creating bitstream files for FPGA IceStorm
toolchain-iverilog Verilog simulation and synthesis tool

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
IceZUM Alhambra FPGA No ICE40-HX1K-TQ144 12MHz 32KB 32KB

Name Debug MCU Frequency Flash RAM
Lattice iCEstick FPGA Evaluation Kit No ICE40-HX1K-TQ144 12MHz 32KB 32KB

Maxim 32

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.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Maxim 32 development platform repository:

  • mbed-blink
  • mbed-serial
  • mbed-rtos
  • mbed-events
  • mbed-dsp

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
Maxim ARM mbed Enabled Development Platform for MAX32600 MAX32600 24MHz 256KB 32KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
MAX32620FTHR MAX32620FTHR 96MHz 2MB 256KB
Maxim Health Sensor Platform MAX32620 96MHz 2MB 256KB
Maxim Wireless Sensor Node Demonstrator MAX32610 24MHz 256KB 32KB

Stable and upstream versions

You can switch between stable releases of Maxim 32 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = maxim32
board = ...
; Custom stable version
[env:custom_stable]
platform = maxim32@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-maxim32.git
board = ...


Name Description
framework-mbed mbed Framework
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-pyocd Open source python library for programming and debugging ARM Cortex-M microcontrollers using CMSIS-DAP
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
MAX32620FTHR External MAX32620FTHR 96MHz 2MB 256KB
MAX32625MBED No MAX32625 96MHz 512KB 160KB
MAX32625NEXPAQ No MAX32625 96MHz 512KB 160KB
MAX32625PICO No MAX32625 96MHz 512KB 160KB
Maxim ARM mbed Enabled Development Platform for MAX32600 On-board MAX32600 24MHz 256KB 32KB
Maxim Health Sensor Platform External MAX32620 96MHz 2MB 256KB
Maxim MAX32630FTHR Application Platform No MAX32630 96MHz 2MB 512KB
Maxim Wireless Sensor Node Demonstrator External MAX32610 24MHz 256KB 32KB

Sigma Delta Technologies

Name Debug MCU Frequency Flash RAM
SDT32620B No MAX32620IWG 96MHz 2MB 256KB
SDT32625B No MAX32625ITK 96MHz 512KB 160KB

Microchip PIC32

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!

For more detailed information please visit vendor site.

  • Examples
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Microchip PIC32 development platform repository:

  • arduino-blink
  • arduino-internal-libs

Stable and upstream versions

You can switch between stable releases of Microchip PIC32 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = microchippic32
board = ...
; Custom stable version
[env:custom_stable]
platform = microchippic32@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-microchippic32.git
board = ...


Name Description
framework-arduinomicrochippic32 Arduino Wiring-based Framework (PIC32 Core)
tool-pic32prog pic32prog
toolchain-microchippic32 GCC for Microchip PIC32

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



4D Systems

Name Debug MCU Frequency Flash RAM
4D Systems PICadillo 35T No 32MX795F512L 80MHz 508KB 128KB

Name Debug MCU Frequency Flash RAM
HelvePic32 No 32MX250F128B 48MHz 120KB 32KB
HelvePic32 No 32MX250F128B 48MHz 120KB 32KB
HelvePic32 No 32MX250F128D 48MHz 120KB 32KB
HelvePic32 MX270 No 32MX270F256B 48MHz 244KB 62KB
HelvePic32 Robot No 32MX270F256D 48MHz 244KB 62KB
HelvePic32 SMD MX270 No 32MX270F256D 48MHz 244KB 62KB

Name Debug MCU Frequency Flash RAM
RGB Station No 32MX270F256D 48MHz 240KB 62KB

Name Debug MCU Frequency Flash RAM
Digilent Cerebot 32MX4 No 32MX460F512L 80MHz 508KB 32KB
Digilent Cerebot 32MX7 No 32MX795F512L 80MHz 508KB 128KB
Digilent OpenScope No 32MZ2048EFG124 200MHz 1.98MB 512KB
Digilent chipKIT Cmod No 32MX150F128D 40MHz 124KB 32KB
Digilent chipKIT DP32 No 32MX250F128B 40MHz 120KB 32KB
Digilent chipKIT MAX32 No 32MX795F512L 80MHz 508KB 128KB
Digilent chipKIT MX3 No 32MX320F128H 80MHz 124KB 16KB
Digilent chipKIT Pro MX4 No 32MX460F512L 80MHz 508KB 32KB
Digilent chipKIT Pro MX7 No 32MX795F512L 80MHz 508KB 128KB
Digilent chipKIT UNO32 No 32MX320F128H 80MHz 124KB 16KB
Digilent chipKIT WF32 No 32MX695F512L 80MHz 508KB 128KB
Digilent chipKIT WiFire No 32MZ2048ECG100 200MHz 1.98MB 512KB
Digilent chipKIT uC32 No 32MX340F512H 80MHz 508KB 32KB
chipKIT WiFire rev. C No 32MZ2048EFG100 200MHz 1.98MB 512KB

Name Debug MCU Frequency Flash RAM
Fubarino Mini No 32MX250F128D 48MHz 120KB 32KB
Fubarino SD (1.5) No 32MX795F512H 80MHz 508KB 128KB
Mini 2.0 No 32MX270F256D 48MHz 240KB 62KB

Name Debug MCU Frequency Flash RAM
DataStation Mini No 32MX150F128C 40MHz 120KB 32KB

Name Debug MCU Frequency Flash RAM
MikroElektronika Clicker 2 No 32MX460F512L 80MHz 508KB 32KB
MikroElektronika Flip N Click MZ No 32MZ2048EFH100 252MHz 1.98MB 512KB

Name Debug MCU Frequency Flash RAM
Olimex PIC32-PINGUINO No 32MX440F256H 80MHz 252KB 32KB

Name Debug MCU Frequency Flash RAM
OpenBCI 32bit No 32MX250F128B 40MHz 120KB 32KB

Name Debug MCU Frequency Flash RAM
PONTECH UAV100 No 32MX440F512H 80MHz 508KB 32KB

Name Debug MCU Frequency Flash RAM
Pontech NoFire No 32MZ2048EFG100 200MHz 1.98MB 512KB
Pontech Quick240 No 32MX795F512L 80MHz 508KB 128KB

Name Debug MCU Frequency Flash RAM
SeeedStudio CUI32stem No 32MX795F512H 80MHz 508KB 128KB

Name Debug MCU Frequency Flash RAM
Pic32 CUI32-Development Stick No 32MX440F512H 80MHz 508KB 32KB

Name Debug MCU Frequency Flash RAM
UBW32 MX460 No 32MX460F512L 80MHz 508KB 32KB
UBW32 MX795 No 32MX795F512L 80MHz 508KB 128KB

Name Debug MCU Frequency Flash RAM
chipKIT Lenny No 32MX270F256D 40MHz 120KB 32KB

Name Debug MCU Frequency Flash RAM
Element14 chipKIT Pi No 32MX250F128B 40MHz 120KB 32KB

Nordic nRF51

platform = nordicnrf51

The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Nordic nRF51 development platform repository:

  • mbed-blink
  • mbed-serial
  • zephyr-blink
  • mbed-events
  • arduino-blink
  • arduino-ble-led
  • zephyr-ble-eddystone
  • arduino-internal-libs
  • zephyr-drivers-entropy
  • mbed-ble-thermometer

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
BBC micro:bit NRF51822 16MHz 256KB 16KB
Calliope mini NRF51822 16MHz 256KB 16KB
Delta DFCM-NNN40 NRF51822 32MHz 256KB 32KB
Delta DFCM-NNN50 NRF51822 32MHz 256KB 16KB
JKSoft Wallbot BLE NRF51822 16MHz 128KB 16KB
Nordic Beacon Kit (PCA20006) NRF51822 32MHz 256KB 32KB
Nordic nRF51 Dongle (PCA10031) NRF51822 32MHz 256KB 32KB
Nordic nRF51822-mKIT NRF51822 16MHz 128KB 16KB
Nordic nRF51X22 Development Kit(PCA1000X) NRF51822 32MHz 256KB 32KB
RedBearLab BLE Nano 1.5 NRF51822 16MHz 256KB 32KB
RedBearLab nRF51822 NRF51822 16MHz 256KB 16KB
Seeed Arch BLE NRF51822 16MHz 128KB 16KB
Seeed Arch Link NRF51822 16MHz 256KB 16KB
Seeed Tiny BLE NRF51822 16MHz 256KB 16KB
Switch Science mbed HRM1017 NRF51822 16MHz 256KB 16KB
Switch Science mbed TY51822r3 NRF51822 32MHz 256KB 32KB
VNG VBLUNO51 NRF51822 16MHz 128KB 32KB
y5 nRF51822 mbug NRF51822 16MHz 256KB 16KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
BluzDK NRF51822 32MHz 256KB 32KB
OSHChip NRF51822 32MHz 256KB 32KB
Sino:Bit NRF51822 32MHz 256KB 32KB
Waveshare BLE400 NRF51822 32MHz 256KB 32KB
ng-beacon NRF51822 16MHz 256KB 32KB

Stable and upstream versions

You can switch between stable releases of Nordic nRF51 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = nordicnrf51
board = ...
; Custom stable version
[env:custom_stable]
platform = nordicnrf51@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-nordicnrf51.git
board = ...


Name Description
framework-arduinonordicnrf5 Arduino Wiring-based Framework (Nordic NRF5 Core)
framework-mbed mbed Framework
framework-zephyr Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
framework-zephyr-canopennode Zephyr module for CANopenNode - a free and open source CANopen Stack
framework-zephyr-civetweb Zephyr module CivetWeb Embedded C/C++ web server
framework-zephyr-fatfs Zephyr module for FATFS filesystem
framework-zephyr-hal-nordic Nordic nRF5x HAL for Zephyr framework
framework-zephyr-libmetal Zephyr module for HAL abstraction layer used by open-amp
framework-zephyr-littlefs Zephyr module for littlefs filesystem
framework-zephyr-loramac-node Zephyr module for LoRaWAN endpoint stack implementation
framework-zephyr-lvgl Zephyr module for LittlevGL - an Open-source Embedded GUI Library
framework-zephyr-mbedtls mbedTLS module for Zephyr
framework-zephyr-mcuboot Zephyr module for MCUboot - a secure bootloader for 32-bit MCUs
framework-zephyr-mcumgr Zephyr module for mcumgr management library for 32-bit MCUs
framework-zephyr-mipi-sys-t Zephyr module for MIPI System Software Trace
framework-zephyr-nrf-hw-models Zephyr module for NRF52xxx HW models
framework-zephyr-open-amp Zephyr module for Open Asymmetric Multi Processing (OpenAMP) framework
framework-zephyr-openthread OpenThread module for Zephyr
framework-zephyr-segger Zephyr module for Segger RTT
framework-zephyr-tinycbor Zephyr module for Concise Binary Object Representation Library
tool-cmake CMake is an open-source, cross-platform family of tools designed to build, test and package software.
tool-dtc Device tree compiler
tool-gperf GNU gperf is a perfect hash function generator.
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-ninja Ninja is a small build system with a focus on speed.
tool-nrfjprog nRF5x command line tool
tool-openocd OpenOCD
tool-sreccat Merging tool
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
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.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
BBC micro:bit On-board NRF51822 16MHz 256KB 16KB

Name Debug MCU Frequency Flash RAM
BluzDK External NRF51822 32MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
Calliope mini On-board NRF51822 16MHz 256KB 16KB

Name Debug MCU Frequency Flash RAM
Delta DFCM-NNN40 On-board NRF51822 32MHz 256KB 32KB
Delta DFCM-NNN50 On-board NRF51822 32MHz 256KB 16KB

Name Debug MCU Frequency Flash RAM
JKSoft Wallbot BLE On-board NRF51822 16MHz 128KB 16KB

Name Debug MCU Frequency Flash RAM
Nordic Beacon Kit (PCA20006) On-board NRF51822 32MHz 256KB 32KB
Nordic nRF51 Dongle (PCA10031) On-board NRF51822 32MHz 256KB 32KB
Nordic nRF51822-mKIT On-board NRF51822 16MHz 128KB 16KB
Nordic nRF51X22 Development Kit(PCA1000X) On-board NRF51822 32MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
OSHChip External NRF51822 32MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
RedBearLab BLE Nano 1.5 On-board NRF51822 16MHz 256KB 32KB
RedBearLab nRF51822 On-board NRF51822 16MHz 256KB 16KB

Name Debug MCU Frequency Flash RAM
Seeed Arch BLE On-board NRF51822 16MHz 128KB 16KB
Seeed Arch Link On-board NRF51822 16MHz 256KB 16KB
Seeed Tiny BLE On-board NRF51822 16MHz 256KB 16KB

Switch Science

Name Debug MCU Frequency Flash RAM
Switch Science mbed HRM1017 On-board NRF51822 16MHz 256KB 16KB
Switch Science mbed TY51822r3 On-board NRF51822 32MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
VNG VBLUNO51 On-board NRF51822 16MHz 128KB 32KB

Name Debug MCU Frequency Flash RAM
Waveshare BLE400 External NRF51822 32MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
ng-beacon External NRF51822 16MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
Sino:Bit External NRF51822 32MHz 256KB 32KB

y5 design

Name Debug MCU Frequency Flash RAM
y5 nRF51822 mbug On-board NRF51822 16MHz 256KB 16KB

Nordic nRF52

platform = nordicnrf52

The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

For more detailed information please visit vendor site.

  • Tutorials
  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

  • Arduino and Nordic nRF52-DK: debugging and unit testing
  • Zephyr and Nordic nRF52-DK: debugging, unit testing, project analysis

Examples are listed from Nordic nRF52 development platform repository:

  • mbed-blink
  • mbed-serial
  • zephyr-blink
  • mbed-rtos
  • mbed-events
  • zephyr-net-echo-client
  • arduino-blink
  • arduino-ble-led
  • zephyr-ble-beacon
  • mbed-nfc
  • zephyr-subsys-nvs
  • mbed-dsp
  • mbed-ble-thermometer
  • arduino-nina-b1-generic-example
  • arduino-bluefruit-bleuart
  • arduino-serial-plotter

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
BL652 Development Kit NRF52832 64MHz 512KB 64KB
BL654 Development Kit NRF52840 64MHz 1MB 256KB
Delta DFBM-NQ620 NRF52832 64MHz 512KB 64KB
ElectronutLabs Blip NRF52840 64MHz 1MB 256KB
ElectronutLabs Papyr NRF52840 64MHz 1MB 256KB
ItsyBitsy nRF52840 Express NRF52840 64MHz 796KB 243KB
Makerdiary nRF52832-MDK NRF52832 64MHz 512KB 64KB
Makerdiary nRF52840-MDK NRF52840 64MHz 1MB 256KB
Nordic nRF52-DK NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK NRF52840 64MHz 1MB 256KB
Nordic nRF52840-DK (Adafruit BSP) NRF52840 64MHz 796KB 243KB
RedBearLab BLE Nano 2 NRF52832 64MHz 512KB 64KB
RedBearLab Blend 2 NRF52832 64MHz 512KB 64KB
VNG VBLUno52 NRF52832 64MHz 512KB 64KB
u-blox EVK-NINA-B1 NRF52832 64MHz 512KB 64KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
96Boards Nitrogen NRF52832 64MHz 512KB 64KB
Adafruit Bluefruit nRF52832 Feather NRF52832 64MHz 512KB 64KB
Adafruit Feather Bluefruit Sense NRF52840 64MHz 796KB 243KB
Adafruit Feather nRF52840 Express NRF52840 64MHz 796KB 243KB
Arduino Nano 33 BLE NRF52840 64MHz 960KB 256KB
Bluey nRF52832 IoT NRF52832 64MHz 512KB 64KB
Circuit Playground Bluefruit NRF52840 64MHz 796KB 243KB
Holyiot YJ-16019 NRF52832 64MHz 512KB 64KB
Metro nRF52840 Express NRF52840 64MHz 796KB 243KB
Nordic Thingy:52 (nRF52-PCA20020) NRF52832 64MHz 512KB 64KB
Particle Argon NRF52840 64MHz 796KB 243KB
Particle Boron NRF52840 64MHz 796KB 243KB
Particle Xenon NRF52840 64MHz 796KB 243KB
SDT52832B NRF52832 64MHz 512KB 64KB
Taida Century nRF52 mini board NRF52832 64MHz 512KB 64KB
hackaBLE NRF52832 64MHz 512KB 64KB

Stable and upstream versions

You can switch between stable releases of Nordic nRF52 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = nordicnrf52
board = ...
; Custom stable version
[env:custom_stable]
platform = nordicnrf52@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-nordicnrf52.git
board = ...


Name Description
framework-arduino-nrf52-mbedos Arduino framework supporting mbed-enabled boards (nRF52 core)
framework-arduinoadafruitnrf52 Arduino Wiring-based Framework (Nordic nRF52 BLE SoC))
framework-arduinonordicnrf5 Arduino Wiring-based Framework (Nordic NRF5 Core)
framework-mbed mbed Framework
framework-zephyr Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
framework-zephyr-canopennode Zephyr module for CANopenNode - a free and open source CANopen Stack
framework-zephyr-civetweb Zephyr module CivetWeb Embedded C/C++ web server
framework-zephyr-fatfs Zephyr module for FATFS filesystem
framework-zephyr-hal-nordic Nordic nRF5x HAL for Zephyr framework
framework-zephyr-libmetal Zephyr module for HAL abstraction layer used by open-amp
framework-zephyr-littlefs Zephyr module for littlefs filesystem
framework-zephyr-loramac-node Zephyr module for LoRaWAN endpoint stack implementation
framework-zephyr-lvgl Zephyr module for LittlevGL - an Open-source Embedded GUI Library
framework-zephyr-mbedtls mbedTLS module for Zephyr
framework-zephyr-mcuboot Zephyr module for MCUboot - a secure bootloader for 32-bit MCUs
framework-zephyr-mcumgr Zephyr module for mcumgr management library for 32-bit MCUs
framework-zephyr-mipi-sys-t Zephyr module for MIPI System Software Trace
framework-zephyr-nrf-hw-models Zephyr module for NRF52xxx HW models
framework-zephyr-open-amp Zephyr module for Open Asymmetric Multi Processing (OpenAMP) framework
framework-zephyr-openthread OpenThread module for Zephyr
framework-zephyr-segger Zephyr module for Segger RTT
framework-zephyr-tinycbor Zephyr module for Concise Binary Object Representation Library
tool-bossac-nordicnrf52 Basic Open Source SAM-BA Application (BOSSA) for nRF52
tool-cmake CMake is an open-source, cross-platform family of tools designed to build, test and package software.
tool-dtc Device tree compiler
tool-gperf GNU gperf is a perfect hash function generator.
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-ninja Ninja is a small build system with a focus on speed.
tool-nrfjprog nRF5x command line tool
tool-openocd OpenOCD
tool-sreccat Merging tool
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
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.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
96Boards Nitrogen External NRF52832 64MHz 512KB 64KB

Name Debug MCU Frequency Flash RAM
Adafruit Bluefruit nRF52832 Feather External NRF52832 64MHz 512KB 64KB
Adafruit Feather Bluefruit Sense External NRF52840 64MHz 796KB 243KB
Adafruit Feather nRF52840 Express External NRF52840 64MHz 796KB 243KB
Circuit Playground Bluefruit External NRF52840 64MHz 796KB 243KB
ItsyBitsy nRF52840 Express On-board NRF52840 64MHz 796KB 243KB
Metro nRF52840 Express External NRF52840 64MHz 796KB 243KB

Name Debug MCU Frequency Flash RAM
Arduino Nano 33 BLE External NRF52840 64MHz 960KB 256KB

Name Debug MCU Frequency Flash RAM
Delta DFBM-NQ620 On-board NRF52832 64MHz 512KB 64KB

Electronut Labs

Name Debug MCU Frequency Flash RAM
Bluey nRF52832 IoT External NRF52832 64MHz 512KB 64KB
hackaBLE External NRF52832 64MHz 512KB 64KB

Name Debug MCU Frequency Flash RAM
ElectronutLabs Blip On-board NRF52840 64MHz 1MB 256KB
ElectronutLabs Papyr On-board NRF52840 64MHz 1MB 256KB

Name Debug MCU Frequency Flash RAM
Holyiot YJ-16019 External NRF52832 64MHz 512KB 64KB

Laird Connectivity

Name Debug MCU Frequency Flash RAM
BL652 Development Kit On-board NRF52832 64MHz 512KB 64KB
BL654 Development Kit On-board NRF52840 64MHz 1MB 256KB

Name Debug MCU Frequency Flash RAM
Makerdiary nRF52832-MDK On-board NRF52832 64MHz 512KB 64KB
Makerdiary nRF52840-MDK On-board NRF52840 64MHz 1MB 256KB

Name Debug MCU Frequency Flash RAM
Nordic Thingy:52 (nRF52-PCA20020) External NRF52832 64MHz 512KB 64KB
Nordic nRF52-DK On-board NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK On-board NRF52840 64MHz 1MB 256KB
Nordic nRF52840-DK (Adafruit BSP) On-board NRF52840 64MHz 796KB 243KB

Name Debug MCU Frequency Flash RAM
Particle Argon External NRF52840 64MHz 796KB 243KB
Particle Boron External NRF52840 64MHz 796KB 243KB
Particle Xenon External NRF52840 64MHz 796KB 243KB

Name Debug MCU Frequency Flash RAM
RedBearLab BLE Nano 2 On-board NRF52832 64MHz 512KB 64KB
RedBearLab Blend 2 On-board NRF52832 64MHz 512KB 64KB

Sigma Delta Technologies

Name Debug MCU Frequency Flash RAM
SDT52832B External NRF52832 64MHz 512KB 64KB

Taida Century

Name Debug MCU Frequency Flash RAM
Taida Century nRF52 mini board External NRF52832 64MHz 512KB 64KB

Name Debug MCU Frequency Flash RAM
VNG VBLUno52 On-board NRF52832 64MHz 512KB 64KB

Name Debug MCU Frequency Flash RAM
u-blox EVK-NINA-B1 On-board NRF52832 64MHz 512KB 64KB

platform = nuclei

Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Nuclei development platform repository:

  • freertos_demo
  • rtthread_demo
  • demo_dsp
  • helloworld
  • dhrystone
  • whetstone
  • demo_eclic
  • ucosii_demo
  • coremark
  • demo_timer

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
GD32VF103V RVStar Kit GD32VF103VBT6 108MHz 128KB 32KB
HummingBird Evaluation Kit HUMMINGBIRD 5MHz 64KB 64KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
GD32VF103V Evaluation Kit GD32VF103VBT6 108MHz 128KB 32KB

Stable and upstream versions

You can switch between stable releases of Nuclei development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = nuclei
board = ...
; Custom stable version
[env:custom_stable]
platform = nuclei@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/Nuclei-Software/platform-nuclei.git
board = ...


Name Description
framework-nuclei-sdk Nuclei N/NX Embedded Software Development Kit
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-openocd-nuclei OpenOCD branch with Nuclei RISCV support
toolchain-riscv-gcc-nuclei Nuclei RISC-V GCC toolchain

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
Nuclei SDK Open Source Software Development Kit for the Nuclei N/NX processors

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
GD32VF103V Evaluation Kit External GD32VF103VBT6 108MHz 128KB 32KB

Name Debug MCU Frequency Flash RAM
GD32VF103V RVStar Kit On-board GD32VF103VBT6 108MHz 128KB 32KB
HummingBird Evaluation Kit On-board HUMMINGBIRD 5MHz 64KB 64KB

NXP i.MX RT

platform = nxpimxrt

The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from NXP i.MX RT development platform repository:

  • mbed-blink
  • zephyr-blink
  • mbed-rtos-ethernet
  • zephyr-synchronization

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
NXP i.MX RT1010 Evaluation Kit MIMXRT1011DAE5A 500MHz 64KB 128KB
NXP i.MX RT1015 Evaluation Kit MIMXRT1015DAF5A 500MHz 96KB 128KB
NXP i.MX RT1020 Evaluation Kit MIMXRT1021DAG5A 500MHz 64MB 256MB
NXP i.MX RT1050 Evaluation Kit MIMXRT1052DVL6B 600MHz 64MB 512KB
NXP i.MX RT1060 Evaluation Kit MIMXRT1062DVL6A 600MHz 64MB 1MB
NXP i.MX RT1064 Evaluation Kit MIMXRT1064DVL6A 600MHz 4MB 1MB

Stable and upstream versions

You can switch between stable releases of NXP i.MX RT development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = nxpimxrt
board = ...
; Custom stable version
[env:custom_stable]
platform = nxpimxrt@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-nxpimxrt.git
board = ...


Name Description
framework-mbed mbed Framework
framework-zephyr Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
framework-zephyr-canopennode Zephyr module for CANopenNode - a free and open source CANopen Stack
framework-zephyr-civetweb Zephyr module CivetWeb Embedded C/C++ web server
framework-zephyr-fatfs Zephyr module for FATFS filesystem
framework-zephyr-hal-nxp NXP HAL for Zephyr framework
framework-zephyr-libmetal Zephyr module for HAL abstraction layer used by open-amp
framework-zephyr-littlefs Zephyr module for littlefs filesystem
framework-zephyr-loramac-node Zephyr module for LoRaWAN endpoint stack implementation
framework-zephyr-lvgl Zephyr module for LittlevGL - an Open-source Embedded GUI Library
framework-zephyr-mbedtls mbedTLS module for Zephyr
framework-zephyr-mcuboot Zephyr module for MCUboot - a secure bootloader for 32-bit MCUs
framework-zephyr-mcumgr Zephyr module for mcumgr management library for 32-bit MCUs
framework-zephyr-mipi-sys-t Zephyr module for MIPI System Software Trace
framework-zephyr-open-amp Zephyr module for Open Asymmetric Multi Processing (OpenAMP) framework
framework-zephyr-openthread OpenThread module for Zephyr
framework-zephyr-segger Zephyr module for Segger RTT
framework-zephyr-tinycbor Zephyr module for Concise Binary Object Representation Library
tool-cmake CMake is an open-source, cross-platform family of tools designed to build, test and package software.
tool-dtc Device tree compiler
tool-gperf GNU gperf is a perfect hash function generator.
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-ninja Ninja is a small build system with a focus on speed.
tool-openocd OpenOCD
tool-pyocd Open source python library for programming and debugging ARM Cortex-M microcontrollers using CMSIS-DAP
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
NXP i.MX RT1010 Evaluation Kit On-board MIMXRT1011DAE5A 500MHz 64KB 128KB
NXP i.MX RT1015 Evaluation Kit On-board MIMXRT1015DAF5A 500MHz 96KB 128KB
NXP i.MX RT1020 Evaluation Kit On-board MIMXRT1021DAG5A 500MHz 64MB 256MB
NXP i.MX RT1050 Evaluation Kit On-board MIMXRT1052DVL6B 600MHz 64MB 512KB
NXP i.MX RT1060 Evaluation Kit On-board MIMXRT1062DVL6A 600MHz 64MB 1MB
NXP i.MX RT1064 Evaluation Kit On-board MIMXRT1064DVL6A 600MHz 4MB 1MB

NXP LPC

platform = nxplpc

The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from NXP LPC development platform repository:

  • mbed-blink
  • mbed-serial
  • zephyr-blink
  • mbed-rtos
  • mbed-events
  • mbed-custom-target
  • zephyr-drivers-watchdog
  • mbed-rtos-ethernet
  • mbed-dsp
  • zephyr-synchronization

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
ARM mbed LPC11U24 (+CAN) LPC11U24 48MHz 32KB 8KB
Bambino-210E LPC4330 204MHz 8MB 264KB
CoCo-ri-Co! LPC812 30MHz 16KB 4KB
Embedded Artists LPC4088 Display Module LPC4088 120MHz 512KB 96KB
Embedded Artists LPC4088 QuickStart Board LPC4088 120MHz 512KB 96KB
LPCXpresso11U68 LPC11U68 50MHz 256KB 36KB
LPCXpresso824-MAX LPC824 30MHz 32KB 8KB
NXP LPC800-MAX LPC812 30MHz 16KB 4KB
NXP LPCXpresso54114 LPC54114J256BD64 100MHz 256KB 192KB
NXP LPCXpresso54608 LPC54608ET512 180MHz 512KB 200KB
NXP mbed LPC11U24 LPC11U24 48MHz 32KB 8KB
NXP mbed LPC1768 LPC1768 96MHz 512KB 64KB
Seeed Arch Pro LPC1768 96MHz 512KB 64KB
Switch Science mbed LPC1114FN28 LPC1114FN28 48MHz 32KB 4KB
Switch Science mbed LPC824 LPC824 30MHz 32KB 8KB
u-blox C027 LPC1768 96MHz 512KB 64KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
CQ Publishing TG-LPC11U35-501 LPC11U35 48MHz 64KB 10KB
DipCortex M3 LPC1347 72MHz 64KB 12KB
EA LPC11U35 QuickStart Board LPC11U35 48MHz 64KB 10KB
NGX Technologies BlueBoard-LPC11U24 LPC11U24 48MHz 32KB 8KB
NXP LPC11C24 LPC11C24 48MHz 32KB 8KB
NXP LPC11U34 LPC11U34 48MHz 40KB 8KB
NXP LPC11U37 LPC11U37 48MHz 128KB 10KB
NXP LPCXpresso1549 LPC1549 72MHz 256KB 36KB
Solder Splash Labs DipCortex M0 LPC11U24 50MHz 32KB 8KB
y5 LPC11U35 mbug LPC11U35 48MHz 64KB 10KB

Stable and upstream versions

You can switch between stable releases of NXP LPC development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = nxplpc
board = ...
; Custom stable version
[env:custom_stable]
platform = nxplpc@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-nxplpc.git
board = ...


Name Description
framework-mbed mbed Framework
framework-zephyr Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
framework-zephyr-canopennode Zephyr module for CANopenNode - a free and open source CANopen Stack
framework-zephyr-civetweb Zephyr module CivetWeb Embedded C/C++ web server
framework-zephyr-fatfs Zephyr module for FATFS filesystem
framework-zephyr-hal-nxp NXP HAL for Zephyr framework
framework-zephyr-libmetal Zephyr module for HAL abstraction layer used by open-amp
framework-zephyr-littlefs Zephyr module for littlefs filesystem
framework-zephyr-loramac-node Zephyr module for LoRaWAN endpoint stack implementation
framework-zephyr-lvgl Zephyr module for LittlevGL - an Open-source Embedded GUI Library
framework-zephyr-mbedtls mbedTLS module for Zephyr
framework-zephyr-mcuboot Zephyr module for MCUboot - a secure bootloader for 32-bit MCUs
framework-zephyr-mcumgr Zephyr module for mcumgr management library for 32-bit MCUs
framework-zephyr-mipi-sys-t Zephyr module for MIPI System Software Trace
framework-zephyr-open-amp Zephyr module for Open Asymmetric Multi Processing (OpenAMP) framework
framework-zephyr-openthread OpenThread module for Zephyr
framework-zephyr-segger Zephyr module for Segger RTT
framework-zephyr-tinycbor Zephyr module for Concise Binary Object Representation Library
tool-cmake CMake is an open-source, cross-platform family of tools designed to build, test and package software.
tool-dtc Device tree compiler
tool-gperf GNU gperf is a perfect hash function generator.
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-ninja Ninja is a small build system with a focus on speed.
tool-openocd OpenOCD
tool-pyocd Open source python library for programming and debugging ARM Cortex-M microcontrollers using CMSIS-DAP
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
MicroNFCBoard No LPC11U34 48MHz 48KB 10KB

CQ Publishing

Name Debug MCU Frequency Flash RAM
CQ Publishing TG-LPC11U35-501 External LPC11U35 48MHz 64KB 10KB

Elektor Labs

Name Debug MCU Frequency Flash RAM
CoCo-ri-Co! On-board LPC812 30MHz 16KB 4KB

Embedded Artists

Name Debug MCU Frequency Flash RAM
EA LPC11U35 QuickStart Board External LPC11U35 48MHz 64KB 10KB
Embedded Artists LPC4088 Display Module On-board LPC4088 120MHz 512KB 96KB
Embedded Artists LPC4088 QuickStart Board On-board LPC4088 120MHz 512KB 96KB

GHI Electronics

Name Debug MCU Frequency Flash RAM
mBuino No LPC11U24 50MHz 32KB 10KB

Name Debug MCU Frequency Flash RAM
Bambino-210E On-board LPC4330 204MHz 8MB 264KB

NGX Technologies

Name Debug MCU Frequency Flash RAM
NGX Technologies BlueBoard-LPC11U24 External LPC11U24 48MHz 32KB 8KB

Name Debug MCU Frequency Flash RAM
ARM mbed LPC11U24 (+CAN) On-board LPC11U24 48MHz 32KB 8KB
LPCXpresso11U68 On-board LPC11U68 50MHz 256KB 36KB
LPCXpresso824-MAX On-board LPC824 30MHz 32KB 8KB
NXP LPC11C24 External LPC11C24 48MHz 32KB 8KB
NXP LPC11U34 External LPC11U34 48MHz 40KB 8KB
NXP LPC11U37 External LPC11U37 48MHz 128KB 10KB
NXP LPC800-MAX On-board LPC812 30MHz 16KB 4KB
NXP LPCXpresso1549 External LPC1549 72MHz 256KB 36KB
NXP LPCXpresso54114 On-board LPC54114J256BD64 100MHz 256KB 192KB
NXP LPCXpresso54608 On-board LPC54608ET512 180MHz 512KB 200KB
NXP mbed LPC11U24 On-board LPC11U24 48MHz 32KB 8KB
NXP mbed LPC1768 On-board LPC1768 96MHz 512KB 64KB

Outrageous Circuits

Name Debug MCU Frequency Flash RAM
Outrageous Circuits mBuino No LPC11U24 48MHz 32KB 8KB

Name Debug MCU Frequency Flash RAM
Seeed Arch GPRS V2 No LPC11U37 48MHz 128KB 10KB
Seeed Arch Pro On-board LPC1768 96MHz 512KB 64KB
Seeed Xadow M0 No LPC11U35 48MHz 64KB 10KB
Name Debug MCU Frequency Flash RAM
Smeshlink xbed LPC1768 No LPC1768 96MHz 512KB 32KB

Solder Splash Labs

Name Debug MCU Frequency Flash RAM
DipCortex M3 External LPC1347 72MHz 64KB 12KB
Solder Splash Labs DipCortex M0 External LPC11U24 50MHz 32KB 8KB

Switch Science

Name Debug MCU Frequency Flash RAM
Switch Science mbed LPC1114FN28 On-board LPC1114FN28 48MHz 32KB 4KB
Switch Science mbed LPC824 On-board LPC824 30MHz 32KB 8KB

Name Debug MCU Frequency Flash RAM
u-blox C027 On-board LPC1768 96MHz 512KB 64KB

y5 design

Name Debug MCU Frequency Flash RAM
y5 LPC11U35 mbug External LPC11U35 48MHz 64KB 10KB

RISC-V GAP

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.

For more detailed information please visit vendor site.

  • Configuration
  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

  • Drivers
  • AutoTiler
  • Running modes
  • Run from RAM
  • Run from RAM (without any bridge interaction)
  • Flash and run from RAM
  • Flash and run from Flash
  • Run from Flash
  • Run from Flash (without any bridge interaction)

•
Uploading files to HyperFlash

See "Drivers" section for FTDI Chip debug probe.

You need GAP8 AutoTiler library, please request it via support@greenwaves-technologies.com

Put a library somewhere on a disk and add this folder to library path using build_flags in "platformio.ini" (Project Configuration File). For example,

[env:gapuino]
platform = riscv_gap
board = gapuino
framework = ...
build_flags = -L/path/to/libtile/folder




GAPuino supports 2 main modes:

1.
Running from RAM, boot_mode=jtag
2.
Running from HyperFlash, boot_mode=jtag_hyper

A running process can be controlled through the internal upload commands:

  • load, @TODO
  • reqloop, @TODO
  • ioloop, @TODO
  • start, @TODO
  • wait, @TODO

You can configure "boot mode" and list of upload commands using "platformio.ini" (Project Configuration File). Default values are:

  • board_upload.boot_mode = jtag
  • board_upload.commands = load reqloop ioloop start wait

This is a default behavior when you run "Upload" task in PlatformIO IDE or use PlatformIO Core (CLI) and platformio run --target command with upload target.

•
Configure build environment using "platformio.ini" (Project Configuration File) as described below

[env:gapuino]
platform = riscv_gap
board = gapuino
framework = ...
board_upload.commands = load start


•
Run "Upload" task in PlatformIO IDE or use PlatformIO Core (CLI) and platformio run --target command with upload target.

The same as Uploading files to HyperFlash.

•
Configure build environment using "platformio.ini" (Project Configuration File) as described below

[env:gapuino]
platform = riscv_gap
board = gapuino
framework = ...
board_upload.boot_mode = jtag_hyper
board_upload.commands = reqloop ioloop start wait


•
Perform Uploading files to HyperFlash.

NOTE:

You have to perform Uploading files to HyperFlash before.


•
Configure build environment using "platformio.ini" (Project Configuration File) as described below

[env:gapuino]
platform = riscv_gap
board = gapuino
framework = ...
board_upload.boot_mode = jtag_hyper
board_upload.commands = reqloop ioloop start wait


•
Run "Upload" task in PlatformIO IDE or use PlatformIO Core (CLI) and platformio run --target command with upload target.

NOTE:

You have to perform Uploading files to HyperFlash before.


•
Configure build environment using "platformio.ini" (Project Configuration File) as described below

[env:gapuino]
platform = riscv_gap
board = gapuino
framework = ...
board_upload.boot_mode = jtag_hyper
board_upload.commands = start


•
Run "Upload" task in PlatformIO IDE or use PlatformIO Core (CLI) and platformio run --target command with upload target.

1.
Create new project using PlatformIO IDE or initialize project using PlatformIO Core (CLI) and platformio project init (if you have not initialized it yet)
2.
Create data folder (it should be on the same level as src folder) and put files here. Also, you can specify own location for data_dir
3.
Run "Upload File System image" task in PlatformIO IDE or use PlatformIO Core (CLI) and platformio run --target command with uploadfs target.

Examples:

•
PULP OS File System

Examples are listed from RISC-V GAP development platform repository:

  • gapuino-mbed-os-irq
  • gapuino-mbed-autotiler-cifar10
  • gapuino-mbed-driver-hyper-flash
  • gapuino-pulp-os-i2c-eeprom
  • gapuino-mbed-events-queue
  • gapuino-pulp-os-kernel-dma
  • gapuino-mbed-driver-hyper-rtc-alarm
  • gapuino-mbed-fft2d
  • gapuino-pulp-os-autotiler-bilinear-resize
  • gapuino-mbed-matadd
  • gapuino-mbed-features-cluster-dma
  • gapuino-mbed-features-filesystem
  • gapuino-pulp-os-filesystem
  • gapuino-mbed-os-memory-pool
  • gapuino-pulp-os-autotiler-cifar10
  • gapuino-mbed-driver-cpp-raw-serial
  • gapuino-pulp-os-hello-world

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
GAPuino GAP8 GAP8 250MHz 64MB 8MB

Stable and upstream versions

You can switch between stable releases of RISC-V GAP development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = riscv_gap
board = ...
; Custom stable version
[env:custom_stable]
platform = riscv_gap@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/pioplus/platform-riscv_gap.git
board = ...


Name Description
framework-gap_sdk The GAP8 SDK allows you to compile and execute applications on the GAP8 IoT Application Processor.
tool-pulp_tools Top project for building PULP development tools
toolchain-riscv-pulp RISC-V GCC toolchain for PULP platform

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
PULP OS PULP is a silicon-proven Parallel Ultra Low Power platform targeting high energy efficiencies. The platform is organized in clusters of RISC-V cores that share a tightly-coupled data memory.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



GreenWaves Technologies

Name Debug MCU Frequency Flash RAM
GAPuino GAP8 On-board GAP8 250MHz 64MB 8MB

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.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Shakti development platform repository:

  • shakti-sdk_gpio-keypad
  • shakti-sdk_i2c-lm75
  • shakti-sdk_uart-hello

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
Artix-7 35T Arty FPGA Evaluation Kit E-CLASS 50MHz 0B 128KB
Arty A7-100: Artix-7 FPGA Development Board C-CLASS 50MHz 0B 128MB

Stable and upstream versions

You can switch between stable releases of Shakti development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = shakti
board = ...
; Custom stable version
[env:custom_stable]
platform = shakti@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-shakti.git
board = ...


Name Description
framework-shakti-sdk A software development kit for developing applications on Shakti class of processors
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-openocd-riscv OpenOCD for RISC-V
tool-qemu-riscv Open source machine emulator and virtualizer
toolchain-riscv GNU toolchain for RISC-V, including GCC

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
Shakti SDK A software development kit for developing applications on Shakti class of processors

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Artix-7 35T Arty FPGA Evaluation Kit On-board E-CLASS 50MHz 0B 128KB
Arty A7-100: Artix-7 FPGA Development Board On-board C-CLASS 50MHz 0B 128MB

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.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from SiFive development platform repository:

  • zephyr-blink
  • native-blink_asm
  • freedom-e-sdk_hello
  • freedom-e-sdk_test-coreip
  • freedom-e-sdk_sifive-welcome
  • freedom-e-sdk_timer-interrupt
  • freedom-e-sdk_multicore-hello
  • freedom-e-sdk_user-syscall
  • freedom-e-sdk_spi
  • freedom-e-sdk_user-mode
  • zephyr-synchronization
  • zephyr-hello-world

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
Arty FPGA Dev Kit FE310 450MHz 16MB 256MB
HiFive Unleashed FU540 1500MHz 32MB 8GB
HiFive1 FE310 320MHz 16MB 16KB
HiFive1 Rev B FE310 320MHz 16MB 16KB
SparkFun RED-V RedBoard FE310 320MHz 16MB 16KB
SparkFun RED-V Thing Plus FE310 320MHz 16MB 16KB

Stable and upstream versions

You can switch between stable releases of SiFive development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = sifive
board = ...
; Custom stable version
[env:custom_stable]
platform = sifive@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-sifive.git
board = ...


Name Description
framework-freedom-e-sdk Open Source Software for Developing on the SiFive Freedom E Platform
framework-zephyr Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
framework-zephyr-canopennode Zephyr module for CANopenNode - a free and open source CANopen Stack
framework-zephyr-civetweb Zephyr module CivetWeb Embedded C/C++ web server
framework-zephyr-fatfs Zephyr module for FATFS filesystem
framework-zephyr-libmetal Zephyr module for HAL abstraction layer used by open-amp
framework-zephyr-littlefs Zephyr module for littlefs filesystem
framework-zephyr-loramac-node Zephyr module for LoRaWAN endpoint stack implementation
framework-zephyr-lvgl Zephyr module for LittlevGL - an Open-source Embedded GUI Library
framework-zephyr-mbedtls mbedTLS module for Zephyr
framework-zephyr-mcuboot Zephyr module for MCUboot - a secure bootloader for 32-bit MCUs
framework-zephyr-mcumgr Zephyr module for mcumgr management library for 32-bit MCUs
framework-zephyr-mipi-sys-t Zephyr module for MIPI System Software Trace
framework-zephyr-open-amp Zephyr module for Open Asymmetric Multi Processing (OpenAMP) framework
framework-zephyr-openthread OpenThread module for Zephyr
framework-zephyr-segger Zephyr module for Segger RTT
framework-zephyr-tinycbor Zephyr module for Concise Binary Object Representation Library
tool-cmake CMake is an open-source, cross-platform family of tools designed to build, test and package software.
tool-dtc Device tree compiler
tool-gperf GNU gperf is a perfect hash function generator.
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-ninja Ninja is a small build system with a focus on speed.
tool-openocd-riscv OpenOCD for RISC-V
tool-qemu-riscv Open source machine emulator and virtualizer
tool-renode Renode is a development framework which accelerates IoT and embedded systems development by letting you simulate physical hardware systems
toolchain-riscv GNU toolchain for RISC-V, including GCC

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
HiFive Unleashed On-board FU540 1500MHz 32MB 8GB
HiFive1 On-board FE310 320MHz 16MB 16KB
HiFive1 Rev B On-board FE310 320MHz 16MB 16KB

Name Debug MCU Frequency Flash RAM
SparkFun RED-V RedBoard On-board FE310 320MHz 16MB 16KB
SparkFun RED-V Thing Plus On-board FE310 320MHz 16MB 16KB

Name Debug MCU Frequency Flash RAM
Arty FPGA Dev Kit On-board FE310 450MHz 16MB 256MB

Silicon Labs EFM32

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.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Silicon Labs EFM32 development platform repository:

  • mbed-blink
  • zephyr-subsys-console-getline
  • mbed-serial
  • zephyr-blink
  • mbed-events
  • mbed-dsp
  • zephyr-sensor-vl53l0x

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
EFM32GG-STK3700 Giant Gecko EFM32GG990F1024 48MHz 1MB 128KB
EFM32LG-STK3600 Leopard Gecko EFM32LG990F256 48MHz 256KB 32KB
EFM32WG-STK3800 Wonder Gecko EFM32WG990F256 48MHz 256KB 32KB
EFM32ZG-STK3200 Zero Gecko EFM32ZG222F32 24MHz 32KB 4KB
SLSTK3400A USB-enabled Happy Gecko EFM32HG322F64 25MHz 64KB 8KB
SLSTK3401A Pearl Gecko PG1 EFM32PG1B200F256GM48 40MHz 256KB 32KB
Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT EFR32MG12P432F1024 40MHz 1MB 256KB

Stable and upstream versions

You can switch between stable releases of Silicon Labs EFM32 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = siliconlabsefm32
board = ...
; Custom stable version
[env:custom_stable]
platform = siliconlabsefm32@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-siliconlabsefm32.git
board = ...


Name Description
framework-mbed mbed Framework
framework-zephyr Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
framework-zephyr-canopennode Zephyr module for CANopenNode - a free and open source CANopen Stack
framework-zephyr-civetweb Zephyr module CivetWeb Embedded C/C++ web server
framework-zephyr-fatfs Zephyr module for FATFS filesystem
framework-zephyr-hal-silabs SiliconLabs HAL for Zephyr framework
framework-zephyr-libmetal Zephyr module for HAL abstraction layer used by open-amp
framework-zephyr-littlefs Zephyr module for littlefs filesystem
framework-zephyr-loramac-node Zephyr module for LoRaWAN endpoint stack implementation
framework-zephyr-lvgl Zephyr module for LittlevGL - an Open-source Embedded GUI Library
framework-zephyr-mbedtls mbedTLS module for Zephyr
framework-zephyr-mcuboot Zephyr module for MCUboot - a secure bootloader for 32-bit MCUs
framework-zephyr-mcumgr Zephyr module for mcumgr management library for 32-bit MCUs
framework-zephyr-mipi-sys-t Zephyr module for MIPI System Software Trace
framework-zephyr-open-amp Zephyr module for Open Asymmetric Multi Processing (OpenAMP) framework
framework-zephyr-openthread OpenThread module for Zephyr
framework-zephyr-segger Zephyr module for Segger RTT
framework-zephyr-tinycbor Zephyr module for Concise Binary Object Representation Library
tool-cmake CMake is an open-source, cross-platform family of tools designed to build, test and package software.
tool-dtc Device tree compiler
tool-gperf GNU gperf is a perfect hash function generator.
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-ninja Ninja is a small build system with a focus on speed.
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Silicon Labs

Name Debug MCU Frequency Flash RAM
EFM32GG-STK3700 Giant Gecko On-board EFM32GG990F1024 48MHz 1MB 128KB
EFM32LG-STK3600 Leopard Gecko On-board EFM32LG990F256 48MHz 256KB 32KB
EFM32WG-STK3800 Wonder Gecko On-board EFM32WG990F256 48MHz 256KB 32KB
EFM32ZG-STK3200 Zero Gecko On-board EFM32ZG222F32 24MHz 32KB 4KB
SLSTK3400A USB-enabled Happy Gecko On-board EFM32HG322F64 25MHz 64KB 8KB
SLSTK3401A Pearl Gecko PG1 On-board EFM32PG1B200F256GM48 40MHz 256KB 32KB
Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT On-board EFR32MG12P432F1024 40MHz 1MB 256KB

ST STM32

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.

For more detailed information please visit vendor site.

  • Tutorials
  • Configuration
  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

•
STM32Cube HAL and Nucleo-F401RE: debugging and unit testing

There are two different Arduino cores for STM32 microcontrollers: STM32Duino and Arduino STM32 (maple). Both of them have been developed independently, therefore, have different functionality and set of internal libraries. By default, official STM32Duino core is used. Some of the boards support both cores. To change the core you can use a board_build.core option that needs be added to build_flags:

An example of "platformio.ini" (Project Configuration File) with maple core

[env:hy_tinystm103tb]
platform = ststm32
framework = arduino
board = hy_tinystm103tb
board_build.core = maple


STM32Duino core has several options that can be configured using the next configuration flags in build_flags section of "platformio.ini" (Project Configuration File):

Name Description
PIO_FRAMEWORK_ARDUINO_STANDARD_LIB Disable Newlib Nano library
PIO_FRAMEWORK_ARDUINO_NANOLIB_FLOAT_PRINTF Newlib Nano + float printf support
PIO_FRAMEWORK_ARDUINO_NANOLIB_FLOAT_SCANF Newlib Nano + float scanf support

Name Description
PIO_FRAMEWORK_ARDUINO_SERIAL_WITHOUT_GENERIC Enabled (no generic Serial)
PIO_FRAMEWORK_ARDUINO_SERIAL_DISABLED Disabled (no Serial support)

Name Description
PIO_FRAMEWORK_ARDUINO_ENABLE_CDC CDC (generic Serial supersede U(S)ART)
PIO_FRAMEWORK_ARDUINO_ENABLE_CDC_WITHOUT_SERIAL CDC (no generic Serial)
PIO_FRAMEWORK_ARDUINO_ENABLE_HID HID (keyboard and mouse)

Name Description
PIO_FRAMEWORK_ARDUINO_USB_HIGHSPEED High Speed mode
PIO_FRAMEWORK_ARDUINO_USB_HIGHSPEED_FULLMODE High Speed in Full Speed mode

Example:

[env:nucleo_f401re]
platform = ststm32
framework = arduino
board = nucleo_f401re
build_flags =
  -D PIO_FRAMEWORK_ARDUINO_ENABLE_CDC
  -D PIO_FRAMEWORK_ARDUINO_NANOLIB_FLOAT_PRINTF
  -D PIO_FRAMEWORK_ARDUINO_USB_HIGHSPEED_FULLMODE


In this core the USB peripheral (STM32F4 boards only) can be configured using the next configuration flags in build_flags section of "platformio.ini" (Project Configuration File):

Name Description
ENABLE_USB_SERIAL USB serial (CDC)
ENABLE_USB_MASS_STORAGE USB Mass Storage (MSC)

Example:

[env:disco_f407vg]
platform = ststm32
framework = arduino
board = disco_f407vg
board_build.core = maple
build_flags = -D ENABLE_USB_MASS_STORAGE


Examples are listed from ST STM32 development platform repository:

  • mbed-blink
  • mbed-filesystem
  • mbed-serial
  • zephyr-blink
  • stm32cube-ll-blink
  • libopencm3-blink
  • mbed-rtos
  • mbed-events
  • mbed-custom-target
  • cmsis-blink
  • arduino-blink
  • spl-blink
  • mbed-rtos-mesh-minimal
  • arduino-mxchip-sensors
  • zephyr-cpp-synchronization
  • zephyr-net-https-client
  • mbed-rtos-ethernet-tls
  • stm32cube-hal-blink
  • zephyr-drivers-can
  • arduino-mxchip-azureiot
  • arduino-mxchip-filesystem
  • arduino-internal-libs
  • mbed-rtos-ethernet
  • arduino-external-libs
  • mbed-rtos-semaphore
  • mbed-dsp
  • arduino-mxchip-wifiscan
  • libopencm3-1bitsy
  • zephyr-subsys-usb-hid-mouse

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
32F412GDISCOVERY STM32F412ZGT6 100MHz 1MB 256KB
32F723EDISCOVERY STM32F723IEK6 216MHz 512KB 192KB
3D printer controller STM32F765VIT6 216MHz 2MB 512KB
3DP001V1 Evaluation board for 3D printer STM32F401VGT6 84MHz 512KB 96KB
96Boards B96B-F446VE STM32F446VET6 168MHz 512KB 128KB
Armstrap Eagle 1024 STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 STM32F407VET6 168MHz 512KB 192KB
L476DMW1K STM32L476VGT6 80MHz 1MB 128KB
Mbed Connect Cloud STM32F439ZIY6 168MHz 2MB 256KB
Microsoft Azure IoT Development Kit (MXChip AZ3166) STM32F412ZGT6 100MHz 1MB 256KB
P-Nucleo WB55RG STM32WB55RG 64MHz 512KB 192.00KB
RushUp Cloud-JAM STM32F401RET6 84MHz 512KB 96KB
RushUp Cloud-JAM L4 STM32L476RGT6 80MHz 1MB 128KB
ST 32F3348DISCOVERY STM32F334C8T6 72MHz 64KB 12KB
ST 32F401CDISCOVERY STM32F401VCT6 84MHz 256KB 64KB
ST 32F411EDISCOVERY STM32F411VET6 100MHz 512KB 128KB
ST 32F413HDISCOVERY STM32F413ZHT6 100MHz 512KB 128KB
ST 32F429IDISCOVERY STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY STM32F769NIH6 216MHz 1MB 512KB
ST 32L0538DISCOVERY STM32L053C8T6 32MHz 64KB 8KB
ST 32L100DISCOVERY STM32L100RCT6 32MHz 256KB 16KB
ST 32L476GDISCOVERY STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F031K6 STM32F031K6T6 48MHz 32KB 4KB
ST Nucleo F042K6 STM32F042K6T6 48MHz 32KB 6KB
ST Nucleo F070RB STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F072RB STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F091RC STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F303ZE STM32F303ZET6 72MHz 512KB 64KB
ST Nucleo F334R8 STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F410RB STM32F410RBT6 100MHz 128KB 32KB
ST Nucleo F411RE STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F439ZI STM32F439ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F446ZE STM32F446ZET6 180MHz 512KB 128KB
ST Nucleo F722ZE STM32F722ZET6 216MHz 512KB 256KB
ST Nucleo F746ZG STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L011K4 STM32L011K4T6 32MHz 16KB 2KB
ST Nucleo L031K6 STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L412KB STM32L412KBU6 80MHz 128KB 40KB
ST Nucleo L432KC STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L433RC-P STM32L433RC 80MHz 256KB 64KB
ST Nucleo L452RE STM32L452RET6 80MHz 256KB 64KB
ST Nucleo L476RG STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L486RG STM32L486RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY STM32F030R8T6 48MHz 64KB 8KB
ST STM32F0DISCOVERY STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY STM32F407VGT6 168MHz 1MB 128KB
ST STM32L073Z-EVAL STM32L073VZT6 32MHz 192KB 20KB
ST STM32LDISCOVERY STM32L152RBT6 32MHz 128KB 16KB
ST STM32VLDISCOVERY STM32F100RBT6 24MHz 128KB 8KB
ST Sensor Node STM32L476JG 80MHz 1MB 128KB
STM32F7508-DK STM32F750N8H6 216MHz 64KB 340KB
STM32H747I-DISCO STM32H747XIH6 400MHz 2MB 512KB
Seeed Arch Max STM32F407VET6 168MHz 512KB 192KB
Seeed Wio 3G STM32F439VI 180MHz 2MB 256KB
sakura.io Evaluation Board STM32F411RET6 100MHz 1MB 128KB
u-blox C030-R410M IoT STM32F437VG 180MHz 1MB 256KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
1Bitsy STM32F415RGT 168MHz 1MB 128KB
3D Printer Controller STM32F407VET6 168MHz 512KB 192KB
3D Printer control board STM32F446RET6 180MHz 512KB 128KB
96Boards Argonkey (STEVAL-MKI187V1) STM32F412CG 100MHz 1MB 256KB
96Boards Neonkey STM32F411CE 100MHz 512KB 128KB
Adafruit Feather STM32F405 STM32F405RGT6 168MHz 1MB 128KB
AfroFlight Rev5 (8MHz) STM32F103CBT6 72MHz 128KB 20KB
Black STM32F407VE STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F103C8 STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) STM32F103C8T6 72MHz 128KB 20KB
BlackPill F303CC STM32F303CCT6 72MHz 256KB 40KB
BlackPill F401CC STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini STM32F407VET6 168MHz 512KB 128KB
BluePill F103C6 STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) STM32F103C8T6 72MHz 128KB 20KB
Core board F401RCT6 STM32F401RCT6 84MHz 256KB 64KB
Demo F030F4 STM32F030F4P6 48MHz 16KB 4KB
Espotel LoRa Module STM32F411RET6 100MHz 512KB 128KB
F407VG STM32F407VGT6 168MHz 512KB 128KB
FK407M1 STM32F407VET6 168MHz 512KB 128KB
M200 V2 STM32F070CBT6 48MHz 120KB 14.81KB
M300 STM32F070CBT6 48MHz 120KB 14.81KB
MKR Sharky STM32WB55CG 64MHz 512KB 192.00KB
MTS Dragonfly STM32F411RET6 100MHz 512KB 128KB
Malyan M200 V1 STM32F103CBT6 72MHz 120KB 20KB
Maple STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original STM32F103CBT6 72MHz 108KB 17KB
Microduino Core STM32 to Flash STM32F103CBT6 72MHz 105.47KB 16.60KB
MultiTech mDot STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot F411 STM32F411RET6 100MHz 512KB 128KB
MultiTech xDot STM32L151CCU6 32MHz 256KB 32KB
N2+ STM32F405RGT6 168MHz 1MB 192KB
NAMote72 STM32L152RC 32MHz 256KB 32KB
Nucleo G071RB STM32G071RBT6 64MHz 128KB 36KB
Nucleo G431KB STM32G431KBT6 170MHz 128KB 32KB
Nucleo G431RB STM32G431RBT6 170MHz 128KB 32KB
Nucleo G474RE STM32G474RET6 170MHz 512KB 128KB
OLIMEXINO-STM32 STM32F103RBT6 72MHz 128KB 20KB
Olimex STM32-P405 STM32F405RGT6 168MHz 1MB 192KB
Piconomix PX-HER0 STM32L072RB 32MHz 128KB 20KB
PrntrBoard V2 STM32F407RE 168MHz 512KB 192KB
RAK811 LoRa Tracker STM32L151RBT6 32MHz 128KB 16KB
RAK811 LoRa Tracker STM32L151RBT6 32MHz 128KB 32KB
RHF76 052 STM32L051C8T6 32MHz 64KB 8KB
STEVAL-FCU001V1 Flight controller unit evaluation board STM32F401CCU6 84MHz 256KB 64KB
STM32-E407 STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 STM32F407ZGT6 168MHz 1MB 128KB
STM3210C-EVAL STM32F107VCT6 72MHz 256KB 64KB
STM32373C-EVAL STM32F373VCT6 72MHz 256KB 32KB
STM32F072-EVAL STM32F072VBT6 48MHz 128KB 16KB
STM32F103C8 (20k RAM. 64k Flash) STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) STM32F103ZET6 72MHz 512KB 64KB
STM32F303CB (32k RAM. 128k Flash) STM32F303CBT6 72MHz 128KB 32KB
STM32F401RB (64k RAM. 128k Flash) STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) STM32F407VGT6 168MHz 1MB 192KB
STM32F4Stamp F405 STM32F405RGT6 168MHz 1MB 192KB
SensorTile.box STM32L4R9ZI 120MHz 2MB 640KB
Sparky V1 F303 STM32F303CCT6 72MHz 256KB 40KB
ThunderPack STM32L072KZ 32MHz 192KB 20KB
Tiny STM103T STM32F103TBU6 72MHz 128KB 20KB
VAkE v1.0 STM32F446RET6 180MHz 512KB 128KB
Wraith V1 ESC STM32F051K6 48MHz 32KB 7.75KB
u-blox C030-N211 IoT Starter Kit STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit STM32F437VG 180MHz 1MB 256KB
u-blox EVK-ODIN-W2 STM32F439ZIY6 168MHz 2MB 256KB
u-blox ODIN-W2 STM32F439ZIY6 168MHz 2MB 256KB

Stable and upstream versions

You can switch between stable releases of ST STM32 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = ststm32
board = ...
; Custom stable version
[env:custom_stable]
platform = ststm32@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-ststm32.git
board = ...


Name Description
framework-arduinostm32mxchip Arduino Wiring-based Framework (ST STM32 MXChip Core)
framework-arduinoststm32 Arduino Wiring-based Framework (STM32 Core)
framework-arduinoststm32-maple Arduino Wiring-based Framework (ST STM32 Maple Core)
framework-cmsis Vendor-independent hardware abstraction layer for the Cortex-M processor series
framework-libopencm3 libOpenCM3 Framework
framework-mbed mbed Framework
framework-spl Standard Peripheral Library for STM32 MCUs
framework-stm32cube STM32Cube embedded software libraries
framework-zephyr Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
framework-zephyr-canopennode Zephyr module for CANopenNode - a free and open source CANopen Stack
framework-zephyr-civetweb Zephyr module CivetWeb Embedded C/C++ web server
framework-zephyr-fatfs Zephyr module for FATFS filesystem
framework-zephyr-hal-st Zephyr module for the official libraries provided by STMicroelectronics
framework-zephyr-hal-stm32 ST STM32 HAL for Zephyr framework
framework-zephyr-libmetal Zephyr module for HAL abstraction layer used by open-amp
framework-zephyr-littlefs Zephyr module for littlefs filesystem
framework-zephyr-loramac-node Zephyr module for LoRaWAN endpoint stack implementation
framework-zephyr-lvgl Zephyr module for LittlevGL - an Open-source Embedded GUI Library
framework-zephyr-mbedtls mbedTLS module for Zephyr
framework-zephyr-mcuboot Zephyr module for MCUboot - a secure bootloader for 32-bit MCUs
framework-zephyr-mcumgr Zephyr module for mcumgr management library for 32-bit MCUs
framework-zephyr-mipi-sys-t Zephyr module for MIPI System Software Trace
framework-zephyr-open-amp Zephyr module for Open Asymmetric Multi Processing (OpenAMP) framework
framework-zephyr-openthread OpenThread module for Zephyr
framework-zephyr-segger Zephyr module for Segger RTT
framework-zephyr-tinycbor Zephyr module for Concise Binary Object Representation Library
tool-cmake CMake is an open-source, cross-platform family of tools designed to build, test and package software.
tool-dfuutil Host side implementation of the DFU 1.0 and DFU 1.1 specifications
tool-dtc Device tree compiler
tool-gperf GNU gperf is a perfect hash function generator.
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-ninja Ninja is a small build system with a focus on speed.
tool-openocd OpenOCD
tool-stm32duino STM32Duino Tools
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
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.
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.
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.
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.
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.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
1Bitsy External STM32F415RGT 168MHz 1MB 128KB

Name Debug MCU Frequency Flash RAM
96Boards Argonkey (STEVAL-MKI187V1) External STM32F412CG 100MHz 1MB 256KB
96Boards B96B-F446VE On-board STM32F446VET6 168MHz 512KB 128KB
96Boards Neonkey External STM32F411CE 100MHz 512KB 128KB

Name Debug MCU Frequency Flash RAM
Adafruit Feather STM32F405 External STM32F405RGT6 168MHz 1MB 128KB

Name Debug MCU Frequency Flash RAM
AfroFlight Rev5 (8MHz) External STM32F103CBT6 72MHz 128KB 20KB

Name Debug MCU Frequency Flash RAM
Wraith V1 ESC External STM32F051K6 48MHz 32KB 7.75KB

Name Debug MCU Frequency Flash RAM
3D Printer Controller External STM32F407VET6 168MHz 512KB 192KB

Name Debug MCU Frequency Flash RAM
Armstrap Eagle 1024 On-board STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 On-board STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 On-board STM32F407VET6 168MHz 512KB 192KB

Avnet Silica

Name Debug MCU Frequency Flash RAM
ST Sensor Node On-board STM32L476JG 80MHz 1MB 128KB

Name Debug MCU Frequency Flash RAM
F407VG External STM32F407VGT6 168MHz 512KB 128KB

Name Debug MCU Frequency Flash RAM
Espotel LoRa Module External STM32F411RET6 100MHz 512KB 128KB

Name Debug MCU Frequency Flash RAM
BlackPill F103C8 External STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) External STM32F103C8T6 72MHz 128KB 20KB
BluePill F103C6 External STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 External STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) External STM32F103C8T6 72MHz 128KB 20KB
Demo F030F4 External STM32F030F4P6 48MHz 16KB 4KB
FK407M1 External STM32F407VET6 168MHz 512KB 128KB
STM32F103C8 (20k RAM. 64k Flash) External STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) External STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) External STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) External STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) External STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) External STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) External STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) External STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) External STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) External STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) External STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) External STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) External STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) External STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) External STM32F103ZET6 72MHz 512KB 64KB
STM32F303CB (32k RAM. 128k Flash) External STM32F303CBT6 72MHz 128KB 32KB
STM32F401RB (64k RAM. 128k Flash) External STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) External STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) External STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) External STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) External STM32F407VGT6 168MHz 1MB 192KB
STM32F4Stamp F405 External STM32F405RGT6 168MHz 1MB 192KB

Name Debug MCU Frequency Flash RAM
Tiny STM103T External STM32F103TBU6 72MHz 128KB 20KB

Name Debug MCU Frequency Flash RAM
Maple External STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) External STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 External STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original External STM32F103CBT6 72MHz 108KB 17KB

Name Debug MCU Frequency Flash RAM
Microsoft Azure IoT Development Kit (MXChip AZ3166) On-board STM32F412ZGT6 100MHz 1MB 256KB

Name Debug MCU Frequency Flash RAM
M200 V2 External STM32F070CBT6 48MHz 120KB 14.81KB
M300 External STM32F070CBT6 48MHz 120KB 14.81KB
Malyan M200 V1 External STM32F103CBT6 72MHz 120KB 20KB

Name Debug MCU Frequency Flash RAM
Microduino Core STM32 to Flash External STM32F103CBT6 72MHz 105.47KB 16.60KB

Name Debug MCU Frequency Flash RAM
MKR Sharky External STM32WB55CG 64MHz 512KB 192.00KB

Name Debug MCU Frequency Flash RAM
MTS Dragonfly External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot F411 External STM32F411RET6 100MHz 512KB 128KB
MultiTech xDot External STM32L151CCU6 32MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
N2+ External STM32F405RGT6 168MHz 1MB 192KB

Name Debug MCU Frequency Flash RAM
OLIMEXINO-STM32 External STM32F103RBT6 72MHz 128KB 20KB
Olimex STM32-P405 External STM32F405RGT6 168MHz 1MB 192KB
STM32-E407 External STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 External STM32F407ZGT6 168MHz 1MB 128KB

Name Debug MCU Frequency Flash RAM
Piconomix PX-HER0 External STM32L072RB 32MHz 128KB 20KB

Name Debug MCU Frequency Flash RAM
PrntrBoard V2 External STM32F407RE 168MHz 512KB 192KB

Name Debug MCU Frequency Flash RAM
RAK811 LoRa Tracker External STM32L151RBT6 32MHz 128KB 16KB
RAK811 LoRa Tracker External STM32L151RBT6 32MHz 128KB 32KB

Name Debug MCU Frequency Flash RAM
3D Printer control board External STM32F446RET6 180MHz 512KB 128KB

Name Debug MCU Frequency Flash RAM
3D printer controller On-board STM32F765VIT6 216MHz 2MB 512KB

Name Debug MCU Frequency Flash RAM
BlackPill F303CC External STM32F303CCT6 72MHz 256KB 40KB

Name Debug MCU Frequency Flash RAM
RushUp Cloud-JAM On-board STM32F401RET6 84MHz 512KB 96KB
RushUp Cloud-JAM L4 On-board STM32L476RGT6 80MHz 1MB 128KB

Name Debug MCU Frequency Flash RAM
32F412GDISCOVERY On-board STM32F412ZGT6 100MHz 1MB 256KB
32F723EDISCOVERY On-board STM32F723IEK6 216MHz 512KB 192KB
3DP001V1 Evaluation board for 3D printer On-board STM32F401VGT6 84MHz 512KB 96KB
Black STM32F407VE External STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG External STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE External STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE External STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F401CC External STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini External STM32F407VET6 168MHz 512KB 128KB
Core board F401RCT6 External STM32F401RCT6 84MHz 256KB 64KB
Nucleo G071RB External STM32G071RBT6 64MHz 128KB 36KB
Nucleo G431KB External STM32G431KBT6 170MHz 128KB 32KB
Nucleo G431RB External STM32G431RBT6 170MHz 128KB 32KB
Nucleo G474RE External STM32G474RET6 170MHz 512KB 128KB
P-Nucleo WB55RG On-board STM32WB55RG 64MHz 512KB 192.00KB
RHF76 052 External STM32L051C8T6 32MHz 64KB 8KB
ST 32F3348DISCOVERY On-board STM32F334C8T6 72MHz 64KB 12KB
ST 32F401CDISCOVERY On-board STM32F401VCT6 84MHz 256KB 64KB
ST 32F411EDISCOVERY On-board STM32F411VET6 100MHz 512KB 128KB
ST 32F413HDISCOVERY On-board STM32F413ZHT6 100MHz 512KB 128KB
ST 32F429IDISCOVERY On-board STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY On-board STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY On-board STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY On-board STM32F769NIH6 216MHz 1MB 512KB
ST 32L0538DISCOVERY On-board STM32L053C8T6 32MHz 64KB 8KB
ST 32L100DISCOVERY On-board STM32L100RCT6 32MHz 256KB 16KB
ST 32L476GDISCOVERY On-board STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY On-board STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit On-board STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 On-board STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 On-board STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F031K6 On-board STM32F031K6T6 48MHz 32KB 4KB
ST Nucleo F042K6 On-board STM32F042K6T6 48MHz 32KB 6KB
ST Nucleo F070RB On-board STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F072RB On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F091RC On-board STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB On-board STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG On-board STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 On-board STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 On-board STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE On-board STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F303ZE On-board STM32F303ZET6 72MHz 512KB 64KB
ST Nucleo F334R8 On-board STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE On-board STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F410RB On-board STM32F410RBT6 100MHz 128KB 32KB
ST Nucleo F411RE On-board STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG On-board STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH On-board STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI On-board STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F439ZI On-board STM32F439ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE On-board STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F446ZE On-board STM32F446ZET6 180MHz 512KB 128KB
ST Nucleo F722ZE On-board STM32F722ZET6 216MHz 512KB 256KB
ST Nucleo F746ZG On-board STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG On-board STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI On-board STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI On-board STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L011K4 On-board STM32L011K4T6 32MHz 16KB 2KB
ST Nucleo L031K6 On-board STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 On-board STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ On-board STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE On-board STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L412KB On-board STM32L412KBU6 80MHz 128KB 40KB
ST Nucleo L432KC On-board STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L433RC-P On-board STM32L433RC 80MHz 256KB 64KB
ST Nucleo L452RE On-board STM32L452RET6 80MHz 256KB 64KB
ST Nucleo L476RG On-board STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L486RG On-board STM32L486RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG On-board STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P On-board STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI On-board STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY On-board STM32F030R8T6 48MHz 64KB 8KB
ST STM32F0DISCOVERY On-board STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32L073Z-EVAL On-board STM32L073VZT6 32MHz 192KB 20KB
ST STM32LDISCOVERY On-board STM32L152RBT6 32MHz 128KB 16KB
ST STM32VLDISCOVERY On-board STM32F100RBT6 24MHz 128KB 8KB
STEVAL-FCU001V1 Flight controller unit evaluation board External STM32F401CCU6 84MHz 256KB 64KB
STM3210C-EVAL External STM32F107VCT6 72MHz 256KB 64KB
STM32373C-EVAL External STM32F373VCT6 72MHz 256KB 32KB
STM32F072-EVAL External STM32F072VBT6 48MHz 128KB 16KB
STM32F7508-DK On-board STM32F750N8H6 216MHz 64KB 340KB
STM32H747I-DISCO On-board STM32H747XIH6 400MHz 2MB 512KB
SensorTile.box External STM32L4R9ZI 120MHz 2MB 640KB

Name Debug MCU Frequency Flash RAM
Seeed Arch Max On-board STM32F407VET6 168MHz 512KB 192KB
Seeed Wio 3G On-board STM32F439VI 180MHz 2MB 256KB

Name Debug MCU Frequency Flash RAM
NAMote72 External STM32L152RC 32MHz 256KB 32KB

Name Debug MCU Frequency Flash RAM
Sparky V1 F303 External STM32F303CCT6 72MHz 256KB 40KB

Name Debug MCU Frequency Flash RAM
ThunderPack External STM32L072KZ 32MHz 192KB 20KB

Name Debug MCU Frequency Flash RAM
VAkE v1.0 External STM32F446RET6 180MHz 512KB 128KB

Name Debug MCU Frequency Flash RAM
L476DMW1K On-board STM32L476VGT6 80MHz 1MB 128KB

Name Debug MCU Frequency Flash RAM
sakura.io Evaluation Board On-board STM32F411RET6 100MHz 1MB 128KB

Name Debug MCU Frequency Flash RAM
Mbed Connect Cloud On-board STM32F439ZIY6 168MHz 2MB 256KB
u-blox C030-N211 IoT Starter Kit External STM32F437VG 180MHz 1MB 256KB
u-blox C030-R410M IoT On-board STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit External STM32F437VG 180MHz 1MB 256KB
u-blox EVK-ODIN-W2 External STM32F439ZIY6 168MHz 2MB 256KB
u-blox ODIN-W2 External STM32F439ZIY6 168MHz 2MB 256KB

ST STM8

platform = ststm8

The STM8 is an 8-bit microcontroller family by STMicroelectronics an extended variant of the ST7 microcontroller architecture. STM8 microcontrollers are particularly low cost for a full-featured 8-bit microcontroller.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from ST STM8 development platform repository:

  • spl-blink
  • arduino-fade-all-pins
  • spl-uart
  • spl-flash
  • arduino-internal-lib
  • arduino-ping-hc04

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
ST STM8S-DISCOVERY STM8S105C6T6 16MHz 32KB 2KB

Stable and upstream versions

You can switch between stable releases of ST STM8 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = ststm8
board = ...
; Custom stable version
[env:custom_stable]
platform = ststm8@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-ststm8.git
board = ...


Name Description
framework-arduinoststm8 Arduino Wiring-based Framework (STM8 Core)
framework-ststm8spl STM8S/A Standard peripheral library
tool-openocd OpenOCD
tool-stm8binutils STM8 GNU binutils
tool-stm8tools STM8 upload tools
toolchain-sdcc Small Device C Compiler

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
ST STM8S-DISCOVERY On-board STM8S105C6T6 16MHz 32KB 2KB
ST STM8S103F3 Breakout Board No STM8S103F3P6 16MHz 8KB 1KB
ST STM8S105K4T6 Breakout Board No STM8S105K4T6 16MHz 16KB 2KB

Name Debug MCU Frequency Flash RAM
sduino MB (STM8S208MBT6B) No STM8S208MBT6 16MHz 128KB 6KB
sduino UNO (STM8S105K6) No STM8S105K6T6 16MHz 32KB 2KB

platform = teensy

Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.

For more detailed information please visit vendor site.

  • Configuration
  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

  • Optimization
  • USB Features

(valid only for Teensy LC, Teensy 3.0-3.6)

You can control firmware optimization via special macro/define using build_flags in "platformio.ini" (Project Configuration File):

  • -D TEENSY_OPT_FASTER, default
  • -D TEENSY_OPT_FASTER_LTO
  • -D TEENSY_OPT_FAST
  • -D TEENSY_OPT_FAST_LTO
  • -D TEENSY_OPT_FASTEST
  • -D TEENSY_OPT_FASTEST_LTO
  • -D TEENSY_OPT_FASTEST_PURE_CODE, valid only for Teensy 3.5-3.6
  • -D TEENSY_OPT_FASTEST_PURE_CODE_LTO, valid only for Teensy 3.5-3.6
  • -D TEENSY_OPT_DEBUG
  • -D TEENSY_OPT_DEBUG_LTO
  • -D TEENSY_OPT_SMALLEST_CODE
  • -D TEENSY_OPT_SMALLEST_CODE_LTO

The only one macro can be used in per one build environment. Also, you can see verbose build using -v, --verbose option for platformio run command.

Example:

Let's set optimization for the smallest code

[env:teensy_hid_device]
platform = teensy
framework = arduino
board = teensy36
build_flags = -D TEENSY_OPT_SMALLEST_CODE


If you want to use Teensy USB Features, you need to add special macro/define using build_flags:

  • -D USB_SERIAL
  • -D USB_KEYBOARDONLY
  • -D USB_TOUCHSCREEN
  • -D USB_HID_TOUCHSCREEN
  • -D USB_HID
  • -D USB_SERIAL_HID
  • -D USB_MIDI
  • -D USB_MIDI4
  • -D USB_MIDI16
  • -D USB_MIDI_SERIAL
  • -D USB_MIDI4_SERIAL
  • -D USB_MIDI16_SERIAL
  • -D USB_AUDIO
  • -D USB_MIDI_AUDIO_SERIAL
  • -D USB_MIDI16_AUDIO_SERIAL
  • -D USB_MTPDISK
  • -D USB_RAWHID
  • -D USB_FLIGHTSIM
  • -D USB_FLIGHTSIM_JOYSTICK
  • -D USB_EVERYTHING
  • -D USB_DISABLED

A default macro is set to -D USB_SERIAL if no one is specified.

Example:

[env:teensy_hid_device]
platform = teensy
framework = arduino
board = teensy20
build_flags = -D USB_RAWHID


See Teensy USB Examples.

Examples are listed from Teensy development platform repository:

  • mbed-blink
  • mbed-serial
  • mbed-events
  • arduino-blink
  • arduino-hid-usb-mouse
  • arduino-internal-libs
  • mbed-dsp

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name MCU Frequency Flash RAM
Teensy 3.1 / 3.2 MK20DX256 72MHz 256KB 64KB
Teensy 3.5 MK64FX512 120MHz 512KB 255.99KB
Teensy 3.6 MK66FX1M0 180MHz 1MB 256KB
Teensy 4.0 IMXRT1062 600MHz 1.94MB 512KB
Teensy 4.1 IMXRT1062 600MHz 7.75MB 512KB
Teensy LC MKL26Z64 48MHz 62KB 8KB

Stable and upstream versions

You can switch between stable releases of Teensy development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = teensy
board = ...
; Custom stable version
[env:custom_stable]
platform = teensy@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-teensy.git
board = ...


Name Description
framework-arduinoteensy Arduino Wiring-based Framework
framework-mbed mbed Framework
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-teensy Teensy Loader
toolchain-atmelavr avr-gcc
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Teensy programming uses only Windows built-in HID drivers. When Teensy is programmed to act as a USB Serial device, Windows XP, Vista, 7 and 8 require this serial driver is needed to access the COM port your program uses. No special driver installation is necessary on Windows 10.




Name Description
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.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
Teensy 2.0 No ATMEGA32U4 16MHz 31.50KB 2.50KB
Teensy 3.0 No MK20DX128 48MHz 128KB 16KB
Teensy 3.1 / 3.2 External MK20DX256 72MHz 256KB 64KB
Teensy 3.5 External MK64FX512 120MHz 512KB 255.99KB
Teensy 3.6 External MK66FX1M0 180MHz 1MB 256KB
Teensy 4.0 External IMXRT1062 600MHz 1.94MB 512KB
Teensy 4.1 External IMXRT1062 600MHz 7.75MB 512KB
Teensy LC External MKL26Z64 48MHz 62KB 8KB
Teensy++ 2.0 No AT90USB1286 16MHz 127KB 8KB

TI MSP430

platform = timsp430

MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from TI MSP430 development platform repository:

  • arduino-blink
  • native-blink
  • arduino-internal-libs

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
TI FraunchPad MSP-EXP430FR5739LP MSP430FR5739 16MHz 15.37KB 1KB
TI LaunchPad MSP-EXP430F5529LP MSP430F5529 25MHz 47KB 8KB
TI LaunchPad MSP-EXP430FR2311LP MSP430FR2311 16MHz 3.75KB 1KB
TI LaunchPad MSP-EXP430FR2433LP MSP430FR2433 8MHz 15KB 4KB
TI LaunchPad MSP-EXP430FR4133LP MSP430FR4133 8MHz 15KB 2KB
TI LaunchPad MSP-EXP430FR5969LP MSP430FR5969 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430FR5994LP MSP430FR5994 16MHz 256KB 4KB
TI LaunchPad MSP-EXP430FR6989LP MSP430FR6989 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430G2 w/ MSP430G2231 MSP430G2231 1MHz 2KB 256B
TI LaunchPad MSP-EXP430G2 w/ MSP430G2452 MSP430G2452 16MHz 8KB 256B
TI LaunchPad MSP-EXP430G2553LP MSP430G2553 16MHz 16KB 512B

Stable and upstream versions

You can switch between stable releases of TI MSP430 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = timsp430
board = ...
; Custom stable version
[env:custom_stable]
platform = timsp430@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-timsp430.git
board = ...


Name Description
framework-energiamsp430 Energia Wiring-based Framework (MSP430 Core)
tool-dslite Uniflash Standalone Flash Tool for TI Microcontrollers, Sitara Processors & SimpleLink devices
tool-mspdebug MSPDebug
toolchain-timsp430 msp-gcc

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
TI FraunchPad MSP-EXP430FR5739LP On-board MSP430FR5739 16MHz 15.37KB 1KB
TI LaunchPad MSP-EXP430F5529LP On-board MSP430F5529 25MHz 47KB 8KB
TI LaunchPad MSP-EXP430FR2311LP On-board MSP430FR2311 16MHz 3.75KB 1KB
TI LaunchPad MSP-EXP430FR2433LP On-board MSP430FR2433 8MHz 15KB 4KB
TI LaunchPad MSP-EXP430FR4133LP On-board MSP430FR4133 8MHz 15KB 2KB
TI LaunchPad MSP-EXP430FR5969LP On-board MSP430FR5969 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430FR5994LP On-board MSP430FR5994 16MHz 256KB 4KB
TI LaunchPad MSP-EXP430FR6989LP On-board MSP430FR6989 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430G2 w/ MSP430G2231 On-board MSP430G2231 1MHz 2KB 256B
TI LaunchPad MSP-EXP430G2 w/ MSP430G2452 On-board MSP430G2452 16MHz 8KB 256B
TI LaunchPad MSP-EXP430G2553LP On-board MSP430G2553 16MHz 16KB 512B

TI TIVA

platform = titiva

Texas Instruments TM4C12x MCUs offer the industrys most popular ARM Cortex-M4 core with scalable memory and package options, unparalleled connectivity peripherals, advanced application functions, industry-leading analog integration, and extensive software solutions.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from TI TIVA development platform repository:

  • libopencm3-blink
  • arduino-blink
  • native-blink
  • arduino-internal-libs

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
TI LaunchPad (Stellaris) w/ lm4f120 (80MHz) LPLM4F120H5QR 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c123 (80MHz) LPTM4C1230C3PM 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c129 (120MHz) LPTM4C1294NCPDT 120MHz 1MB 256KB

Stable and upstream versions

You can switch between stable releases of TI TIVA development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = titiva
board = ...
; Custom stable version
[env:custom_stable]
platform = titiva@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-titiva.git
board = ...


Name Description
framework-energiativa Energia Wiring-based Framework (LM4F Core)
framework-libopencm3 libOpenCM3 Framework
tool-openocd OpenOCD
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
TI LaunchPad (Stellaris) w/ lm4f120 (80MHz) On-board LPLM4F120H5QR 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c123 (80MHz) On-board LPTM4C1230C3PM 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c129 (120MHz) On-board LPTM4C1294NCPDT 120MHz 1MB 256KB

WIZNet W7500

platform = wiznet7500

The IOP (Internet Offload Processor) W7500 is the one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform especially requiring Internet of things

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from WIZNet W7500 development platform repository:

  • mbed-blink
  • mbed-serial
  • mbed-rtos
  • mbed-events
  • mbed-dsp

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name MCU Frequency Flash RAM
WIZwiki-W7500 WIZNET7500 48MHz 128KB 48KB
WIZwiki-W7500ECO WIZNET7500ECO 48MHz 128KB 48KB
WIZwiki-W7500P WIZNET7500P 48MHz 128KB 48KB

Stable and upstream versions

You can switch between stable releases of WIZNet W7500 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = wiznet7500
board = ...
; Custom stable version
[env:custom_stable]
platform = wiznet7500@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-wiznet7500.git
board = ...


Name Description
framework-mbed mbed Framework
tool-jlink SEGGER J-Link Software and Documentation Pack
tool-pyocd Open source python library for programming and debugging ARM Cortex-M microcontrollers using CMSIS-DAP
toolchain-gccarmnoneeabi gcc-arm-embedded

WARNING:

Linux Users:
  • Install "udev" rules 99-platformio-udev.rules
  • Raspberry Pi users, please read this article Enable serial port on Raspberry Pi.



Windows Users:

Please check that you have a correctly installed USB driver from board manufacturer




Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Debug MCU Frequency Flash RAM
WIZwiki-W7500 On-board WIZNET7500 48MHz 128KB 48KB
WIZwiki-W7500ECO On-board WIZNET7500ECO 48MHz 128KB 48KB
WIZwiki-W7500P On-board WIZNET7500P 48MHz 128KB 48KB

platform = native

Native development platform is intended to be used for desktop OS. This platform uses built-in toolchains (preferable based on GCC), frameworks, libs from particular OS where it will be run.

For more detailed information please visit vendor site.

  • Examples
  • Stable and upstream versions

Examples are listed from Native development platform repository:

•
hello-world

Stable and upstream versions

You can switch between stable releases of Native development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = native
board = ...
; Custom stable version
[env:custom_stable]
platform = native@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-native.git
board = ...


Linux ARM

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.

For more detailed information please visit vendor site.

  • Examples
  • Stable and upstream versions
  • Packages
  • Frameworks
  • Boards

Examples are listed from Linux ARM development platform repository:

  • wiringpi-serial
  • wiringpi-blink

Stable and upstream versions

You can switch between stable releases of Linux ARM development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = linux_arm
board = ...
; Custom stable version
[env:custom_stable]
platform = linux_arm@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-linux_arm.git
board = ...


Name Description
framework-wiringpi GPIO Interface library for the Raspberry Pi
toolchain-gccarmlinuxgnueabi GCC for Linux ARM GNU EABI

Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Raspberry Pi

Name Debug MCU Frequency Flash RAM
Raspberry Pi 1 Model B No BCM2835 700MHz 512MB 512MB
Raspberry Pi 2 Model B No BCM2836 900MHz 1GB 1GB
Raspberry Pi 3 Model B No BCM2837 1200MHz 1GB 1GB
Raspberry Pi Zero No BCM2835 1000MHz 512MB 512MB

platform = linux_i686

Linux i686 (32-bit) 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 or Linux 32-bit) you can build native application for Linux i686 platform.

For more detailed information please visit vendor site.

  • Examples
  • Stable and upstream versions
  • Packages

Examples are listed from Linux i686 development platform repository:

•
hello-world

Stable and upstream versions

You can switch between stable releases of Linux i686 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = linux_i686
board = ...
; Custom stable version
[env:custom_stable]
platform = linux_i686@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-linux_i686.git
board = ...


Name Description
toolchain-gcclinux32 GCC for Linux i686

platform = linux_x86_64

Linux x86_64 (64-bit) 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 or Linux 64-bit) you can build native application for Linux x86_64 platform.

For more detailed information please visit vendor site.

  • Examples
  • Stable and upstream versions
  • Packages

Examples are listed from Linux x86_64 development platform repository:

•
hello-world

Stable and upstream versions

You can switch between stable releases of Linux x86_64 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = linux_x86_64
board = ...
; Custom stable version
[env:custom_stable]
platform = linux_x86_64@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-linux_x86_64.git
board = ...


Name Description
toolchain-gcclinux64 GCC for Linux x86_64

platform = windows_x86

Windows x86 (32-bit) is a metafamily of graphical operating systems developed and marketed by Microsoft. Using host OS (Windows, Linux 32/64 or Mac OS X) you can build native application for Windows x86 platform.

For more detailed information please visit vendor site.

  • Examples
  • Stable and upstream versions
  • Packages

Examples are listed from Windows x86 development platform repository:

•
hello-world

Stable and upstream versions

You can switch between stable releases of Windows x86 development platform and the latest upstream version using platform option in "platformio.ini" (Project Configuration File) as described below.

; Latest stable version
[env:latest_stable]
platform = windows_x86
board = ...
; Custom stable version
[env:custom_stable]
platform = windows_x86@x.y.z
board = ...



[env:upstream_develop]
platform = https://github.com/platformio/platform-windows_x86.git
board = ...


Name Description
toolchain-gccmingw32 MinGW

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.

For more detailed information please visit vendor site.

  • Tutorials
  • Configuration
  • Debugging
  • Examples
  • Platforms
  • Boards

  • Get started with Arduino and ESP32-DevKitC: debugging and unit testing
  • Arduino and Nordic nRF52-DK: debugging and unit testing

Please read official documentation how to configure MCUdude's Cores:

  • Configure "MiniCore"
  • Configure "MightyCore"
  • Configure "MegaCore"

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
3D printer controller ST STM32 STM32F765VIT6 216MHz 2MB 512KB
3DP001V1 Evaluation board for 3D printer ST STM32 STM32F401VGT6 84MHz 512KB 96KB
ATmega128/A Atmel AVR ATMEGA128 16MHz 127KB 4KB
ATmega1280 Atmel AVR ATMEGA1280 16MHz 127KB 8KB
ATmega1281 Atmel AVR ATMEGA1281 16MHz 127KB 8KB
ATmega1284 Atmel AVR ATMEGA1284 16MHz 127KB 16KB
ATmega1284P Atmel AVR ATMEGA1284P 16MHz 127KB 16KB
ATmega16 Atmel AVR ATMEGA16 16MHz 15.50KB 1KB
ATmega164P/PA Atmel AVR ATMEGA164P 16MHz 15.50KB 1KB
ATmega168/A Atmel AVR ATMEGA168 16MHz 15.50KB 1KB
ATmega168P/PA Atmel AVR ATMEGA168P 16MHz 15.50KB 1KB
ATmega2560 Atmel AVR ATMEGA2560 16MHz 255KB 8KB
ATmega324A Atmel AVR ATMEGA324A 16MHz 31.50KB 2KB
ATmega324P Atmel AVR ATMEGA324P 16MHz 31.50KB 2KB
ATmega324PA Atmel AVR ATMEGA324PA 16MHz 31.50KB 2KB
ATmega328 Atmel AVR ATMEGA328 16MHz 31.50KB 2KB
ATmega328P/PA Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
ATmega48/A Atmel AVR ATMEGA48 16MHz 4KB 512B
ATmega644P/PA Atmel AVR ATMEGA644P 16MHz 63KB 4KB
ATmega8/A Atmel AVR ATMEGA8 16MHz 7.50KB 1KB
ATmega88/A Atmel AVR ATMEGA88 16MHz 7.50KB 1KB
ATmega88P/PA Atmel AVR ATMEGA88P 16MHz 7.50KB 1KB
ATmega8P/PA Atmel AVR ATMEGA48P 16MHz 4KB 512B
Adafruit Bluefruit Micro Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Circuit Playground Classic Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Feather 328P Atmel AVR ATMEGA328P 8MHz 31.50KB 2KB
Adafruit Feather 32u4 Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Flora Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Gemma Atmel AVR ATTINY85 8MHz 8KB 512B
Adafruit ItsyBitsy 3V/8MHz Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit ItsyBitsy 5V/16MHz Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Adafruit Metro Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
Adafruit Pro Trinket 3V/12MHz (FTDI) Atmel AVR ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 3V/12MHz (USB) Atmel AVR ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (FTDI) Atmel AVR ATMEGA328P 16MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (USB) Atmel AVR ATMEGA328P 16MHz 28KB 2KB
Adafruit Trinket 3V/8MHz Atmel AVR ATTINY85 8MHz 8KB 512B
Adafruit Trinket 5V/16MHz Atmel AVR ATTINY85 16MHz 8KB 512B
Alorium Hinj Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
Alorium Sno Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
Alorium XLR8 Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
Anarduino MiniWireless Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
Arduboy Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduboy DevKit Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduino BT ATmega168 Atmel AVR ATMEGA168 16MHz 14KB 1KB
Arduino BT ATmega328 Atmel AVR ATMEGA328P 16MHz 28KB 2KB
Arduino Duemilanove or Diecimila ATmega168 Atmel AVR ATMEGA168 16MHz 14KB 1KB
Arduino Duemilanove or Diecimila ATmega328 Atmel AVR ATMEGA328P 16MHz 30KB 2KB
Arduino Esplora Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Ethernet Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
Arduino Fio Atmel AVR ATMEGA328P 8MHz 30KB 2KB
Arduino Industrial 101 Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo ETH Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduino LilyPad ATmega168 Atmel AVR ATMEGA168 8MHz 14KB 1KB
Arduino LilyPad ATmega328 Atmel AVR ATMEGA328P 8MHz 30KB 2KB
Arduino LilyPad USB Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
Arduino M0 Pro (Programming/Debug Port) Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino Mega ADK Atmel AVR ATMEGA2560 16MHz 248KB 8KB
Arduino Mega or Mega 2560 ATmega1280 Atmel AVR ATMEGA1280 16MHz 124KB 8KB
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) Atmel AVR ATMEGA2560 16MHz 248KB 8KB
Arduino Micro Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Mini ATmega168 Atmel AVR ATMEGA168 16MHz 14KB 1KB
Arduino Mini ATmega328 Atmel AVR ATMEGA328P 16MHz 28KB 2KB
Arduino NG or older ATmega168 Atmel AVR ATMEGA168 16MHz 14KB 1KB
Arduino NG or older ATmega8 Atmel AVR ATMEGA8 16MHz 7KB 1KB
Arduino Nano ATmega168 Atmel AVR ATMEGA168 16MHz 14KB 1KB
Arduino Nano ATmega328 Atmel AVR ATMEGA328P 16MHz 30KB 2KB
Arduino Nano ATmega328 (New Bootloader) Atmel AVR ATMEGA328P 16MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) Atmel AVR ATMEGA168 8MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) Atmel AVR ATMEGA168 16MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) Atmel AVR ATMEGA328P 8MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) Atmel AVR ATMEGA328P 16MHz 30KB 2KB
Arduino Robot Control Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Robot Motor Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Uno Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
Arduino Yun Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Yun Mini Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Zero (Programming/Debug Port) Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Atmel ATSAMW25-XPRO Atmel SAM SAMD21G18A 48MHz 256KB 32KB
BBC micro:bit Nordic nRF51 NRF51822 16MHz 256KB 16KB
BQ ZUM BT-328 Atmel AVR ATMEGA328P 16MHz 28KB 2KB
BitWizard Raspduino Atmel AVR ATMEGA328P 16MHz 30KB 2KB
Calliope mini Nordic nRF51 NRF51822 16MHz 256KB 16KB
Controllino Maxi Atmel AVR ATMEGA2560 16MHz 248KB 8KB
Controllino Maxi Automation Atmel AVR ATMEGA2560 16MHz 248KB 8KB
Controllino Mega Atmel AVR ATMEGA2560 16MHz 248KB 8KB
Controllino Mini Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
Delta DFBM-NQ620 Nordic nRF52 NRF52832 64MHz 512KB 64KB
Digispark USB Atmel AVR ATTINY85 16MHz 5.87KB 512B
Engduino 3 Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
EnviroDIY Mayfly Atmel AVR ATMEGA1284P 8MHz 127KB 16KB
Espressif ESP-WROVER-KIT Espressif 32 ESP32 240MHz 4MB 320KB
FYSETC F6 V1.3 Atmel AVR ATMEGA2560 16MHz 252KB 8KB
Generic ATtiny13 Atmel AVR ATTINY13 1MHz 1KB 64B
Generic ATtiny13A Atmel AVR ATTINY13A 1MHz 1KB 64B
Generic ATtiny2313 Atmel AVR ATTINY2313 8MHz 2KB 128B
Generic ATtiny24 Atmel AVR ATTINY24 8MHz 2KB 128B
Generic ATtiny25 Atmel AVR ATTINY25 8MHz 2KB 128B
Generic ATtiny4313 Atmel AVR ATTINY4313 8MHz 4KB 256B
Generic ATtiny44 Atmel AVR ATTINY44 8MHz 4KB 256B
Generic ATtiny45 Atmel AVR ATTINY45 8MHz 4KB 256B
Generic ATtiny84 Atmel AVR ATTINY84 8MHz 8KB 512B
Generic ATtiny85 Atmel AVR ATTINY85 8MHz 8KB 512B
ItsyBitsy nRF52840 Express Nordic nRF52 NRF52840 64MHz 796KB 243KB
LightBlue Bean Atmel AVR ATMEGA328P 8MHz 31.50KB 2KB
LightBlue Bean+ Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
LightUp Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
Linino One Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
LinkIt Smart 7688 Duo Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
LoRa32u4II (868-915MHz) Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
LowPowerLab MightyHat Atmel AVR ATMEGA328P 16MHz 31KB 2KB
LowPowerLab Moteino Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
LowPowerLab Moteino (8Mhz) Atmel AVR ATMEGA328P 8MHz 31.50KB 2KB
LowPowerLab MoteinoMEGA Atmel AVR ATMEGA1284P 16MHz 127KB 16KB
Microduino Core (Atmega168PA@16M,5V) Atmel AVR ATMEGA168P 16MHz 15.50KB 1KB
Microduino Core (Atmega168PA@8M,3.3V) Atmel AVR ATMEGA168P 8MHz 15.50KB 1KB
Microduino Core (Atmega328P@16M,5V) Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
Microduino Core (Atmega328P@8M,3.3V) Atmel AVR ATMEGA328P 8MHz 31.50KB 2KB
Microduino Core USB (ATmega32U4@16M,5V) Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Microduino Core+ (ATmega1284P@16M,5V) Atmel AVR ATMEGA1284P 16MHz 127KB 16KB
Microduino Core+ (ATmega1284P@8M,3.3V) Atmel AVR ATMEGA1284P 8MHz 127KB 16KB
Microduino Core+ (Atmega644PA@16M,5V) Atmel AVR ATMEGA644P 16MHz 63KB 4KB
Microduino Core+ (Atmega644PA@8M,3.3V) Atmel AVR ATMEGA644P 8MHz 63KB 4KB
Microsoft Azure IoT Development Kit (MXChip AZ3166) ST STM32 STM32F412ZGT6 100MHz 1MB 256KB
Nordic Beacon Kit (PCA20006) Nordic nRF51 NRF51822 32MHz 256KB 32KB
Nordic nRF51 Dongle (PCA10031) Nordic nRF51 NRF51822 32MHz 256KB 32KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 NRF52840 64MHz 1MB 256KB
Nordic nRF52840-DK (Adafruit BSP) Nordic nRF52 NRF52840 64MHz 796KB 243KB
OpenEnergyMonitor emonPi Atmel AVR ATMEGA328P 16MHz 30KB 2KB
Original Prusa i3 MK3 Multi Material 2.0 Upgrade Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
P-Nucleo WB55RG ST STM32 STM32WB55RG 64MHz 512KB 192.00KB
PanStamp AVR Atmel AVR ATMEGA328P 8MHz 31.50KB 2KB
Pololu A-Star 32U4 Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
Prusa RAMBo Atmel AVR ATMEGA2560 16MHz 252KB 8KB
Quirkbot Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
RedBearLab BLE Nano 1.5 Nordic nRF51 NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 NRF52832 64MHz 512KB 64KB
RedBearLab Blend Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend 2 Nordic nRF52 NRF52832 64MHz 512KB 64KB
RedBearLab Blend Micro 3.3V/16MHz (overclock) Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend Micro 3.3V/8MHz Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
RedBearLab nRF51822 Nordic nRF51 NRF51822 16MHz 256KB 16KB
RepRap RAMBo Atmel AVR ATMEGA2560 16MHz 252KB 8KB
SODAQ GaLoRa Atmel AVR ATMEGA1284P 8MHz 127KB 16KB
SODAQ Mbili Atmel AVR ATMEGA1284P 8MHz 127KB 16KB
SODAQ Moja Atmel AVR ATMEGA328P 8MHz 31.50KB 2KB
SODAQ Ndogo Atmel AVR ATMEGA1284P 8MHz 127KB 16KB
SODAQ Tatu Atmel AVR ATMEGA1284P 8MHz 127KB 16KB
ST 32F746GDISCOVERY ST STM32 STM32F746NGH6 216MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F091RC ST STM32 STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 ST STM32 STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE ST STM32 STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F401RE ST STM32 STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F411RE ST STM32 STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F767ZI ST STM32 STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI ST STM32 STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L031K6 ST STM32 STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 ST STM32 STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE ST STM32 STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L412KB ST STM32 STM32L412KBU6 80MHz 128KB 40KB
ST Nucleo L432KC ST STM32 STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L452RE ST STM32 STM32L452RET6 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P ST STM32 STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI ST STM32 STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY ST STM32 STM32F030R8T6 48MHz 64KB 8KB
ST STM32F4DISCOVERY ST STM32 STM32F407VGT6 168MHz 1MB 128KB
ST STM32VLDISCOVERY ST STM32 STM32F100RBT6 24MHz 128KB 8KB
ST STM8S-DISCOVERY ST STM8 STM8S105C6T6 16MHz 32KB 2KB
Sanguino ATmega1284p (16MHz) Atmel AVR ATMEGA1284P 16MHz 127KB 16KB
Sanguino ATmega1284p (8MHz) Atmel AVR ATMEGA1284P 8MHz 127KB 16KB
Sanguino ATmega644 or ATmega644A (16 MHz) Atmel AVR ATMEGA644 16MHz 63KB 4KB
Sanguino ATmega644 or ATmega644A (8 MHz) Atmel AVR ATMEGA644 8MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (16 MHz) Atmel AVR ATMEGA644P 16MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (8 MHz) Atmel AVR ATMEGA644P 8MHz 63KB 4KB
Seeed Tiny BLE Nordic nRF51 NRF51822 16MHz 256KB 16KB
Seeeduino Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
SparkFun ATmega128RFA1 Dev Board Atmel AVR ATMEGA128RFA1 16MHz 16KB 124KB
SparkFun Digital Sandbox Atmel AVR ATMEGA328P 8MHz 31.50KB 2KB
SparkFun Fio V3 3.3V/8MHz Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Makey Makey Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Mega Pro 3.3V/8MHz Atmel AVR ATMEGA2560 8MHz 252KB 8KB
SparkFun Mega Pro 5V/16MHz Atmel AVR ATMEGA2560 16MHz 248KB 8KB
SparkFun Mega Pro Mini 3.3V Atmel AVR ATMEGA2560 8MHz 252KB 8KB
SparkFun MicroView Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
SparkFun Pro Micro 3.3V/8MHz Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Pro Micro 5V/16MHz Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Qduino Mini Atmel AVR ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun RedBoard Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
SparkFun Serial 7-Segment Display Atmel AVR ATMEGA328P 8MHz 31.50KB 2KB
SpellFoundry Sleepy Pi 2 Atmel AVR ATMEGA328P 8MHz 30KB 2KB
TI FraunchPad MSP-EXP430FR5739LP TI MSP430 MSP430FR5739 16MHz 15.37KB 1KB
TI LaunchPad (Stellaris) w/ lm4f120 (80MHz) TI TIVA LPLM4F120H5QR 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c123 (80MHz) TI TIVA LPTM4C1230C3PM 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c129 (120MHz) TI TIVA LPTM4C1294NCPDT 120MHz 1MB 256KB
TI LaunchPad MSP-EXP430F5529LP TI MSP430 MSP430F5529 25MHz 47KB 8KB
TI LaunchPad MSP-EXP430FR2311LP TI MSP430 MSP430FR2311 16MHz 3.75KB 1KB
TI LaunchPad MSP-EXP430FR2433LP TI MSP430 MSP430FR2433 8MHz 15KB 4KB
TI LaunchPad MSP-EXP430FR4133LP TI MSP430 MSP430FR4133 8MHz 15KB 2KB
TI LaunchPad MSP-EXP430FR5969LP TI MSP430 MSP430FR5969 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430FR5994LP TI MSP430 MSP430FR5994 16MHz 256KB 4KB
TI LaunchPad MSP-EXP430FR6989LP TI MSP430 MSP430FR6989 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430G2 w/ MSP430G2231 TI MSP430 MSP430G2231 1MHz 2KB 256B
TI LaunchPad MSP-EXP430G2 w/ MSP430G2452 TI MSP430 MSP430G2452 16MHz 8KB 256B
TI LaunchPad MSP-EXP430G2553LP TI MSP430 MSP430G2553 16MHz 16KB 512B
Talk2 Whisper Node Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
The Things Uno Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
TinyCircuits TinyDuino Processor Board Atmel AVR ATMEGA328P 8MHz 30KB 2KB
TinyCircuits TinyLily Mini Processor Atmel AVR ATMEGA328P 8MHz 30KB 2KB
USBasp stick Atmel AVR ATMEGA8 12MHz 8KB 1KB
Wicked Device WildFire V2 Atmel AVR ATMEGA1284P 16MHz 120.00KB 16KB
Wicked Device WildFire V3 Atmel AVR ATMEGA1284P 16MHz 127KB 16KB
XMC1100 Boot Kit Infineon XMC XMC1100 32MHz 64KB 16KB
XMC1100 H-Bridge 2Go Infineon XMC XMC1100 32MHz 64KB 16KB
XMC1100 XMC2Go Infineon XMC XMC1100 32MHz 64KB 16KB
XMC1300 Boot Kit Infineon XMC XMC1300 32MHz 64KB 16KB
XMC1300 Sense2GoL Infineon XMC XMC1300 32MHz 32KB 16KB
XMC1400 Boot Kit Infineon XMC XMC1400 48MHz 1.95MB 16KB
XMC4200 Distance2Go Infineon XMC XMC4200 80MHz 256KB 40KB
XMC4700 Relax Kit Infineon XMC XMC4700 144MHz 2.00MB 1.95MB
ftDuino Atmel AVR ATMEGA32U4 16MHz 28KB 2.50KB
nicai-systems BOB3 coding bot Atmel AVR ATMEGA88 8MHz 8KB 1KB
nicai-systems NIBO 2 robot Atmel AVR ATMEGA128 16MHz 128KB 4KB
nicai-systems NIBO burger robot Atmel AVR ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBO burger robot with Tuning Kit Atmel AVR ATMEGA1284P 20MHz 128KB 16KB
nicai-systems NIBObee robot Atmel AVR ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBObee robot with Tuning Kit Atmel AVR ATMEGA1284P 20MHz 128KB 16KB
u-blox EVK-NINA-B1 Nordic nRF52 NRF52832 64MHz 512KB 64KB
ubIQio Ardhat Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
3D Printer Controller ST STM32 STM32F407VET6 168MHz 512KB 192KB
3D Printer control board ST STM32 STM32F446RET6 180MHz 512KB 128KB
AI Thinker ESP32-CAM Espressif 32 ESP32 240MHz 4MB 320KB
ALKS ESP32 Espressif 32 ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 ESP32 240MHz 16MB 520KB
Adafruit Bluefruit nRF52832 Feather Nordic nRF52 NRF52832 64MHz 512KB 64KB
Adafruit Circuit Playground Express Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Adafruit Crickit M0 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Adafruit ESP32 Feather Espressif 32 ESP32 240MHz 4MB 320KB
Adafruit Feather Bluefruit Sense Nordic nRF52 NRF52840 64MHz 796KB 243KB
Adafruit Feather M0 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 Express Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M4 Express Atmel SAM SAMD51J19A 120MHz 512KB 192KB
Adafruit Feather STM32F405 ST STM32 STM32F405RGT6 168MHz 1MB 128KB
Adafruit Feather nRF52840 Express Nordic nRF52 NRF52840 64MHz 796KB 243KB
Adafruit Gemma M0 Atmel SAM SAMD21E18A 48MHz 256KB 32KB
Adafruit Grand Central M4 Atmel SAM SAMD51P20A 120MHz 1MB 256KB
Adafruit Hallowing M0 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Adafruit Hallowing M4 Atmel SAM SAMD51J19A 120MHz 496KB 192KB
Adafruit ItsyBitsy M0 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Adafruit ItsyBitsy M4 Atmel SAM SAMD51G19A 120MHz 512KB 192KB
Adafruit MONSTER M4SK Atmel SAM SAMD51G19A 120MHz 496KB 192KB
Adafruit Metro M0 Expresss Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Adafruit Metro M4 Atmel SAM SAMD51J19A 120MHz 512KB 192KB
Adafruit Metro M4 AirLift Lite Atmel SAM SAMD51J19A 120MHz 512KB 192KB
Adafruit PyGamer Advance M4 Atmel SAM SAMD51J20A 120MHz 1MB 256KB
Adafruit PyGamer M4 Express Atmel SAM SAMD51J19A 120MHz 512KB 192KB
Adafruit PyPortal M4 Atmel SAM SAMD51J20A 120MHz 1MB 256KB
Adafruit PyPortal M4 Titano Atmel SAM SAMD51J20A 120MHz 1MB 256KB
Adafruit Trellis M4 Atmel SAM SAMD51J19A 120MHz 512KB 192KB
Adafruit Trinket M0 Atmel SAM SAMD21E18A 48MHz 256KB 32KB
Adafruit pIRkey Atmel SAM SAMD21E18A 48MHz 256KB 32KB
Adafruit pyBadge AirLift M4 Atmel SAM SAMD51J20A 120MHz 1008KB 192KB
Adafruit pyBadge M4 Express Atmel SAM SAMD51J19A 120MHz 512KB 192KB
AfroFlight Rev5 (8MHz) ST STM32 STM32F103CBT6 72MHz 128KB 20KB
Arduino Due (Programming Port) Atmel SAM AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) Atmel SAM AT91SAM3X8E 84MHz 512KB 96KB
Arduino M0 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Native USB Port) Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino MKR FOX 1200 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino MKR GSM 1400 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino MKR NB 1500 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1300 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1310 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WiFi 1010 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino MKR1000 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino MKRZERO Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino Nano 33 BLE Nordic nRF52 NRF52840 64MHz 960KB 256KB
Arduino Tian Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (USB Native Port) Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Black STM32F407VE ST STM32 STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG ST STM32 STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 STM32F103C8T6 72MHz 128KB 20KB
BlackPill F303CC ST STM32 STM32F303CCT6 72MHz 256KB 40KB
BlackPill F401CC ST STM32 STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini ST STM32 STM32F407VET6 168MHz 512KB 128KB
BluePill F103C6 ST STM32 STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 STM32F103C8T6 72MHz 128KB 20KB
Bluey nRF52832 IoT Nordic nRF52 NRF52832 64MHz 512KB 64KB
BluzDK Nordic nRF51 NRF51822 32MHz 256KB 32KB
Briki ABC (MBC-WB) - ESP32 Espressif 32 ESP32 240MHz 3.25MB 320KB
Briki ABC (MBC-WB) - Samd21 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Briki MBC-WB - ESP32 Espressif 32 ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - Samd21 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Circuit Playground Bluefruit Nordic nRF52 NRF52840 64MHz 796KB 243KB
Core board F401RCT6 ST STM32 STM32F401RCT6 84MHz 256KB 64KB
D-duino-32 Espressif 32 ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 ESP32 240MHz 4MB 320KB
Demo F030F4 ST STM32 STM32F030F4P6 48MHz 16KB 4KB
Digistump DigiX Atmel SAM AT91SAM3X8E 84MHz 512KB 96KB
Dongsen Tech Pocket 32 Espressif 32 ESP32 240MHz 4MB 320KB
ESP32 FM DevKit Espressif 32 ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 ESP32 240MHz 4MB 320KB
F407VG ST STM32 STM32F407VGT6 168MHz 512KB 128KB
FK407M1 ST STM32 STM32F407VET6 168MHz 512KB 128KB
FireBeetle-ESP32 Espressif 32 ESP32 240MHz 4MB 320KB
Frog Board ESP32 Espressif 32 ESP32 240MHz 4MB 320KB
GD32VF103V-EVAL GigaDevice GD32V GD32VF103VBT6 108MHz 128KB 32KB
Heltec WiFi LoRa 32 Espressif 32 ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev Espressif 32 ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 ESP32 240MHz 4MB 320KB
IoTaaP Magnolia Espressif 32 ESP32 240MHz 4MB 320KB
M200 V2 ST STM32 STM32F070CBT6 48MHz 120KB 14.81KB
M300 ST STM32 STM32F070CBT6 48MHz 120KB 14.81KB
MH ET LIVE ESP32DevKIT Espressif 32 ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 ESP32 240MHz 4MB 320KB
MKR Sharky ST STM32 STM32WB55CG 64MHz 512KB 192.00KB
MKR Vidor 4000 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Malyan M200 V1 ST STM32 STM32F103CBT6 72MHz 120KB 20KB
Maple ST STM32 STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) ST STM32 STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 ST STM32 STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original ST STM32 STM32F103CBT6 72MHz 108KB 17KB
Metro nRF52840 Express Nordic nRF52 NRF52840 64MHz 796KB 243KB
Microduino Core STM32 to Flash ST STM32 STM32F103CBT6 72MHz 105.47KB 16.60KB
Minitronics v2.0 Atmel SAM SAMD21J18A 48MHz 256KB 32KB
Moteino M0 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
N2+ ST STM32 STM32F405RGT6 168MHz 1MB 192KB
NANO 33 IoT Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Node32s Espressif 32 ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 ESP32 240MHz 4MB 320KB
Nucleo G071RB ST STM32 STM32G071RBT6 64MHz 128KB 36KB
Nucleo G431KB ST STM32 STM32G431KBT6 170MHz 128KB 32KB
Nucleo G431RB ST STM32 STM32G431RBT6 170MHz 128KB 32KB
Nucleo G474RE ST STM32 STM32G474RET6 170MHz 512KB 128KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 ESP32 240MHz 4MB 320KB
OLIMEXINO-STM32 ST STM32 STM32F103RBT6 72MHz 128KB 20KB
OSHChip Nordic nRF51 NRF51822 32MHz 256KB 32KB
Particle Xenon Nordic nRF52 NRF52840 64MHz 796KB 243KB
Piconomix PX-HER0 ST STM32 STM32L072RB 32MHz 128KB 20KB
PrntrBoard V2 ST STM32 STM32F407RE 168MHz 512KB 192KB
Pycom LoPy Espressif 32 ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 ESP32 240MHz 4MB 1.25MB
RAK811 LoRa Tracker ST STM32 STM32L151RBT6 32MHz 128KB 16KB
RAK811 LoRa Tracker ST STM32 STM32L151RBT6 32MHz 128KB 32KB
RHF76 052 ST STM32 STM32L051C8T6 32MHz 64KB 8KB
SG-O AirMon Espressif 32 ESP32 240MHz 4MB 320KB
SODAQ Autonomo Atmel SAM SAMD21J18A 48MHz 256KB 32KB
SODAQ ExpLoRer Atmel SAM SAMD21J18A 48MHz 256KB 32KB
SODAQ ONE Atmel SAM SAMD21G18A 48MHz 256KB 32KB
SODAQ SARA Atmel SAM SAMD21J18A 48MHz 256KB 32KB
SODAQ SFF Atmel SAM SAMD21G18A 48MHz 256KB 32KB
STM32-E407 ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 STM32F103ZET6 72MHz 512KB 64KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) ST STM32 STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) ST STM32 STM32F407VGT6 168MHz 1MB 192KB
STM32F4Stamp F405 ST STM32 STM32F405RGT6 168MHz 1MB 192KB
SainSmart Due (Programming Port) Atmel SAM AT91SAM3X8E 84MHz 512KB 96KB
SainSmart Due (USB Native Port) Atmel SAM AT91SAM3X8E 84MHz 512KB 96KB
Seeeduino LoRaWAN Atmel SAM SAMD21G18A 48MHz 256KB 32KB
SensorTile.box ST STM32 STM32L4R9ZI 120MHz 2MB 640KB
Silicognition wESP32 Espressif 32 ESP32 240MHz 4MB 320KB
Sino:Bit Nordic nRF51 NRF51822 32MHz 256KB 32KB
Sipeed Longan Nano GigaDevice GD32V GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V GD32VF103C8T6 108MHz 64KB 20KB
Sipeed MAIX BiT Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 K210 400MHz 16MB 6MB
SparkFun 9DoF Razor IMU M0 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
SparkFun ESP32 Thing Espressif 32 ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 ESP32 240MHz 4MB 320KB
SparkFun Qwiic Micro Atmel SAM SAMD21E18A 48MHz 256KB 32KB
SparkFun RedBoard Turbo Atmel SAM SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Dev Breakout Atmel SAM SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Mini Breakout Atmel SAM SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Pro RF Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Sparky V1 F303 ST STM32 STM32F303CCT6 72MHz 256KB 40KB
TTGO LoRa32-OLED V1 Espressif 32 ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 ESP32 240MHz 4MB 320KB
Taida Century nRF52 mini board Nordic nRF52 NRF52832 64MHz 512KB 64KB
Teensy 3.1 / 3.2 Teensy MK20DX256 72MHz 256KB 64KB
Teensy 3.5 Teensy MK64FX512 120MHz 512KB 255.99KB
Teensy 3.6 Teensy MK66FX1M0 180MHz 1MB 256KB
Teensy 4.0 Teensy IMXRT1062 600MHz 1.94MB 512KB
Teensy 4.1 Teensy IMXRT1062 600MHz 7.75MB 512KB
Teensy LC Teensy MKL26Z64 48MHz 62KB 8KB
ThunderPack ST STM32 STM32L072KZ 32MHz 192KB 20KB
Tiny STM103T ST STM32 STM32F103TBU6 72MHz 128KB 20KB
Tuino 096 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
VAkE v1.0 ST STM32 STM32F446RET6 180MHz 512KB 128KB
VintLabs ESP32 Devkit Espressif 32 ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 ESP32 240MHz 4MB 320KB
Waveshare BLE400 Nordic nRF51 NRF51822 32MHz 256KB 32KB
WeMos D1 MINI ESP32 Espressif 32 ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 ESP32 240MHz 4MB 320KB
Wio Lite RISC-V GigaDevice GD32V GD32VF103CBT6 108MHz 128KB 32KB
Wraith V1 ESC ST STM32 STM32F051K6 48MHz 32KB 7.75KB
XinaBox CW02 Espressif 32 ESP32 240MHz 4MB 320KB
hackaBLE Nordic nRF52 NRF52832 64MHz 512KB 64KB
ng-beacon Nordic nRF51 NRF51822 16MHz 256KB 32KB
oddWires IoT-Bus Io Espressif 32 ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 ESP32 240MHz 4MB 320KB

  • Arduino for Atmel AVR
  • Arduino for Atmel megaAVR
  • Arduino for Atmel SAM
  • Arduino for Espressif 32
  • Arduino for Espressif 8266
  • Arduino for GigaDevice GD32V
  • Arduino for Infineon XMC
  • Arduino for Intel ARC32
  • Arduino for Kendryte K210
  • Arduino for Microchip PIC32
  • Arduino for Nordic nRF51
  • Arduino for Nordic nRF52
  • Arduino for ST STM32
  • Arduino for ST STM8
  • Arduino for Teensy
  • Arduino for TI MSP430
  • Arduino for TI TIVA

Name Description
Atmel AVR Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming
Atmel megaAVR 8-bit MCUs Built for Real-time Control with Core Independent Peripherals combining intelligent hardware peripherals along with the low-power capability of an AVR core, megaAVR microcontrollers (MCUs) broaden the effectiveness of your real-time control systems.
Atmel SAM Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Espressif 8266 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
GigaDevice GD32V The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.
Infineon XMC Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform
Intel ARC32 ARC embedded processors are a family of 32-bit CPUs that are widely used in SoC devices for storage, home, mobile, automotive, and Internet of Things applications.
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.
Microchip PIC32 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!
Nordic nRF51 The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.
Nordic nRF52 The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.
ST STM32 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.
ST STM8 The STM8 is an 8-bit microcontroller family by STMicroelectronics an extended variant of the ST7 microcontroller architecture. STM8 microcontrollers are particularly low cost for a full-featured 8-bit microcontroller.
Teensy Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.
TI MSP430 MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.
TI TIVA Texas Instruments TM4C12x MCUs offer the industrys most popular ARM Cortex-M4 core with scalable memory and package options, unparalleled connectivity peripherals, advanced application functions, industry-leading analog integration, and extensive software solutions.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



4D Systems

Name Platform Debug MCU Frequency Flash RAM
4D Systems PICadillo 35T Microchip PIC32 No 32MX795F512L 80MHz 508KB 128KB
4D Systems gen4 IoD Range Espressif 8266 No ESP8266 80MHz 512KB 80KB

AI Thinker

Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB

Name Platform Debug MCU Frequency Flash RAM
Adafruit Bluefruit Micro Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Bluefruit nRF52832 Feather Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Adafruit Circuit Playground Classic Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Circuit Playground Express Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Crickit M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Adafruit Feather 328P Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
Adafruit Feather 32u4 Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Feather Bluefruit Sense Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Adafruit Feather M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 Express Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Feather STM32F405 ST STM32 External STM32F405RGT6 168MHz 1MB 128KB
Adafruit Feather nRF52840 Express Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Adafruit Flora Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Gemma Atmel AVR On-board ATTINY85 8MHz 8KB 512B
Adafruit Gemma M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit Grand Central M4 Atmel SAM External SAMD51P20A 120MHz 1MB 256KB
Adafruit HUZZAH ESP8266 Espressif 8266 No ESP8266 80MHz 4MB 80KB
Adafruit Hallowing M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Hallowing M4 Atmel SAM External SAMD51J19A 120MHz 496KB 192KB
Adafruit ItsyBitsy 3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit ItsyBitsy 5V/16MHz Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Adafruit ItsyBitsy M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit ItsyBitsy M4 Atmel SAM External SAMD51G19A 120MHz 512KB 192KB
Adafruit MONSTER M4SK Atmel SAM External SAMD51G19A 120MHz 496KB 192KB
Adafruit Metro Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Adafruit Metro M0 Expresss Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Metro M4 Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Metro M4 AirLift Lite Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Pro Trinket 3V/12MHz (FTDI) Atmel AVR On-board ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 3V/12MHz (USB) Atmel AVR On-board ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (FTDI) Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (USB) Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Adafruit PyGamer Advance M4 Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit PyGamer M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit PyPortal M4 Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit PyPortal M4 Titano Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit Trellis M4 Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Trinket 3V/8MHz Atmel AVR On-board ATTINY85 8MHz 8KB 512B
Adafruit Trinket 5V/16MHz Atmel AVR On-board ATTINY85 16MHz 8KB 512B
Adafruit Trinket M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit pIRkey Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit pyBadge AirLift M4 Atmel SAM External SAMD51J20A 120MHz 1008KB 192KB
Adafruit pyBadge M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Circuit Playground Bluefruit Nordic nRF52 External NRF52840 64MHz 796KB 243KB
ItsyBitsy nRF52840 Express Nordic nRF52 On-board NRF52840 64MHz 796KB 243KB
Metro nRF52840 Express Nordic nRF52 External NRF52840 64MHz 796KB 243KB

Name Platform Debug MCU Frequency Flash RAM
AfroFlight Rev5 (8MHz) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
Wraith V1 ESC ST STM32 External STM32F051K6 48MHz 32KB 7.75KB

Name Platform Debug MCU Frequency Flash RAM
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB

Alorium Technology

Name Platform Debug MCU Frequency Flash RAM
Alorium Hinj Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Alorium Sno Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Alorium XLR8 Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
WiFi Slot Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Anarduino MiniWireless Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

April Brother

Name Platform Debug MCU Frequency Flash RAM
April Brother ESPea32 Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Arduboy Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduboy DevKit Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
Arduino BT ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino BT ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Arduino Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Duemilanove or Diecimila ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Duemilanove or Diecimila ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Esplora Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Ethernet Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Arduino Fio Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
Arduino Industrial 101 Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo ETH Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino LilyPad ATmega168 Atmel AVR On-board ATMEGA168 8MHz 14KB 1KB
Arduino LilyPad ATmega328 Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
Arduino LilyPad USB Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Arduino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Native USB Port) Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino MKR FOX 1200 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR GSM 1400 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR NB 1500 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1300 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1310 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WiFi 1010 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR1000 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKRZERO Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino Mega ADK Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Arduino Mega or Mega 2560 ATmega1280 Atmel AVR On-board ATMEGA1280 16MHz 124KB 8KB
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Arduino Micro Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Mini ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Mini ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Arduino NG or older ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino NG or older ATmega8 Atmel AVR On-board ATMEGA8 16MHz 7KB 1KB
Arduino Nano 33 BLE Nordic nRF52 External NRF52840 64MHz 960KB 256KB
Arduino Nano ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Nano ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Nano ATmega328 (New Bootloader) Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Nano Every Atmel megaAVR No ATMEGA4809 16MHz 47.50KB 6KB
Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) Atmel AVR On-board ATMEGA168 8MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Robot Control Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Robot Motor Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Tian Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino Uno Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Arduino Uno WiFi Rev2 Atmel megaAVR No ATMEGA4809 16MHz 47.50KB 6KB
Arduino Yun Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Yun Mini Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Zero (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (USB Native Port) Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
MKR Vidor 4000 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
NANO 33 IoT Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
3D Printer Controller ST STM32 External STM32F407VET6 168MHz 512KB 192KB

Name Platform Debug MCU Frequency Flash RAM
Atmel ATSAMW25-XPRO Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Generic ATtiny13 Atmel AVR On-board ATTINY13 1MHz 1KB 64B
Generic ATtiny13A Atmel AVR On-board ATTINY13A 1MHz 1KB 64B
Generic ATtiny1634 Atmel AVR No ATTINY1634 8MHz 16KB 1KB
Generic ATtiny167 Atmel AVR No ATTINY167 8MHz 16KB 512B
Generic ATtiny2313 Atmel AVR On-board ATTINY2313 8MHz 2KB 128B
Generic ATtiny24 Atmel AVR On-board ATTINY24 8MHz 2KB 128B
Generic ATtiny25 Atmel AVR On-board ATTINY25 8MHz 2KB 128B
Generic ATtiny261 Atmel AVR No ATTINY261 8MHz 2KB 128B
Generic ATtiny4313 Atmel AVR On-board ATTINY4313 8MHz 4KB 256B
Generic ATtiny43U Atmel AVR No ATTINY43U 8MHz 4KB 256B
Generic ATtiny44 Atmel AVR On-board ATTINY44 8MHz 4KB 256B
Generic ATtiny441 Atmel AVR No ATTINY441 8MHz 4KB 256B
Generic ATtiny45 Atmel AVR On-board ATTINY45 8MHz 4KB 256B
Generic ATtiny461 Atmel AVR No ATTINY461 8MHz 4KB 256B
Generic ATtiny48 Atmel AVR No ATTINY48 8MHz 4KB 256B
Generic ATtiny828 Atmel AVR No ATTINY828 8MHz 8KB 512B
Generic ATtiny84 Atmel AVR On-board ATTINY84 8MHz 8KB 512B
Generic ATtiny841 Atmel AVR No ATTINY841 8MHz 8KB 512B
Generic ATtiny85 Atmel AVR On-board ATTINY85 8MHz 8KB 512B
Generic ATtiny861 Atmel AVR No ATTINY861 8MHz 8KB 512B
Generic ATtiny87 Atmel AVR No ATTINY87 8MHz 8KB 512B
Generic ATtiny88 Atmel AVR No ATTINY88 8MHz 8KB 512B
USBasp stick Atmel AVR On-board ATMEGA8 12MHz 8KB 1KB

Name Platform Debug MCU Frequency Flash RAM
BBC micro:bit Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

Name Platform Debug MCU Frequency Flash RAM
HelvePic32 Microchip PIC32 No 32MX250F128B 48MHz 120KB 32KB
HelvePic32 Microchip PIC32 No 32MX250F128B 48MHz 120KB 32KB
HelvePic32 Microchip PIC32 No 32MX250F128D 48MHz 120KB 32KB
HelvePic32 MX270 Microchip PIC32 No 32MX270F256B 48MHz 244KB 62KB
HelvePic32 Robot Microchip PIC32 No 32MX270F256D 48MHz 244KB 62KB
HelvePic32 SMD MX270 Microchip PIC32 No 32MX270F256D 48MHz 244KB 62KB

BPI Tech

Name Platform Debug MCU Frequency Flash RAM
BPI-Bit Espressif 32 No ESP32 160MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
BQ ZUM BT-328 Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB

Name Platform Debug MCU Frequency Flash RAM
LoRa32u4II (868-915MHz) Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
BitWizard Raspduino Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB

Name Platform Debug MCU Frequency Flash RAM
BluzDK Nordic nRF51 External NRF51822 32MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Calliope mini Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

Name Platform Debug MCU Frequency Flash RAM
RGB Station Microchip PIC32 No 32MX270F256D 48MHz 240KB 62KB

Name Platform Debug MCU Frequency Flash RAM
Controllino Maxi Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Maxi Automation Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Mega Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Mini Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Delta DFBM-NQ620 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
DigiStump Oak Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Digilent Cerebot 32MX4 Microchip PIC32 No 32MX460F512L 80MHz 508KB 32KB
Digilent Cerebot 32MX7 Microchip PIC32 No 32MX795F512L 80MHz 508KB 128KB
Digilent OpenScope Microchip PIC32 No 32MZ2048EFG124 200MHz 1.98MB 512KB
Digilent chipKIT Cmod Microchip PIC32 No 32MX150F128D 40MHz 124KB 32KB
Digilent chipKIT DP32 Microchip PIC32 No 32MX250F128B 40MHz 120KB 32KB
Digilent chipKIT MAX32 Microchip PIC32 No 32MX795F512L 80MHz 508KB 128KB
Digilent chipKIT MX3 Microchip PIC32 No 32MX320F128H 80MHz 124KB 16KB
Digilent chipKIT Pro MX4 Microchip PIC32 No 32MX460F512L 80MHz 508KB 32KB
Digilent chipKIT Pro MX7 Microchip PIC32 No 32MX795F512L 80MHz 508KB 128KB
Digilent chipKIT UNO32 Microchip PIC32 No 32MX320F128H 80MHz 124KB 16KB
Digilent chipKIT WF32 Microchip PIC32 No 32MX695F512L 80MHz 508KB 128KB
Digilent chipKIT WiFire Microchip PIC32 No 32MZ2048ECG100 200MHz 1.98MB 512KB
Digilent chipKIT uC32 Microchip PIC32 No 32MX340F512H 80MHz 508KB 32KB
chipKIT WiFire rev. C Microchip PIC32 No 32MZ2048EFG100 200MHz 1.98MB 512KB

Name Platform Debug MCU Frequency Flash RAM
Digispark Pro Atmel AVR No ATTINY167 16MHz 14.50KB 512B
Digispark Pro (16 MHz) (64 byte buffer) Atmel AVR No ATTINY167 16MHz 14.50KB 512B
Digispark Pro (32 byte buffer) Atmel AVR No ATTINY167 16MHz 14.50KB 512B
Digispark USB Atmel AVR On-board ATTINY85 16MHz 5.87KB 512B
Digistump DigiX Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB

Name Platform Debug MCU Frequency Flash RAM
F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
ESP-Mx DevKit (ESP8285) Espressif 8266 No ESP8266 80MHz 1MB 80KB
ESPDuino (ESP-13 Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB

Dongsen Technology

Name Platform Debug MCU Frequency Flash RAM
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Dwenguino Atmel AVR No AT90USB646 16MHz 60KB 2KB

Name Platform Debug MCU Frequency Flash RAM
ESPectro Core Espressif 8266 No ESP8266 80MHz 4MB 80KB
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ESPresso Lite 1.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB
ESPresso Lite 2.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESPino Espressif 8266 No ESP8266 80MHz 4MB 80KB

Electronic SweetPeas

Name Platform Debug MCU Frequency Flash RAM
Electronic SweetPeas ESP320 Espressif 32 No ESP32 240MHz 4MB 320KB

Electronut Labs

Name Platform Debug MCU Frequency Flash RAM
Bluey nRF52832 IoT Nordic nRF52 External NRF52832 64MHz 512KB 64KB
hackaBLE Nordic nRF52 External NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
Elektor Uno R4 Atmel AVR No ATMEGA328PB 16MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
Engduino 3 Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
EnviroDIY Mayfly Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB

Name Platform Debug MCU Frequency Flash RAM
ESP-WROOM-02 Espressif 8266 No ESP8266 80MHz 2MB 80KB
ESP32 Pico Kit Espressif 32 No ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB
Espressif ESP8266 ESP-12E Espressif 8266 No ESP8266 80MHz 4MB 80KB
Espressif Generic ESP8266 ESP-01 1M Espressif 8266 No ESP8266 80MHz 1MB 80KB
Espressif Generic ESP8266 ESP-01 512k Espressif 8266 No ESP8266 80MHz 512KB 80KB
Espressif Generic ESP8266 ESP-07 Espressif 8266 No ESP8266 80MHz 4MB 80KB
Generic ESP8285 Module Espressif 8266 No ESP8266 80MHz 1MB 80KB
Phoenix 1.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB
Phoenix 2.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB
WifInfo Espressif 8266 No ESP8266 80MHz 1MB 80KB

Name Platform Debug MCU Frequency Flash RAM
FYSETC F6 V1.3 Atmel AVR On-board ATMEGA2560 16MHz 252KB 8KB

Name Platform Debug MCU Frequency Flash RAM
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Fubarino Mini Microchip PIC32 No 32MX250F128D 48MHz 120KB 32KB
Fubarino SD (1.5) Microchip PIC32 No 32MX795F512H 80MHz 508KB 128KB
Mini 2.0 Microchip PIC32 No 32MX270F256D 48MHz 240KB 62KB

Name Platform Debug MCU Frequency Flash RAM
BlackPill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
BluePill F103C6 ST STM32 External STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
Demo F030F4 ST STM32 External STM32F030F4P6 48MHz 16KB 4KB
FK407M1 ST STM32 External STM32F407VET6 168MHz 512KB 128KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 External STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 External STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 External STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 External STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 External STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 External STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 External STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 External STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 External STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 External STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 External STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 External STM32F103ZET6 72MHz 512KB 64KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 External STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 External STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 External STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) ST STM32 External STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) ST STM32 External STM32F407VGT6 168MHz 1MB 192KB
STM32F4Stamp F405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB

Name Platform Debug MCU Frequency Flash RAM
Tuino 096 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Tiny STM103T ST STM32 External STM32F103TBU6 72MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
ODROID-GO Espressif 32 No ESP32 240MHz 16MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Heltec Wifi kit 8 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Heltec Automation

Name Platform Debug MCU Frequency Flash RAM
Heltec WiFi Kit 32 Espressif 32 No ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Sonoff Basic Espressif 8266 No ESP8266 80MHz 1MB 80KB
Sonoff S20 Espressif 8266 No ESP8266 80MHz 1MB 80KB
Sonoff SV Espressif 8266 No ESP8266 80MHz 1MB 80KB
Sonoff TH Espressif 8266 No ESP8266 80MHz 1MB 80KB

Name Platform Debug MCU Frequency Flash RAM
XMC1100 Boot Kit Infineon XMC On-board XMC1100 32MHz 64KB 16KB
XMC1100 H-Bridge 2Go Infineon XMC On-board XMC1100 32MHz 64KB 16KB
XMC1100 XMC2Go Infineon XMC On-board XMC1100 32MHz 64KB 16KB
XMC1300 Boot Kit Infineon XMC On-board XMC1300 32MHz 64KB 16KB
XMC1300 Sense2GoL Infineon XMC On-board XMC1300 32MHz 32KB 16KB
XMC1400 Boot Kit Infineon XMC On-board XMC1400 48MHz 1.95MB 16KB
XMC4200 Distance2Go Infineon XMC On-board XMC4200 80MHz 256KB 40KB
XMC4700 Relax Kit Infineon XMC On-board XMC4700 144MHz 2.00MB 1.95MB

Name Platform Debug MCU Frequency Flash RAM
Arduino/Genuino 101 Intel ARC32 No ARCV2EM 32MHz 152KB 80KB

Name Platform Debug MCU Frequency Flash RAM
IntoRobot Fig Espressif 32 No ESP32 240MHz 4MB 320KB

Invent One

Name Platform Debug MCU Frequency Flash RAM
Invent One Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Maple ST STM32 External STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) ST STM32 External STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original ST STM32 External STM32F103CBT6 72MHz 108KB 17KB

Name Platform Debug MCU Frequency Flash RAM
LightUp Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
Linino One Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
LowPowerLab CurrentRanger Atmel SAM No SAMD21G18A 48MHz 256KB 32KB
LowPowerLab MightyHat Atmel AVR On-board ATMEGA328P 16MHz 31KB 2KB
LowPowerLab Moteino Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
LowPowerLab Moteino (8Mhz) Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
LowPowerLab MoteinoMEGA Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
Moteino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
M5Stack Core ESP32 Espressif 32 No ESP32 240MHz 4MB 320KB
M5Stack FIRE Espressif 32 No ESP32 240MHz 16MB 6.25MB
M5Stack GREY ESP32 Espressif 32 No ESP32 240MHz 16MB 520KB
M5Stick-C Espressif 32 No ESP32 240MHz 4MB 320KB

MH-ET Live

Name Platform Debug MCU Frequency Flash RAM
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Microsoft Azure IoT Development Kit (MXChip AZ3166) ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
MagicBit Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
MakerAsia Nano32 Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
DataStation Mini Microchip PIC32 No 32MX150F128C 40MHz 120KB 32KB

Name Platform Debug MCU Frequency Flash RAM
M200 V2 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
M300 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
Malyan M200 V1 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB

MediaTek Labs

Name Platform Debug MCU Frequency Flash RAM
LinkIt Smart 7688 Duo Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
AT90CAN128 Atmel AVR No AT90CAN128 16MHz 127KB 4KB
AT90CAN32 Atmel AVR No AT90CAN32 16MHz 31KB 2KB
AT90CAN64 Atmel AVR No AT90CAN64 16MHz 63KB 4KB
ATmega128/A Atmel AVR On-board ATMEGA128 16MHz 127KB 4KB
ATmega1280 Atmel AVR On-board ATMEGA1280 16MHz 127KB 8KB
ATmega1281 Atmel AVR On-board ATMEGA1281 16MHz 127KB 8KB
ATmega1284 Atmel AVR On-board ATMEGA1284 16MHz 127KB 16KB
ATmega1284P Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
ATmega16 Atmel AVR On-board ATMEGA16 16MHz 15.50KB 1KB
ATmega162 Atmel AVR No ATMEGA162 16MHz 15.50KB 1KB
ATmega164A Atmel AVR No ATMEGA164A 16MHz 15.50KB 1KB
ATmega164P/PA Atmel AVR On-board ATMEGA164P 16MHz 15.50KB 1KB
ATmega168/A Atmel AVR On-board ATMEGA168 16MHz 15.50KB 1KB
ATmega168P/PA Atmel AVR On-board ATMEGA168P 16MHz 15.50KB 1KB
ATmega168PB Atmel AVR No ATMEGA168PB 16MHz 15.50KB 1KB
ATmega2560 Atmel AVR On-board ATMEGA2560 16MHz 255KB 8KB
ATmega2561 Atmel AVR No ATMEGA2561 16MHz 255KB 8KB
ATmega32 Atmel AVR No ATMEGA32 16MHz 31.50KB 2KB
ATmega324A Atmel AVR On-board ATMEGA324A 16MHz 31.50KB 2KB
ATmega324P Atmel AVR On-board ATMEGA324P 16MHz 31.50KB 2KB
ATmega324PA Atmel AVR On-board ATMEGA324PA 16MHz 31.50KB 2KB
ATmega324PB Atmel AVR No ATMEGA324PB 16MHz 31.50KB 2KB
ATmega328 Atmel AVR On-board ATMEGA328 16MHz 31.50KB 2KB
ATmega328P/PA Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
ATmega328PB Atmel AVR No ATMEGA328PB 16MHz 31.50KB 2KB
ATmega48/A Atmel AVR On-board ATMEGA48 16MHz 4KB 512B
ATmega48PB Atmel AVR No ATMEGA48PB 16MHz 4KB 512B
ATmega64/A Atmel AVR No ATMEGA64 16MHz 63KB 4KB
ATmega640 Atmel AVR No ATMEGA640 16MHz 63KB 8KB
ATmega644/A Atmel AVR No ATMEGA644A 16MHz 63KB 4KB
ATmega644P/PA Atmel AVR On-board ATMEGA644P 16MHz 63KB 4KB
ATmega8/A Atmel AVR On-board ATMEGA8 16MHz 7.50KB 1KB
ATmega8515 Atmel AVR No ATMEGA8515 16MHz 7.50KB 512B
ATmega8535 Atmel AVR No ATMEGA8535 16MHz 7.50KB 512B
ATmega88/A Atmel AVR On-board ATMEGA88 16MHz 7.50KB 1KB
ATmega88P/PA Atmel AVR On-board ATMEGA88P 16MHz 7.50KB 1KB
ATmega88PB Atmel AVR No ATMEGA88PB 16MHz 7.50KB 1KB
ATmega8P/PA Atmel AVR On-board ATMEGA48P 16MHz 4KB 512B

Name Platform Debug MCU Frequency Flash RAM
Microduino Core (Atmega168PA@16M,5V) Atmel AVR On-board ATMEGA168P 16MHz 15.50KB 1KB
Microduino Core (Atmega168PA@8M,3.3V) Atmel AVR On-board ATMEGA168P 8MHz 15.50KB 1KB
Microduino Core (Atmega328P@16M,5V) Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Microduino Core (Atmega328P@8M,3.3V) Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
Microduino Core ESP32 Espressif 32 No ESP32 240MHz 4MB 320KB
Microduino Core STM32 to Flash ST STM32 External STM32F103CBT6 72MHz 105.47KB 16.60KB
Microduino Core USB (ATmega32U4@16M,5V) Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Microduino Core+ (ATmega1284P@16M,5V) Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
Microduino Core+ (ATmega1284P@8M,3.3V) Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
Microduino Core+ (Atmega644PA@16M,5V) Atmel AVR On-board ATMEGA644P 16MHz 63KB 4KB
Microduino Core+ (Atmega644PA@8M,3.3V) Atmel AVR On-board ATMEGA644P 8MHz 63KB 4KB

Name Platform Debug MCU Frequency Flash RAM
MKR Sharky ST STM32 External STM32WB55CG 64MHz 512KB 192.00KB

Name Platform Debug MCU Frequency Flash RAM
MikroElektronika Clicker 2 Microchip PIC32 No 32MX460F512L 80MHz 508KB 32KB
MikroElektronika Flip N Click MZ Microchip PIC32 No 32MZ2048EFH100 252MHz 1.98MB 512KB

Name Platform Debug MCU Frequency Flash RAM
N2+ ST STM32 External STM32F405RGT6 168MHz 1MB 192KB

Name Platform Debug MCU Frequency Flash RAM
NodeMCU 0.9 (ESP-12 Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB
NodeMCU 1.0 (ESP-12E Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Noduino Quantum Espressif 32 No ESP32 240MHz 16MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Nordic Beacon Kit (PCA20006) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF51 Dongle (PCA10031) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Nordic nRF52840-DK (Adafruit BSP) Nordic nRF52 On-board NRF52840 64MHz 796KB 243KB

Name Platform Debug MCU Frequency Flash RAM
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-PRO Espressif 32 No ESP32 240MHz 4MB 320KB
OLIMEX ESP32-PoE Espressif 32 No ESP32 240MHz 4MB 320KB
OLIMEX ESP32-PoE-ISO Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
OROCA EduBot Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
OSHChip Nordic nRF51 External NRF51822 32MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
OLIMEXINO-STM32 ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
Olimex MOD-WIFI-ESP8266(-DEV) Espressif 8266 No ESP8266 80MHz 2MB 80KB
Olimex PIC32-PINGUINO Microchip PIC32 No 32MX440F256H 80MHz 252KB 32KB
STM32-E407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
Onehorse ESP32 Dev Module Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
OpenBCI 32bit Microchip PIC32 No 32MX250F128B 40MHz 120KB 32KB

Name Platform Debug MCU Frequency Flash RAM
OpenEnergyMonitor emonPi Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB

Name Platform Debug MCU Frequency Flash RAM
PONTECH UAV100 Microchip PIC32 No 32MX440F512H 80MHz 508KB 32KB

Name Platform Debug MCU Frequency Flash RAM
PanStamp AVR Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
Particle Xenon Nordic nRF52 External NRF52840 64MHz 796KB 243KB

Name Platform Debug MCU Frequency Flash RAM
Piconomix PX-HER0 ST STM32 External STM32L072RB 32MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
Pinoccio Scout Atmel AVR No ATMEGA256RFR2 16MHz 248KB 32KB

Pololu Corporation

Name Platform Debug MCU Frequency Flash RAM
Pololu A-Star 32U4 Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
Pontech NoFire Microchip PIC32 No 32MZ2048EFG100 200MHz 1.98MB 512KB
Pontech Quick240 Microchip PIC32 No 32MX795F512L 80MHz 508KB 128KB

Name Platform Debug MCU Frequency Flash RAM
PrntrBoard V2 ST STM32 External STM32F407RE 168MHz 512KB 192KB

Prusa 3D

Name Platform Debug MCU Frequency Flash RAM
Original Prusa i3 MK3 Multi Material 2.0 Upgrade Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Prusa RAMBo Atmel AVR On-board ATMEGA2560 16MHz 252KB 8KB

Punch Through

Name Platform Debug MCU Frequency Flash RAM
LightBlue Bean Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
LightBlue Bean+ Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

Pycom Ltd.

Name Platform Debug MCU Frequency Flash RAM
Pycom GPy Espressif 32 No ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB

Qmobot LLP

Name Platform Debug MCU Frequency Flash RAM
Qchip Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Quirkbot Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 16KB
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 32KB

Name Platform Debug MCU Frequency Flash RAM
3D Printer control board ST STM32 External STM32F446RET6 180MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
RedBearLab BLE Nano 1.5 Nordic nRF51 On-board NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab Blend Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab Blend Micro 3.3V/16MHz (overclock) Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend Micro 3.3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
RedBearLab nRF51822 Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

Name Platform Debug MCU Frequency Flash RAM
3D printer controller ST STM32 On-board STM32F765VIT6 216MHz 2MB 512KB

Name Platform Debug MCU Frequency Flash RAM
RepRap RAMBo Atmel AVR On-board ATMEGA2560 16MHz 252KB 8KB

Name Platform Debug MCU Frequency Flash RAM
Minitronics v2.0 Atmel SAM External SAMD21J18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
BlackPill F303CC ST STM32 External STM32F303CCT6 72MHz 256KB 40KB

Name Platform Debug MCU Frequency Flash RAM
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
SODAQ Autonomo Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ ExpLoRer Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ GaLoRa Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ Mbili Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ Moja Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
SODAQ Ndogo Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ ONE Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SODAQ SARA Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ SFF Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SODAQ Tatu Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB

Name Platform Debug MCU Frequency Flash RAM
3DP001V1 Evaluation board for 3D printer ST STM32 On-board STM32F401VGT6 84MHz 512KB 96KB
Black STM32F407VE ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F401CC ST STM32 External STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Core board F401RCT6 ST STM32 External STM32F401RCT6 84MHz 256KB 64KB
Nucleo G071RB ST STM32 External STM32G071RBT6 64MHz 128KB 36KB
Nucleo G431KB ST STM32 External STM32G431KBT6 170MHz 128KB 32KB
Nucleo G431RB ST STM32 External STM32G431RBT6 170MHz 128KB 32KB
Nucleo G474RE ST STM32 External STM32G474RET6 170MHz 512KB 128KB
P-Nucleo WB55RG ST STM32 On-board STM32WB55RG 64MHz 512KB 192.00KB
RHF76 052 ST STM32 External STM32L051C8T6 32MHz 64KB 8KB
ST 32F746GDISCOVERY ST STM32 On-board STM32F746NGH6 216MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 On-board STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 On-board STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F091RC ST STM32 On-board STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 On-board STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 On-board STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 On-board STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 ST STM32 On-board STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE ST STM32 On-board STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F401RE ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F411RE ST STM32 On-board STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 On-board STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F767ZI ST STM32 On-board STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI ST STM32 On-board STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L031K6 ST STM32 On-board STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 ST STM32 On-board STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 On-board STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE ST STM32 On-board STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L412KB ST STM32 On-board STM32L412KBU6 80MHz 128KB 40KB
ST Nucleo L432KC ST STM32 On-board STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L452RE ST STM32 On-board STM32L452RET6 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 On-board STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P ST STM32 On-board STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI ST STM32 On-board STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32VLDISCOVERY ST STM32 On-board STM32F100RBT6 24MHz 128KB 8KB
ST STM8S-DISCOVERY ST STM8 On-board STM8S105C6T6 16MHz 32KB 2KB
ST STM8S103F3 Breakout Board ST STM8 No STM8S103F3P6 16MHz 8KB 1KB
ST STM8S105K4T6 Breakout Board ST STM8 No STM8S105K4T6 16MHz 16KB 2KB
SensorTile.box ST STM32 External STM32L4R9ZI 120MHz 2MB 640KB

Name Platform Debug MCU Frequency Flash RAM
SainSmart Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
SainSmart Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB

Name Platform Debug MCU Frequency Flash RAM
Sanguino ATmega1284p (16MHz) Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
Sanguino ATmega1284p (8MHz) Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
Sanguino ATmega644 or ATmega644A (16 MHz) Atmel AVR On-board ATMEGA644 16MHz 63KB 4KB
Sanguino ATmega644 or ATmega644A (8 MHz) Atmel AVR On-board ATMEGA644 8MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (16 MHz) Atmel AVR On-board ATMEGA644P 16MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (8 MHz) Atmel AVR On-board ATMEGA644P 8MHz 63KB 4KB

Name Platform Debug MCU Frequency Flash RAM
Schirmilabs Eduino WiFi Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Seeeduino LoRaWAN Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Seeed Tiny BLE Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
SeeedStudio CUI32stem Microchip PIC32 No 32MX795F512H 80MHz 508KB 128KB
Seeeduino Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Wio Link Espressif 8266 No ESP8266 80MHz 4MB 80KB
Wio Lite RISC-V GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Wio Node Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
GD32VF103V-EVAL GigaDevice GD32V External GD32VF103VBT6 108MHz 128KB 32KB
Sipeed Longan Nano GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V External GD32VF103C8T6 108MHz 64KB 20KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB

Name Platform Debug MCU Frequency Flash RAM
Pic32 CUI32-Development Stick Microchip PIC32 No 32MX440F512H 80MHz 508KB 32KB
SparkFun 9DoF Razor IMU M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun ATmega128RFA1 Dev Board Atmel AVR On-board ATMEGA128RFA1 16MHz 16KB 124KB
SparkFun Blynk Board Espressif 8266 No ESP8266 80MHz 4MB 80KB
SparkFun Digital Sandbox Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
SparkFun ESP8266 Thing Espressif 8266 No ESP8266 80MHz 512KB 80KB
SparkFun ESP8266 Thing Dev Espressif 8266 No ESP8266 80MHz 512KB 80KB
SparkFun Fio V3 3.3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun Makey Makey Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Mega Pro 3.3V/8MHz Atmel AVR On-board ATMEGA2560 8MHz 252KB 8KB
SparkFun Mega Pro 5V/16MHz Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
SparkFun Mega Pro Mini 3.3V Atmel AVR On-board ATMEGA2560 8MHz 252KB 8KB
SparkFun MicroView Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
SparkFun Pro Micro 3.3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Pro Micro 5V/16MHz Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Qduino Mini Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Qwiic Micro Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
SparkFun RedBoard Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
SparkFun RedBoard Turbo Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Dev Breakout Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Mini Breakout Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Pro RF Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun Serial 7-Segment Display Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB

SparkFun Electronics

Name Platform Debug MCU Frequency Flash RAM
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
SpellFoundry Sleepy Pi 2 Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB

Name Platform Debug MCU Frequency Flash RAM
SweetPea ESP-210 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
TI FraunchPad MSP-EXP430FR5739LP TI MSP430 On-board MSP430FR5739 16MHz 15.37KB 1KB
TI LaunchPad (Stellaris) w/ lm4f120 (80MHz) TI TIVA On-board LPLM4F120H5QR 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c123 (80MHz) TI TIVA On-board LPTM4C1230C3PM 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c129 (120MHz) TI TIVA On-board LPTM4C1294NCPDT 120MHz 1MB 256KB
TI LaunchPad MSP-EXP430F5529LP TI MSP430 On-board MSP430F5529 25MHz 47KB 8KB
TI LaunchPad MSP-EXP430FR2311LP TI MSP430 On-board MSP430FR2311 16MHz 3.75KB 1KB
TI LaunchPad MSP-EXP430FR2433LP TI MSP430 On-board MSP430FR2433 8MHz 15KB 4KB
TI LaunchPad MSP-EXP430FR4133LP TI MSP430 On-board MSP430FR4133 8MHz 15KB 2KB
TI LaunchPad MSP-EXP430FR5969LP TI MSP430 On-board MSP430FR5969 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430FR5994LP TI MSP430 On-board MSP430FR5994 16MHz 256KB 4KB
TI LaunchPad MSP-EXP430FR6989LP TI MSP430 On-board MSP430FR6989 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430G2 w/ MSP430G2231 TI MSP430 On-board MSP430G2231 1MHz 2KB 256B
TI LaunchPad MSP-EXP430G2 w/ MSP430G2452 TI MSP430 On-board MSP430G2452 16MHz 8KB 256B
TI LaunchPad MSP-EXP430G2553LP TI MSP430 On-board MSP430G2553 16MHz 16KB 512B

Name Platform Debug MCU Frequency Flash RAM
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T-Watch Espressif 32 No ESP32 240MHz 16MB 320KB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB

Taida Century

Name Platform Debug MCU Frequency Flash RAM
Taida Century nRF52 mini board Nordic nRF52 External NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
Sparky V1 F303 ST STM32 External STM32F303CCT6 72MHz 256KB 40KB

Name Platform Debug MCU Frequency Flash RAM
Teensy 2.0 Teensy No ATMEGA32U4 16MHz 31.50KB 2.50KB
Teensy 3.0 Teensy No MK20DX128 48MHz 128KB 16KB
Teensy 3.1 / 3.2 Teensy External MK20DX256 72MHz 256KB 64KB
Teensy 3.5 Teensy External MK64FX512 120MHz 512KB 255.99KB
Teensy 3.6 Teensy External MK66FX1M0 180MHz 1MB 256KB
Teensy 4.0 Teensy External IMXRT1062 600MHz 1.94MB 512KB
Teensy 4.1 Teensy External IMXRT1062 600MHz 7.75MB 512KB
Teensy LC Teensy External MKL26Z64 48MHz 62KB 8KB
Teensy++ 2.0 Teensy No AT90USB1286 16MHz 127KB 8KB

Name Platform Debug MCU Frequency Flash RAM
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB
ThaiEasyElec ESPino Espressif 8266 No ESP8266 80MHz 4MB 80KB

The Things Network

Name Platform Debug MCU Frequency Flash RAM
The Things Uno Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
ThunderPack ST STM32 External STM32L072KZ 32MHz 192KB 20KB

Till Harbaum

Name Platform Debug MCU Frequency Flash RAM
ftDuino Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
TinyCircuits TinyDuino Processor Board Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
TinyCircuits TinyLily Mini Processor Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB

Name Platform Debug MCU Frequency Flash RAM
TinyPICO Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Turta IoT Node Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
UBW32 MX460 Microchip PIC32 No 32MX460F512L 80MHz 508KB 32KB
UBW32 MX795 Microchip PIC32 No 32MX795F512L 80MHz 508KB 128KB

Name Platform Debug MCU Frequency Flash RAM
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
VAkE v1.0 ST STM32 External STM32F446RET6 180MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
WEMOS D1 R1 Espressif 8266 No ESP8266 80MHz 4MB 80KB
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 R2 and mini Espressif 8266 No ESP8266 80MHz 4MB 80KB
WeMos D1 mini Lite Espressif 8266 No ESP8266 80MHz 1MB 80KB
WeMos D1 mini Pro Espressif 8266 No ESP8266 80MHz 16MB 80KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Waveshare BLE400 Nordic nRF51 External NRF51822 32MHz 256KB 32KB

Wicked Device

Name Platform Debug MCU Frequency Flash RAM
Wicked Device WildFire V2 Atmel AVR On-board ATMEGA1284P 16MHz 120.00KB 16KB
Wicked Device WildFire V3 Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB

Name Platform Debug MCU Frequency Flash RAM
Widora AIR Espressif 32 No ESP32 240MHz 16MB 320KB

Name Platform Debug MCU Frequency Flash RAM
WiFiduino Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Talk2 Whisper Node Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
XinaBox CW01 Espressif 8266 No ESP8266 80MHz 4MB 80KB
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
chipKIT Lenny Microchip PIC32 No 32MX270F256D 40MHz 120KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Element14 chipKIT Pi Microchip PIC32 No 32MX250F128B 40MHz 120KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Altair Atmel AVR No ATMEGA256RFR2 16MHz 248KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki ABC (MBC-WB) - Samd21 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - Samd21 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
ng-beacon Nordic nRF51 External NRF51822 16MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
nicai-systems BOB3 coding bot Atmel AVR On-board ATMEGA88 8MHz 8KB 1KB
nicai-systems NIBO 2 robot Atmel AVR On-board ATMEGA128 16MHz 128KB 4KB
nicai-systems NIBO burger robot Atmel AVR On-board ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBO burger robot with Tuning Kit Atmel AVR On-board ATMEGA1284P 20MHz 128KB 16KB
nicai-systems NIBObee robot Atmel AVR On-board ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBObee robot with Tuning Kit Atmel AVR On-board ATMEGA1284P 20MHz 128KB 16KB

Name Platform Debug MCU Frequency Flash RAM
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
sduino MB (STM8S208MBT6B) ST STM8 No STM8S208MBT6 16MHz 128KB 6KB
sduino UNO (STM8S105K6) ST STM8 No STM8S105K6T6 16MHz 32KB 2KB

Name Platform Debug MCU Frequency Flash RAM
Sino:Bit Nordic nRF51 External NRF51822 32MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
u-blox EVK-NINA-B1 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
u-blox NINA-W10 series Espressif 32 No ESP32 240MHz 2MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ubIQio Ardhat Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

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.

For more detailed information please visit vendor site.

  • Debugging
  • Examples
  • Platforms
  • Boards

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
Armstrap Eagle 1024 ST STM32 STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 ST STM32 STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 ST STM32 STM32F407VET6 168MHz 512KB 192KB
RushUp Cloud-JAM ST STM32 STM32F401RET6 84MHz 512KB 96KB
ST 32F411EDISCOVERY ST STM32 STM32F411VET6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 STM32F469NIH6 180MHz 1MB 384KB
ST Nucleo F401RE ST STM32 STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F446ZE ST STM32 STM32F446ZET6 180MHz 512KB 128KB
ST STM32F3DISCOVERY ST STM32 STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 STM32F407VGT6 168MHz 1MB 128KB
ST STM32LDISCOVERY ST STM32 STM32L152RBT6 32MHz 128KB 16KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
1Bitsy ST STM32 STM32F415RGT 168MHz 1MB 128KB
3D Printer Controller ST STM32 STM32F407VET6 168MHz 512KB 192KB
Adafruit Feather STM32F405 ST STM32 STM32F405RGT6 168MHz 1MB 128KB
AfroFlight Rev5 (8MHz) ST STM32 STM32F103CBT6 72MHz 128KB 20KB
Black STM32F407VE ST STM32 STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG ST STM32 STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 STM32F103C8T6 72MHz 128KB 20KB
BlackPill F401CC ST STM32 STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini ST STM32 STM32F407VET6 168MHz 512KB 128KB
BluePill F103C6 ST STM32 STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 STM32F103C8T6 72MHz 128KB 20KB
Core board F401RCT6 ST STM32 STM32F401RCT6 84MHz 256KB 64KB
F407VG ST STM32 STM32F407VGT6 168MHz 512KB 128KB
FK407M1 ST STM32 STM32F407VET6 168MHz 512KB 128KB
M200 V2 ST STM32 STM32F070CBT6 48MHz 120KB 14.81KB
M300 ST STM32 STM32F070CBT6 48MHz 120KB 14.81KB
Piconomix PX-HER0 ST STM32 STM32L072RB 32MHz 128KB 20KB
PrntrBoard V2 ST STM32 STM32F407RE 168MHz 512KB 192KB
RHF76 052 ST STM32 STM32L051C8T6 32MHz 64KB 8KB
STM32-E407 ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
STM3210C-EVAL ST STM32 STM32F107VCT6 72MHz 256KB 64KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 STM32F103ZET6 72MHz 512KB 64KB
STM32F303CB (32k RAM. 128k Flash) ST STM32 STM32F303CBT6 72MHz 128KB 32KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) ST STM32 STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) ST STM32 STM32F407VGT6 168MHz 1MB 192KB
ThunderPack ST STM32 STM32L072KZ 32MHz 192KB 20KB
Wraith V1 ESC ST STM32 STM32F051K6 48MHz 32KB 7.75KB

•
CMSIS for ST STM32

Name Description
ST STM32 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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
1Bitsy ST STM32 External STM32F415RGT 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
Adafruit Feather STM32F405 ST STM32 External STM32F405RGT6 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
AfroFlight Rev5 (8MHz) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
Wraith V1 ESC ST STM32 External STM32F051K6 48MHz 32KB 7.75KB

Name Platform Debug MCU Frequency Flash RAM
3D Printer Controller ST STM32 External STM32F407VET6 168MHz 512KB 192KB

Name Platform Debug MCU Frequency Flash RAM
Armstrap Eagle 1024 ST STM32 On-board STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 ST STM32 On-board STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB

Name Platform Debug MCU Frequency Flash RAM
F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
BlackPill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
BluePill F103C6 ST STM32 External STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
FK407M1 ST STM32 External STM32F407VET6 168MHz 512KB 128KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 External STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 External STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 External STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 External STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 External STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 External STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 External STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 External STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 External STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 External STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 External STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 External STM32F103ZET6 72MHz 512KB 64KB
STM32F303CB (32k RAM. 128k Flash) ST STM32 External STM32F303CBT6 72MHz 128KB 32KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 External STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 External STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 External STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) ST STM32 External STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) ST STM32 External STM32F407VGT6 168MHz 1MB 192KB

Name Platform Debug MCU Frequency Flash RAM
M200 V2 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
M300 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB

Name Platform Debug MCU Frequency Flash RAM
STM32-E407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
Piconomix PX-HER0 ST STM32 External STM32L072RB 32MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
PrntrBoard V2 ST STM32 External STM32F407RE 168MHz 512KB 192KB

Name Platform Debug MCU Frequency Flash RAM
RushUp Cloud-JAM ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB

Name Platform Debug MCU Frequency Flash RAM
Black STM32F407VE ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F401CC ST STM32 External STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Core board F401RCT6 ST STM32 External STM32F401RCT6 84MHz 256KB 64KB
RHF76 052 ST STM32 External STM32L051C8T6 32MHz 64KB 8KB
ST 32F411EDISCOVERY ST STM32 On-board STM32F411VET6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 On-board STM32F469NIH6 180MHz 1MB 384KB
ST Nucleo F401RE ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F446ZE ST STM32 On-board STM32F446ZET6 180MHz 512KB 128KB
ST STM32F3DISCOVERY ST STM32 On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32LDISCOVERY ST STM32 On-board STM32L152RBT6 32MHz 128KB 16KB
STM3210C-EVAL ST STM32 External STM32F107VCT6 72MHz 256KB 64KB

Name Platform Debug MCU Frequency Flash RAM
ThunderPack ST STM32 External STM32L072KZ 32MHz 192KB 20KB

framework = esp8266-nonos-sdk

The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.

For more detailed information please visit vendor site.

  • Examples
  • Platforms
  • Boards

•
ESP8266 Non-OS SDK for Espressif 8266

Name Description
Espressif 8266 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



4D Systems

Name Platform Debug MCU Frequency Flash RAM
4D Systems gen4 IoD Range Espressif 8266 No ESP8266 80MHz 512KB 80KB

Name Platform Debug MCU Frequency Flash RAM
Adafruit HUZZAH ESP8266 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
WiFi Slot Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESP-Mx DevKit (ESP8285) Espressif 8266 No ESP8266 80MHz 1MB 80KB
ESPDuino (ESP-13 Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESPectro Core Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESPresso Lite 1.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB
ESPresso Lite 2.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESPino Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESP-WROOM-02 Espressif 8266 No ESP8266 80MHz 2MB 80KB
Espressif ESP8266 ESP-12E Espressif 8266 No ESP8266 80MHz 4MB 80KB
Espressif Generic ESP8266 ESP-01 1M Espressif 8266 No ESP8266 80MHz 1MB 80KB
Espressif Generic ESP8266 ESP-01 512k Espressif 8266 No ESP8266 80MHz 512KB 80KB
Espressif Generic ESP8266 ESP-07 Espressif 8266 No ESP8266 80MHz 4MB 80KB
Generic ESP8285 Module Espressif 8266 No ESP8266 80MHz 1MB 80KB
Phoenix 1.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB
Phoenix 2.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB
WifInfo Espressif 8266 No ESP8266 80MHz 1MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Heltec Wifi kit 8 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Sonoff Basic Espressif 8266 No ESP8266 80MHz 1MB 80KB
Sonoff S20 Espressif 8266 No ESP8266 80MHz 1MB 80KB
Sonoff SV Espressif 8266 No ESP8266 80MHz 1MB 80KB
Sonoff TH Espressif 8266 No ESP8266 80MHz 1MB 80KB

Invent One

Name Platform Debug MCU Frequency Flash RAM
Invent One Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
NodeMCU 0.9 (ESP-12 Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB
NodeMCU 1.0 (ESP-12E Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Olimex MOD-WIFI-ESP8266(-DEV) Espressif 8266 No ESP8266 80MHz 2MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Schirmilabs Eduino WiFi Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Wio Link Espressif 8266 No ESP8266 80MHz 4MB 80KB
Wio Node Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
SparkFun Blynk Board Espressif 8266 No ESP8266 80MHz 4MB 80KB
SparkFun ESP8266 Thing Espressif 8266 No ESP8266 80MHz 512KB 80KB
SparkFun ESP8266 Thing Dev Espressif 8266 No ESP8266 80MHz 512KB 80KB

Name Platform Debug MCU Frequency Flash RAM
SweetPea ESP-210 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ThaiEasyElec ESPino Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
WEMOS D1 R1 Espressif 8266 No ESP8266 80MHz 4MB 80KB
WeMos D1 R2 and mini Espressif 8266 No ESP8266 80MHz 4MB 80KB
WeMos D1 mini Pro Espressif 8266 No ESP8266 80MHz 16MB 80KB

Name Platform Debug MCU Frequency Flash RAM
WiFiduino Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
XinaBox CW01 Espressif 8266 No ESP8266 80MHz 4MB 80KB

framework = esp8266-rtos-sdk

ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

For more detailed information please visit vendor site.

  • Examples
  • Platforms
  • Boards

•
ESP8266 RTOS SDK for Espressif 8266

Name Description
Espressif 8266 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



4D Systems

Name Platform Debug MCU Frequency Flash RAM
4D Systems gen4 IoD Range Espressif 8266 No ESP8266 80MHz 512KB 80KB

Name Platform Debug MCU Frequency Flash RAM
Adafruit HUZZAH ESP8266 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
WiFi Slot Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESP-Mx DevKit (ESP8285) Espressif 8266 No ESP8266 80MHz 1MB 80KB
ESPDuino (ESP-13 Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESPectro Core Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESPresso Lite 1.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB
ESPresso Lite 2.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESPino Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ESP-WROOM-02 Espressif 8266 No ESP8266 80MHz 2MB 80KB
Espressif ESP8266 ESP-12E Espressif 8266 No ESP8266 80MHz 4MB 80KB
Espressif Generic ESP8266 ESP-01 1M Espressif 8266 No ESP8266 80MHz 1MB 80KB
Espressif Generic ESP8266 ESP-01 512k Espressif 8266 No ESP8266 80MHz 512KB 80KB
Espressif Generic ESP8266 ESP-07 Espressif 8266 No ESP8266 80MHz 4MB 80KB
Generic ESP8285 Module Espressif 8266 No ESP8266 80MHz 1MB 80KB
Phoenix 1.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB
Phoenix 2.0 Espressif 8266 No ESP8266 80MHz 4MB 80KB
WifInfo Espressif 8266 No ESP8266 80MHz 1MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Heltec Wifi kit 8 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Sonoff Basic Espressif 8266 No ESP8266 80MHz 1MB 80KB
Sonoff S20 Espressif 8266 No ESP8266 80MHz 1MB 80KB
Sonoff SV Espressif 8266 No ESP8266 80MHz 1MB 80KB
Sonoff TH Espressif 8266 No ESP8266 80MHz 1MB 80KB

Invent One

Name Platform Debug MCU Frequency Flash RAM
Invent One Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
NodeMCU 0.9 (ESP-12 Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB
NodeMCU 1.0 (ESP-12E Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Olimex MOD-WIFI-ESP8266(-DEV) Espressif 8266 No ESP8266 80MHz 2MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Schirmilabs Eduino WiFi Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Wio Link Espressif 8266 No ESP8266 80MHz 4MB 80KB
Wio Node Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
SparkFun Blynk Board Espressif 8266 No ESP8266 80MHz 4MB 80KB
SparkFun ESP8266 Thing Espressif 8266 No ESP8266 80MHz 512KB 80KB
SparkFun ESP8266 Thing Dev Espressif 8266 No ESP8266 80MHz 512KB 80KB

Name Platform Debug MCU Frequency Flash RAM
SweetPea ESP-210 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
ThaiEasyElec ESPino Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
WEMOS D1 R1 Espressif 8266 No ESP8266 80MHz 4MB 80KB
WeMos D1 R2 and mini Espressif 8266 No ESP8266 80MHz 4MB 80KB
WeMos D1 mini Pro Espressif 8266 No ESP8266 80MHz 16MB 80KB

Name Platform Debug MCU Frequency Flash RAM
WiFiduino Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
XinaBox CW01 Espressif 8266 No ESP8266 80MHz 4MB 80KB

framework = espidf

Espressif IoT Development Framework. Official development framework for ESP32.

For more detailed information please visit vendor site.

  • Tutorials
  • Configuration
  • Debugging
  • Examples
  • Platforms
  • Boards

•
Get started with ESP-IDF and ESP32-DevKitC: debugging, unit testing, project analysis

NOTE:

Starting with ESP-IDF v4.0, a CMake-based build system is used. Different configuration steps are required for ESP-IDF v3.x due to a legacy build system based on GNU Make.


  • Configuration for 4.0
  • Configuration for 3.0, 3.1, 3.2, 3.3

Each release of Espressif 32 platform uses a specific version of ESP-IDF. The latest version of the platform only supports the latest stable version of the framework.

WARNING:

ESP-IDF v4.0 projects are not backwards-compatible with ESP-IDF v3.x projects in terms of project configuration process.


  • Project Structure
  • ESP-IDF components
  • ULP coprocessor programming
  • Limitations

The general project configuration (default optimization level, bootloader configuration partition tables, etc) is set in a single file called sdkconfig in the root folder of the project. This configuration file can be modified via a special target called menuconfig (PlatformIO v4.3.0 greater is required):

platformio run -t menuconfig


WARNING:

ESP-IDF requires some extra tools to be installed in your system in order to build firmware for supported chips. Most of these tools are available in PlatformIO ecosystem as standalone packages, but in order to use configuration tool called menuconfig several additional packages need to be installed on Linux-based systems: 

libncurses5-dev flex bison


More details about required packages can be found in the official ESP-IDF documentation - Standard Setup of Toolchain for Linux.



Project Structure

The ESP-IDF framework requires an unusual project structure because most of the framework configuration is performed by the native for the ESP-IDF build system called CMake.

A typical PlatformIO project for the ESP-IDF framework must have the following structure:

project_dir
├── include
├── src
│    ├── CMakeLists.txt
│    └── main.c
├── CMakeLists.txt
└── platformio.ini


TIP:

It's also possible to use the default ESP-IDF project structure with main folder. To specify main as the folder with source files use src_dir option, for example: 

[platformio]
src_dir = main
[env:esp32dev]
platform = espressif32
framework = espidf
board = esp32dev




Besides the files related to PlatformIO project, there are several additional ESP-IDF-specific files: the main CMakeLists.txt, project-specific CMakeLists.txt in src_dir and optional default configuration file sdkconfig.defaults. CMakeLists.txt files enable features supported by the ESP-IDF's build system, e.g. ULP configuration, adding extra components, etc. A typical CMakeLists.txt file in the root folder has the following content:

# The following lines of boilerplate have to be in your project's CMakeLists
# in this exact order for cmake to work correctly
cmake_minimum_required(VERSION 3.16.0)
include($ENV{IDF_PATH}/tools/cmake/project.cmake)
project(project-name)


The second CMakeLists.txt in src_dir is responsible for controlling the build process of the component and its integration into the overall project. The minimal component CMakeLists.txt file simply registers the component to the build system using idf_component_register:

idf_component_register(SRCS "foo.c" "bar.c")


The files specified using idf_component_register are used ONLY for generating build configurations, but it's highly recommended to specify all application source files in order to keep the project compatible with the usual ESP-IDF workflow.

WARNING:

By default PlatformIO expects source files to be located in the src folder. At the same time, the default location for source files within the ESP-IDF build system is a special folder with the name main. Renaming the main component may require users to manually specify additional dependencies: 

idf_component_register(SRCS "main.c" REQUIRES idf::mbedtls)


More details in the official ESP-IDF documentation - Renaming main component.



Due to the current limitations of CMake file-based API, there is no way of generating build configuration for source files written in various programming languages if they are not specified in idf_component_register command. If your project contains libraries written in languages that differ from the language used for the main application you need to create an empty file with the desired extension (e.g. *.cpp for C++) in order to force CMake generate build configuration for this language.

NOTE:

Build configuration generated for source files specified in idf_component_register is also used as the base build environment for project sources (including libraries).


ESP-IDF components

ESP-IDF modules as modular pieces of standalone code might be useful for structuring reusable code or including third party components that aren’t part of ESP-IDF.

These components contain either a single CMakeLists.txt file which controls the build process of the component and its integration into the overall project. An optional Kconfig file defines the component configuration options that can be set via menuconfig. Some components may also include Kconfig.projbuild and project_include.cmake files, which are special files for overriding parts of the project. All valid components will be compiled as static libraries and linked to the final firmware. There are two possible ways of adding extra components to PlatformIO project:

  • By adding a new component to an optional folder called components in the root of your project. This folder will be automatically scanned for valid components.
  • Using EXTRA_COMPONENT_DIRS option in the root CMakeLists.txt file. This option represents a list of extra directories to search for components.

An example of specifying esp-aws-iot as an extra component:

# The following lines of boilerplate have to be in your project's CMakeLists
# in this exact order for cmake to work correctly
cmake_minimum_required(VERSION 3.16)
include($ENV{IDF_PATH}/tools/cmake/project.cmake)
list(APPEND EXTRA_COMPONENT_DIRS esp-aws-iot)
project(subscribe_publish)


WARNING:

Since src_dir is also passed to CMake as an extra component, you should only append to EXTRA_COMPONENT_DIRS variable in order not to override the default package.


Since the build may not work correctly if the full path to sources is greater than 250 characters (see CMAKE_OBJECT_PATH_MAX) it might be a good idea to keep modules close to the project files.

ULP coprocessor programming

If you want to take measurements using ADC, internal temperature sensor or external I2C sensors, while the main processors are in deep sleep mode you need to use ULP coprocessor. At the moment ULP can be used only with the ESP-IDF.

All ULP code, usually written in assembly in files with .S extension, must be placed into a separate directory with the name ulp in the root folder of your project. So your project structure should look like this:

project_dir
├── include
├── src
│    ├── CMakeLists.txt
│    └── main.c
├── ulp
│    └── ulp_code.S
├── CMakeLists.txt
└── platformio.ini


Since PlatformIO uses the code model generated by CMake it's mandatory to specify ULP source files in CMakeLists.txt as well. An example of typical CMakeLists.txt for ULP:

idf_component_register(SRCS "ulp_adc_example_main.c")
#
# ULP support additions to component CMakeLists.txt.
#
# 1. The ULP app name must be "ulp_main"
set(ulp_app_name ulp_main)
#
# 2. Specify all assembly source files.
#    Paths are relative because ULP files are placed into a special directory "ulp"
#    in the root of the project
set(ulp_s_sources "../ulp/adc.S")
#
# 3. List all the component source files which include automatically
#    generated ULP export file, ${ulp_app_name}.h:
set(ulp_exp_dep_srcs "ulp_adc_example_main.c")
#
# 4. Call function to build ULP binary and embed in project using the argument
#    values above.
ulp_embed_binary(${ulp_app_name} ${ulp_s_sources} ${ulp_exp_dep_srcs})


See full examples with ULP coprocessor programming:

  • https://github.com/platformio/platform-espressif32/tree/develop/examples/espidf-ulp-adc
  • https://github.com/platformio/platform-espressif32/tree/develop/examples/espidf-ulp-pulse

More details are located in the official ESP-IDF documentation - ULP coprocessor programming.

At the moment several limitations are present:

  • No whitespace characters allowed in project paths.
  • The src_filter option cannot be used.

Support for ESP-IDF v3.x is considered obsolete and is not available in the latest platform releases. Please check the platform release notes to figure out what version of the platform should be installed to use required ESP-IDF version, for example:

[env:esp32dev]
; v1.10.0 is the last version that supports ESP-IDF v3.3
platform = espressif32@1.10.0
framework = espidf
board = esp32dev




Project Structure

Due to limited support of GNU Make build system used in ESP-IDF v3.x, the project configuration depends on a pregenerated file sdkconfig.h which contains a list of macro definitions CONFIG_*. These definitions describe project settings that will be used for preparing a proper build environment. You can use the default sdkconfig.h shipped with the platform or generate a custom one using native ESP-IDF build environment.

A typical PlatformIO project for ESP-IDF v3.x must have the following structure:

project_dir
├── include
├── lib
│   └── README
├── test
├── src
│    ├── sdkconfig.h
│    └── main.c
└── platformio.ini


to enable C++ exceptions for ESP-IDF add -D PIO_FRAMEWORK_ESP_IDF_ENABLE_EXCEPTIONS to build_flags of "platformio.ini" (Project Configuration File).

See project example with enabled exceptions.

ULP coprocessor programming

To use ULP in your project you need to make sure that it's enabled in the sdkconfig.h configuration file. The following two lines must be added:

#define CONFIG_ULP_COPROC_ENABLED 1
#define CONFIG_ULP_COPROC_RESERVE_MEM 1024


Usually CONFIG_ULP_COPROC_RESERVE_MEM is already defined in the default sdkconfig.h with value 0. You can modify this value to meet your requirements.

All ULP code, usually written in assembly in files with .S extension, must be placed into a separate directory with the name ulp in the root folder of your project. So your project structure should look like this:

project_dir
├── include
├── lib
│   └── README
├── test
├── src
│    ├── main.c
│    └── sdkconfig.h
├── ulp
│    └── ulp_code.S
└── platformio.ini


See full examples with ULP coprocessor programming for ESP-IDF v3.x:

  • https://github.com/platformio/platform-espressif32/tree/v1.10.0/examples/espidf-ulp-adc
  • https://github.com/platformio/platform-espressif32/tree/v1.10.0/examples/espidf-ulp-pulse

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
Espressif ESP-WROVER-KIT Espressif 32 ESP32 240MHz 4MB 320KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 ESP32 240MHz 16MB 520KB
Adafruit ESP32 Feather Espressif 32 ESP32 240MHz 4MB 320KB
D-duino-32 Espressif 32 ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 ESP32 240MHz 4MB 320KB
Dongsen Tech Pocket 32 Espressif 32 ESP32 240MHz 4MB 320KB
ESP32 FM DevKit Espressif 32 ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 ESP32 240MHz 4MB 320KB
FireBeetle-ESP32 Espressif 32 ESP32 240MHz 4MB 320KB
Frog Board ESP32 Espressif 32 ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev Espressif 32 ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32DevKIT Espressif 32 ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 ESP32 240MHz 4MB 320KB
Node32s Espressif 32 ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 ESP32 240MHz 4MB 320KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 ESP32 240MHz 4MB 1.25MB
SG-O AirMon Espressif 32 ESP32 240MHz 4MB 320KB
Silicognition wESP32 Espressif 32 ESP32 240MHz 4MB 320KB
SparkFun ESP32 Thing Espressif 32 ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V1 Espressif 32 ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 ESP32 240MHz 4MB 320KB
VintLabs ESP32 Devkit Espressif 32 ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 ESP32 240MHz 4MB 320KB
XinaBox CW02 Espressif 32 ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Io Espressif 32 ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 ESP32 240MHz 4MB 320KB

•
ESP-IDF for Espressif 32

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



AI Thinker

Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB

Name Platform Debug MCU Frequency Flash RAM
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB

April Brother

Name Platform Debug MCU Frequency Flash RAM
April Brother ESPea32 Espressif 32 No ESP32 240MHz 4MB 320KB

BPI Tech

Name Platform Debug MCU Frequency Flash RAM
BPI-Bit Espressif 32 No ESP32 160MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB

Dongsen Technology

Name Platform Debug MCU Frequency Flash RAM
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB

Electronic SweetPeas

Name Platform Debug MCU Frequency Flash RAM
Electronic SweetPeas ESP320 Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ESP32 Pico Kit Espressif 32 No ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ODROID-GO Espressif 32 No ESP32 240MHz 16MB 320KB

Heltec Automation

Name Platform Debug MCU Frequency Flash RAM
Heltec WiFi Kit 32 Espressif 32 No ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
IntoRobot Fig Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
M5Stack Core ESP32 Espressif 32 No ESP32 240MHz 4MB 320KB
M5Stack FIRE Espressif 32 No ESP32 240MHz 16MB 6.25MB
M5Stack GREY ESP32 Espressif 32 No ESP32 240MHz 16MB 520KB
M5Stick-C Espressif 32 No ESP32 240MHz 4MB 320KB

MH-ET Live

Name Platform Debug MCU Frequency Flash RAM
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
MagicBit Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
MakerAsia Nano32 Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Microduino Core ESP32 Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Noduino Quantum Espressif 32 No ESP32 240MHz 16MB 320KB

Name Platform Debug MCU Frequency Flash RAM
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-PRO Espressif 32 No ESP32 240MHz 4MB 320KB
OLIMEX ESP32-PoE Espressif 32 No ESP32 240MHz 4MB 320KB
OLIMEX ESP32-PoE-ISO Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
OROCA EduBot Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Onehorse ESP32 Dev Module Espressif 32 No ESP32 240MHz 4MB 320KB

Pycom Ltd.

Name Platform Debug MCU Frequency Flash RAM
Pycom GPy Espressif 32 No ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB

Qmobot LLP

Name Platform Debug MCU Frequency Flash RAM
Qchip Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB

SparkFun Electronics

Name Platform Debug MCU Frequency Flash RAM
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T-Watch Espressif 32 No ESP32 240MHz 16MB 320KB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
TinyPICO Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Turta IoT Node Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Widora AIR Espressif 32 No ESP32 240MHz 16MB 320KB

Name Platform Debug MCU Frequency Flash RAM
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
u-blox NINA-W10 series Espressif 32 No ESP32 240MHz 2MB 320KB

framework = freedom-e-sdk

Open Source Software for Developing on the SiFive Freedom E Platform

For more detailed information please visit vendor site.

  • Debugging
  • Examples
  • Platforms
  • Boards

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
Arty FPGA Dev Kit SiFive FE310 450MHz 16MB 256MB
HiFive Unleashed SiFive FU540 1500MHz 32MB 8GB
HiFive1 SiFive FE310 320MHz 16MB 16KB
HiFive1 Rev B SiFive FE310 320MHz 16MB 16KB
SparkFun RED-V RedBoard SiFive FE310 320MHz 16MB 16KB
SparkFun RED-V Thing Plus SiFive FE310 320MHz 16MB 16KB

•
Freedom E SDK for SiFive

Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
HiFive Unleashed SiFive On-board FU540 1500MHz 32MB 8GB
HiFive1 SiFive On-board FE310 320MHz 16MB 16KB
HiFive1 Rev B SiFive On-board FE310 320MHz 16MB 16KB

Name Platform Debug MCU Frequency Flash RAM
SparkFun RED-V RedBoard SiFive On-board FE310 320MHz 16MB 16KB
SparkFun RED-V Thing Plus SiFive On-board FE310 320MHz 16MB 16KB

Name Platform Debug MCU Frequency Flash RAM
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB

framework = gd32vf103-sdk

GigaDevice GD32VF103 Firmware Library (SDK)

For more detailed information please visit vendor site.

  • Debugging
  • Examples
  • Platforms
  • Boards

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
GD32VF103V-EVAL GigaDevice GD32V GD32VF103VBT6 108MHz 128KB 32KB
Sipeed Longan Nano GigaDevice GD32V GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V GD32VF103C8T6 108MHz 64KB 20KB
Wio Lite RISC-V GigaDevice GD32V GD32VF103CBT6 108MHz 128KB 32KB

•
GigaDevice GD32V SDK for GigaDevice GD32V

Name Description
GigaDevice GD32V The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
Wio Lite RISC-V GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB

Name Platform Debug MCU Frequency Flash RAM
GD32VF103V-EVAL GigaDevice GD32V External GD32VF103VBT6 108MHz 128KB 32KB
Sipeed Longan Nano GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V External GD32VF103C8T6 108MHz 64KB 20KB

framework = kendryte-freertos-sdk

Kendryte SDK with FreeRTOS support

For more detailed information please visit vendor site.

  • Debugging
  • Examples
  • Platforms
  • Boards

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
Sipeed MAIX BiT Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 K210 400MHz 16MB 6MB

•
Kendryte FreeRTOS SDK for Kendryte K210

Name Description
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB

framework = kendryte-standalone-sdk

Kendryte Standalone SDK without OS support

For more detailed information please visit vendor site.

  • Debugging
  • Examples
  • Platforms
  • Boards

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
Sipeed MAIX BiT Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 K210 400MHz 16MB 6MB

•
Kendryte Standalone SDK for Kendryte K210

Name Description
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB

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.

For more detailed information please visit vendor site.

  • Debugging
  • Examples
  • Platforms
  • Boards

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
ST Nucleo F103RB ST STM32 STM32F103RBT6 72MHz 128KB 20KB
ST STM32F3DISCOVERY ST STM32 STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 STM32F407VGT6 168MHz 1MB 128KB
ST STM32LDISCOVERY ST STM32 STM32L152RBT6 32MHz 128KB 16KB
TI LaunchPad (Stellaris) w/ lm4f120 (80MHz) TI TIVA LPLM4F120H5QR 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c123 (80MHz) TI TIVA LPTM4C1230C3PM 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c129 (120MHz) TI TIVA LPTM4C1294NCPDT 120MHz 1MB 256KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
1Bitsy ST STM32 STM32F415RGT 168MHz 1MB 128KB
BlackPill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 STM32F103C8T6 72MHz 128KB 20KB
BluePill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 STM32F103C8T6 72MHz 128KB 20KB
Maple ST STM32 STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) ST STM32 STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 ST STM32 STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original ST STM32 STM32F103CBT6 72MHz 108KB 17KB
OLIMEXINO-STM32 ST STM32 STM32F103RBT6 72MHz 128KB 20KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 STM32F103ZET6 72MHz 512KB 64KB

  • libOpenCM3 for ST STM32
  • libOpenCM3 for TI TIVA

Name Description
ST STM32 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.
TI TIVA Texas Instruments TM4C12x MCUs offer the industrys most popular ARM Cortex-M4 core with scalable memory and package options, unparalleled connectivity peripherals, advanced application functions, industry-leading analog integration, and extensive software solutions.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
1Bitsy ST STM32 External STM32F415RGT 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
BlackPill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
BluePill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 External STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 External STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 External STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 External STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 External STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 External STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 External STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 External STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 External STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 External STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 External STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 External STM32F103ZET6 72MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
Maple ST STM32 External STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) ST STM32 External STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original ST STM32 External STM32F103CBT6 72MHz 108KB 17KB

Name Platform Debug MCU Frequency Flash RAM
OLIMEXINO-STM32 ST STM32 External STM32F103RBT6 72MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
ST Nucleo F103RB ST STM32 On-board STM32F103RBT6 72MHz 128KB 20KB
ST STM32F3DISCOVERY ST STM32 On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32LDISCOVERY ST STM32 On-board STM32L152RBT6 32MHz 128KB 16KB

Name Platform Debug MCU Frequency Flash RAM
TI LaunchPad (Stellaris) w/ lm4f120 (80MHz) TI TIVA On-board LPLM4F120H5QR 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c123 (80MHz) TI TIVA On-board LPTM4C1230C3PM 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c129 (120MHz) TI TIVA On-board LPTM4C1294NCPDT 120MHz 1MB 256KB

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.

For more detailed information please visit vendor site.

  • Configuration
  • Debugging
  • Examples
  • Platforms
  • Boards

  • Configuration system
  • Mbed lib and Mbed OS 5
  • Build profiles
  • Ignoring particular components
  • Custom Targets

PlatformIO allows you to customize mbed OS compile time configuration parameters using mbed_app.json manifest. It should be placed into the root of your project and located on the same level as "platformio.ini" (Project Configuration File).

Configuration is defined using JSON. Some examples of configuration parameters:

  • The sampling period for a data acquisition application.
  • The default stack size for a newly created OS thread.
  • The receive buffer size of a serial communication library.
  • The flash and RAM memory size of a target board.

See more details in the official ARM Mbed OS Configuration System.

A few PlatformIO-ready projects based on ARM mbed OS which use mbed_app.json;

  • Freescale Kinetis: mbed-rtos-tls-client
  • ST STM32: mbed-rtos-mesh-minimal

PlatformIO allows compiling projects with or without Mbed OS. By default, project is built without the OS feature. Most of the framework functionality requires the OS to be enabled. To add the OS feature you can use a special macro definition that needs be added to build_flags of "platformio.ini" (Project Configuration File):

Name Description
PIO_FRAMEWORK_MBED_RTOS_PRESENT Build the project with enabled rtos

An example of "platformio.ini" (Project Configuration File) with enabled rtos

[env:wizwiki_w7500p]
platform = wiznet7500
framework = mbed
board = wizwiki_w7500p
build_flags = -D PIO_FRAMEWORK_MBED_RTOS_PRESENT


By default, PlatformIO builds your project using develop profile which provides optimized firmware size with full error information and allows MCU to go to sleep mode. In the case when default build profile is not suitable for your project there two other profiles release and debug that can be enabled using special macro definitions. You can change build profile build_flags of "platformio.ini" (Project Configuration File):

Name Description
MBED_BUILD_PROFILE_RELEASE Release profile (smallest firmware, minimal error info)
MBED_BUILD_PROFILE_DEBUG Debug profile (largest firmware, disabled sleep mode)

More information about differences between build profiles can be found on the official page ARM Mbed OS Build Profiles.

In case you don't need all parts of the framework or you want to reduce the compilation time, you can explicitly exclude folders with redundant sources. For example, to remove cellular, mbedtls and nanostack features from the build process, navigate to packages_dir and create a new file framework-mbed/features/.mbedignore with the following contents:

cellular/*
mbedtls/*
nanostack/*


If you want to exclude the entire folder, simply create .mbedignore file and add only one symbol * to this file.

In case when your board is not officially supported by Mbed you can manually add custom board definitions to your project. First of all, you need to create a special file custom_targets.json in the root folder of your project where you describe your board, for example here is the configuration for NUCLEO-F401RE board:

{
  "NUCLEO_F401RE": {
        "inherits": ["FAMILY_STM32"],
        "supported_form_factors": ["ARDUINO", "MORPHO"],
        "core": "Cortex-M4F",
        "extra_labels_add": ["STM32F4", "STM32F401xE", "STM32F401RE"],
        "config": {
            "clock_source": {
                "help": "Mask value : USE_PLL_HSE_EXTC | USE_PLL_HSE_XTAL (need HW patch) | USE_PLL_HSI",
                "value": "USE_PLL_HSE_EXTC|USE_PLL_HSI",
                "macro_name": "CLOCK_SOURCE"
            }
        },
        "detect_code": ["0720"],
        "macros_add": ["USB_STM_HAL", "USBHOST_OTHER"],
        "device_has_add": [
            "SERIAL_ASYNCH",
            "FLASH",
            "MPU"
        ],
        "release_versions": ["2", "5"],
        "device_name": "STM32F401RE"
    }
}


Secondly, you need to add code specific to your target to the src folder of your project. Usually, it's a good idea to isolate this code in a separate folder and add the path to this folder to build_flags of "platformio.ini" (Project Configuration File):

[env:my_custom_board]
platform = nxplpc
framework = mbed
board = my_custom_board
build_flags = -I$PROJECT_SRC_DIR/MY_CUSTOM_BOARD_TARGET


Next, you need to inform PlatformIO that there is a new custom board. To do this, you can create boards directory in the root folder of your project and add a board manifest file with your board name, e.g. my_custom_board.json as described here Custom Embedded Boards

After these steps, your project structure should look like this:

project_dir
├── include
├── boards
│    └── my_custom_board.json
├── src
│    ├── main.cpp
│    └── MY_CUSTOM_BOARD_TARGET
│         ├── pinNames.h
│         └── pinNames.c
├── custom_targets.json
└── platformio.ini


Adding and configuring targets.

See full examples with a custom board:

•
https://github.com/platformio/platform-nxplpc/tree/develop/examples/mbed-custom-target

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
32F412GDISCOVERY ST STM32 STM32F412ZGT6 100MHz 1MB 256KB
96Boards B96B-F446VE ST STM32 STM32F446VET6 168MHz 512KB 128KB
ARM mbed LPC11U24 (+CAN) NXP LPC LPC11U24 48MHz 32KB 8KB
Atmel ATSAMR21-XPRO Atmel SAM SAMR21G18A 48MHz 256KB 32KB
Atmel ATSAMW25-XPRO Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO Atmel SAM SAMD21J18A 48MHz 256KB 32KB
Atmel SAML21-XPRO-B Atmel SAM SAML21J18B 48MHz 256KB 32KB
BBC micro:bit Nordic nRF51 NRF51822 16MHz 256KB 16KB
Bambino-210E NXP LPC LPC4330 204MHz 8MB 264KB
CoCo-ri-Co! NXP LPC LPC812 30MHz 16KB 4KB
Delta DFBM-NQ620 Nordic nRF52 NRF52832 64MHz 512KB 64KB
Delta DFCM-NNN40 Nordic nRF51 NRF51822 32MHz 256KB 32KB
Delta DFCM-NNN50 Nordic nRF51 NRF51822 32MHz 256KB 16KB
EFM32GG-STK3700 Giant Gecko Silicon Labs EFM32 EFM32GG990F1024 48MHz 1MB 128KB
EFM32LG-STK3600 Leopard Gecko Silicon Labs EFM32 EFM32LG990F256 48MHz 256KB 32KB
EFM32WG-STK3800 Wonder Gecko Silicon Labs EFM32 EFM32WG990F256 48MHz 256KB 32KB
EFM32ZG-STK3200 Zero Gecko Silicon Labs EFM32 EFM32ZG222F32 24MHz 32KB 4KB
Embedded Artists LPC4088 Display Module NXP LPC LPC4088 120MHz 512KB 96KB
Embedded Artists LPC4088 QuickStart Board NXP LPC LPC4088 120MHz 512KB 96KB
Ethernet IoT Starter Kit Freescale Kinetis MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K20D50M Freescale Kinetis MK20DX128VLH5 48MHz 128KB 16KB
Freescale Kinetis FRDM-K22F Freescale Kinetis MK22FN512VLH12 120MHz 512KB 128KB
Freescale Kinetis FRDM-K64F Freescale Kinetis MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K66F Freescale Kinetis MK66FN2M0VMD18 180MHz 2MB 256KB
Freescale Kinetis FRDM-K82F Freescale Kinetis MK82FN256VLL15 150MHz 256KB 256KB
Freescale Kinetis FRDM-KL05Z Freescale Kinetis MKL05Z32VFM4 48MHz 32KB 4KB
Freescale Kinetis FRDM-KL25Z Freescale Kinetis MKL25Z128VLK4 48MHz 128KB 16KB
Freescale Kinetis FRDM-KL27Z Freescale Kinetis MKL27Z64VLH4 48MHz 64KB 16KB
Freescale Kinetis FRDM-KL43Z Freescale Kinetis MKL43Z256VLH4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL46Z Freescale Kinetis MKL46Z256VLL4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KW41Z Freescale Kinetis MKW41Z512VHT4 48MHz 512KB 128KB
GAPuino GAP8 RISC-V GAP GAP8 250MHz 64MB 8MB
JKSoft Wallbot BLE Nordic nRF51 NRF51822 16MHz 128KB 16KB
L476DMW1K ST STM32 STM32L476VGT6 80MHz 1MB 128KB
LPCXpresso11U68 NXP LPC LPC11U68 50MHz 256KB 36KB
LPCXpresso824-MAX NXP LPC LPC824 30MHz 32KB 8KB
Maxim ARM mbed Enabled Development Platform for MAX32600 Maxim 32 MAX32600 24MHz 256KB 32KB
Mbed Connect Cloud ST STM32 STM32F439ZIY6 168MHz 2MB 256KB
NXP LPC800-MAX NXP LPC LPC812 30MHz 16KB 4KB
NXP LPCXpresso54114 NXP LPC LPC54114J256BD64 100MHz 256KB 192KB
NXP LPCXpresso54608 NXP LPC LPC54608ET512 180MHz 512KB 200KB
NXP i.MX RT1050 Evaluation Kit NXP i.MX RT MIMXRT1052DVL6B 600MHz 64MB 512KB
NXP mbed LPC11U24 NXP LPC LPC11U24 48MHz 32KB 8KB
NXP mbed LPC1768 NXP LPC LPC1768 96MHz 512KB 64KB
Nordic nRF51 Dongle (PCA10031) Nordic nRF51 NRF51822 32MHz 256KB 32KB
Nordic nRF51822-mKIT Nordic nRF51 NRF51822 16MHz 128KB 16KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 NRF52840 64MHz 1MB 256KB
RedBearLab BLE Nano 1.5 Nordic nRF51 NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 NRF52832 64MHz 512KB 64KB
RedBearLab nRF51822 Nordic nRF51 NRF51822 16MHz 256KB 16KB
RushUp Cloud-JAM ST STM32 STM32F401RET6 84MHz 512KB 96KB
RushUp Cloud-JAM L4 ST STM32 STM32L476RGT6 80MHz 1MB 128KB
SLSTK3400A USB-enabled Happy Gecko Silicon Labs EFM32 EFM32HG322F64 25MHz 64KB 8KB
SLSTK3401A Pearl Gecko PG1 Silicon Labs EFM32 EFM32PG1B200F256GM48 40MHz 256KB 32KB
ST 32F3348DISCOVERY ST STM32 STM32F334C8T6 72MHz 64KB 12KB
ST 32F401CDISCOVERY ST STM32 STM32F401VCT6 84MHz 256KB 64KB
ST 32F413HDISCOVERY ST STM32 STM32F413ZHT6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY ST STM32 STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY ST STM32 STM32F769NIH6 216MHz 1MB 512KB
ST 32L0538DISCOVERY ST STM32 STM32L053C8T6 32MHz 64KB 8KB
ST 32L476GDISCOVERY ST STM32 STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY ST STM32 STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F031K6 ST STM32 STM32F031K6T6 48MHz 32KB 4KB
ST Nucleo F042K6 ST STM32 STM32F042K6T6 48MHz 32KB 6KB
ST Nucleo F070RB ST STM32 STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F072RB ST STM32 STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F091RC ST STM32 STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 ST STM32 STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE ST STM32 STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F303ZE ST STM32 STM32F303ZET6 72MHz 512KB 64KB
ST Nucleo F334R8 ST STM32 STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE ST STM32 STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F410RB ST STM32 STM32F410RBT6 100MHz 128KB 32KB
ST Nucleo F411RE ST STM32 STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG ST STM32 STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH ST STM32 STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F439ZI ST STM32 STM32F439ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F446ZE ST STM32 STM32F446ZET6 180MHz 512KB 128KB
ST Nucleo F746ZG ST STM32 STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG ST STM32 STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI ST STM32 STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI ST STM32 STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L031K6 ST STM32 STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 ST STM32 STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE ST STM32 STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L432KC ST STM32 STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L433RC-P ST STM32 STM32L433RC 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L486RG ST STM32 STM32L486RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P ST STM32 STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI ST STM32 STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY ST STM32 STM32F030R8T6 48MHz 64KB 8KB
ST STM32F0DISCOVERY ST STM32 STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY ST STM32 STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 STM32F407VGT6 168MHz 1MB 128KB
ST STM32VLDISCOVERY ST STM32 STM32F100RBT6 24MHz 128KB 8KB
ST Sensor Node ST STM32 STM32L476JG 80MHz 1MB 128KB
Seeed Arch BLE Nordic nRF51 NRF51822 16MHz 128KB 16KB
Seeed Arch Link Nordic nRF51 NRF51822 16MHz 256KB 16KB
Seeed Arch Max ST STM32 STM32F407VET6 168MHz 512KB 192KB
Seeed Arch Pro NXP LPC LPC1768 96MHz 512KB 64KB
Seeed Tiny BLE Nordic nRF51 NRF51822 16MHz 256KB 16KB
Seeed Wio 3G ST STM32 STM32F439VI 180MHz 2MB 256KB
Switch Science mbed HRM1017 Nordic nRF51 NRF51822 16MHz 256KB 16KB
Switch Science mbed LPC1114FN28 NXP LPC LPC1114FN28 48MHz 32KB 4KB
Switch Science mbed LPC824 NXP LPC LPC824 30MHz 32KB 8KB
Switch Science mbed TY51822r3 Nordic nRF51 NRF51822 32MHz 256KB 32KB
Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT Silicon Labs EFM32 EFR32MG12P432F1024 40MHz 1MB 256KB
VNG VBLUNO51 Nordic nRF51 NRF51822 16MHz 128KB 32KB
WIZwiki-W7500 WIZNet W7500 WIZNET7500 48MHz 128KB 48KB
WIZwiki-W7500ECO WIZNet W7500 WIZNET7500ECO 48MHz 128KB 48KB
WIZwiki-W7500P WIZNet W7500 WIZNET7500P 48MHz 128KB 48KB
sakura.io Evaluation Board ST STM32 STM32F411RET6 100MHz 1MB 128KB
u-blox C027 NXP LPC LPC1768 96MHz 512KB 64KB
u-blox C030-R410M IoT ST STM32 STM32F437VG 180MHz 1MB 256KB
u-blox EVK-NINA-B1 Nordic nRF52 NRF52832 64MHz 512KB 64KB
y5 nRF51822 mbug Nordic nRF51 NRF51822 16MHz 256KB 16KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
BluePill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
CQ Publishing TG-LPC11U35-501 NXP LPC LPC11U35 48MHz 64KB 10KB
DipCortex M3 NXP LPC LPC1347 72MHz 64KB 12KB
EA LPC11U35 QuickStart Board NXP LPC LPC11U35 48MHz 64KB 10KB
Espotel LoRa Module ST STM32 STM32F411RET6 100MHz 512KB 128KB
Freescale Kinetis FRDM-KL82Z Freescale Kinetis MKL82Z128VLK7 96MHz 128KB 96KB
Freescale Kinetis FRDM-KW24D512 Freescale Kinetis MKW24D512 50MHz 512KB 64KB
Hexiwear Freescale Kinetis MK64FN1M0VDC12 120MHz 1MB 256KB
MAX32620FTHR Maxim 32 MAX32620FTHR 96MHz 2MB 256KB
MTS Dragonfly ST STM32 STM32F411RET6 100MHz 512KB 128KB
Maxim Health Sensor Platform Maxim 32 MAX32620 96MHz 2MB 256KB
Maxim Wireless Sensor Node Demonstrator Maxim 32 MAX32610 24MHz 256KB 32KB
MultiTech mDot ST STM32 STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot F411 ST STM32 STM32F411RET6 100MHz 512KB 128KB
MultiTech xDot ST STM32 STM32L151CCU6 32MHz 256KB 32KB
NAMote72 ST STM32 STM32L152RC 32MHz 256KB 32KB
NGX Technologies BlueBoard-LPC11U24 NXP LPC LPC11U24 48MHz 32KB 8KB
NXP LPC11C24 NXP LPC LPC11C24 48MHz 32KB 8KB
NXP LPC11U34 NXP LPC LPC11U34 48MHz 40KB 8KB
NXP LPC11U37 NXP LPC LPC11U37 48MHz 128KB 10KB
NXP LPCXpresso1549 NXP LPC LPC1549 72MHz 256KB 36KB
OLIMEXINO-STM32 ST STM32 STM32F103RBT6 72MHz 128KB 20KB
SDT52832B Nordic nRF52 NRF52832 64MHz 512KB 64KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 STM32F103C8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 STM32F103RBT6 72MHz 128KB 20KB
Solder Splash Labs DipCortex M0 NXP LPC LPC11U24 50MHz 32KB 8KB
Teensy 3.1 / 3.2 Teensy MK20DX256 72MHz 256KB 64KB
u-blox C030-N211 IoT Starter Kit ST STM32 STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit ST STM32 STM32F437VG 180MHz 1MB 256KB
u-blox EVK-ODIN-W2 ST STM32 STM32F439ZIY6 168MHz 2MB 256KB
u-blox ODIN-W2 ST STM32 STM32F439ZIY6 168MHz 2MB 256KB
y5 LPC11U35 mbug NXP LPC LPC11U35 48MHz 64KB 10KB

  • Mbed for Atmel SAM
  • Mbed for Freescale Kinetis
  • Mbed for Maxim 32
  • Mbed for Nordic nRF51
  • Mbed for Nordic nRF52
  • Mbed for NXP i.MX RT
  • Mbed for NXP LPC
  • Mbed for RISC-V GAP
  • Mbed for Silicon Labs EFM32
  • Mbed for ST STM32
  • Mbed for Teensy
  • Mbed for WIZNet W7500

Name Description
Atmel SAM Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Freescale Kinetis Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.
Maxim 32 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.
Nordic nRF51 The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.
Nordic nRF52 The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.
NXP i.MX RT The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.
NXP LPC The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.
RISC-V 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.
Silicon Labs EFM32 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.
ST STM32 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.
Teensy Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.
WIZNet W7500 The IOP (Internet Offload Processor) W7500 is the one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform especially requiring Internet of things

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
96Boards B96B-F446VE ST STM32 On-board STM32F446VET6 168MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
MicroNFCBoard NXP LPC No LPC11U34 48MHz 48KB 10KB

Name Platform Debug MCU Frequency Flash RAM
Atmel ATSAMR21-XPRO Atmel SAM On-board SAMR21G18A 48MHz 256KB 32KB
Atmel ATSAMW25-XPRO Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO Atmel SAM On-board SAMD21J18A 48MHz 256KB 32KB
Atmel SAML21-XPRO-B Atmel SAM On-board SAML21J18B 48MHz 256KB 32KB

Avnet Silica

Name Platform Debug MCU Frequency Flash RAM
ST Sensor Node ST STM32 On-board STM32L476JG 80MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
BBC micro:bit Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

CQ Publishing

Name Platform Debug MCU Frequency Flash RAM
CQ Publishing TG-LPC11U35-501 NXP LPC External LPC11U35 48MHz 64KB 10KB

Name Platform Debug MCU Frequency Flash RAM
Delta DFBM-NQ620 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Delta DFCM-NNN40 Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Delta DFCM-NNN50 Nordic nRF51 On-board NRF51822 32MHz 256KB 16KB

Elektor Labs

Name Platform Debug MCU Frequency Flash RAM
CoCo-ri-Co! NXP LPC On-board LPC812 30MHz 16KB 4KB

Embedded Artists

Name Platform Debug MCU Frequency Flash RAM
EA LPC11U35 QuickStart Board NXP LPC External LPC11U35 48MHz 64KB 10KB
Embedded Artists LPC4088 Display Module NXP LPC On-board LPC4088 120MHz 512KB 96KB
Embedded Artists LPC4088 QuickStart Board NXP LPC On-board LPC4088 120MHz 512KB 96KB

Name Platform Debug MCU Frequency Flash RAM
Espotel LoRa Module ST STM32 External STM32F411RET6 100MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
Ethernet IoT Starter Kit Freescale Kinetis On-board MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K20D50M Freescale Kinetis On-board MK20DX128VLH5 48MHz 128KB 16KB
Freescale Kinetis FRDM-K22F Freescale Kinetis On-board MK22FN512VLH12 120MHz 512KB 128KB
Freescale Kinetis FRDM-K64F Freescale Kinetis On-board MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K66F Freescale Kinetis On-board MK66FN2M0VMD18 180MHz 2MB 256KB
Freescale Kinetis FRDM-K82F Freescale Kinetis On-board MK82FN256VLL15 150MHz 256KB 256KB
Freescale Kinetis FRDM-KL05Z Freescale Kinetis On-board MKL05Z32VFM4 48MHz 32KB 4KB
Freescale Kinetis FRDM-KL25Z Freescale Kinetis On-board MKL25Z128VLK4 48MHz 128KB 16KB
Freescale Kinetis FRDM-KL27Z Freescale Kinetis On-board MKL27Z64VLH4 48MHz 64KB 16KB
Freescale Kinetis FRDM-KL43Z Freescale Kinetis On-board MKL43Z256VLH4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL46Z Freescale Kinetis On-board MKL46Z256VLL4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL82Z Freescale Kinetis External MKL82Z128VLK7 96MHz 128KB 96KB
Freescale Kinetis FRDM-KW24D512 Freescale Kinetis External MKW24D512 50MHz 512KB 64KB
Freescale Kinetis FRDM-KW41Z Freescale Kinetis On-board MKW41Z512VHT4 48MHz 512KB 128KB

GHI Electronics

Name Platform Debug MCU Frequency Flash RAM
mBuino NXP LPC No LPC11U24 50MHz 32KB 10KB

Name Platform Debug MCU Frequency Flash RAM
BluePill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 External STM32F103RBT6 72MHz 128KB 20KB

GreenWaves Technologies

Name Platform Debug MCU Frequency Flash RAM
GAPuino GAP8 RISC-V GAP On-board GAP8 250MHz 64MB 8MB

Name Platform Debug MCU Frequency Flash RAM
JKSoft Wallbot BLE Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB

Name Platform Debug MCU Frequency Flash RAM
MAX32620FTHR Maxim 32 External MAX32620FTHR 96MHz 2MB 256KB
MAX32625MBED Maxim 32 No MAX32625 96MHz 512KB 160KB
MAX32625NEXPAQ Maxim 32 No MAX32625 96MHz 512KB 160KB
MAX32625PICO Maxim 32 No MAX32625 96MHz 512KB 160KB
Maxim ARM mbed Enabled Development Platform for MAX32600 Maxim 32 On-board MAX32600 24MHz 256KB 32KB
Maxim Health Sensor Platform Maxim 32 External MAX32620 96MHz 2MB 256KB
Maxim MAX32630FTHR Application Platform Maxim 32 No MAX32630 96MHz 2MB 512KB
Maxim Wireless Sensor Node Demonstrator Maxim 32 External MAX32610 24MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Bambino-210E NXP LPC On-board LPC4330 204MHz 8MB 264KB

Name Platform Debug MCU Frequency Flash RAM
Hexiwear Freescale Kinetis External MK64FN1M0VDC12 120MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
MTS Dragonfly ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot F411 ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech xDot ST STM32 External STM32L151CCU6 32MHz 256KB 32KB

NGX Technologies

Name Platform Debug MCU Frequency Flash RAM
NGX Technologies BlueBoard-LPC11U24 NXP LPC External LPC11U24 48MHz 32KB 8KB

Name Platform Debug MCU Frequency Flash RAM
ARM mbed LPC11U24 (+CAN) NXP LPC On-board LPC11U24 48MHz 32KB 8KB
LPCXpresso11U68 NXP LPC On-board LPC11U68 50MHz 256KB 36KB
LPCXpresso824-MAX NXP LPC On-board LPC824 30MHz 32KB 8KB
NXP LPC11C24 NXP LPC External LPC11C24 48MHz 32KB 8KB
NXP LPC11U34 NXP LPC External LPC11U34 48MHz 40KB 8KB
NXP LPC11U37 NXP LPC External LPC11U37 48MHz 128KB 10KB
NXP LPC800-MAX NXP LPC On-board LPC812 30MHz 16KB 4KB
NXP LPCXpresso1549 NXP LPC External LPC1549 72MHz 256KB 36KB
NXP LPCXpresso54114 NXP LPC On-board LPC54114J256BD64 100MHz 256KB 192KB
NXP LPCXpresso54608 NXP LPC On-board LPC54608ET512 180MHz 512KB 200KB
NXP i.MX RT1050 Evaluation Kit NXP i.MX RT On-board MIMXRT1052DVL6B 600MHz 64MB 512KB
NXP mbed LPC11U24 NXP LPC On-board LPC11U24 48MHz 32KB 8KB
NXP mbed LPC1768 NXP LPC On-board LPC1768 96MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
Nordic nRF51 Dongle (PCA10031) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF51822-mKIT Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
OLIMEXINO-STM32 ST STM32 External STM32F103RBT6 72MHz 128KB 20KB

Outrageous Circuits

Name Platform Debug MCU Frequency Flash RAM
Outrageous Circuits mBuino NXP LPC No LPC11U24 48MHz 32KB 8KB

Name Platform Debug MCU Frequency Flash RAM
RedBearLab BLE Nano 1.5 Nordic nRF51 On-board NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab nRF51822 Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

Name Platform Debug MCU Frequency Flash RAM
RushUp Cloud-JAM ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
RushUp Cloud-JAM L4 ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
32F412GDISCOVERY ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
ST 32F3348DISCOVERY ST STM32 On-board STM32F334C8T6 72MHz 64KB 12KB
ST 32F401CDISCOVERY ST STM32 On-board STM32F401VCT6 84MHz 256KB 64KB
ST 32F413HDISCOVERY ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 On-board STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY ST STM32 On-board STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY ST STM32 On-board STM32F769NIH6 216MHz 1MB 512KB
ST 32L0538DISCOVERY ST STM32 On-board STM32L053C8T6 32MHz 64KB 8KB
ST 32L476GDISCOVERY ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY ST STM32 On-board STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 On-board STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 On-board STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F031K6 ST STM32 On-board STM32F031K6T6 48MHz 32KB 4KB
ST Nucleo F042K6 ST STM32 On-board STM32F042K6T6 48MHz 32KB 6KB
ST Nucleo F070RB ST STM32 On-board STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F091RC ST STM32 On-board STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 On-board STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 On-board STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 On-board STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 ST STM32 On-board STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE ST STM32 On-board STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F303ZE ST STM32 On-board STM32F303ZET6 72MHz 512KB 64KB
ST Nucleo F334R8 ST STM32 On-board STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F410RB ST STM32 On-board STM32F410RBT6 100MHz 128KB 32KB
ST Nucleo F411RE ST STM32 On-board STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F439ZI ST STM32 On-board STM32F439ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 On-board STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F446ZE ST STM32 On-board STM32F446ZET6 180MHz 512KB 128KB
ST Nucleo F746ZG ST STM32 On-board STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG ST STM32 On-board STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI ST STM32 On-board STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI ST STM32 On-board STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L031K6 ST STM32 On-board STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 ST STM32 On-board STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 On-board STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE ST STM32 On-board STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L432KC ST STM32 On-board STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L433RC-P ST STM32 On-board STM32L433RC 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L486RG ST STM32 On-board STM32L486RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 On-board STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P ST STM32 On-board STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI ST STM32 On-board STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST STM32F0DISCOVERY ST STM32 On-board STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY ST STM32 On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32VLDISCOVERY ST STM32 On-board STM32F100RBT6 24MHz 128KB 8KB

Name Platform Debug MCU Frequency Flash RAM
Seeed Arch BLE Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB
Seeed Arch GPRS V2 NXP LPC No LPC11U37 48MHz 128KB 10KB
Seeed Arch Link Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Arch Max ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB
Seeed Arch Pro NXP LPC On-board LPC1768 96MHz 512KB 64KB
Seeed Tiny BLE Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Wio 3G ST STM32 On-board STM32F439VI 180MHz 2MB 256KB
Seeed Xadow M0 NXP LPC No LPC11U35 48MHz 64KB 10KB

Name Platform Debug MCU Frequency Flash RAM
NAMote72 ST STM32 External STM32L152RC 32MHz 256KB 32KB

Sigma Delta Technologies

Name Platform Debug MCU Frequency Flash RAM
SDT32620B Maxim 32 No MAX32620IWG 96MHz 2MB 256KB
SDT32625B Maxim 32 No MAX32625ITK 96MHz 512KB 160KB
SDT52832B Nordic nRF52 External NRF52832 64MHz 512KB 64KB

Silicon Labs

Name Platform Debug MCU Frequency Flash RAM
EFM32GG-STK3700 Giant Gecko Silicon Labs EFM32 On-board EFM32GG990F1024 48MHz 1MB 128KB
EFM32LG-STK3600 Leopard Gecko Silicon Labs EFM32 On-board EFM32LG990F256 48MHz 256KB 32KB
EFM32WG-STK3800 Wonder Gecko Silicon Labs EFM32 On-board EFM32WG990F256 48MHz 256KB 32KB
EFM32ZG-STK3200 Zero Gecko Silicon Labs EFM32 On-board EFM32ZG222F32 24MHz 32KB 4KB
SLSTK3400A USB-enabled Happy Gecko Silicon Labs EFM32 On-board EFM32HG322F64 25MHz 64KB 8KB
SLSTK3401A Pearl Gecko PG1 Silicon Labs EFM32 On-board EFM32PG1B200F256GM48 40MHz 256KB 32KB
Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT Silicon Labs EFM32 On-board EFR32MG12P432F1024 40MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
Smeshlink xbed LPC1768 NXP LPC No LPC1768 96MHz 512KB 32KB

Solder Splash Labs

Name Platform Debug MCU Frequency Flash RAM
DipCortex M3 NXP LPC External LPC1347 72MHz 64KB 12KB
Solder Splash Labs DipCortex M0 NXP LPC External LPC11U24 50MHz 32KB 8KB

Switch Science

Name Platform Debug MCU Frequency Flash RAM
Switch Science mbed HRM1017 Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Switch Science mbed LPC1114FN28 NXP LPC On-board LPC1114FN28 48MHz 32KB 4KB
Switch Science mbed LPC824 NXP LPC On-board LPC824 30MHz 32KB 8KB
Switch Science mbed TY51822r3 Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Teensy 3.1 / 3.2 Teensy External MK20DX256 72MHz 256KB 64KB

Name Platform Debug MCU Frequency Flash RAM
VNG VBLUNO51 Nordic nRF51 On-board NRF51822 16MHz 128KB 32KB

Name Platform Debug MCU Frequency Flash RAM
WIZwiki-W7500 WIZNet W7500 On-board WIZNET7500 48MHz 128KB 48KB
WIZwiki-W7500ECO WIZNet W7500 On-board WIZNET7500ECO 48MHz 128KB 48KB
WIZwiki-W7500P WIZNet W7500 On-board WIZNET7500P 48MHz 128KB 48KB

Name Platform Debug MCU Frequency Flash RAM
L476DMW1K ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
sakura.io Evaluation Board ST STM32 On-board STM32F411RET6 100MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
Mbed Connect Cloud ST STM32 On-board STM32F439ZIY6 168MHz 2MB 256KB
u-blox C027 NXP LPC On-board LPC1768 96MHz 512KB 64KB
u-blox C030-N211 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox C030-R410M IoT ST STM32 On-board STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox EVK-NINA-B1 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
u-blox EVK-ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB
u-blox ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB

y5 design

Name Platform Debug MCU Frequency Flash RAM
y5 LPC11U35 mbug NXP LPC External LPC11U35 48MHz 64KB 10KB
y5 nRF51822 mbug Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

framework = nuclei-sdk

Open Source Software Development Kit for the Nuclei N/NX processors

For more detailed information please visit vendor site.

  • Debugging
  • Examples
  • Platforms
  • Boards

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
GD32VF103V RVStar Kit Nuclei GD32VF103VBT6 108MHz 128KB 32KB
HummingBird Evaluation Kit Nuclei HUMMINGBIRD 5MHz 64KB 64KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
GD32VF103V Evaluation Kit Nuclei GD32VF103VBT6 108MHz 128KB 32KB

•
Nuclei SDK for Nuclei

Name Description
Nuclei Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
GD32VF103V Evaluation Kit Nuclei External GD32VF103VBT6 108MHz 128KB 32KB

Name Platform Debug MCU Frequency Flash RAM
GD32VF103V RVStar Kit Nuclei On-board GD32VF103VBT6 108MHz 128KB 32KB
HummingBird Evaluation Kit Nuclei On-board HUMMINGBIRD 5MHz 64KB 64KB

framework = pulp-os

PULP is a silicon-proven Parallel Ultra Low Power platform targeting high energy efficiencies. The platform is organized in clusters of RISC-V cores that share a tightly-coupled data memory.

For more detailed information please visit vendor site.

  • Debugging
  • Examples
  • Platforms
  • Boards

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
GAPuino GAP8 RISC-V GAP GAP8 250MHz 64MB 8MB

•
PULP OS for RISC-V GAP

Name Description
RISC-V 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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



GreenWaves Technologies

Name Platform Debug MCU Frequency Flash RAM
GAPuino GAP8 RISC-V GAP On-board GAP8 250MHz 64MB 8MB

framework = pumbaa

Pumbaa is Python on top of Simba. The implementation is a port of MicroPython, designed for embedded devices with limited amount of RAM and code memory.

For more detailed information please visit vendor site.

  • Examples
  • Platforms
  • Boards

•
Pumbaa for Espressif 32

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
MakerAsia Nano32 Espressif 32 No ESP32 240MHz 4MB 320KB

framework = shakti-sdk

A software development kit for developing applications on Shakti class of processors

For more detailed information please visit vendor site.

  • Debugging
  • Examples
  • Platforms
  • Boards

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
•
On-Board Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
Artix-7 35T Arty FPGA Evaluation Kit Shakti E-CLASS 50MHz 0B 128KB
Arty A7-100: Artix-7 FPGA Development Board Shakti C-CLASS 50MHz 0B 128MB

•
Shakti SDK for Shakti

Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
Artix-7 35T Arty FPGA Evaluation Kit Shakti On-board E-CLASS 50MHz 0B 128KB
Arty A7-100: Artix-7 FPGA Development Board Shakti On-board C-CLASS 50MHz 0B 128MB

framework = simba

Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

For more detailed information please visit vendor site.

  • Debugging
  • Examples
  • Platforms
  • Boards

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) Atmel AVR ATMEGA2560 16MHz 248KB 8KB
Arduino Nano ATmega328 Atmel AVR ATMEGA328P 16MHz 30KB 2KB
Arduino Nano ATmega328 (New Bootloader) Atmel AVR ATMEGA328P 16MHz 30KB 2KB
Arduino Uno Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB
Seeeduino Atmel AVR ATMEGA328P 16MHz 31.50KB 2KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
Arduino Due (Programming Port) Atmel SAM AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) Atmel SAM AT91SAM3X8E 84MHz 512KB 96KB

  • Simba for Atmel AVR
  • Simba for Atmel SAM
  • Simba for Espressif 32
  • Simba for Espressif 8266

Name Description
Atmel AVR Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming
Atmel SAM Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Espressif 8266 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
Adafruit HUZZAH ESP8266 Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Arduino Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Arduino Nano ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Nano ATmega328 (New Bootloader) Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Uno Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
ESP-WROOM-02 Espressif 8266 No ESP8266 80MHz 2MB 80KB
Espressif ESP8266 ESP-12E Espressif 8266 No ESP8266 80MHz 4MB 80KB
Espressif Generic ESP8266 ESP-01 512k Espressif 8266 No ESP8266 80MHz 512KB 80KB

Invent One

Name Platform Debug MCU Frequency Flash RAM
Invent One Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
MakerAsia Nano32 Espressif 32 No ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
NodeMCU 0.9 (ESP-12 Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB
NodeMCU 1.0 (ESP-12E Module) Espressif 8266 No ESP8266 80MHz 4MB 80KB

Name Platform Debug MCU Frequency Flash RAM
Seeeduino Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

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.

For more detailed information please visit vendor site.

  • Examples
  • Debugging
  • Examples
  • Platforms
  • Boards

All project examples are located in PlatformIO repository Examples for SPL framework.

•
Blink

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
Armstrap Eagle 1024 ST STM32 STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 ST STM32 STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 ST STM32 STM32F407VET6 168MHz 512KB 192KB
RushUp Cloud-JAM ST STM32 STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F401RE ST STM32 STM32F401RET6 84MHz 512KB 96KB
ST STM32F3DISCOVERY ST STM32 STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 STM32F407VGT6 168MHz 1MB 128KB
ST STM32LDISCOVERY ST STM32 STM32L152RBT6 32MHz 128KB 16KB
ST STM8S-DISCOVERY ST STM8 STM8S105C6T6 16MHz 32KB 2KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
1Bitsy ST STM32 STM32F415RGT 168MHz 1MB 128KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 STM32F401RE 84MHz 512KB 96KB

  • SPL for ST STM32
  • SPL for ST STM8

Name Description
ST STM32 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.
ST STM8 The STM8 is an 8-bit microcontroller family by STMicroelectronics an extended variant of the ST7 microcontroller architecture. STM8 microcontrollers are particularly low cost for a full-featured 8-bit microcontroller.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
1Bitsy ST STM32 External STM32F415RGT 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
Armstrap Eagle 1024 ST STM32 On-board STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 ST STM32 On-board STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB

Name Platform Debug MCU Frequency Flash RAM
STM32F401RB (64k RAM. 128k Flash) ST STM32 External STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 External STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 External STM32F401RE 84MHz 512KB 96KB

Name Platform Debug MCU Frequency Flash RAM
RushUp Cloud-JAM ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB

Name Platform Debug MCU Frequency Flash RAM
ST Nucleo F401RE ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
ST STM32F3DISCOVERY ST STM32 On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32LDISCOVERY ST STM32 On-board STM32L152RBT6 32MHz 128KB 16KB
ST STM8S-DISCOVERY ST STM8 On-board STM8S105C6T6 16MHz 32KB 2KB
ST STM8S103F3 Breakout Board ST STM8 No STM8S103F3P6 16MHz 8KB 1KB
ST STM8S105K4T6 Breakout Board ST STM8 No STM8S105K4T6 16MHz 16KB 2KB

Name Platform Debug MCU Frequency Flash RAM
sduino MB (STM8S208MBT6B) ST STM8 No STM8S208MBT6 16MHz 128KB 6KB
sduino UNO (STM8S105K6) ST STM8 No STM8S105K6T6 16MHz 32KB 2KB

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.

For more detailed information please visit vendor site.

  • Tutorials
  • Using with STM32CubeMX
  • Debugging
  • Examples
  • Platforms
  • Boards

•
STM32Cube HAL and Nucleo-F401RE: debugging and unit testing

At the moment there is no seamless integration with projects generated by STM32CubeMX tool. Instead, a small cross-platform Python application called stm32pio can be used to create and update PlatformIO projects from STM32CubeMX .ioc files. It uses STM32CubeMX to generate a HAL-framework-based code and alongside creates PlatformIO project with compatible parameters to stick them both together.

More details about stm32pio tool can be found in the official repository.

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
32F412GDISCOVERY ST STM32 STM32F412ZGT6 100MHz 1MB 256KB
32F723EDISCOVERY ST STM32 STM32F723IEK6 216MHz 512KB 192KB
3D printer controller ST STM32 STM32F765VIT6 216MHz 2MB 512KB
3DP001V1 Evaluation board for 3D printer ST STM32 STM32F401VGT6 84MHz 512KB 96KB
96Boards B96B-F446VE ST STM32 STM32F446VET6 168MHz 512KB 128KB
Armstrap Eagle 1024 ST STM32 STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 ST STM32 STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 ST STM32 STM32F407VET6 168MHz 512KB 192KB
L476DMW1K ST STM32 STM32L476VGT6 80MHz 1MB 128KB
Mbed Connect Cloud ST STM32 STM32F439ZIY6 168MHz 2MB 256KB
Microsoft Azure IoT Development Kit (MXChip AZ3166) ST STM32 STM32F412ZGT6 100MHz 1MB 256KB
RushUp Cloud-JAM ST STM32 STM32F401RET6 84MHz 512KB 96KB
RushUp Cloud-JAM L4 ST STM32 STM32L476RGT6 80MHz 1MB 128KB
ST 32F3348DISCOVERY ST STM32 STM32F334C8T6 72MHz 64KB 12KB
ST 32F401CDISCOVERY ST STM32 STM32F401VCT6 84MHz 256KB 64KB
ST 32F411EDISCOVERY ST STM32 STM32F411VET6 100MHz 512KB 128KB
ST 32F413HDISCOVERY ST STM32 STM32F413ZHT6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY ST STM32 STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY ST STM32 STM32F769NIH6 216MHz 1MB 512KB
ST 32L0538DISCOVERY ST STM32 STM32L053C8T6 32MHz 64KB 8KB
ST 32L100DISCOVERY ST STM32 STM32L100RCT6 32MHz 256KB 16KB
ST 32L476GDISCOVERY ST STM32 STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY ST STM32 STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F031K6 ST STM32 STM32F031K6T6 48MHz 32KB 4KB
ST Nucleo F042K6 ST STM32 STM32F042K6T6 48MHz 32KB 6KB
ST Nucleo F070RB ST STM32 STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F072RB ST STM32 STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F091RC ST STM32 STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 ST STM32 STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE ST STM32 STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F303ZE ST STM32 STM32F303ZET6 72MHz 512KB 64KB
ST Nucleo F334R8 ST STM32 STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE ST STM32 STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F410RB ST STM32 STM32F410RBT6 100MHz 128KB 32KB
ST Nucleo F411RE ST STM32 STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG ST STM32 STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH ST STM32 STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F439ZI ST STM32 STM32F439ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F446ZE ST STM32 STM32F446ZET6 180MHz 512KB 128KB
ST Nucleo F722ZE ST STM32 STM32F722ZET6 216MHz 512KB 256KB
ST Nucleo F746ZG ST STM32 STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG ST STM32 STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI ST STM32 STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI ST STM32 STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L011K4 ST STM32 STM32L011K4T6 32MHz 16KB 2KB
ST Nucleo L031K6 ST STM32 STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 ST STM32 STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE ST STM32 STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L412KB ST STM32 STM32L412KBU6 80MHz 128KB 40KB
ST Nucleo L432KC ST STM32 STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L433RC-P ST STM32 STM32L433RC 80MHz 256KB 64KB
ST Nucleo L452RE ST STM32 STM32L452RET6 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L486RG ST STM32 STM32L486RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P ST STM32 STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI ST STM32 STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY ST STM32 STM32F030R8T6 48MHz 64KB 8KB
ST STM32F0DISCOVERY ST STM32 STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY ST STM32 STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 STM32F407VGT6 168MHz 1MB 128KB
ST STM32L073Z-EVAL ST STM32 STM32L073VZT6 32MHz 192KB 20KB
ST STM32LDISCOVERY ST STM32 STM32L152RBT6 32MHz 128KB 16KB
ST STM32VLDISCOVERY ST STM32 STM32F100RBT6 24MHz 128KB 8KB
ST Sensor Node ST STM32 STM32L476JG 80MHz 1MB 128KB
STM32F7508-DK ST STM32 STM32F750N8H6 216MHz 64KB 340KB
STM32H747I-DISCO ST STM32 STM32H747XIH6 400MHz 2MB 512KB
Seeed Arch Max ST STM32 STM32F407VET6 168MHz 512KB 192KB
Seeed Wio 3G ST STM32 STM32F439VI 180MHz 2MB 256KB
sakura.io Evaluation Board ST STM32 STM32F411RET6 100MHz 1MB 128KB
u-blox C030-R410M IoT ST STM32 STM32F437VG 180MHz 1MB 256KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
1Bitsy ST STM32 STM32F415RGT 168MHz 1MB 128KB
3D Printer Controller ST STM32 STM32F407VET6 168MHz 512KB 192KB
3D Printer control board ST STM32 STM32F446RET6 180MHz 512KB 128KB
96Boards Argonkey (STEVAL-MKI187V1) ST STM32 STM32F412CG 100MHz 1MB 256KB
96Boards Neonkey ST STM32 STM32F411CE 100MHz 512KB 128KB
Adafruit Feather STM32F405 ST STM32 STM32F405RGT6 168MHz 1MB 128KB
AfroFlight Rev5 (8MHz) ST STM32 STM32F103CBT6 72MHz 128KB 20KB
Black STM32F407VE ST STM32 STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG ST STM32 STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 STM32F103C8T6 72MHz 128KB 20KB
BlackPill F303CC ST STM32 STM32F303CCT6 72MHz 256KB 40KB
BlackPill F401CC ST STM32 STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini ST STM32 STM32F407VET6 168MHz 512KB 128KB
BluePill F103C6 ST STM32 STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 STM32F103C8T6 72MHz 128KB 20KB
Core board F401RCT6 ST STM32 STM32F401RCT6 84MHz 256KB 64KB
Demo F030F4 ST STM32 STM32F030F4P6 48MHz 16KB 4KB
Espotel LoRa Module ST STM32 STM32F411RET6 100MHz 512KB 128KB
F407VG ST STM32 STM32F407VGT6 168MHz 512KB 128KB
FK407M1 ST STM32 STM32F407VET6 168MHz 512KB 128KB
M200 V2 ST STM32 STM32F070CBT6 48MHz 120KB 14.81KB
M300 ST STM32 STM32F070CBT6 48MHz 120KB 14.81KB
MTS Dragonfly ST STM32 STM32F411RET6 100MHz 512KB 128KB
Malyan M200 V1 ST STM32 STM32F103CBT6 72MHz 120KB 20KB
Maple ST STM32 STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) ST STM32 STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 ST STM32 STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original ST STM32 STM32F103CBT6 72MHz 108KB 17KB
Microduino Core STM32 to Flash ST STM32 STM32F103CBT6 72MHz 105.47KB 16.60KB
MultiTech mDot ST STM32 STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot F411 ST STM32 STM32F411RET6 100MHz 512KB 128KB
MultiTech xDot ST STM32 STM32L151CCU6 32MHz 256KB 32KB
N2+ ST STM32 STM32F405RGT6 168MHz 1MB 192KB
NAMote72 ST STM32 STM32L152RC 32MHz 256KB 32KB
OLIMEXINO-STM32 ST STM32 STM32F103RBT6 72MHz 128KB 20KB
Olimex STM32-P405 ST STM32 STM32F405RGT6 168MHz 1MB 192KB
Piconomix PX-HER0 ST STM32 STM32L072RB 32MHz 128KB 20KB
PrntrBoard V2 ST STM32 STM32F407RE 168MHz 512KB 192KB
RAK811 LoRa Tracker ST STM32 STM32L151RBT6 32MHz 128KB 16KB
RAK811 LoRa Tracker ST STM32 STM32L151RBT6 32MHz 128KB 32KB
RHF76 052 ST STM32 STM32L051C8T6 32MHz 64KB 8KB
STEVAL-FCU001V1 Flight controller unit evaluation board ST STM32 STM32F401CCU6 84MHz 256KB 64KB
STM32-E407 ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
STM3210C-EVAL ST STM32 STM32F107VCT6 72MHz 256KB 64KB
STM32373C-EVAL ST STM32 STM32F373VCT6 72MHz 256KB 32KB
STM32F072-EVAL ST STM32 STM32F072VBT6 48MHz 128KB 16KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 STM32F103ZET6 72MHz 512KB 64KB
STM32F303CB (32k RAM. 128k Flash) ST STM32 STM32F303CBT6 72MHz 128KB 32KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) ST STM32 STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) ST STM32 STM32F407VGT6 168MHz 1MB 192KB
STM32F4Stamp F405 ST STM32 STM32F405RGT6 168MHz 1MB 192KB
SensorTile.box ST STM32 STM32L4R9ZI 120MHz 2MB 640KB
Sparky V1 F303 ST STM32 STM32F303CCT6 72MHz 256KB 40KB
ThunderPack ST STM32 STM32L072KZ 32MHz 192KB 20KB
Tiny STM103T ST STM32 STM32F103TBU6 72MHz 128KB 20KB
VAkE v1.0 ST STM32 STM32F446RET6 180MHz 512KB 128KB
Wraith V1 ESC ST STM32 STM32F051K6 48MHz 32KB 7.75KB
u-blox C030-N211 IoT Starter Kit ST STM32 STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit ST STM32 STM32F437VG 180MHz 1MB 256KB
u-blox EVK-ODIN-W2 ST STM32 STM32F439ZIY6 168MHz 2MB 256KB
u-blox ODIN-W2 ST STM32 STM32F439ZIY6 168MHz 2MB 256KB

•
STM32Cube for ST STM32

Name Description
ST STM32 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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
1Bitsy ST STM32 External STM32F415RGT 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
96Boards Argonkey (STEVAL-MKI187V1) ST STM32 External STM32F412CG 100MHz 1MB 256KB
96Boards B96B-F446VE ST STM32 On-board STM32F446VET6 168MHz 512KB 128KB
96Boards Neonkey ST STM32 External STM32F411CE 100MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
Adafruit Feather STM32F405 ST STM32 External STM32F405RGT6 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
AfroFlight Rev5 (8MHz) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
Wraith V1 ESC ST STM32 External STM32F051K6 48MHz 32KB 7.75KB

Name Platform Debug MCU Frequency Flash RAM
3D Printer Controller ST STM32 External STM32F407VET6 168MHz 512KB 192KB

Name Platform Debug MCU Frequency Flash RAM
Armstrap Eagle 1024 ST STM32 On-board STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 ST STM32 On-board STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB

Avnet Silica

Name Platform Debug MCU Frequency Flash RAM
ST Sensor Node ST STM32 On-board STM32L476JG 80MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
Espotel LoRa Module ST STM32 External STM32F411RET6 100MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
BlackPill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
BluePill F103C6 ST STM32 External STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
Demo F030F4 ST STM32 External STM32F030F4P6 48MHz 16KB 4KB
FK407M1 ST STM32 External STM32F407VET6 168MHz 512KB 128KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 External STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 External STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 External STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 External STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 External STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 External STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 External STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 External STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 External STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 External STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 External STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 External STM32F103ZET6 72MHz 512KB 64KB
STM32F303CB (32k RAM. 128k Flash) ST STM32 External STM32F303CBT6 72MHz 128KB 32KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 External STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 External STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 External STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) ST STM32 External STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) ST STM32 External STM32F407VGT6 168MHz 1MB 192KB
STM32F4Stamp F405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB

Name Platform Debug MCU Frequency Flash RAM
Tiny STM103T ST STM32 External STM32F103TBU6 72MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
Maple ST STM32 External STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) ST STM32 External STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original ST STM32 External STM32F103CBT6 72MHz 108KB 17KB

Name Platform Debug MCU Frequency Flash RAM
Microsoft Azure IoT Development Kit (MXChip AZ3166) ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
M200 V2 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
M300 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
Malyan M200 V1 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB

Name Platform Debug MCU Frequency Flash RAM
Microduino Core STM32 to Flash ST STM32 External STM32F103CBT6 72MHz 105.47KB 16.60KB

Name Platform Debug MCU Frequency Flash RAM
MTS Dragonfly ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot F411 ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech xDot ST STM32 External STM32L151CCU6 32MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
N2+ ST STM32 External STM32F405RGT6 168MHz 1MB 192KB

Name Platform Debug MCU Frequency Flash RAM
OLIMEXINO-STM32 ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
Olimex STM32-P405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB
STM32-E407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
Piconomix PX-HER0 ST STM32 External STM32L072RB 32MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
PrntrBoard V2 ST STM32 External STM32F407RE 168MHz 512KB 192KB

Name Platform Debug MCU Frequency Flash RAM
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 16KB
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 32KB

Name Platform Debug MCU Frequency Flash RAM
3D Printer control board ST STM32 External STM32F446RET6 180MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
3D printer controller ST STM32 On-board STM32F765VIT6 216MHz 2MB 512KB

Name Platform Debug MCU Frequency Flash RAM
BlackPill F303CC ST STM32 External STM32F303CCT6 72MHz 256KB 40KB

Name Platform Debug MCU Frequency Flash RAM
RushUp Cloud-JAM ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
RushUp Cloud-JAM L4 ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
32F412GDISCOVERY ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
32F723EDISCOVERY ST STM32 On-board STM32F723IEK6 216MHz 512KB 192KB
3DP001V1 Evaluation board for 3D printer ST STM32 On-board STM32F401VGT6 84MHz 512KB 96KB
Black STM32F407VE ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F401CC ST STM32 External STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Core board F401RCT6 ST STM32 External STM32F401RCT6 84MHz 256KB 64KB
RHF76 052 ST STM32 External STM32L051C8T6 32MHz 64KB 8KB
ST 32F3348DISCOVERY ST STM32 On-board STM32F334C8T6 72MHz 64KB 12KB
ST 32F401CDISCOVERY ST STM32 On-board STM32F401VCT6 84MHz 256KB 64KB
ST 32F411EDISCOVERY ST STM32 On-board STM32F411VET6 100MHz 512KB 128KB
ST 32F413HDISCOVERY ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 On-board STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY ST STM32 On-board STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY ST STM32 On-board STM32F769NIH6 216MHz 1MB 512KB
ST 32L0538DISCOVERY ST STM32 On-board STM32L053C8T6 32MHz 64KB 8KB
ST 32L100DISCOVERY ST STM32 On-board STM32L100RCT6 32MHz 256KB 16KB
ST 32L476GDISCOVERY ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY ST STM32 On-board STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 On-board STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 On-board STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F031K6 ST STM32 On-board STM32F031K6T6 48MHz 32KB 4KB
ST Nucleo F042K6 ST STM32 On-board STM32F042K6T6 48MHz 32KB 6KB
ST Nucleo F070RB ST STM32 On-board STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F091RC ST STM32 On-board STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 On-board STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 On-board STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 On-board STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 ST STM32 On-board STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE ST STM32 On-board STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F303ZE ST STM32 On-board STM32F303ZET6 72MHz 512KB 64KB
ST Nucleo F334R8 ST STM32 On-board STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F410RB ST STM32 On-board STM32F410RBT6 100MHz 128KB 32KB
ST Nucleo F411RE ST STM32 On-board STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F439ZI ST STM32 On-board STM32F439ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 On-board STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F446ZE ST STM32 On-board STM32F446ZET6 180MHz 512KB 128KB
ST Nucleo F722ZE ST STM32 On-board STM32F722ZET6 216MHz 512KB 256KB
ST Nucleo F746ZG ST STM32 On-board STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG ST STM32 On-board STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI ST STM32 On-board STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI ST STM32 On-board STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L011K4 ST STM32 On-board STM32L011K4T6 32MHz 16KB 2KB
ST Nucleo L031K6 ST STM32 On-board STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 ST STM32 On-board STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 On-board STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE ST STM32 On-board STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L412KB ST STM32 On-board STM32L412KBU6 80MHz 128KB 40KB
ST Nucleo L432KC ST STM32 On-board STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L433RC-P ST STM32 On-board STM32L433RC 80MHz 256KB 64KB
ST Nucleo L452RE ST STM32 On-board STM32L452RET6 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L486RG ST STM32 On-board STM32L486RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 On-board STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P ST STM32 On-board STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI ST STM32 On-board STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST STM32F0DISCOVERY ST STM32 On-board STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY ST STM32 On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32L073Z-EVAL ST STM32 On-board STM32L073VZT6 32MHz 192KB 20KB
ST STM32LDISCOVERY ST STM32 On-board STM32L152RBT6 32MHz 128KB 16KB
ST STM32VLDISCOVERY ST STM32 On-board STM32F100RBT6 24MHz 128KB 8KB
STEVAL-FCU001V1 Flight controller unit evaluation board ST STM32 External STM32F401CCU6 84MHz 256KB 64KB
STM3210C-EVAL ST STM32 External STM32F107VCT6 72MHz 256KB 64KB
STM32373C-EVAL ST STM32 External STM32F373VCT6 72MHz 256KB 32KB
STM32F072-EVAL ST STM32 External STM32F072VBT6 48MHz 128KB 16KB
STM32F7508-DK ST STM32 On-board STM32F750N8H6 216MHz 64KB 340KB
STM32H747I-DISCO ST STM32 On-board STM32H747XIH6 400MHz 2MB 512KB
SensorTile.box ST STM32 External STM32L4R9ZI 120MHz 2MB 640KB

Name Platform Debug MCU Frequency Flash RAM
Seeed Arch Max ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB
Seeed Wio 3G ST STM32 On-board STM32F439VI 180MHz 2MB 256KB

Name Platform Debug MCU Frequency Flash RAM
NAMote72 ST STM32 External STM32L152RC 32MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Sparky V1 F303 ST STM32 External STM32F303CCT6 72MHz 256KB 40KB

Name Platform Debug MCU Frequency Flash RAM
ThunderPack ST STM32 External STM32L072KZ 32MHz 192KB 20KB

Name Platform Debug MCU Frequency Flash RAM
VAkE v1.0 ST STM32 External STM32F446RET6 180MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
L476DMW1K ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
sakura.io Evaluation Board ST STM32 On-board STM32F411RET6 100MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
Mbed Connect Cloud ST STM32 On-board STM32F439ZIY6 168MHz 2MB 256KB
u-blox C030-N211 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox C030-R410M IoT ST STM32 On-board STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox EVK-ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB
u-blox ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB

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.

For more detailed information please visit vendor site.

  • Examples
  • Platforms
  • Boards

•
WiringPi for Linux ARM

Name Description
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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Raspberry Pi

Name Platform Debug MCU Frequency Flash RAM
Raspberry Pi 1 Model B Linux ARM No BCM2835 700MHz 512MB 512MB
Raspberry Pi 2 Model B Linux ARM No BCM2836 900MHz 1GB 1GB
Raspberry Pi 3 Model B Linux ARM No BCM2837 1200MHz 1GB 1GB
Raspberry Pi Zero Linux ARM No BCM2835 1000MHz 512MB 512MB

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.

For more detailed information please visit vendor site.

  • Tutorials
  • Configuration
  • Debugging
  • Examples
  • Platforms
  • Boards

•
Zephyr and Nordic nRF52-DK: debugging, unit testing, project analysis

  • Project Structure
  • Embedding files at compile time
  • Zephyr modules
  • Limitations

Project Structure

WARNING:

Zephyr framework currently requires Python 3.4 or later.


Zephyr framework requires an unusual project structure because most of the framework configuration is performed by the native for Zephyr build system called CMake.

NOTE:

Since PlatformIO is able to generate CMake-based projects for certain IDEs, Zephyr-related files are moved to a separate folder in order to avoid conflicts between project files. That requires users to specify relative paths to source files in CMakeLists.txt.


A typical PlatformIO project for Zephyr framework must have the following structure:

project_dir
├── include
├── src
│    └── main.c
├── zephyr
│    ├── prj.conf
│    └── CMakeLists.txt
└── platformio.ini


Besides files related to PlatformIO project, there is an additional folder zephyr that contains Zephyr-specific files CMakeLists.txt and prj.conf:

CMakeLists.txt file enables features supported by Zephyr's build system, e.g. board-specific kernel configuration files. A typical CMakeLists.txt file has the following content:

# Boilerplate code, which pulls in the Zephyr build system.
cmake_minimum_required(VERSION 3.13.1)
include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(my_zephyr_app)
# Add your source file to the "app" target. This must come after the boilerplate
# code, which defines the target. Note relative path to source file
target_sources(app PRIVATE ../src/main.c)


The files specified in target_sources are used ONLY for generating build configurations, but it's highly recommended to specify all application source files in order to keep the project compatible with the usual Zephyr workflow.

Due to the current limitations of CMake file-based API, there is no way to generate build configuration for source files written in various programming languages if they are not specified in target_sources command. If your project contains libraries written in languages that differ from the language used for the main application you need to create an empty file with desired extension (e.g. *.cpp for C++) in order to force CMake generate build configuration for this language.

NOTE:

Build configuration generated for source files specified in target_sources is also used as the base build environment for project sources (including libraries).


prj.conf file sets application-specific values for one or more kernel configuration options. These application settings are merged with board-specific settings to produce a kernel configuration.

In case your CMakeLists.txt relies on using generate_inc_* functions that are used for generating and compressing individual files (for example certificates for secure connections) you need to configure your PlatformIO project accordingly using the following structure:

[env:myenv]
platform = ...
board = ...
framework = zephyr
board_build.embed_files =
    # files to be embedded
    src/apps-cert.der
    src/apps-key.der


Where apps-cert.der and apps-key.der are the files you want to embed to your project at the compile time.

NOTE:

PlatformIO automatically installs several default modules used with Zephyr framework including modules that implement silicon vendor Hardware Abstraction Layers (HALs).


Zephyr modules are externally maintained packages that allow using well-established and mature code created by third party developers.

These modules contain either a single module.yml file or CMakeLists.txt and Kconfig files that describe how to build and configure them. You can specify paths to additional directories with source code, Kconfig, etc. using ZEPHYR_EXTRA_MODULES at the top of your project's CMakeLists.txt file, for example:

# Additional modules
set(ZEPHYR_EXTRA_MODULES "path/to-zephyr-custom-module"  [...])
# Boilerplate code, which pulls in the Zephyr build system.
cmake_minimum_required(VERSION 3.13.1)
include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(my_zephyr_app)
# Add your source file to the "app" target. This must come after
# the boilerplate code, which defines the target.
target_sources(app PRIVATE ../src/main.c)


Since the build may not work correctly if the full path to sources is greater than 250 characters (see CMAKE_OBJECT_PATH_MAX) it might be a good idea to keep modules close to the project configuration files (e.g. in zephyr folder) in form of a git submodule.

WARNING:

Make sure the ZEPHYR_EXTRA_MODULES variable is set before including the boilerplate file, as shown above.


At the moment several limitations are present:

  • The minimum supported version of Python is 3.4
  • No whitespace characters allowed in project paths.
  • OpenThread module is not supported

PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

•
Tools & Debug Probes
  • On-Board Debug Tools
  • External Debug Tools


Tools & Debug Probes

Supported debugging tools are listed in "Debug" column. For more detailed information, please scroll table by horizontal. You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions.


On-Board Debug Tools

Boards listed below have on-board debug probe and ARE READY for debugging! You do not need to use/buy external debug probe.

Name Platform MCU Frequency Flash RAM
32F412GDISCOVERY ST STM32 STM32F412ZGT6 100MHz 1MB 256KB
32F723EDISCOVERY ST STM32 STM32F723IEK6 216MHz 512KB 192KB
96Boards B96B-F446VE ST STM32 STM32F446VET6 168MHz 512KB 128KB
Arduino Zero (Programming/Debug Port) Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Atmel ATSAMR21-XPRO Atmel SAM SAMR21G18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO Atmel SAM SAMD21J18A 48MHz 256KB 32KB
BBC micro:bit Nordic nRF51 NRF51822 16MHz 256KB 16KB
BL652 Development Kit Nordic nRF52 NRF52832 64MHz 512KB 64KB
BL654 Development Kit Nordic nRF52 NRF52840 64MHz 1MB 256KB
EFM32WG-STK3800 Wonder Gecko Silicon Labs EFM32 EFM32WG990F256 48MHz 256KB 32KB
ElectronutLabs Blip Nordic nRF52 NRF52840 64MHz 1MB 256KB
ElectronutLabs Papyr Nordic nRF52 NRF52840 64MHz 1MB 256KB
Freescale Kinetis FRDM-K22F Freescale Kinetis MK22FN512VLH12 120MHz 512KB 128KB
Freescale Kinetis FRDM-K64F Freescale Kinetis MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K82F Freescale Kinetis MK82FN256VLL15 150MHz 256KB 256KB
Freescale Kinetis FRDM-KL25Z Freescale Kinetis MKL25Z128VLK4 48MHz 128KB 16KB
Freescale Kinetis FRDM-KW41Z Freescale Kinetis MKW41Z512VHT4 48MHz 512KB 128KB
HiFive1 SiFive FE310 320MHz 16MB 16KB
HiFive1 Rev B SiFive FE310 320MHz 16MB 16KB
Makerdiary nRF52832-MDK Nordic nRF52 NRF52832 64MHz 512KB 64KB
Makerdiary nRF52840-MDK Nordic nRF52 NRF52840 64MHz 1MB 256KB
NXP LPCXpresso54114 NXP LPC LPC54114J256BD64 100MHz 256KB 192KB
NXP i.MX RT1010 Evaluation Kit NXP i.MX RT MIMXRT1011DAE5A 500MHz 64KB 128KB
NXP i.MX RT1015 Evaluation Kit NXP i.MX RT MIMXRT1015DAF5A 500MHz 96KB 128KB
NXP i.MX RT1020 Evaluation Kit NXP i.MX RT MIMXRT1021DAG5A 500MHz 64MB 256MB
NXP i.MX RT1050 Evaluation Kit NXP i.MX RT MIMXRT1052DVL6B 600MHz 64MB 512KB
NXP i.MX RT1060 Evaluation Kit NXP i.MX RT MIMXRT1062DVL6A 600MHz 64MB 1MB
NXP i.MX RT1064 Evaluation Kit NXP i.MX RT MIMXRT1064DVL6A 600MHz 4MB 1MB
Nordic nRF51 Dongle (PCA10031) Nordic nRF51 NRF51822 32MHz 256KB 32KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 NRF52840 64MHz 1MB 256KB
RedBearLab BLE Nano 1.5 Nordic nRF51 NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 NRF52832 64MHz 512KB 64KB
SLSTK3400A USB-enabled Happy Gecko Silicon Labs EFM32 EFM32HG322F64 25MHz 64KB 8KB
ST 32F411EDISCOVERY ST STM32 STM32F411VET6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY ST STM32 STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY ST STM32 STM32F769NIH6 216MHz 1MB 512KB
ST 32L476GDISCOVERY ST STM32 STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY ST STM32 STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F070RB ST STM32 STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F091RC ST STM32 STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F334R8 ST STM32 STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE ST STM32 STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F411RE ST STM32 STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG ST STM32 STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH ST STM32 STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F746ZG ST STM32 STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG ST STM32 STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI ST STM32 STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo L053R8 ST STM32 STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L432KC ST STM32 STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L4R5ZI ST STM32 STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0DISCOVERY ST STM32 STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY ST STM32 STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 STM32F407VGT6 168MHz 1MB 128KB
STM32H747I-DISCO ST STM32 STM32H747XIH6 400MHz 2MB 512KB
SparkFun RED-V RedBoard SiFive FE310 320MHz 16MB 16KB
SparkFun RED-V Thing Plus SiFive FE310 320MHz 16MB 16KB
VNG VBLUNO51 Nordic nRF51 NRF51822 16MHz 128KB 32KB
VNG VBLUno52 Nordic nRF52 NRF52832 64MHz 512KB 64KB

External Debug Tools

Boards listed below are compatible with PIO Unified Debugger but DEPEND ON external debug probe. They ARE NOT READY for debugging. Please click on board name for the further details.

Name Platform MCU Frequency Flash RAM
96Boards Argonkey (STEVAL-MKI187V1) ST STM32 STM32F412CG 100MHz 1MB 256KB
96Boards Neonkey ST STM32 STM32F411CE 100MHz 512KB 128KB
96Boards Nitrogen Nordic nRF52 NRF52832 64MHz 512KB 64KB
Adafruit Bluefruit nRF52832 Feather Nordic nRF52 NRF52832 64MHz 512KB 64KB
Adafruit Feather M0 Atmel SAM SAMD21G18A 48MHz 256KB 32KB
Adafruit Trinket M0 Atmel SAM SAMD21E18A 48MHz 256KB 32KB
Arduino Due (Programming Port) Atmel SAM AT91SAM3X8E 84MHz 512KB 96KB
BlackPill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 STM32F103C8T6 72MHz 128KB 20KB
BluePill F103C8 ST STM32 STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 STM32F103C8T6 72MHz 128KB 20KB
Freescale Kinetis FRDM-KW24D512 Freescale Kinetis MKW24D512 50MHz 512KB 64KB
Hexiwear Freescale Kinetis MK64FN1M0VDC12 120MHz 1MB 256KB
Holyiot YJ-16019 Nordic nRF52 NRF52832 64MHz 512KB 64KB
Nordic Thingy:52 (nRF52-PCA20020) Nordic nRF52 NRF52832 64MHz 512KB 64KB
Nucleo G071RB ST STM32 STM32G071RBT6 64MHz 128KB 36KB
Nucleo G431RB ST STM32 STM32G431RBT6 170MHz 128KB 32KB
Nucleo G474RE ST STM32 STM32G474RET6 170MHz 512KB 128KB
OLIMEXINO-STM32 ST STM32 STM32F103RBT6 72MHz 128KB 20KB
Olimex STM32-P405 ST STM32 STM32F405RGT6 168MHz 1MB 192KB
Particle Argon Nordic nRF52 NRF52840 64MHz 796KB 243KB
Particle Boron Nordic nRF52 NRF52840 64MHz 796KB 243KB
Particle Xenon Nordic nRF52 NRF52840 64MHz 796KB 243KB
STEVAL-FCU001V1 Flight controller unit evaluation board ST STM32 STM32F401CCU6 84MHz 256KB 64KB
STM32-E407 ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 STM32F407ZGT6 168MHz 1MB 128KB
STM3210C-EVAL ST STM32 STM32F107VCT6 72MHz 256KB 64KB
STM32373C-EVAL ST STM32 STM32F373VCT6 72MHz 256KB 32KB
STM32F072-EVAL ST STM32 STM32F072VBT6 48MHz 128KB 16KB
Waveshare BLE400 Nordic nRF51 NRF51822 32MHz 256KB 32KB

  • Zephyr for Atmel SAM
  • Zephyr for Freescale Kinetis
  • Zephyr for Nordic nRF51
  • Zephyr for Nordic nRF52
  • Zephyr for NXP i.MX RT
  • Zephyr for NXP LPC
  • Zephyr for SiFive
  • Zephyr for Silicon Labs EFM32
  • Zephyr for ST STM32

Name Description
Atmel SAM Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Freescale Kinetis Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.
Nordic nRF51 The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.
Nordic nRF52 The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.
NXP i.MX RT The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.
NXP LPC The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.
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.
Silicon Labs EFM32 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.
ST STM32 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.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll the tables below by horizontally.



Name Platform Debug MCU Frequency Flash RAM
96Boards Argonkey (STEVAL-MKI187V1) ST STM32 External STM32F412CG 100MHz 1MB 256KB
96Boards B96B-F446VE ST STM32 On-board STM32F446VET6 168MHz 512KB 128KB
96Boards Neonkey ST STM32 External STM32F411CE 100MHz 512KB 128KB
96Boards Nitrogen Nordic nRF52 External NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
Adafruit Bluefruit nRF52832 Feather Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Adafruit Feather M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Trinket M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Arduino Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Zero (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Atmel ATSAMR21-XPRO Atmel SAM On-board SAMR21G18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO Atmel SAM On-board SAMD21J18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
BBC micro:bit Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

Name Platform Debug MCU Frequency Flash RAM
ElectronutLabs Blip Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
ElectronutLabs Papyr Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
Freescale Kinetis FRDM-K22F Freescale Kinetis On-board MK22FN512VLH12 120MHz 512KB 128KB
Freescale Kinetis FRDM-K64F Freescale Kinetis On-board MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K82F Freescale Kinetis On-board MK82FN256VLL15 150MHz 256KB 256KB
Freescale Kinetis FRDM-KL25Z Freescale Kinetis On-board MKL25Z128VLK4 48MHz 128KB 16KB
Freescale Kinetis FRDM-KW24D512 Freescale Kinetis External MKW24D512 50MHz 512KB 64KB
Freescale Kinetis FRDM-KW41Z Freescale Kinetis On-board MKW41Z512VHT4 48MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
BlackPill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
BluePill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
Holyiot YJ-16019 Nordic nRF52 External NRF52832 64MHz 512KB 64KB

Laird Connectivity

Name Platform Debug MCU Frequency Flash RAM
BL652 Development Kit Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
BL654 Development Kit Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
Makerdiary nRF52832-MDK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Makerdiary nRF52840-MDK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
Hexiwear Freescale Kinetis External MK64FN1M0VDC12 120MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
NXP LPCXpresso54114 NXP LPC On-board LPC54114J256BD64 100MHz 256KB 192KB
NXP i.MX RT1010 Evaluation Kit NXP i.MX RT On-board MIMXRT1011DAE5A 500MHz 64KB 128KB
NXP i.MX RT1015 Evaluation Kit NXP i.MX RT On-board MIMXRT1015DAF5A 500MHz 96KB 128KB
NXP i.MX RT1020 Evaluation Kit NXP i.MX RT On-board MIMXRT1021DAG5A 500MHz 64MB 256MB
NXP i.MX RT1050 Evaluation Kit NXP i.MX RT On-board MIMXRT1052DVL6B 600MHz 64MB 512KB
NXP i.MX RT1060 Evaluation Kit NXP i.MX RT On-board MIMXRT1062DVL6A 600MHz 64MB 1MB
NXP i.MX RT1064 Evaluation Kit NXP i.MX RT On-board MIMXRT1064DVL6A 600MHz 4MB 1MB

Name Platform Debug MCU Frequency Flash RAM
Nordic Thingy:52 (nRF52-PCA20020) Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Nordic nRF51 Dongle (PCA10031) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
OLIMEXINO-STM32 ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
Olimex STM32-P405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB
STM32-E407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
Particle Argon Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Particle Boron Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Particle Xenon Nordic nRF52 External NRF52840 64MHz 796KB 243KB

Name Platform Debug MCU Frequency Flash RAM
RedBearLab BLE Nano 1.5 Nordic nRF51 On-board NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
32F412GDISCOVERY ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
32F723EDISCOVERY ST STM32 On-board STM32F723IEK6 216MHz 512KB 192KB
Nucleo G071RB ST STM32 External STM32G071RBT6 64MHz 128KB 36KB
Nucleo G431RB ST STM32 External STM32G431RBT6 170MHz 128KB 32KB
Nucleo G474RE ST STM32 External STM32G474RET6 170MHz 512KB 128KB
ST 32F411EDISCOVERY ST STM32 On-board STM32F411VET6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 On-board STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY ST STM32 On-board STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY ST STM32 On-board STM32F769NIH6 216MHz 1MB 512KB
ST 32L476GDISCOVERY ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY ST STM32 On-board STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 On-board STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 On-board STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F070RB ST STM32 On-board STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F091RC ST STM32 On-board STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 On-board STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 On-board STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 On-board STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F334R8 ST STM32 On-board STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F411RE ST STM32 On-board STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 On-board STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F746ZG ST STM32 On-board STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG ST STM32 On-board STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI ST STM32 On-board STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo L053R8 ST STM32 On-board STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 On-board STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L432KC ST STM32 On-board STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 On-board STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L4R5ZI ST STM32 On-board STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0DISCOVERY ST STM32 On-board STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY ST STM32 On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
STEVAL-FCU001V1 Flight controller unit evaluation board ST STM32 External STM32F401CCU6 84MHz 256KB 64KB
STM3210C-EVAL ST STM32 External STM32F107VCT6 72MHz 256KB 64KB
STM32373C-EVAL ST STM32 External STM32F373VCT6 72MHz 256KB 32KB
STM32F072-EVAL ST STM32 External STM32F072VBT6 48MHz 128KB 16KB
STM32H747I-DISCO ST STM32 On-board STM32H747XIH6 400MHz 2MB 512KB

Name Platform Debug MCU Frequency Flash RAM
HiFive1 SiFive On-board FE310 320MHz 16MB 16KB
HiFive1 Rev B SiFive On-board FE310 320MHz 16MB 16KB

Silicon Labs

Name Platform Debug MCU Frequency Flash RAM
EFM32WG-STK3800 Wonder Gecko Silicon Labs EFM32 On-board EFM32WG990F256 48MHz 256KB 32KB
SLSTK3400A USB-enabled Happy Gecko Silicon Labs EFM32 On-board EFM32HG322F64 25MHz 64KB 8KB

Name Platform Debug MCU Frequency Flash RAM
SparkFun RED-V RedBoard SiFive On-board FE310 320MHz 16MB 16KB
SparkFun RED-V Thing Plus SiFive On-board FE310 320MHz 16MB 16KB

Name Platform Debug MCU Frequency Flash RAM
VNG VBLUNO51 Nordic nRF51 On-board NRF51822 16MHz 128KB 32KB
VNG VBLUno52 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
Waveshare BLE400 Nordic nRF51 External NRF51822 32MHz 256KB 32KB

Rapid Embedded Development, Continuous and IDE integration in a few steps with PlatformIO thanks to built-in project generator for the most popular embedded boards and IDE.

NOTE:

  • You can list pre-configured boards by platformio boards command or PlatformIO Boards Explorer
  • For more detailed board information please scroll tables below by horizontal.



Aceinna IMU

•
Aceinna Low Cost RTK
  • Hardware
  • Configuration
  • Uploading
  • Debugging


Platform Aceinna IMU: Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.

Microcontroller STM32F469NIH6
Frequency 180MHz
Flash 1MB
RAM 384KB
Vendor Aceinna

Please use LowCostRTK ID for board option in "platformio.ini" (Project Configuration File):

[env:LowCostRTK]
platform = aceinna_imu
board = LowCostRTK


You can override default Aceinna Low Cost RTK settings per build environment using board_*** option, where *** is a JSON object path from board manifest LowCostRTK.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:LowCostRTK]
platform = aceinna_imu
board = LowCostRTK
; change microcontroller
board_build.mcu = stm32f469nih6
; change MCU frequency
board_build.f_cpu = 180000000L


Aceinna Low Cost RTK supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:LowCostRTK]
platform = aceinna_imu
board = LowCostRTK
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Aceinna Low Cost RTK 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

•
Aceinna OpenIMU 300
  • Hardware
  • Configuration
  • Uploading
  • Debugging


Platform Aceinna IMU: Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.

Microcontroller STM32F405RG
Frequency 120MHz
Flash 1MB
RAM 128KB
Vendor Aceinna

Please use OpenIMU300 ID for board option in "platformio.ini" (Project Configuration File):

[env:OpenIMU300]
platform = aceinna_imu
board = OpenIMU300


You can override default Aceinna OpenIMU 300 settings per build environment using board_*** option, where *** is a JSON object path from board manifest OpenIMU300.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:OpenIMU300]
platform = aceinna_imu
board = OpenIMU300
; change microcontroller
board_build.mcu = stm32f405rg
; change MCU frequency
board_build.f_cpu = 120000000L


Aceinna OpenIMU 300 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:OpenIMU300]
platform = aceinna_imu
board = OpenIMU300
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Aceinna OpenIMU 300 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
Black Magic Probe
J-LINK
ST-LINK Yes

•
Aceinna OpenIMU 300ZA
  • Hardware
  • Configuration
  • Uploading
  • Debugging


Platform Aceinna IMU: Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.

Microcontroller STM32F405RG
Frequency 120MHz
Flash 1MB
RAM 128KB
Vendor Aceinna

Please use OpenIMU300ZA ID for board option in "platformio.ini" (Project Configuration File):

[env:OpenIMU300ZA]
platform = aceinna_imu
board = OpenIMU300ZA


You can override default Aceinna OpenIMU 300ZA settings per build environment using board_*** option, where *** is a JSON object path from board manifest OpenIMU300ZA.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:OpenIMU300ZA]
platform = aceinna_imu
board = OpenIMU300ZA
; change microcontroller
board_build.mcu = stm32f405rg
; change MCU frequency
board_build.f_cpu = 120000000L


Aceinna OpenIMU 300ZA supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:OpenIMU300ZA]
platform = aceinna_imu
board = OpenIMU300ZA
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Aceinna OpenIMU 300ZA 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
Black Magic Probe
J-LINK
ST-LINK Yes

•
Aceinna OpenIMU 330
  • Hardware
  • Configuration
  • Uploading
  • Debugging


Platform Aceinna IMU: Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.

Microcontroller STM32L431CB
Frequency 80MHz
Flash 128KB
RAM 64KB
Vendor Aceinna

Please use OpenIMU330 ID for board option in "platformio.ini" (Project Configuration File):

[env:OpenIMU330]
platform = aceinna_imu
board = OpenIMU330


You can override default Aceinna OpenIMU 330 settings per build environment using board_*** option, where *** is a JSON object path from board manifest OpenIMU330.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:OpenIMU330]
platform = aceinna_imu
board = OpenIMU330
; change microcontroller
board_build.mcu = stm32l431cb
; change MCU frequency
board_build.f_cpu = 80000000L


Aceinna OpenIMU 330 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:OpenIMU330]
platform = aceinna_imu
board = OpenIMU330
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Aceinna OpenIMU 330 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
Black Magic Probe
J-LINK
ST-LINK Yes

•
Aceinna OpenIMU 330ZA
  • Hardware
  • Configuration
  • Uploading
  • Debugging


Platform Aceinna IMU: Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.

Microcontroller STM32F469IG
Frequency 180MHz
Flash 1MB
RAM 384KB
Vendor Aceinna

Please use OpenRTK ID for board option in "platformio.ini" (Project Configuration File):

[env:OpenRTK]
platform = aceinna_imu
board = OpenRTK


You can override default Aceinna OpenIMU 330ZA settings per build environment using board_*** option, where *** is a JSON object path from board manifest OpenRTK.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:OpenRTK]
platform = aceinna_imu
board = OpenRTK
; change microcontroller
board_build.mcu = stm32f469IG
; change MCU frequency
board_build.f_cpu = 180000000L


Aceinna OpenIMU 330ZA supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:OpenRTK]
platform = aceinna_imu
board = OpenRTK
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Aceinna OpenIMU 330ZA 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
Black Magic Probe
J-LINK
ST-LINK Yes

•
Aceinna OpenRTK330L
  • Hardware
  • Configuration
  • Uploading
  • Debugging


Platform Aceinna IMU: Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.

Microcontroller STM32F469IG
Frequency 180MHz
Flash 1MB
RAM 384KB
Vendor Aceinna

Please use OpenRTK330L ID for board option in "platformio.ini" (Project Configuration File):

[env:OpenRTK330L]
platform = aceinna_imu
board = OpenRTK330L


You can override default Aceinna OpenRTK330L settings per build environment using board_*** option, where *** is a JSON object path from board manifest OpenRTK330L.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:OpenRTK330L]
platform = aceinna_imu
board = OpenRTK330L
; change microcontroller
board_build.mcu = stm32f469IG
; change MCU frequency
board_build.f_cpu = 180000000L


Aceinna OpenRTK330L supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:OpenRTK330L]
platform = aceinna_imu
board = OpenRTK330L
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Aceinna OpenRTK330L 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
Black Magic Probe
J-LINK
ST-LINK Yes

Atmel AVR

•
AT90CAN128
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller AT90CAN128
Frequency 16MHz
Flash 127KB
RAM 4KB
Vendor Microchip

Please use AT90CAN128 ID for board option in "platformio.ini" (Project Configuration File):

[env:AT90CAN128]
platform = atmelavr
board = AT90CAN128


You can override default AT90CAN128 settings per build environment using board_*** option, where *** is a JSON object path from board manifest AT90CAN128.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:AT90CAN128]
platform = atmelavr
board = AT90CAN128
; change microcontroller
board_build.mcu = at90can128
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support AT90CAN128 board.

Name Description
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.

•
AT90CAN32
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller AT90CAN32
Frequency 16MHz
Flash 31KB
RAM 2KB
Vendor Microchip

Please use AT90CAN32 ID for board option in "platformio.ini" (Project Configuration File):

[env:AT90CAN32]
platform = atmelavr
board = AT90CAN32


You can override default AT90CAN32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest AT90CAN32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:AT90CAN32]
platform = atmelavr
board = AT90CAN32
; change microcontroller
board_build.mcu = at90can32
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support AT90CAN32 board.

Name Description
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.

•
AT90CAN64
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller AT90CAN64
Frequency 16MHz
Flash 63KB
RAM 4KB
Vendor Microchip

Please use AT90CAN64 ID for board option in "platformio.ini" (Project Configuration File):

[env:AT90CAN64]
platform = atmelavr
board = AT90CAN64


You can override default AT90CAN64 settings per build environment using board_*** option, where *** is a JSON object path from board manifest AT90CAN64.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:AT90CAN64]
platform = atmelavr
board = AT90CAN64
; change microcontroller
board_build.mcu = at90can64
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support AT90CAN64 board.

Name Description
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.

•
ATmega128/A
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA128
Frequency 16MHz
Flash 127KB
RAM 4KB
Vendor Microchip

Please use ATmega128 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega128]
platform = atmelavr
board = ATmega128


You can override default ATmega128/A settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega128.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega128]
platform = atmelavr
board = ATmega128
; change microcontroller
board_build.mcu = atmega128
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega128/A 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
simavr Yes Yes

Name Description
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.

•
ATmega1280
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1280
Frequency 16MHz
Flash 127KB
RAM 8KB
Vendor Microchip

Please use ATmega1280 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega1280]
platform = atmelavr
board = ATmega1280


You can override default ATmega1280 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega1280.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega1280]
platform = atmelavr
board = ATmega1280
; change microcontroller
board_build.mcu = atmega1280
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega1280 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
simavr Yes Yes

Name Description
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.

•
ATmega1281
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1281
Frequency 16MHz
Flash 127KB
RAM 8KB
Vendor Microchip

Please use ATmega1281 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega1281]
platform = atmelavr
board = ATmega1281


You can override default ATmega1281 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega1281.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega1281]
platform = atmelavr
board = ATmega1281
; change microcontroller
board_build.mcu = atmega1281
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega1281 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
simavr Yes Yes

Name Description
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.

•
ATmega1284
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284
Frequency 16MHz
Flash 127KB
RAM 16KB
Vendor Microchip

Please use ATmega1284 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega1284]
platform = atmelavr
board = ATmega1284


You can override default ATmega1284 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega1284.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega1284]
platform = atmelavr
board = ATmega1284
; change microcontroller
board_build.mcu = atmega1284
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega1284 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
simavr Yes Yes

Name Description
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.

•
ATmega1284P
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 16MHz
Flash 127KB
RAM 16KB
Vendor Microchip

Please use ATmega1284P ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega1284P]
platform = atmelavr
board = ATmega1284P


You can override default ATmega1284P settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega1284P.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega1284P]
platform = atmelavr
board = ATmega1284P
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega1284P 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
simavr Yes Yes

Name Description
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.

•
ATmega16
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA16
Frequency 16MHz
Flash 15.50KB
RAM 1KB
Vendor Microchip

Please use ATmega16 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega16]
platform = atmelavr
board = ATmega16


You can override default ATmega16 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega16.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega16]
platform = atmelavr
board = ATmega16
; change microcontroller
board_build.mcu = atmega16
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega16 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
simavr Yes Yes

Name Description
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.

•
ATmega162
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA162
Frequency 16MHz
Flash 15.50KB
RAM 1KB
Vendor Microchip

Please use ATmega162 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega162]
platform = atmelavr
board = ATmega162


You can override default ATmega162 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega162.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega162]
platform = atmelavr
board = ATmega162
; change microcontroller
board_build.mcu = atmega162
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega162 board.

Name Description
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.

•
ATmega164A
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA164A
Frequency 16MHz
Flash 15.50KB
RAM 1KB
Vendor Microchip

Please use ATmega164A ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega164A]
platform = atmelavr
board = ATmega164A


You can override default ATmega164A settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega164A.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega164A]
platform = atmelavr
board = ATmega164A
; change microcontroller
board_build.mcu = atmega164a
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega164A board.

Name Description
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.

•
ATmega164P/PA
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA164P
Frequency 16MHz
Flash 15.50KB
RAM 1KB
Vendor Microchip

Please use ATmega164P ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega164P]
platform = atmelavr
board = ATmega164P


You can override default ATmega164P/PA settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega164P.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega164P]
platform = atmelavr
board = ATmega164P
; change microcontroller
board_build.mcu = atmega164p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega164P/PA 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
simavr Yes Yes

Name Description
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.

•
ATmega168/A
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168
Frequency 16MHz
Flash 15.50KB
RAM 1KB
Vendor Microchip

Please use ATmega168 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega168]
platform = atmelavr
board = ATmega168


You can override default ATmega168/A settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega168]
platform = atmelavr
board = ATmega168
; change microcontroller
board_build.mcu = atmega168
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega168/A 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
simavr Yes Yes

Name Description
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.

•
ATmega168P/PA
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168P
Frequency 16MHz
Flash 15.50KB
RAM 1KB
Vendor Microchip

Please use ATmega168P ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega168P]
platform = atmelavr
board = ATmega168P


You can override default ATmega168P/PA settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega168P.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega168P]
platform = atmelavr
board = ATmega168P
; change microcontroller
board_build.mcu = atmega168p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega168P/PA 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
simavr Yes Yes

Name Description
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.

•
ATmega168PB
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168PB
Frequency 16MHz
Flash 15.50KB
RAM 1KB
Vendor Microchip

Please use ATmega168PB ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega168PB]
platform = atmelavr
board = ATmega168PB


You can override default ATmega168PB settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega168PB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega168PB]
platform = atmelavr
board = ATmega168PB
; change microcontroller
board_build.mcu = atmega168pb
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega168PB board.

Name Description
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.

•
ATmega2560
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 16MHz
Flash 255KB
RAM 8KB
Vendor Microchip

Please use ATmega2560 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega2560]
platform = atmelavr
board = ATmega2560


You can override default ATmega2560 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega2560.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega2560]
platform = atmelavr
board = ATmega2560
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega2560 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
simavr Yes Yes

Name Description
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.

•
ATmega2561
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2561
Frequency 16MHz
Flash 255KB
RAM 8KB
Vendor Microchip

Please use ATmega2561 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega2561]
platform = atmelavr
board = ATmega2561


You can override default ATmega2561 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega2561.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega2561]
platform = atmelavr
board = ATmega2561
; change microcontroller
board_build.mcu = atmega2561
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega2561 board.

Name Description
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.

•
ATmega32
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Microchip

Please use ATmega32 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega32]
platform = atmelavr
board = ATmega32


You can override default ATmega32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega32]
platform = atmelavr
board = ATmega32
; change microcontroller
board_build.mcu = atmega32
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega32 board.

Name Description
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.

•
ATmega324A
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA324A
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Microchip

Please use ATmega324A ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega324A]
platform = atmelavr
board = ATmega324A


You can override default ATmega324A settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega324A.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega324A]
platform = atmelavr
board = ATmega324A
; change microcontroller
board_build.mcu = atmega324a
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega324A 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
simavr Yes Yes

Name Description
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.

•
ATmega324P
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA324P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Microchip

Please use ATmega324P ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega324P]
platform = atmelavr
board = ATmega324P


You can override default ATmega324P settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega324P.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega324P]
platform = atmelavr
board = ATmega324P
; change microcontroller
board_build.mcu = atmega324p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega324P 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
simavr Yes Yes

Name Description
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.

•
ATmega324PA
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA324PA
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Microchip

Please use ATmega324PA ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega324PA]
platform = atmelavr
board = ATmega324PA


You can override default ATmega324PA settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega324PA.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega324PA]
platform = atmelavr
board = ATmega324PA
; change microcontroller
board_build.mcu = atmega324pa
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega324PA 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
simavr Yes Yes

Name Description
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.

•
ATmega324PB
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA324PB
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Microchip

Please use ATmega324PB ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega324PB]
platform = atmelavr
board = ATmega324PB


You can override default ATmega324PB settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega324PB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega324PB]
platform = atmelavr
board = ATmega324PB
; change microcontroller
board_build.mcu = atmega324pb
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega324PB board.

Name Description
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.

•
ATmega328
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Microchip

Please use ATmega328 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega328]
platform = atmelavr
board = ATmega328


You can override default ATmega328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega328]
platform = atmelavr
board = ATmega328
; change microcontroller
board_build.mcu = atmega328
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega328 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
simavr Yes Yes

Name Description
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.

•
ATmega328P/PA
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Microchip

Please use ATmega328P ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega328P]
platform = atmelavr
board = ATmega328P


You can override default ATmega328P/PA settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega328P.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega328P]
platform = atmelavr
board = ATmega328P
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega328P/PA 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
simavr Yes Yes

Name Description
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.

•
ATmega328PB
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328PB
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Microchip

Please use ATmega328PB ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega328PB]
platform = atmelavr
board = ATmega328PB


You can override default ATmega328PB settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega328PB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega328PB]
platform = atmelavr
board = ATmega328PB
; change microcontroller
board_build.mcu = atmega328pb
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega328PB board.

Name Description
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.

•
ATmega48/A
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA48
Frequency 16MHz
Flash 4KB
RAM 512B
Vendor Microchip

Please use ATmega48 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega48]
platform = atmelavr
board = ATmega48


You can override default ATmega48/A settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega48.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega48]
platform = atmelavr
board = ATmega48
; change microcontroller
board_build.mcu = atmega48
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega48/A 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
simavr Yes Yes

Name Description
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.

•
ATmega48PB
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA48PB
Frequency 16MHz
Flash 4KB
RAM 512B
Vendor Microchip

Please use ATmega48PB ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega48PB]
platform = atmelavr
board = ATmega48PB


You can override default ATmega48PB settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega48PB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega48PB]
platform = atmelavr
board = ATmega48PB
; change microcontroller
board_build.mcu = atmega48pb
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega48PB board.

Name Description
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.

•
ATmega64/A
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA64
Frequency 16MHz
Flash 63KB
RAM 4KB
Vendor Microchip

Please use ATmega64 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega64]
platform = atmelavr
board = ATmega64


You can override default ATmega64/A settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega64.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega64]
platform = atmelavr
board = ATmega64
; change microcontroller
board_build.mcu = atmega64
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega64/A board.

Name Description
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.

•
ATmega640
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA640
Frequency 16MHz
Flash 63KB
RAM 8KB
Vendor Microchip

Please use ATmega640 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega640]
platform = atmelavr
board = ATmega640


You can override default ATmega640 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega640.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega640]
platform = atmelavr
board = ATmega640
; change microcontroller
board_build.mcu = atmega640
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega640 board.

Name Description
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.

•
ATmega644/A
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA644A
Frequency 16MHz
Flash 63KB
RAM 4KB
Vendor Microchip

Please use ATmega644A ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega644A]
platform = atmelavr
board = ATmega644A


You can override default ATmega644/A settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega644A.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega644A]
platform = atmelavr
board = ATmega644A
; change microcontroller
board_build.mcu = atmega644a
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega644/A board.

Name Description
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.

•
ATmega644P/PA
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA644P
Frequency 16MHz
Flash 63KB
RAM 4KB
Vendor Microchip

Please use ATmega644P ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega644P]
platform = atmelavr
board = ATmega644P


You can override default ATmega644P/PA settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega644P.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega644P]
platform = atmelavr
board = ATmega644P
; change microcontroller
board_build.mcu = atmega644p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega644P/PA 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
simavr Yes Yes

Name Description
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.

•
ATmega8/A
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA8
Frequency 16MHz
Flash 7.50KB
RAM 1KB
Vendor Microchip

Please use ATmega8 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega8]
platform = atmelavr
board = ATmega8


You can override default ATmega8/A settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega8]
platform = atmelavr
board = ATmega8
; change microcontroller
board_build.mcu = atmega8
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega8/A 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
simavr Yes Yes

Name Description
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.

•
ATmega8515
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA8515
Frequency 16MHz
Flash 7.50KB
RAM 512B
Vendor Microchip

Please use ATmega8515 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega8515]
platform = atmelavr
board = ATmega8515


You can override default ATmega8515 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega8515.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega8515]
platform = atmelavr
board = ATmega8515
; change microcontroller
board_build.mcu = atmega8515
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega8515 board.

Name Description
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.

•
ATmega8535
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA8535
Frequency 16MHz
Flash 7.50KB
RAM 512B
Vendor Microchip

Please use ATmega8535 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega8535]
platform = atmelavr
board = ATmega8535


You can override default ATmega8535 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega8535.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega8535]
platform = atmelavr
board = ATmega8535
; change microcontroller
board_build.mcu = atmega8535
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega8535 board.

Name Description
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.

•
ATmega88/A
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA88
Frequency 16MHz
Flash 7.50KB
RAM 1KB
Vendor Microchip

Please use ATmega88 ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega88]
platform = atmelavr
board = ATmega88


You can override default ATmega88/A settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega88.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega88]
platform = atmelavr
board = ATmega88
; change microcontroller
board_build.mcu = atmega88
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega88/A 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
simavr Yes Yes

Name Description
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.

•
ATmega88P/PA
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA88P
Frequency 16MHz
Flash 7.50KB
RAM 1KB
Vendor Microchip

Please use ATmega88P ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega88P]
platform = atmelavr
board = ATmega88P


You can override default ATmega88P/PA settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega88P.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega88P]
platform = atmelavr
board = ATmega88P
; change microcontroller
board_build.mcu = atmega88p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega88P/PA 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
simavr Yes Yes

Name Description
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.

•
ATmega88PB
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA88PB
Frequency 16MHz
Flash 7.50KB
RAM 1KB
Vendor Microchip

Please use ATmega88PB ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega88PB]
platform = atmelavr
board = ATmega88PB


You can override default ATmega88PB settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega88PB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega88PB]
platform = atmelavr
board = ATmega88PB
; change microcontroller
board_build.mcu = atmega88pb
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support ATmega88PB board.

Name Description
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.

•
ATmega8P/PA
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA48P
Frequency 16MHz
Flash 4KB
RAM 512B
Vendor Microchip

Please use ATmega48P ID for board option in "platformio.ini" (Project Configuration File):

[env:ATmega48P]
platform = atmelavr
board = ATmega48P


You can override default ATmega8P/PA settings per build environment using board_*** option, where *** is a JSON object path from board manifest ATmega48P.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ATmega48P]
platform = atmelavr
board = ATmega48P
; change microcontroller
board_build.mcu = atmega48p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ATmega8P/PA 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
simavr Yes Yes

Name Description
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.

•
Adafruit Bluefruit Micro
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor Adafruit

Please use bluefruitmicro ID for board option in "platformio.ini" (Project Configuration File):

[env:bluefruitmicro]
platform = atmelavr
board = bluefruitmicro


You can override default Adafruit Bluefruit Micro settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluefruitmicro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:bluefruitmicro]
platform = atmelavr
board = bluefruitmicro
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Bluefruit Micro 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
simavr Yes Yes

Name Description
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.

•
Adafruit Circuit Playground Classic
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor Adafruit

Please use circuitplay_classic ID for board option in "platformio.ini" (Project Configuration File):

[env:circuitplay_classic]
platform = atmelavr
board = circuitplay_classic


You can override default Adafruit Circuit Playground Classic settings per build environment using board_*** option, where *** is a JSON object path from board manifest circuitplay_classic.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:circuitplay_classic]
platform = atmelavr
board = circuitplay_classic
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Circuit Playground Classic 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
simavr Yes Yes

Name Description
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.

•
Adafruit Feather 328P
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 31.50KB
RAM 2KB
Vendor Adafruit

Please use feather328p ID for board option in "platformio.ini" (Project Configuration File):

[env:feather328p]
platform = atmelavr
board = feather328p


You can override default Adafruit Feather 328P settings per build environment using board_*** option, where *** is a JSON object path from board manifest feather328p.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:feather328p]
platform = atmelavr
board = feather328p
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Feather 328P 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
simavr Yes Yes

Name Description
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.

•
Adafruit Feather 32u4
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor Adafruit

Please use feather32u4 ID for board option in "platformio.ini" (Project Configuration File):

[env:feather32u4]
platform = atmelavr
board = feather32u4


You can override default Adafruit Feather 32u4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest feather32u4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:feather32u4]
platform = atmelavr
board = feather32u4
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Feather 32u4 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
simavr Yes Yes

Name Description
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.

•
Adafruit Flora
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor Adafruit

Please use flora8 ID for board option in "platformio.ini" (Project Configuration File):

[env:flora8]
platform = atmelavr
board = flora8


You can override default Adafruit Flora settings per build environment using board_*** option, where *** is a JSON object path from board manifest flora8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:flora8]
platform = atmelavr
board = flora8
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Flora 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
simavr Yes Yes

Name Description
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.

•
Adafruit Gemma
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY85
Frequency 8MHz
Flash 8KB
RAM 512B
Vendor Adafruit

Please use gemma ID for board option in "platformio.ini" (Project Configuration File):

[env:gemma]
platform = atmelavr
board = gemma


You can override default Adafruit Gemma settings per build environment using board_*** option, where *** is a JSON object path from board manifest gemma.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:gemma]
platform = atmelavr
board = gemma
; change microcontroller
board_build.mcu = attiny85
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Gemma 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
simavr Yes Yes

Name Description
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.

•
Adafruit ItsyBitsy 3V/8MHz
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor Adafruit

Please use itsybitsy32u4_3V ID for board option in "platformio.ini" (Project Configuration File):

[env:itsybitsy32u4_3V]
platform = atmelavr
board = itsybitsy32u4_3V


You can override default Adafruit ItsyBitsy 3V/8MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest itsybitsy32u4_3V.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:itsybitsy32u4_3V]
platform = atmelavr
board = itsybitsy32u4_3V
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit ItsyBitsy 3V/8MHz 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
simavr Yes Yes

Name Description
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.

•
Adafruit ItsyBitsy 5V/16MHz
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Adafruit

Please use itsybitsy32u4_5V ID for board option in "platformio.ini" (Project Configuration File):

[env:itsybitsy32u4_5V]
platform = atmelavr
board = itsybitsy32u4_5V


You can override default Adafruit ItsyBitsy 5V/16MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest itsybitsy32u4_5V.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:itsybitsy32u4_5V]
platform = atmelavr
board = itsybitsy32u4_5V
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit ItsyBitsy 5V/16MHz 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
simavr Yes Yes

Name Description
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.

•
Adafruit Metro
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Adafruit

Please use metro ID for board option in "platformio.ini" (Project Configuration File):

[env:metro]
platform = atmelavr
board = metro


You can override default Adafruit Metro settings per build environment using board_*** option, where *** is a JSON object path from board manifest metro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:metro]
platform = atmelavr
board = metro
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Metro 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
simavr Yes Yes

Name Description
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.

•
Adafruit Pro Trinket 3V/12MHz (FTDI)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 12MHz
Flash 28KB
RAM 2KB
Vendor Adafruit

Please use protrinket3ftdi ID for board option in "platformio.ini" (Project Configuration File):

[env:protrinket3ftdi]
platform = atmelavr
board = protrinket3ftdi


You can override default Adafruit Pro Trinket 3V/12MHz (FTDI) settings per build environment using board_*** option, where *** is a JSON object path from board manifest protrinket3ftdi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:protrinket3ftdi]
platform = atmelavr
board = protrinket3ftdi
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 12000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Pro Trinket 3V/12MHz (FTDI) 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
simavr Yes Yes

Name Description
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.

•
Adafruit Pro Trinket 3V/12MHz (USB)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 12MHz
Flash 28KB
RAM 2KB
Vendor Adafruit

Please use protrinket3 ID for board option in "platformio.ini" (Project Configuration File):

[env:protrinket3]
platform = atmelavr
board = protrinket3


You can override default Adafruit Pro Trinket 3V/12MHz (USB) settings per build environment using board_*** option, where *** is a JSON object path from board manifest protrinket3.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:protrinket3]
platform = atmelavr
board = protrinket3
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 12000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Pro Trinket 3V/12MHz (USB) 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
simavr Yes Yes

Name Description
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.

•
Adafruit Pro Trinket 5V/16MHz (FTDI)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 28KB
RAM 2KB
Vendor Adafruit

Please use protrinket5ftdi ID for board option in "platformio.ini" (Project Configuration File):

[env:protrinket5ftdi]
platform = atmelavr
board = protrinket5ftdi


You can override default Adafruit Pro Trinket 5V/16MHz (FTDI) settings per build environment using board_*** option, where *** is a JSON object path from board manifest protrinket5ftdi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:protrinket5ftdi]
platform = atmelavr
board = protrinket5ftdi
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Pro Trinket 5V/16MHz (FTDI) 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
simavr Yes Yes

Name Description
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.

•
Adafruit Pro Trinket 5V/16MHz (USB)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 28KB
RAM 2KB
Vendor Adafruit

Please use protrinket5 ID for board option in "platformio.ini" (Project Configuration File):

[env:protrinket5]
platform = atmelavr
board = protrinket5


You can override default Adafruit Pro Trinket 5V/16MHz (USB) settings per build environment using board_*** option, where *** is a JSON object path from board manifest protrinket5.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:protrinket5]
platform = atmelavr
board = protrinket5
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Pro Trinket 5V/16MHz (USB) 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
simavr Yes Yes

Name Description
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.

•
Adafruit Trinket 3V/8MHz
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY85
Frequency 8MHz
Flash 8KB
RAM 512B
Vendor Adafruit

Please use trinket3 ID for board option in "platformio.ini" (Project Configuration File):

[env:trinket3]
platform = atmelavr
board = trinket3


You can override default Adafruit Trinket 3V/8MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest trinket3.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:trinket3]
platform = atmelavr
board = trinket3
; change microcontroller
board_build.mcu = attiny85
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Trinket 3V/8MHz 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
simavr Yes Yes

Name Description
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.

•
Adafruit Trinket 5V/16MHz
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY85
Frequency 16MHz
Flash 8KB
RAM 512B
Vendor Adafruit

Please use trinket5 ID for board option in "platformio.ini" (Project Configuration File):

[env:trinket5]
platform = atmelavr
board = trinket5


You can override default Adafruit Trinket 5V/16MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest trinket5.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:trinket5]
platform = atmelavr
board = trinket5
; change microcontroller
board_build.mcu = attiny85
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Trinket 5V/16MHz 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
simavr Yes Yes

Name Description
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.

•
Alorium Hinj
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Alorium Technology

Please use alorium_hinj ID for board option in "platformio.ini" (Project Configuration File):

[env:alorium_hinj]
platform = atmelavr
board = alorium_hinj


You can override default Alorium Hinj settings per build environment using board_*** option, where *** is a JSON object path from board manifest alorium_hinj.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:alorium_hinj]
platform = atmelavr
board = alorium_hinj
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Alorium Hinj 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
simavr Yes Yes

Name Description
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.

•
Alorium Sno
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Alorium Technology

Please use alorium_sno ID for board option in "platformio.ini" (Project Configuration File):

[env:alorium_sno]
platform = atmelavr
board = alorium_sno


You can override default Alorium Sno settings per build environment using board_*** option, where *** is a JSON object path from board manifest alorium_sno.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:alorium_sno]
platform = atmelavr
board = alorium_sno
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Alorium Sno 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
simavr Yes Yes

Name Description
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.

•
Alorium XLR8
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Alorium Technology

Please use alorium_xlr8 ID for board option in "platformio.ini" (Project Configuration File):

[env:alorium_xlr8]
platform = atmelavr
board = alorium_xlr8


You can override default Alorium XLR8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest alorium_xlr8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:alorium_xlr8]
platform = atmelavr
board = alorium_xlr8
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Alorium XLR8 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
simavr Yes Yes

Name Description
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.

•
Altair
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA256RFR2
Frequency 16MHz
Flash 248KB
RAM 32KB
Vendor makerlab.mx

Please use altair ID for board option in "platformio.ini" (Project Configuration File):

[env:altair]
platform = atmelavr
board = altair


You can override default Altair settings per build environment using board_*** option, where *** is a JSON object path from board manifest altair.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:altair]
platform = atmelavr
board = altair
; change microcontroller
board_build.mcu = atmega256rfr2
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Altair board.

Name Description
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.

•
Anarduino MiniWireless
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Anarduino

Please use miniwireless ID for board option in "platformio.ini" (Project Configuration File):

[env:miniwireless]
platform = atmelavr
board = miniwireless


You can override default Anarduino MiniWireless settings per build environment using board_*** option, where *** is a JSON object path from board manifest miniwireless.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:miniwireless]
platform = atmelavr
board = miniwireless
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Anarduino MiniWireless 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
simavr Yes Yes

Name Description
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.

•
Arduboy
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduboy

Please use arduboy ID for board option in "platformio.ini" (Project Configuration File):

[env:arduboy]
platform = atmelavr
board = arduboy


You can override default Arduboy settings per build environment using board_*** option, where *** is a JSON object path from board manifest arduboy.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:arduboy]
platform = atmelavr
board = arduboy
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduboy 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
simavr Yes Yes

Name Description
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.

•
Arduboy DevKit
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduboy

Please use arduboy_devkit ID for board option in "platformio.ini" (Project Configuration File):

[env:arduboy_devkit]
platform = atmelavr
board = arduboy_devkit


You can override default Arduboy DevKit settings per build environment using board_*** option, where *** is a JSON object path from board manifest arduboy_devkit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:arduboy_devkit]
platform = atmelavr
board = arduboy_devkit
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduboy DevKit 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
simavr Yes Yes

Name Description
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.

•
Arduino BT ATmega168
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168
Frequency 16MHz
Flash 14KB
RAM 1KB
Vendor Arduino

Please use btatmega168 ID for board option in "platformio.ini" (Project Configuration File):

[env:btatmega168]
platform = atmelavr
board = btatmega168


You can override default Arduino BT ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest btatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:btatmega168]
platform = atmelavr
board = btatmega168
; change microcontroller
board_build.mcu = atmega168
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino BT ATmega168 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
simavr Yes Yes

Name Description
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.

•
Arduino BT ATmega328
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 28KB
RAM 2KB
Vendor Arduino

Please use btatmega328 ID for board option in "platformio.ini" (Project Configuration File):

[env:btatmega328]
platform = atmelavr
board = btatmega328


You can override default Arduino BT ATmega328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest btatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:btatmega328]
platform = atmelavr
board = btatmega328
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino BT ATmega328 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
simavr Yes Yes

Name Description
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.

•
Arduino Duemilanove or Diecimila ATmega168
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168
Frequency 16MHz
Flash 14KB
RAM 1KB
Vendor Arduino

Please use diecimilaatmega168 ID for board option in "platformio.ini" (Project Configuration File):

[env:diecimilaatmega168]
platform = atmelavr
board = diecimilaatmega168


You can override default Arduino Duemilanove or Diecimila ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest diecimilaatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:diecimilaatmega168]
platform = atmelavr
board = diecimilaatmega168
; change microcontroller
board_build.mcu = atmega168
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Duemilanove or Diecimila ATmega168 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
simavr Yes Yes

Name Description
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.

•
Arduino Duemilanove or Diecimila ATmega328
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 30KB
RAM 2KB
Vendor Arduino

Please use diecimilaatmega328 ID for board option in "platformio.ini" (Project Configuration File):

[env:diecimilaatmega328]
platform = atmelavr
board = diecimilaatmega328


You can override default Arduino Duemilanove or Diecimila ATmega328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest diecimilaatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:diecimilaatmega328]
platform = atmelavr
board = diecimilaatmega328
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Duemilanove or Diecimila ATmega328 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
simavr Yes Yes

Name Description
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.

•
Arduino Esplora
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduino

Please use esplora ID for board option in "platformio.ini" (Project Configuration File):

[env:esplora]
platform = atmelavr
board = esplora


You can override default Arduino Esplora settings per build environment using board_*** option, where *** is a JSON object path from board manifest esplora.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esplora]
platform = atmelavr
board = esplora
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Esplora 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
simavr Yes Yes

Name Description
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.

•
Arduino Ethernet
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Arduino

Please use ethernet ID for board option in "platformio.ini" (Project Configuration File):

[env:ethernet]
platform = atmelavr
board = ethernet


You can override default Arduino Ethernet settings per build environment using board_*** option, where *** is a JSON object path from board manifest ethernet.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ethernet]
platform = atmelavr
board = ethernet
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Ethernet 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
simavr Yes Yes

Name Description
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.

•
Arduino Fio
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 30KB
RAM 2KB
Vendor Arduino

Please use fio ID for board option in "platformio.ini" (Project Configuration File):

[env:fio]
platform = atmelavr
board = fio


You can override default Arduino Fio settings per build environment using board_*** option, where *** is a JSON object path from board manifest fio.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:fio]
platform = atmelavr
board = fio
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Fio 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
simavr Yes Yes

Name Description
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.

•
Arduino Industrial 101
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduino

Please use chiwawa ID for board option in "platformio.ini" (Project Configuration File):

[env:chiwawa]
platform = atmelavr
board = chiwawa


You can override default Arduino Industrial 101 settings per build environment using board_*** option, where *** is a JSON object path from board manifest chiwawa.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:chiwawa]
platform = atmelavr
board = chiwawa
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Industrial 101 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
simavr Yes Yes

Name Description
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.

•
Arduino Leonardo
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduino

Please use leonardo ID for board option in "platformio.ini" (Project Configuration File):

[env:leonardo]
platform = atmelavr
board = leonardo


You can override default Arduino Leonardo settings per build environment using board_*** option, where *** is a JSON object path from board manifest leonardo.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:leonardo]
platform = atmelavr
board = leonardo
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Leonardo 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
simavr Yes Yes

Name Description
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.

•
Arduino Leonardo ETH
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduino

Please use leonardoeth ID for board option in "platformio.ini" (Project Configuration File):

[env:leonardoeth]
platform = atmelavr
board = leonardoeth


You can override default Arduino Leonardo ETH settings per build environment using board_*** option, where *** is a JSON object path from board manifest leonardoeth.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:leonardoeth]
platform = atmelavr
board = leonardoeth
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Leonardo ETH 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
simavr Yes Yes

Name Description
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.

•
Arduino LilyPad ATmega168
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168
Frequency 8MHz
Flash 14KB
RAM 1KB
Vendor Arduino

Please use lilypadatmega168 ID for board option in "platformio.ini" (Project Configuration File):

[env:lilypadatmega168]
platform = atmelavr
board = lilypadatmega168


You can override default Arduino LilyPad ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lilypadatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lilypadatmega168]
platform = atmelavr
board = lilypadatmega168
; change microcontroller
board_build.mcu = atmega168
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino LilyPad ATmega168 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
simavr Yes Yes

Name Description
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.

•
Arduino LilyPad ATmega328
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 30KB
RAM 2KB
Vendor Arduino

Please use lilypadatmega328 ID for board option in "platformio.ini" (Project Configuration File):

[env:lilypadatmega328]
platform = atmelavr
board = lilypadatmega328


You can override default Arduino LilyPad ATmega328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lilypadatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lilypadatmega328]
platform = atmelavr
board = lilypadatmega328
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino LilyPad ATmega328 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
simavr Yes Yes

Name Description
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.

•
Arduino LilyPad USB
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor Arduino

Please use LilyPadUSB ID for board option in "platformio.ini" (Project Configuration File):

[env:LilyPadUSB]
platform = atmelavr
board = LilyPadUSB


You can override default Arduino LilyPad USB settings per build environment using board_*** option, where *** is a JSON object path from board manifest LilyPadUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:LilyPadUSB]
platform = atmelavr
board = LilyPadUSB
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino LilyPad USB 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
simavr Yes Yes

Name Description
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.

•
Arduino Mega ADK
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 16MHz
Flash 248KB
RAM 8KB
Vendor Arduino

Please use megaADK ID for board option in "platformio.ini" (Project Configuration File):

[env:megaADK]
platform = atmelavr
board = megaADK


You can override default Arduino Mega ADK settings per build environment using board_*** option, where *** is a JSON object path from board manifest megaADK.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:megaADK]
platform = atmelavr
board = megaADK
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Mega ADK 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
simavr Yes Yes

Name Description
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.

•
Arduino Mega or Mega 2560 ATmega1280
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1280
Frequency 16MHz
Flash 124KB
RAM 8KB
Vendor Arduino

Please use megaatmega1280 ID for board option in "platformio.ini" (Project Configuration File):

[env:megaatmega1280]
platform = atmelavr
board = megaatmega1280


You can override default Arduino Mega or Mega 2560 ATmega1280 settings per build environment using board_*** option, where *** is a JSON object path from board manifest megaatmega1280.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:megaatmega1280]
platform = atmelavr
board = megaatmega1280
; change microcontroller
board_build.mcu = atmega1280
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Mega or Mega 2560 ATmega1280 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
simavr Yes Yes

Name Description
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.

•
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 16MHz
Flash 248KB
RAM 8KB
Vendor Arduino

Please use megaatmega2560 ID for board option in "platformio.ini" (Project Configuration File):

[env:megaatmega2560]
platform = atmelavr
board = megaatmega2560


You can override default Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) settings per build environment using board_*** option, where *** is a JSON object path from board manifest megaatmega2560.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:megaatmega2560]
platform = atmelavr
board = megaatmega2560
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) 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
simavr Yes Yes

Name Description
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
Arduino Micro
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduino

Please use micro ID for board option in "platformio.ini" (Project Configuration File):

[env:micro]
platform = atmelavr
board = micro


You can override default Arduino Micro settings per build environment using board_*** option, where *** is a JSON object path from board manifest micro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:micro]
platform = atmelavr
board = micro
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Micro 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
simavr Yes Yes

Name Description
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.

•
Arduino Mini ATmega168
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168
Frequency 16MHz
Flash 14KB
RAM 1KB
Vendor Arduino

Please use miniatmega168 ID for board option in "platformio.ini" (Project Configuration File):

[env:miniatmega168]
platform = atmelavr
board = miniatmega168


You can override default Arduino Mini ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest miniatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:miniatmega168]
platform = atmelavr
board = miniatmega168
; change microcontroller
board_build.mcu = atmega168
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Mini ATmega168 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
simavr Yes Yes

Name Description
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.

•
Arduino Mini ATmega328
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 28KB
RAM 2KB
Vendor Arduino

Please use miniatmega328 ID for board option in "platformio.ini" (Project Configuration File):

[env:miniatmega328]
platform = atmelavr
board = miniatmega328


You can override default Arduino Mini ATmega328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest miniatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:miniatmega328]
platform = atmelavr
board = miniatmega328
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Mini ATmega328 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
simavr Yes Yes

Name Description
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.

•
Arduino NG or older ATmega168
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168
Frequency 16MHz
Flash 14KB
RAM 1KB
Vendor Arduino

Please use atmegangatmega168 ID for board option in "platformio.ini" (Project Configuration File):

[env:atmegangatmega168]
platform = atmelavr
board = atmegangatmega168


You can override default Arduino NG or older ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest atmegangatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:atmegangatmega168]
platform = atmelavr
board = atmegangatmega168
; change microcontroller
board_build.mcu = atmega168
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino NG or older ATmega168 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
simavr Yes Yes

Name Description
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.

•
Arduino NG or older ATmega8
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA8
Frequency 16MHz
Flash 7KB
RAM 1KB
Vendor Arduino

Please use atmegangatmega8 ID for board option in "platformio.ini" (Project Configuration File):

[env:atmegangatmega8]
platform = atmelavr
board = atmegangatmega8


You can override default Arduino NG or older ATmega8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest atmegangatmega8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:atmegangatmega8]
platform = atmelavr
board = atmegangatmega8
; change microcontroller
board_build.mcu = atmega8
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino NG or older ATmega8 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
simavr Yes Yes

Name Description
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.

•
Arduino Nano ATmega168
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168
Frequency 16MHz
Flash 14KB
RAM 1KB
Vendor Arduino

Please use nanoatmega168 ID for board option in "platformio.ini" (Project Configuration File):

[env:nanoatmega168]
platform = atmelavr
board = nanoatmega168


You can override default Arduino Nano ATmega168 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nanoatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nanoatmega168]
platform = atmelavr
board = nanoatmega168
; change microcontroller
board_build.mcu = atmega168
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Nano ATmega168 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
simavr Yes Yes

Name Description
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.

•
Arduino Nano ATmega328
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 30KB
RAM 2KB
Vendor Arduino

Please use nanoatmega328 ID for board option in "platformio.ini" (Project Configuration File):

[env:nanoatmega328]
platform = atmelavr
board = nanoatmega328


You can override default Arduino Nano ATmega328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nanoatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nanoatmega328]
platform = atmelavr
board = nanoatmega328
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Nano ATmega328 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
simavr Yes Yes

Name Description
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
Arduino Nano ATmega328 (New Bootloader)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 30KB
RAM 2KB
Vendor Arduino

Please use nanoatmega328new ID for board option in "platformio.ini" (Project Configuration File):

[env:nanoatmega328new]
platform = atmelavr
board = nanoatmega328new


You can override default Arduino Nano ATmega328 (New Bootloader) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nanoatmega328new.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nanoatmega328new]
platform = atmelavr
board = nanoatmega328new
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Nano ATmega328 (New Bootloader) 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
simavr Yes Yes

Name Description
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168
Frequency 8MHz
Flash 14KB
RAM 1KB
Vendor Arduino

Please use pro8MHzatmega168 ID for board option in "platformio.ini" (Project Configuration File):

[env:pro8MHzatmega168]
platform = atmelavr
board = pro8MHzatmega168


You can override default Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest pro8MHzatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:pro8MHzatmega168]
platform = atmelavr
board = pro8MHzatmega168
; change microcontroller
board_build.mcu = atmega168
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) 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
simavr Yes Yes

Name Description
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.

•
Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168
Frequency 16MHz
Flash 14KB
RAM 1KB
Vendor Arduino

Please use pro16MHzatmega168 ID for board option in "platformio.ini" (Project Configuration File):

[env:pro16MHzatmega168]
platform = atmelavr
board = pro16MHzatmega168


You can override default Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest pro16MHzatmega168.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:pro16MHzatmega168]
platform = atmelavr
board = pro16MHzatmega168
; change microcontroller
board_build.mcu = atmega168
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) 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
simavr Yes Yes

Name Description
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.

•
Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 30KB
RAM 2KB
Vendor Arduino

Please use pro8MHzatmega328 ID for board option in "platformio.ini" (Project Configuration File):

[env:pro8MHzatmega328]
platform = atmelavr
board = pro8MHzatmega328


You can override default Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest pro8MHzatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:pro8MHzatmega328]
platform = atmelavr
board = pro8MHzatmega328
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) 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
simavr Yes Yes

Name Description
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.

•
Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 30KB
RAM 2KB
Vendor Arduino

Please use pro16MHzatmega328 ID for board option in "platformio.ini" (Project Configuration File):

[env:pro16MHzatmega328]
platform = atmelavr
board = pro16MHzatmega328


You can override default Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest pro16MHzatmega328.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:pro16MHzatmega328]
platform = atmelavr
board = pro16MHzatmega328
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) 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
simavr Yes Yes

Name Description
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.

•
Arduino Robot Control
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduino

Please use robotControl ID for board option in "platformio.ini" (Project Configuration File):

[env:robotControl]
platform = atmelavr
board = robotControl


You can override default Arduino Robot Control settings per build environment using board_*** option, where *** is a JSON object path from board manifest robotControl.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:robotControl]
platform = atmelavr
board = robotControl
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Robot Control 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
simavr Yes Yes

Name Description
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.

•
Arduino Robot Motor
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduino

Please use robotMotor ID for board option in "platformio.ini" (Project Configuration File):

[env:robotMotor]
platform = atmelavr
board = robotMotor


You can override default Arduino Robot Motor settings per build environment using board_*** option, where *** is a JSON object path from board manifest robotMotor.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:robotMotor]
platform = atmelavr
board = robotMotor
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Robot Motor 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
simavr Yes Yes

Name Description
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.

•
Arduino Uno
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Arduino

Please use uno ID for board option in "platformio.ini" (Project Configuration File):

[env:uno]
platform = atmelavr
board = uno


You can override default Arduino Uno settings per build environment using board_*** option, where *** is a JSON object path from board manifest uno.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:uno]
platform = atmelavr
board = uno
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Uno 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
simavr Yes Yes

Name Description
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
Arduino Yun
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduino

Please use yun ID for board option in "platformio.ini" (Project Configuration File):

[env:yun]
platform = atmelavr
board = yun


You can override default Arduino Yun settings per build environment using board_*** option, where *** is a JSON object path from board manifest yun.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:yun]
platform = atmelavr
board = yun
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Yun 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
simavr Yes Yes

Name Description
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.

•
Arduino Yun Mini
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Arduino

Please use yunmini ID for board option in "platformio.ini" (Project Configuration File):

[env:yunmini]
platform = atmelavr
board = yunmini


You can override default Arduino Yun Mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest yunmini.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:yunmini]
platform = atmelavr
board = yunmini
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Yun Mini 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
simavr Yes Yes

Name Description
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.

•
Atmel AT90PWM216
  • Hardware
  • Configuration
  • Debugging


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller AT90PWM216
Frequency 16MHz
Flash 16KB
RAM 1KB
Vendor Microchip

Please use at90pwm216 ID for board option in "platformio.ini" (Project Configuration File):

[env:at90pwm216]
platform = atmelavr
board = at90pwm216


You can override default Atmel AT90PWM216 settings per build environment using board_*** option, where *** is a JSON object path from board manifest at90pwm216.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:at90pwm216]
platform = atmelavr
board = at90pwm216
; change microcontroller
board_build.mcu = at90pwm216
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Atmel AT90PWM216 board.

•
Atmel AT90PWM316
  • Hardware
  • Configuration
  • Debugging


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller AT90PWM316
Frequency 16MHz
Flash 16KB
RAM 1KB
Vendor Microchip

Please use at90pwm316 ID for board option in "platformio.ini" (Project Configuration File):

[env:at90pwm316]
platform = atmelavr
board = at90pwm316


You can override default Atmel AT90PWM316 settings per build environment using board_*** option, where *** is a JSON object path from board manifest at90pwm316.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:at90pwm316]
platform = atmelavr
board = at90pwm316
; change microcontroller
board_build.mcu = at90pwm316
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Atmel AT90PWM316 board.

•
BQ ZUM BT-328
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 28KB
RAM 2KB
Vendor BQ

Please use zumbt328 ID for board option in "platformio.ini" (Project Configuration File):

[env:zumbt328]
platform = atmelavr
board = zumbt328


You can override default BQ ZUM BT-328 settings per build environment using board_*** option, where *** is a JSON object path from board manifest zumbt328.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:zumbt328]
platform = atmelavr
board = zumbt328
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BQ ZUM BT-328 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
simavr Yes Yes

Name Description
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.

•
BitWizard Raspduino
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 30KB
RAM 2KB
Vendor BitWizard

Please use raspduino ID for board option in "platformio.ini" (Project Configuration File):

[env:raspduino]
platform = atmelavr
board = raspduino


You can override default BitWizard Raspduino settings per build environment using board_*** option, where *** is a JSON object path from board manifest raspduino.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:raspduino]
platform = atmelavr
board = raspduino
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BitWizard Raspduino 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
simavr Yes Yes

Name Description
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.

•
Controllino Maxi
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 16MHz
Flash 248KB
RAM 8KB
Vendor Controllino

Please use controllino_maxi ID for board option in "platformio.ini" (Project Configuration File):

[env:controllino_maxi]
platform = atmelavr
board = controllino_maxi


You can override default Controllino Maxi settings per build environment using board_*** option, where *** is a JSON object path from board manifest controllino_maxi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:controllino_maxi]
platform = atmelavr
board = controllino_maxi
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Controllino Maxi 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
simavr Yes Yes

Name Description
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.

•
Controllino Maxi Automation
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 16MHz
Flash 248KB
RAM 8KB
Vendor Controllino

Please use controllino_maxi_automation ID for board option in "platformio.ini" (Project Configuration File):

[env:controllino_maxi_automation]
platform = atmelavr
board = controllino_maxi_automation


You can override default Controllino Maxi Automation settings per build environment using board_*** option, where *** is a JSON object path from board manifest controllino_maxi_automation.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:controllino_maxi_automation]
platform = atmelavr
board = controllino_maxi_automation
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Controllino Maxi Automation 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
simavr Yes Yes

Name Description
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.

•
Controllino Mega
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 16MHz
Flash 248KB
RAM 8KB
Vendor Controllino

Please use controllino_mega ID for board option in "platformio.ini" (Project Configuration File):

[env:controllino_mega]
platform = atmelavr
board = controllino_mega


You can override default Controllino Mega settings per build environment using board_*** option, where *** is a JSON object path from board manifest controllino_mega.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:controllino_mega]
platform = atmelavr
board = controllino_mega
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Controllino Mega 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
simavr Yes Yes

Name Description
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.

•
Controllino Mini
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Controllino

Please use controllino_mini ID for board option in "platformio.ini" (Project Configuration File):

[env:controllino_mini]
platform = atmelavr
board = controllino_mini


You can override default Controllino Mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest controllino_mini.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:controllino_mini]
platform = atmelavr
board = controllino_mini
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Controllino Mini 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
simavr Yes Yes

Name Description
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.

•
Digispark Pro
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY167
Frequency 16MHz
Flash 14.50KB
RAM 512B
Vendor Digistump

Please use digispark-pro ID for board option in "platformio.ini" (Project Configuration File):

[env:digispark-pro]
platform = atmelavr
board = digispark-pro


You can override default Digispark Pro settings per build environment using board_*** option, where *** is a JSON object path from board manifest digispark-pro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:digispark-pro]
platform = atmelavr
board = digispark-pro
; change microcontroller
board_build.mcu = attiny167
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Digispark Pro board.

Name Description
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.

•
Digispark Pro (16 MHz) (64 byte buffer)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY167
Frequency 16MHz
Flash 14.50KB
RAM 512B
Vendor Digistump

Please use digispark-pro64 ID for board option in "platformio.ini" (Project Configuration File):

[env:digispark-pro64]
platform = atmelavr
board = digispark-pro64


You can override default Digispark Pro (16 MHz) (64 byte buffer) settings per build environment using board_*** option, where *** is a JSON object path from board manifest digispark-pro64.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:digispark-pro64]
platform = atmelavr
board = digispark-pro64
; change microcontroller
board_build.mcu = attiny167
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Digispark Pro (16 MHz) (64 byte buffer) board.

Name Description
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.

•
Digispark Pro (32 byte buffer)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY167
Frequency 16MHz
Flash 14.50KB
RAM 512B
Vendor Digistump

Please use digispark-pro32 ID for board option in "platformio.ini" (Project Configuration File):

[env:digispark-pro32]
platform = atmelavr
board = digispark-pro32


You can override default Digispark Pro (32 byte buffer) settings per build environment using board_*** option, where *** is a JSON object path from board manifest digispark-pro32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:digispark-pro32]
platform = atmelavr
board = digispark-pro32
; change microcontroller
board_build.mcu = attiny167
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Digispark Pro (32 byte buffer) board.

Name Description
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.

•
Digispark USB
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY85
Frequency 16MHz
Flash 5.87KB
RAM 512B
Vendor Digistump

Please use digispark-tiny ID for board option in "platformio.ini" (Project Configuration File):

[env:digispark-tiny]
platform = atmelavr
board = digispark-tiny


You can override default Digispark USB settings per build environment using board_*** option, where *** is a JSON object path from board manifest digispark-tiny.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:digispark-tiny]
platform = atmelavr
board = digispark-tiny
; change microcontroller
board_build.mcu = attiny85
; change MCU frequency
board_build.f_cpu = 16500000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Digispark USB 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
simavr Yes Yes

Name Description
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.

•
Dwenguino
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller AT90USB646
Frequency 16MHz
Flash 60KB
RAM 2KB
Vendor Dwengo

Please use dwenguino ID for board option in "platformio.ini" (Project Configuration File):

[env:dwenguino]
platform = atmelavr
board = dwenguino


You can override default Dwenguino settings per build environment using board_*** option, where *** is a JSON object path from board manifest dwenguino.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:dwenguino]
platform = atmelavr
board = dwenguino
; change microcontroller
board_build.mcu = at90usb646
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Dwenguino board.

Name Description
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.

•
Elektor Uno R4
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328PB
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Elektor

Please use elektor_uno_r4 ID for board option in "platformio.ini" (Project Configuration File):

[env:elektor_uno_r4]
platform = atmelavr
board = elektor_uno_r4


You can override default Elektor Uno R4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest elektor_uno_r4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:elektor_uno_r4]
platform = atmelavr
board = elektor_uno_r4
; change microcontroller
board_build.mcu = atmega328pb
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Elektor Uno R4 board.

Name Description
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.

•
Engduino 3
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor Engduino

Please use engduinov3 ID for board option in "platformio.ini" (Project Configuration File):

[env:engduinov3]
platform = atmelavr
board = engduinov3


You can override default Engduino 3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest engduinov3.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:engduinov3]
platform = atmelavr
board = engduinov3
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Engduino 3 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
simavr Yes Yes

Name Description
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.

•
EnviroDIY Mayfly
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 8MHz
Flash 127KB
RAM 16KB
Vendor EnviroDIY

Please use mayfly ID for board option in "platformio.ini" (Project Configuration File):

[env:mayfly]
platform = atmelavr
board = mayfly


You can override default EnviroDIY Mayfly settings per build environment using board_*** option, where *** is a JSON object path from board manifest mayfly.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mayfly]
platform = atmelavr
board = mayfly
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

EnviroDIY Mayfly 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
simavr Yes Yes

Name Description
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.

•
FYSETC F6 V1.3
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 16MHz
Flash 252KB
RAM 8KB
Vendor FYSETC

Please use fysetc_f6_13 ID for board option in "platformio.ini" (Project Configuration File):

[env:fysetc_f6_13]
platform = atmelavr
board = fysetc_f6_13


You can override default FYSETC F6 V1.3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest fysetc_f6_13.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:fysetc_f6_13]
platform = atmelavr
board = fysetc_f6_13
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

FYSETC F6 V1.3 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny13
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY13
Frequency 1MHz
Flash 1KB
RAM 64B
Vendor Atmel

Please use attiny13 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny13]
platform = atmelavr
board = attiny13


You can override default Generic ATtiny13 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny13.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny13]
platform = atmelavr
board = attiny13
; change microcontroller
board_build.mcu = attiny13
; change MCU frequency
board_build.f_cpu = 1200000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Generic ATtiny13 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny13A
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY13A
Frequency 1MHz
Flash 1KB
RAM 64B
Vendor Atmel

Please use attiny13a ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny13a]
platform = atmelavr
board = attiny13a


You can override default Generic ATtiny13A settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny13a.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny13a]
platform = atmelavr
board = attiny13a
; change microcontroller
board_build.mcu = attiny13a
; change MCU frequency
board_build.f_cpu = 1200000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Generic ATtiny13A 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny1634
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY1634
Frequency 8MHz
Flash 16KB
RAM 1KB
Vendor Atmel

Please use attiny1634 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny1634]
platform = atmelavr
board = attiny1634


You can override default Generic ATtiny1634 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny1634.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny1634]
platform = atmelavr
board = attiny1634
; change microcontroller
board_build.mcu = attiny1634
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny1634 board.

Name Description
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.

•
Generic ATtiny167
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY167
Frequency 8MHz
Flash 16KB
RAM 512B
Vendor Atmel

Please use attiny167 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny167]
platform = atmelavr
board = attiny167


You can override default Generic ATtiny167 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny167.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny167]
platform = atmelavr
board = attiny167
; change microcontroller
board_build.mcu = attiny167
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny167 board.

Name Description
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.

•
Generic ATtiny2313
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY2313
Frequency 8MHz
Flash 2KB
RAM 128B
Vendor Atmel

Please use attiny2313 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny2313]
platform = atmelavr
board = attiny2313


You can override default Generic ATtiny2313 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny2313.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny2313]
platform = atmelavr
board = attiny2313
; change microcontroller
board_build.mcu = attiny2313
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Generic ATtiny2313 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny24
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY24
Frequency 8MHz
Flash 2KB
RAM 128B
Vendor Atmel

Please use attiny24 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny24]
platform = atmelavr
board = attiny24


You can override default Generic ATtiny24 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny24.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny24]
platform = atmelavr
board = attiny24
; change microcontroller
board_build.mcu = attiny24
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Generic ATtiny24 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny25
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY25
Frequency 8MHz
Flash 2KB
RAM 128B
Vendor Atmel

Please use attiny25 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny25]
platform = atmelavr
board = attiny25


You can override default Generic ATtiny25 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny25.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny25]
platform = atmelavr
board = attiny25
; change microcontroller
board_build.mcu = attiny25
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Generic ATtiny25 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny261
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY261
Frequency 8MHz
Flash 2KB
RAM 128B
Vendor Atmel

Please use attiny261 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny261]
platform = atmelavr
board = attiny261


You can override default Generic ATtiny261 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny261.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny261]
platform = atmelavr
board = attiny261
; change microcontroller
board_build.mcu = attiny261
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny261 board.

Name Description
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.

•
Generic ATtiny4313
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY4313
Frequency 8MHz
Flash 4KB
RAM 256B
Vendor Atmel

Please use attiny4313 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny4313]
platform = atmelavr
board = attiny4313


You can override default Generic ATtiny4313 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny4313.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny4313]
platform = atmelavr
board = attiny4313
; change microcontroller
board_build.mcu = attiny4313
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Generic ATtiny4313 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny43U
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY43U
Frequency 8MHz
Flash 4KB
RAM 256B
Vendor Atmel

Please use attiny43 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny43]
platform = atmelavr
board = attiny43


You can override default Generic ATtiny43U settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny43.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny43]
platform = atmelavr
board = attiny43
; change microcontroller
board_build.mcu = attiny43u
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny43U board.

Name Description
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.

•
Generic ATtiny44
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY44
Frequency 8MHz
Flash 4KB
RAM 256B
Vendor Atmel

Please use attiny44 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny44]
platform = atmelavr
board = attiny44


You can override default Generic ATtiny44 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny44.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny44]
platform = atmelavr
board = attiny44
; change microcontroller
board_build.mcu = attiny44
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Generic ATtiny44 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny441
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY441
Frequency 8MHz
Flash 4KB
RAM 256B
Vendor Atmel

Please use attiny441 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny441]
platform = atmelavr
board = attiny441


You can override default Generic ATtiny441 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny441.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny441]
platform = atmelavr
board = attiny441
; change microcontroller
board_build.mcu = attiny441
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny441 board.

Name Description
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.

•
Generic ATtiny45
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY45
Frequency 8MHz
Flash 4KB
RAM 256B
Vendor Atmel

Please use attiny45 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny45]
platform = atmelavr
board = attiny45


You can override default Generic ATtiny45 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny45.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny45]
platform = atmelavr
board = attiny45
; change microcontroller
board_build.mcu = attiny45
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Generic ATtiny45 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny461
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY461
Frequency 8MHz
Flash 4KB
RAM 256B
Vendor Atmel

Please use attiny461 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny461]
platform = atmelavr
board = attiny461


You can override default Generic ATtiny461 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny461.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny461]
platform = atmelavr
board = attiny461
; change microcontroller
board_build.mcu = attiny461
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny461 board.

Name Description
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.

•
Generic ATtiny48
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY48
Frequency 8MHz
Flash 4KB
RAM 256B
Vendor Atmel

Please use attiny48 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny48]
platform = atmelavr
board = attiny48


You can override default Generic ATtiny48 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny48.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny48]
platform = atmelavr
board = attiny48
; change microcontroller
board_build.mcu = attiny48
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny48 board.

Name Description
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.

•
Generic ATtiny828
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY828
Frequency 8MHz
Flash 8KB
RAM 512B
Vendor Atmel

Please use attiny828 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny828]
platform = atmelavr
board = attiny828


You can override default Generic ATtiny828 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny828.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny828]
platform = atmelavr
board = attiny828
; change microcontroller
board_build.mcu = attiny828
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny828 board.

Name Description
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.

•
Generic ATtiny84
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY84
Frequency 8MHz
Flash 8KB
RAM 512B
Vendor Atmel

Please use attiny84 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny84]
platform = atmelavr
board = attiny84


You can override default Generic ATtiny84 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny84.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny84]
platform = atmelavr
board = attiny84
; change microcontroller
board_build.mcu = attiny84
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Generic ATtiny84 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny841
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY841
Frequency 8MHz
Flash 8KB
RAM 512B
Vendor Atmel

Please use attiny841 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny841]
platform = atmelavr
board = attiny841


You can override default Generic ATtiny841 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny841.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny841]
platform = atmelavr
board = attiny841
; change microcontroller
board_build.mcu = attiny841
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny841 board.

Name Description
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.

•
Generic ATtiny85
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY85
Frequency 8MHz
Flash 8KB
RAM 512B
Vendor Atmel

Please use attiny85 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny85]
platform = atmelavr
board = attiny85


You can override default Generic ATtiny85 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny85.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny85]
platform = atmelavr
board = attiny85
; change microcontroller
board_build.mcu = attiny85
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Generic ATtiny85 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
simavr Yes Yes

Name Description
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.

•
Generic ATtiny861
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY861
Frequency 8MHz
Flash 8KB
RAM 512B
Vendor Atmel

Please use attiny861 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny861]
platform = atmelavr
board = attiny861


You can override default Generic ATtiny861 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny861.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny861]
platform = atmelavr
board = attiny861
; change microcontroller
board_build.mcu = attiny861
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny861 board.

Name Description
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.

•
Generic ATtiny87
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY87
Frequency 8MHz
Flash 8KB
RAM 512B
Vendor Atmel

Please use attiny87 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny87]
platform = atmelavr
board = attiny87


You can override default Generic ATtiny87 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny87.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny87]
platform = atmelavr
board = attiny87
; change microcontroller
board_build.mcu = attiny87
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny87 board.

Name Description
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.

•
Generic ATtiny88
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATTINY88
Frequency 8MHz
Flash 8KB
RAM 512B
Vendor Atmel

Please use attiny88 ID for board option in "platformio.ini" (Project Configuration File):

[env:attiny88]
platform = atmelavr
board = attiny88


You can override default Generic ATtiny88 settings per build environment using board_*** option, where *** is a JSON object path from board manifest attiny88.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:attiny88]
platform = atmelavr
board = attiny88
; change microcontroller
board_build.mcu = attiny88
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger currently does not support Generic ATtiny88 board.

Name Description
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.

•
LightBlue Bean
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 31.50KB
RAM 2KB
Vendor Punch Through

Please use lightblue-bean ID for board option in "platformio.ini" (Project Configuration File):

[env:lightblue-bean]
platform = atmelavr
board = lightblue-bean


You can override default LightBlue Bean settings per build environment using board_*** option, where *** is a JSON object path from board manifest lightblue-bean.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lightblue-bean]
platform = atmelavr
board = lightblue-bean
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LightBlue Bean 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
simavr Yes Yes

Name Description
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.

•
LightBlue Bean+
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Punch Through

Please use lightblue-beanplus ID for board option in "platformio.ini" (Project Configuration File):

[env:lightblue-beanplus]
platform = atmelavr
board = lightblue-beanplus


You can override default LightBlue Bean+ settings per build environment using board_*** option, where *** is a JSON object path from board manifest lightblue-beanplus.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lightblue-beanplus]
platform = atmelavr
board = lightblue-beanplus
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LightBlue Bean+ 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
simavr Yes Yes

Name Description
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.

•
LightUp
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor LightUp

Please use lightup ID for board option in "platformio.ini" (Project Configuration File):

[env:lightup]
platform = atmelavr
board = lightup


You can override default LightUp settings per build environment using board_*** option, where *** is a JSON object path from board manifest lightup.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lightup]
platform = atmelavr
board = lightup
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LightUp 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
simavr Yes Yes

Name Description
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.

•
Linino One
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Linino

Please use one ID for board option in "platformio.ini" (Project Configuration File):

[env:one]
platform = atmelavr
board = one


You can override default Linino One settings per build environment using board_*** option, where *** is a JSON object path from board manifest one.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:one]
platform = atmelavr
board = one
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Linino One 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
simavr Yes Yes

Name Description
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.

•
LinkIt Smart 7688 Duo
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor MediaTek Labs

Please use smart7688 ID for board option in "platformio.ini" (Project Configuration File):

[env:smart7688]
platform = atmelavr
board = smart7688


You can override default LinkIt Smart 7688 Duo settings per build environment using board_*** option, where *** is a JSON object path from board manifest smart7688.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:smart7688]
platform = atmelavr
board = smart7688
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LinkIt Smart 7688 Duo 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
simavr Yes Yes

Name Description
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.

•
LoRa32u4II (868-915MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor BSFrance

Please use lora32u4II ID for board option in "platformio.ini" (Project Configuration File):

[env:lora32u4II]
platform = atmelavr
board = lora32u4II


You can override default LoRa32u4II (868-915MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest lora32u4II.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lora32u4II]
platform = atmelavr
board = lora32u4II
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LoRa32u4II (868-915MHz) 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
simavr Yes Yes

Name Description
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.

•
LowPowerLab MightyHat
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31KB
RAM 2KB
Vendor LowPowerLab

Please use mightyhat ID for board option in "platformio.ini" (Project Configuration File):

[env:mightyhat]
platform = atmelavr
board = mightyhat


You can override default LowPowerLab MightyHat settings per build environment using board_*** option, where *** is a JSON object path from board manifest mightyhat.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mightyhat]
platform = atmelavr
board = mightyhat
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LowPowerLab MightyHat 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
simavr Yes Yes

Name Description
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.

•
LowPowerLab Moteino
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor LowPowerLab

Please use moteino ID for board option in "platformio.ini" (Project Configuration File):

[env:moteino]
platform = atmelavr
board = moteino


You can override default LowPowerLab Moteino settings per build environment using board_*** option, where *** is a JSON object path from board manifest moteino.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:moteino]
platform = atmelavr
board = moteino
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LowPowerLab Moteino 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
simavr Yes Yes

Name Description
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.

•
LowPowerLab Moteino (8Mhz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 31.50KB
RAM 2KB
Vendor LowPowerLab

Please use moteino8mhz ID for board option in "platformio.ini" (Project Configuration File):

[env:moteino8mhz]
platform = atmelavr
board = moteino8mhz


You can override default LowPowerLab Moteino (8Mhz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest moteino8mhz.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:moteino8mhz]
platform = atmelavr
board = moteino8mhz
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LowPowerLab Moteino (8Mhz) 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
simavr Yes Yes

Name Description
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.

•
LowPowerLab MoteinoMEGA
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 16MHz
Flash 127KB
RAM 16KB
Vendor LowPowerLab

Please use moteinomega ID for board option in "platformio.ini" (Project Configuration File):

[env:moteinomega]
platform = atmelavr
board = moteinomega


You can override default LowPowerLab MoteinoMEGA settings per build environment using board_*** option, where *** is a JSON object path from board manifest moteinomega.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:moteinomega]
platform = atmelavr
board = moteinomega
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LowPowerLab MoteinoMEGA 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
simavr Yes Yes

Name Description
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.

Microduino Core (Atmega168PA@16M,5V)

•
Microduino Core (Atmega168PA@16M,5V)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168P
Frequency 16MHz
Flash 15.50KB
RAM 1KB
Vendor Microduino

Please use 168pa16m ID for board option in "platformio.ini" (Project Configuration File):

[env:168pa16m]
platform = atmelavr
board = 168pa16m


You can override default Microduino Core (Atmega168PA@16M,5V) settings per build environment using board_*** option, where *** is a JSON object path from board manifest 168pa16m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:168pa16m]
platform = atmelavr
board = 168pa16m
; change microcontroller
board_build.mcu = atmega168p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microduino Core (Atmega168PA@16M,5V) 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
simavr Yes Yes

Name Description
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.

Microduino Core (Atmega168PA@8M,3.3V)

•
Microduino Core (Atmega168PA@8M,3.3V)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA168P
Frequency 8MHz
Flash 15.50KB
RAM 1KB
Vendor Microduino

Please use 168pa8m ID for board option in "platformio.ini" (Project Configuration File):

[env:168pa8m]
platform = atmelavr
board = 168pa8m


You can override default Microduino Core (Atmega168PA@8M,3.3V) settings per build environment using board_*** option, where *** is a JSON object path from board manifest 168pa8m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:168pa8m]
platform = atmelavr
board = 168pa8m
; change microcontroller
board_build.mcu = atmega168p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microduino Core (Atmega168PA@8M,3.3V) 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
simavr Yes Yes

Name Description
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.

Microduino Core (Atmega328P@16M,5V)

•
Microduino Core (Atmega328P@16M,5V)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Microduino

Please use 328p16m ID for board option in "platformio.ini" (Project Configuration File):

[env:328p16m]
platform = atmelavr
board = 328p16m


You can override default Microduino Core (Atmega328P@16M,5V) settings per build environment using board_*** option, where *** is a JSON object path from board manifest 328p16m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:328p16m]
platform = atmelavr
board = 328p16m
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microduino Core (Atmega328P@16M,5V) 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
simavr Yes Yes

Name Description
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.

Microduino Core (Atmega328P@8M,3.3V)

•
Microduino Core (Atmega328P@8M,3.3V)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 31.50KB
RAM 2KB
Vendor Microduino

Please use 328p8m ID for board option in "platformio.ini" (Project Configuration File):

[env:328p8m]
platform = atmelavr
board = 328p8m


You can override default Microduino Core (Atmega328P@8M,3.3V) settings per build environment using board_*** option, where *** is a JSON object path from board manifest 328p8m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:328p8m]
platform = atmelavr
board = 328p8m
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microduino Core (Atmega328P@8M,3.3V) 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
simavr Yes Yes

Name Description
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.

•
Microduino Core USB (ATmega32U4@16M,5V)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Microduino

Please use 32u416m ID for board option in "platformio.ini" (Project Configuration File):

[env:32u416m]
platform = atmelavr
board = 32u416m


You can override default Microduino Core USB (ATmega32U4@16M,5V) settings per build environment using board_*** option, where *** is a JSON object path from board manifest 32u416m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:32u416m]
platform = atmelavr
board = 32u416m
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microduino Core USB (ATmega32U4@16M,5V) 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
simavr Yes Yes

Name Description
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.

Microduino Core+ (ATmega1284P@16M,5V)

•
Microduino Core+ (ATmega1284P@16M,5V)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 16MHz
Flash 127KB
RAM 16KB
Vendor Microduino

Please use 1284p16m ID for board option in "platformio.ini" (Project Configuration File):

[env:1284p16m]
platform = atmelavr
board = 1284p16m


You can override default Microduino Core+ (ATmega1284P@16M,5V) settings per build environment using board_*** option, where *** is a JSON object path from board manifest 1284p16m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:1284p16m]
platform = atmelavr
board = 1284p16m
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microduino Core+ (ATmega1284P@16M,5V) 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
simavr Yes Yes

Name Description
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.

Microduino Core+ (ATmega1284P@8M,3.3V)

•
Microduino Core+ (ATmega1284P@8M,3.3V)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 8MHz
Flash 127KB
RAM 16KB
Vendor Microduino

Please use 1284p8m ID for board option in "platformio.ini" (Project Configuration File):

[env:1284p8m]
platform = atmelavr
board = 1284p8m


You can override default Microduino Core+ (ATmega1284P@8M,3.3V) settings per build environment using board_*** option, where *** is a JSON object path from board manifest 1284p8m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:1284p8m]
platform = atmelavr
board = 1284p8m
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microduino Core+ (ATmega1284P@8M,3.3V) 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
simavr Yes Yes

Name Description
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.

Microduino Core+ (Atmega644PA@16M,5V)

•
Microduino Core+ (Atmega644PA@16M,5V)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA644P
Frequency 16MHz
Flash 63KB
RAM 4KB
Vendor Microduino

Please use 644pa16m ID for board option in "platformio.ini" (Project Configuration File):

[env:644pa16m]
platform = atmelavr
board = 644pa16m


You can override default Microduino Core+ (Atmega644PA@16M,5V) settings per build environment using board_*** option, where *** is a JSON object path from board manifest 644pa16m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:644pa16m]
platform = atmelavr
board = 644pa16m
; change microcontroller
board_build.mcu = atmega644p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microduino Core+ (Atmega644PA@16M,5V) 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
simavr Yes Yes

Name Description
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.

Microduino Core+ (Atmega644PA@8M,3.3V)

•
Microduino Core+ (Atmega644PA@8M,3.3V)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA644P
Frequency 8MHz
Flash 63KB
RAM 4KB
Vendor Microduino

Please use 644pa8m ID for board option in "platformio.ini" (Project Configuration File):

[env:644pa8m]
platform = atmelavr
board = 644pa8m


You can override default Microduino Core+ (Atmega644PA@8M,3.3V) settings per build environment using board_*** option, where *** is a JSON object path from board manifest 644pa8m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:644pa8m]
platform = atmelavr
board = 644pa8m
; change microcontroller
board_build.mcu = atmega644p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microduino Core+ (Atmega644PA@8M,3.3V) 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
simavr Yes Yes

Name Description
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.

•
OpenEnergyMonitor emonPi
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 30KB
RAM 2KB
Vendor OpenEnergyMonitor

Please use emonpi ID for board option in "platformio.ini" (Project Configuration File):

[env:emonpi]
platform = atmelavr
board = emonpi


You can override default OpenEnergyMonitor emonPi settings per build environment using board_*** option, where *** is a JSON object path from board manifest emonpi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:emonpi]
platform = atmelavr
board = emonpi
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

OpenEnergyMonitor emonPi 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
simavr Yes Yes

Name Description
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.

•
Original Prusa i3 MK3 Multi Material 2.0 Upgrade
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Prusa 3D

Please use prusa_mm_control ID for board option in "platformio.ini" (Project Configuration File):

[env:prusa_mm_control]
platform = atmelavr
board = prusa_mm_control


You can override default Original Prusa i3 MK3 Multi Material 2.0 Upgrade settings per build environment using board_*** option, where *** is a JSON object path from board manifest prusa_mm_control.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:prusa_mm_control]
platform = atmelavr
board = prusa_mm_control
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Original Prusa i3 MK3 Multi Material 2.0 Upgrade 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
simavr Yes Yes

Name Description
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.

•
PanStamp AVR
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 31.50KB
RAM 2KB
Vendor PanStamp

Please use panStampAVR ID for board option in "platformio.ini" (Project Configuration File):

[env:panStampAVR]
platform = atmelavr
board = panStampAVR


You can override default PanStamp AVR settings per build environment using board_*** option, where *** is a JSON object path from board manifest panStampAVR.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:panStampAVR]
platform = atmelavr
board = panStampAVR
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

PanStamp AVR 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
simavr Yes Yes

Name Description
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.

•
Pinoccio Scout
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA256RFR2
Frequency 16MHz
Flash 248KB
RAM 32KB
Vendor Pinoccio

Please use pinoccio ID for board option in "platformio.ini" (Project Configuration File):

[env:pinoccio]
platform = atmelavr
board = pinoccio


You can override default Pinoccio Scout settings per build environment using board_*** option, where *** is a JSON object path from board manifest pinoccio.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:pinoccio]
platform = atmelavr
board = pinoccio
; change microcontroller
board_build.mcu = atmega256rfr2
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Pinoccio Scout board.

Name Description
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.

•
Pololu A-Star 32U4
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Pololu Corporation

Please use a-star32U4 ID for board option in "platformio.ini" (Project Configuration File):

[env:a-star32U4]
platform = atmelavr
board = a-star32U4


You can override default Pololu A-Star 32U4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest a-star32U4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:a-star32U4]
platform = atmelavr
board = a-star32U4
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Pololu A-Star 32U4 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
simavr Yes Yes

Name Description
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.

•
Prusa RAMBo
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 16MHz
Flash 252KB
RAM 8KB
Vendor Prusa 3D

Please use prusa_rambo ID for board option in "platformio.ini" (Project Configuration File):

[env:prusa_rambo]
platform = atmelavr
board = prusa_rambo


You can override default Prusa RAMBo settings per build environment using board_*** option, where *** is a JSON object path from board manifest prusa_rambo.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:prusa_rambo]
platform = atmelavr
board = prusa_rambo
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Prusa RAMBo 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
simavr Yes Yes

Name Description
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.

•
Quirkbot
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor Quirkbot

Please use quirkbot ID for board option in "platformio.ini" (Project Configuration File):

[env:quirkbot]
platform = atmelavr
board = quirkbot


You can override default Quirkbot settings per build environment using board_*** option, where *** is a JSON object path from board manifest quirkbot.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:quirkbot]
platform = atmelavr
board = quirkbot
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Quirkbot 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
simavr Yes Yes

Name Description
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.

•
RedBearLab Blend
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor RedBearLab

Please use blend ID for board option in "platformio.ini" (Project Configuration File):

[env:blend]
platform = atmelavr
board = blend


You can override default RedBearLab Blend settings per build environment using board_*** option, where *** is a JSON object path from board manifest blend.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:blend]
platform = atmelavr
board = blend
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RedBearLab Blend 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
simavr Yes Yes

Name Description
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.

•
RedBearLab Blend Micro 3.3V/16MHz (overclock)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor RedBearLab

Please use blendmicro16 ID for board option in "platformio.ini" (Project Configuration File):

[env:blendmicro16]
platform = atmelavr
board = blendmicro16


You can override default RedBearLab Blend Micro 3.3V/16MHz (overclock) settings per build environment using board_*** option, where *** is a JSON object path from board manifest blendmicro16.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:blendmicro16]
platform = atmelavr
board = blendmicro16
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RedBearLab Blend Micro 3.3V/16MHz (overclock) 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
simavr Yes Yes

Name Description
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.

•
RedBearLab Blend Micro 3.3V/8MHz
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor RedBearLab

Please use blendmicro8 ID for board option in "platformio.ini" (Project Configuration File):

[env:blendmicro8]
platform = atmelavr
board = blendmicro8


You can override default RedBearLab Blend Micro 3.3V/8MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest blendmicro8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:blendmicro8]
platform = atmelavr
board = blendmicro8
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RedBearLab Blend Micro 3.3V/8MHz 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
simavr Yes Yes

Name Description
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.

•
RepRap RAMBo
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 16MHz
Flash 252KB
RAM 8KB
Vendor RepRap

Please use reprap_rambo ID for board option in "platformio.ini" (Project Configuration File):

[env:reprap_rambo]
platform = atmelavr
board = reprap_rambo


You can override default RepRap RAMBo settings per build environment using board_*** option, where *** is a JSON object path from board manifest reprap_rambo.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:reprap_rambo]
platform = atmelavr
board = reprap_rambo
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RepRap RAMBo 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
simavr Yes Yes

Name Description
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.

•
SODAQ GaLoRa
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 8MHz
Flash 127KB
RAM 16KB
Vendor SODAQ

Please use sodaq_galora ID for board option in "platformio.ini" (Project Configuration File):

[env:sodaq_galora]
platform = atmelavr
board = sodaq_galora


You can override default SODAQ GaLoRa settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_galora.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sodaq_galora]
platform = atmelavr
board = sodaq_galora
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SODAQ GaLoRa 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
simavr Yes Yes

Name Description
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.

•
SODAQ Mbili
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 8MHz
Flash 127KB
RAM 16KB
Vendor SODAQ

Please use sodaq_mbili ID for board option in "platformio.ini" (Project Configuration File):

[env:sodaq_mbili]
platform = atmelavr
board = sodaq_mbili


You can override default SODAQ Mbili settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_mbili.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sodaq_mbili]
platform = atmelavr
board = sodaq_mbili
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SODAQ Mbili 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
simavr Yes Yes

Name Description
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.

•
SODAQ Moja
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 31.50KB
RAM 2KB
Vendor SODAQ

Please use sodaq_moja ID for board option in "platformio.ini" (Project Configuration File):

[env:sodaq_moja]
platform = atmelavr
board = sodaq_moja


You can override default SODAQ Moja settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_moja.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sodaq_moja]
platform = atmelavr
board = sodaq_moja
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SODAQ Moja 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
simavr Yes Yes

Name Description
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.

•
SODAQ Ndogo
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 8MHz
Flash 127KB
RAM 16KB
Vendor SODAQ

Please use sodaq_ndogo ID for board option in "platformio.ini" (Project Configuration File):

[env:sodaq_ndogo]
platform = atmelavr
board = sodaq_ndogo


You can override default SODAQ Ndogo settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_ndogo.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sodaq_ndogo]
platform = atmelavr
board = sodaq_ndogo
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SODAQ Ndogo 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
simavr Yes Yes

Name Description
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.

•
SODAQ Tatu
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 8MHz
Flash 127KB
RAM 16KB
Vendor SODAQ

Please use sodaq_tatu ID for board option in "platformio.ini" (Project Configuration File):

[env:sodaq_tatu]
platform = atmelavr
board = sodaq_tatu


You can override default SODAQ Tatu settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_tatu.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sodaq_tatu]
platform = atmelavr
board = sodaq_tatu
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SODAQ Tatu 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
simavr Yes Yes

Name Description
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.

•
Sanguino ATmega1284p (16MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 16MHz
Flash 127KB
RAM 16KB
Vendor Sanguino

Please use sanguino_atmega1284p ID for board option in "platformio.ini" (Project Configuration File):

[env:sanguino_atmega1284p]
platform = atmelavr
board = sanguino_atmega1284p


You can override default Sanguino ATmega1284p (16MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest sanguino_atmega1284p.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sanguino_atmega1284p]
platform = atmelavr
board = sanguino_atmega1284p
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Sanguino ATmega1284p (16MHz) 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
simavr Yes Yes

Name Description
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.

•
Sanguino ATmega1284p (8MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 8MHz
Flash 127KB
RAM 16KB
Vendor Sanguino

Please use sanguino_atmega1284_8m ID for board option in "platformio.ini" (Project Configuration File):

[env:sanguino_atmega1284_8m]
platform = atmelavr
board = sanguino_atmega1284_8m


You can override default Sanguino ATmega1284p (8MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest sanguino_atmega1284_8m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sanguino_atmega1284_8m]
platform = atmelavr
board = sanguino_atmega1284_8m
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Sanguino ATmega1284p (8MHz) 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
simavr Yes Yes

Name Description
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.

•
Sanguino ATmega644 or ATmega644A (16 MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA644
Frequency 16MHz
Flash 63KB
RAM 4KB
Vendor Sanguino

Please use sanguino_atmega644 ID for board option in "platformio.ini" (Project Configuration File):

[env:sanguino_atmega644]
platform = atmelavr
board = sanguino_atmega644


You can override default Sanguino ATmega644 or ATmega644A (16 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest sanguino_atmega644.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sanguino_atmega644]
platform = atmelavr
board = sanguino_atmega644
; change microcontroller
board_build.mcu = atmega644
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Sanguino ATmega644 or ATmega644A (16 MHz) 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
simavr Yes Yes

Name Description
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.

•
Sanguino ATmega644 or ATmega644A (8 MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA644
Frequency 8MHz
Flash 63KB
RAM 4KB
Vendor Sanguino

Please use sanguino_atmega644_8m ID for board option in "platformio.ini" (Project Configuration File):

[env:sanguino_atmega644_8m]
platform = atmelavr
board = sanguino_atmega644_8m


You can override default Sanguino ATmega644 or ATmega644A (8 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest sanguino_atmega644_8m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sanguino_atmega644_8m]
platform = atmelavr
board = sanguino_atmega644_8m
; change microcontroller
board_build.mcu = atmega644
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Sanguino ATmega644 or ATmega644A (8 MHz) 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
simavr Yes Yes

Name Description
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.

•
Sanguino ATmega644P or ATmega644PA (16 MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA644P
Frequency 16MHz
Flash 63KB
RAM 4KB
Vendor Sanguino

Please use sanguino_atmega644p ID for board option in "platformio.ini" (Project Configuration File):

[env:sanguino_atmega644p]
platform = atmelavr
board = sanguino_atmega644p


You can override default Sanguino ATmega644P or ATmega644PA (16 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest sanguino_atmega644p.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sanguino_atmega644p]
platform = atmelavr
board = sanguino_atmega644p
; change microcontroller
board_build.mcu = atmega644p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Sanguino ATmega644P or ATmega644PA (16 MHz) 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
simavr Yes Yes

Name Description
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.

•
Sanguino ATmega644P or ATmega644PA (8 MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA644P
Frequency 8MHz
Flash 63KB
RAM 4KB
Vendor Sanguino

Please use sanguino_atmega644p_8m ID for board option in "platformio.ini" (Project Configuration File):

[env:sanguino_atmega644p_8m]
platform = atmelavr
board = sanguino_atmega644p_8m


You can override default Sanguino ATmega644P or ATmega644PA (8 MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest sanguino_atmega644p_8m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sanguino_atmega644p_8m]
platform = atmelavr
board = sanguino_atmega644p_8m
; change microcontroller
board_build.mcu = atmega644p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Sanguino ATmega644P or ATmega644PA (8 MHz) 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
simavr Yes Yes

Name Description
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.

•
Seeeduino
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor SeeedStudio

Please use seeeduino ID for board option in "platformio.ini" (Project Configuration File):

[env:seeeduino]
platform = atmelavr
board = seeeduino


You can override default Seeeduino settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeeduino.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:seeeduino]
platform = atmelavr
board = seeeduino
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Seeeduino 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
simavr Yes Yes

Name Description
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
SparkFun ATmega128RFA1 Dev Board
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA128RFA1
Frequency 16MHz
Flash 16KB
RAM 124KB
Vendor SparkFun

Please use sparkfun_satmega128rfa1 ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_satmega128rfa1]
platform = atmelavr
board = sparkfun_satmega128rfa1


You can override default SparkFun ATmega128RFA1 Dev Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_satmega128rfa1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_satmega128rfa1]
platform = atmelavr
board = sparkfun_satmega128rfa1
; change microcontroller
board_build.mcu = atmega128rfa1
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun ATmega128RFA1 Dev Board 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
simavr Yes Yes

Name Description
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.

•
SparkFun Digital Sandbox
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 31.50KB
RAM 2KB
Vendor SparkFun

Please use sparkfun_digitalsandbox ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_digitalsandbox]
platform = atmelavr
board = sparkfun_digitalsandbox


You can override default SparkFun Digital Sandbox settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_digitalsandbox.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_digitalsandbox]
platform = atmelavr
board = sparkfun_digitalsandbox
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Digital Sandbox 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
simavr Yes Yes

Name Description
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.

•
SparkFun Fio V3 3.3V/8MHz
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor SparkFun

Please use sparkfun_fiov3 ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_fiov3]
platform = atmelavr
board = sparkfun_fiov3


You can override default SparkFun Fio V3 3.3V/8MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_fiov3.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_fiov3]
platform = atmelavr
board = sparkfun_fiov3
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Fio V3 3.3V/8MHz 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
simavr Yes Yes

Name Description
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.

•
SparkFun Makey Makey
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor SparkFun

Please use sparkfun_makeymakey ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_makeymakey]
platform = atmelavr
board = sparkfun_makeymakey


You can override default SparkFun Makey Makey settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_makeymakey.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_makeymakey]
platform = atmelavr
board = sparkfun_makeymakey
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Makey Makey 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
simavr Yes Yes

Name Description
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.

•
SparkFun Mega Pro 3.3V/8MHz
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 8MHz
Flash 252KB
RAM 8KB
Vendor SparkFun

Please use sparkfun_megapro8MHz ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_megapro8MHz]
platform = atmelavr
board = sparkfun_megapro8MHz


You can override default SparkFun Mega Pro 3.3V/8MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_megapro8MHz.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_megapro8MHz]
platform = atmelavr
board = sparkfun_megapro8MHz
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Mega Pro 3.3V/8MHz 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
simavr Yes Yes

Name Description
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.

•
SparkFun Mega Pro 5V/16MHz
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 16MHz
Flash 248KB
RAM 8KB
Vendor SparkFun

Please use sparkfun_megapro16MHz ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_megapro16MHz]
platform = atmelavr
board = sparkfun_megapro16MHz


You can override default SparkFun Mega Pro 5V/16MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_megapro16MHz.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_megapro16MHz]
platform = atmelavr
board = sparkfun_megapro16MHz
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Mega Pro 5V/16MHz 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
simavr Yes Yes

Name Description
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.

•
SparkFun Mega Pro Mini 3.3V
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA2560
Frequency 8MHz
Flash 252KB
RAM 8KB
Vendor SparkFun

Please use sparkfun_megamini ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_megamini]
platform = atmelavr
board = sparkfun_megamini


You can override default SparkFun Mega Pro Mini 3.3V settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_megamini.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_megamini]
platform = atmelavr
board = sparkfun_megamini
; change microcontroller
board_build.mcu = atmega2560
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Mega Pro Mini 3.3V 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
simavr Yes Yes

Name Description
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.

•
SparkFun MicroView
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor SparkFun

Please use uview ID for board option in "platformio.ini" (Project Configuration File):

[env:uview]
platform = atmelavr
board = uview


You can override default SparkFun MicroView settings per build environment using board_*** option, where *** is a JSON object path from board manifest uview.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:uview]
platform = atmelavr
board = uview
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun MicroView 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
simavr Yes Yes

Name Description
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.

•
SparkFun Pro Micro 3.3V/8MHz
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor SparkFun

Please use sparkfun_promicro8 ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_promicro8]
platform = atmelavr
board = sparkfun_promicro8


You can override default SparkFun Pro Micro 3.3V/8MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_promicro8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_promicro8]
platform = atmelavr
board = sparkfun_promicro8
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Pro Micro 3.3V/8MHz 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
simavr Yes Yes

Name Description
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.

•
SparkFun Pro Micro 5V/16MHz
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor SparkFun

Please use sparkfun_promicro16 ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_promicro16]
platform = atmelavr
board = sparkfun_promicro16


You can override default SparkFun Pro Micro 5V/16MHz settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_promicro16.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_promicro16]
platform = atmelavr
board = sparkfun_promicro16
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Pro Micro 5V/16MHz 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
simavr Yes Yes

Name Description
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.

•
SparkFun Qduino Mini
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 8MHz
Flash 28KB
RAM 2.50KB
Vendor SparkFun

Please use sparkfun_qduinomini ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_qduinomini]
platform = atmelavr
board = sparkfun_qduinomini


You can override default SparkFun Qduino Mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_qduinomini.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_qduinomini]
platform = atmelavr
board = sparkfun_qduinomini
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Qduino Mini 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
simavr Yes Yes

Name Description
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.

•
SparkFun RedBoard
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor SparkFun

Please use sparkfun_redboard ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_redboard]
platform = atmelavr
board = sparkfun_redboard


You can override default SparkFun RedBoard settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_redboard.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_redboard]
platform = atmelavr
board = sparkfun_redboard
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun RedBoard 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
simavr Yes Yes

Name Description
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.

•
SparkFun Serial 7-Segment Display
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 31.50KB
RAM 2KB
Vendor SparkFun

Please use sparkfun_serial7seg ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_serial7seg]
platform = atmelavr
board = sparkfun_serial7seg


You can override default SparkFun Serial 7-Segment Display settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_serial7seg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_serial7seg]
platform = atmelavr
board = sparkfun_serial7seg
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Serial 7-Segment Display 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
simavr Yes Yes

Name Description
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.

•
SpellFoundry Sleepy Pi 2
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 30KB
RAM 2KB
Vendor SpellFoundry

Please use sleepypi ID for board option in "platformio.ini" (Project Configuration File):

[env:sleepypi]
platform = atmelavr
board = sleepypi


You can override default SpellFoundry Sleepy Pi 2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest sleepypi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sleepypi]
platform = atmelavr
board = sleepypi
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SpellFoundry Sleepy Pi 2 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
simavr Yes Yes

Name Description
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.

•
Talk2 Whisper Node
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor Wisen

Please use whispernode ID for board option in "platformio.ini" (Project Configuration File):

[env:whispernode]
platform = atmelavr
board = whispernode


You can override default Talk2 Whisper Node settings per build environment using board_*** option, where *** is a JSON object path from board manifest whispernode.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:whispernode]
platform = atmelavr
board = whispernode
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Talk2 Whisper Node 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
simavr Yes Yes

Name Description
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.

•
The Things Uno
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor The Things Network

Please use the_things_uno ID for board option in "platformio.ini" (Project Configuration File):

[env:the_things_uno]
platform = atmelavr
board = the_things_uno


You can override default The Things Uno settings per build environment using board_*** option, where *** is a JSON object path from board manifest the_things_uno.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:the_things_uno]
platform = atmelavr
board = the_things_uno
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

The Things Uno 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
simavr Yes Yes

Name Description
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.

•
TinyCircuits TinyDuino Processor Board
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 30KB
RAM 2KB
Vendor TinyCircuits

Please use tinyduino ID for board option in "platformio.ini" (Project Configuration File):

[env:tinyduino]
platform = atmelavr
board = tinyduino


You can override default TinyCircuits TinyDuino Processor Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest tinyduino.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:tinyduino]
platform = atmelavr
board = tinyduino
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TinyCircuits TinyDuino Processor Board 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
simavr Yes Yes

Name Description
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.

•
TinyCircuits TinyLily Mini Processor
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 8MHz
Flash 30KB
RAM 2KB
Vendor TinyCircuits

Please use tinylily ID for board option in "platformio.ini" (Project Configuration File):

[env:tinylily]
platform = atmelavr
board = tinylily


You can override default TinyCircuits TinyLily Mini Processor settings per build environment using board_*** option, where *** is a JSON object path from board manifest tinylily.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:tinylily]
platform = atmelavr
board = tinylily
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TinyCircuits TinyLily Mini Processor 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
simavr Yes Yes

Name Description
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.

•
USBasp stick
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA8
Frequency 12MHz
Flash 8KB
RAM 1KB
Vendor Atmel

Please use usbasp ID for board option in "platformio.ini" (Project Configuration File):

[env:usbasp]
platform = atmelavr
board = usbasp


You can override default USBasp stick settings per build environment using board_*** option, where *** is a JSON object path from board manifest usbasp.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:usbasp]
platform = atmelavr
board = usbasp
; change microcontroller
board_build.mcu = atmega8
; change MCU frequency
board_build.f_cpu = 12000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

USBasp stick 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
simavr Yes Yes

Name Description
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.

•
Wicked Device WildFire V2
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 16MHz
Flash 120.00KB
RAM 16KB
Vendor Wicked Device

Please use wildfirev2 ID for board option in "platformio.ini" (Project Configuration File):

[env:wildfirev2]
platform = atmelavr
board = wildfirev2


You can override default Wicked Device WildFire V2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest wildfirev2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wildfirev2]
platform = atmelavr
board = wildfirev2
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Wicked Device WildFire V2 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
simavr Yes Yes

Name Description
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.

•
Wicked Device WildFire V3
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 16MHz
Flash 127KB
RAM 16KB
Vendor Wicked Device

Please use wildfirev3 ID for board option in "platformio.ini" (Project Configuration File):

[env:wildfirev3]
platform = atmelavr
board = wildfirev3


You can override default Wicked Device WildFire V3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest wildfirev3.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wildfirev3]
platform = atmelavr
board = wildfirev3
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Wicked Device WildFire V3 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
simavr Yes Yes

Name Description
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.

•
ftDuino
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 28KB
RAM 2.50KB
Vendor Till Harbaum

Please use ftduino ID for board option in "platformio.ini" (Project Configuration File):

[env:ftduino]
platform = atmelavr
board = ftduino


You can override default ftDuino settings per build environment using board_*** option, where *** is a JSON object path from board manifest ftduino.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ftduino]
platform = atmelavr
board = ftduino
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ftDuino 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
simavr Yes Yes

Name Description
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.

nicai-systems BOB3 coding bot

•
nicai-systems BOB3 coding bot
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA88
Frequency 8MHz
Flash 8KB
RAM 1KB
Vendor nicai-systems

Please use bob3 ID for board option in "platformio.ini" (Project Configuration File):

[env:bob3]
platform = atmelavr
board = bob3


You can override default nicai-systems BOB3 coding bot settings per build environment using board_*** option, where *** is a JSON object path from board manifest bob3.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:bob3]
platform = atmelavr
board = bob3
; change microcontroller
board_build.mcu = atmega88
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

nicai-systems BOB3 coding bot 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
simavr Yes Yes

Name Description
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.

nicai-systems NIBO 2 robot

•
nicai-systems NIBO 2 robot
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA128
Frequency 16MHz
Flash 128KB
RAM 4KB
Vendor nicai-systems

Please use nibo2 ID for board option in "platformio.ini" (Project Configuration File):

[env:nibo2]
platform = atmelavr
board = nibo2


You can override default nicai-systems NIBO 2 robot settings per build environment using board_*** option, where *** is a JSON object path from board manifest nibo2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nibo2]
platform = atmelavr
board = nibo2
; change microcontroller
board_build.mcu = atmega128
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

nicai-systems NIBO 2 robot 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
simavr Yes Yes

Name Description
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.

nicai-systems NIBO burger robot

•
nicai-systems NIBO burger robot
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA16
Frequency 15MHz
Flash 16KB
RAM 1KB
Vendor nicai-systems

Please use niboburger ID for board option in "platformio.ini" (Project Configuration File):

[env:niboburger]
platform = atmelavr
board = niboburger


You can override default nicai-systems NIBO burger robot settings per build environment using board_*** option, where *** is a JSON object path from board manifest niboburger.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:niboburger]
platform = atmelavr
board = niboburger
; change microcontroller
board_build.mcu = atmega16
; change MCU frequency
board_build.f_cpu = 15000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

nicai-systems NIBO burger robot 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
simavr Yes Yes

Name Description
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.

nicai-systems NIBO burger robot with Tuning Kit

•
nicai-systems NIBO burger robot with Tuning Kit
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 20MHz
Flash 128KB
RAM 16KB
Vendor nicai-systems

Please use niboburger_1284 ID for board option in "platformio.ini" (Project Configuration File):

[env:niboburger_1284]
platform = atmelavr
board = niboburger_1284


You can override default nicai-systems NIBO burger robot with Tuning Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest niboburger_1284.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:niboburger_1284]
platform = atmelavr
board = niboburger_1284
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 20000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

nicai-systems NIBO burger robot with Tuning 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
simavr Yes Yes

Name Description
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.

nicai-systems NIBObee robot

•
nicai-systems NIBObee robot
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA16
Frequency 15MHz
Flash 16KB
RAM 1KB
Vendor nicai-systems

Please use nibobee ID for board option in "platformio.ini" (Project Configuration File):

[env:nibobee]
platform = atmelavr
board = nibobee


You can override default nicai-systems NIBObee robot settings per build environment using board_*** option, where *** is a JSON object path from board manifest nibobee.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nibobee]
platform = atmelavr
board = nibobee
; change microcontroller
board_build.mcu = atmega16
; change MCU frequency
board_build.f_cpu = 15000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

nicai-systems NIBObee robot 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
simavr Yes Yes

Name Description
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.

nicai-systems NIBObee robot with Tuning Kit

•
nicai-systems NIBObee robot with Tuning Kit
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA1284P
Frequency 20MHz
Flash 128KB
RAM 16KB
Vendor nicai-systems

Please use nibobee_1284 ID for board option in "platformio.ini" (Project Configuration File):

[env:nibobee_1284]
platform = atmelavr
board = nibobee_1284


You can override default nicai-systems NIBObee robot with Tuning Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest nibobee_1284.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nibobee_1284]
platform = atmelavr
board = nibobee_1284
; change microcontroller
board_build.mcu = atmega1284p
; change MCU frequency
board_build.f_cpu = 20000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

nicai-systems NIBObee robot with Tuning 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
simavr Yes Yes

Name Description
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.

•
ubIQio Ardhat
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel AVR: Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Microcontroller ATMEGA328P
Frequency 16MHz
Flash 31.50KB
RAM 2KB
Vendor ubIQio

Please use ardhat ID for board option in "platformio.ini" (Project Configuration File):

[env:ardhat]
platform = atmelavr
board = ardhat


You can override default ubIQio Ardhat settings per build environment using board_*** option, where *** is a JSON object path from board manifest ardhat.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ardhat]
platform = atmelavr
board = ardhat
; change microcontroller
board_build.mcu = atmega328p
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ubIQio Ardhat 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
simavr Yes Yes

Name Description
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.

Atmel megaAVR

•
Arduino Nano Every
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel megaAVR: 8-bit MCUs Built for Real-time Control with Core Independent Peripherals combining intelligent hardware peripherals along with the low-power capability of an AVR core, megaAVR microcontrollers (MCUs) broaden the effectiveness of your real-time control systems.

Microcontroller ATMEGA4809
Frequency 16MHz
Flash 47.50KB
RAM 6KB
Vendor Arduino

Please use nano_every ID for board option in "platformio.ini" (Project Configuration File):

[env:nano_every]
platform = atmelmegaavr
board = nano_every


You can override default Arduino Nano Every settings per build environment using board_*** option, where *** is a JSON object path from board manifest nano_every.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nano_every]
platform = atmelmegaavr
board = nano_every
; change microcontroller
board_build.mcu = atmega4809
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Arduino Nano Every board.

Name Description
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.

•
Arduino Uno WiFi Rev2
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel megaAVR: 8-bit MCUs Built for Real-time Control with Core Independent Peripherals combining intelligent hardware peripherals along with the low-power capability of an AVR core, megaAVR microcontrollers (MCUs) broaden the effectiveness of your real-time control systems.

Microcontroller ATMEGA4809
Frequency 16MHz
Flash 47.50KB
RAM 6KB
Vendor Arduino

Please use uno_wifi_rev2 ID for board option in "platformio.ini" (Project Configuration File):

[env:uno_wifi_rev2]
platform = atmelmegaavr
board = uno_wifi_rev2


You can override default Arduino Uno WiFi Rev2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest uno_wifi_rev2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:uno_wifi_rev2]
platform = atmelmegaavr
board = uno_wifi_rev2
; change microcontroller
board_build.mcu = atmega4809
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger currently does not support Arduino Uno WiFi Rev2 board.

Name Description
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.

Atmel SAM

•
Adafruit Circuit Playground Express
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Adafruit

Please use adafruit_circuitplayground_m0 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_circuitplayground_m0]
platform = atmelsam
board = adafruit_circuitplayground_m0


You can override default Adafruit Circuit Playground Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_circuitplayground_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_circuitplayground_m0]
platform = atmelsam
board = adafruit_circuitplayground_m0
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Adafruit Circuit Playground Express supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_circuitplayground_m0]
platform = atmelsam
board = adafruit_circuitplayground_m0
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Circuit Playground Express 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Adafruit Crickit M0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Adafruit

Please use adafruit_crickit_m0 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_crickit_m0]
platform = atmelsam
board = adafruit_crickit_m0


You can override default Adafruit Crickit M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_crickit_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_crickit_m0]
platform = atmelsam
board = adafruit_crickit_m0
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Adafruit Crickit M0 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_crickit_m0]
platform = atmelsam
board = adafruit_crickit_m0
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Crickit 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.

Compatible Tools On-board Default
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Adafruit Feather M0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Adafruit

Please use adafruit_feather_m0 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_feather_m0]
platform = atmelsam
board = adafruit_feather_m0


You can override default Adafruit Feather M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_feather_m0]
platform = atmelsam
board = adafruit_feather_m0
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Adafruit Feather M0 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_feather_m0]
platform = atmelsam
board = adafruit_feather_m0
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Feather 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.

Compatible Tools On-board Default
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.
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.

•
Adafruit Feather M0 Express
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Adafruit

Please use adafruit_feather_m0_express ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_feather_m0_express]
platform = atmelsam
board = adafruit_feather_m0_express


You can override default Adafruit Feather M0 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_m0_express.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_feather_m0_express]
platform = atmelsam
board = adafruit_feather_m0_express
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Adafruit Feather M0 Express supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_feather_m0_express]
platform = atmelsam
board = adafruit_feather_m0_express
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Feather M0 Express 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Adafruit Feather M4 Express
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J19A
Frequency 120MHz
Flash 512KB
RAM 192KB
Vendor Adafruit

Please use adafruit_feather_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_feather_m4]
platform = atmelsam
board = adafruit_feather_m4


You can override default Adafruit Feather M4 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_feather_m4]
platform = atmelsam
board = adafruit_feather_m4
; change microcontroller
board_build.mcu = samd51j19a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit Feather M4 Express supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_feather_m4]
platform = atmelsam
board = adafruit_feather_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Feather M4 Express 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit Gemma M0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21E18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Adafruit

Please use adafruit_gemma_m0 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_gemma_m0]
platform = atmelsam
board = adafruit_gemma_m0


You can override default Adafruit Gemma M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_gemma_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_gemma_m0]
platform = atmelsam
board = adafruit_gemma_m0
; change microcontroller
board_build.mcu = samd21e18a
; change MCU frequency
board_build.f_cpu = 48000000L


Adafruit Gemma M0 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_gemma_m0]
platform = atmelsam
board = adafruit_gemma_m0
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Gemma 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.

Compatible Tools On-board Default
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Adafruit Grand Central M4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51P20A
Frequency 120MHz
Flash 1MB
RAM 256KB
Vendor Adafruit

Please use adafruit_grandcentral_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_grandcentral_m4]
platform = atmelsam
board = adafruit_grandcentral_m4


You can override default Adafruit Grand Central M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_grandcentral_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_grandcentral_m4]
platform = atmelsam
board = adafruit_grandcentral_m4
; change microcontroller
board_build.mcu = samd51p20a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit Grand Central M4 supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_grandcentral_m4]
platform = atmelsam
board = adafruit_grandcentral_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Grand Central M4 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit Hallowing M0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Adafruit

Please use adafruit_hallowing ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_hallowing]
platform = atmelsam
board = adafruit_hallowing


You can override default Adafruit Hallowing M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_hallowing.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_hallowing]
platform = atmelsam
board = adafruit_hallowing
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Adafruit Hallowing M0 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_hallowing]
platform = atmelsam
board = adafruit_hallowing
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Hallowing 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.

Compatible Tools On-board Default
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Adafruit Hallowing M4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J19A
Frequency 120MHz
Flash 496KB
RAM 192KB
Vendor Adafruit

Please use adafruit_hallowing_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_hallowing_m4]
platform = atmelsam
board = adafruit_hallowing_m4


You can override default Adafruit Hallowing M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_hallowing_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_hallowing_m4]
platform = atmelsam
board = adafruit_hallowing_m4
; change microcontroller
board_build.mcu = samd51j19a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit Hallowing M4 supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_hallowing_m4]
platform = atmelsam
board = adafruit_hallowing_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Hallowing M4 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit ItsyBitsy M0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Adafruit

Please use adafruit_itsybitsy_m0 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_itsybitsy_m0]
platform = atmelsam
board = adafruit_itsybitsy_m0


You can override default Adafruit ItsyBitsy M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_itsybitsy_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_itsybitsy_m0]
platform = atmelsam
board = adafruit_itsybitsy_m0
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Adafruit ItsyBitsy M0 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_itsybitsy_m0]
platform = atmelsam
board = adafruit_itsybitsy_m0
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit ItsyBitsy 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.

Compatible Tools On-board Default
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Adafruit ItsyBitsy M4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51G19A
Frequency 120MHz
Flash 512KB
RAM 192KB
Vendor Adafruit

Please use adafruit_itsybitsy_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_itsybitsy_m4]
platform = atmelsam
board = adafruit_itsybitsy_m4


You can override default Adafruit ItsyBitsy M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_itsybitsy_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_itsybitsy_m4]
platform = atmelsam
board = adafruit_itsybitsy_m4
; change microcontroller
board_build.mcu = samd51g19a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit ItsyBitsy M4 supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_itsybitsy_m4]
platform = atmelsam
board = adafruit_itsybitsy_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit ItsyBitsy M4 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit MONSTER M4SK
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51G19A
Frequency 120MHz
Flash 496KB
RAM 192KB
Vendor Adafruit

Please use adafruit_monster_m4sk ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_monster_m4sk]
platform = atmelsam
board = adafruit_monster_m4sk


You can override default Adafruit MONSTER M4SK settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_monster_m4sk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_monster_m4sk]
platform = atmelsam
board = adafruit_monster_m4sk
; change microcontroller
board_build.mcu = samd51g19a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit MONSTER M4SK supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_monster_m4sk]
platform = atmelsam
board = adafruit_monster_m4sk
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit MONSTER M4SK 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit Metro M0 Expresss
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Adafruit

Please use adafruit_metro_m0 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_metro_m0]
platform = atmelsam
board = adafruit_metro_m0


You can override default Adafruit Metro M0 Expresss settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_metro_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_metro_m0]
platform = atmelsam
board = adafruit_metro_m0
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Adafruit Metro M0 Expresss supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_metro_m0]
platform = atmelsam
board = adafruit_metro_m0
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Metro M0 Expresss 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Adafruit Metro M4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J19A
Frequency 120MHz
Flash 512KB
RAM 192KB
Vendor Adafruit

Please use adafruit_metro_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_metro_m4]
platform = atmelsam
board = adafruit_metro_m4


You can override default Adafruit Metro M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_metro_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_metro_m4]
platform = atmelsam
board = adafruit_metro_m4
; change microcontroller
board_build.mcu = samd51j19a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit Metro M4 supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_metro_m4]
platform = atmelsam
board = adafruit_metro_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Metro M4 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit Metro M4 AirLift Lite
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J19A
Frequency 120MHz
Flash 512KB
RAM 192KB
Vendor Adafruit

Please use adafruit_metro_m4_airliftlite ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_metro_m4_airliftlite]
platform = atmelsam
board = adafruit_metro_m4_airliftlite


You can override default Adafruit Metro M4 AirLift Lite settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_metro_m4_airliftlite.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_metro_m4_airliftlite]
platform = atmelsam
board = adafruit_metro_m4_airliftlite
; change microcontroller
board_build.mcu = samd51j19a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit Metro M4 AirLift Lite supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_metro_m4_airliftlite]
platform = atmelsam
board = adafruit_metro_m4_airliftlite
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Metro M4 AirLift Lite does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit PyGamer Advance M4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J20A
Frequency 120MHz
Flash 1MB
RAM 256KB
Vendor Adafruit

Please use adafruit_pygamer_advance_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_pygamer_advance_m4]
platform = atmelsam
board = adafruit_pygamer_advance_m4


You can override default Adafruit PyGamer Advance M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pygamer_advance_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_pygamer_advance_m4]
platform = atmelsam
board = adafruit_pygamer_advance_m4
; change microcontroller
board_build.mcu = samd51j20a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit PyGamer Advance M4 supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_pygamer_advance_m4]
platform = atmelsam
board = adafruit_pygamer_advance_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit PyGamer Advance M4 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit PyGamer M4 Express
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J19A
Frequency 120MHz
Flash 512KB
RAM 192KB
Vendor Adafruit

Please use adafruit_pygamer_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_pygamer_m4]
platform = atmelsam
board = adafruit_pygamer_m4


You can override default Adafruit PyGamer M4 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pygamer_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_pygamer_m4]
platform = atmelsam
board = adafruit_pygamer_m4
; change microcontroller
board_build.mcu = samd51j19a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit PyGamer M4 Express supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_pygamer_m4]
platform = atmelsam
board = adafruit_pygamer_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit PyGamer M4 Express 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit PyPortal M4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J20A
Frequency 120MHz
Flash 1MB
RAM 256KB
Vendor Adafruit

Please use adafruit_pyportal_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_pyportal_m4]
platform = atmelsam
board = adafruit_pyportal_m4


You can override default Adafruit PyPortal M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pyportal_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_pyportal_m4]
platform = atmelsam
board = adafruit_pyportal_m4
; change microcontroller
board_build.mcu = samd51j20a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit PyPortal M4 supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_pyportal_m4]
platform = atmelsam
board = adafruit_pyportal_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit PyPortal M4 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit PyPortal M4 Titano
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J20A
Frequency 120MHz
Flash 1MB
RAM 256KB
Vendor Adafruit

Please use adafruit_pyportal_m4_titano ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_pyportal_m4_titano]
platform = atmelsam
board = adafruit_pyportal_m4_titano


You can override default Adafruit PyPortal M4 Titano settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pyportal_m4_titano.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_pyportal_m4_titano]
platform = atmelsam
board = adafruit_pyportal_m4_titano
; change microcontroller
board_build.mcu = samd51j20a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit PyPortal M4 Titano supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_pyportal_m4_titano]
platform = atmelsam
board = adafruit_pyportal_m4_titano
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit PyPortal M4 Titano 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit Trellis M4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J19A
Frequency 120MHz
Flash 512KB
RAM 192KB
Vendor Adafruit

Please use adafruit_trellis_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_trellis_m4]
platform = atmelsam
board = adafruit_trellis_m4


You can override default Adafruit Trellis M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_trellis_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_trellis_m4]
platform = atmelsam
board = adafruit_trellis_m4
; change microcontroller
board_build.mcu = samd51j19a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit Trellis M4 supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_trellis_m4]
platform = atmelsam
board = adafruit_trellis_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Trellis M4 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit Trinket M0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21E18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Adafruit

Please use adafruit_trinket_m0 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_trinket_m0]
platform = atmelsam
board = adafruit_trinket_m0


You can override default Adafruit Trinket M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_trinket_m0.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_trinket_m0]
platform = atmelsam
board = adafruit_trinket_m0
; change microcontroller
board_build.mcu = samd21e18a
; change MCU frequency
board_build.f_cpu = 48000000L


Adafruit Trinket M0 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_trinket_m0]
platform = atmelsam
board = adafruit_trinket_m0
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Trinket 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.

Compatible Tools On-board Default
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.
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.

•
Adafruit pIRkey
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21E18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Adafruit

Please use adafruit_pirkey ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_pirkey]
platform = atmelsam
board = adafruit_pirkey


You can override default Adafruit pIRkey settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pirkey.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_pirkey]
platform = atmelsam
board = adafruit_pirkey
; change microcontroller
board_build.mcu = samd21e18a
; change MCU frequency
board_build.f_cpu = 48000000L


Adafruit pIRkey supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_pirkey]
platform = atmelsam
board = adafruit_pirkey
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit pIRkey 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Adafruit pyBadge AirLift M4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J20A
Frequency 120MHz
Flash 1008KB
RAM 192KB
Vendor Adafruit

Please use adafruit_pybadge_airlift_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_pybadge_airlift_m4]
platform = atmelsam
board = adafruit_pybadge_airlift_m4


You can override default Adafruit pyBadge AirLift M4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pybadge_airlift_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_pybadge_airlift_m4]
platform = atmelsam
board = adafruit_pybadge_airlift_m4
; change microcontroller
board_build.mcu = samd51j20a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit pyBadge AirLift M4 supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_pybadge_airlift_m4]
platform = atmelsam
board = adafruit_pybadge_airlift_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit pyBadge AirLift M4 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Adafruit pyBadge M4 Express
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD51J19A
Frequency 120MHz
Flash 512KB
RAM 192KB
Vendor Adafruit

Please use adafruit_pybadge_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_pybadge_m4]
platform = atmelsam
board = adafruit_pybadge_m4


You can override default Adafruit pyBadge M4 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_pybadge_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_pybadge_m4]
platform = atmelsam
board = adafruit_pybadge_m4
; change microcontroller
board_build.mcu = samd51j19a
; change MCU frequency
board_build.f_cpu = 120000000L


Adafruit pyBadge M4 Express supports the next uploading protocols:

  • atmel-ice
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:adafruit_pybadge_m4]
platform = atmelsam
board = adafruit_pybadge_m4
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit pyBadge M4 Express 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
Atmel-ICE Yes
J-LINK

Name Description
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.

•
Arduino Due (Programming Port)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller AT91SAM3X8E
Frequency 84MHz
Flash 512KB
RAM 96KB
Vendor Arduino

Please use due ID for board option in "platformio.ini" (Project Configuration File):

[env:due]
platform = atmelsam
board = due


You can override default Arduino Due (Programming Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest due.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:due]
platform = atmelsam
board = due
; change microcontroller
board_build.mcu = at91sam3x8e
; change MCU frequency
board_build.f_cpu = 84000000L


Arduino Due (Programming Port) supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba
  • stlink

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:due]
platform = atmelsam
board = due
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Due (Programming Port) 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
Atmel-ICE Yes
Black Magic Probe
J-LINK
ST-LINK

Name Description
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.

•
Arduino Due (USB Native Port)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller AT91SAM3X8E
Frequency 84MHz
Flash 512KB
RAM 96KB
Vendor Arduino

Please use dueUSB ID for board option in "platformio.ini" (Project Configuration File):

[env:dueUSB]
platform = atmelsam
board = dueUSB


You can override default Arduino Due (USB Native Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest dueUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:dueUSB]
platform = atmelsam
board = dueUSB
; change microcontroller
board_build.mcu = at91sam3x8e
; change MCU frequency
board_build.f_cpu = 84000000L


Arduino Due (USB Native Port) supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba
  • stlink

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:dueUSB]
platform = atmelsam
board = dueUSB
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Due (USB Native Port) 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
Atmel-ICE Yes
Black Magic Probe
J-LINK
ST-LINK

Name Description
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
Arduino M0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mzeroUSB ID for board option in "platformio.ini" (Project Configuration File):

[env:mzeroUSB]
platform = atmelsam
board = mzeroUSB


You can override default Arduino M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mzeroUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mzeroUSB]
platform = atmelsam
board = mzeroUSB
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino M0 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • stk500v2

Default protocol is stk500v2

You can change upload protocol using upload_protocol option:

[env:mzeroUSB]
platform = atmelsam
board = mzeroUSB
upload_protocol = stk500v2


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino 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.

Compatible Tools On-board Default
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino M0 Pro (Native USB Port)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mzeroproUSB ID for board option in "platformio.ini" (Project Configuration File):

[env:mzeroproUSB]
platform = atmelsam
board = mzeroproUSB


You can override default Arduino M0 Pro (Native USB Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest mzeroproUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mzeroproUSB]
platform = atmelsam
board = mzeroproUSB
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino M0 Pro (Native USB Port) supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • stk500v2

Default protocol is stk500v2

You can change upload protocol using upload_protocol option:

[env:mzeroproUSB]
platform = atmelsam
board = mzeroproUSB
upload_protocol = stk500v2


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino M0 Pro (Native USB Port) 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino M0 Pro (Programming/Debug Port)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mzeropro ID for board option in "platformio.ini" (Project Configuration File):

[env:mzeropro]
platform = atmelsam
board = mzeropro


You can override default Arduino M0 Pro (Programming/Debug Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest mzeropro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mzeropro]
platform = atmelsam
board = mzeropro
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino M0 Pro (Programming/Debug Port) supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • cmsis-dap
  • jlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:mzeropro]
platform = atmelsam
board = mzeropro
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino M0 Pro (Programming/Debug Port) 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
Atmel-ICE
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
Arduino MKR FOX 1200
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mkrfox1200 ID for board option in "platformio.ini" (Project Configuration File):

[env:mkrfox1200]
platform = atmelsam
board = mkrfox1200


You can override default Arduino MKR FOX 1200 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrfox1200.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mkrfox1200]
platform = atmelsam
board = mkrfox1200
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino MKR FOX 1200 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:mkrfox1200]
platform = atmelsam
board = mkrfox1200
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino MKR FOX 1200 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino MKR GSM 1400
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mkrgsm1400 ID for board option in "platformio.ini" (Project Configuration File):

[env:mkrgsm1400]
platform = atmelsam
board = mkrgsm1400


You can override default Arduino MKR GSM 1400 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrgsm1400.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mkrgsm1400]
platform = atmelsam
board = mkrgsm1400
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino MKR GSM 1400 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:mkrgsm1400]
platform = atmelsam
board = mkrgsm1400
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino MKR GSM 1400 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino MKR NB 1500
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mkrnb1500 ID for board option in "platformio.ini" (Project Configuration File):

[env:mkrnb1500]
platform = atmelsam
board = mkrnb1500


You can override default Arduino MKR NB 1500 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrnb1500.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mkrnb1500]
platform = atmelsam
board = mkrnb1500
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino MKR NB 1500 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:mkrnb1500]
platform = atmelsam
board = mkrnb1500
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino MKR NB 1500 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino MKR WAN 1300
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mkrwan1300 ID for board option in "platformio.ini" (Project Configuration File):

[env:mkrwan1300]
platform = atmelsam
board = mkrwan1300


You can override default Arduino MKR WAN 1300 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrwan1300.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mkrwan1300]
platform = atmelsam
board = mkrwan1300
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino MKR WAN 1300 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:mkrwan1300]
platform = atmelsam
board = mkrwan1300
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino MKR WAN 1300 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino MKR WAN 1310
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mkrwan1310 ID for board option in "platformio.ini" (Project Configuration File):

[env:mkrwan1310]
platform = atmelsam
board = mkrwan1310


You can override default Arduino MKR WAN 1310 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrwan1310.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mkrwan1310]
platform = atmelsam
board = mkrwan1310
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino MKR WAN 1310 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:mkrwan1310]
platform = atmelsam
board = mkrwan1310
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino MKR WAN 1310 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino MKR WiFi 1010
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mkrwifi1010 ID for board option in "platformio.ini" (Project Configuration File):

[env:mkrwifi1010]
platform = atmelsam
board = mkrwifi1010


You can override default Arduino MKR WiFi 1010 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrwifi1010.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mkrwifi1010]
platform = atmelsam
board = mkrwifi1010
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino MKR WiFi 1010 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:mkrwifi1010]
platform = atmelsam
board = mkrwifi1010
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino MKR WiFi 1010 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino MKR1000
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mkr1000USB ID for board option in "platformio.ini" (Project Configuration File):

[env:mkr1000USB]
platform = atmelsam
board = mkr1000USB


You can override default Arduino MKR1000 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkr1000USB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mkr1000USB]
platform = atmelsam
board = mkr1000USB
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino MKR1000 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:mkr1000USB]
platform = atmelsam
board = mkr1000USB
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino MKR1000 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino MKRZERO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mkrzero ID for board option in "platformio.ini" (Project Configuration File):

[env:mkrzero]
platform = atmelsam
board = mkrzero


You can override default Arduino MKRZERO settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrzero.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mkrzero]
platform = atmelsam
board = mkrzero
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino MKRZERO supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:mkrzero]
platform = atmelsam
board = mkrzero
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino MKRZERO 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino Tian
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use tian ID for board option in "platformio.ini" (Project Configuration File):

[env:tian]
platform = atmelsam
board = tian


You can override default Arduino Tian settings per build environment using board_*** option, where *** is a JSON object path from board manifest tian.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:tian]
platform = atmelsam
board = tian
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino Tian supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • stk500v2

Default protocol is stk500v2

You can change upload protocol using upload_protocol option:

[env:tian]
platform = atmelsam
board = tian
upload_protocol = stk500v2


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Tian 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Arduino Zero (Programming/Debug Port)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use zero ID for board option in "platformio.ini" (Project Configuration File):

[env:zero]
platform = atmelsam
board = zero


You can override default Arduino Zero (Programming/Debug Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest zero.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:zero]
platform = atmelsam
board = zero
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino Zero (Programming/Debug Port) supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • cmsis-dap
  • jlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:zero]
platform = atmelsam
board = zero
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Zero (Programming/Debug Port) 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
Atmel-ICE
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
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.

•
Arduino Zero (USB Native Port)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use zeroUSB ID for board option in "platformio.ini" (Project Configuration File):

[env:zeroUSB]
platform = atmelsam
board = zeroUSB


You can override default Arduino Zero (USB Native Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest zeroUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:zeroUSB]
platform = atmelsam
board = zeroUSB
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Arduino Zero (USB Native Port) supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:zeroUSB]
platform = atmelsam
board = zeroUSB
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Zero (USB Native Port) 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Atmel ATSAMR21-XPRO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMR21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Atmel

Please use samr21_xpro ID for board option in "platformio.ini" (Project Configuration File):

[env:samr21_xpro]
platform = atmelsam
board = samr21_xpro


You can override default Atmel ATSAMR21-XPRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest samr21_xpro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:samr21_xpro]
platform = atmelsam
board = samr21_xpro
; change microcontroller
board_build.mcu = samr21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Atmel ATSAMR21-XPRO supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • cmsis-dap
  • jlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:samr21_xpro]
platform = atmelsam
board = samr21_xpro
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Atmel ATSAMR21-XPRO 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
Atmel-ICE
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
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.

•
Atmel ATSAMW25-XPRO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Atmel

Please use samd21g18a ID for board option in "platformio.ini" (Project Configuration File):

[env:samd21g18a]
platform = atmelsam
board = samd21g18a


You can override default Atmel ATSAMW25-XPRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest samd21g18a.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:samd21g18a]
platform = atmelsam
board = samd21g18a
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Atmel ATSAMW25-XPRO supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • cmsis-dap
  • jlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:samd21g18a]
platform = atmelsam
board = samd21g18a
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Atmel ATSAMW25-XPRO 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
Atmel-ICE
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
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.

•
Atmel SAMC21-XPRO
  • Hardware
  • Configuration
  • Uploading
  • Debugging


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMC21J18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Atmel

Please use samc21_xpro ID for board option in "platformio.ini" (Project Configuration File):

[env:samc21_xpro]
platform = atmelsam
board = samc21_xpro


You can override default Atmel SAMC21-XPRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest samc21_xpro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:samc21_xpro]
platform = atmelsam
board = samc21_xpro
; change microcontroller
board_build.mcu = samc21j18a
; change MCU frequency
board_build.f_cpu = 48000000L


Atmel SAMC21-XPRO supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • cmsis-dap
  • jlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:samc21_xpro]
platform = atmelsam
board = samc21_xpro
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Atmel SAMC21-XPRO 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
Atmel-ICE
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

•
Atmel SAMD21-XPRO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21J18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Atmel

Please use samd21_xpro ID for board option in "platformio.ini" (Project Configuration File):

[env:samd21_xpro]
platform = atmelsam
board = samd21_xpro


You can override default Atmel SAMD21-XPRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest samd21_xpro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:samd21_xpro]
platform = atmelsam
board = samd21_xpro
; change microcontroller
board_build.mcu = samd21j18a
; change MCU frequency
board_build.f_cpu = 48000000L


Atmel SAMD21-XPRO supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • cmsis-dap
  • jlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:samd21_xpro]
platform = atmelsam
board = samd21_xpro
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Atmel SAMD21-XPRO 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
Atmel-ICE
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
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.

•
Atmel SAML21-XPRO-B
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAML21J18B
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Atmel

Please use saml21_xpro_b ID for board option in "platformio.ini" (Project Configuration File):

[env:saml21_xpro_b]
platform = atmelsam
board = saml21_xpro_b


You can override default Atmel SAML21-XPRO-B settings per build environment using board_*** option, where *** is a JSON object path from board manifest saml21_xpro_b.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:saml21_xpro_b]
platform = atmelsam
board = saml21_xpro_b
; change microcontroller
board_build.mcu = saml21j18b
; change MCU frequency
board_build.f_cpu = 48000000L


Atmel SAML21-XPRO-B supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • cmsis-dap
  • jlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:saml21_xpro_b]
platform = atmelsam
board = saml21_xpro_b
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Atmel SAML21-XPRO-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
Atmel-ICE
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

Briki ABC (MBC-WB) - Samd21

•
Briki ABC (MBC-WB) - Samd21
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor meteca

Please use briki_abc_samd21 ID for board option in "platformio.ini" (Project Configuration File):

[env:briki_abc_samd21]
platform = atmelsam
board = briki_abc_samd21


You can override default Briki ABC (MBC-WB) - Samd21 settings per build environment using board_*** option, where *** is a JSON object path from board manifest briki_abc_samd21.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:briki_abc_samd21]
platform = atmelsam
board = briki_abc_samd21
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Briki ABC (MBC-WB) - Samd21 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • mbctool
  • sam-ba
  • stk500v2

Default protocol is mbctool

You can change upload protocol using upload_protocol option:

[env:briki_abc_samd21]
platform = atmelsam
board = briki_abc_samd21
upload_protocol = mbctool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Briki ABC (MBC-WB) - Samd21 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

Briki MBC-WB - Samd21

•
Briki MBC-WB - Samd21
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor meteca

Please use briki_mbcwb_samd21 ID for board option in "platformio.ini" (Project Configuration File):

[env:briki_mbcwb_samd21]
platform = atmelsam
board = briki_mbcwb_samd21


You can override default Briki MBC-WB - Samd21 settings per build environment using board_*** option, where *** is a JSON object path from board manifest briki_mbcwb_samd21.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:briki_mbcwb_samd21]
platform = atmelsam
board = briki_mbcwb_samd21
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Briki MBC-WB - Samd21 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • mbctool
  • sam-ba
  • stk500v2

Default protocol is mbctool

You can change upload protocol using upload_protocol option:

[env:briki_mbcwb_samd21]
platform = atmelsam
board = briki_mbcwb_samd21
upload_protocol = mbctool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Briki MBC-WB - Samd21 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Digistump DigiX
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller AT91SAM3X8E
Frequency 84MHz
Flash 512KB
RAM 96KB
Vendor Digistump

Please use digix ID for board option in "platformio.ini" (Project Configuration File):

[env:digix]
platform = atmelsam
board = digix


You can override default Digistump DigiX settings per build environment using board_*** option, where *** is a JSON object path from board manifest digix.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:digix]
platform = atmelsam
board = digix
; change microcontroller
board_build.mcu = at91sam3x8e
; change MCU frequency
board_build.f_cpu = 84000000L


Digistump DigiX supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba
  • stlink

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:digix]
platform = atmelsam
board = digix
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Digistump DigiX 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
Atmel-ICE Yes
Black Magic Probe
J-LINK
ST-LINK

Name Description
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.

•
LowPowerLab CurrentRanger
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor LowPowerLab

Please use current_ranger ID for board option in "platformio.ini" (Project Configuration File):

[env:current_ranger]
platform = atmelsam
board = current_ranger


You can override default LowPowerLab CurrentRanger settings per build environment using board_*** option, where *** is a JSON object path from board manifest current_ranger.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:current_ranger]
platform = atmelsam
board = current_ranger
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support LowPowerLab CurrentRanger board.

Name Description
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.

•
MKR Vidor 4000
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use mkrvidor4000 ID for board option in "platformio.ini" (Project Configuration File):

[env:mkrvidor4000]
platform = atmelsam
board = mkrvidor4000


You can override default MKR Vidor 4000 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkrvidor4000.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mkrvidor4000]
platform = atmelsam
board = mkrvidor4000
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


MKR Vidor 4000 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:mkrvidor4000]
platform = atmelsam
board = mkrvidor4000
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

MKR Vidor 4000 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Minitronics v2.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21J18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor ReprapWorld

Please use minitronics20 ID for board option in "platformio.ini" (Project Configuration File):

[env:minitronics20]
platform = atmelsam
board = minitronics20


You can override default Minitronics v2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest minitronics20.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:minitronics20]
platform = atmelsam
board = minitronics20
; change microcontroller
board_build.mcu = samd21j18a
; change MCU frequency
board_build.f_cpu = 48000000L


Minitronics v2.0 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:minitronics20]
platform = atmelsam
board = minitronics20
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Minitronics v2.0 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Moteino M0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor LowPowerLab

Please use moteino_zero ID for board option in "platformio.ini" (Project Configuration File):

[env:moteino_zero]
platform = atmelsam
board = moteino_zero


You can override default Moteino M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest moteino_zero.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:moteino_zero]
platform = atmelsam
board = moteino_zero
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Moteino M0 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • cmsis-dap
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:moteino_zero]
platform = atmelsam
board = moteino_zero
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Moteino 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.

Compatible Tools On-board Default
Atmel-ICE Yes
Black Magic Probe
CMSIS-DAP
J-LINK

Name Description
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.

•
NANO 33 IoT
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Arduino

Please use nano_33_iot ID for board option in "platformio.ini" (Project Configuration File):

[env:nano_33_iot]
platform = atmelsam
board = nano_33_iot


You can override default NANO 33 IoT settings per build environment using board_*** option, where *** is a JSON object path from board manifest nano_33_iot.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nano_33_iot]
platform = atmelsam
board = nano_33_iot
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


NANO 33 IoT supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:nano_33_iot]
platform = atmelsam
board = nano_33_iot
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NANO 33 IoT 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SODAQ Autonomo
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21J18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SODAQ

Please use sodaq_autonomo ID for board option in "platformio.ini" (Project Configuration File):

[env:sodaq_autonomo]
platform = atmelsam
board = sodaq_autonomo


You can override default SODAQ Autonomo settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_autonomo.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sodaq_autonomo]
platform = atmelsam
board = sodaq_autonomo
; change microcontroller
board_build.mcu = samd21j18a
; change MCU frequency
board_build.f_cpu = 48000000L


SODAQ Autonomo supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sodaq_autonomo]
platform = atmelsam
board = sodaq_autonomo
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SODAQ Autonomo 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SODAQ ExpLoRer
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21J18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SODAQ

Please use sodaq_explorer ID for board option in "platformio.ini" (Project Configuration File):

[env:sodaq_explorer]
platform = atmelsam
board = sodaq_explorer


You can override default SODAQ ExpLoRer settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_explorer.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sodaq_explorer]
platform = atmelsam
board = sodaq_explorer
; change microcontroller
board_build.mcu = samd21j18a
; change MCU frequency
board_build.f_cpu = 48000000L


SODAQ ExpLoRer supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sodaq_explorer]
platform = atmelsam
board = sodaq_explorer
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SODAQ ExpLoRer 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SODAQ ONE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SODAQ

Please use sodaq_one ID for board option in "platformio.ini" (Project Configuration File):

[env:sodaq_one]
platform = atmelsam
board = sodaq_one


You can override default SODAQ ONE settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_one.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sodaq_one]
platform = atmelsam
board = sodaq_one
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


SODAQ ONE supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sodaq_one]
platform = atmelsam
board = sodaq_one
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SODAQ ONE 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SODAQ SARA
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21J18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SODAQ

Please use sodaq_sara ID for board option in "platformio.ini" (Project Configuration File):

[env:sodaq_sara]
platform = atmelsam
board = sodaq_sara


You can override default SODAQ SARA settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_sara.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sodaq_sara]
platform = atmelsam
board = sodaq_sara
; change microcontroller
board_build.mcu = samd21j18a
; change MCU frequency
board_build.f_cpu = 48000000L


SODAQ SARA supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sodaq_sara]
platform = atmelsam
board = sodaq_sara
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SODAQ SARA 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SODAQ SFF
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SODAQ

Please use sodaq_sff ID for board option in "platformio.ini" (Project Configuration File):

[env:sodaq_sff]
platform = atmelsam
board = sodaq_sff


You can override default SODAQ SFF settings per build environment using board_*** option, where *** is a JSON object path from board manifest sodaq_sff.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sodaq_sff]
platform = atmelsam
board = sodaq_sff
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


SODAQ SFF supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sodaq_sff]
platform = atmelsam
board = sodaq_sff
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SODAQ SFF 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SainSmart Due (Programming Port)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller AT91SAM3X8E
Frequency 84MHz
Flash 512KB
RAM 96KB
Vendor SainSmart

Please use sainSmartDue ID for board option in "platformio.ini" (Project Configuration File):

[env:sainSmartDue]
platform = atmelsam
board = sainSmartDue


You can override default SainSmart Due (Programming Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest sainSmartDue.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sainSmartDue]
platform = atmelsam
board = sainSmartDue
; change microcontroller
board_build.mcu = at91sam3x8e
; change MCU frequency
board_build.f_cpu = 84000000L


SainSmart Due (Programming Port) supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba
  • stlink

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sainSmartDue]
platform = atmelsam
board = sainSmartDue
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SainSmart Due (Programming Port) 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
Atmel-ICE Yes
Black Magic Probe
J-LINK
ST-LINK

Name Description
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.

•
SainSmart Due (USB Native Port)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller AT91SAM3X8E
Frequency 84MHz
Flash 512KB
RAM 96KB
Vendor SainSmart

Please use sainSmartDueUSB ID for board option in "platformio.ini" (Project Configuration File):

[env:sainSmartDueUSB]
platform = atmelsam
board = sainSmartDueUSB


You can override default SainSmart Due (USB Native Port) settings per build environment using board_*** option, where *** is a JSON object path from board manifest sainSmartDueUSB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sainSmartDueUSB]
platform = atmelsam
board = sainSmartDueUSB
; change microcontroller
board_build.mcu = at91sam3x8e
; change MCU frequency
board_build.f_cpu = 84000000L


SainSmart Due (USB Native Port) supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba
  • stlink

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sainSmartDueUSB]
platform = atmelsam
board = sainSmartDueUSB
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SainSmart Due (USB Native Port) 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
Atmel-ICE Yes
Black Magic Probe
J-LINK
ST-LINK

Name Description
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.

•
Seeeduino LoRaWAN
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Seeed

Please use seeeduino_lorawan ID for board option in "platformio.ini" (Project Configuration File):

[env:seeeduino_lorawan]
platform = atmelsam
board = seeeduino_lorawan


You can override default Seeeduino LoRaWAN settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeeduino_lorawan.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:seeeduino_lorawan]
platform = atmelsam
board = seeeduino_lorawan
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Seeeduino LoRaWAN supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:seeeduino_lorawan]
platform = atmelsam
board = seeeduino_lorawan
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Seeeduino LoRaWAN 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SparkFun 9DoF Razor IMU M0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SparkFun

Please use sparkfun_samd21_9dof ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_samd21_9dof]
platform = atmelsam
board = sparkfun_samd21_9dof


You can override default SparkFun 9DoF Razor IMU M0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_samd21_9dof.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_samd21_9dof]
platform = atmelsam
board = sparkfun_samd21_9dof
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


SparkFun 9DoF Razor IMU M0 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sparkfun_samd21_9dof]
platform = atmelsam
board = sparkfun_samd21_9dof
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun 9DoF Razor IMU 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.

Compatible Tools On-board Default
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SparkFun Qwiic Micro
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21E18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SparkFun

Please use sparkfun_qwiic_micro_samd21e ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_qwiic_micro_samd21e]
platform = atmelsam
board = sparkfun_qwiic_micro_samd21e


You can override default SparkFun Qwiic Micro settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_qwiic_micro_samd21e.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_qwiic_micro_samd21e]
platform = atmelsam
board = sparkfun_qwiic_micro_samd21e
; change microcontroller
board_build.mcu = samd21e18a
; change MCU frequency
board_build.f_cpu = 48000000L


SparkFun Qwiic Micro supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sparkfun_qwiic_micro_samd21e]
platform = atmelsam
board = sparkfun_qwiic_micro_samd21e
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun Qwiic Micro 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SparkFun RedBoard Turbo
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SparkFun

Please use sparkfun_redboard_turbo ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_redboard_turbo]
platform = atmelsam
board = sparkfun_redboard_turbo


You can override default SparkFun RedBoard Turbo settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_redboard_turbo.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_redboard_turbo]
platform = atmelsam
board = sparkfun_redboard_turbo
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


SparkFun RedBoard Turbo supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sparkfun_redboard_turbo]
platform = atmelsam
board = sparkfun_redboard_turbo
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun RedBoard Turbo 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SparkFun SAMD21 Dev Breakout
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SparkFun

Please use sparkfun_samd21_dev_usb ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_samd21_dev_usb]
platform = atmelsam
board = sparkfun_samd21_dev_usb


You can override default SparkFun SAMD21 Dev Breakout settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_samd21_dev_usb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_samd21_dev_usb]
platform = atmelsam
board = sparkfun_samd21_dev_usb
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


SparkFun SAMD21 Dev Breakout supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sparkfun_samd21_dev_usb]
platform = atmelsam
board = sparkfun_samd21_dev_usb
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun SAMD21 Dev Breakout 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SparkFun SAMD21 Mini Breakout
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SparkFun

Please use sparkfun_samd21_mini_usb ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_samd21_mini_usb]
platform = atmelsam
board = sparkfun_samd21_mini_usb


You can override default SparkFun SAMD21 Mini Breakout settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_samd21_mini_usb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_samd21_mini_usb]
platform = atmelsam
board = sparkfun_samd21_mini_usb
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


SparkFun SAMD21 Mini Breakout supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sparkfun_samd21_mini_usb]
platform = atmelsam
board = sparkfun_samd21_mini_usb
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun SAMD21 Mini Breakout 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
SparkFun SAMD21 Pro RF
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor SparkFun

Please use sparkfun_samd21_proRF ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_samd21_proRF]
platform = atmelsam
board = sparkfun_samd21_proRF


You can override default SparkFun SAMD21 Pro RF settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_samd21_proRF.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_samd21_proRF]
platform = atmelsam
board = sparkfun_samd21_proRF
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


SparkFun SAMD21 Pro RF supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:sparkfun_samd21_proRF]
platform = atmelsam
board = sparkfun_samd21_proRF
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun SAMD21 Pro RF 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

•
Tuino 096
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Atmel SAM: Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Microcontroller SAMD21G18A
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Gimasi

Please use tuinozero96 ID for board option in "platformio.ini" (Project Configuration File):

[env:tuinozero96]
platform = atmelsam
board = tuinozero96


You can override default Tuino 096 settings per build environment using board_*** option, where *** is a JSON object path from board manifest tuinozero96.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:tuinozero96]
platform = atmelsam
board = tuinozero96
; change microcontroller
board_build.mcu = samd21g18a
; change MCU frequency
board_build.f_cpu = 48000000L


Tuino 096 supports the next uploading protocols:

  • atmel-ice
  • blackmagic
  • jlink
  • stk500v2

Default protocol is stk500v2

You can change upload protocol using upload_protocol option:

[env:tuinozero96]
platform = atmelsam
board = tuinozero96
upload_protocol = stk500v2


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Tuino 096 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
Atmel-ICE Yes
Black Magic Probe
J-LINK

Name Description
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.

Espressif 32

•
AI Thinker ESP32-CAM
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor AI Thinker

Please use esp32cam ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32cam]
platform = espressif32
board = esp32cam


You can override default AI Thinker ESP32-CAM settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32cam.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32cam]
platform = espressif32
board = esp32cam
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


AI Thinker ESP32-CAM supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32cam]
platform = espressif32
board = esp32cam
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

AI Thinker ESP32-CAM 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
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
ALKS ESP32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor RoboticsBrno

Please use alksesp32 ID for board option in "platformio.ini" (Project Configuration File):

[env:alksesp32]
platform = espressif32
board = alksesp32


You can override default ALKS ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest alksesp32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:alksesp32]
platform = espressif32
board = alksesp32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


ALKS ESP32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:alksesp32]
platform = espressif32
board = alksesp32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ALKS ESP32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.

AZ-Delivery ESP-32 Dev Kit C V4

•
AZ-Delivery ESP-32 Dev Kit C V4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 16MB
RAM 520KB
Vendor AZ-Delivery

Please use az-delivery-devkit-v4 ID for board option in "platformio.ini" (Project Configuration File):

[env:az-delivery-devkit-v4]
platform = espressif32
board = az-delivery-devkit-v4


You can override default AZ-Delivery ESP-32 Dev Kit C V4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest az-delivery-devkit-v4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:az-delivery-devkit-v4]
platform = espressif32
board = az-delivery-devkit-v4
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


AZ-Delivery ESP-32 Dev Kit C V4 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:az-delivery-devkit-v4]
platform = espressif32
board = az-delivery-devkit-v4
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

AZ-Delivery ESP-32 Dev Kit C V4 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
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Adafruit ESP32 Feather
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Adafruit

Please use featheresp32 ID for board option in "platformio.ini" (Project Configuration File):

[env:featheresp32]
platform = espressif32
board = featheresp32


You can override default Adafruit ESP32 Feather settings per build environment using board_*** option, where *** is a JSON object path from board manifest featheresp32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:featheresp32]
platform = espressif32
board = featheresp32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Adafruit ESP32 Feather supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:featheresp32]
platform = espressif32
board = featheresp32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit ESP32 Feather 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
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
April Brother ESPea32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor April Brother

Please use espea32 ID for board option in "platformio.ini" (Project Configuration File):

[env:espea32]
platform = espressif32
board = espea32


You can override default April Brother ESPea32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest espea32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:espea32]
platform = espressif32
board = espea32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


April Brother ESPea32 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:espea32]
platform = espressif32
board = espea32
upload_protocol = esptool


PIO Unified Debugger currently does not support April Brother ESPea32 board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
BPI-Bit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 160MHz
Flash 4MB
RAM 320KB
Vendor BPI Tech

Please use bpi-bit ID for board option in "platformio.ini" (Project Configuration File):

[env:bpi-bit]
platform = espressif32
board = bpi-bit


You can override default BPI-Bit settings per build environment using board_*** option, where *** is a JSON object path from board manifest bpi-bit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:bpi-bit]
platform = espressif32
board = bpi-bit
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 160000000L


BPI-Bit supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:bpi-bit]
platform = espressif32
board = bpi-bit
upload_protocol = esptool


PIO Unified Debugger currently does not support BPI-Bit board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

Briki ABC (MBC-WB) - ESP32

•
Briki ABC (MBC-WB) - ESP32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 3.25MB
RAM 320KB
Vendor meteca

Please use briki_abc_esp32 ID for board option in "platformio.ini" (Project Configuration File):

[env:briki_abc_esp32]
platform = espressif32
board = briki_abc_esp32


You can override default Briki ABC (MBC-WB) - ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest briki_abc_esp32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:briki_abc_esp32]
platform = espressif32
board = briki_abc_esp32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Briki ABC (MBC-WB) - ESP32 supports the next uploading protocols:

  • esp-prog
  • iot-bus-jtag
  • jlink
  • mbctool
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is mbctool

You can change upload protocol using upload_protocol option:

[env:briki_abc_esp32]
platform = espressif32
board = briki_abc_esp32
upload_protocol = mbctool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Briki ABC (MBC-WB) - ESP32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.

Briki MBC-WB - ESP32

•
Briki MBC-WB - ESP32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 3.25MB
RAM 320KB
Vendor meteca

Please use briki_mbc-wb_esp32 ID for board option in "platformio.ini" (Project Configuration File):

[env:briki_mbc-wb_esp32]
platform = espressif32
board = briki_mbc-wb_esp32


You can override default Briki MBC-WB - ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest briki_mbc-wb_esp32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:briki_mbc-wb_esp32]
platform = espressif32
board = briki_mbc-wb_esp32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Briki MBC-WB - ESP32 supports the next uploading protocols:

  • esp-prog
  • iot-bus-jtag
  • jlink
  • mbctool
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is mbctool

You can change upload protocol using upload_protocol option:

[env:briki_mbc-wb_esp32]
platform = espressif32
board = briki_mbc-wb_esp32
upload_protocol = mbctool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Briki MBC-WB - ESP32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.

•
D-duino-32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor DSTIKE

Please use d-duino-32 ID for board option in "platformio.ini" (Project Configuration File):

[env:d-duino-32]
platform = espressif32
board = d-duino-32


You can override default D-duino-32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest d-duino-32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:d-duino-32]
platform = espressif32
board = d-duino-32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


D-duino-32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:d-duino-32]
platform = espressif32
board = d-duino-32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

D-duino-32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
DOIT ESP32 DEVKIT V1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor DOIT

Please use esp32doit-devkit-v1 ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32doit-devkit-v1]
platform = espressif32
board = esp32doit-devkit-v1


You can override default DOIT ESP32 DEVKIT V1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32doit-devkit-v1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32doit-devkit-v1]
platform = espressif32
board = esp32doit-devkit-v1
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


DOIT ESP32 DEVKIT V1 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32doit-devkit-v1]
platform = espressif32
board = esp32doit-devkit-v1
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

DOIT ESP32 DEVKIT V1 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Dongsen Tech Pocket 32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Dongsen Technology

Please use pocket_32 ID for board option in "platformio.ini" (Project Configuration File):

[env:pocket_32]
platform = espressif32
board = pocket_32


You can override default Dongsen Tech Pocket 32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest pocket_32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:pocket_32]
platform = espressif32
board = pocket_32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Dongsen Tech Pocket 32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:pocket_32]
platform = espressif32
board = pocket_32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Dongsen Tech Pocket 32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
ESP32 FM DevKit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Unknown

Please use fm-devkit ID for board option in "platformio.ini" (Project Configuration File):

[env:fm-devkit]
platform = espressif32
board = fm-devkit


You can override default ESP32 FM DevKit settings per build environment using board_*** option, where *** is a JSON object path from board manifest fm-devkit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:fm-devkit]
platform = espressif32
board = fm-devkit
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


ESP32 FM DevKit supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:fm-devkit]
platform = espressif32
board = fm-devkit
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ESP32 FM DevKit does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
ESP32 Pico Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Espressif

Please use pico32 ID for board option in "platformio.ini" (Project Configuration File):

[env:pico32]
platform = espressif32
board = pico32


You can override default ESP32 Pico Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest pico32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:pico32]
platform = espressif32
board = pico32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


ESP32 Pico Kit supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:pico32]
platform = espressif32
board = pico32
upload_protocol = esptool


PIO Unified Debugger currently does not support ESP32 Pico Kit board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
ESP32vn IoT Uno
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor ESP32vn

Please use esp32vn-iot-uno ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32vn-iot-uno]
platform = espressif32
board = esp32vn-iot-uno


You can override default ESP32vn IoT Uno settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32vn-iot-uno.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32vn-iot-uno]
platform = espressif32
board = esp32vn-iot-uno
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


ESP32vn IoT Uno supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32vn-iot-uno]
platform = espressif32
board = esp32vn-iot-uno
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ESP32vn IoT Uno does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
ESPectro32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor DycodeX

Please use espectro32 ID for board option in "platformio.ini" (Project Configuration File):

[env:espectro32]
platform = espressif32
board = espectro32


You can override default ESPectro32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest espectro32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:espectro32]
platform = espressif32
board = espectro32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


ESPectro32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:espectro32]
platform = espressif32
board = espectro32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ESPectro32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
ESPino32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor ThaiEasyElec

Please use espino32 ID for board option in "platformio.ini" (Project Configuration File):

[env:espino32]
platform = espressif32
board = espino32


You can override default ESPino32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest espino32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:espino32]
platform = espressif32
board = espino32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


ESPino32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:espino32]
platform = espressif32
board = espino32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ESPino32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Electronic SweetPeas ESP320
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Electronic SweetPeas

Please use esp320 ID for board option in "platformio.ini" (Project Configuration File):

[env:esp320]
platform = espressif32
board = esp320


You can override default Electronic SweetPeas ESP320 settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp320.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp320]
platform = espressif32
board = esp320
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Electronic SweetPeas ESP320 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp320]
platform = espressif32
board = esp320
upload_protocol = esptool


PIO Unified Debugger currently does not support Electronic SweetPeas ESP320 board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Espressif ESP-WROVER-KIT
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Espressif

Please use esp-wrover-kit ID for board option in "platformio.ini" (Project Configuration File):

[env:esp-wrover-kit]
platform = espressif32
board = esp-wrover-kit


You can override default Espressif ESP-WROVER-KIT settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp-wrover-kit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp-wrover-kit]
platform = espressif32
board = esp-wrover-kit
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Espressif ESP-WROVER-KIT supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • ftdi
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp-wrover-kit]
platform = espressif32
board = esp-wrover-kit
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Espressif ESP-WROVER-KIT has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.

Compatible Tools On-board Default
ESP-Prog
FTDI Chip Yes Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Espressif ESP32 Dev Module
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Espressif

Please use esp32dev ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32dev]
platform = espressif32
board = esp32dev


You can override default Espressif ESP32 Dev Module settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32dev.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32dev]
platform = espressif32
board = esp32dev
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Espressif ESP32 Dev Module supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32dev]
platform = espressif32
board = esp32dev
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Espressif ESP32 Dev Module does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
FireBeetle-ESP32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor DFRobot

Please use firebeetle32 ID for board option in "platformio.ini" (Project Configuration File):

[env:firebeetle32]
platform = espressif32
board = firebeetle32


You can override default FireBeetle-ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest firebeetle32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:firebeetle32]
platform = espressif32
board = firebeetle32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


FireBeetle-ESP32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:firebeetle32]
platform = espressif32
board = firebeetle32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

FireBeetle-ESP32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Frog Board ESP32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Fred

Please use frogboard ID for board option in "platformio.ini" (Project Configuration File):

[env:frogboard]
platform = espressif32
board = frogboard


You can override default Frog Board ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest frogboard.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frogboard]
platform = espressif32
board = frogboard
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Frog Board ESP32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:frogboard]
platform = espressif32
board = frogboard
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Frog Board ESP32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Heltec WiFi Kit 32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Heltec Automation

Please use heltec_wifi_kit_32 ID for board option in "platformio.ini" (Project Configuration File):

[env:heltec_wifi_kit_32]
platform = espressif32
board = heltec_wifi_kit_32


You can override default Heltec WiFi Kit 32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest heltec_wifi_kit_32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:heltec_wifi_kit_32]
platform = espressif32
board = heltec_wifi_kit_32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Heltec WiFi Kit 32 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:heltec_wifi_kit_32]
platform = espressif32
board = heltec_wifi_kit_32
upload_protocol = esptool


PIO Unified Debugger currently does not support Heltec WiFi Kit 32 board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Heltec WiFi LoRa 32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Heltec Automation

Please use heltec_wifi_lora_32 ID for board option in "platformio.ini" (Project Configuration File):

[env:heltec_wifi_lora_32]
platform = espressif32
board = heltec_wifi_lora_32


You can override default Heltec WiFi LoRa 32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest heltec_wifi_lora_32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:heltec_wifi_lora_32]
platform = espressif32
board = heltec_wifi_lora_32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Heltec WiFi LoRa 32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:heltec_wifi_lora_32]
platform = espressif32
board = heltec_wifi_lora_32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Heltec WiFi LoRa 32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Heltec WiFi LoRa 32 (V2)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 8MB
RAM 320KB
Vendor Heltec Automation

Please use heltec_wifi_lora_32_V2 ID for board option in "platformio.ini" (Project Configuration File):

[env:heltec_wifi_lora_32_V2]
platform = espressif32
board = heltec_wifi_lora_32_V2


You can override default Heltec WiFi LoRa 32 (V2) settings per build environment using board_*** option, where *** is a JSON object path from board manifest heltec_wifi_lora_32_V2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:heltec_wifi_lora_32_V2]
platform = espressif32
board = heltec_wifi_lora_32_V2
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Heltec WiFi LoRa 32 (V2) supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:heltec_wifi_lora_32_V2]
platform = espressif32
board = heltec_wifi_lora_32_V2
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Heltec WiFi LoRa 32 (V2) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Heltec Wireless Stick
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 8MB
RAM 320KB
Vendor Heltec Automation

Please use heltec_wireless_stick ID for board option in "platformio.ini" (Project Configuration File):

[env:heltec_wireless_stick]
platform = espressif32
board = heltec_wireless_stick


You can override default Heltec Wireless Stick settings per build environment using board_*** option, where *** is a JSON object path from board manifest heltec_wireless_stick.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:heltec_wireless_stick]
platform = espressif32
board = heltec_wireless_stick
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Heltec Wireless Stick supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:heltec_wireless_stick]
platform = espressif32
board = heltec_wireless_stick
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Heltec Wireless Stick does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Hornbill ESP32 Dev
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Hornbill

Please use hornbill32dev ID for board option in "platformio.ini" (Project Configuration File):

[env:hornbill32dev]
platform = espressif32
board = hornbill32dev


You can override default Hornbill ESP32 Dev settings per build environment using board_*** option, where *** is a JSON object path from board manifest hornbill32dev.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:hornbill32dev]
platform = espressif32
board = hornbill32dev
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Hornbill ESP32 Dev supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:hornbill32dev]
platform = espressif32
board = hornbill32dev
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Hornbill ESP32 Dev does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Hornbill ESP32 Minima
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Hornbill

Please use hornbill32minima ID for board option in "platformio.ini" (Project Configuration File):

[env:hornbill32minima]
platform = espressif32
board = hornbill32minima


You can override default Hornbill ESP32 Minima settings per build environment using board_*** option, where *** is a JSON object path from board manifest hornbill32minima.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:hornbill32minima]
platform = espressif32
board = hornbill32minima
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Hornbill ESP32 Minima supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:hornbill32minima]
platform = espressif32
board = hornbill32minima
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Hornbill ESP32 Minima 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
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
IntoRobot Fig
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor IntoRobot

Please use intorobot ID for board option in "platformio.ini" (Project Configuration File):

[env:intorobot]
platform = espressif32
board = intorobot


You can override default IntoRobot Fig settings per build environment using board_*** option, where *** is a JSON object path from board manifest intorobot.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:intorobot]
platform = espressif32
board = intorobot
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


IntoRobot Fig supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:intorobot]
platform = espressif32
board = intorobot
upload_protocol = esptool


PIO Unified Debugger currently does not support IntoRobot Fig board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
IoTaaP Magnolia
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor IoTaaP

Please use iotaap_magnolia ID for board option in "platformio.ini" (Project Configuration File):

[env:iotaap_magnolia]
platform = espressif32
board = iotaap_magnolia


You can override default IoTaaP Magnolia settings per build environment using board_*** option, where *** is a JSON object path from board manifest iotaap_magnolia.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:iotaap_magnolia]
platform = espressif32
board = iotaap_magnolia
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


IoTaaP Magnolia supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:iotaap_magnolia]
platform = espressif32
board = iotaap_magnolia
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

IoTaaP Magnolia does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.

•
M5Stack Core ESP32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor M5Stack

Please use m5stack-core-esp32 ID for board option in "platformio.ini" (Project Configuration File):

[env:m5stack-core-esp32]
platform = espressif32
board = m5stack-core-esp32


You can override default M5Stack Core ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest m5stack-core-esp32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:m5stack-core-esp32]
platform = espressif32
board = m5stack-core-esp32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


M5Stack Core ESP32 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:m5stack-core-esp32]
platform = espressif32
board = m5stack-core-esp32
upload_protocol = esptool


PIO Unified Debugger currently does not support M5Stack Core ESP32 board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
M5Stack FIRE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 16MB
RAM 6.25MB
Vendor M5Stack

Please use m5stack-fire ID for board option in "platformio.ini" (Project Configuration File):

[env:m5stack-fire]
platform = espressif32
board = m5stack-fire


You can override default M5Stack FIRE settings per build environment using board_*** option, where *** is a JSON object path from board manifest m5stack-fire.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:m5stack-fire]
platform = espressif32
board = m5stack-fire
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


M5Stack FIRE supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:m5stack-fire]
platform = espressif32
board = m5stack-fire
upload_protocol = esptool


PIO Unified Debugger currently does not support M5Stack FIRE board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
M5Stack GREY ESP32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 16MB
RAM 520KB
Vendor M5Stack

Please use m5stack-grey ID for board option in "platformio.ini" (Project Configuration File):

[env:m5stack-grey]
platform = espressif32
board = m5stack-grey


You can override default M5Stack GREY ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest m5stack-grey.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:m5stack-grey]
platform = espressif32
board = m5stack-grey
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


M5Stack GREY ESP32 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:m5stack-grey]
platform = espressif32
board = m5stack-grey
upload_protocol = esptool


PIO Unified Debugger currently does not support M5Stack GREY ESP32 board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
M5Stick-C
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor M5Stack

Please use m5stick-c ID for board option in "platformio.ini" (Project Configuration File):

[env:m5stick-c]
platform = espressif32
board = m5stick-c


You can override default M5Stick-C settings per build environment using board_*** option, where *** is a JSON object path from board manifest m5stick-c.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:m5stick-c]
platform = espressif32
board = m5stick-c
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


M5Stick-C supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:m5stick-c]
platform = espressif32
board = m5stick-c
upload_protocol = esptool


PIO Unified Debugger currently does not support M5Stick-C board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
MH ET LIVE ESP32DevKIT
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor MH-ET Live

Please use mhetesp32devkit ID for board option in "platformio.ini" (Project Configuration File):

[env:mhetesp32devkit]
platform = espressif32
board = mhetesp32devkit


You can override default MH ET LIVE ESP32DevKIT settings per build environment using board_*** option, where *** is a JSON object path from board manifest mhetesp32devkit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mhetesp32devkit]
platform = espressif32
board = mhetesp32devkit
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


MH ET LIVE ESP32DevKIT supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:mhetesp32devkit]
platform = espressif32
board = mhetesp32devkit
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

MH ET LIVE ESP32DevKIT does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
MH ET LIVE ESP32MiniKit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor MH-ET Live

Please use mhetesp32minikit ID for board option in "platformio.ini" (Project Configuration File):

[env:mhetesp32minikit]
platform = espressif32
board = mhetesp32minikit


You can override default MH ET LIVE ESP32MiniKit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mhetesp32minikit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mhetesp32minikit]
platform = espressif32
board = mhetesp32minikit
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


MH ET LIVE ESP32MiniKit supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:mhetesp32minikit]
platform = espressif32
board = mhetesp32minikit
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

MH ET LIVE ESP32MiniKit does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
MagicBit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Magicblocks.io

Please use magicbit ID for board option in "platformio.ini" (Project Configuration File):

[env:magicbit]
platform = espressif32
board = magicbit


You can override default MagicBit settings per build environment using board_*** option, where *** is a JSON object path from board manifest magicbit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:magicbit]
platform = espressif32
board = magicbit
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


MagicBit supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:magicbit]
platform = espressif32
board = magicbit
upload_protocol = esptool


PIO Unified Debugger currently does not support MagicBit board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
MakerAsia Nano32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor MakerAsia

Please use nano32 ID for board option in "platformio.ini" (Project Configuration File):

[env:nano32]
platform = espressif32
board = nano32


You can override default MakerAsia Nano32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nano32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nano32]
platform = espressif32
board = nano32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


MakerAsia Nano32 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:nano32]
platform = espressif32
board = nano32
upload_protocol = esptool


PIO Unified Debugger currently does not support MakerAsia Nano32 board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Pumbaa Pumbaa is Python on top of Simba. The implementation is a port of MicroPython, designed for embedded devices with limited amount of RAM and code memory.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
Microduino Core ESP32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Microduino

Please use microduino-core-esp32 ID for board option in "platformio.ini" (Project Configuration File):

[env:microduino-core-esp32]
platform = espressif32
board = microduino-core-esp32


You can override default Microduino Core ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest microduino-core-esp32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:microduino-core-esp32]
platform = espressif32
board = microduino-core-esp32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Microduino Core ESP32 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:microduino-core-esp32]
platform = espressif32
board = microduino-core-esp32
upload_protocol = esptool


PIO Unified Debugger currently does not support Microduino Core ESP32 board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Node32s
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Aiyarafun

Please use node32s ID for board option in "platformio.ini" (Project Configuration File):

[env:node32s]
platform = espressif32
board = node32s


You can override default Node32s settings per build environment using board_*** option, where *** is a JSON object path from board manifest node32s.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:node32s]
platform = espressif32
board = node32s
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Node32s supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:node32s]
platform = espressif32
board = node32s
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Node32s does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

NodeMCU-32S

•
NodeMCU-32S
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor NodeMCU

Please use nodemcu-32s ID for board option in "platformio.ini" (Project Configuration File):

[env:nodemcu-32s]
platform = espressif32
board = nodemcu-32s


You can override default NodeMCU-32S settings per build environment using board_*** option, where *** is a JSON object path from board manifest nodemcu-32s.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nodemcu-32s]
platform = espressif32
board = nodemcu-32s
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


NodeMCU-32S supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:nodemcu-32s]
platform = espressif32
board = nodemcu-32s
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NodeMCU-32S does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Noduino Quantum
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 16MB
RAM 320KB
Vendor Noduino

Please use quantum ID for board option in "platformio.ini" (Project Configuration File):

[env:quantum]
platform = espressif32
board = quantum


You can override default Noduino Quantum settings per build environment using board_*** option, where *** is a JSON object path from board manifest quantum.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:quantum]
platform = espressif32
board = quantum
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Noduino Quantum supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:quantum]
platform = espressif32
board = quantum
upload_protocol = esptool


PIO Unified Debugger currently does not support Noduino Quantum board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
ODROID-GO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 16MB
RAM 320KB
Vendor Hardkernel

Please use odroid_esp32 ID for board option in "platformio.ini" (Project Configuration File):

[env:odroid_esp32]
platform = espressif32
board = odroid_esp32


You can override default ODROID-GO settings per build environment using board_*** option, where *** is a JSON object path from board manifest odroid_esp32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:odroid_esp32]
platform = espressif32
board = odroid_esp32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


ODROID-GO supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:odroid_esp32]
platform = espressif32
board = odroid_esp32
upload_protocol = esptool


PIO Unified Debugger currently does not support ODROID-GO board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

OLIMEX ESP32-DevKit-LiPo

•
OLIMEX ESP32-DevKit-LiPo
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor OLIMEX

Please use esp32-devkitlipo ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32-devkitlipo]
platform = espressif32
board = esp32-devkitlipo


You can override default OLIMEX ESP32-DevKit-LiPo settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-devkitlipo.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32-devkitlipo]
platform = espressif32
board = esp32-devkitlipo
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


OLIMEX ESP32-DevKit-LiPo supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32-devkitlipo]
platform = espressif32
board = esp32-devkitlipo
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

OLIMEX ESP32-DevKit-LiPo does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

OLIMEX ESP32-EVB

•
OLIMEX ESP32-EVB
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor OLIMEX

Please use esp32-evb ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32-evb]
platform = espressif32
board = esp32-evb


You can override default OLIMEX ESP32-EVB settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-evb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32-evb]
platform = espressif32
board = esp32-evb
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


OLIMEX ESP32-EVB supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32-evb]
platform = espressif32
board = esp32-evb
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

OLIMEX ESP32-EVB does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

OLIMEX ESP32-GATEWAY

•
OLIMEX ESP32-GATEWAY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor OLIMEX

Please use esp32-gateway ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32-gateway]
platform = espressif32
board = esp32-gateway


You can override default OLIMEX ESP32-GATEWAY settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-gateway.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32-gateway]
platform = espressif32
board = esp32-gateway
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


OLIMEX ESP32-GATEWAY supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32-gateway]
platform = espressif32
board = esp32-gateway
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

OLIMEX ESP32-GATEWAY does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

OLIMEX ESP32-PRO

•
OLIMEX ESP32-PRO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor OLIMEX

Please use esp32-pro ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32-pro]
platform = espressif32
board = esp32-pro


You can override default OLIMEX ESP32-PRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-pro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32-pro]
platform = espressif32
board = esp32-pro
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


OLIMEX ESP32-PRO supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32-pro]
platform = espressif32
board = esp32-pro
upload_protocol = esptool


PIO Unified Debugger currently does not support OLIMEX ESP32-PRO board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

OLIMEX ESP32-PoE

•
OLIMEX ESP32-PoE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor OLIMEX

Please use esp32-poe ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32-poe]
platform = espressif32
board = esp32-poe


You can override default OLIMEX ESP32-PoE settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-poe.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32-poe]
platform = espressif32
board = esp32-poe
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


OLIMEX ESP32-PoE supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32-poe]
platform = espressif32
board = esp32-poe
upload_protocol = esptool


PIO Unified Debugger currently does not support OLIMEX ESP32-PoE board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

OLIMEX ESP32-PoE-ISO

•
OLIMEX ESP32-PoE-ISO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor OLIMEX

Please use esp32-poe-iso ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32-poe-iso]
platform = espressif32
board = esp32-poe-iso


You can override default OLIMEX ESP32-PoE-ISO settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32-poe-iso.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32-poe-iso]
platform = espressif32
board = esp32-poe-iso
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


OLIMEX ESP32-PoE-ISO supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32-poe-iso]
platform = espressif32
board = esp32-poe-iso
upload_protocol = esptool


PIO Unified Debugger currently does not support OLIMEX ESP32-PoE-ISO board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
OROCA EduBot
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor OROCA

Please use oroca_edubot ID for board option in "platformio.ini" (Project Configuration File):

[env:oroca_edubot]
platform = espressif32
board = oroca_edubot


You can override default OROCA EduBot settings per build environment using board_*** option, where *** is a JSON object path from board manifest oroca_edubot.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:oroca_edubot]
platform = espressif32
board = oroca_edubot
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


OROCA EduBot supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:oroca_edubot]
platform = espressif32
board = oroca_edubot
upload_protocol = esptool


PIO Unified Debugger currently does not support OROCA EduBot board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Onehorse ESP32 Dev Module
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Onehorse

Please use onehorse32dev ID for board option in "platformio.ini" (Project Configuration File):

[env:onehorse32dev]
platform = espressif32
board = onehorse32dev


You can override default Onehorse ESP32 Dev Module settings per build environment using board_*** option, where *** is a JSON object path from board manifest onehorse32dev.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:onehorse32dev]
platform = espressif32
board = onehorse32dev
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Onehorse ESP32 Dev Module supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:onehorse32dev]
platform = espressif32
board = onehorse32dev
upload_protocol = esptool


PIO Unified Debugger currently does not support Onehorse ESP32 Dev Module board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Pycom GPy
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Pycom Ltd.

Please use pycom_gpy ID for board option in "platformio.ini" (Project Configuration File):

[env:pycom_gpy]
platform = espressif32
board = pycom_gpy


You can override default Pycom GPy settings per build environment using board_*** option, where *** is a JSON object path from board manifest pycom_gpy.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:pycom_gpy]
platform = espressif32
board = pycom_gpy
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Pycom GPy supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:pycom_gpy]
platform = espressif32
board = pycom_gpy
upload_protocol = esptool


PIO Unified Debugger currently does not support Pycom GPy board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Pycom LoPy
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Pycom Ltd.

Please use lopy ID for board option in "platformio.ini" (Project Configuration File):

[env:lopy]
platform = espressif32
board = lopy


You can override default Pycom LoPy settings per build environment using board_*** option, where *** is a JSON object path from board manifest lopy.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lopy]
platform = espressif32
board = lopy
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Pycom LoPy supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:lopy]
platform = espressif32
board = lopy
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Pycom LoPy does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Pycom LoPy4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 1.25MB
Vendor Pycom Ltd.

Please use lopy4 ID for board option in "platformio.ini" (Project Configuration File):

[env:lopy4]
platform = espressif32
board = lopy4


You can override default Pycom LoPy4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lopy4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lopy4]
platform = espressif32
board = lopy4
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Pycom LoPy4 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:lopy4]
platform = espressif32
board = lopy4
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Pycom LoPy4 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Qchip
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Qmobot LLP

Please use qchip ID for board option in "platformio.ini" (Project Configuration File):

[env:qchip]
platform = espressif32
board = qchip


You can override default Qchip settings per build environment using board_*** option, where *** is a JSON object path from board manifest qchip.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:qchip]
platform = espressif32
board = qchip
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Qchip supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:qchip]
platform = espressif32
board = qchip
upload_protocol = esptool


PIO Unified Debugger currently does not support Qchip board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

SG-O AirMon

•
SG-O AirMon
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor SG-O

Please use sg-o_airMon ID for board option in "platformio.ini" (Project Configuration File):

[env:sg-o_airMon]
platform = espressif32
board = sg-o_airMon


You can override default SG-O AirMon settings per build environment using board_*** option, where *** is a JSON object path from board manifest sg-o_airMon.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sg-o_airMon]
platform = espressif32
board = sg-o_airMon
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


SG-O AirMon supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:sg-o_airMon]
platform = espressif32
board = sg-o_airMon
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SG-O AirMon does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Silicognition wESP32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Silicognition

Please use wesp32 ID for board option in "platformio.ini" (Project Configuration File):

[env:wesp32]
platform = espressif32
board = wesp32


You can override default Silicognition wESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest wesp32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wesp32]
platform = espressif32
board = wesp32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Silicognition wESP32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:wesp32]
platform = espressif32
board = wesp32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Silicognition wESP32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
SparkFun ESP32 Thing
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor SparkFun Electronics

Please use esp32thing ID for board option in "platformio.ini" (Project Configuration File):

[env:esp32thing]
platform = espressif32
board = esp32thing


You can override default SparkFun ESP32 Thing settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp32thing.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp32thing]
platform = espressif32
board = esp32thing
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


SparkFun ESP32 Thing supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp32thing]
platform = espressif32
board = esp32thing
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun ESP32 Thing does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
SparkFun LoRa Gateway 1-Channel
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor SparkFun

Please use sparkfun_lora_gateway_1-channel ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfun_lora_gateway_1-channel]
platform = espressif32
board = sparkfun_lora_gateway_1-channel


You can override default SparkFun LoRa Gateway 1-Channel settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfun_lora_gateway_1-channel.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfun_lora_gateway_1-channel]
platform = espressif32
board = sparkfun_lora_gateway_1-channel
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


SparkFun LoRa Gateway 1-Channel supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:sparkfun_lora_gateway_1-channel]
platform = espressif32
board = sparkfun_lora_gateway_1-channel
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun LoRa Gateway 1-Channel does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

TTGO LoRa32-OLED V1

•
TTGO LoRa32-OLED V1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor TTGO

Please use ttgo-lora32-v1 ID for board option in "platformio.ini" (Project Configuration File):

[env:ttgo-lora32-v1]
platform = espressif32
board = ttgo-lora32-v1


You can override default TTGO LoRa32-OLED V1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ttgo-lora32-v1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ttgo-lora32-v1]
platform = espressif32
board = ttgo-lora32-v1
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


TTGO LoRa32-OLED V1 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:ttgo-lora32-v1]
platform = espressif32
board = ttgo-lora32-v1
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TTGO LoRa32-OLED V1 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

TTGO LoRa32-OLED V2

•
TTGO LoRa32-OLED V2
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor TTGO

Please use ttgo-lora32-v2 ID for board option in "platformio.ini" (Project Configuration File):

[env:ttgo-lora32-v2]
platform = espressif32
board = ttgo-lora32-v2


You can override default TTGO LoRa32-OLED V2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ttgo-lora32-v2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ttgo-lora32-v2]
platform = espressif32
board = ttgo-lora32-v2
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


TTGO LoRa32-OLED V2 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:ttgo-lora32-v2]
platform = espressif32
board = ttgo-lora32-v2
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TTGO LoRa32-OLED V2 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

TTGO T-Beam

•
TTGO T-Beam
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 1.25MB
Vendor TTGO

Please use ttgo-t-beam ID for board option in "platformio.ini" (Project Configuration File):

[env:ttgo-t-beam]
platform = espressif32
board = ttgo-t-beam


You can override default TTGO T-Beam settings per build environment using board_*** option, where *** is a JSON object path from board manifest ttgo-t-beam.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ttgo-t-beam]
platform = espressif32
board = ttgo-t-beam
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


TTGO T-Beam supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:ttgo-t-beam]
platform = espressif32
board = ttgo-t-beam
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TTGO T-Beam does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

TTGO T-Watch

•
TTGO T-Watch
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 16MB
RAM 320KB
Vendor TTGO

Please use ttgo-t-watch ID for board option in "platformio.ini" (Project Configuration File):

[env:ttgo-t-watch]
platform = espressif32
board = ttgo-t-watch


You can override default TTGO T-Watch settings per build environment using board_*** option, where *** is a JSON object path from board manifest ttgo-t-watch.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ttgo-t-watch]
platform = espressif32
board = ttgo-t-watch
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


TTGO T-Watch supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:ttgo-t-watch]
platform = espressif32
board = ttgo-t-watch
upload_protocol = esptool


PIO Unified Debugger currently does not support TTGO T-Watch board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
TTGO T1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor TTGO

Please use ttgo-t1 ID for board option in "platformio.ini" (Project Configuration File):

[env:ttgo-t1]
platform = espressif32
board = ttgo-t1


You can override default TTGO T1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ttgo-t1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ttgo-t1]
platform = espressif32
board = ttgo-t1
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


TTGO T1 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:ttgo-t1]
platform = espressif32
board = ttgo-t1
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TTGO T1 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
TinyPICO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor TinyPICO

Please use tinypico ID for board option in "platformio.ini" (Project Configuration File):

[env:tinypico]
platform = espressif32
board = tinypico


You can override default TinyPICO settings per build environment using board_*** option, where *** is a JSON object path from board manifest tinypico.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:tinypico]
platform = espressif32
board = tinypico
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


TinyPICO supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:tinypico]
platform = espressif32
board = tinypico
upload_protocol = esptool


PIO Unified Debugger currently does not support TinyPICO board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Turta IoT Node
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor Turta

Please use turta_iot_node ID for board option in "platformio.ini" (Project Configuration File):

[env:turta_iot_node]
platform = espressif32
board = turta_iot_node


You can override default Turta IoT Node settings per build environment using board_*** option, where *** is a JSON object path from board manifest turta_iot_node.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:turta_iot_node]
platform = espressif32
board = turta_iot_node
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Turta IoT Node supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:turta_iot_node]
platform = espressif32
board = turta_iot_node
upload_protocol = esptool


PIO Unified Debugger currently does not support Turta IoT Node board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
VintLabs ESP32 Devkit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor VintLabs

Please use vintlabs-devkit-v1 ID for board option in "platformio.ini" (Project Configuration File):

[env:vintlabs-devkit-v1]
platform = espressif32
board = vintlabs-devkit-v1


You can override default VintLabs ESP32 Devkit settings per build environment using board_*** option, where *** is a JSON object path from board manifest vintlabs-devkit-v1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:vintlabs-devkit-v1]
platform = espressif32
board = vintlabs-devkit-v1
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


VintLabs ESP32 Devkit supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:vintlabs-devkit-v1]
platform = espressif32
board = vintlabs-devkit-v1
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

VintLabs ESP32 Devkit does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
WEMOS LOLIN D32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor WEMOS

Please use lolin_d32 ID for board option in "platformio.ini" (Project Configuration File):

[env:lolin_d32]
platform = espressif32
board = lolin_d32


You can override default WEMOS LOLIN D32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lolin_d32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lolin_d32]
platform = espressif32
board = lolin_d32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


WEMOS LOLIN D32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:lolin_d32]
platform = espressif32
board = lolin_d32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WEMOS LOLIN D32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
WEMOS LOLIN D32 PRO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor WEMOS

Please use lolin_d32_pro ID for board option in "platformio.ini" (Project Configuration File):

[env:lolin_d32_pro]
platform = espressif32
board = lolin_d32_pro


You can override default WEMOS LOLIN D32 PRO settings per build environment using board_*** option, where *** is a JSON object path from board manifest lolin_d32_pro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lolin_d32_pro]
platform = espressif32
board = lolin_d32_pro
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


WEMOS LOLIN D32 PRO supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:lolin_d32_pro]
platform = espressif32
board = lolin_d32_pro
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WEMOS LOLIN D32 PRO does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
WEMOS LOLIN32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor WEMOS

Please use lolin32 ID for board option in "platformio.ini" (Project Configuration File):

[env:lolin32]
platform = espressif32
board = lolin32


You can override default WEMOS LOLIN32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lolin32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lolin32]
platform = espressif32
board = lolin32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


WEMOS LOLIN32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:lolin32]
platform = espressif32
board = lolin32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WEMOS LOLIN32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
WeMos D1 MINI ESP32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor WEMOS

Please use wemos_d1_mini32 ID for board option in "platformio.ini" (Project Configuration File):

[env:wemos_d1_mini32]
platform = espressif32
board = wemos_d1_mini32


You can override default WeMos D1 MINI ESP32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest wemos_d1_mini32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wemos_d1_mini32]
platform = espressif32
board = wemos_d1_mini32
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


WeMos D1 MINI ESP32 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:wemos_d1_mini32]
platform = espressif32
board = wemos_d1_mini32
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WeMos D1 MINI ESP32 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
WeMos WiFi and Bluetooth Battery
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor WEMOS

Please use wemosbat ID for board option in "platformio.ini" (Project Configuration File):

[env:wemosbat]
platform = espressif32
board = wemosbat


You can override default WeMos WiFi and Bluetooth Battery settings per build environment using board_*** option, where *** is a JSON object path from board manifest wemosbat.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wemosbat]
platform = espressif32
board = wemosbat
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


WeMos WiFi and Bluetooth Battery supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:wemosbat]
platform = espressif32
board = wemosbat
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WeMos WiFi and Bluetooth Battery does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
Widora AIR
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 16MB
RAM 320KB
Vendor Widora

Please use widora-air ID for board option in "platformio.ini" (Project Configuration File):

[env:widora-air]
platform = espressif32
board = widora-air


You can override default Widora AIR settings per build environment using board_*** option, where *** is a JSON object path from board manifest widora-air.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:widora-air]
platform = espressif32
board = widora-air
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


Widora AIR supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:widora-air]
platform = espressif32
board = widora-air
upload_protocol = esptool


PIO Unified Debugger currently does not support Widora AIR board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

•
XinaBox CW02
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor XinaBox

Please use xinabox_cw02 ID for board option in "platformio.ini" (Project Configuration File):

[env:xinabox_cw02]
platform = espressif32
board = xinabox_cw02


You can override default XinaBox CW02 settings per build environment using board_*** option, where *** is a JSON object path from board manifest xinabox_cw02.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xinabox_cw02]
platform = espressif32
board = xinabox_cw02
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


XinaBox CW02 supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:xinabox_cw02]
platform = espressif32
board = xinabox_cw02
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

XinaBox CW02 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog Yes
oddWires IOT-Bus JTAG
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

oddWires IoT-Bus Io

•
oddWires IoT-Bus Io
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor oddWires

Please use iotbusio ID for board option in "platformio.ini" (Project Configuration File):

[env:iotbusio]
platform = espressif32
board = iotbusio


You can override default oddWires IoT-Bus Io settings per build environment using board_*** option, where *** is a JSON object path from board manifest iotbusio.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:iotbusio]
platform = espressif32
board = iotbusio
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


oddWires IoT-Bus Io supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:iotbusio]
platform = espressif32
board = iotbusio
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

oddWires IoT-Bus Io does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog
oddWires IOT-Bus JTAG Yes
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

oddWires IoT-Bus Proteus

•
oddWires IoT-Bus Proteus
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 4MB
RAM 320KB
Vendor oddWires

Please use iotbusproteus ID for board option in "platformio.ini" (Project Configuration File):

[env:iotbusproteus]
platform = espressif32
board = iotbusproteus


You can override default oddWires IoT-Bus Proteus settings per build environment using board_*** option, where *** is a JSON object path from board manifest iotbusproteus.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:iotbusproteus]
platform = espressif32
board = iotbusproteus
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


oddWires IoT-Bus Proteus supports the next uploading protocols:

  • esp-prog
  • espota
  • esptool
  • iot-bus-jtag
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:iotbusproteus]
platform = espressif32
board = iotbusproteus
upload_protocol = esptool


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

oddWires IoT-Bus Proteus does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
ESP-Prog
oddWires IOT-Bus JTAG Yes
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

u-blox NINA-W10 series

•
u-blox NINA-W10 series
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 32: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP32
Frequency 240MHz
Flash 2MB
RAM 320KB
Vendor u-blox

Please use nina_w10 ID for board option in "platformio.ini" (Project Configuration File):

[env:nina_w10]
platform = espressif32
board = nina_w10


You can override default u-blox NINA-W10 series settings per build environment using board_*** option, where *** is a JSON object path from board manifest nina_w10.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nina_w10]
platform = espressif32
board = nina_w10
; change microcontroller
board_build.mcu = esp32
; change MCU frequency
board_build.f_cpu = 240000000L


u-blox NINA-W10 series supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:nina_w10]
platform = espressif32
board = nina_w10
upload_protocol = esptool


PIO Unified Debugger currently does not support u-blox NINA-W10 series board.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.

Espressif 8266

•
4D Systems gen4 IoD Range
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 512KB
RAM 80KB
Vendor 4D Systems

Please use gen4iod ID for board option in "platformio.ini" (Project Configuration File):

[env:gen4iod]
platform = espressif8266
board = gen4iod


You can override default 4D Systems gen4 IoD Range settings per build environment using board_*** option, where *** is a JSON object path from board manifest gen4iod.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:gen4iod]
platform = espressif8266
board = gen4iod
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


4D Systems gen4 IoD Range supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:gen4iod]
platform = espressif8266
board = gen4iod
upload_protocol = esptool


PIO Unified Debugger currently does not support 4D Systems gen4 IoD Range board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Adafruit HUZZAH ESP8266
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor Adafruit

Please use huzzah ID for board option in "platformio.ini" (Project Configuration File):

[env:huzzah]
platform = espressif8266
board = huzzah


You can override default Adafruit HUZZAH ESP8266 settings per build environment using board_*** option, where *** is a JSON object path from board manifest huzzah.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:huzzah]
platform = espressif8266
board = huzzah
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Adafruit HUZZAH ESP8266 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:huzzah]
platform = espressif8266
board = huzzah
upload_protocol = esptool


PIO Unified Debugger currently does not support Adafruit HUZZAH ESP8266 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
DigiStump Oak
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor DigiStump

Please use oak ID for board option in "platformio.ini" (Project Configuration File):

[env:oak]
platform = espressif8266
board = oak


You can override default DigiStump Oak settings per build environment using board_*** option, where *** is a JSON object path from board manifest oak.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:oak]
platform = espressif8266
board = oak
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


DigiStump Oak supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:oak]
platform = espressif8266
board = oak
upload_protocol = esptool


PIO Unified Debugger currently does not support DigiStump Oak board.

Name Description
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.

ESP-Mx DevKit (ESP8285)

•
ESP-Mx DevKit (ESP8285)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 1MB
RAM 80KB
Vendor Doit

Please use espmxdevkit ID for board option in "platformio.ini" (Project Configuration File):

[env:espmxdevkit]
platform = espressif8266
board = espmxdevkit


You can override default ESP-Mx DevKit (ESP8285) settings per build environment using board_*** option, where *** is a JSON object path from board manifest espmxdevkit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:espmxdevkit]
platform = espressif8266
board = espmxdevkit
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


ESP-Mx DevKit (ESP8285) supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:espmxdevkit]
platform = espressif8266
board = espmxdevkit
upload_protocol = esptool


PIO Unified Debugger currently does not support ESP-Mx DevKit (ESP8285) board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
ESP-WROOM-02
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 2MB
RAM 80KB
Vendor Espressif

Please use esp_wroom_02 ID for board option in "platformio.ini" (Project Configuration File):

[env:esp_wroom_02]
platform = espressif8266
board = esp_wroom_02


You can override default ESP-WROOM-02 settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp_wroom_02.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp_wroom_02]
platform = espressif8266
board = esp_wroom_02
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


ESP-WROOM-02 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp_wroom_02]
platform = espressif8266
board = esp_wroom_02
upload_protocol = esptool


PIO Unified Debugger currently does not support ESP-WROOM-02 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
ESPDuino (ESP-13 Module)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor Doit

Please use espduino ID for board option in "platformio.ini" (Project Configuration File):

[env:espduino]
platform = espressif8266
board = espduino


You can override default ESPDuino (ESP-13 Module) settings per build environment using board_*** option, where *** is a JSON object path from board manifest espduino.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:espduino]
platform = espressif8266
board = espduino
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


ESPDuino (ESP-13 Module) supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:espduino]
platform = espressif8266
board = espduino
upload_protocol = esptool


PIO Unified Debugger currently does not support ESPDuino (ESP-13 Module) board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
ESPectro Core
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor DycodeX

Please use espectro ID for board option in "platformio.ini" (Project Configuration File):

[env:espectro]
platform = espressif8266
board = espectro


You can override default ESPectro Core settings per build environment using board_*** option, where *** is a JSON object path from board manifest espectro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:espectro]
platform = espressif8266
board = espectro
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


ESPectro Core supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:espectro]
platform = espressif8266
board = espectro
upload_protocol = esptool


PIO Unified Debugger currently does not support ESPectro Core board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
ESPino
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor ESPino

Please use espino ID for board option in "platformio.ini" (Project Configuration File):

[env:espino]
platform = espressif8266
board = espino


You can override default ESPino settings per build environment using board_*** option, where *** is a JSON object path from board manifest espino.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:espino]
platform = espressif8266
board = espino
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


ESPino supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:espino]
platform = espressif8266
board = espino
upload_protocol = esptool


PIO Unified Debugger currently does not support ESPino board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
ESPresso Lite 1.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor ESPert

Please use espresso_lite_v1 ID for board option in "platformio.ini" (Project Configuration File):

[env:espresso_lite_v1]
platform = espressif8266
board = espresso_lite_v1


You can override default ESPresso Lite 1.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest espresso_lite_v1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:espresso_lite_v1]
platform = espressif8266
board = espresso_lite_v1
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


ESPresso Lite 1.0 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:espresso_lite_v1]
platform = espressif8266
board = espresso_lite_v1
upload_protocol = esptool


PIO Unified Debugger currently does not support ESPresso Lite 1.0 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
ESPresso Lite 2.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor ESPert

Please use espresso_lite_v2 ID for board option in "platformio.ini" (Project Configuration File):

[env:espresso_lite_v2]
platform = espressif8266
board = espresso_lite_v2


You can override default ESPresso Lite 2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest espresso_lite_v2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:espresso_lite_v2]
platform = espressif8266
board = espresso_lite_v2
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


ESPresso Lite 2.0 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:espresso_lite_v2]
platform = espressif8266
board = espresso_lite_v2
upload_protocol = esptool


PIO Unified Debugger currently does not support ESPresso Lite 2.0 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Espressif ESP8266 ESP-12E
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor Espressif

Please use esp12e ID for board option in "platformio.ini" (Project Configuration File):

[env:esp12e]
platform = espressif8266
board = esp12e


You can override default Espressif ESP8266 ESP-12E settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp12e.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp12e]
platform = espressif8266
board = esp12e
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Espressif ESP8266 ESP-12E supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp12e]
platform = espressif8266
board = esp12e
upload_protocol = esptool


PIO Unified Debugger currently does not support Espressif ESP8266 ESP-12E board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

Espressif Generic ESP8266 ESP-01 1M

•
Espressif Generic ESP8266 ESP-01 1M
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 1MB
RAM 80KB
Vendor Espressif

Please use esp01_1m ID for board option in "platformio.ini" (Project Configuration File):

[env:esp01_1m]
platform = espressif8266
board = esp01_1m


You can override default Espressif Generic ESP8266 ESP-01 1M settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp01_1m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp01_1m]
platform = espressif8266
board = esp01_1m
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Espressif Generic ESP8266 ESP-01 1M supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp01_1m]
platform = espressif8266
board = esp01_1m
upload_protocol = esptool


PIO Unified Debugger currently does not support Espressif Generic ESP8266 ESP-01 1M board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

Espressif Generic ESP8266 ESP-01 512k

•
Espressif Generic ESP8266 ESP-01 512k
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 512KB
RAM 80KB
Vendor Espressif

Please use esp01 ID for board option in "platformio.ini" (Project Configuration File):

[env:esp01]
platform = espressif8266
board = esp01


You can override default Espressif Generic ESP8266 ESP-01 512k settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp01.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp01]
platform = espressif8266
board = esp01
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Espressif Generic ESP8266 ESP-01 512k supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp01]
platform = espressif8266
board = esp01
upload_protocol = esptool


PIO Unified Debugger currently does not support Espressif Generic ESP8266 ESP-01 512k board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

Espressif Generic ESP8266 ESP-07

•
Espressif Generic ESP8266 ESP-07
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor Espressif

Please use esp07 ID for board option in "platformio.ini" (Project Configuration File):

[env:esp07]
platform = espressif8266
board = esp07


You can override default Espressif Generic ESP8266 ESP-07 settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp07.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp07]
platform = espressif8266
board = esp07
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Espressif Generic ESP8266 ESP-07 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp07]
platform = espressif8266
board = esp07
upload_protocol = esptool


PIO Unified Debugger currently does not support Espressif Generic ESP8266 ESP-07 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Generic ESP8285 Module
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 1MB
RAM 80KB
Vendor Espressif

Please use esp8285 ID for board option in "platformio.ini" (Project Configuration File):

[env:esp8285]
platform = espressif8266
board = esp8285


You can override default Generic ESP8285 Module settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp8285.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp8285]
platform = espressif8266
board = esp8285
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Generic ESP8285 Module supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp8285]
platform = espressif8266
board = esp8285
upload_protocol = esptool


PIO Unified Debugger currently does not support Generic ESP8285 Module board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Heltec Wifi kit 8
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor Heltec

Please use heltec_wifi_kit_8 ID for board option in "platformio.ini" (Project Configuration File):

[env:heltec_wifi_kit_8]
platform = espressif8266
board = heltec_wifi_kit_8


You can override default Heltec Wifi kit 8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest heltec_wifi_kit_8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:heltec_wifi_kit_8]
platform = espressif8266
board = heltec_wifi_kit_8
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Heltec Wifi kit 8 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:heltec_wifi_kit_8]
platform = espressif8266
board = heltec_wifi_kit_8
upload_protocol = esptool


PIO Unified Debugger currently does not support Heltec Wifi kit 8 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

Invent One

•
Invent One
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor Invent One

Please use inventone ID for board option in "platformio.ini" (Project Configuration File):

[env:inventone]
platform = espressif8266
board = inventone


You can override default Invent One settings per build environment using board_*** option, where *** is a JSON object path from board manifest inventone.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:inventone]
platform = espressif8266
board = inventone
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Invent One supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:inventone]
platform = espressif8266
board = inventone
upload_protocol = esptool


PIO Unified Debugger currently does not support Invent One board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
NodeMCU 0.9 (ESP-12 Module)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor NodeMCU

Please use nodemcu ID for board option in "platformio.ini" (Project Configuration File):

[env:nodemcu]
platform = espressif8266
board = nodemcu


You can override default NodeMCU 0.9 (ESP-12 Module) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nodemcu.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nodemcu]
platform = espressif8266
board = nodemcu
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


NodeMCU 0.9 (ESP-12 Module) supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:nodemcu]
platform = espressif8266
board = nodemcu
upload_protocol = esptool


PIO Unified Debugger currently does not support NodeMCU 0.9 (ESP-12 Module) board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
NodeMCU 1.0 (ESP-12E Module)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor NodeMCU

Please use nodemcuv2 ID for board option in "platformio.ini" (Project Configuration File):

[env:nodemcuv2]
platform = espressif8266
board = nodemcuv2


You can override default NodeMCU 1.0 (ESP-12E Module) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nodemcuv2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nodemcuv2]
platform = espressif8266
board = nodemcuv2
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


NodeMCU 1.0 (ESP-12E Module) supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:nodemcuv2]
platform = espressif8266
board = nodemcuv2
upload_protocol = esptool


PIO Unified Debugger currently does not support NodeMCU 1.0 (ESP-12E Module) board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

•
Olimex MOD-WIFI-ESP8266(-DEV)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 2MB
RAM 80KB
Vendor Olimex

Please use modwifi ID for board option in "platformio.ini" (Project Configuration File):

[env:modwifi]
platform = espressif8266
board = modwifi


You can override default Olimex MOD-WIFI-ESP8266(-DEV) settings per build environment using board_*** option, where *** is a JSON object path from board manifest modwifi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:modwifi]
platform = espressif8266
board = modwifi
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Olimex MOD-WIFI-ESP8266(-DEV) supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:modwifi]
platform = espressif8266
board = modwifi
upload_protocol = esptool


PIO Unified Debugger currently does not support Olimex MOD-WIFI-ESP8266(-DEV) board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Phoenix 1.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor Espressif

Please use phoenix_v1 ID for board option in "platformio.ini" (Project Configuration File):

[env:phoenix_v1]
platform = espressif8266
board = phoenix_v1


You can override default Phoenix 1.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest phoenix_v1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:phoenix_v1]
platform = espressif8266
board = phoenix_v1
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Phoenix 1.0 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:phoenix_v1]
platform = espressif8266
board = phoenix_v1
upload_protocol = esptool


PIO Unified Debugger currently does not support Phoenix 1.0 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Phoenix 2.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor Espressif

Please use phoenix_v2 ID for board option in "platformio.ini" (Project Configuration File):

[env:phoenix_v2]
platform = espressif8266
board = phoenix_v2


You can override default Phoenix 2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest phoenix_v2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:phoenix_v2]
platform = espressif8266
board = phoenix_v2
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Phoenix 2.0 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:phoenix_v2]
platform = espressif8266
board = phoenix_v2
upload_protocol = esptool


PIO Unified Debugger currently does not support Phoenix 2.0 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Schirmilabs Eduino WiFi
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor Schirmilabs

Please use eduinowifi ID for board option in "platformio.ini" (Project Configuration File):

[env:eduinowifi]
platform = espressif8266
board = eduinowifi


You can override default Schirmilabs Eduino WiFi settings per build environment using board_*** option, where *** is a JSON object path from board manifest eduinowifi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:eduinowifi]
platform = espressif8266
board = eduinowifi
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Schirmilabs Eduino WiFi supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:eduinowifi]
platform = espressif8266
board = eduinowifi
upload_protocol = esptool


PIO Unified Debugger currently does not support Schirmilabs Eduino WiFi board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Sonoff Basic
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 1MB
RAM 80KB
Vendor ITEAD

Please use sonoff_basic ID for board option in "platformio.ini" (Project Configuration File):

[env:sonoff_basic]
platform = espressif8266
board = sonoff_basic


You can override default Sonoff Basic settings per build environment using board_*** option, where *** is a JSON object path from board manifest sonoff_basic.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sonoff_basic]
platform = espressif8266
board = sonoff_basic
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Sonoff Basic supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:sonoff_basic]
platform = espressif8266
board = sonoff_basic
upload_protocol = esptool


PIO Unified Debugger currently does not support Sonoff Basic board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Sonoff S20
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 1MB
RAM 80KB
Vendor ITEAD

Please use sonoff_s20 ID for board option in "platformio.ini" (Project Configuration File):

[env:sonoff_s20]
platform = espressif8266
board = sonoff_s20


You can override default Sonoff S20 settings per build environment using board_*** option, where *** is a JSON object path from board manifest sonoff_s20.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sonoff_s20]
platform = espressif8266
board = sonoff_s20
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Sonoff S20 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:sonoff_s20]
platform = espressif8266
board = sonoff_s20
upload_protocol = esptool


PIO Unified Debugger currently does not support Sonoff S20 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Sonoff SV
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 1MB
RAM 80KB
Vendor ITEAD

Please use sonoff_sv ID for board option in "platformio.ini" (Project Configuration File):

[env:sonoff_sv]
platform = espressif8266
board = sonoff_sv


You can override default Sonoff SV settings per build environment using board_*** option, where *** is a JSON object path from board manifest sonoff_sv.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sonoff_sv]
platform = espressif8266
board = sonoff_sv
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Sonoff SV supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:sonoff_sv]
platform = espressif8266
board = sonoff_sv
upload_protocol = esptool


PIO Unified Debugger currently does not support Sonoff SV board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Sonoff TH
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 1MB
RAM 80KB
Vendor ITEAD

Please use sonoff_th ID for board option in "platformio.ini" (Project Configuration File):

[env:sonoff_th]
platform = espressif8266
board = sonoff_th


You can override default Sonoff TH settings per build environment using board_*** option, where *** is a JSON object path from board manifest sonoff_th.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sonoff_th]
platform = espressif8266
board = sonoff_th
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Sonoff TH supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:sonoff_th]
platform = espressif8266
board = sonoff_th
upload_protocol = esptool


PIO Unified Debugger currently does not support Sonoff TH board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
SparkFun Blynk Board
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor SparkFun

Please use sparkfunBlynk ID for board option in "platformio.ini" (Project Configuration File):

[env:sparkfunBlynk]
platform = espressif8266
board = sparkfunBlynk


You can override default SparkFun Blynk Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparkfunBlynk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparkfunBlynk]
platform = espressif8266
board = sparkfunBlynk
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


SparkFun Blynk Board supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:sparkfunBlynk]
platform = espressif8266
board = sparkfunBlynk
upload_protocol = esptool


PIO Unified Debugger currently does not support SparkFun Blynk Board board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
SparkFun ESP8266 Thing
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 512KB
RAM 80KB
Vendor SparkFun

Please use thing ID for board option in "platformio.ini" (Project Configuration File):

[env:thing]
platform = espressif8266
board = thing


You can override default SparkFun ESP8266 Thing settings per build environment using board_*** option, where *** is a JSON object path from board manifest thing.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:thing]
platform = espressif8266
board = thing
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


SparkFun ESP8266 Thing supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:thing]
platform = espressif8266
board = thing
upload_protocol = esptool


PIO Unified Debugger currently does not support SparkFun ESP8266 Thing board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
SparkFun ESP8266 Thing Dev
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 512KB
RAM 80KB
Vendor SparkFun

Please use thingdev ID for board option in "platformio.ini" (Project Configuration File):

[env:thingdev]
platform = espressif8266
board = thingdev


You can override default SparkFun ESP8266 Thing Dev settings per build environment using board_*** option, where *** is a JSON object path from board manifest thingdev.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:thingdev]
platform = espressif8266
board = thingdev
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


SparkFun ESP8266 Thing Dev supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:thingdev]
platform = espressif8266
board = thingdev
upload_protocol = esptool


PIO Unified Debugger currently does not support SparkFun ESP8266 Thing Dev board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
SweetPea ESP-210
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor SweetPea

Please use esp210 ID for board option in "platformio.ini" (Project Configuration File):

[env:esp210]
platform = espressif8266
board = esp210


You can override default SweetPea ESP-210 settings per build environment using board_*** option, where *** is a JSON object path from board manifest esp210.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:esp210]
platform = espressif8266
board = esp210
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


SweetPea ESP-210 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:esp210]
platform = espressif8266
board = esp210
upload_protocol = esptool


PIO Unified Debugger currently does not support SweetPea ESP-210 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
ThaiEasyElec ESPino
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor ThaiEasyElec

Please use espinotee ID for board option in "platformio.ini" (Project Configuration File):

[env:espinotee]
platform = espressif8266
board = espinotee


You can override default ThaiEasyElec ESPino settings per build environment using board_*** option, where *** is a JSON object path from board manifest espinotee.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:espinotee]
platform = espressif8266
board = espinotee
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


ThaiEasyElec ESPino supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:espinotee]
platform = espressif8266
board = espinotee
upload_protocol = esptool


PIO Unified Debugger currently does not support ThaiEasyElec ESPino board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
WEMOS D1 R1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor WEMOS

Please use d1 ID for board option in "platformio.ini" (Project Configuration File):

[env:d1]
platform = espressif8266
board = d1


You can override default WEMOS D1 R1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest d1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:d1]
platform = espressif8266
board = d1
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


WEMOS D1 R1 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:d1]
platform = espressif8266
board = d1
upload_protocol = esptool


PIO Unified Debugger currently does not support WEMOS D1 R1 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
WeMos D1 R2 and mini
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor WEMOS

Please use d1_mini ID for board option in "platformio.ini" (Project Configuration File):

[env:d1_mini]
platform = espressif8266
board = d1_mini


You can override default WeMos D1 R2 and mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest d1_mini.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:d1_mini]
platform = espressif8266
board = d1_mini
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


WeMos D1 R2 and mini supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:d1_mini]
platform = espressif8266
board = d1_mini
upload_protocol = esptool


PIO Unified Debugger currently does not support WeMos D1 R2 and mini board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
WeMos D1 mini Lite
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 1MB
RAM 80KB
Vendor WEMOS

Please use d1_mini_lite ID for board option in "platformio.ini" (Project Configuration File):

[env:d1_mini_lite]
platform = espressif8266
board = d1_mini_lite


You can override default WeMos D1 mini Lite settings per build environment using board_*** option, where *** is a JSON object path from board manifest d1_mini_lite.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:d1_mini_lite]
platform = espressif8266
board = d1_mini_lite
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


WeMos D1 mini Lite supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:d1_mini_lite]
platform = espressif8266
board = d1_mini_lite
upload_protocol = esptool


PIO Unified Debugger currently does not support WeMos D1 mini Lite board.

Name Description
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.

•
WeMos D1 mini Pro
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 16MB
RAM 80KB
Vendor WEMOS

Please use d1_mini_pro ID for board option in "platformio.ini" (Project Configuration File):

[env:d1_mini_pro]
platform = espressif8266
board = d1_mini_pro


You can override default WeMos D1 mini Pro settings per build environment using board_*** option, where *** is a JSON object path from board manifest d1_mini_pro.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:d1_mini_pro]
platform = espressif8266
board = d1_mini_pro
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


WeMos D1 mini Pro supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:d1_mini_pro]
platform = espressif8266
board = d1_mini_pro
upload_protocol = esptool


PIO Unified Debugger currently does not support WeMos D1 mini Pro board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
WiFi Slot
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor Amperka

Please use wifi_slot ID for board option in "platformio.ini" (Project Configuration File):

[env:wifi_slot]
platform = espressif8266
board = wifi_slot


You can override default WiFi Slot settings per build environment using board_*** option, where *** is a JSON object path from board manifest wifi_slot.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wifi_slot]
platform = espressif8266
board = wifi_slot
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


WiFi Slot supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:wifi_slot]
platform = espressif8266
board = wifi_slot
upload_protocol = esptool


PIO Unified Debugger currently does not support WiFi Slot board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
WiFiduino
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor WifiDuino

Please use wifiduino ID for board option in "platformio.ini" (Project Configuration File):

[env:wifiduino]
platform = espressif8266
board = wifiduino


You can override default WiFiduino settings per build environment using board_*** option, where *** is a JSON object path from board manifest wifiduino.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wifiduino]
platform = espressif8266
board = wifiduino
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


WiFiduino supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:wifiduino]
platform = espressif8266
board = wifiduino
upload_protocol = esptool


PIO Unified Debugger currently does not support WiFiduino board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
WifInfo
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 1MB
RAM 80KB
Vendor Espressif

Please use wifinfo ID for board option in "platformio.ini" (Project Configuration File):

[env:wifinfo]
platform = espressif8266
board = wifinfo


You can override default WifInfo settings per build environment using board_*** option, where *** is a JSON object path from board manifest wifinfo.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wifinfo]
platform = espressif8266
board = wifinfo
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


WifInfo supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:wifinfo]
platform = espressif8266
board = wifinfo
upload_protocol = esptool


PIO Unified Debugger currently does not support WifInfo board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Wio Link
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor SeeedStudio

Please use wio_link ID for board option in "platformio.ini" (Project Configuration File):

[env:wio_link]
platform = espressif8266
board = wio_link


You can override default Wio Link settings per build environment using board_*** option, where *** is a JSON object path from board manifest wio_link.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wio_link]
platform = espressif8266
board = wio_link
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Wio Link supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:wio_link]
platform = espressif8266
board = wio_link
upload_protocol = esptool


PIO Unified Debugger currently does not support Wio Link board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
Wio Node
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor SeeedStudio

Please use wio_node ID for board option in "platformio.ini" (Project Configuration File):

[env:wio_node]
platform = espressif8266
board = wio_node


You can override default Wio Node settings per build environment using board_*** option, where *** is a JSON object path from board manifest wio_node.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wio_node]
platform = espressif8266
board = wio_node
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


Wio Node supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:wio_node]
platform = espressif8266
board = wio_node
upload_protocol = esptool


PIO Unified Debugger currently does not support Wio Node board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

•
XinaBox CW01
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Espressif 8266: Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Microcontroller ESP8266
Frequency 80MHz
Flash 4MB
RAM 80KB
Vendor XinaBox

Please use xinabox_cw01 ID for board option in "platformio.ini" (Project Configuration File):

[env:xinabox_cw01]
platform = espressif8266
board = xinabox_cw01


You can override default XinaBox CW01 settings per build environment using board_*** option, where *** is a JSON object path from board manifest xinabox_cw01.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xinabox_cw01]
platform = espressif8266
board = xinabox_cw01
; change microcontroller
board_build.mcu = esp8266
; change MCU frequency
board_build.f_cpu = 80000000L


XinaBox CW01 supports the next uploading protocols:

  • espota
  • esptool

Default protocol is esptool

You can change upload protocol using upload_protocol option:

[env:xinabox_cw01]
platform = espressif8266
board = xinabox_cw01
upload_protocol = esptool


PIO Unified Debugger currently does not support XinaBox CW01 board.

Name Description
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.
ESP8266 Non-OS SDK The non-OS SDK provides a set of application programming interfaces (APIs) for core ESP8266 functionalities such as data reception/transmission over Wi-Fi, TCP/IP stack functions, hardware interface functions and basic system management functions.
ESP8266 RTOS SDK ESP8266 SDK based on FreeRTOS, a truly free professional grade RTOS for microcontrollers

Freescale Kinetis

•
Ethernet IoT Starter Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MK64FN1M0VLL12
Frequency 120MHz
Flash 1MB
RAM 256KB
Vendor Freescale

Please use IBMEthernetKit ID for board option in "platformio.ini" (Project Configuration File):

[env:IBMEthernetKit]
platform = freescalekinetis
board = IBMEthernetKit


You can override default Ethernet IoT Starter Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest IBMEthernetKit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:IBMEthernetKit]
platform = freescalekinetis
board = IBMEthernetKit
; change microcontroller
board_build.mcu = mk64fn1m0vll12
; change MCU frequency
board_build.f_cpu = 120000000L


Ethernet IoT Starter Kit supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:IBMEthernetKit]
platform = freescalekinetis
board = IBMEthernetKit
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Ethernet IoT Starter Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.

Compatible Tools On-board Default
CMSIS-DAP Yes Yes
J-LINK

Name Description
Mbed The mbed framework The mbed SDK has been designed to provide enough hardware abstraction to be intuitive and concise, yet powerful enough to build complex projects. It is built on the low-level ARM CMSIS APIs, allowing you to code down to the metal if needed. In addition to RTOS, USB and Networking libraries, a cookbook of hundreds of reusable peripheral and module libraries have been built on top of the SDK by the mbed Developer Community.

Freescale Kinetis FRDM-K20D50M

•
Freescale Kinetis FRDM-K20D50M
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MK20DX128VLH5
Frequency 48MHz
Flash 128KB
RAM 16KB
Vendor Freescale

Please use frdm_k20d50m ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_k20d50m]
platform = freescalekinetis
board = frdm_k20d50m


You can override default Freescale Kinetis FRDM-K20D50M settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_k20d50m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_k20d50m]
platform = freescalekinetis
board = frdm_k20d50m
; change microcontroller
board_build.mcu = mk20dx128vlh5
; change MCU frequency
board_build.f_cpu = 48000000L


Freescale Kinetis FRDM-K20D50M supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_k20d50m]
platform = freescalekinetis
board = frdm_k20d50m
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-K20D50M 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
Mbed The mbed framework The mbed SDK has been designed to provide enough hardware abstraction to be intuitive and concise, yet powerful enough to build complex projects. It is built on the low-level ARM CMSIS APIs, allowing you to code down to the metal if needed. In addition to RTOS, USB and Networking libraries, a cookbook of hundreds of reusable peripheral and module libraries have been built on top of the SDK by the mbed Developer Community.

Freescale Kinetis FRDM-K22F

•
Freescale Kinetis FRDM-K22F
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MK22FN512VLH12
Frequency 120MHz
Flash 512KB
RAM 128KB
Vendor Freescale

Please use frdm_k22f ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_k22f]
platform = freescalekinetis
board = frdm_k22f


You can override default Freescale Kinetis FRDM-K22F settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_k22f.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_k22f]
platform = freescalekinetis
board = frdm_k22f
; change microcontroller
board_build.mcu = mk22fn512vlh12
; change MCU frequency
board_build.f_cpu = 120000000L


Freescale Kinetis FRDM-K22F supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_k22f]
platform = freescalekinetis
board = frdm_k22f
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-K22F 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
Zephyr The Zephyr Project is a scalable real-time operating system (RTOS) supporting multiple hardware architectures, optimized for resource constrained devices, and built with safety and security in mind.

Freescale Kinetis FRDM-K64F

•
Freescale Kinetis FRDM-K64F
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MK64FN1M0VLL12
Frequency 120MHz
Flash 1MB
RAM 256KB
Vendor Freescale

Please use frdm_k64f ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_k64f]
platform = freescalekinetis
board = frdm_k64f


You can override default Freescale Kinetis FRDM-K64F settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_k64f.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_k64f]
platform = freescalekinetis
board = frdm_k64f
; change microcontroller
board_build.mcu = mk64fn1m0vll12
; change MCU frequency
board_build.f_cpu = 120000000L


Freescale Kinetis FRDM-K64F supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_k64f]
platform = freescalekinetis
board = frdm_k64f
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-K64F 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
Zephyr The Zephyr Project is a scalable real-time operating system (RTOS) supporting multiple hardware architectures, optimized for resource constrained devices, and built with safety and security in mind.

Freescale Kinetis FRDM-K66F

•
Freescale Kinetis FRDM-K66F
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MK66FN2M0VMD18
Frequency 180MHz
Flash 2MB
RAM 256KB
Vendor Freescale

Please use frdm_k66f ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_k66f]
platform = freescalekinetis
board = frdm_k66f


You can override default Freescale Kinetis FRDM-K66F settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_k66f.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_k66f]
platform = freescalekinetis
board = frdm_k66f
; change microcontroller
board_build.mcu = mk66fn2m0vmd18
; change MCU frequency
board_build.f_cpu = 180000000L


Freescale Kinetis FRDM-K66F supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_k66f]
platform = freescalekinetis
board = frdm_k66f
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-K66F 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
Mbed The mbed framework The mbed SDK has been designed to provide enough hardware abstraction to be intuitive and concise, yet powerful enough to build complex projects. It is built on the low-level ARM CMSIS APIs, allowing you to code down to the metal if needed. In addition to RTOS, USB and Networking libraries, a cookbook of hundreds of reusable peripheral and module libraries have been built on top of the SDK by the mbed Developer Community.

Freescale Kinetis FRDM-K82F

•
Freescale Kinetis FRDM-K82F
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MK82FN256VLL15
Frequency 150MHz
Flash 256KB
RAM 256KB
Vendor Freescale

Please use frdm_k82f ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_k82f]
platform = freescalekinetis
board = frdm_k82f


You can override default Freescale Kinetis FRDM-K82F settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_k82f.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_k82f]
platform = freescalekinetis
board = frdm_k82f
; change microcontroller
board_build.mcu = mk82fn256vll15
; change MCU frequency
board_build.f_cpu = 150000000L


Freescale Kinetis FRDM-K82F supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_k82f]
platform = freescalekinetis
board = frdm_k82f
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-K82F 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
Zephyr The Zephyr Project is a scalable real-time operating system (RTOS) supporting multiple hardware architectures, optimized for resource constrained devices, and built with safety and security in mind.

Freescale Kinetis FRDM-KL05Z

•
Freescale Kinetis FRDM-KL05Z
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MKL05Z32VFM4
Frequency 48MHz
Flash 32KB
RAM 4KB
Vendor Freescale

Please use frdm_kl05z ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_kl05z]
platform = freescalekinetis
board = frdm_kl05z


You can override default Freescale Kinetis FRDM-KL05Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl05z.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_kl05z]
platform = freescalekinetis
board = frdm_kl05z
; change microcontroller
board_build.mcu = mkl05z32vfm4
; change MCU frequency
board_build.f_cpu = 48000000L


Freescale Kinetis FRDM-KL05Z supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_kl05z]
platform = freescalekinetis
board = frdm_kl05z
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-KL05Z 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
Mbed The mbed framework The mbed SDK has been designed to provide enough hardware abstraction to be intuitive and concise, yet powerful enough to build complex projects. It is built on the low-level ARM CMSIS APIs, allowing you to code down to the metal if needed. In addition to RTOS, USB and Networking libraries, a cookbook of hundreds of reusable peripheral and module libraries have been built on top of the SDK by the mbed Developer Community.

Freescale Kinetis FRDM-KL25Z

•
Freescale Kinetis FRDM-KL25Z
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MKL25Z128VLK4
Frequency 48MHz
Flash 128KB
RAM 16KB
Vendor Freescale

Please use frdm_kl25z ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_kl25z]
platform = freescalekinetis
board = frdm_kl25z


You can override default Freescale Kinetis FRDM-KL25Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl25z.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_kl25z]
platform = freescalekinetis
board = frdm_kl25z
; change microcontroller
board_build.mcu = mkl25z128vlk4
; change MCU frequency
board_build.f_cpu = 48000000L


Freescale Kinetis FRDM-KL25Z supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_kl25z]
platform = freescalekinetis
board = frdm_kl25z
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-KL25Z has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.

Compatible Tools On-board Default
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
Zephyr The Zephyr Project is a scalable real-time operating system (RTOS) supporting multiple hardware architectures, optimized for resource constrained devices, and built with safety and security in mind.

Freescale Kinetis FRDM-KL27Z

•
Freescale Kinetis FRDM-KL27Z
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MKL27Z64VLH4
Frequency 48MHz
Flash 64KB
RAM 16KB
Vendor Freescale

Please use frdm_kl27z ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_kl27z]
platform = freescalekinetis
board = frdm_kl27z


You can override default Freescale Kinetis FRDM-KL27Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl27z.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_kl27z]
platform = freescalekinetis
board = frdm_kl27z
; change microcontroller
board_build.mcu = mkl27z64vlh4
; change MCU frequency
board_build.f_cpu = 48000000L


Freescale Kinetis FRDM-KL27Z supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_kl27z]
platform = freescalekinetis
board = frdm_kl27z
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-KL27Z 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
Mbed The mbed framework The mbed SDK has been designed to provide enough hardware abstraction to be intuitive and concise, yet powerful enough to build complex projects. It is built on the low-level ARM CMSIS APIs, allowing you to code down to the metal if needed. In addition to RTOS, USB and Networking libraries, a cookbook of hundreds of reusable peripheral and module libraries have been built on top of the SDK by the mbed Developer Community.

Freescale Kinetis FRDM-KL43Z

•
Freescale Kinetis FRDM-KL43Z
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MKL43Z256VLH4
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Freescale

Please use frdm_kl43z ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_kl43z]
platform = freescalekinetis
board = frdm_kl43z


You can override default Freescale Kinetis FRDM-KL43Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl43z.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_kl43z]
platform = freescalekinetis
board = frdm_kl43z
; change microcontroller
board_build.mcu = mkl43z256vlh4
; change MCU frequency
board_build.f_cpu = 48000000L


Freescale Kinetis FRDM-KL43Z supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_kl43z]
platform = freescalekinetis
board = frdm_kl43z
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-KL43Z 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
Mbed The mbed framework The mbed SDK has been designed to provide enough hardware abstraction to be intuitive and concise, yet powerful enough to build complex projects. It is built on the low-level ARM CMSIS APIs, allowing you to code down to the metal if needed. In addition to RTOS, USB and Networking libraries, a cookbook of hundreds of reusable peripheral and module libraries have been built on top of the SDK by the mbed Developer Community.

Freescale Kinetis FRDM-KL46Z

•
Freescale Kinetis FRDM-KL46Z
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MKL46Z256VLL4
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Freescale

Please use frdm_kl46z ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_kl46z]
platform = freescalekinetis
board = frdm_kl46z


You can override default Freescale Kinetis FRDM-KL46Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl46z.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_kl46z]
platform = freescalekinetis
board = frdm_kl46z
; change microcontroller
board_build.mcu = mkl46z256vll4
; change MCU frequency
board_build.f_cpu = 48000000L


Freescale Kinetis FRDM-KL46Z supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_kl46z]
platform = freescalekinetis
board = frdm_kl46z
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-KL46Z 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
Mbed The mbed framework The mbed SDK has been designed to provide enough hardware abstraction to be intuitive and concise, yet powerful enough to build complex projects. It is built on the low-level ARM CMSIS APIs, allowing you to code down to the metal if needed. In addition to RTOS, USB and Networking libraries, a cookbook of hundreds of reusable peripheral and module libraries have been built on top of the SDK by the mbed Developer Community.

Freescale Kinetis FRDM-KL82Z

•
Freescale Kinetis FRDM-KL82Z
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MKL82Z128VLK7
Frequency 96MHz
Flash 128KB
RAM 96KB
Vendor Freescale

Please use frdm_kl82z ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_kl82z]
platform = freescalekinetis
board = frdm_kl82z


You can override default Freescale Kinetis FRDM-KL82Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kl82z.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_kl82z]
platform = freescalekinetis
board = frdm_kl82z
; change microcontroller
board_build.mcu = mkl82z128vlk7
; change MCU frequency
board_build.f_cpu = 96000000L


Freescale Kinetis FRDM-KL82Z supports the next uploading protocols:

  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_kl82z]
platform = freescalekinetis
board = frdm_kl82z
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-KL82Z does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
J-LINK Yes

Name Description
Mbed The mbed framework The mbed SDK has been designed to provide enough hardware abstraction to be intuitive and concise, yet powerful enough to build complex projects. It is built on the low-level ARM CMSIS APIs, allowing you to code down to the metal if needed. In addition to RTOS, USB and Networking libraries, a cookbook of hundreds of reusable peripheral and module libraries have been built on top of the SDK by the mbed Developer Community.

Freescale Kinetis FRDM-KW24D512

•
Freescale Kinetis FRDM-KW24D512
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MKW24D512
Frequency 50MHz
Flash 512KB
RAM 64KB
Vendor Freescale

Please use frdm_kw24d ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_kw24d]
platform = freescalekinetis
board = frdm_kw24d


You can override default Freescale Kinetis FRDM-KW24D512 settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kw24d.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_kw24d]
platform = freescalekinetis
board = frdm_kw24d
; change microcontroller
board_build.mcu = mkw24d512
; change MCU frequency
board_build.f_cpu = 50000000L


Freescale Kinetis FRDM-KW24D512 supports the next uploading protocols:

  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_kw24d]
platform = freescalekinetis
board = frdm_kw24d
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-KW24D512 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
J-LINK Yes

Name Description
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.
Zephyr The Zephyr Project is a scalable real-time operating system (RTOS) supporting multiple hardware architectures, optimized for resource constrained devices, and built with safety and security in mind.

Freescale Kinetis FRDM-KW41Z

•
Freescale Kinetis FRDM-KW41Z
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MKW41Z512VHT4
Frequency 48MHz
Flash 512KB
RAM 128KB
Vendor Freescale

Please use frdm_kw41z ID for board option in "platformio.ini" (Project Configuration File):

[env:frdm_kw41z]
platform = freescalekinetis
board = frdm_kw41z


You can override default Freescale Kinetis FRDM-KW41Z settings per build environment using board_*** option, where *** is a JSON object path from board manifest frdm_kw41z.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:frdm_kw41z]
platform = freescalekinetis
board = frdm_kw41z
; change microcontroller
board_build.mcu = mkw41z512vht4
; change MCU frequency
board_build.f_cpu = 48000000L


Freescale Kinetis FRDM-KW41Z supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:frdm_kw41z]
platform = freescalekinetis
board = frdm_kw41z
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Freescale Kinetis FRDM-KW41Z 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
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.

•
Hexiwear
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Freescale Kinetis: Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.

Microcontroller MK64FN1M0VDC12
Frequency 120MHz
Flash 1MB
RAM 256KB
Vendor MikroElektronika

Please use hexiwear ID for board option in "platformio.ini" (Project Configuration File):

[env:hexiwear]
platform = freescalekinetis
board = hexiwear


You can override default Hexiwear settings per build environment using board_*** option, where *** is a JSON object path from board manifest hexiwear.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:hexiwear]
platform = freescalekinetis
board = hexiwear
; change microcontroller
board_build.mcu = mk64fn1m0vdc12
; change MCU frequency
board_build.f_cpu = 120000000L


Hexiwear supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:hexiwear]
platform = freescalekinetis
board = hexiwear
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Hexiwear does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
CMSIS-DAP Yes
J-LINK

Name Description
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.
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.

GigaDevice GD32V

•
GD32VF103V-EVAL
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform GigaDevice GD32V: The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.

Microcontroller GD32VF103VBT6
Frequency 108MHz
Flash 128KB
RAM 32KB
Vendor Sipeed

Please use gd32vf103v-eval ID for board option in "platformio.ini" (Project Configuration File):

[env:gd32vf103v-eval]
platform = gd32v
board = gd32vf103v-eval


You can override default GD32VF103V-EVAL settings per build environment using board_*** option, where *** is a JSON object path from board manifest gd32vf103v-eval.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:gd32vf103v-eval]
platform = gd32v
board = gd32vf103v-eval
; change microcontroller
board_build.mcu = GD32VF103VBT6
; change MCU frequency
board_build.f_cpu = 108000000L


GD32VF103V-EVAL supports the next uploading protocols:

  • altera-usb-blaster
  • gd-link
  • jlink
  • rv-link
  • serial
  • sipeed-rv-debugger
  • um232h

Default protocol is gd-link

You can change upload protocol using upload_protocol option:

[env:gd32vf103v-eval]
platform = gd32v
board = gd32vf103v-eval
upload_protocol = gd-link


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

GD32VF103V-EVAL does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Altera / Intel USB-Blaster Download Cable Yes
GD-LINK
J-LINK
RV-LINK
Sipeed RV Debugger
UM232H

Name Description
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.
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)

•
Sipeed Longan Nano
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform GigaDevice GD32V: The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.

Microcontroller GD32VF103CBT6
Frequency 108MHz
Flash 128KB
RAM 32KB
Vendor Sipeed

Please use sipeed-longan-nano ID for board option in "platformio.ini" (Project Configuration File):

[env:sipeed-longan-nano]
platform = gd32v
board = sipeed-longan-nano


You can override default Sipeed Longan Nano settings per build environment using board_*** option, where *** is a JSON object path from board manifest sipeed-longan-nano.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sipeed-longan-nano]
platform = gd32v
board = sipeed-longan-nano
; change microcontroller
board_build.mcu = GD32VF103CBT6
; change MCU frequency
board_build.f_cpu = 108000000L


Sipeed Longan Nano supports the next uploading protocols:

  • altera-usb-blaster
  • gd-link
  • jlink
  • rv-link
  • serial
  • sipeed-rv-debugger
  • um232h

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:sipeed-longan-nano]
platform = gd32v
board = sipeed-longan-nano
upload_protocol = serial


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Sipeed Longan Nano does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Altera / Intel USB-Blaster Download Cable Yes
GD-LINK
J-LINK
RV-LINK
Sipeed RV Debugger
UM232H

Name Description
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.
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)

•
Sipeed Longan Nano Lite
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform GigaDevice GD32V: The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.

Microcontroller GD32VF103C8T6
Frequency 108MHz
Flash 64KB
RAM 20KB
Vendor Sipeed

Please use sipeed-longan-nano-lite ID for board option in "platformio.ini" (Project Configuration File):

[env:sipeed-longan-nano-lite]
platform = gd32v
board = sipeed-longan-nano-lite


You can override default Sipeed Longan Nano Lite settings per build environment using board_*** option, where *** is a JSON object path from board manifest sipeed-longan-nano-lite.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sipeed-longan-nano-lite]
platform = gd32v
board = sipeed-longan-nano-lite
; change microcontroller
board_build.mcu = GD32VF103C8T6
; change MCU frequency
board_build.f_cpu = 108000000L


Sipeed Longan Nano Lite supports the next uploading protocols:

  • altera-usb-blaster
  • gd-link
  • jlink
  • rv-link
  • serial
  • sipeed-rv-debugger
  • um232h

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:sipeed-longan-nano-lite]
platform = gd32v
board = sipeed-longan-nano-lite
upload_protocol = serial


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Sipeed Longan Nano Lite does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Altera / Intel USB-Blaster Download Cable Yes
GD-LINK
J-LINK
RV-LINK
Sipeed RV Debugger
UM232H

Name Description
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.
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)

•
Wio Lite RISC-V
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform GigaDevice GD32V: The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.

Microcontroller GD32VF103CBT6
Frequency 108MHz
Flash 128KB
RAM 32KB
Vendor SeeedStudio

Please use wio_lite_risc-v ID for board option in "platformio.ini" (Project Configuration File):

[env:wio_lite_risc-v]
platform = gd32v
board = wio_lite_risc-v


You can override default Wio Lite RISC-V settings per build environment using board_*** option, where *** is a JSON object path from board manifest wio_lite_risc-v.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wio_lite_risc-v]
platform = gd32v
board = wio_lite_risc-v
; change microcontroller
board_build.mcu = GD32VF103CBT6
; change MCU frequency
board_build.f_cpu = 108000000L


Wio Lite RISC-V supports the next uploading protocols:

  • altera-usb-blaster
  • gd-link
  • jlink
  • rv-link
  • serial
  • sipeed-rv-debugger
  • um232h

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:wio_lite_risc-v]
platform = gd32v
board = wio_lite_risc-v
upload_protocol = serial


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Wio Lite RISC-V does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Altera / Intel USB-Blaster Download Cable Yes
GD-LINK
J-LINK
RV-LINK
Sipeed RV Debugger
UM232H

Name Description
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.
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)

Infineon XMC

•
XMC1100 Boot Kit
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Infineon XMC: Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform

Microcontroller XMC1100
Frequency 32MHz
Flash 64KB
RAM 16KB
Vendor Infineon

Please use xmc1100_boot_kit ID for board option in "platformio.ini" (Project Configuration File):

[env:xmc1100_boot_kit]
platform = infineonxmc
board = xmc1100_boot_kit


You can override default XMC1100 Boot Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1100_boot_kit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xmc1100_boot_kit]
platform = infineonxmc
board = xmc1100_boot_kit
; change microcontroller
board_build.mcu = XMC1100
; change MCU frequency
board_build.f_cpu = 32000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

XMC1100 Boot Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.

Compatible Tools On-board Default
J-LINK Yes Yes

Name Description
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.

•
XMC1100 H-Bridge 2Go
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Infineon XMC: Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform

Microcontroller XMC1100
Frequency 32MHz
Flash 64KB
RAM 16KB
Vendor Infineon

Please use xmc1100_h_bridge2go ID for board option in "platformio.ini" (Project Configuration File):

[env:xmc1100_h_bridge2go]
platform = infineonxmc
board = xmc1100_h_bridge2go


You can override default XMC1100 H-Bridge 2Go settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1100_h_bridge2go.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xmc1100_h_bridge2go]
platform = infineonxmc
board = xmc1100_h_bridge2go
; change microcontroller
board_build.mcu = XMC1100
; change MCU frequency
board_build.f_cpu = 32000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

XMC1100 H-Bridge 2Go 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
J-LINK Yes Yes

Name Description
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.

•
XMC1100 XMC2Go
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Infineon XMC: Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform

Microcontroller XMC1100
Frequency 32MHz
Flash 64KB
RAM 16KB
Vendor Infineon

Please use xmc1100_xmc2go ID for board option in "platformio.ini" (Project Configuration File):

[env:xmc1100_xmc2go]
platform = infineonxmc
board = xmc1100_xmc2go


You can override default XMC1100 XMC2Go settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1100_xmc2go.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xmc1100_xmc2go]
platform = infineonxmc
board = xmc1100_xmc2go
; change microcontroller
board_build.mcu = XMC1100
; change MCU frequency
board_build.f_cpu = 32000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

XMC1100 XMC2Go 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
J-LINK Yes Yes

Name Description
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.

•
XMC1300 Boot Kit
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Infineon XMC: Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform

Microcontroller XMC1300
Frequency 32MHz
Flash 64KB
RAM 16KB
Vendor Infineon

Please use xmc1300_boot_kit ID for board option in "platformio.ini" (Project Configuration File):

[env:xmc1300_boot_kit]
platform = infineonxmc
board = xmc1300_boot_kit


You can override default XMC1300 Boot Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1300_boot_kit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xmc1300_boot_kit]
platform = infineonxmc
board = xmc1300_boot_kit
; change microcontroller
board_build.mcu = XMC1300
; change MCU frequency
board_build.f_cpu = 32000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

XMC1300 Boot Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.

Compatible Tools On-board Default
J-LINK Yes Yes

Name Description
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.

•
XMC1300 Sense2GoL
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Infineon XMC: Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform

Microcontroller XMC1300
Frequency 32MHz
Flash 32KB
RAM 16KB
Vendor Infineon

Please use xmc1300_sense2gol ID for board option in "platformio.ini" (Project Configuration File):

[env:xmc1300_sense2gol]
platform = infineonxmc
board = xmc1300_sense2gol


You can override default XMC1300 Sense2GoL settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1300_sense2gol.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xmc1300_sense2gol]
platform = infineonxmc
board = xmc1300_sense2gol
; change microcontroller
board_build.mcu = XMC1300
; change MCU frequency
board_build.f_cpu = 32000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

XMC1300 Sense2GoL 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
J-LINK Yes Yes

Name Description
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.

•
XMC1400 Boot Kit
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Infineon XMC: Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform

Microcontroller XMC1400
Frequency 48MHz
Flash 1.95MB
RAM 16KB
Vendor Infineon

Please use xmc1400_boot_kit ID for board option in "platformio.ini" (Project Configuration File):

[env:xmc1400_boot_kit]
platform = infineonxmc
board = xmc1400_boot_kit


You can override default XMC1400 Boot Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc1400_boot_kit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xmc1400_boot_kit]
platform = infineonxmc
board = xmc1400_boot_kit
; change microcontroller
board_build.mcu = XMC1400
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

XMC1400 Boot Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.

Compatible Tools On-board Default
J-LINK Yes Yes

Name Description
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.

•
XMC4200 Distance2Go
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Infineon XMC: Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform

Microcontroller XMC4200
Frequency 80MHz
Flash 256KB
RAM 40KB
Vendor Infineon

Please use xmc4200_distance2go ID for board option in "platformio.ini" (Project Configuration File):

[env:xmc4200_distance2go]
platform = infineonxmc
board = xmc4200_distance2go


You can override default XMC4200 Distance2Go settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc4200_distance2go.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xmc4200_distance2go]
platform = infineonxmc
board = xmc4200_distance2go
; change microcontroller
board_build.mcu = XMC4200
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

XMC4200 Distance2Go 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
J-LINK Yes Yes

Name Description
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.

•
XMC4700 Relax Kit
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Infineon XMC: Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform

Microcontroller XMC4700
Frequency 144MHz
Flash 2.00MB
RAM 1.95MB
Vendor Infineon

Please use xmc4700_relax_kit ID for board option in "platformio.ini" (Project Configuration File):

[env:xmc4700_relax_kit]
platform = infineonxmc
board = xmc4700_relax_kit


You can override default XMC4700 Relax Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest xmc4700_relax_kit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xmc4700_relax_kit]
platform = infineonxmc
board = xmc4700_relax_kit
; change microcontroller
board_build.mcu = XMC4700
; change MCU frequency
board_build.f_cpu = 144000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

XMC4700 Relax 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
J-LINK Yes Yes

Name Description
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.

Intel ARC32

•
Arduino/Genuino 101
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Intel ARC32: ARC embedded processors are a family of 32-bit CPUs that are widely used in SoC devices for storage, home, mobile, automotive, and Internet of Things applications.

Microcontroller ARCV2EM
Frequency 32MHz
Flash 152KB
RAM 80KB
Vendor Intel

Please use genuino101 ID for board option in "platformio.ini" (Project Configuration File):

[env:genuino101]
platform = intel_arc32
board = genuino101


You can override default Arduino/Genuino 101 settings per build environment using board_*** option, where *** is a JSON object path from board manifest genuino101.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genuino101]
platform = intel_arc32
board = genuino101
; change microcontroller
board_build.mcu = ARCv2EM
; change MCU frequency
board_build.f_cpu = 32000000L


PIO Unified Debugger currently does not support Arduino/Genuino 101 board.

Name Description
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.

Intel MCS-51 (8051)

•
Generic N79E8432
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller N79E8432
Frequency 22MHz
Flash 4KB
RAM 512B
Vendor Nuvoton

Please use n79e8432 ID for board option in "platformio.ini" (Project Configuration File):

[env:n79e8432]
platform = intel_mcs51
board = n79e8432


You can override default Generic N79E8432 settings per build environment using board_*** option, where *** is a JSON object path from board manifest n79e8432.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:n79e8432]
platform = intel_mcs51
board = n79e8432
; change microcontroller
board_build.mcu = n79e8432
; change MCU frequency
board_build.f_cpu = 22118400L


PIO Unified Debugger currently does not support Generic N79E8432 board.

•
Generic N79E844
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller N79E844
Frequency 22MHz
Flash 8KB
RAM 512B
Vendor Nuvoton

Please use n79e844 ID for board option in "platformio.ini" (Project Configuration File):

[env:n79e844]
platform = intel_mcs51
board = n79e844


You can override default Generic N79E844 settings per build environment using board_*** option, where *** is a JSON object path from board manifest n79e844.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:n79e844]
platform = intel_mcs51
board = n79e844
; change microcontroller
board_build.mcu = n79e844
; change MCU frequency
board_build.f_cpu = 22118400L


PIO Unified Debugger currently does not support Generic N79E844 board.

•
Generic N79E845
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller N79E845
Frequency 22MHz
Flash 16KB
RAM 512B
Vendor Nuvoton

Please use n79e845 ID for board option in "platformio.ini" (Project Configuration File):

[env:n79e845]
platform = intel_mcs51
board = n79e845


You can override default Generic N79E845 settings per build environment using board_*** option, where *** is a JSON object path from board manifest n79e845.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:n79e845]
platform = intel_mcs51
board = n79e845
; change microcontroller
board_build.mcu = n79e845
; change MCU frequency
board_build.f_cpu = 22118400L


PIO Unified Debugger currently does not support Generic N79E845 board.

•
Generic N79E854
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller N79E854
Frequency 22MHz
Flash 8KB
RAM 512B
Vendor Nuvoton

Please use n79e854 ID for board option in "platformio.ini" (Project Configuration File):

[env:n79e854]
platform = intel_mcs51
board = n79e854


You can override default Generic N79E854 settings per build environment using board_*** option, where *** is a JSON object path from board manifest n79e854.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:n79e854]
platform = intel_mcs51
board = n79e854
; change microcontroller
board_build.mcu = n79e854
; change MCU frequency
board_build.f_cpu = 22118400L


PIO Unified Debugger currently does not support Generic N79E854 board.

•
Generic N79E855
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller N79E855
Frequency 22MHz
Flash 16KB
RAM 512B
Vendor Nuvoton

Please use n79e855 ID for board option in "platformio.ini" (Project Configuration File):

[env:n79e855]
platform = intel_mcs51
board = n79e855


You can override default Generic N79E855 settings per build environment using board_*** option, where *** is a JSON object path from board manifest n79e855.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:n79e855]
platform = intel_mcs51
board = n79e855
; change microcontroller
board_build.mcu = n79e855
; change MCU frequency
board_build.f_cpu = 22118400L


PIO Unified Debugger currently does not support Generic N79E855 board.

•
Generic STC15F204EA
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller STC15F204EA
Frequency 11MHz
Flash 4KB
RAM 256B
Vendor STC

Please use stc15f204ea ID for board option in "platformio.ini" (Project Configuration File):

[env:stc15f204ea]
platform = intel_mcs51
board = stc15f204ea


You can override default Generic STC15F204EA settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc15f204ea.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:stc15f204ea]
platform = intel_mcs51
board = stc15f204ea
; change microcontroller
board_build.mcu = stc15f204ea
; change MCU frequency
board_build.f_cpu = 11059200L


PIO Unified Debugger currently does not support Generic STC15F204EA board.

•
Generic STC15F2K60S2
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller STC15F2K60S2
Frequency 6MHz
Flash 60KB
RAM 2KB
Vendor STC

Please use stc15f2k60s2 ID for board option in "platformio.ini" (Project Configuration File):

[env:stc15f2k60s2]
platform = intel_mcs51
board = stc15f2k60s2


You can override default Generic STC15F2K60S2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc15f2k60s2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:stc15f2k60s2]
platform = intel_mcs51
board = stc15f2k60s2
; change microcontroller
board_build.mcu = stc15f2k60s2
; change MCU frequency
board_build.f_cpu = 6000000L


PIO Unified Debugger currently does not support Generic STC15F2K60S2 board.

•
Generic STC15W204S
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller STC15W204S
Frequency 11MHz
Flash 4KB
RAM 256B
Vendor STC

Please use stc15w204s ID for board option in "platformio.ini" (Project Configuration File):

[env:stc15w204s]
platform = intel_mcs51
board = stc15w204s


You can override default Generic STC15W204S settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc15w204s.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:stc15w204s]
platform = intel_mcs51
board = stc15w204s
; change microcontroller
board_build.mcu = stc15w204s
; change MCU frequency
board_build.f_cpu = 11059200L


PIO Unified Debugger currently does not support Generic STC15W204S board.

•
Generic STC15W404AS
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller STC15W404AS
Frequency 11MHz
Flash 4KB
RAM 512B
Vendor STC

Please use stc15w404as ID for board option in "platformio.ini" (Project Configuration File):

[env:stc15w404as]
platform = intel_mcs51
board = stc15w404as


You can override default Generic STC15W404AS settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc15w404as.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:stc15w404as]
platform = intel_mcs51
board = stc15w404as
; change microcontroller
board_build.mcu = stc15w404as
; change MCU frequency
board_build.f_cpu = 11059200L


PIO Unified Debugger currently does not support Generic STC15W404AS board.

•
Generic STC15W408AS
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller STC15W408AS
Frequency 11MHz
Flash 8KB
RAM 512B
Vendor STC

Please use stc15w408as ID for board option in "platformio.ini" (Project Configuration File):

[env:stc15w408as]
platform = intel_mcs51
board = stc15w408as


You can override default Generic STC15W408AS settings per build environment using board_*** option, where *** is a JSON object path from board manifest stc15w408as.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:stc15w408as]
platform = intel_mcs51
board = stc15w408as
; change microcontroller
board_build.mcu = stc15w408as
; change MCU frequency
board_build.f_cpu = 11059200L


PIO Unified Debugger currently does not support Generic STC15W408AS board.

•
Generic STC89C52RC
  • Hardware
  • Configuration
  • Debugging


Platform Intel MCS-51 (8051): The Intel MCS-51 (commonly termed 8051) is an internally Harvard architecture, complex instruction set computer (CISC) instruction set, single chip microcontroller (uC) series developed by Intel in 1980 for use in embedded systems.

Microcontroller STC89C52RC
Frequency 11MHz
Flash 8KB
RAM 512B
Vendor STC

Please use stc89c52rc ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:stc89c52rc]
platform = intel_mcs51
board = stc89c52rc
; change microcontroller
board_build.mcu = stc89c52rc
; change MCU frequency
board_build.f_cpu = 11059200L


PIO Unified Debugger currently does not support Generic STC89C52RC board.

Kendryte K210

•
Sipeed MAIX BiT
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Kendryte K210: Kendryte K210 is an AI capable RISCV64 dual core SoC.

Microcontroller K210
Frequency 400MHz
Flash 16MB
RAM 6MB
Vendor Sipeed

Please use sipeed-maix-bit ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:sipeed-maix-bit]
platform = kendryte210
board = sipeed-maix-bit
; change microcontroller
board_build.mcu = K210
; change MCU frequency
board_build.f_cpu = 400000000L


Sipeed MAIX BiT supports the next uploading protocols:

  • iot-bus-jtag
  • jlink
  • kflash
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • sipeed-rv-debugger
  • tumpa

Default protocol is kflash

You can change upload protocol using upload_protocol option:

[env:sipeed-maix-bit]
platform = kendryte210
board = sipeed-maix-bit
upload_protocol = kflash


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
oddWires IOT-Bus JTAG Yes
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
Sipeed RV Debugger
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support

•
Sipeed MAIX BiT with Mic
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Kendryte K210: Kendryte K210 is an AI capable RISCV64 dual core SoC.

Microcontroller K210
Frequency 400MHz
Flash 16MB
RAM 6MB
Vendor Sipeed

Please use sipeed-maix-bit-mic ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:sipeed-maix-bit-mic]
platform = kendryte210
board = sipeed-maix-bit-mic
; change microcontroller
board_build.mcu = K210
; change MCU frequency
board_build.f_cpu = 400000000L


Sipeed MAIX BiT with Mic supports the next uploading protocols:

  • iot-bus-jtag
  • jlink
  • kflash
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • sipeed-rv-debugger
  • tumpa

Default protocol is kflash

You can change upload protocol using upload_protocol option:

[env:sipeed-maix-bit-mic]
platform = kendryte210
board = sipeed-maix-bit-mic
upload_protocol = kflash


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
oddWires IOT-Bus JTAG Yes
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
Sipeed RV Debugger
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support

•
Sipeed MAIX GO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Kendryte K210: Kendryte K210 is an AI capable RISCV64 dual core SoC.

Microcontroller K210
Frequency 400MHz
Flash 16MB
RAM 6MB
Vendor Sipeed

Please use sipeed-maix-go ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:sipeed-maix-go]
platform = kendryte210
board = sipeed-maix-go
; change microcontroller
board_build.mcu = K210
; change MCU frequency
board_build.f_cpu = 400000000L


Sipeed MAIX GO supports the next uploading protocols:

  • iot-bus-jtag
  • jlink
  • kflash
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • sipeed-rv-debugger
  • tumpa

Default protocol is kflash

You can change upload protocol using upload_protocol option:

[env:sipeed-maix-go]
platform = kendryte210
board = sipeed-maix-go
upload_protocol = kflash


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
oddWires IOT-Bus JTAG Yes
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
Sipeed RV Debugger
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support

•
Sipeed MAIX ONE DOCK
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Kendryte K210: Kendryte K210 is an AI capable RISCV64 dual core SoC.

Microcontroller K210
Frequency 400MHz
Flash 16MB
RAM 6MB
Vendor Sipeed

Please use sipeed-maix-one-dock ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:sipeed-maix-one-dock]
platform = kendryte210
board = sipeed-maix-one-dock
; change microcontroller
board_build.mcu = K210
; change MCU frequency
board_build.f_cpu = 400000000L


Sipeed MAIX ONE DOCK supports the next uploading protocols:

  • iot-bus-jtag
  • jlink
  • kflash
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • sipeed-rv-debugger
  • tumpa

Default protocol is kflash

You can change upload protocol using upload_protocol option:

[env:sipeed-maix-one-dock]
platform = kendryte210
board = sipeed-maix-one-dock
upload_protocol = kflash


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
oddWires IOT-Bus JTAG Yes
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
Sipeed RV Debugger
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support

•
Sipeed MAIXDUINO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Kendryte K210: Kendryte K210 is an AI capable RISCV64 dual core SoC.

Microcontroller K210
Frequency 400MHz
Flash 16MB
RAM 6MB
Vendor Sipeed

Please use sipeed-maixduino ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:sipeed-maixduino]
platform = kendryte210
board = sipeed-maixduino
; change microcontroller
board_build.mcu = K210
; change MCU frequency
board_build.f_cpu = 400000000L


Sipeed MAIXDUINO supports the next uploading protocols:

  • iot-bus-jtag
  • jlink
  • kflash
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • sipeed-rv-debugger
  • tumpa

Default protocol is kflash

You can change upload protocol using upload_protocol option:

[env:sipeed-maixduino]
platform = kendryte210
board = sipeed-maixduino
upload_protocol = kflash


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
oddWires IOT-Bus JTAG Yes
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
Sipeed RV Debugger
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
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.
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support

•
Sipeed MF1 MF1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Kendryte K210: Kendryte K210 is an AI capable RISCV64 dual core SoC.

Microcontroller K210
Frequency 400MHz
Flash 16MB
RAM 6MB
Vendor Sipeed

Please use sipeed-MF1 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:sipeed-MF1]
platform = kendryte210
board = sipeed-MF1
; change microcontroller
board_build.mcu = K210
; change MCU frequency
board_build.f_cpu = 400000000L


Sipeed MF1 MF1 supports the next uploading protocols:

  • iot-bus-jtag
  • jlink
  • kflash
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • sipeed-rv-debugger
  • tumpa

Default protocol is kflash

You can change upload protocol using upload_protocol option:

[env:sipeed-MF1]
platform = kendryte210
board = sipeed-MF1
upload_protocol = kflash


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
oddWires IOT-Bus JTAG Yes
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
Sipeed RV Debugger
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support

Lattice iCE40

•
IceZUM Alhambra FPGA
  • Hardware
  • Configuration
  • Debugging


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

Please use icezum ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:icezum]
platform = lattice_ice40
board = icezum
; change microcontroller
board_build.mcu = iCE40-HX1K-TQ144
; change MCU frequency
board_build.f_cpu = 12000000L


PIO Unified Debugger currently does not support IceZUM Alhambra FPGA board.

•
Lattice iCEstick FPGA Evaluation Kit
  • Hardware
  • Configuration
  • Debugging


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 Lattice

Please use icestick ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:icestick]
platform = lattice_ice40
board = icestick
; change microcontroller
board_build.mcu = iCE40-HX1K-TQ144
; change MCU frequency
board_build.f_cpu = 12000000L


PIO Unified Debugger currently does not support Lattice iCEstick FPGA Evaluation Kit board.

Linux ARM

•
Raspberry Pi 1 Model B
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


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

Please use raspberrypi_1b ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:raspberrypi_1b]
platform = linux_arm
board = raspberrypi_1b
; change microcontroller
board_build.mcu = bcm2835
; change MCU frequency
board_build.f_cpu = 700000000L


PIO Unified Debugger currently does not support Raspberry Pi 1 Model B board.

Name Description
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
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


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 BCM2836
Frequency 900MHz
Flash 1GB
RAM 1GB
Vendor Raspberry Pi

Please use raspberrypi_2b ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:raspberrypi_2b]
platform = linux_arm
board = raspberrypi_2b
; change microcontroller
board_build.mcu = bcm2836
; change MCU frequency
board_build.f_cpu = 900000000L


PIO Unified Debugger currently does not support Raspberry Pi 2 Model B board.

Name Description
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 3 Model B
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


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 BCM2837
Frequency 1200MHz
Flash 1GB
RAM 1GB
Vendor Raspberry Pi

Please use raspberrypi_3b ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:raspberrypi_3b]
platform = linux_arm
board = raspberrypi_3b
; change microcontroller
board_build.mcu = bcm2837
; change MCU frequency
board_build.f_cpu = 1200000000L


PIO Unified Debugger currently does not support Raspberry Pi 3 Model B board.

Name Description
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 Zero
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


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 1000MHz
Flash 512MB
RAM 512MB
Vendor Raspberry Pi

Please use raspberrypi_zero ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:raspberrypi_zero]
platform = linux_arm
board = raspberrypi_zero
; change microcontroller
board_build.mcu = bcm2835
; change MCU frequency
board_build.f_cpu = 1000000000L


PIO Unified Debugger currently does not support Raspberry Pi Zero board.

Name Description
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.

Maxim 32

•
MAX32620FTHR
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Maxim 32: 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

Please use max32620fthr ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:max32620fthr]
platform = maxim32
board = max32620fthr
; change microcontroller
board_build.mcu = max32620fthr
; change MCU frequency
board_build.f_cpu = 96000000L


MAX32620FTHR supports the next uploading protocols:

  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:max32620fthr]
platform = maxim32
board = max32620fthr
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
J-LINK Yes

Name Description
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.

•
MAX32625MBED
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Maxim 32: 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 MAX32625
Frequency 96MHz
Flash 512KB
RAM 160KB
Vendor Maxim

Please use max32625mbed ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:max32625mbed]
platform = maxim32
board = max32625mbed
; change microcontroller
board_build.mcu = max32625
; change MCU frequency
board_build.f_cpu = 96000000L


PIO Unified Debugger currently does not support MAX32625MBED board.

Name Description
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.

•
MAX32625NEXPAQ
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Maxim 32: 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 MAX32625
Frequency 96MHz
Flash 512KB
RAM 160KB
Vendor Maxim

Please use max32625nexpaq ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:max32625nexpaq]
platform = maxim32
board = max32625nexpaq
; change microcontroller
board_build.mcu = max32625
; change MCU frequency
board_build.f_cpu = 96000000L


PIO Unified Debugger currently does not support MAX32625NEXPAQ board.

Name Description
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.

•
MAX32625PICO
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Maxim 32: 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 MAX32625
Frequency 96MHz
Flash 512KB
RAM 160KB
Vendor Maxim

Please use max32625pico ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:max32625pico]
platform = maxim32
board = max32625pico
; change microcontroller
board_build.mcu = max32625
; change MCU frequency
board_build.f_cpu = 96000000L


PIO Unified Debugger currently does not support MAX32625PICO board.

Name Description
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.

•
Maxim ARM mbed Enabled Development Platform for MAX32600
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Maxim 32: 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 MAX32600
Frequency 24MHz
Flash 256KB
RAM 32KB
Vendor Maxim

Please use max32600mbed ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:max32600mbed]
platform = maxim32
board = max32600mbed
; change microcontroller
board_build.mcu = max32600
; change MCU frequency
board_build.f_cpu = 24000000L


Maxim ARM mbed Enabled Development Platform for MAX32600 supports the next uploading protocols:

  • cmsis-dap
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:max32600mbed]
platform = maxim32
board = max32600mbed
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
CMSIS-DAP Yes Yes

Name Description
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.

•
Maxim Health Sensor Platform
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Maxim 32: 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 MAX32620
Frequency 96MHz
Flash 2MB
RAM 256KB
Vendor Maxim

Please use max32620hsp ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:max32620hsp]
platform = maxim32
board = max32620hsp
; change microcontroller
board_build.mcu = max32620
; change MCU frequency
board_build.f_cpu = 96000000L


Maxim Health Sensor Platform supports the next uploading protocols:

  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:max32620hsp]
platform = maxim32
board = max32620hsp
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
J-LINK Yes

Name Description
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.

•
Maxim MAX32630FTHR Application Platform
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Maxim 32: 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 MAX32630
Frequency 96MHz
Flash 2MB
RAM 512KB
Vendor Maxim

Please use max32630fthr ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:max32630fthr]
platform = maxim32
board = max32630fthr
; change microcontroller
board_build.mcu = max32630
; change MCU frequency
board_build.f_cpu = 96000000L


PIO Unified Debugger currently does not support Maxim MAX32630FTHR Application Platform board.

Name Description
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.

•
Maxim Wireless Sensor Node Demonstrator
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Maxim 32: 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 MAX32610
Frequency 24MHz
Flash 256KB
RAM 32KB
Vendor Maxim

Please use maxwsnenv ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:maxwsnenv]
platform = maxim32
board = maxwsnenv
; change microcontroller
board_build.mcu = max32610
; change MCU frequency
board_build.f_cpu = 24000000L


Maxim Wireless Sensor Node Demonstrator supports the next uploading protocols:

  • cmsis-dap
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:maxwsnenv]
platform = maxim32
board = maxwsnenv
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
CMSIS-DAP Yes

Name Description
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.

•
SDT32620B
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Maxim 32: 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 MAX32620IWG
Frequency 96MHz
Flash 2MB
RAM 256KB
Vendor Sigma Delta Technologies

Please use sdt32620b ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:sdt32620b]
platform = maxim32
board = sdt32620b
; change microcontroller
board_build.mcu = max32620iwg
; change MCU frequency
board_build.f_cpu = 96000000L


PIO Unified Debugger currently does not support SDT32620B board.

Name Description
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.

•
SDT32625B
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Maxim 32: 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 MAX32625ITK
Frequency 96MHz
Flash 512KB
RAM 160KB
Vendor Sigma Delta Technologies

Please use sdt32625b ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:sdt32625b]
platform = maxim32
board = sdt32625b
; change microcontroller
board_build.mcu = max32625itk
; change MCU frequency
board_build.f_cpu = 96000000L


PIO Unified Debugger currently does not support SDT32625B board.

Name Description
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.

Microchip PIC32

•
4D Systems PICadillo 35T
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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

Please use picadillo_35t ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:picadillo_35t]
platform = microchippic32
board = picadillo_35t
; change microcontroller
board_build.mcu = 32MX795F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support 4D Systems PICadillo 35T board.

Name Description
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.

•
DataStation Mini
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX150F128C
Frequency 40MHz
Flash 120KB
RAM 32KB
Vendor Makerology

Please use dsmini ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:dsmini]
platform = microchippic32
board = dsmini
; change microcontroller
board_build.mcu = 32MX150F128C
; change MCU frequency
board_build.f_cpu = 40000000L


PIO Unified Debugger currently does not support DataStation Mini board.

Name Description
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.

•
Digilent Cerebot 32MX4
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX460F512L
Frequency 80MHz
Flash 508KB
RAM 32KB
Vendor Digilent

Please use cerebot32mx4 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:cerebot32mx4]
platform = microchippic32
board = cerebot32mx4
; change microcontroller
board_build.mcu = 32MX460F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Digilent Cerebot 32MX4 board.

Name Description
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.

•
Digilent Cerebot 32MX7
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 Digilent

Please use cerebot32mx7 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:cerebot32mx7]
platform = microchippic32
board = cerebot32mx7
; change microcontroller
board_build.mcu = 32MX795F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Digilent Cerebot 32MX7 board.

Name Description
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.

•
Digilent OpenScope
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MZ2048EFG124
Frequency 200MHz
Flash 1.98MB
RAM 512KB
Vendor Digilent

Please use openscope ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:openscope]
platform = microchippic32
board = openscope
; change microcontroller
board_build.mcu = 32MZ2048EFG124
; change MCU frequency
board_build.f_cpu = 200000000L


PIO Unified Debugger currently does not support Digilent OpenScope board.

Name Description
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.

•
Digilent chipKIT Cmod
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX150F128D
Frequency 40MHz
Flash 124KB
RAM 32KB
Vendor Digilent

Please use chipkit_cmod ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:chipkit_cmod]
platform = microchippic32
board = chipkit_cmod
; change microcontroller
board_build.mcu = 32MX150F128D
; change MCU frequency
board_build.f_cpu = 40000000L


PIO Unified Debugger currently does not support Digilent chipKIT Cmod board.

Name Description
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.

•
Digilent chipKIT DP32
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX250F128B
Frequency 40MHz
Flash 120KB
RAM 32KB
Vendor Digilent

Please use chipkit_dp32 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:chipkit_dp32]
platform = microchippic32
board = chipkit_dp32
; change microcontroller
board_build.mcu = 32MX250F128B
; change MCU frequency
board_build.f_cpu = 40000000L


PIO Unified Debugger currently does not support Digilent chipKIT DP32 board.

Name Description
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.

•
Digilent chipKIT MAX32
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 Digilent

Please use mega_pic32 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:mega_pic32]
platform = microchippic32
board = mega_pic32
; change microcontroller
board_build.mcu = 32MX795F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Digilent chipKIT MAX32 board.

Name Description
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.

•
Digilent chipKIT MX3
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX320F128H
Frequency 80MHz
Flash 124KB
RAM 16KB
Vendor Digilent

Please use chipkit_mx3 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:chipkit_mx3]
platform = microchippic32
board = chipkit_mx3
; change microcontroller
board_build.mcu = 32MX320F128H
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Digilent chipKIT MX3 board.

Name Description
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.

•
Digilent chipKIT Pro MX4
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX460F512L
Frequency 80MHz
Flash 508KB
RAM 32KB
Vendor Digilent

Please use chipkit_pro_mx4 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:chipkit_pro_mx4]
platform = microchippic32
board = chipkit_pro_mx4
; change microcontroller
board_build.mcu = 32MX460F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Digilent chipKIT Pro MX4 board.

Name Description
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.

•
Digilent chipKIT Pro MX7
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 Digilent

Please use chipkit_pro_mx7 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:chipkit_pro_mx7]
platform = microchippic32
board = chipkit_pro_mx7
; change microcontroller
board_build.mcu = 32MX795F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Digilent chipKIT Pro MX7 board.

Name Description
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.

•
Digilent chipKIT UNO32
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX320F128H
Frequency 80MHz
Flash 124KB
RAM 16KB
Vendor Digilent

Please use uno_pic32 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:uno_pic32]
platform = microchippic32
board = uno_pic32
; change microcontroller
board_build.mcu = 32MX320F128H
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Digilent chipKIT UNO32 board.

Name Description
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.

•
Digilent chipKIT WF32
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX695F512L
Frequency 80MHz
Flash 508KB
RAM 128KB
Vendor Digilent

Please use chipkit_wf32 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:chipkit_wf32]
platform = microchippic32
board = chipkit_wf32
; change microcontroller
board_build.mcu = 32MX695F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Digilent chipKIT WF32 board.

Name Description
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.

•
Digilent chipKIT WiFire
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MZ2048ECG100
Frequency 200MHz
Flash 1.98MB
RAM 512KB
Vendor Digilent

Please use chipkit_wifire ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:chipkit_wifire]
platform = microchippic32
board = chipkit_wifire
; change microcontroller
board_build.mcu = 32MZ2048ECG100
; change MCU frequency
board_build.f_cpu = 200000000L


PIO Unified Debugger currently does not support Digilent chipKIT WiFire board.

Name Description
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.

•
Digilent chipKIT uC32
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX340F512H
Frequency 80MHz
Flash 508KB
RAM 32KB
Vendor Digilent

Please use chipkit_uc32 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:chipkit_uc32]
platform = microchippic32
board = chipkit_uc32
; change microcontroller
board_build.mcu = 32MX340F512H
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Digilent chipKIT uC32 board.

Name Description
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.

•
Element14 chipKIT Pi
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX250F128B
Frequency 40MHz
Flash 120KB
RAM 32KB
Vendor element14

Please use chipkit_pi ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:chipkit_pi]
platform = microchippic32
board = chipkit_pi
; change microcontroller
board_build.mcu = 32MX250F128B
; change MCU frequency
board_build.f_cpu = 40000000L


PIO Unified Debugger currently does not support Element14 chipKIT Pi board.

Name Description
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.

•
Fubarino Mini
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX250F128D
Frequency 48MHz
Flash 120KB
RAM 32KB
Vendor Fubarino

Please use fubarino_mini ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:fubarino_mini]
platform = microchippic32
board = fubarino_mini
; change microcontroller
board_build.mcu = 32MX250F128D
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support Fubarino Mini board.

Name Description
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.

•
Fubarino SD (1.5)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX795F512H
Frequency 80MHz
Flash 508KB
RAM 128KB
Vendor Fubarino

Please use fubarino_sd ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:fubarino_sd]
platform = microchippic32
board = fubarino_sd
; change microcontroller
board_build.mcu = 32MX795F512H
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Fubarino SD (1.5) board.

Name Description
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.

•
HelvePic32
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX250F128B
Frequency 48MHz
Flash 120KB
RAM 32KB
Vendor BOXTEC

Please use helvepic32 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:helvepic32]
platform = microchippic32
board = helvepic32
; change microcontroller
board_build.mcu = 32MX250F128B
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support HelvePic32 board.

Name Description
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.

•
HelvePic32
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX250F128B
Frequency 48MHz
Flash 120KB
RAM 32KB
Vendor BOXTEC

Please use helvepic32_breadboardside ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:helvepic32_breadboardside]
platform = microchippic32
board = helvepic32_breadboardside
; change microcontroller
board_build.mcu = 32MX250F128B
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support HelvePic32 board.

Name Description
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.

•
HelvePic32
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX250F128D
Frequency 48MHz
Flash 120KB
RAM 32KB
Vendor BOXTEC

Please use helvepic32_smd ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:helvepic32_smd]
platform = microchippic32
board = helvepic32_smd
; change microcontroller
board_build.mcu = 32MX250F128D
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support HelvePic32 board.

Name Description
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.

•
HelvePic32 MX270
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX270F256B
Frequency 48MHz
Flash 244KB
RAM 62KB
Vendor BOXTEC

Please use helvepic32_mx270 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:helvepic32_mx270]
platform = microchippic32
board = helvepic32_mx270
; change microcontroller
board_build.mcu = 32MX270F256B
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support HelvePic32 MX270 board.

Name Description
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.

•
HelvePic32 Robot
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX270F256D
Frequency 48MHz
Flash 244KB
RAM 62KB
Vendor BOXTEC

Please use helvepic32_robot ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:helvepic32_robot]
platform = microchippic32
board = helvepic32_robot
; change microcontroller
board_build.mcu = 32MX270F256D
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support HelvePic32 Robot board.

Name Description
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.

•
HelvePic32 SMD MX270
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX270F256D
Frequency 48MHz
Flash 244KB
RAM 62KB
Vendor BOXTEC

Please use helvepic32_smd_mx270 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:helvepic32_smd_mx270]
platform = microchippic32
board = helvepic32_smd_mx270
; change microcontroller
board_build.mcu = 32MX270F256D
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support HelvePic32 SMD MX270 board.

Name Description
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.

•
MikroElektronika Clicker 2
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX460F512L
Frequency 80MHz
Flash 508KB
RAM 32KB
Vendor MikroElektronika

Please use clicker2 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:clicker2]
platform = microchippic32
board = clicker2
; change microcontroller
board_build.mcu = 32MX460F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support MikroElektronika Clicker 2 board.

Name Description
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.

•
MikroElektronika Flip N Click MZ
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MZ2048EFH100
Frequency 252MHz
Flash 1.98MB
RAM 512KB
Vendor MikroElektronika

Please use flipnclickmz ID for board option in "platformio.ini" (Project Configuration File):

[env:flipnclickmz]
platform = microchippic32
board = flipnclickmz


You can override default MikroElektronika Flip N Click MZ settings per build environment using board_*** option, where *** is a JSON object path from board manifest flipnclickmz.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:flipnclickmz]
platform = microchippic32
board = flipnclickmz
; change microcontroller
board_build.mcu = 32MZ2048EFH100
; change MCU frequency
board_build.f_cpu = 252000000L


PIO Unified Debugger currently does not support MikroElektronika Flip N Click MZ board.

Name Description
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.

•
Mini 2.0
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX270F256D
Frequency 48MHz
Flash 240KB
RAM 62KB
Vendor Fubarino

Please use fubarino_mini_20 ID for board option in "platformio.ini" (Project Configuration File):

[env:fubarino_mini_20]
platform = microchippic32
board = fubarino_mini_20


You can override default Mini 2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest fubarino_mini_20.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:fubarino_mini_20]
platform = microchippic32
board = fubarino_mini_20
; change microcontroller
board_build.mcu = 32MX270F256D
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support Mini 2.0 board.

Name Description
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.

•
Olimex PIC32-PINGUINO
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX440F256H
Frequency 80MHz
Flash 252KB
RAM 32KB
Vendor Olimex

Please use pinguino32 ID for board option in "platformio.ini" (Project Configuration File):

[env:pinguino32]
platform = microchippic32
board = pinguino32


You can override default Olimex PIC32-PINGUINO settings per build environment using board_*** option, where *** is a JSON object path from board manifest pinguino32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:pinguino32]
platform = microchippic32
board = pinguino32
; change microcontroller
board_build.mcu = 32MX440F256H
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Olimex PIC32-PINGUINO board.

Name Description
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.

•
OpenBCI 32bit
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX250F128B
Frequency 40MHz
Flash 120KB
RAM 32KB
Vendor OpenBCI

Please use openbci ID for board option in "platformio.ini" (Project Configuration File):

[env:openbci]
platform = microchippic32
board = openbci


You can override default OpenBCI 32bit settings per build environment using board_*** option, where *** is a JSON object path from board manifest openbci.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:openbci]
platform = microchippic32
board = openbci
; change microcontroller
board_build.mcu = 32MX250F128B
; change MCU frequency
board_build.f_cpu = 40000000L


PIO Unified Debugger currently does not support OpenBCI 32bit board.

Name Description
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.

•
PONTECH UAV100
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX440F512H
Frequency 80MHz
Flash 508KB
RAM 32KB
Vendor PONTECH

Please use usbono_pic32 ID for board option in "platformio.ini" (Project Configuration File):

[env:usbono_pic32]
platform = microchippic32
board = usbono_pic32


You can override default PONTECH UAV100 settings per build environment using board_*** option, where *** is a JSON object path from board manifest usbono_pic32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:usbono_pic32]
platform = microchippic32
board = usbono_pic32
; change microcontroller
board_build.mcu = 32MX440F512H
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support PONTECH UAV100 board.

Name Description
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.

•
Pic32 CUI32-Development Stick
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX440F512H
Frequency 80MHz
Flash 508KB
RAM 32KB
Vendor SparkFun

Please use cui32 ID for board option in "platformio.ini" (Project Configuration File):

[env:cui32]
platform = microchippic32
board = cui32


You can override default Pic32 CUI32-Development Stick settings per build environment using board_*** option, where *** is a JSON object path from board manifest cui32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:cui32]
platform = microchippic32
board = cui32
; change microcontroller
board_build.mcu = 32MX440F512H
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Pic32 CUI32-Development Stick board.

Name Description
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.

•
Pontech NoFire
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MZ2048EFG100
Frequency 200MHz
Flash 1.98MB
RAM 512KB
Vendor Pontech

Please use nofire ID for board option in "platformio.ini" (Project Configuration File):

[env:nofire]
platform = microchippic32
board = nofire


You can override default Pontech NoFire settings per build environment using board_*** option, where *** is a JSON object path from board manifest nofire.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nofire]
platform = microchippic32
board = nofire
; change microcontroller
board_build.mcu = 32MZ2048EFG100
; change MCU frequency
board_build.f_cpu = 200000000L


PIO Unified Debugger currently does not support Pontech NoFire board.

Name Description
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.

•
Pontech Quick240
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 Pontech

Please use quick240_usb ID for board option in "platformio.ini" (Project Configuration File):

[env:quick240_usb]
platform = microchippic32
board = quick240_usb


You can override default Pontech Quick240 settings per build environment using board_*** option, where *** is a JSON object path from board manifest quick240_usb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:quick240_usb]
platform = microchippic32
board = quick240_usb
; change microcontroller
board_build.mcu = 32MX795F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support Pontech Quick240 board.

Name Description
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.

•
RGB Station
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX270F256D
Frequency 48MHz
Flash 240KB
RAM 62KB
Vendor ChipKIT

Please use rgb_station ID for board option in "platformio.ini" (Project Configuration File):

[env:rgb_station]
platform = microchippic32
board = rgb_station


You can override default RGB Station settings per build environment using board_*** option, where *** is a JSON object path from board manifest rgb_station.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:rgb_station]
platform = microchippic32
board = rgb_station
; change microcontroller
board_build.mcu = 32MX270F256D
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support RGB Station board.

Name Description
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.

•
SeeedStudio CUI32stem
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX795F512H
Frequency 80MHz
Flash 508KB
RAM 128KB
Vendor SeeedStudio

Please use cui32stem ID for board option in "platformio.ini" (Project Configuration File):

[env:cui32stem]
platform = microchippic32
board = cui32stem


You can override default SeeedStudio CUI32stem settings per build environment using board_*** option, where *** is a JSON object path from board manifest cui32stem.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:cui32stem]
platform = microchippic32
board = cui32stem
; change microcontroller
board_build.mcu = 32MX795F512H
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support SeeedStudio CUI32stem board.

Name Description
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.

•
UBW32 MX460
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX460F512L
Frequency 80MHz
Flash 508KB
RAM 32KB
Vendor UBW32

Please use ubw32_mx460 ID for board option in "platformio.ini" (Project Configuration File):

[env:ubw32_mx460]
platform = microchippic32
board = ubw32_mx460


You can override default UBW32 MX460 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ubw32_mx460.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ubw32_mx460]
platform = microchippic32
board = ubw32_mx460
; change microcontroller
board_build.mcu = 32MX460F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support UBW32 MX460 board.

Name Description
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.

•
UBW32 MX795
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 UBW32

Please use ubw32_mx795 ID for board option in "platformio.ini" (Project Configuration File):

[env:ubw32_mx795]
platform = microchippic32
board = ubw32_mx795


You can override default UBW32 MX795 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ubw32_mx795.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ubw32_mx795]
platform = microchippic32
board = ubw32_mx795
; change microcontroller
board_build.mcu = 32MX795F512L
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger currently does not support UBW32 MX795 board.

Name Description
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.

•
chipKIT Lenny
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MX270F256D
Frequency 40MHz
Flash 120KB
RAM 32KB
Vendor chipKIT

Please use lenny ID for board option in "platformio.ini" (Project Configuration File):

[env:lenny]
platform = microchippic32
board = lenny


You can override default chipKIT Lenny settings per build environment using board_*** option, where *** is a JSON object path from board manifest lenny.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lenny]
platform = microchippic32
board = lenny
; change microcontroller
board_build.mcu = 32MX270F256D
; change MCU frequency
board_build.f_cpu = 40000000L


PIO Unified Debugger currently does not support chipKIT Lenny board.

Name Description
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.

•
chipKIT WiFire rev. C
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Microchip PIC32: 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 32MZ2048EFG100
Frequency 200MHz
Flash 1.98MB
RAM 512KB
Vendor Digilent

Please use chipkit_wifire_revc ID for board option in "platformio.ini" (Project Configuration File):

[env:chipkit_wifire_revc]
platform = microchippic32
board = chipkit_wifire_revc


You can override default chipKIT WiFire rev. C settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_wifire_revc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:chipkit_wifire_revc]
platform = microchippic32
board = chipkit_wifire_revc
; change microcontroller
board_build.mcu = 32MZ2048EFG100
; change MCU frequency
board_build.f_cpu = 200000000L


PIO Unified Debugger currently does not support chipKIT WiFire rev. C board.

Name Description
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.

Nordic nRF51

•
BBC micro:bit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 256KB
RAM 16KB
Vendor BBC

Please use bbcmicrobit ID for board option in "platformio.ini" (Project Configuration File):

[env:bbcmicrobit]
platform = nordicnrf51
board = bbcmicrobit


You can override default BBC micro:bit settings per build environment using board_*** option, where *** is a JSON object path from board manifest bbcmicrobit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:bbcmicrobit]
platform = nordicnrf51
board = bbcmicrobit
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


BBC micro:bit supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:bbcmicrobit]
platform = nordicnrf51
board = bbcmicrobit
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BBC micro:bit 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
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.
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.

•
BluzDK
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor BluzDK

Please use bluz_dk ID for board option in "platformio.ini" (Project Configuration File):

[env:bluz_dk]
platform = nordicnrf51
board = bluz_dk


You can override default BluzDK settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluz_dk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:bluz_dk]
platform = nordicnrf51
board = bluz_dk
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 32000000L


BluzDK supports the next uploading protocols:

  • blackmagic
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:bluz_dk]
platform = nordicnrf51
board = bluz_dk
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BluzDK 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.

•
Calliope mini
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 256KB
RAM 16KB
Vendor Calliope

Please use calliope_mini ID for board option in "platformio.ini" (Project Configuration File):

[env:calliope_mini]
platform = nordicnrf51
board = calliope_mini


You can override default Calliope mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest calliope_mini.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:calliope_mini]
platform = nordicnrf51
board = calliope_mini
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


Calliope mini supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:calliope_mini]
platform = nordicnrf51
board = calliope_mini
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Calliope mini 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

Delta DFCM-NNN40

•
Delta DFCM-NNN40
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor Delta

Please use dfcm_nnn40 ID for board option in "platformio.ini" (Project Configuration File):

[env:dfcm_nnn40]
platform = nordicnrf51
board = dfcm_nnn40


You can override default Delta DFCM-NNN40 settings per build environment using board_*** option, where *** is a JSON object path from board manifest dfcm_nnn40.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:dfcm_nnn40]
platform = nordicnrf51
board = dfcm_nnn40
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 32000000L


Delta DFCM-NNN40 supports the next uploading protocols:

  • cmsis-dap
  • mbed

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:dfcm_nnn40]
platform = nordicnrf51
board = dfcm_nnn40
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Delta DFCM-NNN40 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
CMSIS-DAP Yes Yes

Name Description
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.

Delta DFCM-NNN50

•
Delta DFCM-NNN50
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 32MHz
Flash 256KB
RAM 16KB
Vendor Delta

Please use delta_dfcm_nnn50 ID for board option in "platformio.ini" (Project Configuration File):

[env:delta_dfcm_nnn50]
platform = nordicnrf51
board = delta_dfcm_nnn50


You can override default Delta DFCM-NNN50 settings per build environment using board_*** option, where *** is a JSON object path from board manifest delta_dfcm_nnn50.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:delta_dfcm_nnn50]
platform = nordicnrf51
board = delta_dfcm_nnn50
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 32000000L


Delta DFCM-NNN50 supports the next uploading protocols:

  • cmsis-dap
  • mbed

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:delta_dfcm_nnn50]
platform = nordicnrf51
board = delta_dfcm_nnn50
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Delta DFCM-NNN50 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
CMSIS-DAP Yes Yes

Name Description
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.

•
JKSoft Wallbot BLE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 128KB
RAM 16KB
Vendor JKSoft

Please use wallbot_ble ID for board option in "platformio.ini" (Project Configuration File):

[env:wallbot_ble]
platform = nordicnrf51
board = wallbot_ble


You can override default JKSoft Wallbot BLE settings per build environment using board_*** option, where *** is a JSON object path from board manifest wallbot_ble.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wallbot_ble]
platform = nordicnrf51
board = wallbot_ble
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


JKSoft Wallbot BLE supports the next uploading protocols:

  • cmsis-dap
  • mbed

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:wallbot_ble]
platform = nordicnrf51
board = wallbot_ble
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

JKSoft Wallbot BLE 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
CMSIS-DAP Yes Yes

Name Description
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.

•
Nordic Beacon Kit (PCA20006)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor Nordic

Please use nrf51_beacon ID for board option in "platformio.ini" (Project Configuration File):

[env:nrf51_beacon]
platform = nordicnrf51
board = nrf51_beacon


You can override default Nordic Beacon Kit (PCA20006) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf51_beacon.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nrf51_beacon]
platform = nordicnrf51
board = nrf51_beacon
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 32000000L


Nordic Beacon Kit (PCA20006) supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:nrf51_beacon]
platform = nordicnrf51
board = nrf51_beacon
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nordic Beacon Kit (PCA20006) 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
Black Magic Probe
CMSIS-DAP Yes
J-LINK Yes Yes
ST-LINK

Name Description
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.

•
Nordic nRF51 Dongle (PCA10031)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor Nordic

Please use nrf51_dongle ID for board option in "platformio.ini" (Project Configuration File):

[env:nrf51_dongle]
platform = nordicnrf51
board = nrf51_dongle


You can override default Nordic nRF51 Dongle (PCA10031) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf51_dongle.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nrf51_dongle]
platform = nordicnrf51
board = nrf51_dongle
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 32000000L


Nordic nRF51 Dongle (PCA10031) supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:nrf51_dongle]
platform = nordicnrf51
board = nrf51_dongle
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nordic nRF51 Dongle (PCA10031) 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
CMSIS-DAP Yes
J-LINK Yes Yes

Name Description
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.
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.
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.

•
Nordic nRF51822-mKIT
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 128KB
RAM 16KB
Vendor Nordic

Please use nrf51_mkit ID for board option in "platformio.ini" (Project Configuration File):

[env:nrf51_mkit]
platform = nordicnrf51
board = nrf51_mkit


You can override default Nordic nRF51822-mKIT settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf51_mkit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nrf51_mkit]
platform = nordicnrf51
board = nrf51_mkit
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


Nordic nRF51822-mKIT supports the next uploading protocols:

  • cmsis-dap
  • mbed

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:nrf51_mkit]
platform = nordicnrf51
board = nrf51_mkit
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nordic nRF51822-mKIT 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
CMSIS-DAP Yes Yes

Name Description
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.

•
Nordic nRF51X22 Development Kit(PCA1000X)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor Nordic

Please use nrf51_dk ID for board option in "platformio.ini" (Project Configuration File):

[env:nrf51_dk]
platform = nordicnrf51
board = nrf51_dk


You can override default Nordic nRF51X22 Development Kit(PCA1000X) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf51_dk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nrf51_dk]
platform = nordicnrf51
board = nrf51_dk
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 32000000L


Nordic nRF51X22 Development Kit(PCA1000X) supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:nrf51_dk]
platform = nordicnrf51
board = nrf51_dk
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nordic nRF51X22 Development Kit(PCA1000X) 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
Black Magic Probe
CMSIS-DAP Yes
J-LINK Yes Yes
ST-LINK

Name Description
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.
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.
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.

•
OSHChip
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor OSHChip

Please use oshchip ID for board option in "platformio.ini" (Project Configuration File):

[env:oshchip]
platform = nordicnrf51
board = oshchip


You can override default OSHChip settings per build environment using board_*** option, where *** is a JSON object path from board manifest oshchip.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:oshchip]
platform = nordicnrf51
board = oshchip
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 32000000L


OSHChip supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:oshchip]
platform = nordicnrf51
board = oshchip
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

OSHChip 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.

•
RedBearLab BLE Nano 1.5
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 256KB
RAM 32KB
Vendor RedBearLab

Please use redBearLabBLENano ID for board option in "platformio.ini" (Project Configuration File):

[env:redBearLabBLENano]
platform = nordicnrf51
board = redBearLabBLENano


You can override default RedBearLab BLE Nano 1.5 settings per build environment using board_*** option, where *** is a JSON object path from board manifest redBearLabBLENano.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:redBearLabBLENano]
platform = nordicnrf51
board = redBearLabBLENano
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


RedBearLab BLE Nano 1.5 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:redBearLabBLENano]
platform = nordicnrf51
board = redBearLabBLENano
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RedBearLab BLE Nano 1.5 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
RedBearLab nRF51822
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 256KB
RAM 16KB
Vendor RedBearLab

Please use redBearLab ID for board option in "platformio.ini" (Project Configuration File):

[env:redBearLab]
platform = nordicnrf51
board = redBearLab


You can override default RedBearLab nRF51822 settings per build environment using board_*** option, where *** is a JSON object path from board manifest redBearLab.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:redBearLab]
platform = nordicnrf51
board = redBearLab
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


RedBearLab nRF51822 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:redBearLab]
platform = nordicnrf51
board = redBearLab
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RedBearLab nRF51822 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
Seeed Arch BLE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 128KB
RAM 16KB
Vendor SeeedStudio

Please use seeedArchBLE ID for board option in "platformio.ini" (Project Configuration File):

[env:seeedArchBLE]
platform = nordicnrf51
board = seeedArchBLE


You can override default Seeed Arch BLE settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeedArchBLE.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:seeedArchBLE]
platform = nordicnrf51
board = seeedArchBLE
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


Seeed Arch BLE supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:seeedArchBLE]
platform = nordicnrf51
board = seeedArchBLE
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Seeed Arch BLE 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.

•
Seeed Arch Link
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 256KB
RAM 16KB
Vendor SeeedStudio

Please use seeedArchLink ID for board option in "platformio.ini" (Project Configuration File):

[env:seeedArchLink]
platform = nordicnrf51
board = seeedArchLink


You can override default Seeed Arch Link settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeedArchLink.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:seeedArchLink]
platform = nordicnrf51
board = seeedArchLink
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


Seeed Arch Link supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:seeedArchLink]
platform = nordicnrf51
board = seeedArchLink
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Seeed Arch Link 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.

•
Seeed Tiny BLE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 256KB
RAM 16KB
Vendor SeeedStudio

Please use seeedTinyBLE ID for board option in "platformio.ini" (Project Configuration File):

[env:seeedTinyBLE]
platform = nordicnrf51
board = seeedTinyBLE


You can override default Seeed Tiny BLE settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeedTinyBLE.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:seeedTinyBLE]
platform = nordicnrf51
board = seeedTinyBLE
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


Seeed Tiny BLE supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:seeedTinyBLE]
platform = nordicnrf51
board = seeedTinyBLE
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Seeed Tiny BLE 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
Sino:Bit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor sino:bit

Please use Sinobit ID for board option in "platformio.ini" (Project Configuration File):

[env:Sinobit]
platform = nordicnrf51
board = Sinobit


You can override default Sino:Bit settings per build environment using board_*** option, where *** is a JSON object path from board manifest Sinobit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:Sinobit]
platform = nordicnrf51
board = Sinobit
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 32000000L


Sino:Bit supports the next uploading protocols:

  • blackmagic
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:Sinobit]
platform = nordicnrf51
board = Sinobit
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Sino: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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.

•
Switch Science mbed HRM1017
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 256KB
RAM 16KB
Vendor Switch Science

Please use hrm1017 ID for board option in "platformio.ini" (Project Configuration File):

[env:hrm1017]
platform = nordicnrf51
board = hrm1017


You can override default Switch Science mbed HRM1017 settings per build environment using board_*** option, where *** is a JSON object path from board manifest hrm1017.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:hrm1017]
platform = nordicnrf51
board = hrm1017
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


Switch Science mbed HRM1017 supports the next uploading protocols:

  • cmsis-dap
  • mbed

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:hrm1017]
platform = nordicnrf51
board = hrm1017
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Switch Science mbed HRM1017 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
CMSIS-DAP Yes Yes

Name Description
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.

•
Switch Science mbed TY51822r3
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor Switch Science

Please use ty51822r3 ID for board option in "platformio.ini" (Project Configuration File):

[env:ty51822r3]
platform = nordicnrf51
board = ty51822r3


You can override default Switch Science mbed TY51822r3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ty51822r3.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ty51822r3]
platform = nordicnrf51
board = ty51822r3
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 32000000L


Switch Science mbed TY51822r3 supports the next uploading protocols:

  • cmsis-dap
  • mbed

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:ty51822r3]
platform = nordicnrf51
board = ty51822r3
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Switch Science mbed TY51822r3 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
CMSIS-DAP Yes Yes

Name Description
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.

•
VNG VBLUNO51
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 128KB
RAM 32KB
Vendor VNG

Please use vbluno51 ID for board option in "platformio.ini" (Project Configuration File):

[env:vbluno51]
platform = nordicnrf51
board = vbluno51


You can override default VNG VBLUNO51 settings per build environment using board_*** option, where *** is a JSON object path from board manifest vbluno51.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:vbluno51]
platform = nordicnrf51
board = vbluno51
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


VNG VBLUNO51 supports the next uploading protocols:

  • cmsis-dap
  • mbed

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:vbluno51]
platform = nordicnrf51
board = vbluno51
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

VNG VBLUNO51 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
CMSIS-DAP Yes Yes

Name Description
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.
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.

•
Waveshare BLE400
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor Waveshare

Please use waveshare_ble400 ID for board option in "platformio.ini" (Project Configuration File):

[env:waveshare_ble400]
platform = nordicnrf51
board = waveshare_ble400


You can override default Waveshare BLE400 settings per build environment using board_*** option, where *** is a JSON object path from board manifest waveshare_ble400.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:waveshare_ble400]
platform = nordicnrf51
board = waveshare_ble400
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 32000000L


Waveshare BLE400 supports the next uploading protocols:

  • blackmagic
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:waveshare_ble400]
platform = nordicnrf51
board = waveshare_ble400
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Waveshare BLE400 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
ng-beacon
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 256KB
RAM 32KB
Vendor ng-beacon

Please use ng_beacon ID for board option in "platformio.ini" (Project Configuration File):

[env:ng_beacon]
platform = nordicnrf51
board = ng_beacon


You can override default ng-beacon settings per build environment using board_*** option, where *** is a JSON object path from board manifest ng_beacon.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ng_beacon]
platform = nordicnrf51
board = ng_beacon
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


ng-beacon supports the next uploading protocols:

  • blackmagic
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:ng_beacon]
platform = nordicnrf51
board = ng_beacon
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ng-beacon 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.

•
y5 nRF51822 mbug
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.

Microcontroller NRF51822
Frequency 16MHz
Flash 256KB
RAM 16KB
Vendor y5 design

Please use nrf51822_y5_mbug ID for board option in "platformio.ini" (Project Configuration File):

[env:nrf51822_y5_mbug]
platform = nordicnrf51
board = nrf51822_y5_mbug


You can override default y5 nRF51822 mbug settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf51822_y5_mbug.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nrf51822_y5_mbug]
platform = nordicnrf51
board = nrf51822_y5_mbug
; change microcontroller
board_build.mcu = nrf51822
; change MCU frequency
board_build.f_cpu = 16000000L


y5 nRF51822 mbug supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:nrf51822_y5_mbug]
platform = nordicnrf51
board = nrf51822_y5_mbug
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

y5 nRF51822 mbug 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.

Nordic nRF52

•
96Boards Nitrogen
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor 96Boards

Please use 96b_nitrogen ID for board option in "platformio.ini" (Project Configuration File):

[env:96b_nitrogen]
platform = nordicnrf52
board = 96b_nitrogen


You can override default 96Boards Nitrogen settings per build environment using board_*** option, where *** is a JSON object path from board manifest 96b_nitrogen.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:96b_nitrogen]
platform = nordicnrf52
board = 96b_nitrogen
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


96Boards Nitrogen supports the next uploading protocols:

  • blackmagic
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:96b_nitrogen]
platform = nordicnrf52
board = 96b_nitrogen
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

96Boards Nitrogen 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.

•
Adafruit Bluefruit nRF52832 Feather
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Adafruit

Please use adafruit_feather_nrf52832 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_feather_nrf52832]
platform = nordicnrf52
board = adafruit_feather_nrf52832


You can override default Adafruit Bluefruit nRF52832 Feather settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_nrf52832.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_feather_nrf52832]
platform = nordicnrf52
board = adafruit_feather_nrf52832
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


Adafruit Bluefruit nRF52832 Feather supports the next uploading protocols:

  • jlink
  • nrfjprog
  • nrfutil
  • stlink

Default protocol is nrfutil

You can change upload protocol using upload_protocol option:

[env:adafruit_feather_nrf52832]
platform = nordicnrf52
board = adafruit_feather_nrf52832
upload_protocol = nrfutil


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Bluefruit nRF52832 Feather 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
J-LINK Yes
ST-LINK

Name Description
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.
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.

•
Adafruit Feather Bluefruit Sense
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 796KB
RAM 243KB
Vendor Adafruit

Please use adafruit_feather_nrf52840_sense ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_feather_nrf52840_sense]
platform = nordicnrf52
board = adafruit_feather_nrf52840_sense


You can override default Adafruit Feather Bluefruit Sense settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_nrf52840_sense.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_feather_nrf52840_sense]
platform = nordicnrf52
board = adafruit_feather_nrf52840_sense
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Adafruit Feather Bluefruit Sense supports the next uploading protocols:

  • jlink
  • nrfjprog
  • nrfutil
  • stlink

Default protocol is nrfutil

You can change upload protocol using upload_protocol option:

[env:adafruit_feather_nrf52840_sense]
platform = nordicnrf52
board = adafruit_feather_nrf52840_sense
upload_protocol = nrfutil


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Feather Bluefruit Sense 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
J-LINK Yes
ST-LINK

Name Description
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.

•
Adafruit Feather nRF52840 Express
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 796KB
RAM 243KB
Vendor Adafruit

Please use adafruit_feather_nrf52840 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_feather_nrf52840]
platform = nordicnrf52
board = adafruit_feather_nrf52840


You can override default Adafruit Feather nRF52840 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_nrf52840.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_feather_nrf52840]
platform = nordicnrf52
board = adafruit_feather_nrf52840
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Adafruit Feather nRF52840 Express supports the next uploading protocols:

  • jlink
  • nrfjprog
  • nrfutil
  • stlink

Default protocol is nrfutil

You can change upload protocol using upload_protocol option:

[env:adafruit_feather_nrf52840]
platform = nordicnrf52
board = adafruit_feather_nrf52840
upload_protocol = nrfutil


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Feather nRF52840 Express 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
J-LINK Yes
ST-LINK

Name Description
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.

•
Arduino Nano 33 BLE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 960KB
RAM 256KB
Vendor Arduino

Please use nano33ble ID for board option in "platformio.ini" (Project Configuration File):

[env:nano33ble]
platform = nordicnrf52
board = nano33ble


You can override default Arduino Nano 33 BLE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nano33ble.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nano33ble]
platform = nordicnrf52
board = nano33ble
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Arduino Nano 33 BLE supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • nrfjprog
  • nrfutil
  • sam-ba

Default protocol is sam-ba

You can change upload protocol using upload_protocol option:

[env:nano33ble]
platform = nordicnrf52
board = nano33ble
upload_protocol = sam-ba


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Arduino Nano 33 BLE 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
CMSIS-DAP Yes
J-LINK

Name Description
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.

•
BL652 Development Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Laird Connectivity

Please use laird_bl652_dvk ID for board option in "platformio.ini" (Project Configuration File):

[env:laird_bl652_dvk]
platform = nordicnrf52
board = laird_bl652_dvk


You can override default BL652 Development Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest laird_bl652_dvk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:laird_bl652_dvk]
platform = nordicnrf52
board = laird_bl652_dvk
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


BL652 Development Kit supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:laird_bl652_dvk]
platform = nordicnrf52
board = laird_bl652_dvk
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BL652 Development 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
Black Magic Probe
CMSIS-DAP Yes
J-LINK Yes Yes
ST-LINK

Name Description
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.

•
BL654 Development Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 1MB
RAM 256KB
Vendor Laird Connectivity

Please use laird_bl654_dvk ID for board option in "platformio.ini" (Project Configuration File):

[env:laird_bl654_dvk]
platform = nordicnrf52
board = laird_bl654_dvk


You can override default BL654 Development Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest laird_bl654_dvk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:laird_bl654_dvk]
platform = nordicnrf52
board = laird_bl654_dvk
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


BL654 Development Kit supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:laird_bl654_dvk]
platform = nordicnrf52
board = laird_bl654_dvk
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BL654 Development 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
Black Magic Probe
CMSIS-DAP Yes
J-LINK Yes Yes
ST-LINK

Name Description
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.

•
Bluey nRF52832 IoT
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Electronut Labs

Please use bluey ID for board option in "platformio.ini" (Project Configuration File):

[env:bluey]
platform = nordicnrf52
board = bluey


You can override default Bluey nRF52832 IoT settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluey.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:bluey]
platform = nordicnrf52
board = bluey
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


Bluey nRF52832 IoT supports the next uploading protocols:

  • blackmagic
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:bluey]
platform = nordicnrf52
board = bluey
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Bluey nRF52832 IoT 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.

•
Circuit Playground Bluefruit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 796KB
RAM 243KB
Vendor Adafruit

Please use adafruit_cplaynrf52840 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_cplaynrf52840]
platform = nordicnrf52
board = adafruit_cplaynrf52840


You can override default Circuit Playground Bluefruit settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_cplaynrf52840.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_cplaynrf52840]
platform = nordicnrf52
board = adafruit_cplaynrf52840
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Circuit Playground Bluefruit supports the next uploading protocols:

  • jlink
  • nrfjprog
  • nrfutil
  • stlink

Default protocol is nrfutil

You can change upload protocol using upload_protocol option:

[env:adafruit_cplaynrf52840]
platform = nordicnrf52
board = adafruit_cplaynrf52840
upload_protocol = nrfutil


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Circuit Playground Bluefruit 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
J-LINK Yes
ST-LINK

Name Description
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.

•
Delta DFBM-NQ620
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Delta

Please use delta_dfbm_nq620 ID for board option in "platformio.ini" (Project Configuration File):

[env:delta_dfbm_nq620]
platform = nordicnrf52
board = delta_dfbm_nq620


You can override default Delta DFBM-NQ620 settings per build environment using board_*** option, where *** is a JSON object path from board manifest delta_dfbm_nq620.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:delta_dfbm_nq620]
platform = nordicnrf52
board = delta_dfbm_nq620
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


Delta DFBM-NQ620 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:delta_dfbm_nq620]
platform = nordicnrf52
board = delta_dfbm_nq620
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Delta DFBM-NQ620 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
ElectronutLabs Blip
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 1MB
RAM 256KB
Vendor ElectronutLabs

Please use electronut_blip ID for board option in "platformio.ini" (Project Configuration File):

[env:electronut_blip]
platform = nordicnrf52
board = electronut_blip


You can override default ElectronutLabs Blip settings per build environment using board_*** option, where *** is a JSON object path from board manifest electronut_blip.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:electronut_blip]
platform = nordicnrf52
board = electronut_blip
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


ElectronutLabs Blip supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • nrfjprog
  • stlink

Default protocol is blackmagic

You can change upload protocol using upload_protocol option:

[env:electronut_blip]
platform = nordicnrf52
board = electronut_blip
upload_protocol = blackmagic


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ElectronutLabs Blip 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
Black Magic Probe Yes Yes
CMSIS-DAP
J-LINK
ST-LINK

Name Description
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.

•
ElectronutLabs Papyr
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 1MB
RAM 256KB
Vendor ElectronutLabs

Please use electronut_papyr ID for board option in "platformio.ini" (Project Configuration File):

[env:electronut_papyr]
platform = nordicnrf52
board = electronut_papyr


You can override default ElectronutLabs Papyr settings per build environment using board_*** option, where *** is a JSON object path from board manifest electronut_papyr.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:electronut_papyr]
platform = nordicnrf52
board = electronut_papyr
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


ElectronutLabs Papyr supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • nrfjprog
  • stlink

Default protocol is blackmagic

You can change upload protocol using upload_protocol option:

[env:electronut_papyr]
platform = nordicnrf52
board = electronut_papyr
upload_protocol = blackmagic


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ElectronutLabs Papyr 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
Black Magic Probe Yes Yes
CMSIS-DAP
J-LINK
ST-LINK

Name Description
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.

•
Holyiot YJ-16019
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Holyiot

Please use holyiot_yj16019 ID for board option in "platformio.ini" (Project Configuration File):

[env:holyiot_yj16019]
platform = nordicnrf52
board = holyiot_yj16019


You can override default Holyiot YJ-16019 settings per build environment using board_*** option, where *** is a JSON object path from board manifest holyiot_yj16019.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:holyiot_yj16019]
platform = nordicnrf52
board = holyiot_yj16019
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


Holyiot YJ-16019 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:holyiot_yj16019]
platform = nordicnrf52
board = holyiot_yj16019
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Holyiot YJ-16019 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
Black Magic Probe Yes
CMSIS-DAP
J-LINK
ST-LINK

Name Description
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.

•
ItsyBitsy nRF52840 Express
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 796KB
RAM 243KB
Vendor Adafruit

Please use adafruit_itsybitsy_nrf52840 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_itsybitsy_nrf52840]
platform = nordicnrf52
board = adafruit_itsybitsy_nrf52840


You can override default ItsyBitsy nRF52840 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_itsybitsy_nrf52840.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_itsybitsy_nrf52840]
platform = nordicnrf52
board = adafruit_itsybitsy_nrf52840
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


ItsyBitsy nRF52840 Express supports the next uploading protocols:

  • jlink
  • nrfjprog
  • nrfutil
  • stlink

Default protocol is nrfutil

You can change upload protocol using upload_protocol option:

[env:adafruit_itsybitsy_nrf52840]
platform = nordicnrf52
board = adafruit_itsybitsy_nrf52840
upload_protocol = nrfutil


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ItsyBitsy nRF52840 Express 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
J-LINK Yes Yes
ST-LINK

Name Description
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.

•
Makerdiary nRF52832-MDK
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Makerdiary

Please use nrf52832_mdk ID for board option in "platformio.ini" (Project Configuration File):

[env:nrf52832_mdk]
platform = nordicnrf52
board = nrf52832_mdk


You can override default Makerdiary nRF52832-MDK settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf52832_mdk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nrf52832_mdk]
platform = nordicnrf52
board = nrf52832_mdk
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


Makerdiary nRF52832-MDK supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:nrf52832_mdk]
platform = nordicnrf52
board = nrf52832_mdk
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Makerdiary nRF52832-MDK 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.

•
Makerdiary nRF52840-MDK
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 1MB
RAM 256KB
Vendor Makerdiary

Please use nrf52840_mdk ID for board option in "platformio.ini" (Project Configuration File):

[env:nrf52840_mdk]
platform = nordicnrf52
board = nrf52840_mdk


You can override default Makerdiary nRF52840-MDK settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf52840_mdk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nrf52840_mdk]
platform = nordicnrf52
board = nrf52840_mdk
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Makerdiary nRF52840-MDK supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:nrf52840_mdk]
platform = nordicnrf52
board = nrf52840_mdk
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Makerdiary nRF52840-MDK 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.

•
Metro nRF52840 Express
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 796KB
RAM 243KB
Vendor Adafruit

Please use adafruit_metro_nrf52840 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_metro_nrf52840]
platform = nordicnrf52
board = adafruit_metro_nrf52840


You can override default Metro nRF52840 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_metro_nrf52840.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_metro_nrf52840]
platform = nordicnrf52
board = adafruit_metro_nrf52840
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Metro nRF52840 Express supports the next uploading protocols:

  • jlink
  • nrfjprog
  • nrfutil
  • stlink

Default protocol is nrfutil

You can change upload protocol using upload_protocol option:

[env:adafruit_metro_nrf52840]
platform = nordicnrf52
board = adafruit_metro_nrf52840
upload_protocol = nrfutil


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Metro nRF52840 Express 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
J-LINK Yes
ST-LINK

Name Description
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.

•
Nordic Thingy:52 (nRF52-PCA20020)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Nordic

Please use thingy_52 ID for board option in "platformio.ini" (Project Configuration File):

[env:thingy_52]
platform = nordicnrf52
board = thingy_52


You can override default Nordic Thingy:52 (nRF52-PCA20020) settings per build environment using board_*** option, where *** is a JSON object path from board manifest thingy_52.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:thingy_52]
platform = nordicnrf52
board = thingy_52
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


Nordic Thingy:52 (nRF52-PCA20020) supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:thingy_52]
platform = nordicnrf52
board = thingy_52
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nordic Thingy:52 (nRF52-PCA20020) 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
Black Magic Probe Yes
CMSIS-DAP
J-LINK
ST-LINK

Name Description
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.

Nordic nRF52-DK

•
Nordic nRF52-DK
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Nordic

Please use nrf52_dk ID for board option in "platformio.ini" (Project Configuration File):

[env:nrf52_dk]
platform = nordicnrf52
board = nrf52_dk


You can override default Nordic nRF52-DK settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf52_dk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nrf52_dk]
platform = nordicnrf52
board = nrf52_dk
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


Nordic nRF52-DK supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:nrf52_dk]
platform = nordicnrf52
board = nrf52_dk
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nordic nRF52-DK 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
Black Magic Probe
CMSIS-DAP Yes
J-LINK Yes Yes
ST-LINK

Name Description
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.
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.
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.

Nordic nRF52840-DK

•
Nordic nRF52840-DK
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 1MB
RAM 256KB
Vendor Nordic

Please use nrf52840_dk ID for board option in "platformio.ini" (Project Configuration File):

[env:nrf52840_dk]
platform = nordicnrf52
board = nrf52840_dk


You can override default Nordic nRF52840-DK settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf52840_dk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nrf52840_dk]
platform = nordicnrf52
board = nrf52840_dk
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Nordic nRF52840-DK supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:nrf52840_dk]
platform = nordicnrf52
board = nrf52840_dk
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nordic nRF52840-DK 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
Black Magic Probe
CMSIS-DAP Yes
J-LINK Yes Yes
ST-LINK

Name Description
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.
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.
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.

Nordic nRF52840-DK (Adafruit BSP)

•
Nordic nRF52840-DK (Adafruit BSP)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 796KB
RAM 243KB
Vendor Nordic

Please use nrf52840_dk_adafruit ID for board option in "platformio.ini" (Project Configuration File):

[env:nrf52840_dk_adafruit]
platform = nordicnrf52
board = nrf52840_dk_adafruit


You can override default Nordic nRF52840-DK (Adafruit BSP) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf52840_dk_adafruit.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nrf52840_dk_adafruit]
platform = nordicnrf52
board = nrf52840_dk_adafruit
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Nordic nRF52840-DK (Adafruit BSP) supports the next uploading protocols:

  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:nrf52840_dk_adafruit]
platform = nordicnrf52
board = nrf52840_dk_adafruit
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nordic nRF52840-DK (Adafruit BSP) 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
J-LINK Yes Yes
ST-LINK

Name Description
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.

•
Particle Argon
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 796KB
RAM 243KB
Vendor Particle

Please use particle_argon ID for board option in "platformio.ini" (Project Configuration File):

[env:particle_argon]
platform = nordicnrf52
board = particle_argon


You can override default Particle Argon settings per build environment using board_*** option, where *** is a JSON object path from board manifest particle_argon.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:particle_argon]
platform = nordicnrf52
board = particle_argon
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Particle Argon supports the next uploading protocols:

  • jlink
  • nrfjprog
  • nrfutil

Default protocol is nrfutil

You can change upload protocol using upload_protocol option:

[env:particle_argon]
platform = nordicnrf52
board = particle_argon
upload_protocol = nrfutil


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Particle Argon 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
J-LINK Yes

Name Description
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.

•
Particle Boron
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 796KB
RAM 243KB
Vendor Particle

Please use particle_boron ID for board option in "platformio.ini" (Project Configuration File):

[env:particle_boron]
platform = nordicnrf52
board = particle_boron


You can override default Particle Boron settings per build environment using board_*** option, where *** is a JSON object path from board manifest particle_boron.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:particle_boron]
platform = nordicnrf52
board = particle_boron
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Particle Boron supports the next uploading protocols:

  • jlink
  • nrfjprog
  • nrfutil

Default protocol is nrfutil

You can change upload protocol using upload_protocol option:

[env:particle_boron]
platform = nordicnrf52
board = particle_boron
upload_protocol = nrfutil


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Particle Boron 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
J-LINK Yes

Name Description
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.

•
Particle Xenon
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52840
Frequency 64MHz
Flash 796KB
RAM 243KB
Vendor Particle

Please use particle_xenon ID for board option in "platformio.ini" (Project Configuration File):

[env:particle_xenon]
platform = nordicnrf52
board = particle_xenon


You can override default Particle Xenon settings per build environment using board_*** option, where *** is a JSON object path from board manifest particle_xenon.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:particle_xenon]
platform = nordicnrf52
board = particle_xenon
; change microcontroller
board_build.mcu = nrf52840
; change MCU frequency
board_build.f_cpu = 64000000L


Particle Xenon supports the next uploading protocols:

  • jlink
  • nrfjprog
  • nrfutil
  • stlink

Default protocol is nrfutil

You can change upload protocol using upload_protocol option:

[env:particle_xenon]
platform = nordicnrf52
board = particle_xenon
upload_protocol = nrfutil


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Particle Xenon 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
J-LINK Yes
ST-LINK

Name Description
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.
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.

•
RedBearLab BLE Nano 2
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor RedBearLab

Please use redbear_blenano2 ID for board option in "platformio.ini" (Project Configuration File):

[env:redbear_blenano2]
platform = nordicnrf52
board = redbear_blenano2


You can override default RedBearLab BLE Nano 2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest redbear_blenano2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:redbear_blenano2]
platform = nordicnrf52
board = redbear_blenano2
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


RedBearLab BLE Nano 2 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:redbear_blenano2]
platform = nordicnrf52
board = redbear_blenano2
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RedBearLab BLE Nano 2 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
RedBearLab Blend 2
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor RedBearLab

Please use redbear_blend2 ID for board option in "platformio.ini" (Project Configuration File):

[env:redbear_blend2]
platform = nordicnrf52
board = redbear_blend2


You can override default RedBearLab Blend 2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest redbear_blend2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:redbear_blend2]
platform = nordicnrf52
board = redbear_blend2
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


RedBearLab Blend 2 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:redbear_blend2]
platform = nordicnrf52
board = redbear_blend2
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RedBearLab Blend 2 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.

•
SDT52832B
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Sigma Delta Technologies

Please use sdt52832b ID for board option in "platformio.ini" (Project Configuration File):

[env:sdt52832b]
platform = nordicnrf52
board = sdt52832b


You can override default SDT52832B settings per build environment using board_*** option, where *** is a JSON object path from board manifest sdt52832b.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sdt52832b]
platform = nordicnrf52
board = sdt52832b
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


SDT52832B supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:sdt52832b]
platform = nordicnrf52
board = sdt52832b
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SDT52832B 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
Black Magic Probe Yes
CMSIS-DAP
J-LINK
ST-LINK

Name Description
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.

•
Taida Century nRF52 mini board
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Taida Century

Please use stct_nrf52_minidev ID for board option in "platformio.ini" (Project Configuration File):

[env:stct_nrf52_minidev]
platform = nordicnrf52
board = stct_nrf52_minidev


You can override default Taida Century nRF52 mini board settings per build environment using board_*** option, where *** is a JSON object path from board manifest stct_nrf52_minidev.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:stct_nrf52_minidev]
platform = nordicnrf52
board = stct_nrf52_minidev
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


Taida Century nRF52 mini board supports the next uploading protocols:

  • blackmagic
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:stct_nrf52_minidev]
platform = nordicnrf52
board = stct_nrf52_minidev
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Taida Century nRF52 mini board 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.

•
VNG VBLUno52
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor VNG

Please use vbluno52 ID for board option in "platformio.ini" (Project Configuration File):

[env:vbluno52]
platform = nordicnrf52
board = vbluno52


You can override default VNG VBLUno52 settings per build environment using board_*** option, where *** is a JSON object path from board manifest vbluno52.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:vbluno52]
platform = nordicnrf52
board = vbluno52
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


VNG VBLUno52 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • nrfjprog
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:vbluno52]
platform = nordicnrf52
board = vbluno52
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

VNG VBLUno52 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.

•
hackaBLE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor Electronut Labs

Please use hackaBLE ID for board option in "platformio.ini" (Project Configuration File):

[env:hackaBLE]
platform = nordicnrf52
board = hackaBLE


You can override default hackaBLE settings per build environment using board_*** option, where *** is a JSON object path from board manifest hackaBLE.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:hackaBLE]
platform = nordicnrf52
board = hackaBLE
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


hackaBLE supports the next uploading protocols:

  • blackmagic
  • jlink
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:hackaBLE]
platform = nordicnrf52
board = hackaBLE
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

hackaBLE 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.

u-blox EVK-NINA-B1

•
u-blox EVK-NINA-B1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nordic nRF52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.

Microcontroller NRF52832
Frequency 64MHz
Flash 512KB
RAM 64KB
Vendor u-blox

Please use ublox_evk_nina_b1 ID for board option in "platformio.ini" (Project Configuration File):

[env:ublox_evk_nina_b1]
platform = nordicnrf52
board = ublox_evk_nina_b1


You can override default u-blox EVK-NINA-B1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ublox_evk_nina_b1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ublox_evk_nina_b1]
platform = nordicnrf52
board = ublox_evk_nina_b1
; change microcontroller
board_build.mcu = nrf52832
; change MCU frequency
board_build.f_cpu = 64000000L


u-blox EVK-NINA-B1 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • nrfjprog
  • stlink

Default protocol is jlink

You can change upload protocol using upload_protocol option:

[env:ublox_evk_nina_b1]
platform = nordicnrf52
board = ublox_evk_nina_b1
upload_protocol = jlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

u-blox EVK-NINA-B1 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
Black Magic Probe
J-LINK Yes Yes
ST-LINK

Name Description
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.
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.

•
GD32VF103V Evaluation Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nuclei: Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.

Microcontroller GD32VF103VBT6
Frequency 108MHz
Flash 128KB
RAM 32KB
Vendor GigaDevice

Please use gd32vf103v_eval ID for board option in "platformio.ini" (Project Configuration File):

[env:gd32vf103v_eval]
platform = nuclei
board = gd32vf103v_eval


You can override default GD32VF103V Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest gd32vf103v_eval.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:gd32vf103v_eval]
platform = nuclei
board = gd32vf103v_eval
; change microcontroller
board_build.mcu = gd32vf103vbt6
; change MCU frequency
board_build.f_cpu = 108000000L


GD32VF103V Evaluation Kit supports the next uploading protocols:

  • altera-usb-blaster
  • gd-link
  • jlink
  • rv-link

Default protocol is rv-link

You can change upload protocol using upload_protocol option:

[env:gd32vf103v_eval]
platform = nuclei
board = gd32vf103v_eval
upload_protocol = rv-link


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

GD32VF103V Evaluation Kit 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
Altera / Intel USB-Blaster Download Cable Yes
GD-LINK
J-LINK
RV-LINK

Name Description
Nuclei SDK Open Source Software Development Kit for the Nuclei N/NX processors

•
GD32VF103V RVStar Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Nuclei: Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.

Microcontroller GD32VF103VBT6
Frequency 108MHz
Flash 128KB
RAM 32KB
Vendor Nuclei

Please use gd32vf103v_rvstar ID for board option in "platformio.ini" (Project Configuration File):

[env:gd32vf103v_rvstar]
platform = nuclei
board = gd32vf103v_rvstar


You can override default GD32VF103V RVStar Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest gd32vf103v_rvstar.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:gd32vf103v_rvstar]
platform = nuclei
board = gd32vf103v_rvstar
; change microcontroller
board_build.mcu = gd32vf103vbt6
; change MCU frequency
board_build.f_cpu = 108000000L


GD32VF103V RVStar Kit supports the next uploading protocols:

  • altera-usb-blaster
  • gd-link
  • jlink
  • rv-link

Default protocol is rv-link

You can change upload protocol using upload_protocol option:

[env:gd32vf103v_rvstar]
platform = nuclei
board = gd32vf103v_rvstar
upload_protocol = rv-link


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

GD32VF103V RVStar 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
Altera / Intel USB-Blaster Download Cable
GD-LINK
J-LINK
RV-LINK Yes Yes

Name Description
Nuclei SDK Open Source Software Development Kit for the Nuclei N/NX processors

•
HummingBird Evaluation Kit
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform Nuclei: Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.

Microcontroller HUMMINGBIRD
Frequency 5MHz
Flash 64KB
RAM 64KB
Vendor Nuclei

Please use hbird_eval ID for board option in "platformio.ini" (Project Configuration File):

[env:hbird_eval]
platform = nuclei
board = hbird_eval


You can override default HummingBird Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest hbird_eval.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:hbird_eval]
platform = nuclei
board = hbird_eval
; change microcontroller
board_build.mcu = HummingBird
; change MCU frequency
board_build.f_cpu = 5000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

HummingBird 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
RV-LINK Yes Yes

Name Description
Nuclei SDK Open Source Software Development Kit for the Nuclei N/NX processors

NXP i.MX RT

•
NXP i.MX RT1010 Evaluation Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP i.MX RT: The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.

Microcontroller MIMXRT1011DAE5A
Frequency 500MHz
Flash 64KB
RAM 128KB
Vendor NXP

Please use mimxrt1010_evk ID for board option in "platformio.ini" (Project Configuration File):

[env:mimxrt1010_evk]
platform = nxpimxrt
board = mimxrt1010_evk


You can override default NXP i.MX RT1010 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1010_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mimxrt1010_evk]
platform = nxpimxrt
board = mimxrt1010_evk
; change microcontroller
board_build.mcu = mimxrt1011dae5a
; change MCU frequency
board_build.f_cpu = 500000000L


NXP i.MX RT1010 Evaluation Kit supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mimxrt1010_evk]
platform = nxpimxrt
board = mimxrt1010_evk
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP i.MX RT1010 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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.

•
NXP i.MX RT1015 Evaluation Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP i.MX RT: The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.

Microcontroller MIMXRT1015DAF5A
Frequency 500MHz
Flash 96KB
RAM 128KB
Vendor NXP

Please use mimxrt1015_evk ID for board option in "platformio.ini" (Project Configuration File):

[env:mimxrt1015_evk]
platform = nxpimxrt
board = mimxrt1015_evk


You can override default NXP i.MX RT1015 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1015_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mimxrt1015_evk]
platform = nxpimxrt
board = mimxrt1015_evk
; change microcontroller
board_build.mcu = mimxrt1015daf5a
; change MCU frequency
board_build.f_cpu = 500000000L


NXP i.MX RT1015 Evaluation Kit supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mimxrt1015_evk]
platform = nxpimxrt
board = mimxrt1015_evk
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP i.MX RT1015 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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.

•
NXP i.MX RT1020 Evaluation Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP i.MX RT: The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.

Microcontroller MIMXRT1021DAG5A
Frequency 500MHz
Flash 64MB
RAM 256MB
Vendor NXP

Please use mimxrt1020_evk ID for board option in "platformio.ini" (Project Configuration File):

[env:mimxrt1020_evk]
platform = nxpimxrt
board = mimxrt1020_evk


You can override default NXP i.MX RT1020 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1020_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mimxrt1020_evk]
platform = nxpimxrt
board = mimxrt1020_evk
; change microcontroller
board_build.mcu = mimxrt1021dag5a
; change MCU frequency
board_build.f_cpu = 500000000L


NXP i.MX RT1020 Evaluation Kit supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mimxrt1020_evk]
platform = nxpimxrt
board = mimxrt1020_evk
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP i.MX RT1020 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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.

•
NXP i.MX RT1050 Evaluation Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP i.MX RT: The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.

Microcontroller MIMXRT1052DVL6B
Frequency 600MHz
Flash 64MB
RAM 512KB
Vendor NXP

Please use mimxrt1050_evk ID for board option in "platformio.ini" (Project Configuration File):

[env:mimxrt1050_evk]
platform = nxpimxrt
board = mimxrt1050_evk


You can override default NXP i.MX RT1050 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1050_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mimxrt1050_evk]
platform = nxpimxrt
board = mimxrt1050_evk
; change microcontroller
board_build.mcu = mimxrt1052dvl6b
; change MCU frequency
board_build.f_cpu = 600000000L


NXP i.MX RT1050 Evaluation Kit supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mimxrt1050_evk]
platform = nxpimxrt
board = mimxrt1050_evk
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP i.MX RT1050 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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.
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.

•
NXP i.MX RT1060 Evaluation Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP i.MX RT: The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.

Microcontroller MIMXRT1062DVL6A
Frequency 600MHz
Flash 64MB
RAM 1MB
Vendor NXP

Please use mimxrt1060_evk ID for board option in "platformio.ini" (Project Configuration File):

[env:mimxrt1060_evk]
platform = nxpimxrt
board = mimxrt1060_evk


You can override default NXP i.MX RT1060 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1060_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mimxrt1060_evk]
platform = nxpimxrt
board = mimxrt1060_evk
; change microcontroller
board_build.mcu = mimxrt1062dvl6a
; change MCU frequency
board_build.f_cpu = 600000000L


NXP i.MX RT1060 Evaluation Kit supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mimxrt1060_evk]
platform = nxpimxrt
board = mimxrt1060_evk
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP i.MX RT1060 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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.

•
NXP i.MX RT1064 Evaluation Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP i.MX RT: The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.

Microcontroller MIMXRT1064DVL6A
Frequency 600MHz
Flash 4MB
RAM 1MB
Vendor NXP

Please use mimxrt1064_evk ID for board option in "platformio.ini" (Project Configuration File):

[env:mimxrt1064_evk]
platform = nxpimxrt
board = mimxrt1064_evk


You can override default NXP i.MX RT1064 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1064_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mimxrt1064_evk]
platform = nxpimxrt
board = mimxrt1064_evk
; change microcontroller
board_build.mcu = mimxrt1064dvl6a
; change MCU frequency
board_build.f_cpu = 600000000L


NXP i.MX RT1064 Evaluation Kit supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mimxrt1064_evk]
platform = nxpimxrt
board = mimxrt1064_evk
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP i.MX RT1064 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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.

NXP LPC

•
ARM mbed LPC11U24 (+CAN)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U24
Frequency 48MHz
Flash 32KB
RAM 8KB
Vendor NXP

Please use lpc11u24_301 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc11u24_301]
platform = nxplpc
board = lpc11u24_301


You can override default ARM mbed LPC11U24 (+CAN) settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u24_301.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc11u24_301]
platform = nxplpc
board = lpc11u24_301
; change microcontroller
board_build.mcu = lpc11u24
; change MCU frequency
board_build.f_cpu = 48000000L


ARM mbed LPC11U24 (+CAN) supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc11u24_301]
platform = nxplpc
board = lpc11u24_301
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ARM mbed LPC11U24 (+CAN) 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
Bambino-210E
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC4330
Frequency 204MHz
Flash 8MB
RAM 264KB
Vendor Micromint

Please use lpc4330_m4 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc4330_m4]
platform = nxplpc
board = lpc4330_m4


You can override default Bambino-210E settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc4330_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc4330_m4]
platform = nxplpc
board = lpc4330_m4
; change microcontroller
board_build.mcu = lpc4330
; change MCU frequency
board_build.f_cpu = 204000000L


Bambino-210E supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc4330_m4]
platform = nxplpc
board = lpc4330_m4
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Bambino-210E 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
CQ Publishing TG-LPC11U35-501
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U35
Frequency 48MHz
Flash 64KB
RAM 10KB
Vendor CQ Publishing

Please use lpc11u35_501 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc11u35_501]
platform = nxplpc
board = lpc11u35_501


You can override default CQ Publishing TG-LPC11U35-501 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u35_501.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc11u35_501]
platform = nxplpc
board = lpc11u35_501
; change microcontroller
board_build.mcu = lpc11u35
; change MCU frequency
board_build.f_cpu = 48000000L


CQ Publishing TG-LPC11U35-501 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc11u35_501]
platform = nxplpc
board = lpc11u35_501
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

CQ Publishing TG-LPC11U35-501 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
Black Magic Probe Yes
J-LINK

Name Description
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.

•
CoCo-ri-Co!
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC812
Frequency 30MHz
Flash 16KB
RAM 4KB
Vendor Elektor Labs

Please use elektor_cocorico ID for board option in "platformio.ini" (Project Configuration File):

[env:elektor_cocorico]
platform = nxplpc
board = elektor_cocorico


You can override default CoCo-ri-Co! settings per build environment using board_*** option, where *** is a JSON object path from board manifest elektor_cocorico.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:elektor_cocorico]
platform = nxplpc
board = elektor_cocorico
; change microcontroller
board_build.mcu = lpc812
; change MCU frequency
board_build.f_cpu = 30000000L


CoCo-ri-Co! supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:elektor_cocorico]
platform = nxplpc
board = elektor_cocorico
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

CoCo-ri-Co! 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
DipCortex M3
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC1347
Frequency 72MHz
Flash 64KB
RAM 12KB
Vendor Solder Splash Labs

Please use lpc1347 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc1347]
platform = nxplpc
board = lpc1347


You can override default DipCortex M3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc1347.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc1347]
platform = nxplpc
board = lpc1347
; change microcontroller
board_build.mcu = lpc1347
; change MCU frequency
board_build.f_cpu = 72000000L


DipCortex M3 supports the next uploading protocols:

  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc1347]
platform = nxplpc
board = lpc1347
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

DipCortex M3 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
J-LINK Yes

Name Description
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.

•
EA LPC11U35 QuickStart Board
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U35
Frequency 48MHz
Flash 64KB
RAM 10KB
Vendor Embedded Artists

Please use lpc11u35 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc11u35]
platform = nxplpc
board = lpc11u35


You can override default EA LPC11U35 QuickStart Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u35.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc11u35]
platform = nxplpc
board = lpc11u35
; change microcontroller
board_build.mcu = lpc11u35
; change MCU frequency
board_build.f_cpu = 48000000L


EA LPC11U35 QuickStart Board supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc11u35]
platform = nxplpc
board = lpc11u35
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

EA LPC11U35 QuickStart Board 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
Black Magic Probe Yes
J-LINK

Name Description
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.

•
Embedded Artists LPC4088 Display Module
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC4088
Frequency 120MHz
Flash 512KB
RAM 96KB
Vendor Embedded Artists

Please use lpc4088_dm ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc4088_dm]
platform = nxplpc
board = lpc4088_dm


You can override default Embedded Artists LPC4088 Display Module settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc4088_dm.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc4088_dm]
platform = nxplpc
board = lpc4088_dm
; change microcontroller
board_build.mcu = lpc4088
; change MCU frequency
board_build.f_cpu = 120000000L


Embedded Artists LPC4088 Display Module supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc4088_dm]
platform = nxplpc
board = lpc4088_dm
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Embedded Artists LPC4088 Display Module 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
Embedded Artists LPC4088 QuickStart Board
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC4088
Frequency 120MHz
Flash 512KB
RAM 96KB
Vendor Embedded Artists

Please use lpc4088 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc4088]
platform = nxplpc
board = lpc4088


You can override default Embedded Artists LPC4088 QuickStart Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc4088.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc4088]
platform = nxplpc
board = lpc4088
; change microcontroller
board_build.mcu = lpc4088
; change MCU frequency
board_build.f_cpu = 120000000L


Embedded Artists LPC4088 QuickStart Board supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc4088]
platform = nxplpc
board = lpc4088
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Embedded Artists LPC4088 QuickStart Board 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
LPCXpresso11U68
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U68
Frequency 50MHz
Flash 256KB
RAM 36KB
Vendor NXP

Please use lpc11u68 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc11u68]
platform = nxplpc
board = lpc11u68


You can override default LPCXpresso11U68 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u68.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc11u68]
platform = nxplpc
board = lpc11u68
; change microcontroller
board_build.mcu = lpc11u68
; change MCU frequency
board_build.f_cpu = 50000000L


LPCXpresso11U68 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc11u68]
platform = nxplpc
board = lpc11u68
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LPCXpresso11U68 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
LPCXpresso824-MAX
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC824
Frequency 30MHz
Flash 32KB
RAM 8KB
Vendor NXP

Please use lpc824 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc824]
platform = nxplpc
board = lpc824


You can override default LPCXpresso824-MAX settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc824.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc824]
platform = nxplpc
board = lpc824
; change microcontroller
board_build.mcu = lpc824
; change MCU frequency
board_build.f_cpu = 30000000L


LPCXpresso824-MAX supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc824]
platform = nxplpc
board = lpc824
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

LPCXpresso824-MAX 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
MicroNFCBoard
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U34
Frequency 48MHz
Flash 48KB
RAM 10KB
Vendor AppNearMe

Please use micronfcboard ID for board option in "platformio.ini" (Project Configuration File):

[env:micronfcboard]
platform = nxplpc
board = micronfcboard


You can override default MicroNFCBoard settings per build environment using board_*** option, where *** is a JSON object path from board manifest micronfcboard.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:micronfcboard]
platform = nxplpc
board = micronfcboard
; change microcontroller
board_build.mcu = lpc11u34
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support MicroNFCBoard board.

Name Description
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.

•
NGX Technologies BlueBoard-LPC11U24
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U24
Frequency 48MHz
Flash 32KB
RAM 8KB
Vendor NGX Technologies

Please use blueboard_lpc11u24 ID for board option in "platformio.ini" (Project Configuration File):

[env:blueboard_lpc11u24]
platform = nxplpc
board = blueboard_lpc11u24


You can override default NGX Technologies BlueBoard-LPC11U24 settings per build environment using board_*** option, where *** is a JSON object path from board manifest blueboard_lpc11u24.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:blueboard_lpc11u24]
platform = nxplpc
board = blueboard_lpc11u24
; change microcontroller
board_build.mcu = lpc11u24
; change MCU frequency
board_build.f_cpu = 48000000L


NGX Technologies BlueBoard-LPC11U24 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:blueboard_lpc11u24]
platform = nxplpc
board = blueboard_lpc11u24
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NGX Technologies BlueBoard-LPC11U24 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
Black Magic Probe Yes
J-LINK

Name Description
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.

•
NXP LPC11C24
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11C24
Frequency 48MHz
Flash 32KB
RAM 8KB
Vendor NXP

Please use lpc11c24 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc11c24]
platform = nxplpc
board = lpc11c24


You can override default NXP LPC11C24 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11c24.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc11c24]
platform = nxplpc
board = lpc11c24
; change microcontroller
board_build.mcu = lpc11c24
; change MCU frequency
board_build.f_cpu = 48000000L


NXP LPC11C24 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc11c24]
platform = nxplpc
board = lpc11c24
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP LPC11C24 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
Black Magic Probe Yes
J-LINK

Name Description
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.

•
NXP LPC11U34
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U34
Frequency 48MHz
Flash 40KB
RAM 8KB
Vendor NXP

Please use lpc11u34_421 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc11u34_421]
platform = nxplpc
board = lpc11u34_421


You can override default NXP LPC11U34 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u34_421.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc11u34_421]
platform = nxplpc
board = lpc11u34_421
; change microcontroller
board_build.mcu = lpc11u34
; change MCU frequency
board_build.f_cpu = 48000000L


NXP LPC11U34 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc11u34_421]
platform = nxplpc
board = lpc11u34_421
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP LPC11U34 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
Black Magic Probe Yes
J-LINK

Name Description
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.

•
NXP LPC11U37
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U37
Frequency 48MHz
Flash 128KB
RAM 10KB
Vendor NXP

Please use lpc11u37_501 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc11u37_501]
platform = nxplpc
board = lpc11u37_501


You can override default NXP LPC11U37 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u37_501.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc11u37_501]
platform = nxplpc
board = lpc11u37_501
; change microcontroller
board_build.mcu = lpc11u37
; change MCU frequency
board_build.f_cpu = 48000000L


NXP LPC11U37 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc11u37_501]
platform = nxplpc
board = lpc11u37_501
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP LPC11U37 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
Black Magic Probe Yes
J-LINK

Name Description
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.

•
NXP LPC800-MAX
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC812
Frequency 30MHz
Flash 16KB
RAM 4KB
Vendor NXP

Please use lpc812 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc812]
platform = nxplpc
board = lpc812


You can override default NXP LPC800-MAX settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc812.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc812]
platform = nxplpc
board = lpc812
; change microcontroller
board_build.mcu = lpc812
; change MCU frequency
board_build.f_cpu = 30000000L


NXP LPC800-MAX supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc812]
platform = nxplpc
board = lpc812
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP LPC800-MAX 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
NXP LPCXpresso1549
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC1549
Frequency 72MHz
Flash 256KB
RAM 36KB
Vendor NXP

Please use lpc1549 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpc1549]
platform = nxplpc
board = lpc1549


You can override default NXP LPCXpresso1549 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc1549.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpc1549]
platform = nxplpc
board = lpc1549
; change microcontroller
board_build.mcu = lpc1549
; change MCU frequency
board_build.f_cpu = 72000000L


NXP LPCXpresso1549 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc1549]
platform = nxplpc
board = lpc1549
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP LPCXpresso1549 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
Black Magic Probe Yes
J-LINK

Name Description
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.

•
NXP LPCXpresso54114
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC54114J256BD64
Frequency 100MHz
Flash 256KB
RAM 192KB
Vendor NXP

Please use lpc54114 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:lpc54114]
platform = nxplpc
board = lpc54114
; change microcontroller
board_build.mcu = lpc54114j256bd64
; change MCU frequency
board_build.f_cpu = 100000000L


NXP LPCXpresso54114 supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc54114]
platform = nxplpc
board = lpc54114
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP LPCXpresso54114 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.
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.

•
NXP LPCXpresso54608
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC54608ET512
Frequency 180MHz
Flash 512KB
RAM 200KB
Vendor NXP

Please use lpc546xx ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:lpc546xx]
platform = nxplpc
board = lpc546xx
; change microcontroller
board_build.mcu = lpc54608et512
; change MCU frequency
board_build.f_cpu = 180000000L


NXP LPCXpresso54608 supports the next uploading protocols:

  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc546xx]
platform = nxplpc
board = lpc546xx
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP LPCXpresso54608 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
J-LINK Yes Yes

Name Description
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.

•
NXP mbed LPC11U24
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U24
Frequency 48MHz
Flash 32KB
RAM 8KB
Vendor NXP

Please use lpc11u24 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:lpc11u24]
platform = nxplpc
board = lpc11u24
; change microcontroller
board_build.mcu = lpc11u24
; change MCU frequency
board_build.f_cpu = 48000000L


NXP mbed LPC11U24 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc11u24]
platform = nxplpc
board = lpc11u24
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP mbed LPC11U24 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
NXP mbed LPC1768
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC1768
Frequency 96MHz
Flash 512KB
RAM 64KB
Vendor NXP

Please use lpc1768 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:lpc1768]
platform = nxplpc
board = lpc1768
; change microcontroller
board_build.mcu = lpc1768
; change MCU frequency
board_build.f_cpu = 96000000L


NXP mbed LPC1768 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc1768]
platform = nxplpc
board = lpc1768
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NXP mbed LPC1768 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
Outrageous Circuits mBuino
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U24
Frequency 48MHz
Flash 32KB
RAM 8KB
Vendor Outrageous Circuits

Please use mbuino ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:mbuino]
platform = nxplpc
board = mbuino
; change microcontroller
board_build.mcu = lpc11u24
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support Outrageous Circuits mBuino board.

Name Description
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.

•
Seeed Arch GPRS V2
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U37
Frequency 48MHz
Flash 128KB
RAM 10KB
Vendor SeeedStudio

Please use seeedArchGPRS ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:seeedArchGPRS]
platform = nxplpc
board = seeedArchGPRS
; change microcontroller
board_build.mcu = lpc11u37
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support Seeed Arch GPRS V2 board.

Name Description
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.

•
Seeed Arch Pro
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC1768
Frequency 96MHz
Flash 512KB
RAM 64KB
Vendor SeeedStudio

Please use seeedArchPro ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:seeedArchPro]
platform = nxplpc
board = seeedArchPro
; change microcontroller
board_build.mcu = lpc1768
; change MCU frequency
board_build.f_cpu = 96000000L


Seeed Arch Pro supports the next uploading protocols:

  • cmsis-dap
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:seeedArchPro]
platform = nxplpc
board = seeedArchPro
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Seeed Arch Pro 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
CMSIS-DAP Yes Yes

Name Description
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.

•
Seeed Xadow M0
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U35
Frequency 48MHz
Flash 64KB
RAM 10KB
Vendor SeeedStudio

Please use xadow_m0 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:xadow_m0]
platform = nxplpc
board = xadow_m0
; change microcontroller
board_build.mcu = lpc11u35
; change MCU frequency
board_build.f_cpu = 48000000L


PIO Unified Debugger currently does not support Seeed Xadow M0 board.

Name Description
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.

•
Smeshlink xbed LPC1768
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC1768
Frequency 96MHz
Flash 512KB
RAM 32KB
Vendor Smeshlink

Please use xbed_lpc1768 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:xbed_lpc1768]
platform = nxplpc
board = xbed_lpc1768
; change microcontroller
board_build.mcu = lpc1768
; change MCU frequency
board_build.f_cpu = 96000000L


PIO Unified Debugger currently does not support Smeshlink xbed LPC1768 board.

Name Description
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.

•
Solder Splash Labs DipCortex M0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U24
Frequency 50MHz
Flash 32KB
RAM 8KB
Vendor Solder Splash Labs

Please use dipcortexm0 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:dipcortexm0]
platform = nxplpc
board = dipcortexm0
; change microcontroller
board_build.mcu = lpc11u24
; change MCU frequency
board_build.f_cpu = 50000000L


Solder Splash Labs DipCortex M0 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:dipcortexm0]
platform = nxplpc
board = dipcortexm0
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
Black Magic Probe Yes
J-LINK

Name Description
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.

•
Switch Science mbed LPC1114FN28
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC1114FN28
Frequency 48MHz
Flash 32KB
RAM 4KB
Vendor Switch Science

Please use lpc1114fn28 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:lpc1114fn28]
platform = nxplpc
board = lpc1114fn28
; change microcontroller
board_build.mcu = lpc1114fn28
; change MCU frequency
board_build.f_cpu = 48000000L


Switch Science mbed LPC1114FN28 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc1114fn28]
platform = nxplpc
board = lpc1114fn28
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Switch Science mbed LPC1114FN28 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
Switch Science mbed LPC824
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC824
Frequency 30MHz
Flash 32KB
RAM 8KB
Vendor Switch Science

Please use ssci824 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:ssci824]
platform = nxplpc
board = ssci824
; change microcontroller
board_build.mcu = lpc824
; change MCU frequency
board_build.f_cpu = 30000000L


Switch Science mbed LPC824 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:ssci824]
platform = nxplpc
board = ssci824
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Switch Science mbed LPC824 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
mBuino
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U24
Frequency 50MHz
Flash 32KB
RAM 10KB
Vendor GHI Electronics

Please use oc_mbuino ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:oc_mbuino]
platform = nxplpc
board = oc_mbuino
; change microcontroller
board_build.mcu = lpc11u24
; change MCU frequency
board_build.f_cpu = 50000000L


PIO Unified Debugger currently does not support mBuino board.

Name Description
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.

u-blox C027

•
u-blox C027
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC1768
Frequency 96MHz
Flash 512KB
RAM 64KB
Vendor u-blox

Please use ubloxc027 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:ubloxc027]
platform = nxplpc
board = ubloxc027
; change microcontroller
board_build.mcu = lpc1768
; change MCU frequency
board_build.f_cpu = 96000000L


u-blox C027 supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:ubloxc027]
platform = nxplpc
board = ubloxc027
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

u-blox C027 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
y5 LPC11U35 mbug
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform NXP LPC: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.

Microcontroller LPC11U35
Frequency 48MHz
Flash 64KB
RAM 10KB
Vendor y5 design

Please use lpc11u35_y5_mbug ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:lpc11u35_y5_mbug]
platform = nxplpc
board = lpc11u35_y5_mbug
; change microcontroller
board_build.mcu = lpc11u35
; change MCU frequency
board_build.f_cpu = 48000000L


y5 LPC11U35 mbug supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:lpc11u35_y5_mbug]
platform = nxplpc
board = lpc11u35_y5_mbug
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
Black Magic Probe Yes
J-LINK

Name Description
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.

RISC-V GAP

•
GAPuino GAP8
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform RISC-V 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

Please use gapuino ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:gapuino]
platform = riscv_gap
board = gapuino
; change microcontroller
board_build.mcu = gap8
; change MCU frequency
board_build.f_cpu = 250000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
FTDI Chip Yes Yes

Name Description
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.
PULP OS PULP is a silicon-proven Parallel Ultra Low Power platform targeting high energy efficiencies. The platform is organized in clusters of RISC-V cores that share a tightly-coupled data memory.

•
Artix-7 35T Arty FPGA Evaluation Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


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

Please use artix7_35t ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:artix7_35t]
platform = shakti
board = artix7_35t
; change microcontroller
board_build.mcu = E-Class
; change MCU frequency
board_build.f_cpu = 50000000L


Artix-7 35T Arty FPGA Evaluation Kit supports the next uploading protocols:

  • ftdi
  • ftdi
  • jlink
  • jlink

Default protocol is ftdi

You can change upload protocol using upload_protocol option:

[env:artix7_35t]
platform = shakti
board = artix7_35t
upload_protocol = ftdi


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
FTDI Chip Yes Yes
J-LINK

Name Description
Shakti SDK A software development kit for developing applications on Shakti class of processors

•
Arty A7-100: Artix-7 FPGA Development Board
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


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 C-CLASS
Frequency 50MHz
Flash 0B
RAM 128MB
Vendor Xilinx

Please use artix7_100t ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:artix7_100t]
platform = shakti
board = artix7_100t
; change microcontroller
board_build.mcu = C-Class
; change MCU frequency
board_build.f_cpu = 50000000L


Arty A7-100: Artix-7 FPGA Development Board supports the next uploading protocols:

  • ftdi
  • ftdi
  • jlink
  • jlink

Default protocol is ftdi

You can change upload protocol using upload_protocol option:

[env:artix7_100t]
platform = shakti
board = artix7_100t
upload_protocol = ftdi


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
FTDI Chip Yes Yes
J-LINK

Name Description
Shakti SDK A software development kit for developing applications on Shakti class of processors

•
Arty FPGA Dev Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


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

Please use e310-arty ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:e310-arty]
platform = sifive
board = e310-arty
; change microcontroller
board_build.mcu = fe310
; change MCU frequency
board_build.f_cpu = 450000000L


Arty FPGA Dev Kit supports the next uploading protocols:

  • ftdi
  • jlink
  • minimodule
  • olimex-arm-usb-ocd
  • olimex-arm-usb-ocd-h
  • olimex-arm-usb-tiny-h
  • olimex-jtag-tiny
  • tumpa

Default protocol is ftdi

You can change upload protocol using upload_protocol option:

[env:e310-arty]
platform = sifive
board = e310-arty
upload_protocol = ftdi


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
FTDI Chip Yes Yes
J-LINK
Mini-Module FT2232H
Olimex ARM-USB-OCD
Olimex ARM-USB-OCD-H
Olimex ARM-USB-TINY-H
Olimex ARM-USB-TINY
QEMU Yes
Renode Yes
TIAO USB Multi-Protocol Adapter (TUMPA)

Name Description
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform

•
HiFive Unleashed
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


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 FU540
Frequency 1500MHz
Flash 32MB
RAM 8GB
Vendor SiFive

Please use hifive-unleashed ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:hifive-unleashed]
platform = sifive
board = hifive-unleashed
; change microcontroller
board_build.mcu = fu540
; change MCU frequency
board_build.f_cpu = 1500000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
FTDI Chip Yes Yes
QEMU Yes
Renode Yes

Name Description
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform

•
HiFive1
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


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 320MHz
Flash 16MB
RAM 16KB
Vendor SiFive

Please use hifive1 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:hifive1]
platform = sifive
board = hifive1
; change microcontroller
board_build.mcu = fe310
; change MCU frequency
board_build.f_cpu = 320000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

HiFive1 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
FTDI Chip Yes Yes
QEMU Yes
Renode Yes

Name Description
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
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
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


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 320MHz
Flash 16MB
RAM 16KB
Vendor SiFive

Please use hifive1-revb ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:hifive1-revb]
platform = sifive
board = hifive1-revb
; change microcontroller
board_build.mcu = fe310
; change MCU frequency
board_build.f_cpu = 320000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
J-LINK Yes Yes
Renode Yes

Name Description
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
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

•
SparkFun RED-V RedBoard
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


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 320MHz
Flash 16MB
RAM 16KB
Vendor SparkFun

Please use sparkfun_redboard_v ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:sparkfun_redboard_v]
platform = sifive
board = sparkfun_redboard_v
; change microcontroller
board_build.mcu = fe310
; change MCU frequency
board_build.f_cpu = 320000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SparkFun RED-V RedBoard 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
J-LINK Yes Yes
Renode Yes

Name Description
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
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 Thing Plus

•
SparkFun RED-V Thing Plus
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


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 320MHz
Flash 16MB
RAM 16KB
Vendor SparkFun

Please use sparkfun_thing_plus_v ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:sparkfun_thing_plus_v]
platform = sifive
board = sparkfun_thing_plus_v
; change microcontroller
board_build.mcu = fe310
; change MCU frequency
board_build.f_cpu = 320000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
J-LINK Yes Yes
Renode Yes

Name Description
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
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.

Silicon Labs EFM32

•
EFM32GG-STK3700 Giant Gecko
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Silicon Labs EFM32: 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

Please use efm32gg_stk3700 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:efm32gg_stk3700]
platform = siliconlabsefm32
board = efm32gg_stk3700
; change microcontroller
board_build.mcu = efm32gg990f1024
; change MCU frequency
board_build.f_cpu = 48000000L


EFM32GG-STK3700 Giant Gecko supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:efm32gg_stk3700]
platform = siliconlabsefm32
board = efm32gg_stk3700
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

EFM32GG-STK3700 Giant 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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.

•
EFM32LG-STK3600 Leopard Gecko
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Silicon Labs EFM32: 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 EFM32LG990F256
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Silicon Labs

Please use efm32lg_stk3600 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:efm32lg_stk3600]
platform = siliconlabsefm32
board = efm32lg_stk3600
; change microcontroller
board_build.mcu = efm32lg990f256
; change MCU frequency
board_build.f_cpu = 48000000L


EFM32LG-STK3600 Leopard Gecko supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:efm32lg_stk3600]
platform = siliconlabsefm32
board = efm32lg_stk3600
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

EFM32LG-STK3600 Leopard 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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.

•
EFM32WG-STK3800 Wonder Gecko
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Silicon Labs EFM32: 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 EFM32WG990F256
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor Silicon Labs

Please use efm32wg_stk3800 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:efm32wg_stk3800]
platform = siliconlabsefm32
board = efm32wg_stk3800
; change microcontroller
board_build.mcu = efm32wg990f256
; change MCU frequency
board_build.f_cpu = 48000000L


EFM32WG-STK3800 Wonder Gecko supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:efm32wg_stk3800]
platform = siliconlabsefm32
board = efm32wg_stk3800
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

EFM32WG-STK3800 Wonder 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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.
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.

•
EFM32ZG-STK3200 Zero Gecko
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Silicon Labs EFM32: 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 EFM32ZG222F32
Frequency 24MHz
Flash 32KB
RAM 4KB
Vendor Silicon Labs

Please use efm32zg_stk3200 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:efm32zg_stk3200]
platform = siliconlabsefm32
board = efm32zg_stk3200
; change microcontroller
board_build.mcu = efm32zg222f32
; change MCU frequency
board_build.f_cpu = 24000000L


EFM32ZG-STK3200 Zero Gecko supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:efm32zg_stk3200]
platform = siliconlabsefm32
board = efm32zg_stk3200
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.

•
SLSTK3400A USB-enabled Happy Gecko
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Silicon Labs EFM32: 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 EFM32HG322F64
Frequency 25MHz
Flash 64KB
RAM 8KB
Vendor Silicon Labs

Please use efm32hg_stk3400 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:efm32hg_stk3400]
platform = siliconlabsefm32
board = efm32hg_stk3400
; change microcontroller
board_build.mcu = efm32hg322f64
; change MCU frequency
board_build.f_cpu = 25000000L


SLSTK3400A USB-enabled Happy Gecko supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:efm32hg_stk3400]
platform = siliconlabsefm32
board = efm32hg_stk3400
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
Black Magic Probe
J-LINK Yes Yes

Name Description
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.
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.

•
SLSTK3401A Pearl Gecko PG1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Silicon Labs EFM32: 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 EFM32PG1B200F256GM48
Frequency 40MHz
Flash 256KB
RAM 32KB
Vendor Silicon Labs

Please use efm32pg_stk3401 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:efm32pg_stk3401]
platform = siliconlabsefm32
board = efm32pg_stk3401
; change microcontroller
board_build.mcu = efm32pg1b200f256gm48
; change MCU frequency
board_build.f_cpu = 40000000L


SLSTK3401A Pearl Gecko PG1 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:efm32pg_stk3401]
platform = siliconlabsefm32
board = efm32pg_stk3401
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SLSTK3401A Pearl Gecko PG1 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
Black Magic Probe
J-LINK Yes Yes

Name Description
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.

•
Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Silicon Labs EFM32: 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 EFR32MG12P432F1024
Frequency 40MHz
Flash 1MB
RAM 256KB
Vendor Silicon Labs

Please use tb_sense_12 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:tb_sense_12]
platform = siliconlabsefm32
board = tb_sense_12
; change microcontroller
board_build.mcu = EFR32MG12P432F1024
; change MCU frequency
board_build.f_cpu = 40000000L


Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:tb_sense_12]
platform = siliconlabsefm32
board = tb_sense_12
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
Black Magic Probe
J-LINK Yes Yes

Name Description
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.

ST STM32

•
1Bitsy
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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

Please use 1bitsy_stm32f415rgt ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:1bitsy_stm32f415rgt]
platform = ststm32
board = 1bitsy_stm32f415rgt
; change microcontroller
board_build.mcu = stm32f415rgt
; change MCU frequency
board_build.f_cpu = 168000000L


1Bitsy supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is blackmagic

You can change upload protocol using upload_protocol option:

[env:1bitsy_stm32f415rgt]
platform = ststm32
board = 1bitsy_stm32f415rgt
upload_protocol = blackmagic


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F412ZGT6
Frequency 100MHz
Flash 1MB
RAM 256KB
Vendor ST

Please use disco_f412zg ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:disco_f412zg]
platform = ststm32
board = disco_f412zg
; change microcontroller
board_build.mcu = stm32f412zgt6
; change MCU frequency
board_build.f_cpu = 100000000L


32F412GDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f412zg]
platform = ststm32
board = disco_f412zg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

32F412GDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F723IEK6
Frequency 216MHz
Flash 512KB
RAM 192KB
Vendor ST

Please use disco_f723ie ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:disco_f723ie]
platform = ststm32
board = disco_f723ie
; change microcontroller
board_build.mcu = stm32f723iek6
; change MCU frequency
board_build.f_cpu = 216000000L


32F723EDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f723ie]
platform = ststm32
board = disco_f723ie
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

32F723EDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VET6
Frequency 168MHz
Flash 512KB
RAM 192KB
Vendor Armed

Please use armed_v1 ID for board option in "platformio.ini" (Project Configuration File):

[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.

[env:armed_v1]
platform = ststm32
board = armed_v1
; change microcontroller
board_build.mcu = stm32f407vet6
; change MCU frequency
board_build.f_cpu = 168000000L


3D Printer Controller supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:armed_v1]
platform = ststm32
board = armed_v1
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

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.

Compatible Tools On-board Default
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
3D Printer control board
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F446RET6
Frequency 180MHz
Flash 512KB
RAM 128KB
Vendor RUMBA

Please use rumba32_f446ve ID for board option in "platformio.ini" (Project Configuration File):

[env:rumba32_f446ve]
platform = ststm32
board = rumba32_f446ve


You can override default 3D Printer control board settings per build environment using board_*** option, where *** is a JSON object path from board manifest rumba32_f446ve.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:rumba32_f446ve]
platform = ststm32
board = rumba32_f446ve
; change microcontroller
board_build.mcu = stm32f446ret6
; change MCU frequency
board_build.f_cpu = 180000000L


3D Printer control board supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:rumba32_f446ve]
platform = ststm32
board = rumba32_f446ve
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

3D Printer control board 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
3D printer controller
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F765VIT6
Frequency 216MHz
Flash 2MB
RAM 512KB
Vendor RemRam

Please use remram_v1 ID for board option in "platformio.ini" (Project Configuration File):

[env:remram_v1]
platform = ststm32
board = remram_v1


You can override default 3D printer controller settings per build environment using board_*** option, where *** is a JSON object path from board manifest remram_v1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:remram_v1]
platform = ststm32
board = remram_v1
; change microcontroller
board_build.mcu = stm32f765vit6
; change MCU frequency
board_build.f_cpu = 216000000L


3D printer controller supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:remram_v1]
platform = ststm32
board = remram_v1
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

3D printer controller 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
3DP001V1 Evaluation board for 3D printer
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F401VGT6
Frequency 84MHz
Flash 512KB
RAM 96KB
Vendor ST

Please use st3dp001_eval ID for board option in "platformio.ini" (Project Configuration File):

[env:st3dp001_eval]
platform = ststm32
board = st3dp001_eval


You can override default 3DP001V1 Evaluation board for 3D printer settings per build environment using board_*** option, where *** is a JSON object path from board manifest st3dp001_eval.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:st3dp001_eval]
platform = ststm32
board = st3dp001_eval
; change microcontroller
board_build.mcu = stm32f401vgt6
; change MCU frequency
board_build.f_cpu = 84000000L


3DP001V1 Evaluation board for 3D printer supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:st3dp001_eval]
platform = ststm32
board = st3dp001_eval
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

3DP001V1 Evaluation board for 3D printer 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
96Boards Argonkey (STEVAL-MKI187V1)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F412CG
Frequency 100MHz
Flash 1MB
RAM 256KB
Vendor 96Boards

Please use b96b_argonkey ID for board option in "platformio.ini" (Project Configuration File):

[env:b96b_argonkey]
platform = ststm32
board = b96b_argonkey


You can override default 96Boards Argonkey (STEVAL-MKI187V1) settings per build environment using board_*** option, where *** is a JSON object path from board manifest b96b_argonkey.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:b96b_argonkey]
platform = ststm32
board = b96b_argonkey
; change microcontroller
board_build.mcu = stm32f412cg
; change MCU frequency
board_build.f_cpu = 100000000L


96Boards Argonkey (STEVAL-MKI187V1) supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:b96b_argonkey]
platform = ststm32
board = b96b_argonkey
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

96Boards Argonkey (STEVAL-MKI187V1) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
96Boards B96B-F446VE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F446VET6
Frequency 168MHz
Flash 512KB
RAM 128KB
Vendor 96Boards

Please use b96b_f446ve ID for board option in "platformio.ini" (Project Configuration File):

[env:b96b_f446ve]
platform = ststm32
board = b96b_f446ve


You can override default 96Boards B96B-F446VE settings per build environment using board_*** option, where *** is a JSON object path from board manifest b96b_f446ve.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:b96b_f446ve]
platform = ststm32
board = b96b_f446ve
; change microcontroller
board_build.mcu = stm32f446vet6
; change MCU frequency
board_build.f_cpu = 168000000L


96Boards B96B-F446VE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:b96b_f446ve]
platform = ststm32
board = b96b_f446ve
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

96Boards B96B-F446VE 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
96Boards Neonkey
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F411CE
Frequency 100MHz
Flash 512KB
RAM 128KB
Vendor 96Boards

Please use b96b_neonkey ID for board option in "platformio.ini" (Project Configuration File):

[env:b96b_neonkey]
platform = ststm32
board = b96b_neonkey


You can override default 96Boards Neonkey settings per build environment using board_*** option, where *** is a JSON object path from board manifest b96b_neonkey.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:b96b_neonkey]
platform = ststm32
board = b96b_neonkey
; change microcontroller
board_build.mcu = stm32f411ce
; change MCU frequency
board_build.f_cpu = 100000000L


96Boards Neonkey supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:b96b_neonkey]
platform = ststm32
board = b96b_neonkey
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

96Boards Neonkey 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
Adafruit Feather STM32F405
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F405RGT6
Frequency 168MHz
Flash 1MB
RAM 128KB
Vendor Adafruit

Please use adafruit_feather_f405 ID for board option in "platformio.ini" (Project Configuration File):

[env:adafruit_feather_f405]
platform = ststm32
board = adafruit_feather_f405


You can override default Adafruit Feather STM32F405 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_f405.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:adafruit_feather_f405]
platform = ststm32
board = adafruit_feather_f405
; change microcontroller
board_build.mcu = stm32f405rgt6
; change MCU frequency
board_build.f_cpu = 168000000L


Adafruit Feather STM32F405 supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:adafruit_feather_f405]
platform = ststm32
board = adafruit_feather_f405
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Adafruit Feather STM32F405 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
AfroFlight Rev5 (8MHz)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103CBT6
Frequency 72MHz
Flash 128KB
RAM 20KB
Vendor AfroFlight

Please use afroflight_f103cb ID for board option in "platformio.ini" (Project Configuration File):

[env:afroflight_f103cb]
platform = ststm32
board = afroflight_f103cb


You can override default AfroFlight Rev5 (8MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest afroflight_f103cb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:afroflight_f103cb]
platform = ststm32
board = afroflight_f103cb
; change microcontroller
board_build.mcu = stm32f103cbt6
; change MCU frequency
board_build.f_cpu = 72000000L


AfroFlight Rev5 (8MHz) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:afroflight_f103cb]
platform = ststm32
board = afroflight_f103cb
upload_protocol = serial


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

AfroFlight Rev5 (8MHz) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Armstrap Eagle 1024
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F417VGT6
Frequency 168MHz
Flash 1MB
RAM 192KB
Vendor Armstrap

Please use armstrap_eagle1024 ID for board option in "platformio.ini" (Project Configuration File):

[env:armstrap_eagle1024]
platform = ststm32
board = armstrap_eagle1024


You can override default Armstrap Eagle 1024 settings per build environment using board_*** option, where *** is a JSON object path from board manifest armstrap_eagle1024.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:armstrap_eagle1024]
platform = ststm32
board = armstrap_eagle1024
; change microcontroller
board_build.mcu = stm32f417vgt6
; change MCU frequency
board_build.f_cpu = 168000000L


Armstrap Eagle 1024 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is blackmagic

You can change upload protocol using upload_protocol option:

[env:armstrap_eagle1024]
platform = ststm32
board = armstrap_eagle1024
upload_protocol = blackmagic


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Armstrap Eagle 1024 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
Black Magic Probe Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Armstrap Eagle 2048
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F427VIT6
Frequency 168MHz
Flash 1.99MB
RAM 256KB
Vendor Armstrap

Please use armstrap_eagle2048 ID for board option in "platformio.ini" (Project Configuration File):

[env:armstrap_eagle2048]
platform = ststm32
board = armstrap_eagle2048


You can override default Armstrap Eagle 2048 settings per build environment using board_*** option, where *** is a JSON object path from board manifest armstrap_eagle2048.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:armstrap_eagle2048]
platform = ststm32
board = armstrap_eagle2048
; change microcontroller
board_build.mcu = stm32f427vit6
; change MCU frequency
board_build.f_cpu = 168000000L


Armstrap Eagle 2048 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is blackmagic

You can change upload protocol using upload_protocol option:

[env:armstrap_eagle2048]
platform = ststm32
board = armstrap_eagle2048
upload_protocol = blackmagic


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Armstrap Eagle 2048 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
Black Magic Probe Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Armstrap Eagle 512
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VET6
Frequency 168MHz
Flash 512KB
RAM 192KB
Vendor Armstrap

Please use armstrap_eagle512 ID for board option in "platformio.ini" (Project Configuration File):

[env:armstrap_eagle512]
platform = ststm32
board = armstrap_eagle512


You can override default Armstrap Eagle 512 settings per build environment using board_*** option, where *** is a JSON object path from board manifest armstrap_eagle512.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:armstrap_eagle512]
platform = ststm32
board = armstrap_eagle512
; change microcontroller
board_build.mcu = stm32f407vet6
; change MCU frequency
board_build.f_cpu = 168000000L


Armstrap Eagle 512 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is blackmagic

You can change upload protocol using upload_protocol option:

[env:armstrap_eagle512]
platform = ststm32
board = armstrap_eagle512
upload_protocol = blackmagic


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Armstrap Eagle 512 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
Black Magic Probe Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Black STM32F407VE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VET6
Frequency 168MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use black_f407ve ID for board option in "platformio.ini" (Project Configuration File):

[env:black_f407ve]
platform = ststm32
board = black_f407ve


You can override default Black STM32F407VE settings per build environment using board_*** option, where *** is a JSON object path from board manifest black_f407ve.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:black_f407ve]
platform = ststm32
board = black_f407ve
; change microcontroller
board_build.mcu = stm32f407vet6
; change MCU frequency
board_build.f_cpu = 168000000L


Black STM32F407VE supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:black_f407ve]
platform = ststm32
board = black_f407ve
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Black STM32F407VE 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Black STM32F407VG
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VGT6
Frequency 168MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use black_f407vg ID for board option in "platformio.ini" (Project Configuration File):

[env:black_f407vg]
platform = ststm32
board = black_f407vg


You can override default Black STM32F407VG settings per build environment using board_*** option, where *** is a JSON object path from board manifest black_f407vg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:black_f407vg]
platform = ststm32
board = black_f407vg
; change microcontroller
board_build.mcu = stm32f407vgt6
; change MCU frequency
board_build.f_cpu = 168000000L


Black STM32F407VG supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:black_f407vg]
platform = ststm32
board = black_f407vg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Black STM32F407VG 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

Black STM32F407ZE

•
Black STM32F407ZE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407ZET6
Frequency 168MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use black_f407ze ID for board option in "platformio.ini" (Project Configuration File):

[env:black_f407ze]
platform = ststm32
board = black_f407ze


You can override default Black STM32F407ZE settings per build environment using board_*** option, where *** is a JSON object path from board manifest black_f407ze.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:black_f407ze]
platform = ststm32
board = black_f407ze
; change microcontroller
board_build.mcu = stm32f407zet6
; change MCU frequency
board_build.f_cpu = 168000000L


Black STM32F407ZE supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:black_f407ze]
platform = ststm32
board = black_f407ze
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Black STM32F407ZE 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

Black STM32F407ZE

•
Black STM32F407ZE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407ZGT6
Frequency 168MHz
Flash 1MB
RAM 128KB
Vendor ST

Please use black_f407zg ID for board option in "platformio.ini" (Project Configuration File):

[env:black_f407zg]
platform = ststm32
board = black_f407zg


You can override default Black STM32F407ZE settings per build environment using board_*** option, where *** is a JSON object path from board manifest black_f407zg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:black_f407zg]
platform = ststm32
board = black_f407zg
; change microcontroller
board_build.mcu = stm32f407zgt6
; change MCU frequency
board_build.f_cpu = 168000000L


Black STM32F407ZE supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:black_f407zg]
platform = ststm32
board = black_f407zg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Black STM32F407ZE 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
BlackPill F103C8
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103C8T6
Frequency 72MHz
Flash 64KB
RAM 20KB
Vendor Generic

Please use blackpill_f103c8 ID for board option in "platformio.ini" (Project Configuration File):

[env:blackpill_f103c8]
platform = ststm32
board = blackpill_f103c8


You can override default BlackPill F103C8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest blackpill_f103c8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:blackpill_f103c8]
platform = ststm32
board = blackpill_f103c8
; change microcontroller
board_build.mcu = stm32f103c8t6
; change MCU frequency
board_build.f_cpu = 72000000L


BlackPill F103C8 supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:blackpill_f103c8]
platform = ststm32
board = blackpill_f103c8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BlackPill F103C8 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
Black Magic Probe
J-LINK
ST-LINK Yes

Name Description
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.
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.
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.
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.
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.

•
BlackPill F103C8 (128k)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103C8T6
Frequency 72MHz
Flash 128KB
RAM 20KB
Vendor Generic

Please use blackpill_f103c8_128 ID for board option in "platformio.ini" (Project Configuration File):

[env:blackpill_f103c8_128]
platform = ststm32
board = blackpill_f103c8_128


You can override default BlackPill F103C8 (128k) settings per build environment using board_*** option, where *** is a JSON object path from board manifest blackpill_f103c8_128.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:blackpill_f103c8_128]
platform = ststm32
board = blackpill_f103c8_128
; change microcontroller
board_build.mcu = stm32f103c8t6
; change MCU frequency
board_build.f_cpu = 72000000L


BlackPill F103C8 (128k) supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:blackpill_f103c8_128]
platform = ststm32
board = blackpill_f103c8_128
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BlackPill F103C8 (128k) 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
Black Magic Probe
J-LINK
ST-LINK Yes

Name Description
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.
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.
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.
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.
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.

•
BlackPill F303CC
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F303CCT6
Frequency 72MHz
Flash 256KB
RAM 40KB
Vendor RobotDyn

Please use robotdyn_blackpill_f303cc ID for board option in "platformio.ini" (Project Configuration File):

[env:robotdyn_blackpill_f303cc]
platform = ststm32
board = robotdyn_blackpill_f303cc


You can override default BlackPill F303CC settings per build environment using board_*** option, where *** is a JSON object path from board manifest robotdyn_blackpill_f303cc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:robotdyn_blackpill_f303cc]
platform = ststm32
board = robotdyn_blackpill_f303cc
; change microcontroller
board_build.mcu = stm32f303cct6
; change MCU frequency
board_build.f_cpu = 72000000L


BlackPill F303CC supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:robotdyn_blackpill_f303cc]
platform = ststm32
board = robotdyn_blackpill_f303cc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BlackPill F303CC 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
BlackPill F401CC
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F401CCT6
Frequency 84MHz
Flash 256KB
RAM 64KB
Vendor ST

Please use blackpill_f401cc ID for board option in "platformio.ini" (Project Configuration File):

[env:blackpill_f401cc]
platform = ststm32
board = blackpill_f401cc


You can override default BlackPill F401CC settings per build environment using board_*** option, where *** is a JSON object path from board manifest blackpill_f401cc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:blackpill_f401cc]
platform = ststm32
board = blackpill_f401cc
; change microcontroller
board_build.mcu = stm32f401cct6
; change MCU frequency
board_build.f_cpu = 84000000L


BlackPill F401CC supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:blackpill_f401cc]
platform = ststm32
board = blackpill_f401cc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BlackPill F401CC 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Blue STM32F407VE Mini
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VET6
Frequency 168MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use blue_f407ve_mini ID for board option in "platformio.ini" (Project Configuration File):

[env:blue_f407ve_mini]
platform = ststm32
board = blue_f407ve_mini


You can override default Blue STM32F407VE Mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest blue_f407ve_mini.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:blue_f407ve_mini]
platform = ststm32
board = blue_f407ve_mini
; change microcontroller
board_build.mcu = stm32f407vet6
; change MCU frequency
board_build.f_cpu = 168000000L


Blue STM32F407VE Mini supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:blue_f407ve_mini]
platform = ststm32
board = blue_f407ve_mini
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Blue STM32F407VE Mini 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
BluePill F103C6
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103C6T6
Frequency 72MHz
Flash 32KB
RAM 10KB
Vendor Generic

Please use bluepill_f103c6 ID for board option in "platformio.ini" (Project Configuration File):

[env:bluepill_f103c6]
platform = ststm32
board = bluepill_f103c6


You can override default BluePill F103C6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluepill_f103c6.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:bluepill_f103c6]
platform = ststm32
board = bluepill_f103c6
; change microcontroller
board_build.mcu = stm32f103c6t6
; change MCU frequency
board_build.f_cpu = 72000000L


BluePill F103C6 supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:bluepill_f103c6]
platform = ststm32
board = bluepill_f103c6
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BluePill F103C6 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
Black Magic Probe
J-LINK
ST-LINK Yes

Name Description
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.
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.
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.

•
BluePill F103C8
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103C8T6
Frequency 72MHz
Flash 64KB
RAM 20KB
Vendor Generic

Please use bluepill_f103c8 ID for board option in "platformio.ini" (Project Configuration File):

[env:bluepill_f103c8]
platform = ststm32
board = bluepill_f103c8


You can override default BluePill F103C8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluepill_f103c8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:bluepill_f103c8]
platform = ststm32
board = bluepill_f103c8
; change microcontroller
board_build.mcu = stm32f103c8t6
; change MCU frequency
board_build.f_cpu = 72000000L


BluePill F103C8 supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:bluepill_f103c8]
platform = ststm32
board = bluepill_f103c8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BluePill F103C8 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
Black Magic Probe
J-LINK
ST-LINK Yes

Name Description
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.
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.
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.
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.
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.
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.

•
BluePill F103C8 (128k)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103C8T6
Frequency 72MHz
Flash 128KB
RAM 20KB
Vendor Generic

Please use bluepill_f103c8_128k ID for board option in "platformio.ini" (Project Configuration File):

[env:bluepill_f103c8_128k]
platform = ststm32
board = bluepill_f103c8_128k


You can override default BluePill F103C8 (128k) settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluepill_f103c8_128k.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:bluepill_f103c8_128k]
platform = ststm32
board = bluepill_f103c8_128k
; change microcontroller
board_build.mcu = stm32f103c8t6
; change MCU frequency
board_build.f_cpu = 72000000L


BluePill F103C8 (128k) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:bluepill_f103c8_128k]
platform = ststm32
board = bluepill_f103c8_128k
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

BluePill F103C8 (128k) 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
Black Magic Probe
J-LINK
ST-LINK Yes

Name Description
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.
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.
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.
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.
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.

•
Core board F401RCT6
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F401RCT6
Frequency 84MHz
Flash 256KB
RAM 64KB
Vendor ST

Please use coreboard_f401rc ID for board option in "platformio.ini" (Project Configuration File):

[env:coreboard_f401rc]
platform = ststm32
board = coreboard_f401rc


You can override default Core board F401RCT6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest coreboard_f401rc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:coreboard_f401rc]
platform = ststm32
board = coreboard_f401rc
; change microcontroller
board_build.mcu = stm32f401rct6
; change MCU frequency
board_build.f_cpu = 84000000L


Core board F401RCT6 supports the next uploading protocols:

  • blackmagic
  • dfu
  • hid
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:coreboard_f401rc]
platform = ststm32
board = coreboard_f401rc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Core board F401RCT6 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Demo F030F4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F030F4P6
Frequency 48MHz
Flash 16KB
RAM 4KB
Vendor Generic

Please use demo_f030f4 ID for board option in "platformio.ini" (Project Configuration File):

[env:demo_f030f4]
platform = ststm32
board = demo_f030f4


You can override default Demo F030F4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest demo_f030f4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:demo_f030f4]
platform = ststm32
board = demo_f030f4
; change microcontroller
board_build.mcu = stm32f030f4p6
; change MCU frequency
board_build.f_cpu = 48000000L


Demo F030F4 supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:demo_f030f4]
platform = ststm32
board = demo_f030f4
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Demo F030F4 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
Espotel LoRa Module
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F411RET6
Frequency 100MHz
Flash 512KB
RAM 128KB
Vendor Espotel

Please use elmo_f411re ID for board option in "platformio.ini" (Project Configuration File):

[env:elmo_f411re]
platform = ststm32
board = elmo_f411re


You can override default Espotel LoRa Module settings per build environment using board_*** option, where *** is a JSON object path from board manifest elmo_f411re.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:elmo_f411re]
platform = ststm32
board = elmo_f411re
; change microcontroller
board_build.mcu = stm32f411ret6
; change MCU frequency
board_build.f_cpu = 100000000L


Espotel LoRa Module supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:elmo_f411re]
platform = ststm32
board = elmo_f411re
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Espotel LoRa Module does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Black Magic Probe
J-LINK
ST-LINK Yes

Name Description
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.
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.

•
F407VG
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VGT6
Frequency 168MHz
Flash 512KB
RAM 128KB
Vendor Diymore

Please use diymore_f407vgt ID for board option in "platformio.ini" (Project Configuration File):

[env:diymore_f407vgt]
platform = ststm32
board = diymore_f407vgt


You can override default F407VG settings per build environment using board_*** option, where *** is a JSON object path from board manifest diymore_f407vgt.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:diymore_f407vgt]
platform = ststm32
board = diymore_f407vgt
; change microcontroller
board_build.mcu = stm32f407vgt6
; change MCU frequency
board_build.f_cpu = 168000000L


F407VG supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:diymore_f407vgt]
platform = ststm32
board = diymore_f407vgt
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

F407VG 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
FK407M1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VET6
Frequency 168MHz
Flash 512KB
RAM 128KB
Vendor Generic

Please use fk407m1 ID for board option in "platformio.ini" (Project Configuration File):

[env:fk407m1]
platform = ststm32
board = fk407m1


You can override default FK407M1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest fk407m1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:fk407m1]
platform = ststm32
board = fk407m1
; change microcontroller
board_build.mcu = stm32f407vet6
; change MCU frequency
board_build.f_cpu = 168000000L


FK407M1 supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:fk407m1]
platform = ststm32
board = fk407m1
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

FK407M1 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
L476DMW1K
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L476VGT6
Frequency 80MHz
Flash 1MB
RAM 128KB
Vendor rhomb.io

Please use rhombio_l476dmw1k ID for board option in "platformio.ini" (Project Configuration File):

[env:rhombio_l476dmw1k]
platform = ststm32
board = rhombio_l476dmw1k


You can override default L476DMW1K settings per build environment using board_*** option, where *** is a JSON object path from board manifest rhombio_l476dmw1k.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:rhombio_l476dmw1k]
platform = ststm32
board = rhombio_l476dmw1k
; change microcontroller
board_build.mcu = stm32l476vgt6
; change MCU frequency
board_build.f_cpu = 80000000L


L476DMW1K supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • stlink

Default protocol is cmsis-dap

You can change upload protocol using upload_protocol option:

[env:rhombio_l476dmw1k]
platform = ststm32
board = rhombio_l476dmw1k
upload_protocol = cmsis-dap


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

L476DMW1K 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
M200 V2
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F070CBT6
Frequency 48MHz
Flash 120KB
RAM 14.81KB
Vendor Malyan

Please use malyanm200_f070cb ID for board option in "platformio.ini" (Project Configuration File):

[env:malyanm200_f070cb]
platform = ststm32
board = malyanm200_f070cb


You can override default M200 V2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest malyanm200_f070cb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:malyanm200_f070cb]
platform = ststm32
board = malyanm200_f070cb
; change microcontroller
board_build.mcu = stm32f070cbt6
; change MCU frequency
board_build.f_cpu = 48000000L


M200 V2 supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:malyanm200_f070cb]
platform = ststm32
board = malyanm200_f070cb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

M200 V2 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
M300
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F070CBT6
Frequency 48MHz
Flash 120KB
RAM 14.81KB
Vendor Malyan

Please use malyanm300_f070cb ID for board option in "platformio.ini" (Project Configuration File):

[env:malyanm300_f070cb]
platform = ststm32
board = malyanm300_f070cb


You can override default M300 settings per build environment using board_*** option, where *** is a JSON object path from board manifest malyanm300_f070cb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:malyanm300_f070cb]
platform = ststm32
board = malyanm300_f070cb
; change microcontroller
board_build.mcu = stm32f070cbt6
; change MCU frequency
board_build.f_cpu = 48000000L


M300 supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:malyanm300_f070cb]
platform = ststm32
board = malyanm300_f070cb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

M300 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
MKR Sharky
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32WB55CG
Frequency 64MHz
Flash 512KB
RAM 192.00KB
Vendor Midatronics

Please use mkr_sharky ID for board option in "platformio.ini" (Project Configuration File):

[env:mkr_sharky]
platform = ststm32
board = mkr_sharky


You can override default MKR Sharky settings per build environment using board_*** option, where *** is a JSON object path from board manifest mkr_sharky.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mkr_sharky]
platform = ststm32
board = mkr_sharky
; change microcontroller
board_build.mcu = stm32wb55cg
; change MCU frequency
board_build.f_cpu = 64000000L


MKR Sharky supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • mbed
  • serial

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mkr_sharky]
platform = ststm32
board = mkr_sharky
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

MKR Sharky 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
Black Magic Probe Yes
J-LINK

Name Description
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.

•
MTS Dragonfly
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F411RET6
Frequency 100MHz
Flash 512KB
RAM 128KB
Vendor MultiTech

Please use mts_dragonfly_f411re ID for board option in "platformio.ini" (Project Configuration File):

[env:mts_dragonfly_f411re]
platform = ststm32
board = mts_dragonfly_f411re


You can override default MTS Dragonfly settings per build environment using board_*** option, where *** is a JSON object path from board manifest mts_dragonfly_f411re.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mts_dragonfly_f411re]
platform = ststm32
board = mts_dragonfly_f411re
; change microcontroller
board_build.mcu = stm32f411ret6
; change MCU frequency
board_build.f_cpu = 100000000L


MTS Dragonfly supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mts_dragonfly_f411re]
platform = ststm32
board = mts_dragonfly_f411re
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

MTS Dragonfly 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
Malyan M200 V1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103CBT6
Frequency 72MHz
Flash 120KB
RAM 20KB
Vendor Malyan

Please use malyanm200_f103cb ID for board option in "platformio.ini" (Project Configuration File):

[env:malyanm200_f103cb]
platform = ststm32
board = malyanm200_f103cb


You can override default Malyan M200 V1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest malyanm200_f103cb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:malyanm200_f103cb]
platform = ststm32
board = malyanm200_f103cb
; change microcontroller
board_build.mcu = stm32f103cbt6
; change MCU frequency
board_build.f_cpu = 72000000L


Malyan M200 V1 supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:malyanm200_f103cb]
platform = ststm32
board = malyanm200_f103cb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Malyan M200 V1 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
Maple
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103RBT6
Frequency 72MHz
Flash 108KB
RAM 17KB
Vendor LeafLabs

Please use maple ID for board option in "platformio.ini" (Project Configuration File):

[env:maple]
platform = ststm32
board = maple


You can override default Maple settings per build environment using board_*** option, where *** is a JSON object path from board manifest maple.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:maple]
platform = ststm32
board = maple
; change microcontroller
board_build.mcu = stm32f103rbt6
; change MCU frequency
board_build.f_cpu = 72000000L


Maple supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • stlink

Default protocol is dfu

You can change upload protocol using upload_protocol option:

[env:maple]
platform = ststm32
board = maple
upload_protocol = dfu


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Maple 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Maple (RET6)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103RET6
Frequency 72MHz
Flash 256KB
RAM 48KB
Vendor LeafLabs

Please use maple_ret6 ID for board option in "platformio.ini" (Project Configuration File):

[env:maple_ret6]
platform = ststm32
board = maple_ret6


You can override default Maple (RET6) settings per build environment using board_*** option, where *** is a JSON object path from board manifest maple_ret6.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:maple_ret6]
platform = ststm32
board = maple_ret6
; change microcontroller
board_build.mcu = stm32f103ret6
; change MCU frequency
board_build.f_cpu = 72000000L


Maple (RET6) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • stlink

Default protocol is dfu

You can change upload protocol using upload_protocol option:

[env:maple_ret6]
platform = ststm32
board = maple_ret6
upload_protocol = dfu


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Maple (RET6) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Maple Mini Bootloader 2.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103CBT6
Frequency 72MHz
Flash 120KB
RAM 20KB
Vendor LeafLabs

Please use maple_mini_b20 ID for board option in "platformio.ini" (Project Configuration File):

[env:maple_mini_b20]
platform = ststm32
board = maple_mini_b20


You can override default Maple Mini Bootloader 2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest maple_mini_b20.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:maple_mini_b20]
platform = ststm32
board = maple_mini_b20
; change microcontroller
board_build.mcu = stm32f103cbt6
; change MCU frequency
board_build.f_cpu = 72000000L


Maple Mini Bootloader 2.0 supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • stlink

Default protocol is dfu

You can change upload protocol using upload_protocol option:

[env:maple_mini_b20]
platform = ststm32
board = maple_mini_b20
upload_protocol = dfu


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Maple Mini Bootloader 2.0 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Maple Mini Original
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103CBT6
Frequency 72MHz
Flash 108KB
RAM 17KB
Vendor LeafLabs

Please use maple_mini_origin ID for board option in "platformio.ini" (Project Configuration File):

[env:maple_mini_origin]
platform = ststm32
board = maple_mini_origin


You can override default Maple Mini Original settings per build environment using board_*** option, where *** is a JSON object path from board manifest maple_mini_origin.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:maple_mini_origin]
platform = ststm32
board = maple_mini_origin
; change microcontroller
board_build.mcu = stm32f103cbt6
; change MCU frequency
board_build.f_cpu = 72000000L


Maple Mini Original supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is dfu

You can change upload protocol using upload_protocol option:

[env:maple_mini_origin]
platform = ststm32
board = maple_mini_origin
upload_protocol = dfu


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Maple Mini Original 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Mbed Connect Cloud
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F439ZIY6
Frequency 168MHz
Flash 2MB
RAM 256KB
Vendor u-blox

Please use mbed_connect_odin ID for board option in "platformio.ini" (Project Configuration File):

[env:mbed_connect_odin]
platform = ststm32
board = mbed_connect_odin


You can override default Mbed Connect Cloud settings per build environment using board_*** option, where *** is a JSON object path from board manifest mbed_connect_odin.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mbed_connect_odin]
platform = ststm32
board = mbed_connect_odin
; change microcontroller
board_build.mcu = stm32f439ziy6
; change MCU frequency
board_build.f_cpu = 168000000L


Mbed Connect Cloud supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:mbed_connect_odin]
platform = ststm32
board = mbed_connect_odin
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Mbed Connect Cloud 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
Microduino Core STM32 to Flash
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103CBT6
Frequency 72MHz
Flash 105.47KB
RAM 16.60KB
Vendor Microduino

Please use microduino32_flash ID for board option in "platformio.ini" (Project Configuration File):

[env:microduino32_flash]
platform = ststm32
board = microduino32_flash


You can override default Microduino Core STM32 to Flash settings per build environment using board_*** option, where *** is a JSON object path from board manifest microduino32_flash.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:microduino32_flash]
platform = ststm32
board = microduino32_flash
; change microcontroller
board_build.mcu = stm32f103cbt6
; change MCU frequency
board_build.f_cpu = 72000000L


Microduino Core STM32 to Flash supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • stlink

Default protocol is dfu

You can change upload protocol using upload_protocol option:

[env:microduino32_flash]
platform = ststm32
board = microduino32_flash
upload_protocol = dfu


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microduino Core STM32 to Flash 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
Microsoft Azure IoT Development Kit (MXChip AZ3166)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F412ZGT6
Frequency 100MHz
Flash 1MB
RAM 256KB
Vendor MXChip

Please use mxchip_az3166 ID for board option in "platformio.ini" (Project Configuration File):

[env:mxchip_az3166]
platform = ststm32
board = mxchip_az3166


You can override default Microsoft Azure IoT Development Kit (MXChip AZ3166) settings per build environment using board_*** option, where *** is a JSON object path from board manifest mxchip_az3166.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mxchip_az3166]
platform = ststm32
board = mxchip_az3166
; change microcontroller
board_build.mcu = stm32f412zgt6
; change MCU frequency
board_build.f_cpu = 100000000L


Microsoft Azure IoT Development Kit (MXChip AZ3166) supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:mxchip_az3166]
platform = ststm32
board = mxchip_az3166
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Microsoft Azure IoT Development Kit (MXChip AZ3166) 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
MultiTech mDot
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F411RET6
Frequency 100MHz
Flash 512KB
RAM 128KB
Vendor MultiTech

Please use mts_mdot_f405rg ID for board option in "platformio.ini" (Project Configuration File):

[env:mts_mdot_f405rg]
platform = ststm32
board = mts_mdot_f405rg


You can override default MultiTech mDot settings per build environment using board_*** option, where *** is a JSON object path from board manifest mts_mdot_f405rg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mts_mdot_f405rg]
platform = ststm32
board = mts_mdot_f405rg
; change microcontroller
board_build.mcu = stm32f411ret6
; change MCU frequency
board_build.f_cpu = 100000000L


MultiTech mDot supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mts_mdot_f405rg]
platform = ststm32
board = mts_mdot_f405rg
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

MultiTech mDot 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
MultiTech mDot F411
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F411RET6
Frequency 100MHz
Flash 512KB
RAM 128KB
Vendor MultiTech

Please use mts_mdot_f411re ID for board option in "platformio.ini" (Project Configuration File):

[env:mts_mdot_f411re]
platform = ststm32
board = mts_mdot_f411re


You can override default MultiTech mDot F411 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mts_mdot_f411re.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mts_mdot_f411re]
platform = ststm32
board = mts_mdot_f411re
; change microcontroller
board_build.mcu = stm32f411ret6
; change MCU frequency
board_build.f_cpu = 100000000L


MultiTech mDot F411 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mts_mdot_f411re]
platform = ststm32
board = mts_mdot_f411re
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

MultiTech mDot F411 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
MultiTech xDot
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L151CCU6
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor MultiTech

Please use xdot_l151cc ID for board option in "platformio.ini" (Project Configuration File):

[env:xdot_l151cc]
platform = ststm32
board = xdot_l151cc


You can override default MultiTech xDot settings per build environment using board_*** option, where *** is a JSON object path from board manifest xdot_l151cc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:xdot_l151cc]
platform = ststm32
board = xdot_l151cc
; change microcontroller
board_build.mcu = stm32l151ccu6
; change MCU frequency
board_build.f_cpu = 32000000L


MultiTech xDot supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:xdot_l151cc]
platform = ststm32
board = xdot_l151cc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

MultiTech xDot 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
N2+
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F405RGT6
Frequency 168MHz
Flash 1MB
RAM 192KB
Vendor Netduino

Please use netduino2plus ID for board option in "platformio.ini" (Project Configuration File):

[env:netduino2plus]
platform = ststm32
board = netduino2plus


You can override default N2+ settings per build environment using board_*** option, where *** is a JSON object path from board manifest netduino2plus.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:netduino2plus]
platform = ststm32
board = netduino2plus
; change microcontroller
board_build.mcu = stm32f405rgt6
; change MCU frequency
board_build.f_cpu = 168000000L


N2+ supports the next uploading protocols:

  • dfu
  • jlink
  • stlink

Default protocol is dfu

You can change upload protocol using upload_protocol option:

[env:netduino2plus]
platform = ststm32
board = netduino2plus
upload_protocol = dfu


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

N2+ 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
J-LINK
ST-LINK Yes

Name Description
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.
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.

•
NAMote72
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L152RC
Frequency 32MHz
Flash 256KB
RAM 32KB
Vendor Semtech

Please use mote_l152rc ID for board option in "platformio.ini" (Project Configuration File):

[env:mote_l152rc]
platform = ststm32
board = mote_l152rc


You can override default NAMote72 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mote_l152rc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mote_l152rc]
platform = ststm32
board = mote_l152rc
; change microcontroller
board_build.mcu = stm32l152rc
; change MCU frequency
board_build.f_cpu = 32000000L


NAMote72 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:mote_l152rc]
platform = ststm32
board = mote_l152rc
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

NAMote72 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
Nucleo G071RB
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32G071RBT6
Frequency 64MHz
Flash 128KB
RAM 36KB
Vendor ST

Please use nucleo_g071rb ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_g071rb]
platform = ststm32
board = nucleo_g071rb


You can override default Nucleo G071RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_g071rb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_g071rb]
platform = ststm32
board = nucleo_g071rb
; change microcontroller
board_build.mcu = stm32g071rbt6
; change MCU frequency
board_build.f_cpu = 64000000L


Nucleo G071RB supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:nucleo_g071rb]
platform = ststm32
board = nucleo_g071rb
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nucleo G071RB 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
Black Magic Probe Yes
J-LINK

Name Description
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.
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.

•
Nucleo G431KB
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32G431KBT6
Frequency 170MHz
Flash 128KB
RAM 32KB
Vendor ST

Please use nucleo_g431kb ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_g431kb]
platform = ststm32
board = nucleo_g431kb


You can override default Nucleo G431KB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_g431kb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_g431kb]
platform = ststm32
board = nucleo_g431kb
; change microcontroller
board_build.mcu = stm32g431kbt6
; change MCU frequency
board_build.f_cpu = 170000000L


Nucleo G431KB supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:nucleo_g431kb]
platform = ststm32
board = nucleo_g431kb
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nucleo G431KB 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
Black Magic Probe Yes
J-LINK

Name Description
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.

•
Nucleo G431RB
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32G431RBT6
Frequency 170MHz
Flash 128KB
RAM 32KB
Vendor ST

Please use nucleo_g431rb ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_g431rb]
platform = ststm32
board = nucleo_g431rb


You can override default Nucleo G431RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_g431rb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_g431rb]
platform = ststm32
board = nucleo_g431rb
; change microcontroller
board_build.mcu = stm32g431rbt6
; change MCU frequency
board_build.f_cpu = 170000000L


Nucleo G431RB supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:nucleo_g431rb]
platform = ststm32
board = nucleo_g431rb
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nucleo G431RB 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
Black Magic Probe Yes
J-LINK

Name Description
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.
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.

•
Nucleo G474RE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32G474RET6
Frequency 170MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use nucleo_g474re ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_g474re]
platform = ststm32
board = nucleo_g474re


You can override default Nucleo G474RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_g474re.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_g474re]
platform = ststm32
board = nucleo_g474re
; change microcontroller
board_build.mcu = stm32g474ret6
; change MCU frequency
board_build.f_cpu = 170000000L


Nucleo G474RE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:nucleo_g474re]
platform = ststm32
board = nucleo_g474re
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Nucleo G474RE 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
Black Magic Probe Yes
J-LINK

Name Description
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.
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.

•
OLIMEXINO-STM32
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103RBT6
Frequency 72MHz
Flash 128KB
RAM 20KB
Vendor Olimex

Please use olimexino ID for board option in "platformio.ini" (Project Configuration File):

[env:olimexino]
platform = ststm32
board = olimexino


You can override default OLIMEXINO-STM32 settings per build environment using board_*** option, where *** is a JSON object path from board manifest olimexino.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:olimexino]
platform = ststm32
board = olimexino
; change microcontroller
board_build.mcu = stm32f103rbt6
; change MCU frequency
board_build.f_cpu = 72000000L


OLIMEXINO-STM32 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:olimexino]
platform = ststm32
board = olimexino
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

OLIMEXINO-STM32 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.
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.

•
Olimex STM32-P405
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F405RGT6
Frequency 168MHz
Flash 1MB
RAM 192KB
Vendor Olimex

Please use olimex_p405 ID for board option in "platformio.ini" (Project Configuration File):

[env:olimex_p405]
platform = ststm32
board = olimex_p405


You can override default Olimex STM32-P405 settings per build environment using board_*** option, where *** is a JSON object path from board manifest olimex_p405.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:olimex_p405]
platform = ststm32
board = olimex_p405
; change microcontroller
board_build.mcu = stm32f405rgt6
; change MCU frequency
board_build.f_cpu = 168000000L


Olimex STM32-P405 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:olimex_p405]
platform = ststm32
board = olimex_p405
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Olimex STM32-P405 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
P-Nucleo WB55RG
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32WB55RG
Frequency 64MHz
Flash 512KB
RAM 192.00KB
Vendor ST

Please use nucleo_wb55rg_p ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_wb55rg_p]
platform = ststm32
board = nucleo_wb55rg_p


You can override default P-Nucleo WB55RG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_wb55rg_p.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_wb55rg_p]
platform = ststm32
board = nucleo_wb55rg_p
; change microcontroller
board_build.mcu = stm32wb55rg
; change MCU frequency
board_build.f_cpu = 64000000L


P-Nucleo WB55RG supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_wb55rg_p]
platform = ststm32
board = nucleo_wb55rg_p
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

P-Nucleo WB55RG 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.

•
Piconomix PX-HER0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L072RB
Frequency 32MHz
Flash 128KB
RAM 20KB
Vendor Piconomix

Please use piconomix_px_her0 ID for board option in "platformio.ini" (Project Configuration File):

[env:piconomix_px_her0]
platform = ststm32
board = piconomix_px_her0


You can override default Piconomix PX-HER0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest piconomix_px_her0.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:piconomix_px_her0]
platform = ststm32
board = piconomix_px_her0
; change microcontroller
board_build.mcu = stm32l072rb
; change MCU frequency
board_build.f_cpu = 32000000L


Piconomix PX-HER0 supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:piconomix_px_her0]
platform = ststm32
board = piconomix_px_her0
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Piconomix PX-HER0 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
PrntrBoard V2
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407RE
Frequency 168MHz
Flash 512KB
RAM 192KB
Vendor PrntrBoard

Please use prntr_v2 ID for board option in "platformio.ini" (Project Configuration File):

[env:prntr_v2]
platform = ststm32
board = prntr_v2


You can override default PrntrBoard V2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest prntr_v2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:prntr_v2]
platform = ststm32
board = prntr_v2
; change microcontroller
board_build.mcu = stm32f407re
; change MCU frequency
board_build.f_cpu = 168000000L


PrntrBoard V2 supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:prntr_v2]
platform = ststm32
board = prntr_v2
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

PrntrBoard V2 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

RAK811 LoRa Tracker

•
RAK811 LoRa Tracker
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L151RBT6
Frequency 32MHz
Flash 128KB
RAM 16KB
Vendor RAK

Please use rak811_tracker ID for board option in "platformio.ini" (Project Configuration File):

[env:rak811_tracker]
platform = ststm32
board = rak811_tracker


You can override default RAK811 LoRa Tracker settings per build environment using board_*** option, where *** is a JSON object path from board manifest rak811_tracker.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:rak811_tracker]
platform = ststm32
board = rak811_tracker
; change microcontroller
board_build.mcu = stm32l151rbt6
; change MCU frequency
board_build.f_cpu = 32000000L


RAK811 LoRa Tracker supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:rak811_tracker]
platform = ststm32
board = rak811_tracker
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RAK811 LoRa Tracker 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

RAK811 LoRa Tracker

•
RAK811 LoRa Tracker
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L151RBT6
Frequency 32MHz
Flash 128KB
RAM 32KB
Vendor RAK

Please use rak811_tracker_32 ID for board option in "platformio.ini" (Project Configuration File):

[env:rak811_tracker_32]
platform = ststm32
board = rak811_tracker_32


You can override default RAK811 LoRa Tracker settings per build environment using board_*** option, where *** is a JSON object path from board manifest rak811_tracker_32.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:rak811_tracker_32]
platform = ststm32
board = rak811_tracker_32
; change microcontroller
board_build.mcu = stm32l151rbt6
; change MCU frequency
board_build.f_cpu = 32000000L


RAK811 LoRa Tracker supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:rak811_tracker_32]
platform = ststm32
board = rak811_tracker_32
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RAK811 LoRa Tracker 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
RHF76 052
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L051C8T6
Frequency 32MHz
Flash 64KB
RAM 8KB
Vendor ST

Please use rhf76_052 ID for board option in "platformio.ini" (Project Configuration File):

[env:rhf76_052]
platform = ststm32
board = rhf76_052


You can override default RHF76 052 settings per build environment using board_*** option, where *** is a JSON object path from board manifest rhf76_052.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:rhf76_052]
platform = ststm32
board = rhf76_052
; change microcontroller
board_build.mcu = stm32l051c8t6
; change MCU frequency
board_build.f_cpu = 32000000L


RHF76 052 supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:rhf76_052]
platform = ststm32
board = rhf76_052
upload_protocol = serial


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RHF76 052 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

RushUp Cloud-JAM

•
RushUp Cloud-JAM
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F401RET6
Frequency 84MHz
Flash 512KB
RAM 96KB
Vendor RushUp

Please use cloud_jam ID for board option in "platformio.ini" (Project Configuration File):

[env:cloud_jam]
platform = ststm32
board = cloud_jam


You can override default RushUp Cloud-JAM settings per build environment using board_*** option, where *** is a JSON object path from board manifest cloud_jam.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:cloud_jam]
platform = ststm32
board = cloud_jam
; change microcontroller
board_build.mcu = stm32f401ret6
; change MCU frequency
board_build.f_cpu = 84000000L


RushUp Cloud-JAM supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:cloud_jam]
platform = ststm32
board = cloud_jam
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RushUp Cloud-JAM 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

RushUp Cloud-JAM L4

•
RushUp Cloud-JAM L4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L476RGT6
Frequency 80MHz
Flash 1MB
RAM 128KB
Vendor RushUp

Please use cloud_jam_l4 ID for board option in "platformio.ini" (Project Configuration File):

[env:cloud_jam_l4]
platform = ststm32
board = cloud_jam_l4


You can override default RushUp Cloud-JAM L4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest cloud_jam_l4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:cloud_jam_l4]
platform = ststm32
board = cloud_jam_l4
; change microcontroller
board_build.mcu = stm32l476rgt6
; change MCU frequency
board_build.f_cpu = 80000000L


RushUp Cloud-JAM L4 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:cloud_jam_l4]
platform = ststm32
board = cloud_jam_l4
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

RushUp Cloud-JAM L4 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST 32F3348DISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F334C8T6
Frequency 72MHz
Flash 64KB
RAM 12KB
Vendor ST

Please use disco_f334c8 ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f334c8]
platform = ststm32
board = disco_f334c8


You can override default ST 32F3348DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f334c8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f334c8]
platform = ststm32
board = disco_f334c8
; change microcontroller
board_build.mcu = stm32f334c8t6
; change MCU frequency
board_build.f_cpu = 72000000L


ST 32F3348DISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f334c8]
platform = ststm32
board = disco_f334c8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32F3348DISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST 32F401CDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F401VCT6
Frequency 84MHz
Flash 256KB
RAM 64KB
Vendor ST

Please use disco_f401vc ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f401vc]
platform = ststm32
board = disco_f401vc


You can override default ST 32F401CDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f401vc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f401vc]
platform = ststm32
board = disco_f401vc
; change microcontroller
board_build.mcu = stm32f401vct6
; change MCU frequency
board_build.f_cpu = 84000000L


ST 32F401CDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f401vc]
platform = ststm32
board = disco_f401vc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32F401CDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST 32F411EDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F411VET6
Frequency 100MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use disco_f411ve ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f411ve]
platform = ststm32
board = disco_f411ve


You can override default ST 32F411EDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f411ve.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f411ve]
platform = ststm32
board = disco_f411ve
; change microcontroller
board_build.mcu = stm32f411vet6
; change MCU frequency
board_build.f_cpu = 100000000L


ST 32F411EDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f411ve]
platform = ststm32
board = disco_f411ve
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32F411EDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST 32F413HDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F413ZHT6
Frequency 100MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use disco_f413zh ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f413zh]
platform = ststm32
board = disco_f413zh


You can override default ST 32F413HDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f413zh.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f413zh]
platform = ststm32
board = disco_f413zh
; change microcontroller
board_build.mcu = stm32f413zht6
; change MCU frequency
board_build.f_cpu = 100000000L


ST 32F413HDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f413zh]
platform = ststm32
board = disco_f413zh
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32F413HDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST 32F429IDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F429ZIT6
Frequency 180MHz
Flash 2MB
RAM 256KB
Vendor ST

Please use disco_f429zi ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f429zi]
platform = ststm32
board = disco_f429zi


You can override default ST 32F429IDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f429zi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f429zi]
platform = ststm32
board = disco_f429zi
; change microcontroller
board_build.mcu = stm32f429zit6
; change MCU frequency
board_build.f_cpu = 180000000L


ST 32F429IDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f429zi]
platform = ststm32
board = disco_f429zi
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32F429IDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST 32F469IDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F469NIH6
Frequency 180MHz
Flash 1MB
RAM 384KB
Vendor ST

Please use disco_f469ni ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f469ni]
platform = ststm32
board = disco_f469ni


You can override default ST 32F469IDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f469ni.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f469ni]
platform = ststm32
board = disco_f469ni
; change microcontroller
board_build.mcu = stm32f469nih6
; change MCU frequency
board_build.f_cpu = 180000000L


ST 32F469IDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f469ni]
platform = ststm32
board = disco_f469ni
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32F469IDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST 32F746GDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F746NGH6
Frequency 216MHz
Flash 1MB
RAM 320KB
Vendor ST

Please use disco_f746ng ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f746ng]
platform = ststm32
board = disco_f746ng


You can override default ST 32F746GDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f746ng.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f746ng]
platform = ststm32
board = disco_f746ng
; change microcontroller
board_build.mcu = stm32f746ngh6
; change MCU frequency
board_build.f_cpu = 216000000L


ST 32F746GDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f746ng]
platform = ststm32
board = disco_f746ng
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32F746GDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST 32F769IDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F769NIH6
Frequency 216MHz
Flash 1MB
RAM 512KB
Vendor ST

Please use disco_f769ni ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f769ni]
platform = ststm32
board = disco_f769ni


You can override default ST 32F769IDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f769ni.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f769ni]
platform = ststm32
board = disco_f769ni
; change microcontroller
board_build.mcu = stm32f769nih6
; change MCU frequency
board_build.f_cpu = 216000000L


ST 32F769IDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f769ni]
platform = ststm32
board = disco_f769ni
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32F769IDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST 32L0538DISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L053C8T6
Frequency 32MHz
Flash 64KB
RAM 8KB
Vendor ST

Please use disco_l053c8 ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_l053c8]
platform = ststm32
board = disco_l053c8


You can override default ST 32L0538DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l053c8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_l053c8]
platform = ststm32
board = disco_l053c8
; change microcontroller
board_build.mcu = stm32l053c8t6
; change MCU frequency
board_build.f_cpu = 32000000L


ST 32L0538DISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_l053c8]
platform = ststm32
board = disco_l053c8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32L0538DISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST 32L100DISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L100RCT6
Frequency 32MHz
Flash 256KB
RAM 16KB
Vendor ST

Please use disco_l100rc ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_l100rc]
platform = ststm32
board = disco_l100rc


You can override default ST 32L100DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l100rc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_l100rc]
platform = ststm32
board = disco_l100rc
; change microcontroller
board_build.mcu = stm32l100rct6
; change MCU frequency
board_build.f_cpu = 32000000L


ST 32L100DISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_l100rc]
platform = ststm32
board = disco_l100rc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32L100DISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.

•
ST 32L476GDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L476VGT6
Frequency 80MHz
Flash 1MB
RAM 128KB
Vendor ST

Please use disco_l476vg ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_l476vg]
platform = ststm32
board = disco_l476vg


You can override default ST 32L476GDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l476vg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_l476vg]
platform = ststm32
board = disco_l476vg
; change microcontroller
board_build.mcu = stm32l476vgt6
; change MCU frequency
board_build.f_cpu = 80000000L


ST 32L476GDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_l476vg]
platform = ststm32
board = disco_l476vg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32L476GDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST 32L496GDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L496AGI6
Frequency 80MHz
Flash 1MB
RAM 320KB
Vendor ST

Please use disco_l496ag ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_l496ag]
platform = ststm32
board = disco_l496ag


You can override default ST 32L496GDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l496ag.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_l496ag]
platform = ststm32
board = disco_l496ag
; change microcontroller
board_build.mcu = stm32l496agi6
; change MCU frequency
board_build.f_cpu = 80000000L


ST 32L496GDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_l496ag]
platform = ststm32
board = disco_l496ag
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST 32L496GDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST B-L475E-IOT01A Discovery kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L475VGT6
Frequency 80MHz
Flash 1MB
RAM 128KB
Vendor ST

Please use disco_l475vg_iot01a ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_l475vg_iot01a]
platform = ststm32
board = disco_l475vg_iot01a


You can override default ST B-L475E-IOT01A Discovery kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l475vg_iot01a.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_l475vg_iot01a]
platform = ststm32
board = disco_l475vg_iot01a
; change microcontroller
board_build.mcu = stm32l475vgt6
; change MCU frequency
board_build.f_cpu = 80000000L


ST B-L475E-IOT01A Discovery kit supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_l475vg_iot01a]
platform = ststm32
board = disco_l475vg_iot01a
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST B-L475E-IOT01A Discovery 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST DISCO-L072CZ-LRWAN1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L072CZ
Frequency 32MHz
Flash 192KB
RAM 20KB
Vendor ST

Please use disco_l072cz_lrwan1 ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_l072cz_lrwan1]
platform = ststm32
board = disco_l072cz_lrwan1


You can override default ST DISCO-L072CZ-LRWAN1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l072cz_lrwan1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_l072cz_lrwan1]
platform = ststm32
board = disco_l072cz_lrwan1
; change microcontroller
board_build.mcu = stm32l072cz
; change MCU frequency
board_build.f_cpu = 32000000L


ST DISCO-L072CZ-LRWAN1 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_l072cz_lrwan1]
platform = ststm32
board = disco_l072cz_lrwan1
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST DISCO-L072CZ-LRWAN1 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Discovery F072RB
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F072RBT6
Frequency 48MHz
Flash 128KB
RAM 16KB
Vendor ST

Please use disco_f072rb ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f072rb]
platform = ststm32
board = disco_f072rb


You can override default ST Discovery F072RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f072rb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f072rb]
platform = ststm32
board = disco_f072rb
; change microcontroller
board_build.mcu = stm32f072rbt6
; change MCU frequency
board_build.f_cpu = 48000000L


ST Discovery F072RB supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f072rb]
platform = ststm32
board = disco_f072rb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Discovery F072RB 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo F030R8
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F030R8T6
Frequency 48MHz
Flash 64KB
RAM 8KB
Vendor ST

Please use nucleo_f030r8 ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f030r8]
platform = ststm32
board = nucleo_f030r8


You can override default ST Nucleo F030R8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f030r8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f030r8]
platform = ststm32
board = nucleo_f030r8
; change microcontroller
board_build.mcu = stm32f030r8t6
; change MCU frequency
board_build.f_cpu = 48000000L


ST Nucleo F030R8 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f030r8]
platform = ststm32
board = nucleo_f030r8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F030R8 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo F031K6
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F031K6T6
Frequency 48MHz
Flash 32KB
RAM 4KB
Vendor ST

Please use nucleo_f031k6 ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f031k6]
platform = ststm32
board = nucleo_f031k6


You can override default ST Nucleo F031K6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f031k6.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f031k6]
platform = ststm32
board = nucleo_f031k6
; change microcontroller
board_build.mcu = stm32f031k6t6
; change MCU frequency
board_build.f_cpu = 48000000L


ST Nucleo F031K6 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f031k6]
platform = ststm32
board = nucleo_f031k6
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F031K6 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST Nucleo F042K6
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F042K6T6
Frequency 48MHz
Flash 32KB
RAM 6KB
Vendor ST

Please use nucleo_f042k6 ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f042k6]
platform = ststm32
board = nucleo_f042k6


You can override default ST Nucleo F042K6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f042k6.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f042k6]
platform = ststm32
board = nucleo_f042k6
; change microcontroller
board_build.mcu = stm32f042k6t6
; change MCU frequency
board_build.f_cpu = 48000000L


ST Nucleo F042K6 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f042k6]
platform = ststm32
board = nucleo_f042k6
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F042K6 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST Nucleo F070RB
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F070RBT6
Frequency 48MHz
Flash 128KB
RAM 16KB
Vendor ST

Please use nucleo_f070rb ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f070rb]
platform = ststm32
board = nucleo_f070rb


You can override default ST Nucleo F070RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f070rb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f070rb]
platform = ststm32
board = nucleo_f070rb
; change microcontroller
board_build.mcu = stm32f070rbt6
; change MCU frequency
board_build.f_cpu = 48000000L


ST Nucleo F070RB supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f070rb]
platform = ststm32
board = nucleo_f070rb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F070RB 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo F072RB
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F072RBT6
Frequency 48MHz
Flash 128KB
RAM 16KB
Vendor ST

Please use nucleo_f072rb ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f072rb]
platform = ststm32
board = nucleo_f072rb


You can override default ST Nucleo F072RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f072rb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f072rb]
platform = ststm32
board = nucleo_f072rb
; change microcontroller
board_build.mcu = stm32f072rbt6
; change MCU frequency
board_build.f_cpu = 48000000L


ST Nucleo F072RB supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f072rb]
platform = ststm32
board = nucleo_f072rb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F072RB 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST Nucleo F091RC
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F091RCT6
Frequency 48MHz
Flash 256KB
RAM 32KB
Vendor ST

Please use nucleo_f091rc ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f091rc]
platform = ststm32
board = nucleo_f091rc


You can override default ST Nucleo F091RC settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f091rc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f091rc]
platform = ststm32
board = nucleo_f091rc
; change microcontroller
board_build.mcu = stm32f091rct6
; change MCU frequency
board_build.f_cpu = 48000000L


ST Nucleo F091RC supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f091rc]
platform = ststm32
board = nucleo_f091rc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F091RC 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo F103RB
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103RBT6
Frequency 72MHz
Flash 128KB
RAM 20KB
Vendor ST

Please use nucleo_f103rb ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f103rb]
platform = ststm32
board = nucleo_f103rb


You can override default ST Nucleo F103RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f103rb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f103rb]
platform = ststm32
board = nucleo_f103rb
; change microcontroller
board_build.mcu = stm32f103rbt6
; change MCU frequency
board_build.f_cpu = 72000000L


ST Nucleo F103RB supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f103rb]
platform = ststm32
board = nucleo_f103rb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F103RB 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.
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.

•
ST Nucleo F207ZG
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F207ZGT6
Frequency 120MHz
Flash 1MB
RAM 128KB
Vendor ST

Please use nucleo_f207zg ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f207zg]
platform = ststm32
board = nucleo_f207zg


You can override default ST Nucleo F207ZG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f207zg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f207zg]
platform = ststm32
board = nucleo_f207zg
; change microcontroller
board_build.mcu = stm32f207zgt6
; change MCU frequency
board_build.f_cpu = 120000000L


ST Nucleo F207ZG supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f207zg]
platform = ststm32
board = nucleo_f207zg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F207ZG 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo F302R8
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F302R8T6
Frequency 72MHz
Flash 64KB
RAM 16KB
Vendor ST

Please use nucleo_f302r8 ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f302r8]
platform = ststm32
board = nucleo_f302r8


You can override default ST Nucleo F302R8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f302r8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f302r8]
platform = ststm32
board = nucleo_f302r8
; change microcontroller
board_build.mcu = stm32f302r8t6
; change MCU frequency
board_build.f_cpu = 72000000L


ST Nucleo F302R8 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f302r8]
platform = ststm32
board = nucleo_f302r8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F302R8 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo F303K8
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F303K8T6
Frequency 72MHz
Flash 64KB
RAM 12KB
Vendor ST

Please use nucleo_f303k8 ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f303k8]
platform = ststm32
board = nucleo_f303k8


You can override default ST Nucleo F303K8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f303k8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f303k8]
platform = ststm32
board = nucleo_f303k8
; change microcontroller
board_build.mcu = stm32f303k8t6
; change MCU frequency
board_build.f_cpu = 72000000L


ST Nucleo F303K8 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f303k8]
platform = ststm32
board = nucleo_f303k8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F303K8 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo F303RE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F303RET6
Frequency 72MHz
Flash 512KB
RAM 64KB
Vendor ST

Please use nucleo_f303re ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f303re]
platform = ststm32
board = nucleo_f303re


You can override default ST Nucleo F303RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f303re.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f303re]
platform = ststm32
board = nucleo_f303re
; change microcontroller
board_build.mcu = stm32f303ret6
; change MCU frequency
board_build.f_cpu = 72000000L


ST Nucleo F303RE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f303re]
platform = ststm32
board = nucleo_f303re
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F303RE 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo F303ZE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F303ZET6
Frequency 72MHz
Flash 512KB
RAM 64KB
Vendor ST

Please use nucleo_f303ze ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f303ze]
platform = ststm32
board = nucleo_f303ze


You can override default ST Nucleo F303ZE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f303ze.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f303ze]
platform = ststm32
board = nucleo_f303ze
; change microcontroller
board_build.mcu = stm32f303zet6
; change MCU frequency
board_build.f_cpu = 72000000L


ST Nucleo F303ZE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f303ze]
platform = ststm32
board = nucleo_f303ze
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F303ZE 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST Nucleo F334R8
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F334R8T6
Frequency 72MHz
Flash 64KB
RAM 16KB
Vendor ST

Please use nucleo_f334r8 ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f334r8]
platform = ststm32
board = nucleo_f334r8


You can override default ST Nucleo F334R8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f334r8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f334r8]
platform = ststm32
board = nucleo_f334r8
; change microcontroller
board_build.mcu = stm32f334r8t6
; change MCU frequency
board_build.f_cpu = 72000000L


ST Nucleo F334R8 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f334r8]
platform = ststm32
board = nucleo_f334r8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F334R8 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo F401RE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F401RET6
Frequency 84MHz
Flash 512KB
RAM 96KB
Vendor ST

Please use nucleo_f401re ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f401re]
platform = ststm32
board = nucleo_f401re


You can override default ST Nucleo F401RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f401re.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f401re]
platform = ststm32
board = nucleo_f401re
; change microcontroller
board_build.mcu = stm32f401ret6
; change MCU frequency
board_build.f_cpu = 84000000L


ST Nucleo F401RE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f401re]
platform = ststm32
board = nucleo_f401re
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F401RE 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.
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.
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.

•
ST Nucleo F410RB
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F410RBT6
Frequency 100MHz
Flash 128KB
RAM 32KB
Vendor ST

Please use nucleo_f410rb ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f410rb]
platform = ststm32
board = nucleo_f410rb


You can override default ST Nucleo F410RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f410rb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f410rb]
platform = ststm32
board = nucleo_f410rb
; change microcontroller
board_build.mcu = stm32f410rbt6
; change MCU frequency
board_build.f_cpu = 100000000L


ST Nucleo F410RB supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f410rb]
platform = ststm32
board = nucleo_f410rb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F410RB 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST Nucleo F411RE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F411RET6
Frequency 100MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use nucleo_f411re ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f411re]
platform = ststm32
board = nucleo_f411re


You can override default ST Nucleo F411RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f411re.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f411re]
platform = ststm32
board = nucleo_f411re
; change microcontroller
board_build.mcu = stm32f411ret6
; change MCU frequency
board_build.f_cpu = 100000000L


ST Nucleo F411RE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f411re]
platform = ststm32
board = nucleo_f411re
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F411RE 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo F412ZG
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F412ZGT6
Frequency 100MHz
Flash 1MB
RAM 256KB
Vendor ST

Please use nucleo_f412zg ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f412zg]
platform = ststm32
board = nucleo_f412zg


You can override default ST Nucleo F412ZG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f412zg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f412zg]
platform = ststm32
board = nucleo_f412zg
; change microcontroller
board_build.mcu = stm32f412zgt6
; change MCU frequency
board_build.f_cpu = 100000000L


ST Nucleo F412ZG supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f412zg]
platform = ststm32
board = nucleo_f412zg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F412ZG 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo F413ZH
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F413ZHT6
Frequency 100MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use nucleo_f413zh ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f413zh]
platform = ststm32
board = nucleo_f413zh


You can override default ST Nucleo F413ZH settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f413zh.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f413zh]
platform = ststm32
board = nucleo_f413zh
; change microcontroller
board_build.mcu = stm32f413zht6
; change MCU frequency
board_build.f_cpu = 100000000L


ST Nucleo F413ZH supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f413zh]
platform = ststm32
board = nucleo_f413zh
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F413ZH 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo F429ZI
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F429ZIT6
Frequency 180MHz
Flash 2MB
RAM 256KB
Vendor ST

Please use nucleo_f429zi ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f429zi]
platform = ststm32
board = nucleo_f429zi


You can override default ST Nucleo F429ZI settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f429zi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f429zi]
platform = ststm32
board = nucleo_f429zi
; change microcontroller
board_build.mcu = stm32f429zit6
; change MCU frequency
board_build.f_cpu = 180000000L


ST Nucleo F429ZI supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f429zi]
platform = ststm32
board = nucleo_f429zi
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F429ZI 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo F439ZI
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F439ZIT6
Frequency 180MHz
Flash 2MB
RAM 256KB
Vendor ST

Please use nucleo_f439zi ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f439zi]
platform = ststm32
board = nucleo_f439zi


You can override default ST Nucleo F439ZI settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f439zi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f439zi]
platform = ststm32
board = nucleo_f439zi
; change microcontroller
board_build.mcu = stm32f439zit6
; change MCU frequency
board_build.f_cpu = 180000000L


ST Nucleo F439ZI supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f439zi]
platform = ststm32
board = nucleo_f439zi
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F439ZI 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST Nucleo F446RE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F446RET6
Frequency 180MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use nucleo_f446re ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f446re]
platform = ststm32
board = nucleo_f446re


You can override default ST Nucleo F446RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f446re.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f446re]
platform = ststm32
board = nucleo_f446re
; change microcontroller
board_build.mcu = stm32f446ret6
; change MCU frequency
board_build.f_cpu = 180000000L


ST Nucleo F446RE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f446re]
platform = ststm32
board = nucleo_f446re
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F446RE 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo F446ZE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F446ZET6
Frequency 180MHz
Flash 512KB
RAM 128KB
Vendor ST

Please use nucleo_f446ze ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f446ze]
platform = ststm32
board = nucleo_f446ze


You can override default ST Nucleo F446ZE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f446ze.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f446ze]
platform = ststm32
board = nucleo_f446ze
; change microcontroller
board_build.mcu = stm32f446zet6
; change MCU frequency
board_build.f_cpu = 180000000L


ST Nucleo F446ZE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f446ze]
platform = ststm32
board = nucleo_f446ze
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F446ZE 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo F722ZE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F722ZET6
Frequency 216MHz
Flash 512KB
RAM 256KB
Vendor ST

Please use nucleo_f722ze ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f722ze]
platform = ststm32
board = nucleo_f722ze


You can override default ST Nucleo F722ZE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f722ze.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f722ze]
platform = ststm32
board = nucleo_f722ze
; change microcontroller
board_build.mcu = stm32f722zet6
; change MCU frequency
board_build.f_cpu = 216000000L


ST Nucleo F722ZE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f722ze]
platform = ststm32
board = nucleo_f722ze
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F722ZE 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.

•
ST Nucleo F746ZG
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F746ZGT6
Frequency 216MHz
Flash 1MB
RAM 320KB
Vendor ST

Please use nucleo_f746zg ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f746zg]
platform = ststm32
board = nucleo_f746zg


You can override default ST Nucleo F746ZG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f746zg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f746zg]
platform = ststm32
board = nucleo_f746zg
; change microcontroller
board_build.mcu = stm32f746zgt6
; change MCU frequency
board_build.f_cpu = 216000000L


ST Nucleo F746ZG supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f746zg]
platform = ststm32
board = nucleo_f746zg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F746ZG 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo F756ZG
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F756ZG
Frequency 216MHz
Flash 1MB
RAM 320KB
Vendor ST

Please use nucleo_f756zg ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f756zg]
platform = ststm32
board = nucleo_f756zg


You can override default ST Nucleo F756ZG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f756zg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f756zg]
platform = ststm32
board = nucleo_f756zg
; change microcontroller
board_build.mcu = stm32f756zg
; change MCU frequency
board_build.f_cpu = 216000000L


ST Nucleo F756ZG supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f756zg]
platform = ststm32
board = nucleo_f756zg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F756ZG 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo F767ZI
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F767ZIT6
Frequency 216MHz
Flash 2MB
RAM 512KB
Vendor ST

Please use nucleo_f767zi ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_f767zi]
platform = ststm32
board = nucleo_f767zi


You can override default ST Nucleo F767ZI settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f767zi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_f767zi]
platform = ststm32
board = nucleo_f767zi
; change microcontroller
board_build.mcu = stm32f767zit6
; change MCU frequency
board_build.f_cpu = 216000000L


ST Nucleo F767ZI supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_f767zi]
platform = ststm32
board = nucleo_f767zi
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo F767ZI 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo H743ZI
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32H743ZIT6
Frequency 400MHz
Flash 2MB
RAM 512KB
Vendor ST

Please use nucleo_h743zi ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_h743zi]
platform = ststm32
board = nucleo_h743zi


You can override default ST Nucleo H743ZI settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_h743zi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_h743zi]
platform = ststm32
board = nucleo_h743zi
; change microcontroller
board_build.mcu = stm32h743zit6
; change MCU frequency
board_build.f_cpu = 400000000L


ST Nucleo H743ZI supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_h743zi]
platform = ststm32
board = nucleo_h743zi
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo H743ZI 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo L011K4
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L011K4T6
Frequency 32MHz
Flash 16KB
RAM 2KB
Vendor ST

Please use nucleo_l011k4 ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l011k4]
platform = ststm32
board = nucleo_l011k4


You can override default ST Nucleo L011K4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l011k4.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l011k4]
platform = ststm32
board = nucleo_l011k4
; change microcontroller
board_build.mcu = stm32l011k4t6
; change MCU frequency
board_build.f_cpu = 32000000L


ST Nucleo L011K4 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l011k4]
platform = ststm32
board = nucleo_l011k4
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L011K4 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.

•
ST Nucleo L031K6
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L031K6T6
Frequency 32MHz
Flash 32KB
RAM 8KB
Vendor ST

Please use nucleo_l031k6 ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l031k6]
platform = ststm32
board = nucleo_l031k6


You can override default ST Nucleo L031K6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l031k6.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l031k6]
platform = ststm32
board = nucleo_l031k6
; change microcontroller
board_build.mcu = stm32l031k6t6
; change MCU frequency
board_build.f_cpu = 32000000L


ST Nucleo L031K6 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l031k6]
platform = ststm32
board = nucleo_l031k6
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L031K6 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo L053R8
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L053R8T6
Frequency 32MHz
Flash 64KB
RAM 8KB
Vendor ST

Please use nucleo_l053r8 ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l053r8]
platform = ststm32
board = nucleo_l053r8


You can override default ST Nucleo L053R8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l053r8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l053r8]
platform = ststm32
board = nucleo_l053r8
; change microcontroller
board_build.mcu = stm32l053r8t6
; change MCU frequency
board_build.f_cpu = 32000000L


ST Nucleo L053R8 supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l053r8]
platform = ststm32
board = nucleo_l053r8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L053R8 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo L073RZ
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L073RZ
Frequency 32MHz
Flash 192KB
RAM 20KB
Vendor ST

Please use nucleo_l073rz ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l073rz]
platform = ststm32
board = nucleo_l073rz


You can override default ST Nucleo L073RZ settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l073rz.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l073rz]
platform = ststm32
board = nucleo_l073rz
; change microcontroller
board_build.mcu = stm32l073rz
; change MCU frequency
board_build.f_cpu = 32000000L


ST Nucleo L073RZ supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l073rz]
platform = ststm32
board = nucleo_l073rz
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L073RZ 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo L152RE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L152RET6
Frequency 32MHz
Flash 512KB
RAM 80KB
Vendor ST

Please use nucleo_l152re ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l152re]
platform = ststm32
board = nucleo_l152re


You can override default ST Nucleo L152RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l152re.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l152re]
platform = ststm32
board = nucleo_l152re
; change microcontroller
board_build.mcu = stm32l152ret6
; change MCU frequency
board_build.f_cpu = 32000000L


ST Nucleo L152RE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l152re]
platform = ststm32
board = nucleo_l152re
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L152RE 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo L412KB
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L412KBU6
Frequency 80MHz
Flash 128KB
RAM 40KB
Vendor ST

Please use nucleo_l412kb ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l412kb]
platform = ststm32
board = nucleo_l412kb


You can override default ST Nucleo L412KB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l412kb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l412kb]
platform = ststm32
board = nucleo_l412kb
; change microcontroller
board_build.mcu = stm32l412kbu6
; change MCU frequency
board_build.f_cpu = 80000000L


ST Nucleo L412KB supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l412kb]
platform = ststm32
board = nucleo_l412kb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L412KB 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST Nucleo L432KC
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L432KCU6
Frequency 80MHz
Flash 256KB
RAM 64KB
Vendor ST

Please use nucleo_l432kc ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l432kc]
platform = ststm32
board = nucleo_l432kc


You can override default ST Nucleo L432KC settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l432kc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l432kc]
platform = ststm32
board = nucleo_l432kc
; change microcontroller
board_build.mcu = stm32l432kcu6
; change MCU frequency
board_build.f_cpu = 80000000L


ST Nucleo L432KC supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l432kc]
platform = ststm32
board = nucleo_l432kc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L432KC 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo L433RC-P
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L433RC
Frequency 80MHz
Flash 256KB
RAM 64KB
Vendor ST

Please use nucleo_l433rc_p ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l433rc_p]
platform = ststm32
board = nucleo_l433rc_p


You can override default ST Nucleo L433RC-P settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l433rc_p.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l433rc_p]
platform = ststm32
board = nucleo_l433rc_p
; change microcontroller
board_build.mcu = stm32l433rc
; change MCU frequency
board_build.f_cpu = 80000000L


ST Nucleo L433RC-P supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l433rc_p]
platform = ststm32
board = nucleo_l433rc_p
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L433RC-P 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST Nucleo L452RE
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L452RET6
Frequency 80MHz
Flash 256KB
RAM 64KB
Vendor ST

Please use nucleo_l452re ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l452re]
platform = ststm32
board = nucleo_l452re


You can override default ST Nucleo L452RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l452re.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l452re]
platform = ststm32
board = nucleo_l452re
; change microcontroller
board_build.mcu = stm32l452ret6
; change MCU frequency
board_build.f_cpu = 80000000L


ST Nucleo L452RE supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l452re]
platform = ststm32
board = nucleo_l452re
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L452RE 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
ST Nucleo L476RG
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L476RGT6
Frequency 80MHz
Flash 1MB
RAM 128KB
Vendor ST

Please use nucleo_l476rg ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l476rg]
platform = ststm32
board = nucleo_l476rg


You can override default ST Nucleo L476RG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l476rg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l476rg]
platform = ststm32
board = nucleo_l476rg
; change microcontroller
board_build.mcu = stm32l476rgt6
; change MCU frequency
board_build.f_cpu = 80000000L


ST Nucleo L476RG supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l476rg]
platform = ststm32
board = nucleo_l476rg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L476RG 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST Nucleo L486RG
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L486RGT6
Frequency 80MHz
Flash 1MB
RAM 128KB
Vendor ST

Please use nucleo_l486rg ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l486rg]
platform = ststm32
board = nucleo_l486rg


You can override default ST Nucleo L486RG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l486rg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l486rg]
platform = ststm32
board = nucleo_l486rg
; change microcontroller
board_build.mcu = stm32l486rgt6
; change MCU frequency
board_build.f_cpu = 80000000L


ST Nucleo L486RG supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l486rg]
platform = ststm32
board = nucleo_l486rg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L486RG 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

ST Nucleo L496ZG

•
ST Nucleo L496ZG
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L496ZGT6
Frequency 80MHz
Flash 1MB
RAM 128KB
Vendor ST

Please use nucleo_l496zg ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l496zg]
platform = ststm32
board = nucleo_l496zg


You can override default ST Nucleo L496ZG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l496zg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l496zg]
platform = ststm32
board = nucleo_l496zg
; change microcontroller
board_build.mcu = stm32l496zgt6
; change MCU frequency
board_build.f_cpu = 80000000L


ST Nucleo L496ZG supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l496zg]
platform = ststm32
board = nucleo_l496zg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L496ZG 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

ST Nucleo L496ZG-P

•
ST Nucleo L496ZG-P
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L496ZGT6P
Frequency 80MHz
Flash 1MB
RAM 320KB
Vendor ST

Please use nucleo_l496zg_p ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l496zg_p]
platform = ststm32
board = nucleo_l496zg_p


You can override default ST Nucleo L496ZG-P settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l496zg_p.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l496zg_p]
platform = ststm32
board = nucleo_l496zg_p
; change microcontroller
board_build.mcu = stm32l496zgt6p
; change MCU frequency
board_build.f_cpu = 80000000L


ST Nucleo L496ZG-P supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l496zg_p]
platform = ststm32
board = nucleo_l496zg_p
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L496ZG-P 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Nucleo L4R5ZI
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L4R5ZIT6
Frequency 120MHz
Flash 2MB
RAM 640KB
Vendor ST

Please use nucleo_l4r5zi ID for board option in "platformio.ini" (Project Configuration File):

[env:nucleo_l4r5zi]
platform = ststm32
board = nucleo_l4r5zi


You can override default ST Nucleo L4R5ZI settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l4r5zi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:nucleo_l4r5zi]
platform = ststm32
board = nucleo_l4r5zi
; change microcontroller
board_build.mcu = stm32l4r5zit6
; change MCU frequency
board_build.f_cpu = 120000000L


ST Nucleo L4R5ZI supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:nucleo_l4r5zi]
platform = ststm32
board = nucleo_l4r5zi
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Nucleo L4R5ZI 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST STM32F0308DISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F030R8T6
Frequency 48MHz
Flash 64KB
RAM 8KB
Vendor ST

Please use disco_f030r8 ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f030r8]
platform = ststm32
board = disco_f030r8


You can override default ST STM32F0308DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f030r8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f030r8]
platform = ststm32
board = disco_f030r8
; change microcontroller
board_build.mcu = stm32f030r8t6
; change MCU frequency
board_build.f_cpu = 48000000L


ST STM32F0308DISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f030r8]
platform = ststm32
board = disco_f030r8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST STM32F0308DISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST STM32F0DISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F051R8T6
Frequency 48MHz
Flash 64KB
RAM 8KB
Vendor ST

Please use disco_f051r8 ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f051r8]
platform = ststm32
board = disco_f051r8


You can override default ST STM32F0DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f051r8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f051r8]
platform = ststm32
board = disco_f051r8
; change microcontroller
board_build.mcu = stm32f051r8t6
; change MCU frequency
board_build.f_cpu = 48000000L


ST STM32F0DISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f051r8]
platform = ststm32
board = disco_f051r8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST STM32F0DISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST STM32F3DISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F303VCT6
Frequency 72MHz
Flash 256KB
RAM 48KB
Vendor ST

Please use disco_f303vc ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f303vc]
platform = ststm32
board = disco_f303vc


You can override default ST STM32F3DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f303vc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f303vc]
platform = ststm32
board = disco_f303vc
; change microcontroller
board_build.mcu = stm32f303vct6
; change MCU frequency
board_build.f_cpu = 72000000L


ST STM32F3DISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f303vc]
platform = ststm32
board = disco_f303vc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST STM32F3DISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.
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.
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.

•
ST STM32F4DISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VGT6
Frequency 168MHz
Flash 1MB
RAM 128KB
Vendor ST

Please use disco_f407vg ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f407vg]
platform = ststm32
board = disco_f407vg


You can override default ST STM32F4DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f407vg.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f407vg]
platform = ststm32
board = disco_f407vg
; change microcontroller
board_build.mcu = stm32f407vgt6
; change MCU frequency
board_build.f_cpu = 168000000L


ST STM32F4DISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f407vg]
platform = ststm32
board = disco_f407vg
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST STM32F4DISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.
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.
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.
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.

•
ST STM32L073Z-EVAL
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L073VZT6
Frequency 32MHz
Flash 192KB
RAM 20KB
Vendor ST

Please use eval_l073z ID for board option in "platformio.ini" (Project Configuration File):

[env:eval_l073z]
platform = ststm32
board = eval_l073z


You can override default ST STM32L073Z-EVAL settings per build environment using board_*** option, where *** is a JSON object path from board manifest eval_l073z.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:eval_l073z]
platform = ststm32
board = eval_l073z
; change microcontroller
board_build.mcu = stm32l073vzt6
; change MCU frequency
board_build.f_cpu = 32000000L


ST STM32L073Z-EVAL supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:eval_l073z]
platform = ststm32
board = eval_l073z
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST STM32L073Z-EVAL 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.

•
ST STM32LDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L152RBT6
Frequency 32MHz
Flash 128KB
RAM 16KB
Vendor ST

Please use disco_l152rb ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_l152rb]
platform = ststm32
board = disco_l152rb


You can override default ST STM32LDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l152rb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_l152rb]
platform = ststm32
board = disco_l152rb
; change microcontroller
board_build.mcu = stm32l152rbt6
; change MCU frequency
board_build.f_cpu = 32000000L


ST STM32LDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_l152rb]
platform = ststm32
board = disco_l152rb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST STM32LDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.
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.

•
ST STM32VLDISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F100RBT6
Frequency 24MHz
Flash 128KB
RAM 8KB
Vendor ST

Please use disco_f100rb ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f100rb]
platform = ststm32
board = disco_f100rb


You can override default ST STM32VLDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f100rb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f100rb]
platform = ststm32
board = disco_f100rb
; change microcontroller
board_build.mcu = stm32f100rbt6
; change MCU frequency
board_build.f_cpu = 24000000L


ST STM32VLDISCOVERY supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f100rb]
platform = ststm32
board = disco_f100rb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST STM32VLDISCOVERY 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.
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.

•
ST Sensor Node
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L476JG
Frequency 80MHz
Flash 1MB
RAM 128KB
Vendor Avnet Silica

Please use silica_sensor_node ID for board option in "platformio.ini" (Project Configuration File):

[env:silica_sensor_node]
platform = ststm32
board = silica_sensor_node


You can override default ST Sensor Node settings per build environment using board_*** option, where *** is a JSON object path from board manifest silica_sensor_node.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:silica_sensor_node]
platform = ststm32
board = silica_sensor_node
; change microcontroller
board_build.mcu = stm32l476jg
; change MCU frequency
board_build.f_cpu = 80000000L


ST Sensor Node supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:silica_sensor_node]
platform = ststm32
board = silica_sensor_node
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST Sensor Node 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
STEVAL-FCU001V1 Flight controller unit evaluation board
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F401CCU6
Frequency 84MHz
Flash 256KB
RAM 64KB
Vendor ST

Please use steval_fcu001v1 ID for board option in "platformio.ini" (Project Configuration File):

[env:steval_fcu001v1]
platform = ststm32
board = steval_fcu001v1


You can override default STEVAL-FCU001V1 Flight controller unit evaluation board settings per build environment using board_*** option, where *** is a JSON object path from board manifest steval_fcu001v1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:steval_fcu001v1]
platform = ststm32
board = steval_fcu001v1
; change microcontroller
board_build.mcu = stm32f401ccu6
; change MCU frequency
board_build.f_cpu = 84000000L


STEVAL-FCU001V1 Flight controller unit evaluation board supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:steval_fcu001v1]
platform = ststm32
board = steval_fcu001v1
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STEVAL-FCU001V1 Flight controller unit evaluation board 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
STM32-E407
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407ZGT6
Frequency 168MHz
Flash 1MB
RAM 128KB
Vendor Olimex

Please use olimex_e407 ID for board option in "platformio.ini" (Project Configuration File):

[env:olimex_e407]
platform = ststm32
board = olimex_e407


You can override default STM32-E407 settings per build environment using board_*** option, where *** is a JSON object path from board manifest olimex_e407.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:olimex_e407]
platform = ststm32
board = olimex_e407
; change microcontroller
board_build.mcu = stm32f407zgt6
; change MCU frequency
board_build.f_cpu = 168000000L


STM32-E407 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:olimex_e407]
platform = ststm32
board = olimex_e407
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32-E407 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32-H407
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407ZGT6
Frequency 168MHz
Flash 1MB
RAM 128KB
Vendor Olimex

Please use olimex_h407 ID for board option in "platformio.ini" (Project Configuration File):

[env:olimex_h407]
platform = ststm32
board = olimex_h407


You can override default STM32-H407 settings per build environment using board_*** option, where *** is a JSON object path from board manifest olimex_h407.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:olimex_h407]
platform = ststm32
board = olimex_h407
; change microcontroller
board_build.mcu = stm32f407zgt6
; change MCU frequency
board_build.f_cpu = 168000000L


STM32-H407 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:olimex_h407]
platform = ststm32
board = olimex_h407
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32-H407 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM3210C-EVAL
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F107VCT6
Frequency 72MHz
Flash 256KB
RAM 64KB
Vendor ST

Please use eval_f107vc ID for board option in "platformio.ini" (Project Configuration File):

[env:eval_f107vc]
platform = ststm32
board = eval_f107vc


You can override default STM3210C-EVAL settings per build environment using board_*** option, where *** is a JSON object path from board manifest eval_f107vc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:eval_f107vc]
platform = ststm32
board = eval_f107vc
; change microcontroller
board_build.mcu = stm32f107vct6
; change MCU frequency
board_build.f_cpu = 72000000L


STM3210C-EVAL supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:eval_f107vc]
platform = ststm32
board = eval_f107vc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM3210C-EVAL does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
STM32373C-EVAL
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F373VCT6
Frequency 72MHz
Flash 256KB
RAM 32KB
Vendor ST

Please use eval_f373vc ID for board option in "platformio.ini" (Project Configuration File):

[env:eval_f373vc]
platform = ststm32
board = eval_f373vc


You can override default STM32373C-EVAL settings per build environment using board_*** option, where *** is a JSON object path from board manifest eval_f373vc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:eval_f373vc]
platform = ststm32
board = eval_f373vc
; change microcontroller
board_build.mcu = stm32f373vct6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32373C-EVAL supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:eval_f373vc]
platform = ststm32
board = eval_f373vc
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32373C-EVAL does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
STM32F072-EVAL
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F072VBT6
Frequency 48MHz
Flash 128KB
RAM 16KB
Vendor ST

Please use eval_f072vb ID for board option in "platformio.ini" (Project Configuration File):

[env:eval_f072vb]
platform = ststm32
board = eval_f072vb


You can override default STM32F072-EVAL settings per build environment using board_*** option, where *** is a JSON object path from board manifest eval_f072vb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:eval_f072vb]
platform = ststm32
board = eval_f072vb
; change microcontroller
board_build.mcu = stm32f072vbt6
; change MCU frequency
board_build.f_cpu = 48000000L


STM32F072-EVAL supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:eval_f072vb]
platform = ststm32
board = eval_f072vb
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F072-EVAL does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.

Compatible Tools On-board Default
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
STM32F103C8 (20k RAM. 64k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103C8T6
Frequency 72MHz
Flash 64KB
RAM 20KB
Vendor Generic

Please use genericSTM32F103C8 ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103C8]
platform = ststm32
board = genericSTM32F103C8


You can override default STM32F103C8 (20k RAM. 64k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103C8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103C8]
platform = ststm32
board = genericSTM32F103C8
; change microcontroller
board_build.mcu = stm32f103c8t6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103C8 (20k RAM. 64k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103C8]
platform = ststm32
board = genericSTM32F103C8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103C8 (20k RAM. 64k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.
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.

•
STM32F103CB (20k RAM. 128k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103CBT6
Frequency 72MHz
Flash 128KB
RAM 20KB
Vendor Generic

Please use genericSTM32F103CB ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103CB]
platform = ststm32
board = genericSTM32F103CB


You can override default STM32F103CB (20k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103CB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103CB]
platform = ststm32
board = genericSTM32F103CB
; change microcontroller
board_build.mcu = stm32f103cbt6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103CB (20k RAM. 128k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103CB]
platform = ststm32
board = genericSTM32F103CB
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103CB (20k RAM. 128k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103R8 (20k RAM. 64 Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103R8T6
Frequency 72MHz
Flash 64KB
RAM 20KB
Vendor Generic

Please use genericSTM32F103R8 ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103R8]
platform = ststm32
board = genericSTM32F103R8


You can override default STM32F103R8 (20k RAM. 64 Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103R8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103R8]
platform = ststm32
board = genericSTM32F103R8
; change microcontroller
board_build.mcu = stm32f103r8t6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103R8 (20k RAM. 64 Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103R8]
platform = ststm32
board = genericSTM32F103R8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103R8 (20k RAM. 64 Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103RB (20k RAM. 128k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103RBT6
Frequency 72MHz
Flash 128KB
RAM 20KB
Vendor Generic

Please use genericSTM32F103RB ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103RB]
platform = ststm32
board = genericSTM32F103RB


You can override default STM32F103RB (20k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103RB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103RB]
platform = ststm32
board = genericSTM32F103RB
; change microcontroller
board_build.mcu = stm32f103rbt6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103RB (20k RAM. 128k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103RB]
platform = ststm32
board = genericSTM32F103RB
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103RB (20k RAM. 128k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.
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.

•
STM32F103RC (48k RAM. 256k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103RCT6
Frequency 72MHz
Flash 256KB
RAM 48KB
Vendor Generic

Please use genericSTM32F103RC ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103RC]
platform = ststm32
board = genericSTM32F103RC


You can override default STM32F103RC (48k RAM. 256k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103RC.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103RC]
platform = ststm32
board = genericSTM32F103RC
; change microcontroller
board_build.mcu = stm32f103rct6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103RC (48k RAM. 256k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103RC]
platform = ststm32
board = genericSTM32F103RC
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103RC (48k RAM. 256k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103RE (64k RAM. 512k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103RET6
Frequency 72MHz
Flash 512KB
RAM 64KB
Vendor Generic

Please use genericSTM32F103RE ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103RE]
platform = ststm32
board = genericSTM32F103RE


You can override default STM32F103RE (64k RAM. 512k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103RE.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103RE]
platform = ststm32
board = genericSTM32F103RE
; change microcontroller
board_build.mcu = stm32f103ret6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103RE (64k RAM. 512k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103RE]
platform = ststm32
board = genericSTM32F103RE
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103RE (64k RAM. 512k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103T8 (20k RAM. 64k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103T8T6
Frequency 72MHz
Flash 64KB
RAM 20KB
Vendor Generic

Please use genericSTM32F103T8 ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103T8]
platform = ststm32
board = genericSTM32F103T8


You can override default STM32F103T8 (20k RAM. 64k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103T8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103T8]
platform = ststm32
board = genericSTM32F103T8
; change microcontroller
board_build.mcu = stm32f103t8t6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103T8 (20k RAM. 64k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103T8]
platform = ststm32
board = genericSTM32F103T8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103T8 (20k RAM. 64k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103TB (20k RAM. 128k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103TBT6
Frequency 72MHz
Flash 128KB
RAM 20KB
Vendor Generic

Please use genericSTM32F103TB ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103TB]
platform = ststm32
board = genericSTM32F103TB


You can override default STM32F103TB (20k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103TB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103TB]
platform = ststm32
board = genericSTM32F103TB
; change microcontroller
board_build.mcu = stm32f103tbt6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103TB (20k RAM. 128k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103TB]
platform = ststm32
board = genericSTM32F103TB
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103TB (20k RAM. 128k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103VB (20k RAM. 128k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103VBT6
Frequency 72MHz
Flash 128KB
RAM 20KB
Vendor Generic

Please use genericSTM32F103VB ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103VB]
platform = ststm32
board = genericSTM32F103VB


You can override default STM32F103VB (20k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103VB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103VB]
platform = ststm32
board = genericSTM32F103VB
; change microcontroller
board_build.mcu = stm32f103vbt6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103VB (20k RAM. 128k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103VB]
platform = ststm32
board = genericSTM32F103VB
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103VB (20k RAM. 128k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103VC (48k RAM. 256k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103VCT6
Frequency 72MHz
Flash 256KB
RAM 48KB
Vendor Generic

Please use genericSTM32F103VC ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103VC]
platform = ststm32
board = genericSTM32F103VC


You can override default STM32F103VC (48k RAM. 256k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103VC.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103VC]
platform = ststm32
board = genericSTM32F103VC
; change microcontroller
board_build.mcu = stm32f103vct6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103VC (48k RAM. 256k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103VC]
platform = ststm32
board = genericSTM32F103VC
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103VC (48k RAM. 256k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103VD (64k RAM. 384k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103VDT6
Frequency 72MHz
Flash 384KB
RAM 64KB
Vendor Generic

Please use genericSTM32F103VD ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103VD]
platform = ststm32
board = genericSTM32F103VD


You can override default STM32F103VD (64k RAM. 384k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103VD.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103VD]
platform = ststm32
board = genericSTM32F103VD
; change microcontroller
board_build.mcu = stm32f103vdt6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103VD (64k RAM. 384k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103VD]
platform = ststm32
board = genericSTM32F103VD
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103VD (64k RAM. 384k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103VE (64k RAM. 512k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103VET6
Frequency 72MHz
Flash 512KB
RAM 64KB
Vendor Generic

Please use genericSTM32F103VE ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103VE]
platform = ststm32
board = genericSTM32F103VE


You can override default STM32F103VE (64k RAM. 512k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103VE.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103VE]
platform = ststm32
board = genericSTM32F103VE
; change microcontroller
board_build.mcu = stm32f103vet6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103VE (64k RAM. 512k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103VE]
platform = ststm32
board = genericSTM32F103VE
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103VE (64k RAM. 512k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103ZC (48k RAM. 256k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103ZCT6
Frequency 72MHz
Flash 256KB
RAM 48KB
Vendor Generic

Please use genericSTM32F103ZC ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103ZC]
platform = ststm32
board = genericSTM32F103ZC


You can override default STM32F103ZC (48k RAM. 256k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103ZC.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103ZC]
platform = ststm32
board = genericSTM32F103ZC
; change microcontroller
board_build.mcu = stm32f103zct6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103ZC (48k RAM. 256k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103ZC]
platform = ststm32
board = genericSTM32F103ZC
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103ZC (48k RAM. 256k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103ZD (64k RAM. 384k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103ZDT6
Frequency 72MHz
Flash 384KB
RAM 64KB
Vendor Generic

Please use genericSTM32F103ZD ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103ZD]
platform = ststm32
board = genericSTM32F103ZD


You can override default STM32F103ZD (64k RAM. 384k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103ZD.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103ZD]
platform = ststm32
board = genericSTM32F103ZD
; change microcontroller
board_build.mcu = stm32f103zdt6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103ZD (64k RAM. 384k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103ZD]
platform = ststm32
board = genericSTM32F103ZD
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103ZD (64k RAM. 384k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F103ZE (64k RAM. 512k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103ZET6
Frequency 72MHz
Flash 512KB
RAM 64KB
Vendor Generic

Please use genericSTM32F103ZE ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F103ZE]
platform = ststm32
board = genericSTM32F103ZE


You can override default STM32F103ZE (64k RAM. 512k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103ZE.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F103ZE]
platform = ststm32
board = genericSTM32F103ZE
; change microcontroller
board_build.mcu = stm32f103zet6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F103ZE (64k RAM. 512k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F103ZE]
platform = ststm32
board = genericSTM32F103ZE
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F103ZE (64k RAM. 512k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F303CB (32k RAM. 128k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F303CBT6
Frequency 72MHz
Flash 128KB
RAM 32KB
Vendor Generic

Please use genericSTM32F303CB ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F303CB]
platform = ststm32
board = genericSTM32F303CB


You can override default STM32F303CB (32k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F303CB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F303CB]
platform = ststm32
board = genericSTM32F303CB
; change microcontroller
board_build.mcu = stm32f303cbt6
; change MCU frequency
board_build.f_cpu = 72000000L


STM32F303CB (32k RAM. 128k Flash) supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F303CB]
platform = ststm32
board = genericSTM32F303CB
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F303CB (32k RAM. 128k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
STM32F401RB (64k RAM. 128k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F401RB
Frequency 84MHz
Flash 128KB
RAM 64KB
Vendor Generic

Please use genericSTM32F401RB ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F401RB]
platform = ststm32
board = genericSTM32F401RB


You can override default STM32F401RB (64k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F401RB.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F401RB]
platform = ststm32
board = genericSTM32F401RB
; change microcontroller
board_build.mcu = stm32f401rb
; change MCU frequency
board_build.f_cpu = 84000000L


STM32F401RB (64k RAM. 128k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:genericSTM32F401RB]
platform = ststm32
board = genericSTM32F401RB
upload_protocol = serial


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F401RB (64k RAM. 128k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F401RC (64k RAM. 256k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F401RC
Frequency 84MHz
Flash 256KB
RAM 64KB
Vendor Generic

Please use genericSTM32F401RC ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F401RC]
platform = ststm32
board = genericSTM32F401RC


You can override default STM32F401RC (64k RAM. 256k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F401RC.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F401RC]
platform = ststm32
board = genericSTM32F401RC
; change microcontroller
board_build.mcu = stm32f401rc
; change MCU frequency
board_build.f_cpu = 84000000L


STM32F401RC (64k RAM. 256k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:genericSTM32F401RC]
platform = ststm32
board = genericSTM32F401RC
upload_protocol = serial


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F401RC (64k RAM. 256k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F401RE (96k RAM. 512k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F401RE
Frequency 84MHz
Flash 512KB
RAM 96KB
Vendor Generic

Please use genericSTM32F401RE ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F401RE]
platform = ststm32
board = genericSTM32F401RE


You can override default STM32F401RE (96k RAM. 512k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F401RE.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F401RE]
platform = ststm32
board = genericSTM32F401RE
; change microcontroller
board_build.mcu = stm32f401re
; change MCU frequency
board_build.f_cpu = 84000000L


STM32F401RE (96k RAM. 512k Flash) supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:genericSTM32F401RE]
platform = ststm32
board = genericSTM32F401RE
upload_protocol = serial


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F401RE (96k RAM. 512k Flash) 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.
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.

•
STM32F407VE (192k RAM. 512k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VET6
Frequency 168MHz
Flash 502.23KB
RAM 128KB
Vendor Generic

Please use genericSTM32F407VET6 ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F407VET6]
platform = ststm32
board = genericSTM32F407VET6


You can override default STM32F407VE (192k RAM. 512k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F407VET6.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F407VET6]
platform = ststm32
board = genericSTM32F407VET6
; change microcontroller
board_build.mcu = stm32f407vet6
; change MCU frequency
board_build.f_cpu = 168000000L


STM32F407VE (192k RAM. 512k Flash) supports the next uploading protocols:

  • dfu
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F407VET6]
platform = ststm32
board = genericSTM32F407VET6
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F407VE (192k RAM. 512k Flash) 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
J-LINK
ST-LINK Yes

Name Description
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.
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.
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.

•
STM32F407VG (192k RAM. 1024k Flash)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VGT6
Frequency 168MHz
Flash 1MB
RAM 192KB
Vendor Generic

Please use genericSTM32F407VGT6 ID for board option in "platformio.ini" (Project Configuration File):

[env:genericSTM32F407VGT6]
platform = ststm32
board = genericSTM32F407VGT6


You can override default STM32F407VG (192k RAM. 1024k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F407VGT6.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:genericSTM32F407VGT6]
platform = ststm32
board = genericSTM32F407VGT6
; change microcontroller
board_build.mcu = stm32f407vgt6
; change MCU frequency
board_build.f_cpu = 168000000L


STM32F407VG (192k RAM. 1024k Flash) supports the next uploading protocols:

  • dfu
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:genericSTM32F407VGT6]
platform = ststm32
board = genericSTM32F407VGT6
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F407VG (192k RAM. 1024k Flash) 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
J-LINK
ST-LINK Yes

Name Description
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.
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.
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.

•
STM32F4Stamp F405
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F405RGT6
Frequency 168MHz
Flash 1MB
RAM 192KB
Vendor Generic

Please use stm32f4stamp ID for board option in "platformio.ini" (Project Configuration File):

[env:stm32f4stamp]
platform = ststm32
board = stm32f4stamp


You can override default STM32F4Stamp F405 settings per build environment using board_*** option, where *** is a JSON object path from board manifest stm32f4stamp.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:stm32f4stamp]
platform = ststm32
board = stm32f4stamp
; change microcontroller
board_build.mcu = stm32f405rgt6
; change MCU frequency
board_build.f_cpu = 168000000L


STM32F4Stamp F405 supports the next uploading protocols:

  • dfu
  • jlink
  • stlink

Default protocol is dfu

You can change upload protocol using upload_protocol option:

[env:stm32f4stamp]
platform = ststm32
board = stm32f4stamp
upload_protocol = dfu


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F4Stamp F405 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
J-LINK
ST-LINK Yes

Name Description
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.
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.

•
STM32F7508-DK
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F750N8H6
Frequency 216MHz
Flash 64KB
RAM 340KB
Vendor ST

Please use disco_f750n8 ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_f750n8]
platform = ststm32
board = disco_f750n8


You can override default STM32F7508-DK settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f750n8.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_f750n8]
platform = ststm32
board = disco_f750n8
; change microcontroller
board_build.mcu = stm32f750n8h6
; change MCU frequency
board_build.f_cpu = 216000000L


STM32F7508-DK supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_f750n8]
platform = ststm32
board = disco_f750n8
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32F7508-DK 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.

•
STM32H747I-DISCO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32H747XIH6
Frequency 400MHz
Flash 2MB
RAM 512KB
Vendor ST

Please use disco_h743xi ID for board option in "platformio.ini" (Project Configuration File):

[env:disco_h743xi]
platform = ststm32
board = disco_h743xi


You can override default STM32H747I-DISCO settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_h743xi.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:disco_h743xi]
platform = ststm32
board = disco_h743xi
; change microcontroller
board_build.mcu = stm32h747xih6
; change MCU frequency
board_build.f_cpu = 400000000L


STM32H747I-DISCO supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:disco_h743xi]
platform = ststm32
board = disco_h743xi
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

STM32H747I-DISCO 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
Seeed Arch Max
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F407VET6
Frequency 168MHz
Flash 512KB
RAM 192KB
Vendor SeeedStudio

Please use seeedArchMax ID for board option in "platformio.ini" (Project Configuration File):

[env:seeedArchMax]
platform = ststm32
board = seeedArchMax


You can override default Seeed Arch Max settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeedArchMax.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:seeedArchMax]
platform = ststm32
board = seeedArchMax
; change microcontroller
board_build.mcu = stm32f407vet6
; change MCU frequency
board_build.f_cpu = 168000000L


Seeed Arch Max supports the next uploading protocols:

  • blackmagic
  • jlink
  • mbed
  • stlink

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:seeedArchMax]
platform = ststm32
board = seeedArchMax
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Seeed Arch Max 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
Seeed Wio 3G
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F439VI
Frequency 180MHz
Flash 2MB
RAM 256KB
Vendor SeeedStudio

Please use wio_3g ID for board option in "platformio.ini" (Project Configuration File):

[env:wio_3g]
platform = ststm32
board = wio_3g


You can override default Seeed Wio 3G settings per build environment using board_*** option, where *** is a JSON object path from board manifest wio_3g.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wio_3g]
platform = ststm32
board = wio_3g
; change microcontroller
board_build.mcu = stm32f439vi
; change MCU frequency
board_build.f_cpu = 180000000L


Seeed Wio 3G supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:wio_3g]
platform = ststm32
board = wio_3g
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Seeed Wio 3G 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

•
SensorTile.box
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L4R9ZI
Frequency 120MHz
Flash 2MB
RAM 640KB
Vendor ST

Please use steval_mksboxv1 ID for board option in "platformio.ini" (Project Configuration File):

[env:steval_mksboxv1]
platform = ststm32
board = steval_mksboxv1


You can override default SensorTile.box settings per build environment using board_*** option, where *** is a JSON object path from board manifest steval_mksboxv1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:steval_mksboxv1]
platform = ststm32
board = steval_mksboxv1
; change microcontroller
board_build.mcu = stm32l4r9zi
; change MCU frequency
board_build.f_cpu = 120000000L


SensorTile.box supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:steval_mksboxv1]
platform = ststm32
board = steval_mksboxv1
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

SensorTile.box 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
Black Magic Probe
J-LINK
ST-LINK Yes

Name Description
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.
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.

•
Sparky V1 F303
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F303CCT6
Frequency 72MHz
Flash 256KB
RAM 40KB
Vendor TauLabs

Please use sparky_v1 ID for board option in "platformio.ini" (Project Configuration File):

[env:sparky_v1]
platform = ststm32
board = sparky_v1


You can override default Sparky V1 F303 settings per build environment using board_*** option, where *** is a JSON object path from board manifest sparky_v1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sparky_v1]
platform = ststm32
board = sparky_v1
; change microcontroller
board_build.mcu = stm32f303cct6
; change MCU frequency
board_build.f_cpu = 72000000L


Sparky V1 F303 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:sparky_v1]
platform = ststm32
board = sparky_v1
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Sparky V1 F303 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
ThunderPack
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32L072KZ
Frequency 32MHz
Flash 192KB
RAM 20KB
Vendor ThunderPack

Please use thunder_pack ID for board option in "platformio.ini" (Project Configuration File):

[env:thunder_pack]
platform = ststm32
board = thunder_pack


You can override default ThunderPack settings per build environment using board_*** option, where *** is a JSON object path from board manifest thunder_pack.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:thunder_pack]
platform = ststm32
board = thunder_pack
; change microcontroller
board_build.mcu = stm32l072kz
; change MCU frequency
board_build.f_cpu = 32000000L


ThunderPack supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:thunder_pack]
platform = ststm32
board = thunder_pack
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ThunderPack 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
Tiny STM103T
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F103TBU6
Frequency 72MHz
Flash 128KB
RAM 20KB
Vendor HY

Please use hy_tinystm103tb ID for board option in "platformio.ini" (Project Configuration File):

[env:hy_tinystm103tb]
platform = ststm32
board = hy_tinystm103tb


You can override default Tiny STM103T settings per build environment using board_*** option, where *** is a JSON object path from board manifest hy_tinystm103tb.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:hy_tinystm103tb]
platform = ststm32
board = hy_tinystm103tb
; change microcontroller
board_build.mcu = stm32f103tbu6
; change MCU frequency
board_build.f_cpu = 72000000L


Tiny STM103T supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is dfu

You can change upload protocol using upload_protocol option:

[env:hy_tinystm103tb]
platform = ststm32
board = hy_tinystm103tb
upload_protocol = dfu


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Tiny STM103T 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
VAkE v1.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F446RET6
Frequency 180MHz
Flash 512KB
RAM 128KB
Vendor VAE

Please use vake_v1 ID for board option in "platformio.ini" (Project Configuration File):

[env:vake_v1]
platform = ststm32
board = vake_v1


You can override default VAkE v1.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest vake_v1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:vake_v1]
platform = ststm32
board = vake_v1
; change microcontroller
board_build.mcu = stm32f446ret6
; change MCU frequency
board_build.f_cpu = 180000000L


VAkE v1.0 supports the next uploading protocols:

  • blackmagic
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:vake_v1]
platform = ststm32
board = vake_v1
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

VAkE v1.0 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

•
Wraith V1 ESC
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F051K6
Frequency 48MHz
Flash 32KB
RAM 7.75KB
Vendor Airbot

Please use wraith32_v1 ID for board option in "platformio.ini" (Project Configuration File):

[env:wraith32_v1]
platform = ststm32
board = wraith32_v1


You can override default Wraith V1 ESC settings per build environment using board_*** option, where *** is a JSON object path from board manifest wraith32_v1.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wraith32_v1]
platform = ststm32
board = wraith32_v1
; change microcontroller
board_build.mcu = stm32f051k6
; change MCU frequency
board_build.f_cpu = 48000000L


Wraith V1 ESC supports the next uploading protocols:

  • blackmagic
  • dfu
  • jlink
  • serial
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:wraith32_v1]
platform = ststm32
board = wraith32_v1
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Wraith V1 ESC 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.
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.

•
sakura.io Evaluation Board
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F411RET6
Frequency 100MHz
Flash 1MB
RAM 128KB
Vendor sakura.io

Please use sakuraio_evb_01 ID for board option in "platformio.ini" (Project Configuration File):

[env:sakuraio_evb_01]
platform = ststm32
board = sakuraio_evb_01


You can override default sakura.io Evaluation Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest sakuraio_evb_01.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:sakuraio_evb_01]
platform = ststm32
board = sakuraio_evb_01
; change microcontroller
board_build.mcu = stm32f411ret6
; change MCU frequency
board_build.f_cpu = 100000000L


sakura.io Evaluation Board supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • stlink

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:sakuraio_evb_01]
platform = ststm32
board = sakuraio_evb_01
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

sakura.io Evaluation Board 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
Black Magic Probe
CMSIS-DAP Yes Yes
J-LINK
ST-LINK

Name Description
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.
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.

u-blox C030-N211 IoT Starter Kit

•
u-blox C030-N211 IoT Starter Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F437VG
Frequency 180MHz
Flash 1MB
RAM 256KB
Vendor u-blox

Please use ublox_c030_n211 ID for board option in "platformio.ini" (Project Configuration File):

[env:ublox_c030_n211]
platform = ststm32
board = ublox_c030_n211


You can override default u-blox C030-N211 IoT Starter Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest ublox_c030_n211.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ublox_c030_n211]
platform = ststm32
board = ublox_c030_n211
; change microcontroller
board_build.mcu = stm32f437vg
; change MCU frequency
board_build.f_cpu = 180000000L


u-blox C030-N211 IoT Starter Kit supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • stlink

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:ublox_c030_n211]
platform = ststm32
board = ublox_c030_n211
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

u-blox C030-N211 IoT Starter Kit 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
Black Magic Probe Yes
CMSIS-DAP
J-LINK
ST-LINK

Name Description
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.
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.

u-blox C030-R410M IoT

•
u-blox C030-R410M IoT
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F437VG
Frequency 180MHz
Flash 1MB
RAM 256KB
Vendor u-blox

Please use ublox_c030_r410m ID for board option in "platformio.ini" (Project Configuration File):

[env:ublox_c030_r410m]
platform = ststm32
board = ublox_c030_r410m


You can override default u-blox C030-R410M IoT settings per build environment using board_*** option, where *** is a JSON object path from board manifest ublox_c030_r410m.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ublox_c030_r410m]
platform = ststm32
board = ublox_c030_r410m
; change microcontroller
board_build.mcu = stm32f437vg
; change MCU frequency
board_build.f_cpu = 180000000L


u-blox C030-R410M IoT supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:ublox_c030_r410m]
platform = ststm32
board = ublox_c030_r410m
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

u-blox C030-R410M IoT 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
Black Magic Probe
J-LINK
ST-LINK Yes Yes

Name Description
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.
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.

u-blox C030-U201 IoT Starter Kit

•
u-blox C030-U201 IoT Starter Kit
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F437VG
Frequency 180MHz
Flash 1MB
RAM 256KB
Vendor u-blox

Please use ublox_c030_u201 ID for board option in "platformio.ini" (Project Configuration File):

[env:ublox_c030_u201]
platform = ststm32
board = ublox_c030_u201


You can override default u-blox C030-U201 IoT Starter Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest ublox_c030_u201.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ublox_c030_u201]
platform = ststm32
board = ublox_c030_u201
; change microcontroller
board_build.mcu = stm32f437vg
; change MCU frequency
board_build.f_cpu = 180000000L


u-blox C030-U201 IoT Starter Kit supports the next uploading protocols:

  • blackmagic
  • cmsis-dap
  • jlink
  • mbed
  • stlink

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:ublox_c030_u201]
platform = ststm32
board = ublox_c030_u201
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

u-blox C030-U201 IoT Starter Kit 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
Black Magic Probe Yes
CMSIS-DAP
J-LINK
ST-LINK

Name Description
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.
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.

u-blox EVK-ODIN-W2

•
u-blox EVK-ODIN-W2
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F439ZIY6
Frequency 168MHz
Flash 2MB
RAM 256KB
Vendor u-blox

Please use ublox_evk_odin_w2 ID for board option in "platformio.ini" (Project Configuration File):

[env:ublox_evk_odin_w2]
platform = ststm32
board = ublox_evk_odin_w2


You can override default u-blox EVK-ODIN-W2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ublox_evk_odin_w2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:ublox_evk_odin_w2]
platform = ststm32
board = ublox_evk_odin_w2
; change microcontroller
board_build.mcu = stm32f439ziy6
; change MCU frequency
board_build.f_cpu = 168000000L


u-blox EVK-ODIN-W2 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:ublox_evk_odin_w2]
platform = ststm32
board = ublox_evk_odin_w2
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

u-blox EVK-ODIN-W2 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

u-blox ODIN-W2

•
u-blox ODIN-W2
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM32: 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 STM32F439ZIY6
Frequency 168MHz
Flash 2MB
RAM 256KB
Vendor u-blox

Please use mtb_ublox_odin_w2 ID for board option in "platformio.ini" (Project Configuration File):

[env:mtb_ublox_odin_w2]
platform = ststm32
board = mtb_ublox_odin_w2


You can override default u-blox ODIN-W2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest mtb_ublox_odin_w2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mtb_ublox_odin_w2]
platform = ststm32
board = mtb_ublox_odin_w2
; change microcontroller
board_build.mcu = stm32f439ziy6
; change MCU frequency
board_build.f_cpu = 168000000L


u-blox ODIN-W2 supports the next uploading protocols:

  • blackmagic
  • jlink
  • stlink

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:mtb_ublox_odin_w2]
platform = ststm32
board = mtb_ublox_odin_w2
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

u-blox ODIN-W2 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
Black Magic Probe Yes
J-LINK
ST-LINK

Name Description
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.
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.

ST STM8

•
ST STM8S-DISCOVERY
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM8: The STM8 is an 8-bit microcontroller family by STMicroelectronics an extended variant of the ST7 microcontroller architecture. STM8 microcontrollers are particularly low cost for a full-featured 8-bit microcontroller.

Microcontroller STM8S105C6T6
Frequency 16MHz
Flash 32KB
RAM 2KB
Vendor ST

Please use stm8sdisco ID for board option in "platformio.ini" (Project Configuration File):

[env:stm8sdisco]
platform = ststm8
board = stm8sdisco


You can override default ST STM8S-DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest stm8sdisco.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:stm8sdisco]
platform = ststm8
board = stm8sdisco
; change microcontroller
board_build.mcu = stm8s105c6t6
; change MCU frequency
board_build.f_cpu = 16000000L


ST STM8S-DISCOVERY supports the next uploading protocols:

  • serial
  • stlink
  • stlinkv2

Default protocol is stlink

You can change upload protocol using upload_protocol option:

[env:stm8sdisco]
platform = ststm8
board = stm8sdisco
upload_protocol = stlink


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

ST STM8S-DISCOVERY 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
ST-LINK Yes Yes

Name Description
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.
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.

•
ST STM8S103F3 Breakout Board
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM8: The STM8 is an 8-bit microcontroller family by STMicroelectronics an extended variant of the ST7 microcontroller architecture. STM8 microcontrollers are particularly low cost for a full-featured 8-bit microcontroller.

Microcontroller STM8S103F3P6
Frequency 16MHz
Flash 8KB
RAM 1KB
Vendor ST

Please use stm8sblue ID for board option in "platformio.ini" (Project Configuration File):

[env:stm8sblue]
platform = ststm8
board = stm8sblue


You can override default ST STM8S103F3 Breakout Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest stm8sblue.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:stm8sblue]
platform = ststm8
board = stm8sblue
; change microcontroller
board_build.mcu = stm8s103f3p6
; change MCU frequency
board_build.f_cpu = 16000000L


ST STM8S103F3 Breakout Board supports the next uploading protocols:

  • serial
  • stlinkv2

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:stm8sblue]
platform = ststm8
board = stm8sblue
upload_protocol = serial


PIO Unified Debugger currently does not support ST STM8S103F3 Breakout Board board.

Name Description
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.
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.

•
ST STM8S105K4T6 Breakout Board
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM8: The STM8 is an 8-bit microcontroller family by STMicroelectronics an extended variant of the ST7 microcontroller architecture. STM8 microcontrollers are particularly low cost for a full-featured 8-bit microcontroller.

Microcontroller STM8S105K4T6
Frequency 16MHz
Flash 16KB
RAM 2KB
Vendor ST

Please use stm8sblack ID for board option in "platformio.ini" (Project Configuration File):

[env:stm8sblack]
platform = ststm8
board = stm8sblack


You can override default ST STM8S105K4T6 Breakout Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest stm8sblack.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:stm8sblack]
platform = ststm8
board = stm8sblack
; change microcontroller
board_build.mcu = stm8s105k4t6
; change MCU frequency
board_build.f_cpu = 16000000L


ST STM8S105K4T6 Breakout Board supports the next uploading protocols:

  • serial
  • stlinkv2

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:stm8sblack]
platform = ststm8
board = stm8sblack
upload_protocol = serial


PIO Unified Debugger currently does not support ST STM8S105K4T6 Breakout Board board.

Name Description
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.
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.

•
sduino MB (STM8S208MBT6B)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM8: The STM8 is an 8-bit microcontroller family by STMicroelectronics an extended variant of the ST7 microcontroller architecture. STM8 microcontrollers are particularly low cost for a full-featured 8-bit microcontroller.

Microcontroller STM8S208MBT6
Frequency 16MHz
Flash 128KB
RAM 6KB
Vendor sduino

Please use mb208 ID for board option in "platformio.ini" (Project Configuration File):

[env:mb208]
platform = ststm8
board = mb208


You can override default sduino MB (STM8S208MBT6B) settings per build environment using board_*** option, where *** is a JSON object path from board manifest mb208.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:mb208]
platform = ststm8
board = mb208
; change microcontroller
board_build.mcu = stm8s208mbt6
; change MCU frequency
board_build.f_cpu = 16000000L


sduino MB (STM8S208MBT6B) supports the next uploading protocols:

  • serial
  • stlinkv2

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:mb208]
platform = ststm8
board = mb208
upload_protocol = serial


PIO Unified Debugger currently does not support sduino MB (STM8S208MBT6B) board.

Name Description
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.
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.

•
sduino UNO (STM8S105K6)
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform ST STM8: The STM8 is an 8-bit microcontroller family by STMicroelectronics an extended variant of the ST7 microcontroller architecture. STM8 microcontrollers are particularly low cost for a full-featured 8-bit microcontroller.

Microcontroller STM8S105K6T6
Frequency 16MHz
Flash 32KB
RAM 2KB
Vendor sduino

Please use s8uno ID for board option in "platformio.ini" (Project Configuration File):

[env:s8uno]
platform = ststm8
board = s8uno


You can override default sduino UNO (STM8S105K6) settings per build environment using board_*** option, where *** is a JSON object path from board manifest s8uno.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:s8uno]
platform = ststm8
board = s8uno
; change microcontroller
board_build.mcu = stm8s105k6t6
; change MCU frequency
board_build.f_cpu = 16000000L


sduino UNO (STM8S105K6) supports the next uploading protocols:

  • serial
  • stlinkv2

Default protocol is serial

You can change upload protocol using upload_protocol option:

[env:s8uno]
platform = ststm8
board = s8uno
upload_protocol = serial


PIO Unified Debugger currently does not support sduino UNO (STM8S105K6) board.

Name Description
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.
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.

•
Teensy 2.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Teensy: Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.

Microcontroller ATMEGA32U4
Frequency 16MHz
Flash 31.50KB
RAM 2.50KB
Vendor Teensy

Please use teensy2 ID for board option in "platformio.ini" (Project Configuration File):

[env:teensy2]
platform = teensy
board = teensy2


You can override default Teensy 2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest teensy2.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:teensy2]
platform = teensy
board = teensy2
; change microcontroller
board_build.mcu = atmega32u4
; change MCU frequency
board_build.f_cpu = 16000000L


Teensy 2.0 supports the next uploading protocols:

  • teensy-cli
  • teensy-gui

Default protocol is teensy-gui

You can change upload protocol using upload_protocol option:

[env:teensy2]
platform = teensy
board = teensy2
upload_protocol = teensy-gui


PIO Unified Debugger currently does not support Teensy 2.0 board.

Name Description
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.

•
Teensy 3.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Teensy: Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.

Microcontroller MK20DX128
Frequency 48MHz
Flash 128KB
RAM 16KB
Vendor Teensy

Please use teensy30 ID for board option in "platformio.ini" (Project Configuration File):

[env:teensy30]
platform = teensy
board = teensy30


You can override default Teensy 3.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest teensy30.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:teensy30]
platform = teensy
board = teensy30
; change microcontroller
board_build.mcu = mk20dx128
; change MCU frequency
board_build.f_cpu = 48000000L


Teensy 3.0 supports the next uploading protocols:

  • teensy-cli
  • teensy-gui

Default protocol is teensy-gui

You can change upload protocol using upload_protocol option:

[env:teensy30]
platform = teensy
board = teensy30
upload_protocol = teensy-gui


PIO Unified Debugger currently does not support Teensy 3.0 board.

Name Description
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.

•
Teensy 3.1 / 3.2
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Teensy: Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.

Microcontroller MK20DX256
Frequency 72MHz
Flash 256KB
RAM 64KB
Vendor Teensy

Please use teensy31 ID for board option in "platformio.ini" (Project Configuration File):

[env:teensy31]
platform = teensy
board = teensy31


You can override default Teensy 3.1 / 3.2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest teensy31.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:teensy31]
platform = teensy
board = teensy31
; change microcontroller
board_build.mcu = mk20dx256
; change MCU frequency
board_build.f_cpu = 72000000L


Teensy 3.1 / 3.2 supports the next uploading protocols:

  • jlink
  • teensy-cli
  • teensy-gui

Default protocol is teensy-gui

You can change upload protocol using upload_protocol option:

[env:teensy31]
platform = teensy
board = teensy31
upload_protocol = teensy-gui


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Teensy 3.1 / 3.2 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
J-LINK Yes

Name Description
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.
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.

•
Teensy 3.5
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Teensy: Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.

Microcontroller MK64FX512
Frequency 120MHz
Flash 512KB
RAM 255.99KB
Vendor Teensy

Please use teensy35 ID for board option in "platformio.ini" (Project Configuration File):

[env:teensy35]
platform = teensy
board = teensy35


You can override default Teensy 3.5 settings per build environment using board_*** option, where *** is a JSON object path from board manifest teensy35.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:teensy35]
platform = teensy
board = teensy35
; change microcontroller
board_build.mcu = mk64fx512
; change MCU frequency
board_build.f_cpu = 120000000L


Teensy 3.5 supports the next uploading protocols:

  • jlink
  • teensy-cli
  • teensy-gui

Default protocol is teensy-gui

You can change upload protocol using upload_protocol option:

[env:teensy35]
platform = teensy
board = teensy35
upload_protocol = teensy-gui


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Teensy 3.5 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
J-LINK Yes

Name Description
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.

•
Teensy 3.6
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Teensy: Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.

Microcontroller MK66FX1M0
Frequency 180MHz
Flash 1MB
RAM 256KB
Vendor Teensy

Please use teensy36 ID for board option in "platformio.ini" (Project Configuration File):

[env:teensy36]
platform = teensy
board = teensy36


You can override default Teensy 3.6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest teensy36.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:teensy36]
platform = teensy
board = teensy36
; change microcontroller
board_build.mcu = mk66fx1m0
; change MCU frequency
board_build.f_cpu = 180000000L


Teensy 3.6 supports the next uploading protocols:

  • jlink
  • teensy-cli
  • teensy-gui

Default protocol is teensy-gui

You can change upload protocol using upload_protocol option:

[env:teensy36]
platform = teensy
board = teensy36
upload_protocol = teensy-gui


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Teensy 3.6 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
J-LINK Yes

Name Description
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.

•
Teensy 4.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Teensy: Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.

Microcontroller IMXRT1062
Frequency 600MHz
Flash 1.94MB
RAM 512KB
Vendor Teensy

Please use teensy40 ID for board option in "platformio.ini" (Project Configuration File):

[env:teensy40]
platform = teensy
board = teensy40


You can override default Teensy 4.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest teensy40.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:teensy40]
platform = teensy
board = teensy40
; change microcontroller
board_build.mcu = imxrt1062
; change MCU frequency
board_build.f_cpu = 600000000L


Teensy 4.0 supports the next uploading protocols:

  • jlink
  • teensy-gui

Default protocol is teensy-gui

You can change upload protocol using upload_protocol option:

[env:teensy40]
platform = teensy
board = teensy40
upload_protocol = teensy-gui


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Teensy 4.0 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
J-LINK Yes

Name Description
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.

•
Teensy 4.1
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Teensy: Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.

Microcontroller IMXRT1062
Frequency 600MHz
Flash 7.75MB
RAM 512KB
Vendor Teensy

Please use teensy41 ID for board option in "platformio.ini" (Project Configuration File):

[env:teensy41]
platform = teensy
board = teensy41


You can override default Teensy 4.1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest teensy41.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:teensy41]
platform = teensy
board = teensy41
; change microcontroller
board_build.mcu = imxrt1062
; change MCU frequency
board_build.f_cpu = 600000000L


Teensy 4.1 supports the next uploading protocols:

  • jlink
  • teensy-gui

Default protocol is teensy-gui

You can change upload protocol using upload_protocol option:

[env:teensy41]
platform = teensy
board = teensy41
upload_protocol = teensy-gui


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Teensy 4.1 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
J-LINK Yes

Name Description
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.

•
Teensy LC
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Teensy: Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.

Microcontroller MKL26Z64
Frequency 48MHz
Flash 62KB
RAM 8KB
Vendor Teensy

Please use teensylc ID for board option in "platformio.ini" (Project Configuration File):

[env:teensylc]
platform = teensy
board = teensylc


You can override default Teensy LC settings per build environment using board_*** option, where *** is a JSON object path from board manifest teensylc.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:teensylc]
platform = teensy
board = teensylc
; change microcontroller
board_build.mcu = mkl26z64
; change MCU frequency
board_build.f_cpu = 48000000L


Teensy LC supports the next uploading protocols:

  • jlink
  • teensy-cli
  • teensy-gui

Default protocol is teensy-gui

You can change upload protocol using upload_protocol option:

[env:teensylc]
platform = teensy
board = teensylc
upload_protocol = teensy-gui


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

Teensy LC 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
J-LINK Yes

Name Description
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.

•
Teensy++ 2.0
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform Teensy: Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.

Microcontroller AT90USB1286
Frequency 16MHz
Flash 127KB
RAM 8KB
Vendor Teensy

Please use teensy2pp ID for board option in "platformio.ini" (Project Configuration File):

[env:teensy2pp]
platform = teensy
board = teensy2pp


You can override default Teensy++ 2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest teensy2pp.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:teensy2pp]
platform = teensy
board = teensy2pp
; change microcontroller
board_build.mcu = at90usb1286
; change MCU frequency
board_build.f_cpu = 16000000L


Teensy++ 2.0 supports the next uploading protocols:

  • teensy-cli
  • teensy-gui

Default protocol is teensy-gui

You can change upload protocol using upload_protocol option:

[env:teensy2pp]
platform = teensy
board = teensy2pp
upload_protocol = teensy-gui


PIO Unified Debugger currently does not support Teensy++ 2.0 board.

Name Description
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.

TI MSP430

•
TI FraunchPad MSP-EXP430FR5739LP
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430FR5739
Frequency 16MHz
Flash 15.37KB
RAM 1KB
Vendor TI

Please use lpmsp430fr5739 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430fr5739]
platform = timsp430
board = lpmsp430fr5739


You can override default TI FraunchPad MSP-EXP430FR5739LP settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430fr5739.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430fr5739]
platform = timsp430
board = lpmsp430fr5739
; change microcontroller
board_build.mcu = msp430fr5739
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI FraunchPad MSP-EXP430FR5739LP 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
MSP Debug Yes Yes

Name Description
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.

TI LaunchPad MSP-EXP430F5529LP

•
TI LaunchPad MSP-EXP430F5529LP
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430F5529
Frequency 25MHz
Flash 47KB
RAM 8KB
Vendor TI

Please use lpmsp430f5529 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430f5529]
platform = timsp430
board = lpmsp430f5529


You can override default TI LaunchPad MSP-EXP430F5529LP settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430f5529.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430f5529]
platform = timsp430
board = lpmsp430f5529
; change microcontroller
board_build.mcu = msp430f5529
; change MCU frequency
board_build.f_cpu = 25000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad MSP-EXP430F5529LP 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
MSP Debug Yes Yes

Name Description
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.

TI LaunchPad MSP-EXP430FR2311LP

•
TI LaunchPad MSP-EXP430FR2311LP
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430FR2311
Frequency 16MHz
Flash 3.75KB
RAM 1KB
Vendor TI

Please use lpmsp430fr2311 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430fr2311]
platform = timsp430
board = lpmsp430fr2311


You can override default TI LaunchPad MSP-EXP430FR2311LP settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430fr2311.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430fr2311]
platform = timsp430
board = lpmsp430fr2311
; change microcontroller
board_build.mcu = msp430fr2311
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad MSP-EXP430FR2311LP 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
MSP Debug Yes Yes

Name Description
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.

TI LaunchPad MSP-EXP430FR2433LP

•
TI LaunchPad MSP-EXP430FR2433LP
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430FR2433
Frequency 8MHz
Flash 15KB
RAM 4KB
Vendor TI

Please use lpmsp430fr2433 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430fr2433]
platform = timsp430
board = lpmsp430fr2433


You can override default TI LaunchPad MSP-EXP430FR2433LP settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430fr2433.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430fr2433]
platform = timsp430
board = lpmsp430fr2433
; change microcontroller
board_build.mcu = msp430fr2433
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad MSP-EXP430FR2433LP 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
MSP Debug Yes Yes

Name Description
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.

TI LaunchPad MSP-EXP430FR4133LP

•
TI LaunchPad MSP-EXP430FR4133LP
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430FR4133
Frequency 8MHz
Flash 15KB
RAM 2KB
Vendor TI

Please use lpmsp430fr4133 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430fr4133]
platform = timsp430
board = lpmsp430fr4133


You can override default TI LaunchPad MSP-EXP430FR4133LP settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430fr4133.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430fr4133]
platform = timsp430
board = lpmsp430fr4133
; change microcontroller
board_build.mcu = msp430fr4133
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad MSP-EXP430FR4133LP 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
MSP Debug Yes Yes

Name Description
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.

TI LaunchPad MSP-EXP430FR5969LP

•
TI LaunchPad MSP-EXP430FR5969LP
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430FR5969
Frequency 8MHz
Flash 47KB
RAM 2KB
Vendor TI

Please use lpmsp430fr5969 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430fr5969]
platform = timsp430
board = lpmsp430fr5969


You can override default TI LaunchPad MSP-EXP430FR5969LP settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430fr5969.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430fr5969]
platform = timsp430
board = lpmsp430fr5969
; change microcontroller
board_build.mcu = msp430fr5969
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad MSP-EXP430FR5969LP 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
MSP Debug Yes Yes

Name Description
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.

TI LaunchPad MSP-EXP430FR5994LP

•
TI LaunchPad MSP-EXP430FR5994LP
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430FR5994
Frequency 16MHz
Flash 256KB
RAM 4KB
Vendor TI

Please use lpmsp430fr5994 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430fr5994]
platform = timsp430
board = lpmsp430fr5994


You can override default TI LaunchPad MSP-EXP430FR5994LP settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430fr5994.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430fr5994]
platform = timsp430
board = lpmsp430fr5994
; change microcontroller
board_build.mcu = msp430fr5994
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad MSP-EXP430FR5994LP 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
MSP Debug Yes Yes

Name Description
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.

TI LaunchPad MSP-EXP430FR6989LP

•
TI LaunchPad MSP-EXP430FR6989LP
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430FR6989
Frequency 8MHz
Flash 47KB
RAM 2KB
Vendor TI

Please use lpmsp430fr6989 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430fr6989]
platform = timsp430
board = lpmsp430fr6989


You can override default TI LaunchPad MSP-EXP430FR6989LP settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430fr6989.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430fr6989]
platform = timsp430
board = lpmsp430fr6989
; change microcontroller
board_build.mcu = msp430fr6989
; change MCU frequency
board_build.f_cpu = 8000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad MSP-EXP430FR6989LP 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
MSP Debug Yes Yes

Name Description
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.

TI LaunchPad MSP-EXP430G2 w/ MSP430G2231

•
TI LaunchPad MSP-EXP430G2 w/ MSP430G2231
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430G2231
Frequency 1MHz
Flash 2KB
RAM 256B
Vendor TI

Please use lpmsp430g2231 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430g2231]
platform = timsp430
board = lpmsp430g2231


You can override default TI LaunchPad MSP-EXP430G2 w/ MSP430G2231 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430g2231.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430g2231]
platform = timsp430
board = lpmsp430g2231
; change microcontroller
board_build.mcu = msp430g2231
; change MCU frequency
board_build.f_cpu = 1000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad MSP-EXP430G2 w/ MSP430G2231 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
MSP Debug Yes Yes

Name Description
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.

TI LaunchPad MSP-EXP430G2 w/ MSP430G2452

•
TI LaunchPad MSP-EXP430G2 w/ MSP430G2452
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430G2452
Frequency 16MHz
Flash 8KB
RAM 256B
Vendor TI

Please use lpmsp430g2452 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430g2452]
platform = timsp430
board = lpmsp430g2452


You can override default TI LaunchPad MSP-EXP430G2 w/ MSP430G2452 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430g2452.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430g2452]
platform = timsp430
board = lpmsp430g2452
; change microcontroller
board_build.mcu = msp430g2452
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad MSP-EXP430G2 w/ MSP430G2452 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
MSP Debug Yes Yes

Name Description
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.

TI LaunchPad MSP-EXP430G2553LP

•
TI LaunchPad MSP-EXP430G2553LP
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI MSP430: MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Microcontroller MSP430G2553
Frequency 16MHz
Flash 16KB
RAM 512B
Vendor TI

Please use lpmsp430g2553 ID for board option in "platformio.ini" (Project Configuration File):

[env:lpmsp430g2553]
platform = timsp430
board = lpmsp430g2553


You can override default TI LaunchPad MSP-EXP430G2553LP settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpmsp430g2553.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lpmsp430g2553]
platform = timsp430
board = lpmsp430g2553
; change microcontroller
board_build.mcu = msp430g2553
; change MCU frequency
board_build.f_cpu = 16000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad MSP-EXP430G2553LP 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
MSP Debug Yes Yes

Name Description
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.

TI TIVA

•
TI LaunchPad (Stellaris) w/ lm4f120 (80MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI TIVA: Texas Instruments TM4C12x MCUs offer the industrys most popular ARM Cortex-M4 core with scalable memory and package options, unparalleled connectivity peripherals, advanced application functions, industry-leading analog integration, and extensive software solutions.

Microcontroller LPLM4F120H5QR
Frequency 80MHz
Flash 256KB
RAM 32KB
Vendor TI

Please use lplm4f120h5qr ID for board option in "platformio.ini" (Project Configuration File):

[env:lplm4f120h5qr]
platform = titiva
board = lplm4f120h5qr


You can override default TI LaunchPad (Stellaris) w/ lm4f120 (80MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest lplm4f120h5qr.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lplm4f120h5qr]
platform = titiva
board = lplm4f120h5qr
; change microcontroller
board_build.mcu = lplm4f120h5qr
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad (Stellaris) w/ lm4f120 (80MHz) 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
TI-ICDI Yes Yes

Name Description
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.
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.

•
TI LaunchPad (Tiva C) w/ tm4c123 (80MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI TIVA: Texas Instruments TM4C12x MCUs offer the industrys most popular ARM Cortex-M4 core with scalable memory and package options, unparalleled connectivity peripherals, advanced application functions, industry-leading analog integration, and extensive software solutions.

Microcontroller LPTM4C1230C3PM
Frequency 80MHz
Flash 256KB
RAM 32KB
Vendor TI

Please use lptm4c1230c3pm ID for board option in "platformio.ini" (Project Configuration File):

[env:lptm4c1230c3pm]
platform = titiva
board = lptm4c1230c3pm


You can override default TI LaunchPad (Tiva C) w/ tm4c123 (80MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest lptm4c1230c3pm.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lptm4c1230c3pm]
platform = titiva
board = lptm4c1230c3pm
; change microcontroller
board_build.mcu = lptm4c1230c3pm
; change MCU frequency
board_build.f_cpu = 80000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad (Tiva C) w/ tm4c123 (80MHz) 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
TI-ICDI Yes Yes

Name Description
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.
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.

•
TI LaunchPad (Tiva C) w/ tm4c129 (120MHz)
  • Hardware
  • Configuration
  • Debugging
  • Frameworks


Platform TI TIVA: Texas Instruments TM4C12x MCUs offer the industrys most popular ARM Cortex-M4 core with scalable memory and package options, unparalleled connectivity peripherals, advanced application functions, industry-leading analog integration, and extensive software solutions.

Microcontroller LPTM4C1294NCPDT
Frequency 120MHz
Flash 1MB
RAM 256KB
Vendor TI

Please use lptm4c1294ncpdt ID for board option in "platformio.ini" (Project Configuration File):

[env:lptm4c1294ncpdt]
platform = titiva
board = lptm4c1294ncpdt


You can override default TI LaunchPad (Tiva C) w/ tm4c129 (120MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest lptm4c1294ncpdt.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:lptm4c1294ncpdt]
platform = titiva
board = lptm4c1294ncpdt
; change microcontroller
board_build.mcu = lptm4c1294ncpdt
; change MCU frequency
board_build.f_cpu = 120000000L


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

TI LaunchPad (Tiva C) w/ tm4c129 (120MHz) 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
TI-ICDI Yes Yes

Name Description
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.
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.

WIZNet W7500

•
WIZwiki-W7500
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform WIZNet W7500: The IOP (Internet Offload Processor) W7500 is the one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform especially requiring Internet of things

Microcontroller WIZNET7500
Frequency 48MHz
Flash 128KB
RAM 48KB
Vendor WIZNet

Please use wizwiki_w7500 ID for board option in "platformio.ini" (Project Configuration File):

[env:wizwiki_w7500]
platform = wiznet7500
board = wizwiki_w7500


You can override default WIZwiki-W7500 settings per build environment using board_*** option, where *** is a JSON object path from board manifest wizwiki_w7500.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wizwiki_w7500]
platform = wiznet7500
board = wizwiki_w7500
; change microcontroller
board_build.mcu = wiznet7500
; change MCU frequency
board_build.f_cpu = 48000000L


WIZwiki-W7500 supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:wizwiki_w7500]
platform = wiznet7500
board = wizwiki_w7500
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WIZwiki-W7500 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
WIZwiki-W7500ECO
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform WIZNet W7500: The IOP (Internet Offload Processor) W7500 is the one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform especially requiring Internet of things

Microcontroller WIZNET7500ECO
Frequency 48MHz
Flash 128KB
RAM 48KB
Vendor WIZNet

Please use wizwiki_w7500eco ID for board option in "platformio.ini" (Project Configuration File):

[env:wizwiki_w7500eco]
platform = wiznet7500
board = wizwiki_w7500eco


You can override default WIZwiki-W7500ECO settings per build environment using board_*** option, where *** is a JSON object path from board manifest wizwiki_w7500eco.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wizwiki_w7500eco]
platform = wiznet7500
board = wizwiki_w7500eco
; change microcontroller
board_build.mcu = wiznet7500eco
; change MCU frequency
board_build.f_cpu = 48000000L


WIZwiki-W7500ECO supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:wizwiki_w7500eco]
platform = wiznet7500
board = wizwiki_w7500eco
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WIZwiki-W7500ECO 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

•
WIZwiki-W7500P
  • Hardware
  • Configuration
  • Uploading
  • Debugging
  • Frameworks


Platform WIZNet W7500: The IOP (Internet Offload Processor) W7500 is the one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform especially requiring Internet of things

Microcontroller WIZNET7500P
Frequency 48MHz
Flash 128KB
RAM 48KB
Vendor WIZNet

Please use wizwiki_w7500p ID for board option in "platformio.ini" (Project Configuration File):

[env:wizwiki_w7500p]
platform = wiznet7500
board = wizwiki_w7500p


You can override default WIZwiki-W7500P settings per build environment using board_*** option, where *** is a JSON object path from board manifest wizwiki_w7500p.json. For example, board_build.mcu, board_build.f_cpu, etc.

[env:wizwiki_w7500p]
platform = wiznet7500
board = wizwiki_w7500p
; change microcontroller
board_build.mcu = wiznet7500p
; change MCU frequency
board_build.f_cpu = 48000000L


WIZwiki-W7500P supports the next uploading protocols:

  • cmsis-dap
  • jlink
  • mbed

Default protocol is mbed

You can change upload protocol using upload_protocol option:

[env:wizwiki_w7500p]
platform = wiznet7500
board = wizwiki_w7500p
upload_protocol = mbed


PIO Unified Debugger - "1-click" solution for debugging with a zero configuration.

WARNING:

You will need to install debug tool drivers depending on your system. Please click on compatible debug tool below for the further instructions and configuration information.


You can switch between debugging Tools & Debug Probes using debug_tool option in "platformio.ini" (Project Configuration File).

WIZwiki-W7500P 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
CMSIS-DAP Yes Yes
J-LINK

Name Description
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.

PlatformIO can build the same binary code under different host systems via the single command platformio run without any dependent software or requirements.

A manifest describes how to produce binaries for a particular platform under one or multiple host systems by a set of build scripts, toolchains, the settings for the most popular embedded boards, etc.

This guide explains how to write manifests, to support building for new development platforms.

Step-by-Step Manual

1.
Choose Packages for platform
2.
Create Manifest File platform.json
3.
Create Build Script main.py
4.
Finish with the Installation.

•
Custom Development Platforms
  • Packages
  • Manifest File platform.json
  • Build Script main.py
  • Installation
  • Examples


Some tools are the same when compiling for several platforms, for example a common compiler. A package is some tool or framework that can be used when compiling for one or multiple platforms. Even if multiple platforms use the same package, the package only needs to be downloaded once. Since each package is pre-built for the different host systems (Windows, Mac, Linux), developers can get started without first compiling the tools.

PlatformIO has a registry with pre-built packages for the most popular operating systems and you can use them in your platform manifest. These packages are stored in the super-fast and reliably CDN storage provided by JFrog Bintray.

Each platform definition must define packageRepositories to link to package manifest files that lists how PlatformIO can download the used packages. To use the pre-built packages, include http://dl.platformio.org/packages/manifest.json in the packageRepositories list. Platform definitions can also use custom packages.

Each platform definition includes a manifest file with a particular format that is parsed by PlatformIO when handling projects using that platform.

Here is an example platform.json for the fictitious platform "myplatform":

{
  "name": "myplatform",
  "title": "My Platform",
  "description": "My custom development platform",
  "url": "http://example.com",
  "homepage": "https://platformio.org/platforms/myplatform",
  "license": "Apache-2.0",
  "engines": {
    "platformio": "~3.0.0"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/platformio/platform-myplatform.git"
  },
  "version": "0.0.0",
  "packageRepositories": [
    "https://dl.bintray.com/platformio/dl-packages/manifest.json",
    "http://dl.platformio.org/packages/manifest.json",
    {
      "my_custom_package": [
        {
          "url": "http://dl.example.com/my_custom_package-darwin_x86_64-1.2.3.tar.gz",
          "sha1": "bb7ddac56a314b5cb1926cc1790ae4de3a03e65c",
          "version": "1.2.3",
          "system": [
              "darwin_x86_64",
              "darwin_i386"
          ]
        },
        {
          "url": "http://dl.example.com/my_custom_package-linux_aarch64-1.2.3.tar.gz",
          "sha1": "127ddac56a314b5cb1926cc1790ae4de3a03e65c",
          "version": "1.2.3",
          "system": "linux_aarch64"
        }
      ],
      "framework-%FRAMEWORK_NAME_1%": [
        {
          "url": "http://dl.example.com/packages/framework-%FRAMEWORK_NAME_1%-1.10607.0.tar.gz",
          "sha1": "adce2cd30a830d71cb6572575bf08461b7b73c07",
          "version": "1.10607.0",
          "system": "*"
        }
      ]
    }
  ],
  "frameworks": {
    "%FRAMEWORK_NAME_1%": {
      "package": "framework-%FRAMEWORK_NAME_1%",
      "script": "builder/frameworks/%FRAMEWORK_NAME_1%.py"
    },
    "%FRAMEWORK_NAME_N%": {
      "package": "framework-%FRAMEWORK_NAME_N%",
      "script": "builder/frameworks/%FRAMEWORK_NAME_N%.py"
    }
  },
  "packages": {
    "toolchain-gccarmnoneeabi": {
      "type": "toolchain",
      "version": ">=1.40803.0,<1.40805.0"
    },
    "framework-%FRAMEWORK_NAME_1%": {
      "type": "framework",
      "optional": true,
      "version": "~1.10607.0"
    },
    "framework-%FRAMEWORK_NAME_N%": {
      "type": "framework",
      "optional": true,
      "version": "~1.117.0"
    },
    "tool-direct-vcs-url": {
      "type": "uploader",
      "optional": true,
      "version": "https://github.com/user/repo.git"
    }
  },
  "pythonPackages": {
    "pypi-pkg-1": "1.2.3",
    "pypi-pkg-2": ">=2.3, <3"
  }
}


Each platform definition must include a main.py.

PlatformIO's build script is based on a next-generation build tool named SCons. PlatformIO has its own built-in firmware builder env.BuildProgram with deep library search. Please see the following template as start for developing your own main.py.

"""
    Build script for test.py
    test-builder.py
"""
from os.path import join
from SCons.Script import AlwaysBuild, Builder, Default, DefaultEnvironment
env = DefaultEnvironment()
# A full list with the available variables
# http://www.scons.org/doc/production/HTML/scons-user.html#app-variables
env.Replace(
    AR="ar",
    AS="gcc",
    CC="gcc",
    CXX="g++",
    OBJCOPY="objcopy",
    RANLIB="ranlib",
    UPLOADER=join("$PIOPACKAGES_DIR", "tool-bar", "uploader"),
    UPLOADCMD="$UPLOADER $SOURCES"
)
env.Append(
    ARFLAGS=["..."],
    ASFLAGS=["flag1", "flag2", "flagN"],
    CCFLAGS=["flag1", "flag2", "flagN"],
    CXXFLAGS=["flag1", "flag2", "flagN"],
    LINKFLAGS=["flag1", "flag2", "flagN"],
    CPPDEFINES=["DEFINE_1", "DEFINE=2", "DEFINE_N"],
    LIBS=["additional", "libs", "here"],
    BUILDERS=dict(
        ElfToBin=Builder(
            action=" ".join([
                "$OBJCOPY",
                "-O",
                "binary",
                "$SOURCES",
                "$TARGET"]),
            suffix=".bin"
        )
    )
)
# The source code of "platformio-build-tool" is here
# https://github.com/platformio/platformio-core/blob/develop/platformio/builder/tools/platformio.py
#
# Target: Build executable and linkable firmware
#
target_elf = env.BuildProgram()
#
# Target: Build the .bin file
#
target_bin = env.ElfToBin(join("$BUILD_DIR", "firmware"), target_elf)
#
# Target: Upload firmware
#
upload = env.Alias(["upload"], target_bin, "$UPLOADCMD")
AlwaysBuild(upload)
#
# Target: Define targets
#
Default(target_bin)


Using the "myplatform" platform example above:

1.
Create a platforms directory in core_dir if it doesn't exist.
2.
Create a myplatform directory in platforms
3.
Copy the platform.json and builder/main.py files to the myplatform directory.
4.
Search the available platforms via the platformio platform search command. You should see the new myplatform platform.
5.
Install the myplatform platform via the platformio platform install command.

Now, you can use myplatform as value for the platform option in "platformio.ini" (Project Configuration File).

Please take a look at the source code of existing PlatformIO Development Platforms.

PlatformIO has pre-built settings for many popular embedded boards. The list of these boards is available as a web page at PlatformIO Boards Explorer or through the CLI command platformio boards.

Custom boards can also be defined from scratch or by overriding settings of existing boards. All data is declared using the JSON syntax via associative array name/value pairs.

•
Custom Embedded Boards
  • JSON Structure
  • Installation
  • Examples


The key fields are:

  • build data is handed over to the Development Platforms and Frameworks builders
  • frameworks is the list with supported Frameworks. Each working environment for each project that uses the board will choose one of the frameworks declared here.
  • platform name of Development Platforms
  • upload upload settings which depend on the platform

For details, see existing boards as examples, available under .platformio/platforms/*/boards/.

{
  "build": {
    "extra_flags": "-DHELLO_PLATFORMIO",
    "f_cpu": "16000000L",
    "hwids": [
      [
        "0x1234",
        "0x0013"
      ],
      [
        "0x4567",
        "0x0013"
      ]
    ],
    "mcu": "%MCU_TYPE_HERE%"
  },
  "frameworks": ["%LIST_WITH_SUPPORTED_FRAMEWORKS%"],
  "platforms": ["%LIST_WITH_COMPATIBLE_PLATFORMS%"]
  "name": "My Test Board",
  "upload": {
    "maximum_ram_size": 2048,
    "maximum_size": 32256
  },
  "url": "http://example.com",
  "vendor": "MyCompany"
}


1.
Create boards directory in core_dir if it doesn't exist.
2.
Create myboard.json file in this boards directory.
3.
Search available boards via platformio boards command. You should see myboard board.

Now, you can use myboard for the board option in "platformio.ini" (Project Configuration File).

NOTE:

You can have custom boards per project. In this case, please put your board's JSON files to boards_dir.


Please take a look at the source code of PlatformIO Development Platforms and navigate to boards folder of the repository.

PIO Account is required for using:

  • Community Forum
  • PIO Remote

PlatformIO IDE

PlatformIO IDE has built-in UI in PIO Home to manage PIO Account. You can create a new account, reset your password, update profile, or fetch an authentication token.

CLI Guide

New in version 4.1.

Automated code analysis without hassle!

Static analysis became an important part of software development cycle. It can identify potential bugs, vulnerabilities and security threats by doing an analysis on the source code level without having to test it on hardware or execute any code.

PIO Check helps reduce development cost by enabling engineers to detect the precise location of defects and eliminate issues more efficiently and earlier in the development cycle. It can also ensure compliance with internal or industry coding standards such as MISRA, CERT, etc.

  • Fully integrated within the PlatformIO ecosystem and easy to execute on the entire project.
  • Straightforward integration with Continuous Integration services.
  • Possibility to reuse the same setup on other projects.
  • Easy and flexible rule configuration.
  • Comprehensive and detailed error information
  • Multiple architectures and development platforms.
  • Cross-platform: Windows, MacOS, Linux.



  • Potential NULL pointer dereferences
  • Possible indexing beyond array bounds
  • Suspicious assignments
  • Reads of potentially uninitialized objects
  • Unused variables or functions
  • Out of scope memory usage


WARNING:

Before performimg a static analysis check, make sure your project builds without errors. For information about how to build a project, see the platformio run command or VSCode guide.


There is the rich and friendly interface for PIO Check in PlatformIO Home. It allows you to filter messages or directly jump to an issue in a source code. [image] [image]

PIO Check allows selecting what tool is used for finding defects in the project, what source files are checked. PIO Check can be configured from "platformio.ini" (Project Configuration File) using the next options:

You can switch between or specify multiple tools used for finding defects using check_tool option:

[env:myenv]
platform = ...
board = ...
check_tool = cppcheck, clangtidy


Detailed information about supported check tools and their configuration process can be found on these pages:

Cppcheck is a static analysis tool for C/C++ code. It provides a unique code analysis to detect bugs and focuses on detecting undefined behavior and dangerous coding constructs. The goal is to detect only real errors in the code (i.e. have very few false positives). More information about this tool on the official webpage.

HINT:

Cppcheck is rarely wrong about reported errors. But there are many bugs that it doesn't detect. You will find more bugs in your software by testing your software carefully than by using Cppcheck.


  • Features
  • Additional checks
  • Configuration
  • Extra flags
  • Suppressing warnings
  • Addons (MISRA, CERT)
  • MISRA
  • CERT


Cppcheck supports a wide variety of static checks that may not be covered by the compiler itself. These checks are static analysis checks that can be performed at a source code level. The program is directed towards static analysis checks that are rigorous, rather than heuristic in nature.

  • Automatic variable checking
  • Bounds checking for array overruns
  • Classes checking (e.g. unused functions, variable initialization, and memory duplication)
  • Usage of deprecated or superseded functions
  • Exception safety checking, for example, usage of memory allocation and destructor checks
  • Memory leaks, e.g. due to lost scope without deallocation
  • Resource leaks, e.g. due to forgetting to close a file handle
  • Invalid usage of Standard Template Library functions and idioms
  • Miscellaneous stylistic and performance errors


Be default Cppcheck is configured to check the next additional defects:

  • warning
  • style
  • performance
  • portability
  • unusedFunction

The full list of supported check with detailed description is located on the official webpage.

Cppcheck is implicitly used as the default check tool when check_tool option in "platformio.ini" (Project Configuration File) is not set. To be explicit, you can specify it in the configuration directly:

[env:myenv]
platform = ...
board = ...
check_tool = cppcheck
check_flags = --enable=all


Useful options that can be used used for adjusting check process:

Extra flags

Useful flags that can help more precisely configure Cppcheck to satisfy your project requirements:

Flag Meaning
--enable=<id> Enable additional checks. The available ids are: all, warning, style, performance, portability, information, unusedFunction, missingInclude
--std=<id> Set standard. The available options are: c89, c99, c11, c++03, c++11, c++14, c++17, c++20 (default)
--language=<language> Forces Cppcheck to check all files as the given language. Valid values are: c, c++
--inline-suppr Enable inline suppressions. Use them by placing one or more comments, like: // cppcheck-suppress warningId on the lines before the warning to suppress (enabled by default if no extra flags specified).
--suppress=<spec> Suppress warnings that match <spec>. The format of <spec> is: [error id]:[filename]:[line]
--platform=<type> Specifies platform-specific types and sizes. The available built-in platforms are: unix32, unix64, win32A, win32W, win64, avr8, native, unspecified (default)
--inconclusive Allow reporting defects even though the analysis is inconclusive.
-D<ID> Define a preprocessor symbol. Example: -DDEBUG=1
-U<ID> Undefine preprocessor symbol. Use -U to explicitly hide certain #ifdef <ID> code paths from checking. Example: -UDEBUG
-I <dir> Give a path to search for include files. Give several -I parameters to give several paths.
-j <jobs> Start <jobs> threads to do the checking simultaneously.


It might be useful to explicitly instruct Cppcheck to ignore some of the known defects in project codebase. Since --inline-suppr is enabled by default, it's possible to directly mark pieces of code that will be excluded from Cppcheck report using // cppcheck-suppress warningId syntax.

NOTE:

Warning ID can be found in square brackets at the end of defect description, for example: src\Blink.cpp:17: [low:style] The function 'loop' is never used. [unusedFunction]


By default, PIO Check command doesn't scan framework sources and that's why some functions from in your project might be reported as unused. For example, you can ignore warnings about setup and loop functions from Arduino-based projects:

// cppcheck-suppress unusedFunction
void setup()
{
  ...
}
// cppcheck-suppress unusedFunction
void loop()
{
  ...
}


Cppcheck provides several addon scripts that analyze dump files to check compatibility with secure coding standards and to locate various issues. Most useful addons for verifying compliance with popular guidelines are MISRA and CERT.

MISRA is a proprietary set of software development guidelines for the C/C++ programming languages developed by MISRA (Motor Industry Software Reliability Association). It aims to facilitate code safety, security, portability, and reliability in the context of embedded systems, specifically those systems programmed in ISO C/C++.

NOTE:

Since this standard is proprietary, Cppcheck does not display error text by specifying only the number of violated rules (for example, [c2012-21.3]). If you want to display full texts for violated rules, you will need to create a text file containing MISRA rules, which you will have to pass when calling the script with --rule-texts flag.


In order to use MISRA addon you will need to provide a special file with the description of MISRA rules. Usually, it has the next contents:

Appendix A Summary of guidelines
Rule 3.1 Required
R3.1 Rule description
Rule 4.1 Required
...
Rule 21.3 Required
R21.3 Rule description
Rule 21.4
R21.4 Rule description


Next, you need to instruct Cppcheck that you want to run an additional addon script. Since this script requires an additional file with rules, you can pass it via a special json file:

{
  "script": "addons/misra.py",
  "args": ["--rule-texts=misra-rules.txt"]
}


Finally, add new flag to check_flags:

[env:myenv]
platform = ...
board = ...
check_tool = cppcheck
check_flags =
  cppcheck: --addon=misra.json


The full list of implemented MISRA checks can be found on the official webpage.

SEI CERT coding standard provides rules for secure coding in the C programming language. The goal of these rules and recommendations is to develop safe, reliable, and secure systems, for example by eliminating undefined behaviors that can lead to undefined program behaviors and exploitable vulnerabilities.

In order to use the CERT addon, simply specify it as an additional flag in check_flags section:

[env:myenv]
platform = ...
board = ...
check_tool = cppcheck
check_flags =
  cppcheck: --addon=cert.py


Clang-Tidy is a clang-based C++ "linter" tool. Its purpose is to provide an extensible framework for diagnosing and fixing typical programming errors, like style violations, interface misuse, or bugs that can be deduced via static analysis. Official page can be found here.

  • Features
  • Configuration
  • Supported checks
  • Extra flags

Clang-Tidy supports a large variety of static checks that may not be covered by the compiler itself. These checks are static analysis checks that can be performed at a source code level.

Some of the defects that might be detected include:

  • Buffer overflow
  • Potential NULL pointer dereferences
  • Use of memory that has already been deallocated
  • Out of scope memory usage
  • Failure to set a return value from a subroutine

To enable Clang-Tidy tool simply add it to the check_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
check_tool = clangtidy


Useful options that can be used used for adjusting check process:

There are currently the following groups of most used checks (By default all checks are enabled):

Check Description
abseil- Checks related to Abseil library.
boost- Checks related to Boost library.
bugprone- Checks that target bugprone code constructs.
cert- Checks related to CERT Secure Coding Guidelines.
cppcoreguidelines- Checks related to C++ Core Guidelines.
clang-analyzer- Clang Static Analyzer checks.
google- Checks related to Google coding conventions.
hicpp- Checks related to High Integrity C++ Coding Standard.
modernize- Checks that advocate usage of modern (currently modern means C++11) language constructs.
performance- Checks that target performance-related issues.
portability- Checks that target portability-related issues that don’t relate to any particular coding style.
readability- Checks that target readability-related issues that don’t relate to any particular coding style.


The full list of supported checks can be found on the official webpage.

Extra flags

Useful flags that can help more precisely configure Clang-Tidy to satisfy your project requirements:

Flag Meaning
--checks=<string> Comma-separated list of enabled checks (* default)
--fix Apply suggested fixes. Without -fix-errors clang-tidy will bail out if any compilation errors were found.
--fix-errors Apply suggested fixes even if compilation errors were found. If compiler errors have attached fix-its, clang-tidy will apply them as well.
--format-style=<string> Style for formatting code around applied fixes: llvm, google, webkit, mozilla, none (default)
--system-headers Display the errors from system headers.


An example with enabling specific checks and fixing code on the fly:

[env:myenv]
platform = ...
board = ...
check_tool = clangtidy
check_flags =
  clangtidy: --checks=-*,cert-*,clang-analyzer-* --fix


PVS-Studio is a static code analysis tool for detecting bugs and security weaknesses in the source code of programs, written in C, C++, C# and Java. It analyze source code intended for 32-bit, 64-bit and embedded ARM platforms. Official page can be found here.

  • Features
  • Configuration
  • Extra flags
  • Obtaining license

PVS-Studio performs a wide range of code checks, and it is also useful in finding misprints and Copy-Paste errors. These checks are static analysis checks that can be performed at a source code level. Some of the defects that might be detected include:

  • Arithmetic over/underflow
  • Array index out of bounds
  • Undefined/unspecified behavior
  • Incorrect usage of exceptions
  • Buffer overrun
  • Null pointer/null reference dereference
  • Improper understanding of function/class operation logic
  • Illegal bitwise/shift operations

The full list of supported checks can be found on the official webpage.

To enable PVS-Studio tool simply add it to the check_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
check_tool = pvs-studio


Useful options that can be used used for adjusting check process:

Extra flags

Useful flags that can help more precisely configure PVS-Studio to satisfy your project requirements:

Flag Meaning
--analysis-mode <arg> Analysis mode (0 - full analysis (default), 1 - 64-bit. analysis, 2 - reserved, 4 - general analysis, 8 - optimization, 16 - customer's specific requests, 32 - MISRA)
--analyzer-errors <arg> Errors activation (Default: all errors is on)
--errors-off <arg> Errors OFF (Default: all errors is on)
--exclude-path <arg> All code that is located under the path will be excluded from analysis
--lic-file <arg> Path to custom license file. Default locations ~/.config/PVS-Studio/PVS-Studio.lic on Unix and %APPDATA%\PVS-Studio\PVS-Studio.lic on Windows
--rules-config <arg> Specifies the path to rules configuration file.
--platform <arg> Platform name (Win32, x64, etc) (Default: ARM)


An example with a special analysis mode, disabled errors and license file:

[env:myenv]
platform = ...
board = ...
check_tool = pvs-studio
check_flags =
  pvs-studio: --analysis-mode=4 --errors-off=V532,V586 --lic-file=/path/to/file.lic


Since PVS-Studio is a paid B2B solution, a license should be purchased. But PVS-Studio can be used for free of charge, for example for checking open source projects. More information about the cases when you can get a free PVS-Studio license can be found on the official webpage.

TIP:

If you're experiencing problems with the license file or see the following error message: License information is incorrect. Please check your registration data or contact Customer Support, try saving the license file in UTF-8 + BOM format with the following contents: 

name@domain.com
AAAA-BBBB-CCCC-DDDD




Defect severity is a classification of software defect (bug, vulnerability, etc) that indicates the degree of negative impact on the quality of software. PIO Check uses the next classification of possible defects:

Severity Meaning
high Issues that are possibly bugs
medium Suggestions about defensive programming in order to prevent potential bugs
low Issues related to code cleanup and performance (unused functions, redundant code, const-ness, etc)

CLI Guide

PIO Check can be configured using command line commands. Detailed description of these commands can be found here:

Your devices are always with you!

PIO Remote allows you to work remotely with devices from Anywhere In The World. No matter where are you now! Run a small and cross-platform PIO Remote Agent on a remote machine and you are able to list active devices (wireless + wired), to upload firmware (program), to process remote unit tests, or to start remote debugging session via Remote Serial Port Monitor.

Using PIO Remote you can share your devices with colleagues across your organization or friends. In combination with Cloud IDE, you can create awesome things at any time when inspiration comes to you.

You should have PIO Account to work with PIO Remote. A registration is FREE.

•
PIO Remote
  • Features
  • Use Cases
  • Technology
  • Installation
  • Quick Start
  • CLI Guide


  • Remote Device Manager
  • Remote Serial Port Monitor
  • Remote Firmware Updates
  • PIO Remote Share
  • Continuous Deployment
  • Continuous Delivery
  • Remote Unit Testing

Program your devices from anywhere in the world using the most popular Cloud IDE. You do not need to install any extra software, no need to have static IP or open network ports. Everything works out of the box.
Work with your favorite development environment and program devices connected to card-sized PC (Raspberry Pi, Cubie Board, etc.). You do not need to open SSH ports, install any extra Linux packages, toolchains.
Remote Unit Testing
Instruct any of Continuous Integration services to run remote tests on a physical device. See the documentation for Remote Test Runner.

How does it work?

  • You commit new changes to your source code repository
  • Continuous Integration service deploys unit tests to a remote agent
  • PIO Unit Testing engine runs tests on a physical device, process them, and send results
  • Continuous Integration service prints results in human readable format
  • If one test fails, current CI build will fail too.

A similar concept as described in "Remote Unit Testing" above. Let's imagine that you need to test some logic on the unlimited number of target devices. Very often it can be the same hardware prototype but with different factory revisions.

You connect these devices via USB hub to PC and instruct PIO Remote to process your test on ALL targets connected to a specific agent. See documentation below.

Remote Serial Monitor
Sometimes you don't have physical access to a target device but you need to read data from some serial port. PIO Remote allows you to connect to a remote agent and list connected devices with their serial ports. See platformio remote device monitor command for details.

[image]

PIO Remote is an own PlatformIO technology for remote solutions without external dependencies to operating system or its software based on client-server architecture. The Server component (PlatformIO Cloud) plays a role of coupling link between PIO Remote Agent and Client (PlatformIO Remote CLI, Cloud IDE, Continuous Integration, SDKs, etc.). When you start PIO Remote Agent, it connects over the Internet with PlatformIO Cloud and listen for the actions/commands which you can send in Client role from anywhere in the world.

PIO Remote is multi-agents and multi-clients system. A single agent can be shared with multiple clients, where different clients can use the same agent. This approach allows one to work with distributed hardware located in the different places, networks, etc.

This technology allows one to work with remote devices in generic form as you do that with local devices using PlatformIO ecosystem. The only one difference is a prefix "remote" before each generic PlatformIO command. For example, listing of local and remote devices will look like platformio device list and platformio remote device list.

PIO Remote is built into PlatformIO IDE. Please open PlatformIO IDE Terminal and run pio remote --help command for usage (see PlatformIO Remote CLI).

If you do not have PlatformIO IDE, or use Cloud IDE or a card-sized PC (Raspberry Pi, BeagleBoard, etc.), please install PlatformIO Core (CLI).

Quick Start

1.
Start PIO Remote Agent using platformio remote agent start command on a remote machine where devices are connected physically or are accessible via network. PIO Remote Agent works on Windows, macOS, Linux and Linux ARMv6+. It means that you can use desktop machine, laptop or credit card sized PC (Raspberry Pi, BeagleBoard, etc).

You can share own devices/hardware with friends, team or other developers using platformio remote agent start --share option.

2.
Using host machine (PlatformIO Remote CLI, Cloud IDE Terminal in a browser, SDKs, etc.), please authorize via platformio account login command with the same credentials that you used on the previous step. Now, you can use PlatformIO Remote CLI commands to work with remote machine and its devices.

You don't need to have networking or other access to remote machine where PIO Remote Agent is started.

If you use PIO Remote in pair with Continuous Integration or want automatically authorize, please set PLATFORMIO_AUTH_TOKEN system environment variable instead of using platformio account login command.


NOTE:

In case with Cloud IDE, your browser with Cloud IDE's VM is a "host machine". The machine where devices are connected physically (your real PC) is called "remote machine" in this case. You should run PIO Remote Agent here (not in Cloud IDE's Terminal).


NOTE:

Please use local IP as "upload port" when device is not connected directly to a remote machine where PIO Remote Agent is started but supports natively Over-the-Air (OTA) updates. For example, Espressif 8266 and Over-the-Air (OTA) update. In this case, the final command for remote OTA update will look as platformio remote run -t upload --upload-port 192.168.0.255 or platformio remote run -t upload --upload-port myesp8266.local.


CLI Guide

It Simply Works. Easier than ever before!

NOTE:

Demo, discussions, request a support for new hardware.


PlatformIO offers a unique debugging experience for productive embedded development. Using our multi-board and multi-architecture programming experience, we simplified the debugging process in the same way. A zero debugging configuration with support for the most popular debugging probes and compatibility between IDEs and OS.

Developers can finally forget about complex UI windows which they need to pre-configure before a simple “Hello World!” debugging session. No need to know any aspects about the debugging server or how to configure it. PIO Unified Debugger does this complex work automatically having a rich configuration database per each board and debugging probe.

Just select a board, connect debugging probe (if a board does not have onboard debugging interface), specify it in PlatformIO project configuration file “platformio.ini”, and a project is ready for 1-Click debugging.

  • "1-click" solution, zero configuration
  • Support over 300+ embedded boards (see below)
  • Multiple architectures and development platforms
  • Windows, MacOS, Linux
  • Built-in into PlatformIO IDE for Atom and VSCode
  • Integration with Eclipse and Sublime Text

You should have PIO Account to work with PIO Unified Debugger. A registration is FREE.

HINT:

In our experience, VSCode has the best system performance, modern interface for PIO Unified Debugger, and users have found it easier to get started. Key debugging features of VSCode:
  • Local, Global, and Static Variable Explorer
  • Conditional Breakpoints
  • Expressions and Watchpoints
  • Generic Registers
  • Peripheral Registers
  • Memory Viewer
  • Disassembly
  • Multi-thread support
  • A hot restart of an active debugging session



.SS Contents
  • Tutorials
  • Configuration
  • Tools & Debug Probes
  • CLI Guide
  • Platforms
  • Frameworks
  • Boards

  • Arduino In-circuit Debugging with PlatformIO
  • Use the PlatformIO Debugger on the ESP32 Using an ESP-prog
  • ThingForward: First steps with PlatformIO’s Unified Debugger
  • [VIDEO] ThingForward - Intro to PIO Unified Debugger using ARM mbed OS and PlatformIO IDE for VSCode
  • Get started with Arduino and ESP32-DevKitC: debugging and unit testing
  • Get started with ESP-IDF and ESP32-DevKitC: debugging, unit testing, project analysis
  • Arduino and Nordic nRF52-DK: debugging and unit testing
  • Zephyr and Nordic nRF52-DK: debugging, unit testing, project analysis
  • STM32Cube HAL and Nucleo-F401RE: debugging and unit testing

PIO Unified Debugger can be configured from "platformio.ini" (Project Configuration File):

Tools & Debug Probes

You can switch between debugging tools using debug_tool option.

WARNING:

You will need to install debug tool drivers depending on your operating system. Please check "Drivers" section for debugging tool below.


USB Blaster Download Cable is designed for ALTERA FPGA, CPLD, Active Serial Configuration Devices and Enhanced Configuration Devices, USB 2.0 connection to the PC and JTAG, AS, PS to the target device. Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
•
JTAG Interface

  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = altera-usb-blaster


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = altera-usb-blaster
upload_protocol = altera-usb-blaster


More options:

  • Debugging options
  • Upload options

Please install official drivers.

Wiring Connections

[image]

JTAG Interface

USB-Blaster JTAG 10-Pin Connector Board JTAG Pin Description
1 TCK JTAG Return Test Clock
2 GND Digital ground
3 TDO Test Data Out pin
4 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
5 TMS Test Mode State pin
9 TDI Test Data In pin

Name Description
GigaDevice GD32V The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.
Nuclei Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.

Name Description
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.
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)
Nuclei SDK Open Source Software Development Kit for the Nuclei N/NX processors

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
GD32VF103V Evaluation Kit Nuclei External GD32VF103VBT6 108MHz 128KB 32KB
GD32VF103V RVStar Kit Nuclei On-board GD32VF103VBT6 108MHz 128KB 32KB
GD32VF103V-EVAL GigaDevice GD32V External GD32VF103VBT6 108MHz 128KB 32KB
Sipeed Longan Nano GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V External GD32VF103C8T6 108MHz 64KB 20KB
Wio Lite RISC-V GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB

Atmel-ICE

Atmel-ICE is a powerful development tool for debugging and programming ARM® Cortex®-M based SAM and AVR microcontrollers with on-chip debug capability. Official reference can be found here.

  • Configuration
  • Drivers
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = atmel-ice


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = atmel-ice
upload_protocol = atmel-ice


More options:

  • Debugging options
  • Upload options

When installing the Atmel-ICE on a computer running Microsoft Windows, the USB driver is loaded when the Atmel-ICE is first plugged in.
Not required.
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Name Description
Atmel SAM Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.

Name Description
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.
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
Adafruit Circuit Playground Express Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Crickit M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 Express Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Gemma M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit Grand Central M4 Atmel SAM External SAMD51P20A 120MHz 1MB 256KB
Adafruit Hallowing M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Hallowing M4 Atmel SAM External SAMD51J19A 120MHz 496KB 192KB
Adafruit ItsyBitsy M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit ItsyBitsy M4 Atmel SAM External SAMD51G19A 120MHz 512KB 192KB
Adafruit MONSTER M4SK Atmel SAM External SAMD51G19A 120MHz 496KB 192KB
Adafruit Metro M0 Expresss Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Metro M4 Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Metro M4 AirLift Lite Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit PyGamer Advance M4 Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit PyGamer M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit PyPortal M4 Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit PyPortal M4 Titano Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit Trellis M4 Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Trinket M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit pIRkey Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit pyBadge AirLift M4 Atmel SAM External SAMD51J20A 120MHz 1008KB 192KB
Adafruit pyBadge M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Arduino Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Native USB Port) Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino MKR FOX 1200 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR GSM 1400 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR NB 1500 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1300 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1310 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WiFi 1010 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR1000 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKRZERO Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino Tian Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (USB Native Port) Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Atmel ATSAMR21-XPRO Atmel SAM On-board SAMR21G18A 48MHz 256KB 32KB
Atmel ATSAMW25-XPRO Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Atmel SAMC21-XPRO Atmel SAM On-board SAMC21J18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO Atmel SAM On-board SAMD21J18A 48MHz 256KB 32KB
Atmel SAML21-XPRO-B Atmel SAM On-board SAML21J18B 48MHz 256KB 32KB
Briki ABC (MBC-WB) - Samd21 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Briki MBC-WB - Samd21 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Digistump DigiX Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
MKR Vidor 4000 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Minitronics v2.0 Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
Moteino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
NANO 33 IoT Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SODAQ Autonomo Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ ExpLoRer Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ ONE Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SODAQ SARA Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ SFF Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SainSmart Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
SainSmart Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Seeeduino LoRaWAN Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun 9DoF Razor IMU M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun Qwiic Micro Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
SparkFun RedBoard Turbo Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Dev Breakout Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Mini Breakout Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Pro RF Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Tuino 096 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

The Black Magic Probe is a modern, in-application debugging tool for embedded microprocessors. It is able to control and examine the state of the target microprocessor using a JTAG or Serial Wire Debugging (SWD) port and on-chip debug logic provided by the microprocessor. The probe connects to a host computer using a standard USB interface. Official reference can be found here.

Also, see Custom debugging configuration with Black Magic Probe.

  • Configuration
  • Drivers
  • Wiring Connections
  • JTAG Interface
  • Serial Wire Mode Interface (SWD)

  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = blackmagic
debug_port = <CONFIGURE GDB PORT>
;
; Debug Port Examples
;
; Linux
debug_port = /dev/ttyACM0
; Windows for COM1-COM9
debug_port = COM3
; Windows for COM10-XXX
debug_port = \\.\COM13
; macOS
debug_port = /dev/cu.usbmodemE2C0C4C6


Black Magic Probe has 2 serial ports: UART and GDB. We will need "GDB" port. Please use PlatformIO Home > Devices or PlatformIO Core (CLI) and platformio device list command to list available ports. If you do not see "Black Magic Probe GDB" port, please try both. More details.

If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = blackmagic
debug_port = <CONFIGURE GDB PORT>
upload_port = <THE SAME AS DEBUG PORT>
; SWD interface
upload_protocol = blackmagic
; JTAG interface
upload_protocol = blackmagic-jtag


More options:

  • Debugging options
  • Upload options

Not required.

Wiring Connections

JTAG Interface

[image]

Black Magic Probe 10-Pin Connector Board JTAG Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
3 GND Digital ground
2 TMS Test Mode State
4 TCLK JTAG Return Test Clock
6 TDO Test Data Out
8 TDI Test Data In
10 RESET Connect this pin to the (active low) reset input of the target CPU

Serial Wire Mode Interface (SWD)

[image]

Black Magic Probe 10-Pin Connector Board SWD Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
3 GND Digital ground
2 SWDIO Data I/O
4 SWCLK Clock
10 RESET Connect this pin to the (active low) reset input of the target CPU

Name Description
Aceinna IMU Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.
Atmel SAM Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Freescale Kinetis Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.
Nordic nRF51 The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.
Nordic nRF52 The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.
NXP i.MX RT The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.
NXP LPC The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.
Silicon Labs EFM32 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.
ST STM32 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.

Name Description
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.
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.
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.
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.
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.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
1Bitsy ST STM32 External STM32F415RGT 168MHz 1MB 128KB
32F412GDISCOVERY ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
32F723EDISCOVERY ST STM32 On-board STM32F723IEK6 216MHz 512KB 192KB
3D Printer Controller ST STM32 External STM32F407VET6 168MHz 512KB 192KB
3D Printer control board ST STM32 External STM32F446RET6 180MHz 512KB 128KB
3D printer controller ST STM32 On-board STM32F765VIT6 216MHz 2MB 512KB
3DP001V1 Evaluation board for 3D printer ST STM32 On-board STM32F401VGT6 84MHz 512KB 96KB
96Boards Argonkey (STEVAL-MKI187V1) ST STM32 External STM32F412CG 100MHz 1MB 256KB
96Boards B96B-F446VE ST STM32 On-board STM32F446VET6 168MHz 512KB 128KB
96Boards Neonkey ST STM32 External STM32F411CE 100MHz 512KB 128KB
96Boards Nitrogen Nordic nRF52 External NRF52832 64MHz 512KB 64KB
ARM mbed LPC11U24 (+CAN) NXP LPC On-board LPC11U24 48MHz 32KB 8KB
Aceinna Low Cost RTK Aceinna IMU On-board STM32F469NIH6 180MHz 1MB 384KB
Aceinna OpenIMU 300 Aceinna IMU External STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 300ZA Aceinna IMU External STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 330 Aceinna IMU External STM32L431CB 80MHz 128KB 64KB
Aceinna OpenIMU 330ZA Aceinna IMU External STM32F469IG 180MHz 1MB 384KB
Aceinna OpenRTK330L Aceinna IMU External STM32F469IG 180MHz 1MB 384KB
Adafruit Circuit Playground Express Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Crickit M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 Express Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather STM32F405 ST STM32 External STM32F405RGT6 168MHz 1MB 128KB
Adafruit Gemma M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit Hallowing M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit ItsyBitsy M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Metro M0 Expresss Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Trinket M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit pIRkey Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
AfroFlight Rev5 (8MHz) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
Arduino Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Native USB Port) Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino MKR FOX 1200 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR GSM 1400 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR NB 1500 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1300 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1310 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WiFi 1010 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR1000 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKRZERO Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino Tian Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (USB Native Port) Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Armstrap Eagle 1024 ST STM32 On-board STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 ST STM32 On-board STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB
Atmel ATSAMR21-XPRO Atmel SAM On-board SAMR21G18A 48MHz 256KB 32KB
Atmel ATSAMW25-XPRO Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Atmel SAMC21-XPRO Atmel SAM On-board SAMC21J18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO Atmel SAM On-board SAMD21J18A 48MHz 256KB 32KB
Atmel SAML21-XPRO-B Atmel SAM On-board SAML21J18B 48MHz 256KB 32KB
BL652 Development Kit Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
BL654 Development Kit Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Bambino-210E NXP LPC On-board LPC4330 204MHz 8MB 264KB
Black STM32F407VE ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
BlackPill F303CC ST STM32 External STM32F303CCT6 72MHz 256KB 40KB
BlackPill F401CC ST STM32 External STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini ST STM32 External STM32F407VET6 168MHz 512KB 128KB
BluePill F103C6 ST STM32 External STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
Bluey nRF52832 IoT Nordic nRF52 External NRF52832 64MHz 512KB 64KB
BluzDK Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Briki ABC (MBC-WB) - Samd21 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Briki MBC-WB - Samd21 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
CQ Publishing TG-LPC11U35-501 NXP LPC External LPC11U35 48MHz 64KB 10KB
CoCo-ri-Co! NXP LPC On-board LPC812 30MHz 16KB 4KB
Core board F401RCT6 ST STM32 External STM32F401RCT6 84MHz 256KB 64KB
Delta DFBM-NQ620 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Demo F030F4 ST STM32 External STM32F030F4P6 48MHz 16KB 4KB
Digistump DigiX Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
EA LPC11U35 QuickStart Board NXP LPC External LPC11U35 48MHz 64KB 10KB
EFM32GG-STK3700 Giant Gecko Silicon Labs EFM32 On-board EFM32GG990F1024 48MHz 1MB 128KB
EFM32LG-STK3600 Leopard Gecko Silicon Labs EFM32 On-board EFM32LG990F256 48MHz 256KB 32KB
EFM32WG-STK3800 Wonder Gecko Silicon Labs EFM32 On-board EFM32WG990F256 48MHz 256KB 32KB
EFM32ZG-STK3200 Zero Gecko Silicon Labs EFM32 On-board EFM32ZG222F32 24MHz 32KB 4KB
ElectronutLabs Blip Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
ElectronutLabs Papyr Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Espotel LoRa Module ST STM32 External STM32F411RET6 100MHz 512KB 128KB
F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB
FK407M1 ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Freescale Kinetis FRDM-KL25Z Freescale Kinetis On-board MKL25Z128VLK4 48MHz 128KB 16KB
Freescale Kinetis FRDM-KL27Z Freescale Kinetis On-board MKL27Z64VLH4 48MHz 64KB 16KB
Holyiot YJ-16019 Nordic nRF52 External NRF52832 64MHz 512KB 64KB
L476DMW1K ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
LPCXpresso11U68 NXP LPC On-board LPC11U68 50MHz 256KB 36KB
LPCXpresso824-MAX NXP LPC On-board LPC824 30MHz 32KB 8KB
M200 V2 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
M300 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
MKR Sharky ST STM32 External STM32WB55CG 64MHz 512KB 192.00KB
MKR Vidor 4000 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
MTS Dragonfly ST STM32 External STM32F411RET6 100MHz 512KB 128KB
Makerdiary nRF52832-MDK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Makerdiary nRF52840-MDK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Malyan M200 V1 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB
Maple ST STM32 External STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) ST STM32 External STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original ST STM32 External STM32F103CBT6 72MHz 108KB 17KB
Mbed Connect Cloud ST STM32 On-board STM32F439ZIY6 168MHz 2MB 256KB
Microduino Core STM32 to Flash ST STM32 External STM32F103CBT6 72MHz 105.47KB 16.60KB
Microsoft Azure IoT Development Kit (MXChip AZ3166) ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
Minitronics v2.0 Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
Moteino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
MultiTech mDot ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot F411 ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech xDot ST STM32 External STM32L151CCU6 32MHz 256KB 32KB
NAMote72 ST STM32 External STM32L152RC 32MHz 256KB 32KB
NANO 33 IoT Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
NGX Technologies BlueBoard-LPC11U24 NXP LPC External LPC11U24 48MHz 32KB 8KB
NXP LPC11C24 NXP LPC External LPC11C24 48MHz 32KB 8KB
NXP LPC11U34 NXP LPC External LPC11U34 48MHz 40KB 8KB
NXP LPC11U37 NXP LPC External LPC11U37 48MHz 128KB 10KB
NXP LPC800-MAX NXP LPC On-board LPC812 30MHz 16KB 4KB
NXP LPCXpresso1549 NXP LPC External LPC1549 72MHz 256KB 36KB
NXP i.MX RT1010 Evaluation Kit NXP i.MX RT On-board MIMXRT1011DAE5A 500MHz 64KB 128KB
NXP i.MX RT1015 Evaluation Kit NXP i.MX RT On-board MIMXRT1015DAF5A 500MHz 96KB 128KB
NXP i.MX RT1020 Evaluation Kit NXP i.MX RT On-board MIMXRT1021DAG5A 500MHz 64MB 256MB
NXP i.MX RT1050 Evaluation Kit NXP i.MX RT On-board MIMXRT1052DVL6B 600MHz 64MB 512KB
NXP i.MX RT1060 Evaluation Kit NXP i.MX RT On-board MIMXRT1062DVL6A 600MHz 64MB 1MB
NXP i.MX RT1064 Evaluation Kit NXP i.MX RT On-board MIMXRT1064DVL6A 600MHz 4MB 1MB
NXP mbed LPC11U24 NXP LPC On-board LPC11U24 48MHz 32KB 8KB
NXP mbed LPC1768 NXP LPC On-board LPC1768 96MHz 512KB 64KB
Nordic Beacon Kit (PCA20006) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic Thingy:52 (nRF52-PCA20020) Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Nucleo G071RB ST STM32 External STM32G071RBT6 64MHz 128KB 36KB
Nucleo G431KB ST STM32 External STM32G431KBT6 170MHz 128KB 32KB
Nucleo G431RB ST STM32 External STM32G431RBT6 170MHz 128KB 32KB
Nucleo G474RE ST STM32 External STM32G474RET6 170MHz 512KB 128KB
OLIMEXINO-STM32 ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
OSHChip Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Olimex STM32-P405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB
P-Nucleo WB55RG ST STM32 On-board STM32WB55RG 64MHz 512KB 192.00KB
Piconomix PX-HER0 ST STM32 External STM32L072RB 32MHz 128KB 20KB
PrntrBoard V2 ST STM32 External STM32F407RE 168MHz 512KB 192KB
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 16KB
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 32KB
RHF76 052 ST STM32 External STM32L051C8T6 32MHz 64KB 8KB
RedBearLab BLE Nano 1.5 Nordic nRF51 On-board NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab Blend 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab nRF51822 Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
RushUp Cloud-JAM ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
RushUp Cloud-JAM L4 ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
SDT52832B Nordic nRF52 External NRF52832 64MHz 512KB 64KB
SLSTK3400A USB-enabled Happy Gecko Silicon Labs EFM32 On-board EFM32HG322F64 25MHz 64KB 8KB
SLSTK3401A Pearl Gecko PG1 Silicon Labs EFM32 On-board EFM32PG1B200F256GM48 40MHz 256KB 32KB
SODAQ Autonomo Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ ExpLoRer Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ ONE Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SODAQ SARA Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ SFF Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
ST 32F3348DISCOVERY ST STM32 On-board STM32F334C8T6 72MHz 64KB 12KB
ST 32F401CDISCOVERY ST STM32 On-board STM32F401VCT6 84MHz 256KB 64KB
ST 32F411EDISCOVERY ST STM32 On-board STM32F411VET6 100MHz 512KB 128KB
ST 32F413HDISCOVERY ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 On-board STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY ST STM32 On-board STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY ST STM32 On-board STM32F769NIH6 216MHz 1MB 512KB
ST 32L0538DISCOVERY ST STM32 On-board STM32L053C8T6 32MHz 64KB 8KB
ST 32L100DISCOVERY ST STM32 On-board STM32L100RCT6 32MHz 256KB 16KB
ST 32L476GDISCOVERY ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY ST STM32 On-board STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 On-board STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 On-board STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F031K6 ST STM32 On-board STM32F031K6T6 48MHz 32KB 4KB
ST Nucleo F042K6 ST STM32 On-board STM32F042K6T6 48MHz 32KB 6KB
ST Nucleo F070RB ST STM32 On-board STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F091RC ST STM32 On-board STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 On-board STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 On-board STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 On-board STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 ST STM32 On-board STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE ST STM32 On-board STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F303ZE ST STM32 On-board STM32F303ZET6 72MHz 512KB 64KB
ST Nucleo F334R8 ST STM32 On-board STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F410RB ST STM32 On-board STM32F410RBT6 100MHz 128KB 32KB
ST Nucleo F411RE ST STM32 On-board STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F439ZI ST STM32 On-board STM32F439ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 On-board STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F446ZE ST STM32 On-board STM32F446ZET6 180MHz 512KB 128KB
ST Nucleo F722ZE ST STM32 On-board STM32F722ZET6 216MHz 512KB 256KB
ST Nucleo F746ZG ST STM32 On-board STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG ST STM32 On-board STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI ST STM32 On-board STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI ST STM32 On-board STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L011K4 ST STM32 On-board STM32L011K4T6 32MHz 16KB 2KB
ST Nucleo L031K6 ST STM32 On-board STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 ST STM32 On-board STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 On-board STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE ST STM32 On-board STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L412KB ST STM32 On-board STM32L412KBU6 80MHz 128KB 40KB
ST Nucleo L432KC ST STM32 On-board STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L433RC-P ST STM32 On-board STM32L433RC 80MHz 256KB 64KB
ST Nucleo L452RE ST STM32 On-board STM32L452RET6 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L486RG ST STM32 On-board STM32L486RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 On-board STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P ST STM32 On-board STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI ST STM32 On-board STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST STM32F0DISCOVERY ST STM32 On-board STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY ST STM32 On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32L073Z-EVAL ST STM32 On-board STM32L073VZT6 32MHz 192KB 20KB
ST STM32LDISCOVERY ST STM32 On-board STM32L152RBT6 32MHz 128KB 16KB
ST STM32VLDISCOVERY ST STM32 On-board STM32F100RBT6 24MHz 128KB 8KB
ST Sensor Node ST STM32 On-board STM32L476JG 80MHz 1MB 128KB
STEVAL-FCU001V1 Flight controller unit evaluation board ST STM32 External STM32F401CCU6 84MHz 256KB 64KB
STM32-E407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM3210C-EVAL ST STM32 External STM32F107VCT6 72MHz 256KB 64KB
STM32373C-EVAL ST STM32 External STM32F373VCT6 72MHz 256KB 32KB
STM32F072-EVAL ST STM32 External STM32F072VBT6 48MHz 128KB 16KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 External STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 External STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 External STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 External STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 External STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 External STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 External STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 External STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 External STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 External STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 External STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 External STM32F103ZET6 72MHz 512KB 64KB
STM32F303CB (32k RAM. 128k Flash) ST STM32 External STM32F303CBT6 72MHz 128KB 32KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 External STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 External STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 External STM32F401RE 84MHz 512KB 96KB
STM32F7508-DK ST STM32 On-board STM32F750N8H6 216MHz 64KB 340KB
STM32H747I-DISCO ST STM32 On-board STM32H747XIH6 400MHz 2MB 512KB
SainSmart Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
SainSmart Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Seeed Arch BLE Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB
Seeed Arch Link Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Arch Max ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB
Seeed Tiny BLE Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Wio 3G ST STM32 On-board STM32F439VI 180MHz 2MB 256KB
Seeeduino LoRaWAN Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SensorTile.box ST STM32 External STM32L4R9ZI 120MHz 2MB 640KB
Sino:Bit Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Solder Splash Labs DipCortex M0 NXP LPC External LPC11U24 50MHz 32KB 8KB
SparkFun 9DoF Razor IMU M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun Qwiic Micro Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
SparkFun RedBoard Turbo Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Dev Breakout Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Mini Breakout Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Pro RF Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Sparky V1 F303 ST STM32 External STM32F303CCT6 72MHz 256KB 40KB
Switch Science mbed LPC1114FN28 NXP LPC On-board LPC1114FN28 48MHz 32KB 4KB
Switch Science mbed LPC824 NXP LPC On-board LPC824 30MHz 32KB 8KB
Taida Century nRF52 mini board Nordic nRF52 External NRF52832 64MHz 512KB 64KB
ThunderPack ST STM32 External STM32L072KZ 32MHz 192KB 20KB
Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT Silicon Labs EFM32 On-board EFR32MG12P432F1024 40MHz 1MB 256KB
Tiny STM103T ST STM32 External STM32F103TBU6 72MHz 128KB 20KB
Tuino 096 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
VAkE v1.0 ST STM32 External STM32F446RET6 180MHz 512KB 128KB
VNG VBLUno52 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Waveshare BLE400 Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Wraith V1 ESC ST STM32 External STM32F051K6 48MHz 32KB 7.75KB
hackaBLE Nordic nRF52 External NRF52832 64MHz 512KB 64KB
ng-beacon Nordic nRF51 External NRF51822 16MHz 256KB 32KB
sakura.io Evaluation Board ST STM32 On-board STM32F411RET6 100MHz 1MB 128KB
u-blox C027 NXP LPC On-board LPC1768 96MHz 512KB 64KB
u-blox C030-N211 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox C030-R410M IoT ST STM32 On-board STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox EVK-NINA-B1 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
u-blox EVK-ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB
u-blox ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB
y5 LPC11U35 mbug NXP LPC External LPC11U35 48MHz 64KB 10KB
y5 nRF51822 mbug Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

CMSIS-DAP

CMSIS-DAP is generally implemented as an on-board interface chip, providing direct USB connection from a development board to a debugger running on a host computer on one side, and over JTAG (Joint Test Action Group) or SWD (Serial Wire Debug) to the target device to access the Coresight DAP on the other. Official reference can be found here.

  • Configuration
  • Drivers
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = cmsis-dap


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = cmsis-dap
upload_protocol = cmsis-dap


More options:

  • Debugging options
  • Upload options

Please install Windows serial driver and check "USB Driver Installation" guide for your board.
Not required.
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Name Description
Atmel SAM Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Freescale Kinetis Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.
Maxim 32 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.
Nordic nRF51 The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.
Nordic nRF52 The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.
NXP LPC The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.
ST STM32 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.
WIZNet W7500 The IOP (Internet Offload Processor) W7500 is the one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform especially requiring Internet of things

Name Description
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.
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.
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.
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.
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.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
ARM mbed LPC11U24 (+CAN) NXP LPC On-board LPC11U24 48MHz 32KB 8KB
Arduino M0 Pro (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino Nano 33 BLE Nordic nRF52 External NRF52840 64MHz 960KB 256KB
Arduino Zero (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Atmel ATSAMR21-XPRO Atmel SAM On-board SAMR21G18A 48MHz 256KB 32KB
Atmel ATSAMW25-XPRO Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Atmel SAMC21-XPRO Atmel SAM On-board SAMC21J18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO Atmel SAM On-board SAMD21J18A 48MHz 256KB 32KB
Atmel SAML21-XPRO-B Atmel SAM On-board SAML21J18B 48MHz 256KB 32KB
BBC micro:bit Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
BL652 Development Kit Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
BL654 Development Kit Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Bambino-210E NXP LPC On-board LPC4330 204MHz 8MB 264KB
Calliope mini Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
CoCo-ri-Co! NXP LPC On-board LPC812 30MHz 16KB 4KB
Delta DFBM-NQ620 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Delta DFCM-NNN40 Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Delta DFCM-NNN50 Nordic nRF51 On-board NRF51822 32MHz 256KB 16KB
ElectronutLabs Blip Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
ElectronutLabs Papyr Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Embedded Artists LPC4088 Display Module NXP LPC On-board LPC4088 120MHz 512KB 96KB
Embedded Artists LPC4088 QuickStart Board NXP LPC On-board LPC4088 120MHz 512KB 96KB
Ethernet IoT Starter Kit Freescale Kinetis On-board MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K20D50M Freescale Kinetis On-board MK20DX128VLH5 48MHz 128KB 16KB
Freescale Kinetis FRDM-K22F Freescale Kinetis On-board MK22FN512VLH12 120MHz 512KB 128KB
Freescale Kinetis FRDM-K64F Freescale Kinetis On-board MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K66F Freescale Kinetis On-board MK66FN2M0VMD18 180MHz 2MB 256KB
Freescale Kinetis FRDM-K82F Freescale Kinetis On-board MK82FN256VLL15 150MHz 256KB 256KB
Freescale Kinetis FRDM-KL05Z Freescale Kinetis On-board MKL05Z32VFM4 48MHz 32KB 4KB
Freescale Kinetis FRDM-KL25Z Freescale Kinetis On-board MKL25Z128VLK4 48MHz 128KB 16KB
Freescale Kinetis FRDM-KL27Z Freescale Kinetis On-board MKL27Z64VLH4 48MHz 64KB 16KB
Freescale Kinetis FRDM-KL43Z Freescale Kinetis On-board MKL43Z256VLH4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL46Z Freescale Kinetis On-board MKL46Z256VLL4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KW41Z Freescale Kinetis On-board MKW41Z512VHT4 48MHz 512KB 128KB
Hexiwear Freescale Kinetis External MK64FN1M0VDC12 120MHz 1MB 256KB
Holyiot YJ-16019 Nordic nRF52 External NRF52832 64MHz 512KB 64KB
JKSoft Wallbot BLE Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB
L476DMW1K ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
LPCXpresso11U68 NXP LPC On-board LPC11U68 50MHz 256KB 36KB
LPCXpresso824-MAX NXP LPC On-board LPC824 30MHz 32KB 8KB
Makerdiary nRF52832-MDK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Makerdiary nRF52840-MDK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Maxim ARM mbed Enabled Development Platform for MAX32600 Maxim 32 On-board MAX32600 24MHz 256KB 32KB
Maxim Wireless Sensor Node Demonstrator Maxim 32 External MAX32610 24MHz 256KB 32KB
Mbed Connect Cloud ST STM32 On-board STM32F439ZIY6 168MHz 2MB 256KB
Moteino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
NXP LPC800-MAX NXP LPC On-board LPC812 30MHz 16KB 4KB
NXP LPCXpresso54114 NXP LPC On-board LPC54114J256BD64 100MHz 256KB 192KB
NXP mbed LPC11U24 NXP LPC On-board LPC11U24 48MHz 32KB 8KB
NXP mbed LPC1768 NXP LPC On-board LPC1768 96MHz 512KB 64KB
Nordic Beacon Kit (PCA20006) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic Thingy:52 (nRF52-PCA20020) Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Nordic nRF51 Dongle (PCA10031) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF51822-mKIT Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
RedBearLab BLE Nano 1.5 Nordic nRF51 On-board NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab Blend 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab nRF51822 Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
SDT52832B Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Seeed Arch BLE Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB
Seeed Arch Link Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Arch Pro NXP LPC On-board LPC1768 96MHz 512KB 64KB
Seeed Tiny BLE Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Switch Science mbed HRM1017 Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Switch Science mbed LPC1114FN28 NXP LPC On-board LPC1114FN28 48MHz 32KB 4KB
Switch Science mbed LPC824 NXP LPC On-board LPC824 30MHz 32KB 8KB
Switch Science mbed TY51822r3 Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
VNG VBLUNO51 Nordic nRF51 On-board NRF51822 16MHz 128KB 32KB
VNG VBLUno52 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
WIZwiki-W7500 WIZNet W7500 On-board WIZNET7500 48MHz 128KB 48KB
WIZwiki-W7500ECO WIZNet W7500 On-board WIZNET7500ECO 48MHz 128KB 48KB
WIZwiki-W7500P WIZNet W7500 On-board WIZNET7500P 48MHz 128KB 48KB
sakura.io Evaluation Board ST STM32 On-board STM32F411RET6 100MHz 1MB 128KB
u-blox C027 NXP LPC On-board LPC1768 96MHz 512KB 64KB
u-blox C030-N211 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
y5 nRF51822 mbug Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

ESP-Prog is one of Espressif’s development and debugging tools, with functions including automatic firmware downloading, serial communication, and JTAG online debugging. ESP-Prog's automatic firmware downloading and serial communication functions are supported on both the ESP8266 and ESP32 platforms, while the JTAG online debugging is supported only on the ESP32 platform. Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
  • Tutorials
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = esp-prog


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = esp-prog
upload_protocol = esp-prog


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

[image]

ESP-Prog JTAG 10-Pin Connector Board JTAG Pin Description
1 VDD Positive Supply Voltage — Power supply for JTAG interface drivers
3 GND Digital ground
2 ESP_TMS Test Mode State
4 ESP_TCK JTAG Return Test Clock
6 ESP_TDO Test Data Out
8 ESP_TDI Test Data In

•
Use the PlatformIO Debugger on the ESP32 Using an ESP-prog

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

FTDI Chip develops innovative silicon solutions that enhance interaction with today’s technology. When a designer needs to add a USB port, rest assured that FTDI Chip has a full range of USB solutions to get the job done. Official reference can be found here.

  • Configuration
  • Drivers
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = ftdi


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = ftdi
upload_protocol = ftdi


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
RISC-V 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.
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.
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.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
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.
PULP OS PULP is a silicon-proven Parallel Ultra Low Power platform targeting high energy efficiencies. The platform is organized in clusters of RISC-V cores that share a tightly-coupled data memory.
Shakti SDK A software development kit for developing applications on Shakti class of processors
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
Artix-7 35T Arty FPGA Evaluation Kit Shakti On-board E-CLASS 50MHz 0B 128KB
Arty A7-100: Artix-7 FPGA Development Board Shakti On-board C-CLASS 50MHz 0B 128MB
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
GAPuino GAP8 RISC-V GAP On-board GAP8 250MHz 64MB 8MB
HiFive Unleashed SiFive On-board FU540 1500MHz 32MB 8GB
HiFive1 SiFive On-board FE310 320MHz 16MB 16KB

GD-Link adapter is a three-in-one multi-function development tool for GD32 series of MCUs. It provides CMSIS-DAP debugger port with JTAG/SWD interface. Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
  • JTAG Interface
  • Serial Wire Mode Interface (SWD)

  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = gd-link


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = gd-link
upload_protocol = gd-link


More options:

  • Debugging options
  • Upload options

Check vendor recommendations.
Not required.
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

JTAG Interface

GD-Link JTAG 20-Pin Connector Board JTAG Pin Description
+3V3 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
TMS/IO TMS Test Mode State pin
TCK/CLK TCK JTAG Return Test Clock
TDO/SWO TDO Test Data Out pin
TDI TDI Test Data In pin
GDN GND Digital ground
TReset RESET Connect this pin to the (active low) reset input of the target CPU

Serial Wire Mode Interface (SWD)

GD-Link SWD 20-Pin Connector Board SWD Pin Description
+3V3 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
GND GND Digital ground
TMS/IO SWDIO Data I/O
TCK/CLK SWCLK Clock
TReset RESET Connect this pin to the (active low) reset input of the target CPU

Name Description
GigaDevice GD32V The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.
Nuclei Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.

Name Description
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.
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)
Nuclei SDK Open Source Software Development Kit for the Nuclei N/NX processors

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
GD32VF103V Evaluation Kit Nuclei External GD32VF103VBT6 108MHz 128KB 32KB
GD32VF103V RVStar Kit Nuclei On-board GD32VF103VBT6 108MHz 128KB 32KB
GD32VF103V-EVAL GigaDevice GD32V External GD32VF103VBT6 108MHz 128KB 32KB
Sipeed Longan Nano GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V External GD32VF103C8T6 108MHz 64KB 20KB
Wio Lite RISC-V GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB

This IoT-Bus module provides JTAG debugging for the oddWires IoT-Bus Io and oddWires IoT-Bus Proteus boards (can be used with other boards too, see wiring connections below). The board uses the FT232H to provide a USB controller with JTAG support. Both debugging and flashing is possible using this port. Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = iot-bus-jtag


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = iot-bus-jtag
upload_protocol = iot-bus-jtag


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

IOT-Bus JTAG Pin Board JTAG Pin Description
3V3 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
GND GND Digital ground
12 TDI Test Data In pin
14 TMS Test Mode State pin
13 TCK JTAG Return Test Clock
15 TDO Test Data Out pin
EN RESET Connect this pin to the (active low) reset input of the target CPU (EN for ESP32)

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

SEGGER J-Links are the most widely used line of debug probes available today. They've proven their value for more than 10 years with over 400,000 units sold, including OEM versions and on-board solutions. This popularity stems from the unparalleled performance, extensive feature set, large number of supported CPUs, and compatibility with all popular development environments. Official reference can be found here.

•
J-Link Supported Devices

Also, see Custom debugging configuration with J-Link GDB Server.

•
Configuration
•
Custom Server

  • Drivers
  • Wiring Connections
  • JTAG Interface
  • Serial Wire Mode Interface (SWD)

  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = jlink


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = jlink
; SWD interface
upload_protocol = jlink
; JTAG interface
upload_protocol = jlink-jtag


More options:

  • Debugging options
  • Upload options

[env:debug_jlink]
platform = ststm32
framework = mbed
board = nucleo_f446re
debug_tool = jlink
debug_port = :2331
debug_server =
  /full/path/to/JLinkGDBServerCL
  -singlerun
  -if
  SWD
  -select
  USB
  -port
  2331
  -device
  STM32F446RE


1.
Start debugging session using PlatformIO IDE. PlatformIO will install J-Link software dependencies
2.
Navigate to core_dir/packages/tool-jlink/USBDriver
3.
Run InstDrivers.exe.

Not required.
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

[image]

JTAG Interface

J-Link JTAG 20-Pin Connector Board JTAG Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
4 GND Digital ground
5 TDI Test Data In pin
7 TMS Test Mode State pin
9 TCK JTAG Return Test Clock
13 TDO Test Data Out pin
15 RESET Connect this pin to the (active low) reset input of the target CPU (EN for ESP32)

Serial Wire Mode Interface (SWD)

J-Link SWD 20-Pin Connector Board SWD Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
4 GND Digital ground
7 SWDIO Data I/O
9 SWCLK Clock
15 RESET Connect this pin to the (active low) reset input of the target CPU

Name Description
Aceinna IMU Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.
Atmel SAM Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Freescale Kinetis Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.
GigaDevice GD32V The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.
Infineon XMC Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.
Maxim 32 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.
Nordic nRF51 The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.
Nordic nRF52 The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.
Nuclei Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.
NXP i.MX RT The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.
NXP LPC The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.
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.
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.
Silicon Labs EFM32 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.
ST STM32 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.
Teensy Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.
WIZNet W7500 The IOP (Internet Offload Processor) W7500 is the one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform especially requiring Internet of things

Name Description
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.
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support
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.
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.
Nuclei SDK Open Source Software Development Kit for the Nuclei N/NX processors
Shakti SDK A software development kit for developing applications on Shakti class of processors
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.
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.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
1Bitsy ST STM32 External STM32F415RGT 168MHz 1MB 128KB
32F412GDISCOVERY ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
32F723EDISCOVERY ST STM32 On-board STM32F723IEK6 216MHz 512KB 192KB
3D Printer Controller ST STM32 External STM32F407VET6 168MHz 512KB 192KB
3D Printer control board ST STM32 External STM32F446RET6 180MHz 512KB 128KB
3D printer controller ST STM32 On-board STM32F765VIT6 216MHz 2MB 512KB
3DP001V1 Evaluation board for 3D printer ST STM32 On-board STM32F401VGT6 84MHz 512KB 96KB
96Boards Argonkey (STEVAL-MKI187V1) ST STM32 External STM32F412CG 100MHz 1MB 256KB
96Boards B96B-F446VE ST STM32 On-board STM32F446VET6 168MHz 512KB 128KB
96Boards Neonkey ST STM32 External STM32F411CE 100MHz 512KB 128KB
96Boards Nitrogen Nordic nRF52 External NRF52832 64MHz 512KB 64KB
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
ARM mbed LPC11U24 (+CAN) NXP LPC On-board LPC11U24 48MHz 32KB 8KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB
Aceinna Low Cost RTK Aceinna IMU On-board STM32F469NIH6 180MHz 1MB 384KB
Aceinna OpenIMU 300 Aceinna IMU External STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 300ZA Aceinna IMU External STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 330 Aceinna IMU External STM32L431CB 80MHz 128KB 64KB
Aceinna OpenIMU 330ZA Aceinna IMU External STM32F469IG 180MHz 1MB 384KB
Aceinna OpenRTK330L Aceinna IMU External STM32F469IG 180MHz 1MB 384KB
Adafruit Bluefruit nRF52832 Feather Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Adafruit Circuit Playground Express Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Crickit M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Adafruit Feather Bluefruit Sense Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Adafruit Feather M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 Express Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Feather STM32F405 ST STM32 External STM32F405RGT6 168MHz 1MB 128KB
Adafruit Feather nRF52840 Express Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Adafruit Gemma M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit Grand Central M4 Atmel SAM External SAMD51P20A 120MHz 1MB 256KB
Adafruit Hallowing M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Hallowing M4 Atmel SAM External SAMD51J19A 120MHz 496KB 192KB
Adafruit ItsyBitsy M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit ItsyBitsy M4 Atmel SAM External SAMD51G19A 120MHz 512KB 192KB
Adafruit MONSTER M4SK Atmel SAM External SAMD51G19A 120MHz 496KB 192KB
Adafruit Metro M0 Expresss Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Metro M4 Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Metro M4 AirLift Lite Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit PyGamer Advance M4 Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit PyGamer M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit PyPortal M4 Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit PyPortal M4 Titano Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit Trellis M4 Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Trinket M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit pIRkey Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit pyBadge AirLift M4 Atmel SAM External SAMD51J20A 120MHz 1008KB 192KB
Adafruit pyBadge M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
AfroFlight Rev5 (8MHz) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
Arduino Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Native USB Port) Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino MKR FOX 1200 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR GSM 1400 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR NB 1500 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1300 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1310 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WiFi 1010 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR1000 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKRZERO Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino Nano 33 BLE Nordic nRF52 External NRF52840 64MHz 960KB 256KB
Arduino Tian Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (USB Native Port) Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Armstrap Eagle 1024 ST STM32 On-board STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 ST STM32 On-board STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB
Artix-7 35T Arty FPGA Evaluation Kit Shakti On-board E-CLASS 50MHz 0B 128KB
Arty A7-100: Artix-7 FPGA Development Board Shakti On-board C-CLASS 50MHz 0B 128MB
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB
Atmel ATSAMR21-XPRO Atmel SAM On-board SAMR21G18A 48MHz 256KB 32KB
Atmel ATSAMW25-XPRO Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Atmel SAMC21-XPRO Atmel SAM On-board SAMC21J18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO Atmel SAM On-board SAMD21J18A 48MHz 256KB 32KB
Atmel SAML21-XPRO-B Atmel SAM On-board SAML21J18B 48MHz 256KB 32KB
BBC micro:bit Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
BL652 Development Kit Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
BL654 Development Kit Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Bambino-210E NXP LPC On-board LPC4330 204MHz 8MB 264KB
Black STM32F407VE ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
BlackPill F303CC ST STM32 External STM32F303CCT6 72MHz 256KB 40KB
BlackPill F401CC ST STM32 External STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini ST STM32 External STM32F407VET6 168MHz 512KB 128KB
BluePill F103C6 ST STM32 External STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
Bluey nRF52832 IoT Nordic nRF52 External NRF52832 64MHz 512KB 64KB
BluzDK Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki ABC (MBC-WB) - Samd21 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - Samd21 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
CQ Publishing TG-LPC11U35-501 NXP LPC External LPC11U35 48MHz 64KB 10KB
Calliope mini Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Circuit Playground Bluefruit Nordic nRF52 External NRF52840 64MHz 796KB 243KB
CoCo-ri-Co! NXP LPC On-board LPC812 30MHz 16KB 4KB
Core board F401RCT6 ST STM32 External STM32F401RCT6 84MHz 256KB 64KB
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB
Delta DFBM-NQ620 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Demo F030F4 ST STM32 External STM32F030F4P6 48MHz 16KB 4KB
Digistump DigiX Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
DipCortex M3 NXP LPC External LPC1347 72MHz 64KB 12KB
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB
EA LPC11U35 QuickStart Board NXP LPC External LPC11U35 48MHz 64KB 10KB
EFM32GG-STK3700 Giant Gecko Silicon Labs EFM32 On-board EFM32GG990F1024 48MHz 1MB 128KB
EFM32LG-STK3600 Leopard Gecko Silicon Labs EFM32 On-board EFM32LG990F256 48MHz 256KB 32KB
EFM32WG-STK3800 Wonder Gecko Silicon Labs EFM32 On-board EFM32WG990F256 48MHz 256KB 32KB
EFM32ZG-STK3200 Zero Gecko Silicon Labs EFM32 On-board EFM32ZG222F32 24MHz 32KB 4KB
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB
ElectronutLabs Blip Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
ElectronutLabs Papyr Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Embedded Artists LPC4088 Display Module NXP LPC On-board LPC4088 120MHz 512KB 96KB
Embedded Artists LPC4088 QuickStart Board NXP LPC On-board LPC4088 120MHz 512KB 96KB
Espotel LoRa Module ST STM32 External STM32F411RET6 100MHz 512KB 128KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB
Ethernet IoT Starter Kit Freescale Kinetis On-board MK64FN1M0VLL12 120MHz 1MB 256KB
F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB
FK407M1 ST STM32 External STM32F407VET6 168MHz 512KB 128KB
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Freescale Kinetis FRDM-K20D50M Freescale Kinetis On-board MK20DX128VLH5 48MHz 128KB 16KB
Freescale Kinetis FRDM-K22F Freescale Kinetis On-board MK22FN512VLH12 120MHz 512KB 128KB
Freescale Kinetis FRDM-K64F Freescale Kinetis On-board MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K66F Freescale Kinetis On-board MK66FN2M0VMD18 180MHz 2MB 256KB
Freescale Kinetis FRDM-K82F Freescale Kinetis On-board MK82FN256VLL15 150MHz 256KB 256KB
Freescale Kinetis FRDM-KL05Z Freescale Kinetis On-board MKL05Z32VFM4 48MHz 32KB 4KB
Freescale Kinetis FRDM-KL25Z Freescale Kinetis On-board MKL25Z128VLK4 48MHz 128KB 16KB
Freescale Kinetis FRDM-KL27Z Freescale Kinetis On-board MKL27Z64VLH4 48MHz 64KB 16KB
Freescale Kinetis FRDM-KL43Z Freescale Kinetis On-board MKL43Z256VLH4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL46Z Freescale Kinetis On-board MKL46Z256VLL4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL82Z Freescale Kinetis External MKL82Z128VLK7 96MHz 128KB 96KB
Freescale Kinetis FRDM-KW24D512 Freescale Kinetis External MKW24D512 50MHz 512KB 64KB
Freescale Kinetis FRDM-KW41Z Freescale Kinetis On-board MKW41Z512VHT4 48MHz 512KB 128KB
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
GD32VF103V Evaluation Kit Nuclei External GD32VF103VBT6 108MHz 128KB 32KB
GD32VF103V RVStar Kit Nuclei On-board GD32VF103VBT6 108MHz 128KB 32KB
GD32VF103V-EVAL GigaDevice GD32V External GD32VF103VBT6 108MHz 128KB 32KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB
Hexiwear Freescale Kinetis External MK64FN1M0VDC12 120MHz 1MB 256KB
HiFive1 Rev B SiFive On-board FE310 320MHz 16MB 16KB
Holyiot YJ-16019 Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB
ItsyBitsy nRF52840 Express Nordic nRF52 On-board NRF52840 64MHz 796KB 243KB
L476DMW1K ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
LPCXpresso11U68 NXP LPC On-board LPC11U68 50MHz 256KB 36KB
LPCXpresso824-MAX NXP LPC On-board LPC824 30MHz 32KB 8KB
M200 V2 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
M300 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
MAX32620FTHR Maxim 32 External MAX32620FTHR 96MHz 2MB 256KB
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB
MKR Sharky ST STM32 External STM32WB55CG 64MHz 512KB 192.00KB
MKR Vidor 4000 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
MTS Dragonfly ST STM32 External STM32F411RET6 100MHz 512KB 128KB
Makerdiary nRF52832-MDK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Makerdiary nRF52840-MDK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Malyan M200 V1 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB
Maple ST STM32 External STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) ST STM32 External STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original ST STM32 External STM32F103CBT6 72MHz 108KB 17KB
Maxim Health Sensor Platform Maxim 32 External MAX32620 96MHz 2MB 256KB
Mbed Connect Cloud ST STM32 On-board STM32F439ZIY6 168MHz 2MB 256KB
Metro nRF52840 Express Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Microduino Core STM32 to Flash ST STM32 External STM32F103CBT6 72MHz 105.47KB 16.60KB
Microsoft Azure IoT Development Kit (MXChip AZ3166) ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
Minitronics v2.0 Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
Moteino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
MultiTech mDot ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot F411 ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech xDot ST STM32 External STM32L151CCU6 32MHz 256KB 32KB
N2+ ST STM32 External STM32F405RGT6 168MHz 1MB 192KB
NAMote72 ST STM32 External STM32L152RC 32MHz 256KB 32KB
NANO 33 IoT Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
NGX Technologies BlueBoard-LPC11U24 NXP LPC External LPC11U24 48MHz 32KB 8KB
NXP LPC11C24 NXP LPC External LPC11C24 48MHz 32KB 8KB
NXP LPC11U34 NXP LPC External LPC11U34 48MHz 40KB 8KB
NXP LPC11U37 NXP LPC External LPC11U37 48MHz 128KB 10KB
NXP LPC800-MAX NXP LPC On-board LPC812 30MHz 16KB 4KB
NXP LPCXpresso1549 NXP LPC External LPC1549 72MHz 256KB 36KB
NXP LPCXpresso54114 NXP LPC On-board LPC54114J256BD64 100MHz 256KB 192KB
NXP LPCXpresso54608 NXP LPC On-board LPC54608ET512 180MHz 512KB 200KB
NXP i.MX RT1010 Evaluation Kit NXP i.MX RT On-board MIMXRT1011DAE5A 500MHz 64KB 128KB
NXP i.MX RT1015 Evaluation Kit NXP i.MX RT On-board MIMXRT1015DAF5A 500MHz 96KB 128KB
NXP i.MX RT1020 Evaluation Kit NXP i.MX RT On-board MIMXRT1021DAG5A 500MHz 64MB 256MB
NXP i.MX RT1050 Evaluation Kit NXP i.MX RT On-board MIMXRT1052DVL6B 600MHz 64MB 512KB
NXP i.MX RT1060 Evaluation Kit NXP i.MX RT On-board MIMXRT1062DVL6A 600MHz 64MB 1MB
NXP i.MX RT1064 Evaluation Kit NXP i.MX RT On-board MIMXRT1064DVL6A 600MHz 4MB 1MB
NXP mbed LPC11U24 NXP LPC On-board LPC11U24 48MHz 32KB 8KB
NXP mbed LPC1768 NXP LPC On-board LPC1768 96MHz 512KB 64KB
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB
Nordic Beacon Kit (PCA20006) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic Thingy:52 (nRF52-PCA20020) Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Nordic nRF51 Dongle (PCA10031) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Nordic nRF52840-DK (Adafruit BSP) Nordic nRF52 On-board NRF52840 64MHz 796KB 243KB
Nucleo G071RB ST STM32 External STM32G071RBT6 64MHz 128KB 36KB
Nucleo G431KB ST STM32 External STM32G431KBT6 170MHz 128KB 32KB
Nucleo G431RB ST STM32 External STM32G431RBT6 170MHz 128KB 32KB
Nucleo G474RE ST STM32 External STM32G474RET6 170MHz 512KB 128KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEXINO-STM32 ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
OSHChip Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Olimex STM32-P405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB
P-Nucleo WB55RG ST STM32 On-board STM32WB55RG 64MHz 512KB 192.00KB
Particle Argon Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Particle Boron Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Particle Xenon Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Piconomix PX-HER0 ST STM32 External STM32L072RB 32MHz 128KB 20KB
PrntrBoard V2 ST STM32 External STM32F407RE 168MHz 512KB 192KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 16KB
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 32KB
RHF76 052 ST STM32 External STM32L051C8T6 32MHz 64KB 8KB
RedBearLab BLE Nano 1.5 Nordic nRF51 On-board NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab Blend 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab nRF51822 Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
RushUp Cloud-JAM ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
RushUp Cloud-JAM L4 ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
SDT52832B Nordic nRF52 External NRF52832 64MHz 512KB 64KB
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB
SLSTK3400A USB-enabled Happy Gecko Silicon Labs EFM32 On-board EFM32HG322F64 25MHz 64KB 8KB
SLSTK3401A Pearl Gecko PG1 Silicon Labs EFM32 On-board EFM32PG1B200F256GM48 40MHz 256KB 32KB
SODAQ Autonomo Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ ExpLoRer Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ ONE Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SODAQ SARA Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ SFF Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
ST 32F3348DISCOVERY ST STM32 On-board STM32F334C8T6 72MHz 64KB 12KB
ST 32F401CDISCOVERY ST STM32 On-board STM32F401VCT6 84MHz 256KB 64KB
ST 32F411EDISCOVERY ST STM32 On-board STM32F411VET6 100MHz 512KB 128KB
ST 32F413HDISCOVERY ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 On-board STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY ST STM32 On-board STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY ST STM32 On-board STM32F769NIH6 216MHz 1MB 512KB
ST 32L0538DISCOVERY ST STM32 On-board STM32L053C8T6 32MHz 64KB 8KB
ST 32L100DISCOVERY ST STM32 On-board STM32L100RCT6 32MHz 256KB 16KB
ST 32L476GDISCOVERY ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY ST STM32 On-board STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 On-board STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 On-board STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F031K6 ST STM32 On-board STM32F031K6T6 48MHz 32KB 4KB
ST Nucleo F042K6 ST STM32 On-board STM32F042K6T6 48MHz 32KB 6KB
ST Nucleo F070RB ST STM32 On-board STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F091RC ST STM32 On-board STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 On-board STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 On-board STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 On-board STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 ST STM32 On-board STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE ST STM32 On-board STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F303ZE ST STM32 On-board STM32F303ZET6 72MHz 512KB 64KB
ST Nucleo F334R8 ST STM32 On-board STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F410RB ST STM32 On-board STM32F410RBT6 100MHz 128KB 32KB
ST Nucleo F411RE ST STM32 On-board STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F439ZI ST STM32 On-board STM32F439ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 On-board STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F446ZE ST STM32 On-board STM32F446ZET6 180MHz 512KB 128KB
ST Nucleo F722ZE ST STM32 On-board STM32F722ZET6 216MHz 512KB 256KB
ST Nucleo F746ZG ST STM32 On-board STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG ST STM32 On-board STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI ST STM32 On-board STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI ST STM32 On-board STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L011K4 ST STM32 On-board STM32L011K4T6 32MHz 16KB 2KB
ST Nucleo L031K6 ST STM32 On-board STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 ST STM32 On-board STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 On-board STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE ST STM32 On-board STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L412KB ST STM32 On-board STM32L412KBU6 80MHz 128KB 40KB
ST Nucleo L432KC ST STM32 On-board STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L433RC-P ST STM32 On-board STM32L433RC 80MHz 256KB 64KB
ST Nucleo L452RE ST STM32 On-board STM32L452RET6 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L486RG ST STM32 On-board STM32L486RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 On-board STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P ST STM32 On-board STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI ST STM32 On-board STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST STM32F0DISCOVERY ST STM32 On-board STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY ST STM32 On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32L073Z-EVAL ST STM32 On-board STM32L073VZT6 32MHz 192KB 20KB
ST STM32LDISCOVERY ST STM32 On-board STM32L152RBT6 32MHz 128KB 16KB
ST STM32VLDISCOVERY ST STM32 On-board STM32F100RBT6 24MHz 128KB 8KB
ST Sensor Node ST STM32 On-board STM32L476JG 80MHz 1MB 128KB
STEVAL-FCU001V1 Flight controller unit evaluation board ST STM32 External STM32F401CCU6 84MHz 256KB 64KB
STM32-E407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM3210C-EVAL ST STM32 External STM32F107VCT6 72MHz 256KB 64KB
STM32373C-EVAL ST STM32 External STM32F373VCT6 72MHz 256KB 32KB
STM32F072-EVAL ST STM32 External STM32F072VBT6 48MHz 128KB 16KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 External STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 External STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 External STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 External STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 External STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 External STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 External STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 External STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 External STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 External STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 External STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 External STM32F103ZET6 72MHz 512KB 64KB
STM32F303CB (32k RAM. 128k Flash) ST STM32 External STM32F303CBT6 72MHz 128KB 32KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 External STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 External STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 External STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) ST STM32 External STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) ST STM32 External STM32F407VGT6 168MHz 1MB 192KB
STM32F4Stamp F405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB
STM32F7508-DK ST STM32 On-board STM32F750N8H6 216MHz 64KB 340KB
STM32H747I-DISCO ST STM32 On-board STM32H747XIH6 400MHz 2MB 512KB
SainSmart Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
SainSmart Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Seeed Arch BLE Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB
Seeed Arch Link Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Arch Max ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB
Seeed Tiny BLE Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Wio 3G ST STM32 On-board STM32F439VI 180MHz 2MB 256KB
Seeeduino LoRaWAN Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SensorTile.box ST STM32 External STM32L4R9ZI 120MHz 2MB 640KB
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Sino:Bit Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Sipeed Longan Nano GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V External GD32VF103C8T6 108MHz 64KB 20KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB
Solder Splash Labs DipCortex M0 NXP LPC External LPC11U24 50MHz 32KB 8KB
SparkFun 9DoF Razor IMU M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun Qwiic Micro Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
SparkFun RED-V RedBoard SiFive On-board FE310 320MHz 16MB 16KB
SparkFun RED-V Thing Plus SiFive On-board FE310 320MHz 16MB 16KB
SparkFun RedBoard Turbo Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Dev Breakout Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Mini Breakout Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Pro RF Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Sparky V1 F303 ST STM32 External STM32F303CCT6 72MHz 256KB 40KB
Switch Science mbed LPC1114FN28 NXP LPC On-board LPC1114FN28 48MHz 32KB 4KB
Switch Science mbed LPC824 NXP LPC On-board LPC824 30MHz 32KB 8KB
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB
Taida Century nRF52 mini board Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Teensy 3.1 / 3.2 Teensy External MK20DX256 72MHz 256KB 64KB
Teensy 3.5 Teensy External MK64FX512 120MHz 512KB 255.99KB
Teensy 3.6 Teensy External MK66FX1M0 180MHz 1MB 256KB
Teensy 4.0 Teensy External IMXRT1062 600MHz 1.94MB 512KB
Teensy 4.1 Teensy External IMXRT1062 600MHz 7.75MB 512KB
Teensy LC Teensy External MKL26Z64 48MHz 62KB 8KB
ThunderPack ST STM32 External STM32L072KZ 32MHz 192KB 20KB
Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT Silicon Labs EFM32 On-board EFR32MG12P432F1024 40MHz 1MB 256KB
Tiny STM103T ST STM32 External STM32F103TBU6 72MHz 128KB 20KB
Tuino 096 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
VAkE v1.0 ST STM32 External STM32F446RET6 180MHz 512KB 128KB
VNG VBLUno52 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WIZwiki-W7500 WIZNet W7500 On-board WIZNET7500 48MHz 128KB 48KB
WIZwiki-W7500ECO WIZNet W7500 On-board WIZNET7500ECO 48MHz 128KB 48KB
WIZwiki-W7500P WIZNet W7500 On-board WIZNET7500P 48MHz 128KB 48KB
Waveshare BLE400 Nordic nRF51 External NRF51822 32MHz 256KB 32KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB
Wio Lite RISC-V GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Wraith V1 ESC ST STM32 External STM32F051K6 48MHz 32KB 7.75KB
XMC1100 Boot Kit Infineon XMC On-board XMC1100 32MHz 64KB 16KB
XMC1100 H-Bridge 2Go Infineon XMC On-board XMC1100 32MHz 64KB 16KB
XMC1100 XMC2Go Infineon XMC On-board XMC1100 32MHz 64KB 16KB
XMC1300 Boot Kit Infineon XMC On-board XMC1300 32MHz 64KB 16KB
XMC1300 Sense2GoL Infineon XMC On-board XMC1300 32MHz 32KB 16KB
XMC1400 Boot Kit Infineon XMC On-board XMC1400 48MHz 1.95MB 16KB
XMC4200 Distance2Go Infineon XMC On-board XMC4200 80MHz 256KB 40KB
XMC4700 Relax Kit Infineon XMC On-board XMC4700 144MHz 2.00MB 1.95MB
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB
hackaBLE Nordic nRF52 External NRF52832 64MHz 512KB 64KB
ng-beacon Nordic nRF51 External NRF51822 16MHz 256KB 32KB
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB
sakura.io Evaluation Board ST STM32 On-board STM32F411RET6 100MHz 1MB 128KB
u-blox C027 NXP LPC On-board LPC1768 96MHz 512KB 64KB
u-blox C030-N211 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox C030-R410M IoT ST STM32 On-board STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox EVK-NINA-B1 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
u-blox EVK-ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB
u-blox ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB
y5 LPC11U35 mbug NXP LPC External LPC11U35 48MHz 64KB 10KB
y5 nRF51822 mbug Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

The FT2232H Mini Module is a USB to dual channel serial/MPSSE/FIFO interface converter module based on the FT2232H USB Hi-Speed IC. The FT2232H handles all the USB signalling and protocol handling. The module provides access to device I/O interfaces via 2 double row 0.1" pitch male connectors. The module is ideal for development purposes to quickly prove functionality of adding USB to a target design. Official reference can be found here

  • Configuration
  • Drivers
  • Wiring Connections
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = minimodule


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = minimodule
upload_protocol = minimodule


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

FT2232H Mini-Module Pin Board JTAG Pin Description
GND GND Digital ground
AD0 TCK JTAG Return Test Clock
AD1 TDI Test Data In
AD2 TDO Test Data Out
AD3 TMS Test Mode State
RESET# RESET Connect this pin to the (active low) reset input of the target CPU (EN for ESP32)

You will also need to connect Vbus [CN3-1] to Vcc [CN3-3] of FT2232H Mini-Module to power the FTDI chip. See FT2232H Mini-Module Datasheet

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.
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.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

The MSP debug stack (MSPDS) for all MSP430™ microcontrollers (MCUs) and SimpleLink™ MSP432™ devices consists of a static library on the host system side as well as an embedded firmware that runs on debug tools including the MSP-FET, MSP-FET430UIF or on-board eZ debuggers. It is the bridging element between all PC software and all MSP430 and SimpleLink MSP432 microcontroller derivatives and handles tasks such as code download, stepping through code or break points. Official reference can be found here.

  • Configuration
  • Drivers
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = mspdebug


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = mspdebug
upload_protocol = mspdebug


More options:

  • Debugging options
  • Upload options

Please "USB Driver Installation" guide for your board.
Not required.
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Name Description
TI MSP430 MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.

Name Description
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
TI FraunchPad MSP-EXP430FR5739LP TI MSP430 On-board MSP430FR5739 16MHz 15.37KB 1KB
TI LaunchPad MSP-EXP430F5529LP TI MSP430 On-board MSP430F5529 25MHz 47KB 8KB
TI LaunchPad MSP-EXP430FR2311LP TI MSP430 On-board MSP430FR2311 16MHz 3.75KB 1KB
TI LaunchPad MSP-EXP430FR2433LP TI MSP430 On-board MSP430FR2433 8MHz 15KB 4KB
TI LaunchPad MSP-EXP430FR4133LP TI MSP430 On-board MSP430FR4133 8MHz 15KB 2KB
TI LaunchPad MSP-EXP430FR5969LP TI MSP430 On-board MSP430FR5969 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430FR5994LP TI MSP430 On-board MSP430FR5994 16MHz 256KB 4KB
TI LaunchPad MSP-EXP430FR6989LP TI MSP430 On-board MSP430FR6989 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430G2 w/ MSP430G2231 TI MSP430 On-board MSP430G2231 1MHz 2KB 256B
TI LaunchPad MSP-EXP430G2 w/ MSP430G2452 TI MSP430 On-board MSP430G2452 16MHz 8KB 256B
TI LaunchPad MSP-EXP430G2553LP TI MSP430 On-board MSP430G2553 16MHz 16KB 512B

Olimex ARM-USB-OCD-H

High-speed 3-IN-1 fast USB ARM/ESP32 JTAG, USB-to-RS232 virtual port and power supply 5VDC device. Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = olimex-arm-usb-ocd-h


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = olimex-arm-usb-ocd-h
upload_protocol = olimex-arm-usb-ocd-h


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

[image]

Olimex ARM-USB-OCD-H JTAG 20-Pin Connector Board JTAG Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
4 GND Digital ground
5 TDI Test Data In pin
7 TMS Test Mode State pin
9 TCK JTAG Return Test Clock
13 TDO Test Data Out pin
3 RESET Connect this pin to the (active low) reset input of the target CPU (EN for ESP32)

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.
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.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

Olimex ARM-USB-OCD

3-IN-1 fast USB ARM/ESP32 JTAG, USB-to-RS232 virtual port and power supply 5-9-12VDC device (supported by OpenOCD ARM debugger software). Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = olimex-arm-usb-ocd


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = olimex-arm-usb-ocd
upload_protocol = olimex-arm-usb-ocd


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

[image]

Olimex ARM-USB-OCD JTAG 20-Pin Connector Board JTAG Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
4 GND Digital ground
5 TDI Test Data In pin
7 TMS Test Mode State pin
9 TCK JTAG Return Test Clock
13 TDO Test Data Out pin
3 RESET Connect this pin to the (active low) reset input of the target CPU (EN for ESP32)

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.
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.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

Olimex ARM-USB-TINY-H

Low-cost and high-speed ARM/ESP32 USB JTAG. Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = olimex-arm-usb-tiny-h


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = olimex-arm-usb-tiny-h
upload_protocol = olimex-arm-usb-tiny-h


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

[image]

Olimex ARM-USB-TINY-H JTAG 20-Pin Connector Board JTAG Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
4 GND Digital ground
5 TDI Test Data In pin
7 TMS Test Mode State pin
9 TCK JTAG Return Test Clock
13 TDO Test Data Out pin
3 RESET Connect this pin to the (active low) reset input of the target CPU (EN for ESP32)

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.
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.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

Olimex ARM-USB-TINY

Low-cost and high-speed ARM/ESP32 USB JTAG. Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = olimex-jtag-tiny


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = olimex-jtag-tiny
upload_protocol = olimex-jtag-tiny


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

[image]

Olimex ARM-USB-TINY 20-Pin Connector Board JTAG Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
4 GND Digital ground
5 TDI Test Data In pin
7 TMS Test Mode State pin
9 TCK JTAG Return Test Clock
13 TDO Test Data Out pin
3 RESET Connect this pin to the (active low) reset input of the target CPU (EN for ESP32)

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.
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.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

QEMU is a free and open-source emulator that performs hardware virtualization. Official reference can be found here.

  • Configuration
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = qemu


More options:

•
Debugging options

Name Description
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.

Name Description
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB
HiFive Unleashed SiFive On-board FU540 1500MHz 32MB 8GB
HiFive1 SiFive On-board FE310 320MHz 16MB 16KB

Renode is a development framework which accelerates IoT and embedded systems development by letting you simulate physical hardware systems - including both the CPU, peripherals, sensors, environment and wired or wireless medium between nodes. For more information, see Renode's official website.

  • Configuration
  • Installation
  • Platforms
  • Frameworks
  • Boards

You can configure Renode as a debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = renode


More options:

•
Debugging options

We will automatically install for you the latest Renode package using PlatformIO package manager. The only requirement is to install Mono/.NET framework.

On Windows 7, download and install .NET Framework 4.7. Windows 10 ships with .NET by default, so no action is required there.
Install Homebrew and the mono package using brew install mono.
Install the mono-complete package as per the installation instructions for various Linux distributions which can be found on the Mono project website.

Check the official Renode installation guide for more details.

Name Description
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.

Name Description
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB
HiFive Unleashed SiFive On-board FU540 1500MHz 32MB 8GB
HiFive1 SiFive On-board FE310 320MHz 16MB 16KB
HiFive1 Rev B SiFive On-board FE310 320MHz 16MB 16KB
SparkFun RED-V RedBoard SiFive On-board FE310 320MHz 16MB 16KB
SparkFun RED-V Thing Plus SiFive On-board FE310 320MHz 16MB 16KB

RISC-V emulator implemented with RISC-V development board. Unlike other emulators: RV-LINK interacts directly with GDB via a USB serial port and does not require an intermediary such as OpenOCD. Official reference can be found here.

  • Configuration
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = rv-link


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = rv-link
upload_protocol = rv-link


More options:

  • Debugging options
  • Upload options

Name Description
GigaDevice GD32V The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.
Nuclei Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.

Name Description
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.
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)
Nuclei SDK Open Source Software Development Kit for the Nuclei N/NX processors

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
GD32VF103V Evaluation Kit Nuclei External GD32VF103VBT6 108MHz 128KB 32KB
GD32VF103V RVStar Kit Nuclei On-board GD32VF103VBT6 108MHz 128KB 32KB
GD32VF103V-EVAL GigaDevice GD32V External GD32VF103VBT6 108MHz 128KB 32KB
HummingBird Evaluation Kit Nuclei On-board HUMMINGBIRD 5MHz 64KB 64KB
Sipeed Longan Nano GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V External GD32VF103C8T6 108MHz 64KB 20KB
Wio Lite RISC-V GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB

simavr is a lean, mean and hackable AVR simulator. Official reference can be found here.

  • Configuration
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = simavr


More options:

•
Debugging options

Name Description
Atmel AVR Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming

Name Description
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
ATmega128/A Atmel AVR On-board ATMEGA128 16MHz 127KB 4KB
ATmega1280 Atmel AVR On-board ATMEGA1280 16MHz 127KB 8KB
ATmega1281 Atmel AVR On-board ATMEGA1281 16MHz 127KB 8KB
ATmega1284 Atmel AVR On-board ATMEGA1284 16MHz 127KB 16KB
ATmega1284P Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
ATmega16 Atmel AVR On-board ATMEGA16 16MHz 15.50KB 1KB
ATmega164P/PA Atmel AVR On-board ATMEGA164P 16MHz 15.50KB 1KB
ATmega168/A Atmel AVR On-board ATMEGA168 16MHz 15.50KB 1KB
ATmega168P/PA Atmel AVR On-board ATMEGA168P 16MHz 15.50KB 1KB
ATmega2560 Atmel AVR On-board ATMEGA2560 16MHz 255KB 8KB
ATmega324A Atmel AVR On-board ATMEGA324A 16MHz 31.50KB 2KB
ATmega324P Atmel AVR On-board ATMEGA324P 16MHz 31.50KB 2KB
ATmega324PA Atmel AVR On-board ATMEGA324PA 16MHz 31.50KB 2KB
ATmega328 Atmel AVR On-board ATMEGA328 16MHz 31.50KB 2KB
ATmega328P/PA Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
ATmega48/A Atmel AVR On-board ATMEGA48 16MHz 4KB 512B
ATmega644P/PA Atmel AVR On-board ATMEGA644P 16MHz 63KB 4KB
ATmega8/A Atmel AVR On-board ATMEGA8 16MHz 7.50KB 1KB
ATmega88/A Atmel AVR On-board ATMEGA88 16MHz 7.50KB 1KB
ATmega88P/PA Atmel AVR On-board ATMEGA88P 16MHz 7.50KB 1KB
ATmega8P/PA Atmel AVR On-board ATMEGA48P 16MHz 4KB 512B
Adafruit Bluefruit Micro Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Circuit Playground Classic Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Feather 328P Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
Adafruit Feather 32u4 Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Flora Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Gemma Atmel AVR On-board ATTINY85 8MHz 8KB 512B
Adafruit ItsyBitsy 3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit ItsyBitsy 5V/16MHz Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Adafruit Metro Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Adafruit Pro Trinket 3V/12MHz (FTDI) Atmel AVR On-board ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 3V/12MHz (USB) Atmel AVR On-board ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (FTDI) Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (USB) Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Adafruit Trinket 3V/8MHz Atmel AVR On-board ATTINY85 8MHz 8KB 512B
Adafruit Trinket 5V/16MHz Atmel AVR On-board ATTINY85 16MHz 8KB 512B
Alorium Hinj Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Alorium Sno Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Alorium XLR8 Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Anarduino MiniWireless Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Arduboy Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduboy DevKit Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino BT ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino BT ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Arduino Duemilanove or Diecimila ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Duemilanove or Diecimila ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Esplora Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Ethernet Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Arduino Fio Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
Arduino Industrial 101 Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo ETH Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino LilyPad ATmega168 Atmel AVR On-board ATMEGA168 8MHz 14KB 1KB
Arduino LilyPad ATmega328 Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
Arduino LilyPad USB Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Arduino Mega ADK Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Arduino Mega or Mega 2560 ATmega1280 Atmel AVR On-board ATMEGA1280 16MHz 124KB 8KB
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Arduino Micro Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Mini ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Mini ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Arduino NG or older ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino NG or older ATmega8 Atmel AVR On-board ATMEGA8 16MHz 7KB 1KB
Arduino Nano ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Nano ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Nano ATmega328 (New Bootloader) Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) Atmel AVR On-board ATMEGA168 8MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Robot Control Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Robot Motor Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Uno Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Arduino Yun Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Yun Mini Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
BQ ZUM BT-328 Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
BitWizard Raspduino Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Controllino Maxi Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Maxi Automation Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Mega Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Mini Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Digispark USB Atmel AVR On-board ATTINY85 16MHz 5.87KB 512B
Engduino 3 Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
EnviroDIY Mayfly Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
FYSETC F6 V1.3 Atmel AVR On-board ATMEGA2560 16MHz 252KB 8KB
Generic ATtiny13 Atmel AVR On-board ATTINY13 1MHz 1KB 64B
Generic ATtiny13A Atmel AVR On-board ATTINY13A 1MHz 1KB 64B
Generic ATtiny2313 Atmel AVR On-board ATTINY2313 8MHz 2KB 128B
Generic ATtiny24 Atmel AVR On-board ATTINY24 8MHz 2KB 128B
Generic ATtiny25 Atmel AVR On-board ATTINY25 8MHz 2KB 128B
Generic ATtiny4313 Atmel AVR On-board ATTINY4313 8MHz 4KB 256B
Generic ATtiny44 Atmel AVR On-board ATTINY44 8MHz 4KB 256B
Generic ATtiny45 Atmel AVR On-board ATTINY45 8MHz 4KB 256B
Generic ATtiny84 Atmel AVR On-board ATTINY84 8MHz 8KB 512B
Generic ATtiny85 Atmel AVR On-board ATTINY85 8MHz 8KB 512B
LightBlue Bean Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
LightBlue Bean+ Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
LightUp Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Linino One Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
LinkIt Smart 7688 Duo Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
LoRa32u4II (868-915MHz) Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
LowPowerLab MightyHat Atmel AVR On-board ATMEGA328P 16MHz 31KB 2KB
LowPowerLab Moteino Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
LowPowerLab Moteino (8Mhz) Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
LowPowerLab MoteinoMEGA Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
Microduino Core (Atmega168PA@16M,5V) Atmel AVR On-board ATMEGA168P 16MHz 15.50KB 1KB
Microduino Core (Atmega168PA@8M,3.3V) Atmel AVR On-board ATMEGA168P 8MHz 15.50KB 1KB
Microduino Core (Atmega328P@16M,5V) Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Microduino Core (Atmega328P@8M,3.3V) Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
Microduino Core USB (ATmega32U4@16M,5V) Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Microduino Core+ (ATmega1284P@16M,5V) Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
Microduino Core+ (ATmega1284P@8M,3.3V) Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
Microduino Core+ (Atmega644PA@16M,5V) Atmel AVR On-board ATMEGA644P 16MHz 63KB 4KB
Microduino Core+ (Atmega644PA@8M,3.3V) Atmel AVR On-board ATMEGA644P 8MHz 63KB 4KB
OpenEnergyMonitor emonPi Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Original Prusa i3 MK3 Multi Material 2.0 Upgrade Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
PanStamp AVR Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
Pololu A-Star 32U4 Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Prusa RAMBo Atmel AVR On-board ATMEGA2560 16MHz 252KB 8KB
Quirkbot Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
RedBearLab Blend Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend Micro 3.3V/16MHz (overclock) Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend Micro 3.3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
RepRap RAMBo Atmel AVR On-board ATMEGA2560 16MHz 252KB 8KB
SODAQ GaLoRa Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ Mbili Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ Moja Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
SODAQ Ndogo Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ Tatu Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
Sanguino ATmega1284p (16MHz) Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
Sanguino ATmega1284p (8MHz) Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
Sanguino ATmega644 or ATmega644A (16 MHz) Atmel AVR On-board ATMEGA644 16MHz 63KB 4KB
Sanguino ATmega644 or ATmega644A (8 MHz) Atmel AVR On-board ATMEGA644 8MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (16 MHz) Atmel AVR On-board ATMEGA644P 16MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (8 MHz) Atmel AVR On-board ATMEGA644P 8MHz 63KB 4KB
Seeeduino Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
SparkFun ATmega128RFA1 Dev Board Atmel AVR On-board ATMEGA128RFA1 16MHz 16KB 124KB
SparkFun Digital Sandbox Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
SparkFun Fio V3 3.3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Makey Makey Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Mega Pro 3.3V/8MHz Atmel AVR On-board ATMEGA2560 8MHz 252KB 8KB
SparkFun Mega Pro 5V/16MHz Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
SparkFun Mega Pro Mini 3.3V Atmel AVR On-board ATMEGA2560 8MHz 252KB 8KB
SparkFun MicroView Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
SparkFun Pro Micro 3.3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Pro Micro 5V/16MHz Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Qduino Mini Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun RedBoard Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
SparkFun Serial 7-Segment Display Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
SpellFoundry Sleepy Pi 2 Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
Talk2 Whisper Node Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
The Things Uno Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
TinyCircuits TinyDuino Processor Board Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
TinyCircuits TinyLily Mini Processor Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
USBasp stick Atmel AVR On-board ATMEGA8 12MHz 8KB 1KB
Wicked Device WildFire V2 Atmel AVR On-board ATMEGA1284P 16MHz 120.00KB 16KB
Wicked Device WildFire V3 Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
ftDuino Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
nicai-systems BOB3 coding bot Atmel AVR On-board ATMEGA88 8MHz 8KB 1KB
nicai-systems NIBO 2 robot Atmel AVR On-board ATMEGA128 16MHz 128KB 4KB
nicai-systems NIBO burger robot Atmel AVR On-board ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBO burger robot with Tuning Kit Atmel AVR On-board ATMEGA1284P 20MHz 128KB 16KB
nicai-systems NIBObee robot Atmel AVR On-board ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBObee robot with Tuning Kit Atmel AVR On-board ATMEGA1284P 20MHz 128KB 16KB
ubIQio Ardhat Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

High-speed 3-IN-1 fast USB ARM/ESP32 JTAG, USB-to-RS232 virtual port and power supply 5VDC device. Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = sipeed-rv-debugger


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = sipeed-rv-debugger
upload_protocol = sipeed-rv-debugger


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

Sipeed RV Debugger Connector Board JTAG Pin Description
1 GND Digital ground
2 TDI Test Data In pin
6 TMS Test Mode State pin
10 TCK JTAG Return Test Clock
8 TDO Test Data Out pin
4 RST Connect this pin to the (active low) reset input of the target CPU

Name Description
GigaDevice GD32V The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.

Name Description
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.
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
GD32VF103V-EVAL GigaDevice GD32V External GD32VF103VBT6 108MHz 128KB 32KB
Sipeed Longan Nano GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V External GD32VF103C8T6 108MHz 64KB 20KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB
Wio Lite RISC-V GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB

ST-LINK

The ST-LINK is an in-circuit debugger and programmer for the STM8 and STM32 microcontroller families. The single wire interface module (SWIM) and JTAG/serial wire debugging (SWD) interfaces are used to communicate with any STM8 or STM32 microcontroller located on an application board. Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
  • JTAG Interface
  • Serial Wire Mode Interface (SWD)

  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = stlink


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = stlink
upload_protocol = stlink


More options:

  • Debugging options
  • Upload options

Please install official ST-LINK USB driver.
Not required.
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

[image]

JTAG Interface

ST-Link JTAG 20-Pin Connector Board JTAG Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
4 GND Digital ground
5 TDI Test Data In pin
7 TMS Test Mode State pin
9 TCK JTAG Return Test Clock
13 TDO Test Data Out pin
15 RESET Connect this pin to the (active low) reset input of the target CPU

Serial Wire Mode Interface (SWD)

ST-Link SWD 20-Pin Connector Board SWD Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
4 GND Digital ground
7 SWDIO Data I/O
9 SWCLK Clock
15 RESET Connect this pin to the (active low) reset input of the target CPU

Name Description
Aceinna IMU Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.
Atmel SAM Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Nordic nRF51 The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.
Nordic nRF52 The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.
ST STM32 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.
ST STM8 The STM8 is an 8-bit microcontroller family by STMicroelectronics an extended variant of the ST7 microcontroller architecture. STM8 microcontrollers are particularly low cost for a full-featured 8-bit microcontroller.

Name Description
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.
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.
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.
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.
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.
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.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
1Bitsy ST STM32 External STM32F415RGT 168MHz 1MB 128KB
32F412GDISCOVERY ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
32F723EDISCOVERY ST STM32 On-board STM32F723IEK6 216MHz 512KB 192KB
3D Printer Controller ST STM32 External STM32F407VET6 168MHz 512KB 192KB
3D Printer control board ST STM32 External STM32F446RET6 180MHz 512KB 128KB
3D printer controller ST STM32 On-board STM32F765VIT6 216MHz 2MB 512KB
3DP001V1 Evaluation board for 3D printer ST STM32 On-board STM32F401VGT6 84MHz 512KB 96KB
96Boards Argonkey (STEVAL-MKI187V1) ST STM32 External STM32F412CG 100MHz 1MB 256KB
96Boards B96B-F446VE ST STM32 On-board STM32F446VET6 168MHz 512KB 128KB
96Boards Neonkey ST STM32 External STM32F411CE 100MHz 512KB 128KB
96Boards Nitrogen Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Aceinna Low Cost RTK Aceinna IMU On-board STM32F469NIH6 180MHz 1MB 384KB
Aceinna OpenIMU 300 Aceinna IMU External STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 300ZA Aceinna IMU External STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 330 Aceinna IMU External STM32L431CB 80MHz 128KB 64KB
Aceinna OpenIMU 330ZA Aceinna IMU External STM32F469IG 180MHz 1MB 384KB
Aceinna OpenRTK330L Aceinna IMU External STM32F469IG 180MHz 1MB 384KB
Adafruit Bluefruit nRF52832 Feather Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Adafruit Feather Bluefruit Sense Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Adafruit Feather STM32F405 ST STM32 External STM32F405RGT6 168MHz 1MB 128KB
Adafruit Feather nRF52840 Express Nordic nRF52 External NRF52840 64MHz 796KB 243KB
AfroFlight Rev5 (8MHz) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
Arduino Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Armstrap Eagle 1024 ST STM32 On-board STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 ST STM32 On-board STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB
BL652 Development Kit Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
BL654 Development Kit Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Black STM32F407VE ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
BlackPill F303CC ST STM32 External STM32F303CCT6 72MHz 256KB 40KB
BlackPill F401CC ST STM32 External STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini ST STM32 External STM32F407VET6 168MHz 512KB 128KB
BluePill F103C6 ST STM32 External STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
Bluey nRF52832 IoT Nordic nRF52 External NRF52832 64MHz 512KB 64KB
BluzDK Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Circuit Playground Bluefruit Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Core board F401RCT6 ST STM32 External STM32F401RCT6 84MHz 256KB 64KB
Delta DFBM-NQ620 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Demo F030F4 ST STM32 External STM32F030F4P6 48MHz 16KB 4KB
Digistump DigiX Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
ElectronutLabs Blip Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
ElectronutLabs Papyr Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Espotel LoRa Module ST STM32 External STM32F411RET6 100MHz 512KB 128KB
F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB
FK407M1 ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Holyiot YJ-16019 Nordic nRF52 External NRF52832 64MHz 512KB 64KB
ItsyBitsy nRF52840 Express Nordic nRF52 On-board NRF52840 64MHz 796KB 243KB
L476DMW1K ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
M200 V2 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
M300 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
MTS Dragonfly ST STM32 External STM32F411RET6 100MHz 512KB 128KB
Makerdiary nRF52832-MDK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Makerdiary nRF52840-MDK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Malyan M200 V1 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB
Maple ST STM32 External STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) ST STM32 External STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original ST STM32 External STM32F103CBT6 72MHz 108KB 17KB
Mbed Connect Cloud ST STM32 On-board STM32F439ZIY6 168MHz 2MB 256KB
Metro nRF52840 Express Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Microduino Core STM32 to Flash ST STM32 External STM32F103CBT6 72MHz 105.47KB 16.60KB
Microsoft Azure IoT Development Kit (MXChip AZ3166) ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
MultiTech mDot ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot F411 ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech xDot ST STM32 External STM32L151CCU6 32MHz 256KB 32KB
N2+ ST STM32 External STM32F405RGT6 168MHz 1MB 192KB
NAMote72 ST STM32 External STM32L152RC 32MHz 256KB 32KB
Nordic Beacon Kit (PCA20006) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic Thingy:52 (nRF52-PCA20020) Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Nordic nRF52840-DK (Adafruit BSP) Nordic nRF52 On-board NRF52840 64MHz 796KB 243KB
OLIMEXINO-STM32 ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
OSHChip Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Olimex STM32-P405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB
P-Nucleo WB55RG ST STM32 On-board STM32WB55RG 64MHz 512KB 192.00KB
Particle Xenon Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Piconomix PX-HER0 ST STM32 External STM32L072RB 32MHz 128KB 20KB
PrntrBoard V2 ST STM32 External STM32F407RE 168MHz 512KB 192KB
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 16KB
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 32KB
RHF76 052 ST STM32 External STM32L051C8T6 32MHz 64KB 8KB
RedBearLab BLE Nano 1.5 Nordic nRF51 On-board NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab Blend 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab nRF51822 Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
RushUp Cloud-JAM ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
RushUp Cloud-JAM L4 ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
SDT52832B Nordic nRF52 External NRF52832 64MHz 512KB 64KB
ST 32F3348DISCOVERY ST STM32 On-board STM32F334C8T6 72MHz 64KB 12KB
ST 32F401CDISCOVERY ST STM32 On-board STM32F401VCT6 84MHz 256KB 64KB
ST 32F411EDISCOVERY ST STM32 On-board STM32F411VET6 100MHz 512KB 128KB
ST 32F413HDISCOVERY ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 On-board STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY ST STM32 On-board STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY ST STM32 On-board STM32F769NIH6 216MHz 1MB 512KB
ST 32L0538DISCOVERY ST STM32 On-board STM32L053C8T6 32MHz 64KB 8KB
ST 32L100DISCOVERY ST STM32 On-board STM32L100RCT6 32MHz 256KB 16KB
ST 32L476GDISCOVERY ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY ST STM32 On-board STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 On-board STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 On-board STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F031K6 ST STM32 On-board STM32F031K6T6 48MHz 32KB 4KB
ST Nucleo F042K6 ST STM32 On-board STM32F042K6T6 48MHz 32KB 6KB
ST Nucleo F070RB ST STM32 On-board STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F091RC ST STM32 On-board STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 On-board STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 On-board STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 On-board STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 ST STM32 On-board STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE ST STM32 On-board STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F303ZE ST STM32 On-board STM32F303ZET6 72MHz 512KB 64KB
ST Nucleo F334R8 ST STM32 On-board STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F410RB ST STM32 On-board STM32F410RBT6 100MHz 128KB 32KB
ST Nucleo F411RE ST STM32 On-board STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F439ZI ST STM32 On-board STM32F439ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 On-board STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F446ZE ST STM32 On-board STM32F446ZET6 180MHz 512KB 128KB
ST Nucleo F722ZE ST STM32 On-board STM32F722ZET6 216MHz 512KB 256KB
ST Nucleo F746ZG ST STM32 On-board STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG ST STM32 On-board STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI ST STM32 On-board STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI ST STM32 On-board STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L011K4 ST STM32 On-board STM32L011K4T6 32MHz 16KB 2KB
ST Nucleo L031K6 ST STM32 On-board STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 ST STM32 On-board STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 On-board STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE ST STM32 On-board STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L412KB ST STM32 On-board STM32L412KBU6 80MHz 128KB 40KB
ST Nucleo L432KC ST STM32 On-board STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L433RC-P ST STM32 On-board STM32L433RC 80MHz 256KB 64KB
ST Nucleo L452RE ST STM32 On-board STM32L452RET6 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L486RG ST STM32 On-board STM32L486RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 On-board STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P ST STM32 On-board STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI ST STM32 On-board STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST STM32F0DISCOVERY ST STM32 On-board STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY ST STM32 On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32L073Z-EVAL ST STM32 On-board STM32L073VZT6 32MHz 192KB 20KB
ST STM32LDISCOVERY ST STM32 On-board STM32L152RBT6 32MHz 128KB 16KB
ST STM32VLDISCOVERY ST STM32 On-board STM32F100RBT6 24MHz 128KB 8KB
ST STM8S-DISCOVERY ST STM8 On-board STM8S105C6T6 16MHz 32KB 2KB
ST Sensor Node ST STM32 On-board STM32L476JG 80MHz 1MB 128KB
STEVAL-FCU001V1 Flight controller unit evaluation board ST STM32 External STM32F401CCU6 84MHz 256KB 64KB
STM32-E407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM3210C-EVAL ST STM32 External STM32F107VCT6 72MHz 256KB 64KB
STM32373C-EVAL ST STM32 External STM32F373VCT6 72MHz 256KB 32KB
STM32F072-EVAL ST STM32 External STM32F072VBT6 48MHz 128KB 16KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 External STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 External STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 External STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 External STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 External STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 External STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 External STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 External STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 External STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 External STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 External STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 External STM32F103ZET6 72MHz 512KB 64KB
STM32F303CB (32k RAM. 128k Flash) ST STM32 External STM32F303CBT6 72MHz 128KB 32KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 External STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 External STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 External STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) ST STM32 External STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) ST STM32 External STM32F407VGT6 168MHz 1MB 192KB
STM32F4Stamp F405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB
STM32F7508-DK ST STM32 On-board STM32F750N8H6 216MHz 64KB 340KB
STM32H747I-DISCO ST STM32 On-board STM32H747XIH6 400MHz 2MB 512KB
SainSmart Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
SainSmart Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Seeed Arch BLE Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB
Seeed Arch Link Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Arch Max ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB
Seeed Tiny BLE Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Wio 3G ST STM32 On-board STM32F439VI 180MHz 2MB 256KB
SensorTile.box ST STM32 External STM32L4R9ZI 120MHz 2MB 640KB
Sino:Bit Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Sparky V1 F303 ST STM32 External STM32F303CCT6 72MHz 256KB 40KB
Taida Century nRF52 mini board Nordic nRF52 External NRF52832 64MHz 512KB 64KB
ThunderPack ST STM32 External STM32L072KZ 32MHz 192KB 20KB
Tiny STM103T ST STM32 External STM32F103TBU6 72MHz 128KB 20KB
VAkE v1.0 ST STM32 External STM32F446RET6 180MHz 512KB 128KB
VNG VBLUno52 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Waveshare BLE400 Nordic nRF51 External NRF51822 32MHz 256KB 32KB
Wraith V1 ESC ST STM32 External STM32F051K6 48MHz 32KB 7.75KB
hackaBLE Nordic nRF52 External NRF52832 64MHz 512KB 64KB
ng-beacon Nordic nRF51 External NRF51822 16MHz 256KB 32KB
sakura.io Evaluation Board ST STM32 On-board STM32F411RET6 100MHz 1MB 128KB
u-blox C030-N211 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox C030-R410M IoT ST STM32 On-board STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox EVK-NINA-B1 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
u-blox EVK-ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB
u-blox ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB
y5 nRF51822 mbug Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

TI-ICDI

Tiva™ C Series evaluation and reference design kits provide an integrated In-Circuit Debug Interface (ICDI) which allows programming and debugging of the onboard C Series microcontroller. Official reference can be found here.

  • Configuration
  • Drivers
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = ti-icdi


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = ti-icdi
upload_protocol = ti-icdi


More options:

  • Debugging options
  • Upload options

Please "USB Driver Installation" guide for your board.
Not required.
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Name Description
TI TIVA Texas Instruments TM4C12x MCUs offer the industrys most popular ARM Cortex-M4 core with scalable memory and package options, unparalleled connectivity peripherals, advanced application functions, industry-leading analog integration, and extensive software solutions.

Name Description
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.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
TI LaunchPad (Stellaris) w/ lm4f120 (80MHz) TI TIVA On-board LPLM4F120H5QR 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c123 (80MHz) TI TIVA On-board LPTM4C1230C3PM 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c129 (120MHz) TI TIVA On-board LPTM4C1294NCPDT 120MHz 1MB 256KB

The TIAO USB Multi Protocol Adapter (TUMPA) is a multi-functional USB communication adapter for hobbyists or engineers. The adapter is based on FDTI's flagship communication chip FT2232H, a USB 2.0 Hi-Speed (480Mb/s) to UART/FIFO IC. It has two multi-protocol synchronous serial engines (MPSSEs) which allow for communication using JTAG, I2C and SPI on two channels simultaneously. Official reference can be found here.

  • Configuration
  • Drivers
  • Wiring Connections
  • JTAG Interface
  • Serial Wire Mode Interface (SWD)

  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = tumpa


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = tumpa
upload_protocol = tumpa


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

[image]

JTAG Interface

TUMPA JTAG 20-Pin Connector Board JTAG Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
4 GND Digital ground
5 TDI Test Data In pin
7 TMS Test Mode State pin
9 TCK JTAG Return Test Clock
13 TDO Test Data Out pin
15 RESET Connect this pin to the (active low) reset input of the target CPU (EN for ESP32)

Serial Wire Mode Interface (SWD)

TUMPA SWD 20-Pin Connector Board SWD Pin Description
1 VCC Positive Supply Voltage — Power supply for JTAG interface drivers
4 GND Digital ground
7 SWDIO Data I/O
9 SWCLK Clock
15 RESET Connect this pin to the (active low) reset input of the target CPU

Name Description
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.
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.

Name Description
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

The UM232H is a USB-to-serial/FIFO development module in the FTDI product range which utilizes the FT232H USB Hi-Speed (480Mb/s) single-port bridge chip to handle the USB signaling and protocols. Official reference can be found here

  • Configuration
  • Drivers
  • Wiring Connections
  • Platforms
  • Frameworks
  • Boards

You can configure debugging tool using debug_tool option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
board = ...
debug_tool = um232h


If you would like to use this tool for firmware uploading, please change upload protocol:

[env:myenv]
platform = ...
board = ...
debug_tool = um232h
upload_protocol = um232h


More options:

  • Debugging options
  • Upload options

  • Step-by-step guide: Drivers, Zadig, Wiring
  • Video tutorial

macOS contains default FTDIUSBSerialDriver driver which conflicts with debug tools which are based on this chip. FTDI Chip company recommends removing this default driver from a system. Everything should work after system rebooting. See detailed instruction in official application note (Page 16, Section 4: Uninstalling FTDI Drivers on OS X) AN134: FTDI Drivers Installation guide for MAC OS X
Please install "udev" rules 99-platformio-udev.rules. If you already installed them before, please check that your rules are up-to-date or repeat steps.

Wiring Connections

Please read 4. UM232H Pin Out and Signal Descriptions section for details.

UM232H Pin Board JTAG Pin Description
GND GND Digital ground
AD0 TCK JTAG Return Test Clock
AD1 TDI Test Data In
AD2 TDO Test Data Out
AD3 TMS Test Mode State

You will also need to connect VIO to V3V and USB to 5V0 of UM232H to power the FTDI chip and board. See UM232H Datasheet

Name Description
GigaDevice GD32V The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.

Name Description
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.
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
GD32VF103V-EVAL GigaDevice GD32V External GD32VF103VBT6 108MHz 128KB 32KB
Sipeed Longan Nano GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V External GD32VF103C8T6 108MHz 64KB 20KB
Wio Lite RISC-V GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB

debug_tool = custom

PIO Unified Debugger can be configured from "platformio.ini" (Project Configuration File):

  • J-Link and ST Nucleo
  • J-Link as debugger and uploader
  • ST-Util and ST-Link
  • OpenOCD and ST-Link
  • pyOCD and CMSIS-DAP

J-Link and ST Nucleo

Segger J-Link probe and ST Nucleo F446RE board in pair with J-Link GDB Server:

  • Install J-Link GDB Server
  • Convert ST-LINK On-Board Into a J-Link

NOTE:

You can use configuration below in pair with other boards, not only with ST Nucleo F446RE. In this case, please replace STM32F446RE with your own device name in debug_server option.

See full list with J-Link Supported Devices.



[env:debug_jlink]
platform = ststm32
framework = mbed
board = nucleo_f446re
debug_tool = custom
debug_port = :2331
debug_server =
  /full/path/to/JLinkGDBServerCL
  -singlerun
  -if
  SWD
  -select
  USB
  -port
  2331
  -device
  STM32F446RE
debug_init_cmds =
  define pio_reset_halt_target
      monitor reset
      monitor halt
  end
  define pio_reset_run_target
      monitor clrbp
      monitor reset
      monitor go
  end
  target extended-remote $DEBUG_PORT
  monitor clrbp
  monitor speed auto
  pio_reset_halt_target
  $LOAD_CMDS
  $INIT_BREAK


J-Link as debugger and uploader

Segger J-Link probe as debugger and uploader for a custom board. If you plan to use with other board, please change device MK20DX256xxx7 to a valid identifier. See supported J-Link devices at J-LINK.

•
Install J-Link GDB Server

[env:jlink_debug_and_upload]
platform = teensy
framework = arduino
board = teensy31
extra_scripts = extra_script.py
upload_protocol = custom
debug_tool = jlink
debug_server =
  /full/path/to/JLinkGDBServerCL
  -singlerun
  -if
  SWD
  -select
  USB
  -port
  2331
  -device
  MK20DX256xxx7


extra_script.py

Place this file on the same level as "platformio.ini" (Project Configuration File).

from os import makedirs
from os.path import isdir, join
Import('env')
def _jlink_cmd_script(env, source):
    build_dir = env.subst("$BUILD_DIR")
    if not isdir(build_dir):
        makedirs(build_dir)
    script_path = join(build_dir, "upload.jlink")
    commands = ["h", "loadbin %s,0x0" % source, "r", "q"]
    with open(script_path, "w") as fp:
        fp.write("\n".join(commands))
    return script_path
env.Replace(
    __jlink_cmd_script=_jlink_cmd_script,
    UPLOADER="/full/path/to/JLink",
    UPLOADERFLAGS=[
        "-device", "MK20DX256xxx7",
        "-speed", "4000",
        "-if", "swd",
        "-autoconnect", "1"
    ],
    UPLOADCMD='"$UPLOADER" $UPLOADERFLAGS -CommanderScript ${__jlink_cmd_script(__env__, SOURCE)}'
)


ST-Util and ST-Link

On-board ST-Link V2/V2-1 in pair with ST-Util GDB Server:

[env:debug]
platform = ststm32
framework = mbed
board = ...
debug_tool = custom
debug_port = :4242
debug_server = $PLATFORMIO_CORE_DIR/packages/tool-stlink/bin/st-util


On-board ST-Link V2/V2-1 in pair with OpenOCD GDB Server:

[env:debug]
platform = ststm32
framework = mbed
board = ...
debug_tool = custom
debug_server =
  $PLATFORMIO_CORE_DIR/packages/tool-openocd/bin/openocd
  -f
  $PLATFORMIO_CORE_DIR/packages/tool-openocd/scripts/board/st_nucleo_f4.cfg


Using pyOCD for CMSIS-DAP based boards

Firstly, please install pyOCD and check that pyocd-gdbserver --version command works.

[env:debug]
platform = ...
board = ...
framework = mbed
debug_tool = custom
debug_server = pyocd-gdbserver


CLI Guide

Name Description
Aceinna IMU Open-source, embedded development platform for Aceinna IMU hardware. Run custom algorithms and navigation code on Aceinna IMU/INS hardware.
Atmel AVR Atmel AVR 8-bit MCUs deliver a unique combination of performance, power efficiency and design flexibility. Optimized to speed time to market-and easily adapt to new ones-they are based on the industry's most code-efficient architecture for C and assembly programming
Atmel SAM Atmel | SMART offers Flash- based ARM products based on the ARM Cortex-M0+, Cortex-M3 and Cortex-M4 architectures, ranging from 8KB to 2MB of Flash including a rich peripheral and feature mix.
Espressif 32 Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications and Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.
Freescale Kinetis Freescale Kinetis Microcontrollers is family of multiple hardware- and software-compatible ARM Cortex-M0+, Cortex-M4 and Cortex-M7-based MCU series. Kinetis MCUs offer exceptional low-power performance, scalability and feature integration.
GigaDevice GD32V The GigaDevice GD32V device is a 32-bit general-purpose microcontroller based on the RISC-V core with an impressive balance of processing power, reduced power consumption and peripheral set.
Infineon XMC Infineon has designed the XMC microcontrollers for real-time critical applications with an industry-standard core. The XMC microcontrollers can be integrated with the Arduino platform
Kendryte K210 Kendryte K210 is an AI capable RISCV64 dual core SoC.
Maxim 32 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.
Nordic nRF51 The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.
Nordic nRF52 The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.
Nuclei Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.
NXP i.MX RT The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.
NXP LPC The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.
RISC-V 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.
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.
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.
Silicon Labs EFM32 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.
ST STM32 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.
ST STM8 The STM8 is an 8-bit microcontroller family by STMicroelectronics an extended variant of the ST7 microcontroller architecture. STM8 microcontrollers are particularly low cost for a full-featured 8-bit microcontroller.
Teensy Teensy is a complete USB-based microcontroller development system, in a very small footprint, capable of implementing many types of projects. All programming is done via the USB port. No special programmer is needed, only a standard USB cable and a PC or Macintosh with a USB port.
TI MSP430 MSP430 microcontrollers (MCUs) from Texas Instruments (TI) are 16-bit, RISC-based, mixed-signal processors designed for ultra-low power. These MCUs offer the lowest power consumption and the perfect mix of integrated peripherals for thousands of applications.
TI TIVA Texas Instruments TM4C12x MCUs offer the industrys most popular ARM Cortex-M4 core with scalable memory and package options, unparalleled connectivity peripherals, advanced application functions, industry-leading analog integration, and extensive software solutions.
WIZNet W7500 The IOP (Internet Offload Processor) W7500 is the one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform especially requiring Internet of things

Name Description
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.
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.
ESP-IDF Espressif IoT Development Framework. Official development framework for ESP32.
Freedom E SDK Open Source Software for Developing on the SiFive Freedom E Platform
GigaDevice GD32V SDK GigaDevice GD32VF103 Firmware Library (SDK)
Kendryte Standalone SDK Kendryte Standalone SDK without OS support
Kendryte FreeRTOS SDK Kendryte SDK with FreeRTOS support
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.
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.
Nuclei SDK Open Source Software Development Kit for the Nuclei N/NX processors
PULP OS PULP is a silicon-proven Parallel Ultra Low Power platform targeting high energy efficiencies. The platform is organized in clusters of RISC-V cores that share a tightly-coupled data memory.
Shakti SDK A software development kit for developing applications on Shakti class of processors
Simba Simba is an RTOS and build framework. It aims to make embedded programming easy and portable.
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.
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.
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.

NOTE:

For more detailed board information please scroll tables below by horizontal.


Name Platform Debug MCU Frequency Flash RAM
1Bitsy ST STM32 External STM32F415RGT 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
96Boards Argonkey (STEVAL-MKI187V1) ST STM32 External STM32F412CG 100MHz 1MB 256KB
96Boards B96B-F446VE ST STM32 On-board STM32F446VET6 168MHz 512KB 128KB
96Boards Neonkey ST STM32 External STM32F411CE 100MHz 512KB 128KB
96Boards Nitrogen Nordic nRF52 External NRF52832 64MHz 512KB 64KB

AI Thinker

Name Platform Debug MCU Frequency Flash RAM
AI Thinker ESP32-CAM Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
AZ-Delivery ESP-32 Dev Kit C V4 Espressif 32 External ESP32 240MHz 16MB 520KB

Name Platform Debug MCU Frequency Flash RAM
Aceinna Low Cost RTK Aceinna IMU On-board STM32F469NIH6 180MHz 1MB 384KB
Aceinna OpenIMU 300 Aceinna IMU External STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 300ZA Aceinna IMU External STM32F405RG 120MHz 1MB 128KB
Aceinna OpenIMU 330 Aceinna IMU External STM32L431CB 80MHz 128KB 64KB
Aceinna OpenIMU 330ZA Aceinna IMU External STM32F469IG 180MHz 1MB 384KB
Aceinna OpenRTK330L Aceinna IMU External STM32F469IG 180MHz 1MB 384KB

Name Platform Debug MCU Frequency Flash RAM
Adafruit Bluefruit Micro Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Bluefruit nRF52832 Feather Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Adafruit Circuit Playground Classic Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Circuit Playground Express Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Crickit M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit ESP32 Feather Espressif 32 External ESP32 240MHz 4MB 320KB
Adafruit Feather 328P Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
Adafruit Feather 32u4 Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Feather Bluefruit Sense Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Adafruit Feather M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M0 Express Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Feather M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Feather STM32F405 ST STM32 External STM32F405RGT6 168MHz 1MB 128KB
Adafruit Feather nRF52840 Express Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Adafruit Flora Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit Gemma Atmel AVR On-board ATTINY85 8MHz 8KB 512B
Adafruit Gemma M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit Grand Central M4 Atmel SAM External SAMD51P20A 120MHz 1MB 256KB
Adafruit Hallowing M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Hallowing M4 Atmel SAM External SAMD51J19A 120MHz 496KB 192KB
Adafruit ItsyBitsy 3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Adafruit ItsyBitsy 5V/16MHz Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Adafruit ItsyBitsy M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit ItsyBitsy M4 Atmel SAM External SAMD51G19A 120MHz 512KB 192KB
Adafruit MONSTER M4SK Atmel SAM External SAMD51G19A 120MHz 496KB 192KB
Adafruit Metro Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Adafruit Metro M0 Expresss Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Adafruit Metro M4 Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Metro M4 AirLift Lite Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Pro Trinket 3V/12MHz (FTDI) Atmel AVR On-board ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 3V/12MHz (USB) Atmel AVR On-board ATMEGA328P 12MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (FTDI) Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Adafruit Pro Trinket 5V/16MHz (USB) Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Adafruit PyGamer Advance M4 Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit PyGamer M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit PyPortal M4 Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit PyPortal M4 Titano Atmel SAM External SAMD51J20A 120MHz 1MB 256KB
Adafruit Trellis M4 Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Adafruit Trinket 3V/8MHz Atmel AVR On-board ATTINY85 8MHz 8KB 512B
Adafruit Trinket 5V/16MHz Atmel AVR On-board ATTINY85 16MHz 8KB 512B
Adafruit Trinket M0 Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit pIRkey Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
Adafruit pyBadge AirLift M4 Atmel SAM External SAMD51J20A 120MHz 1008KB 192KB
Adafruit pyBadge M4 Express Atmel SAM External SAMD51J19A 120MHz 512KB 192KB
Circuit Playground Bluefruit Nordic nRF52 External NRF52840 64MHz 796KB 243KB
ItsyBitsy nRF52840 Express Nordic nRF52 On-board NRF52840 64MHz 796KB 243KB
Metro nRF52840 Express Nordic nRF52 External NRF52840 64MHz 796KB 243KB

Name Platform Debug MCU Frequency Flash RAM
AfroFlight Rev5 (8MHz) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB

Name Platform Debug MCU Frequency Flash RAM
Wraith V1 ESC ST STM32 External STM32F051K6 48MHz 32KB 7.75KB

Name Platform Debug MCU Frequency Flash RAM
Node32s Espressif 32 External ESP32 240MHz 4MB 320KB

Alorium Technology

Name Platform Debug MCU Frequency Flash RAM
Alorium Hinj Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Alorium Sno Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Alorium XLR8 Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
Anarduino MiniWireless Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
Arduboy Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduboy DevKit Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
Arduino BT ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino BT ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Arduino Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
Arduino Duemilanove or Diecimila ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Duemilanove or Diecimila ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Esplora Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Ethernet Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Arduino Fio Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
Arduino Industrial 101 Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Leonardo ETH Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino LilyPad ATmega168 Atmel AVR On-board ATMEGA168 8MHz 14KB 1KB
Arduino LilyPad ATmega328 Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
Arduino LilyPad USB Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
Arduino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Native USB Port) Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino M0 Pro (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino MKR FOX 1200 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR GSM 1400 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR NB 1500 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1300 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WAN 1310 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR WiFi 1010 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKR1000 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino MKRZERO Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino Mega ADK Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Arduino Mega or Mega 2560 ATmega1280 Atmel AVR On-board ATMEGA1280 16MHz 124KB 8KB
Arduino Mega or Mega 2560 ATmega2560 (Mega 2560) Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Arduino Micro Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Mini ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Mini ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB
Arduino NG or older ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino NG or older ATmega8 Atmel AVR On-board ATMEGA8 16MHz 7KB 1KB
Arduino Nano 33 BLE Nordic nRF52 External NRF52840 64MHz 960KB 256KB
Arduino Nano ATmega168 Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Nano ATmega328 Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Nano ATmega328 (New Bootloader) Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega168 (3.3V, 8 MHz) Atmel AVR On-board ATMEGA168 8MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega168 (5V, 16 MHz) Atmel AVR On-board ATMEGA168 16MHz 14KB 1KB
Arduino Pro or Pro Mini ATmega328 (3.3V, 8 MHz) Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
Arduino Pro or Pro Mini ATmega328 (5V, 16 MHz) Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB
Arduino Robot Control Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Robot Motor Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Tian Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Arduino Uno Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Arduino Yun Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Yun Mini Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Arduino Zero (Programming/Debug Port) Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Arduino Zero (USB Native Port) Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
MKR Vidor 4000 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
NANO 33 IoT Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
3D Printer Controller ST STM32 External STM32F407VET6 168MHz 512KB 192KB

Name Platform Debug MCU Frequency Flash RAM
Armstrap Eagle 1024 ST STM32 On-board STM32F417VGT6 168MHz 1MB 192KB
Armstrap Eagle 2048 ST STM32 On-board STM32F427VIT6 168MHz 1.99MB 256KB
Armstrap Eagle 512 ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB

Name Platform Debug MCU Frequency Flash RAM
Atmel ATSAMR21-XPRO Atmel SAM On-board SAMR21G18A 48MHz 256KB 32KB
Atmel ATSAMW25-XPRO Atmel SAM On-board SAMD21G18A 48MHz 256KB 32KB
Atmel SAMC21-XPRO Atmel SAM On-board SAMC21J18A 48MHz 256KB 32KB
Atmel SAMD21-XPRO Atmel SAM On-board SAMD21J18A 48MHz 256KB 32KB
Atmel SAML21-XPRO-B Atmel SAM On-board SAML21J18B 48MHz 256KB 32KB
Generic ATtiny13 Atmel AVR On-board ATTINY13 1MHz 1KB 64B
Generic ATtiny13A Atmel AVR On-board ATTINY13A 1MHz 1KB 64B
Generic ATtiny2313 Atmel AVR On-board ATTINY2313 8MHz 2KB 128B
Generic ATtiny24 Atmel AVR On-board ATTINY24 8MHz 2KB 128B
Generic ATtiny25 Atmel AVR On-board ATTINY25 8MHz 2KB 128B
Generic ATtiny4313 Atmel AVR On-board ATTINY4313 8MHz 4KB 256B
Generic ATtiny44 Atmel AVR On-board ATTINY44 8MHz 4KB 256B
Generic ATtiny45 Atmel AVR On-board ATTINY45 8MHz 4KB 256B
Generic ATtiny84 Atmel AVR On-board ATTINY84 8MHz 8KB 512B
Generic ATtiny85 Atmel AVR On-board ATTINY85 8MHz 8KB 512B
USBasp stick Atmel AVR On-board ATMEGA8 12MHz 8KB 1KB

Avnet Silica

Name Platform Debug MCU Frequency Flash RAM
ST Sensor Node ST STM32 On-board STM32L476JG 80MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
BBC micro:bit Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

Name Platform Debug MCU Frequency Flash RAM
BQ ZUM BT-328 Atmel AVR On-board ATMEGA328P 16MHz 28KB 2KB

Name Platform Debug MCU Frequency Flash RAM
LoRa32u4II (868-915MHz) Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
BitWizard Raspduino Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB

Name Platform Debug MCU Frequency Flash RAM
BluzDK Nordic nRF51 External NRF51822 32MHz 256KB 32KB

CQ Publishing

Name Platform Debug MCU Frequency Flash RAM
CQ Publishing TG-LPC11U35-501 NXP LPC External LPC11U35 48MHz 64KB 10KB

Name Platform Debug MCU Frequency Flash RAM
Calliope mini Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

Name Platform Debug MCU Frequency Flash RAM
Controllino Maxi Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Maxi Automation Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Mega Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
Controllino Mini Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
FireBeetle-ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
DOIT ESP32 DEVKIT V1 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
D-duino-32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Delta DFBM-NQ620 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Delta DFCM-NNN40 Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Delta DFCM-NNN50 Nordic nRF51 On-board NRF51822 32MHz 256KB 16KB

Name Platform Debug MCU Frequency Flash RAM
Digispark USB Atmel AVR On-board ATTINY85 16MHz 5.87KB 512B
Digistump DigiX Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB

Name Platform Debug MCU Frequency Flash RAM
F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB

Dongsen Technology

Name Platform Debug MCU Frequency Flash RAM
Dongsen Tech Pocket 32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ESPectro32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
ESP32vn IoT Uno Espressif 32 External ESP32 240MHz 4MB 320KB

Electronut Labs

Name Platform Debug MCU Frequency Flash RAM
Bluey nRF52832 IoT Nordic nRF52 External NRF52832 64MHz 512KB 64KB
hackaBLE Nordic nRF52 External NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
ElectronutLabs Blip Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
ElectronutLabs Papyr Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB

Elektor Labs

Name Platform Debug MCU Frequency Flash RAM
CoCo-ri-Co! NXP LPC On-board LPC812 30MHz 16KB 4KB

Embedded Artists

Name Platform Debug MCU Frequency Flash RAM
EA LPC11U35 QuickStart Board NXP LPC External LPC11U35 48MHz 64KB 10KB
Embedded Artists LPC4088 Display Module NXP LPC On-board LPC4088 120MHz 512KB 96KB
Embedded Artists LPC4088 QuickStart Board NXP LPC On-board LPC4088 120MHz 512KB 96KB

Name Platform Debug MCU Frequency Flash RAM
Engduino 3 Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
EnviroDIY Mayfly Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB

Name Platform Debug MCU Frequency Flash RAM
Espotel LoRa Module ST STM32 External STM32F411RET6 100MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
Espressif ESP-WROVER-KIT Espressif 32 On-board ESP32 240MHz 4MB 320KB
Espressif ESP32 Dev Module Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
FYSETC F6 V1.3 Atmel AVR On-board ATMEGA2560 16MHz 252KB 8KB

Name Platform Debug MCU Frequency Flash RAM
Frog Board ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Ethernet IoT Starter Kit Freescale Kinetis On-board MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K20D50M Freescale Kinetis On-board MK20DX128VLH5 48MHz 128KB 16KB
Freescale Kinetis FRDM-K22F Freescale Kinetis On-board MK22FN512VLH12 120MHz 512KB 128KB
Freescale Kinetis FRDM-K64F Freescale Kinetis On-board MK64FN1M0VLL12 120MHz 1MB 256KB
Freescale Kinetis FRDM-K66F Freescale Kinetis On-board MK66FN2M0VMD18 180MHz 2MB 256KB
Freescale Kinetis FRDM-K82F Freescale Kinetis On-board MK82FN256VLL15 150MHz 256KB 256KB
Freescale Kinetis FRDM-KL05Z Freescale Kinetis On-board MKL05Z32VFM4 48MHz 32KB 4KB
Freescale Kinetis FRDM-KL25Z Freescale Kinetis On-board MKL25Z128VLK4 48MHz 128KB 16KB
Freescale Kinetis FRDM-KL27Z Freescale Kinetis On-board MKL27Z64VLH4 48MHz 64KB 16KB
Freescale Kinetis FRDM-KL43Z Freescale Kinetis On-board MKL43Z256VLH4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL46Z Freescale Kinetis On-board MKL46Z256VLL4 48MHz 256KB 32KB
Freescale Kinetis FRDM-KL82Z Freescale Kinetis External MKL82Z128VLK7 96MHz 128KB 96KB
Freescale Kinetis FRDM-KW24D512 Freescale Kinetis External MKW24D512 50MHz 512KB 64KB
Freescale Kinetis FRDM-KW41Z Freescale Kinetis On-board MKW41Z512VHT4 48MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
BlackPill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BlackPill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
BluePill F103C6 ST STM32 External STM32F103C6T6 72MHz 32KB 10KB
BluePill F103C8 ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
BluePill F103C8 (128k) ST STM32 External STM32F103C8T6 72MHz 128KB 20KB
Demo F030F4 ST STM32 External STM32F030F4P6 48MHz 16KB 4KB
FK407M1 ST STM32 External STM32F407VET6 168MHz 512KB 128KB
STM32F103C8 (20k RAM. 64k Flash) ST STM32 External STM32F103C8T6 72MHz 64KB 20KB
STM32F103CB (20k RAM. 128k Flash) ST STM32 External STM32F103CBT6 72MHz 128KB 20KB
STM32F103R8 (20k RAM. 64 Flash) ST STM32 External STM32F103R8T6 72MHz 64KB 20KB
STM32F103RB (20k RAM. 128k Flash) ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
STM32F103RC (48k RAM. 256k Flash) ST STM32 External STM32F103RCT6 72MHz 256KB 48KB
STM32F103RE (64k RAM. 512k Flash) ST STM32 External STM32F103RET6 72MHz 512KB 64KB
STM32F103T8 (20k RAM. 64k Flash) ST STM32 External STM32F103T8T6 72MHz 64KB 20KB
STM32F103TB (20k RAM. 128k Flash) ST STM32 External STM32F103TBT6 72MHz 128KB 20KB
STM32F103VB (20k RAM. 128k Flash) ST STM32 External STM32F103VBT6 72MHz 128KB 20KB
STM32F103VC (48k RAM. 256k Flash) ST STM32 External STM32F103VCT6 72MHz 256KB 48KB
STM32F103VD (64k RAM. 384k Flash) ST STM32 External STM32F103VDT6 72MHz 384KB 64KB
STM32F103VE (64k RAM. 512k Flash) ST STM32 External STM32F103VET6 72MHz 512KB 64KB
STM32F103ZC (48k RAM. 256k Flash) ST STM32 External STM32F103ZCT6 72MHz 256KB 48KB
STM32F103ZD (64k RAM. 384k Flash) ST STM32 External STM32F103ZDT6 72MHz 384KB 64KB
STM32F103ZE (64k RAM. 512k Flash) ST STM32 External STM32F103ZET6 72MHz 512KB 64KB
STM32F303CB (32k RAM. 128k Flash) ST STM32 External STM32F303CBT6 72MHz 128KB 32KB
STM32F401RB (64k RAM. 128k Flash) ST STM32 External STM32F401RB 84MHz 128KB 64KB
STM32F401RC (64k RAM. 256k Flash) ST STM32 External STM32F401RC 84MHz 256KB 64KB
STM32F401RE (96k RAM. 512k Flash) ST STM32 External STM32F401RE 84MHz 512KB 96KB
STM32F407VE (192k RAM. 512k Flash) ST STM32 External STM32F407VET6 168MHz 502.23KB 128KB
STM32F407VG (192k RAM. 1024k Flash) ST STM32 External STM32F407VGT6 168MHz 1MB 192KB
STM32F4Stamp F405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB

Name Platform Debug MCU Frequency Flash RAM
GD32VF103V Evaluation Kit Nuclei External GD32VF103VBT6 108MHz 128KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Tuino 096 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

GreenWaves Technologies

Name Platform Debug MCU Frequency Flash RAM
GAPuino GAP8 RISC-V GAP On-board GAP8 250MHz 64MB 8MB

Name Platform Debug MCU Frequency Flash RAM
Tiny STM103T ST STM32 External STM32F103TBU6 72MHz 128KB 20KB

Heltec Automation

Name Platform Debug MCU Frequency Flash RAM
Heltec WiFi LoRa 32 Espressif 32 External ESP32 240MHz 4MB 320KB
Heltec WiFi LoRa 32 (V2) Espressif 32 External ESP32 240MHz 8MB 320KB
Heltec Wireless Stick Espressif 32 External ESP32 240MHz 8MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Holyiot YJ-16019 Nordic nRF52 External NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
Hornbill ESP32 Dev Espressif 32 External ESP32 240MHz 4MB 320KB
Hornbill ESP32 Minima Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
XMC1100 Boot Kit Infineon XMC On-board XMC1100 32MHz 64KB 16KB
XMC1100 H-Bridge 2Go Infineon XMC On-board XMC1100 32MHz 64KB 16KB
XMC1100 XMC2Go Infineon XMC On-board XMC1100 32MHz 64KB 16KB
XMC1300 Boot Kit Infineon XMC On-board XMC1300 32MHz 64KB 16KB
XMC1300 Sense2GoL Infineon XMC On-board XMC1300 32MHz 32KB 16KB
XMC1400 Boot Kit Infineon XMC On-board XMC1400 48MHz 1.95MB 16KB
XMC4200 Distance2Go Infineon XMC On-board XMC4200 80MHz 256KB 40KB
XMC4700 Relax Kit Infineon XMC On-board XMC4700 144MHz 2.00MB 1.95MB

Name Platform Debug MCU Frequency Flash RAM
IoTaaP Magnolia Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
JKSoft Wallbot BLE Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB

Laird Connectivity

Name Platform Debug MCU Frequency Flash RAM
BL652 Development Kit Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
BL654 Development Kit Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
Maple ST STM32 External STM32F103RBT6 72MHz 108KB 17KB
Maple (RET6) ST STM32 External STM32F103RET6 72MHz 256KB 48KB
Maple Mini Bootloader 2.0 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB
Maple Mini Original ST STM32 External STM32F103CBT6 72MHz 108KB 17KB

Name Platform Debug MCU Frequency Flash RAM
LightUp Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
Linino One Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
LowPowerLab MightyHat Atmel AVR On-board ATMEGA328P 16MHz 31KB 2KB
LowPowerLab Moteino Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
LowPowerLab Moteino (8Mhz) Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
LowPowerLab MoteinoMEGA Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
Moteino M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

MH-ET Live

Name Platform Debug MCU Frequency Flash RAM
MH ET LIVE ESP32DevKIT Espressif 32 External ESP32 240MHz 4MB 320KB
MH ET LIVE ESP32MiniKit Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Microsoft Azure IoT Development Kit (MXChip AZ3166) ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
Makerdiary nRF52832-MDK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Makerdiary nRF52840-MDK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
M200 V2 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
M300 ST STM32 External STM32F070CBT6 48MHz 120KB 14.81KB
Malyan M200 V1 ST STM32 External STM32F103CBT6 72MHz 120KB 20KB

Name Platform Debug MCU Frequency Flash RAM
MAX32620FTHR Maxim 32 External MAX32620FTHR 96MHz 2MB 256KB
Maxim ARM mbed Enabled Development Platform for MAX32600 Maxim 32 On-board MAX32600 24MHz 256KB 32KB
Maxim Health Sensor Platform Maxim 32 External MAX32620 96MHz 2MB 256KB
Maxim Wireless Sensor Node Demonstrator Maxim 32 External MAX32610 24MHz 256KB 32KB

MediaTek Labs

Name Platform Debug MCU Frequency Flash RAM
LinkIt Smart 7688 Duo Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
ATmega128/A Atmel AVR On-board ATMEGA128 16MHz 127KB 4KB
ATmega1280 Atmel AVR On-board ATMEGA1280 16MHz 127KB 8KB
ATmega1281 Atmel AVR On-board ATMEGA1281 16MHz 127KB 8KB
ATmega1284 Atmel AVR On-board ATMEGA1284 16MHz 127KB 16KB
ATmega1284P Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
ATmega16 Atmel AVR On-board ATMEGA16 16MHz 15.50KB 1KB
ATmega164P/PA Atmel AVR On-board ATMEGA164P 16MHz 15.50KB 1KB
ATmega168/A Atmel AVR On-board ATMEGA168 16MHz 15.50KB 1KB
ATmega168P/PA Atmel AVR On-board ATMEGA168P 16MHz 15.50KB 1KB
ATmega2560 Atmel AVR On-board ATMEGA2560 16MHz 255KB 8KB
ATmega324A Atmel AVR On-board ATMEGA324A 16MHz 31.50KB 2KB
ATmega324P Atmel AVR On-board ATMEGA324P 16MHz 31.50KB 2KB
ATmega324PA Atmel AVR On-board ATMEGA324PA 16MHz 31.50KB 2KB
ATmega328 Atmel AVR On-board ATMEGA328 16MHz 31.50KB 2KB
ATmega328P/PA Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
ATmega48/A Atmel AVR On-board ATMEGA48 16MHz 4KB 512B
ATmega644P/PA Atmel AVR On-board ATMEGA644P 16MHz 63KB 4KB
ATmega8/A Atmel AVR On-board ATMEGA8 16MHz 7.50KB 1KB
ATmega88/A Atmel AVR On-board ATMEGA88 16MHz 7.50KB 1KB
ATmega88P/PA Atmel AVR On-board ATMEGA88P 16MHz 7.50KB 1KB
ATmega8P/PA Atmel AVR On-board ATMEGA48P 16MHz 4KB 512B

Name Platform Debug MCU Frequency Flash RAM
Microduino Core (Atmega168PA@16M,5V) Atmel AVR On-board ATMEGA168P 16MHz 15.50KB 1KB
Microduino Core (Atmega168PA@8M,3.3V) Atmel AVR On-board ATMEGA168P 8MHz 15.50KB 1KB
Microduino Core (Atmega328P@16M,5V) Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Microduino Core (Atmega328P@8M,3.3V) Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
Microduino Core STM32 to Flash ST STM32 External STM32F103CBT6 72MHz 105.47KB 16.60KB
Microduino Core USB (ATmega32U4@16M,5V) Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Microduino Core+ (ATmega1284P@16M,5V) Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
Microduino Core+ (ATmega1284P@8M,3.3V) Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
Microduino Core+ (Atmega644PA@16M,5V) Atmel AVR On-board ATMEGA644P 16MHz 63KB 4KB
Microduino Core+ (Atmega644PA@8M,3.3V) Atmel AVR On-board ATMEGA644P 8MHz 63KB 4KB

Name Platform Debug MCU Frequency Flash RAM
Bambino-210E NXP LPC On-board LPC4330 204MHz 8MB 264KB

Name Platform Debug MCU Frequency Flash RAM
MKR Sharky ST STM32 External STM32WB55CG 64MHz 512KB 192.00KB

Name Platform Debug MCU Frequency Flash RAM
Hexiwear Freescale Kinetis External MK64FN1M0VDC12 120MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
MTS Dragonfly ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech mDot F411 ST STM32 External STM32F411RET6 100MHz 512KB 128KB
MultiTech xDot ST STM32 External STM32L151CCU6 32MHz 256KB 32KB

NGX Technologies

Name Platform Debug MCU Frequency Flash RAM
NGX Technologies BlueBoard-LPC11U24 NXP LPC External LPC11U24 48MHz 32KB 8KB

Name Platform Debug MCU Frequency Flash RAM
ARM mbed LPC11U24 (+CAN) NXP LPC On-board LPC11U24 48MHz 32KB 8KB
LPCXpresso11U68 NXP LPC On-board LPC11U68 50MHz 256KB 36KB
LPCXpresso824-MAX NXP LPC On-board LPC824 30MHz 32KB 8KB
NXP LPC11C24 NXP LPC External LPC11C24 48MHz 32KB 8KB
NXP LPC11U34 NXP LPC External LPC11U34 48MHz 40KB 8KB
NXP LPC11U37 NXP LPC External LPC11U37 48MHz 128KB 10KB
NXP LPC800-MAX NXP LPC On-board LPC812 30MHz 16KB 4KB
NXP LPCXpresso1549 NXP LPC External LPC1549 72MHz 256KB 36KB
NXP LPCXpresso54114 NXP LPC On-board LPC54114J256BD64 100MHz 256KB 192KB
NXP LPCXpresso54608 NXP LPC On-board LPC54608ET512 180MHz 512KB 200KB
NXP i.MX RT1010 Evaluation Kit NXP i.MX RT On-board MIMXRT1011DAE5A 500MHz 64KB 128KB
NXP i.MX RT1015 Evaluation Kit NXP i.MX RT On-board MIMXRT1015DAF5A 500MHz 96KB 128KB
NXP i.MX RT1020 Evaluation Kit NXP i.MX RT On-board MIMXRT1021DAG5A 500MHz 64MB 256MB
NXP i.MX RT1050 Evaluation Kit NXP i.MX RT On-board MIMXRT1052DVL6B 600MHz 64MB 512KB
NXP i.MX RT1060 Evaluation Kit NXP i.MX RT On-board MIMXRT1062DVL6A 600MHz 64MB 1MB
NXP i.MX RT1064 Evaluation Kit NXP i.MX RT On-board MIMXRT1064DVL6A 600MHz 4MB 1MB
NXP mbed LPC11U24 NXP LPC On-board LPC11U24 48MHz 32KB 8KB
NXP mbed LPC1768 NXP LPC On-board LPC1768 96MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
N2+ ST STM32 External STM32F405RGT6 168MHz 1MB 192KB

Name Platform Debug MCU Frequency Flash RAM
NodeMCU-32S Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Nordic Beacon Kit (PCA20006) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic Thingy:52 (nRF52-PCA20020) Nordic nRF52 External NRF52832 64MHz 512KB 64KB
Nordic nRF51 Dongle (PCA10031) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF51822-mKIT Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB
Nordic nRF51X22 Development Kit(PCA1000X) Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB
Nordic nRF52-DK Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
Nordic nRF52840-DK Nordic nRF52 On-board NRF52840 64MHz 1MB 256KB
Nordic nRF52840-DK (Adafruit BSP) Nordic nRF52 On-board NRF52840 64MHz 796KB 243KB

Name Platform Debug MCU Frequency Flash RAM
GD32VF103V RVStar Kit Nuclei On-board GD32VF103VBT6 108MHz 128KB 32KB
HummingBird Evaluation Kit Nuclei On-board HUMMINGBIRD 5MHz 64KB 64KB

Name Platform Debug MCU Frequency Flash RAM
OLIMEX ESP32-DevKit-LiPo Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-EVB Espressif 32 External ESP32 240MHz 4MB 320KB
OLIMEX ESP32-GATEWAY Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
OSHChip Nordic nRF51 External NRF51822 32MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
OLIMEXINO-STM32 ST STM32 External STM32F103RBT6 72MHz 128KB 20KB
Olimex STM32-P405 ST STM32 External STM32F405RGT6 168MHz 1MB 192KB
STM32-E407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
STM32-H407 ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
OpenEnergyMonitor emonPi Atmel AVR On-board ATMEGA328P 16MHz 30KB 2KB

Name Platform Debug MCU Frequency Flash RAM
PanStamp AVR Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
Particle Argon Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Particle Boron Nordic nRF52 External NRF52840 64MHz 796KB 243KB
Particle Xenon Nordic nRF52 External NRF52840 64MHz 796KB 243KB

Name Platform Debug MCU Frequency Flash RAM
Piconomix PX-HER0 ST STM32 External STM32L072RB 32MHz 128KB 20KB

Pololu Corporation

Name Platform Debug MCU Frequency Flash RAM
Pololu A-Star 32U4 Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
PrntrBoard V2 ST STM32 External STM32F407RE 168MHz 512KB 192KB

Prusa 3D

Name Platform Debug MCU Frequency Flash RAM
Original Prusa i3 MK3 Multi Material 2.0 Upgrade Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
Prusa RAMBo Atmel AVR On-board ATMEGA2560 16MHz 252KB 8KB

Punch Through

Name Platform Debug MCU Frequency Flash RAM
LightBlue Bean Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
LightBlue Bean+ Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

Pycom Ltd.

Name Platform Debug MCU Frequency Flash RAM
Pycom LoPy Espressif 32 External ESP32 240MHz 4MB 320KB
Pycom LoPy4 Espressif 32 External ESP32 240MHz 4MB 1.25MB

Name Platform Debug MCU Frequency Flash RAM
Quirkbot Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 16KB
RAK811 LoRa Tracker ST STM32 External STM32L151RBT6 32MHz 128KB 32KB

Name Platform Debug MCU Frequency Flash RAM
3D Printer control board ST STM32 External STM32F446RET6 180MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
RedBearLab BLE Nano 1.5 Nordic nRF51 On-board NRF51822 16MHz 256KB 32KB
RedBearLab BLE Nano 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab Blend Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend 2 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
RedBearLab Blend Micro 3.3V/16MHz (overclock) Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
RedBearLab Blend Micro 3.3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
RedBearLab nRF51822 Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

Name Platform Debug MCU Frequency Flash RAM
3D printer controller ST STM32 On-board STM32F765VIT6 216MHz 2MB 512KB

Name Platform Debug MCU Frequency Flash RAM
RepRap RAMBo Atmel AVR On-board ATMEGA2560 16MHz 252KB 8KB

Name Platform Debug MCU Frequency Flash RAM
Minitronics v2.0 Atmel SAM External SAMD21J18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
BlackPill F303CC ST STM32 External STM32F303CCT6 72MHz 256KB 40KB

Name Platform Debug MCU Frequency Flash RAM
ALKS ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
RushUp Cloud-JAM ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
RushUp Cloud-JAM L4 ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
SG-O AirMon Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
SODAQ Autonomo Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ ExpLoRer Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ GaLoRa Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ Mbili Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ Moja Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
SODAQ Ndogo Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
SODAQ ONE Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SODAQ SARA Atmel SAM External SAMD21J18A 48MHz 256KB 32KB
SODAQ SFF Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SODAQ Tatu Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB

Name Platform Debug MCU Frequency Flash RAM
32F412GDISCOVERY ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
32F723EDISCOVERY ST STM32 On-board STM32F723IEK6 216MHz 512KB 192KB
3DP001V1 Evaluation board for 3D printer ST STM32 On-board STM32F401VGT6 84MHz 512KB 96KB
Black STM32F407VE ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Black STM32F407VG ST STM32 External STM32F407VGT6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZET6 168MHz 512KB 128KB
Black STM32F407ZE ST STM32 External STM32F407ZGT6 168MHz 1MB 128KB
BlackPill F401CC ST STM32 External STM32F401CCT6 84MHz 256KB 64KB
Blue STM32F407VE Mini ST STM32 External STM32F407VET6 168MHz 512KB 128KB
Core board F401RCT6 ST STM32 External STM32F401RCT6 84MHz 256KB 64KB
Nucleo G071RB ST STM32 External STM32G071RBT6 64MHz 128KB 36KB
Nucleo G431KB ST STM32 External STM32G431KBT6 170MHz 128KB 32KB
Nucleo G431RB ST STM32 External STM32G431RBT6 170MHz 128KB 32KB
Nucleo G474RE ST STM32 External STM32G474RET6 170MHz 512KB 128KB
P-Nucleo WB55RG ST STM32 On-board STM32WB55RG 64MHz 512KB 192.00KB
RHF76 052 ST STM32 External STM32L051C8T6 32MHz 64KB 8KB
ST 32F3348DISCOVERY ST STM32 On-board STM32F334C8T6 72MHz 64KB 12KB
ST 32F401CDISCOVERY ST STM32 On-board STM32F401VCT6 84MHz 256KB 64KB
ST 32F411EDISCOVERY ST STM32 On-board STM32F411VET6 100MHz 512KB 128KB
ST 32F413HDISCOVERY ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST 32F429IDISCOVERY ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST 32F469IDISCOVERY ST STM32 On-board STM32F469NIH6 180MHz 1MB 384KB
ST 32F746GDISCOVERY ST STM32 On-board STM32F746NGH6 216MHz 1MB 320KB
ST 32F769IDISCOVERY ST STM32 On-board STM32F769NIH6 216MHz 1MB 512KB
ST 32L0538DISCOVERY ST STM32 On-board STM32L053C8T6 32MHz 64KB 8KB
ST 32L100DISCOVERY ST STM32 On-board STM32L100RCT6 32MHz 256KB 16KB
ST 32L476GDISCOVERY ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB
ST 32L496GDISCOVERY ST STM32 On-board STM32L496AGI6 80MHz 1MB 320KB
ST B-L475E-IOT01A Discovery kit ST STM32 On-board STM32L475VGT6 80MHz 1MB 128KB
ST DISCO-L072CZ-LRWAN1 ST STM32 On-board STM32L072CZ 32MHz 192KB 20KB
ST Discovery F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F030R8 ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST Nucleo F031K6 ST STM32 On-board STM32F031K6T6 48MHz 32KB 4KB
ST Nucleo F042K6 ST STM32 On-board STM32F042K6T6 48MHz 32KB 6KB
ST Nucleo F070RB ST STM32 On-board STM32F070RBT6 48MHz 128KB 16KB
ST Nucleo F072RB ST STM32 On-board STM32F072RBT6 48MHz 128KB 16KB
ST Nucleo F091RC ST STM32 On-board STM32F091RCT6 48MHz 256KB 32KB
ST Nucleo F103RB ST STM32 On-board STM32F103RBT6 72MHz 128KB 20KB
ST Nucleo F207ZG ST STM32 On-board STM32F207ZGT6 120MHz 1MB 128KB
ST Nucleo F302R8 ST STM32 On-board STM32F302R8T6 72MHz 64KB 16KB
ST Nucleo F303K8 ST STM32 On-board STM32F303K8T6 72MHz 64KB 12KB
ST Nucleo F303RE ST STM32 On-board STM32F303RET6 72MHz 512KB 64KB
ST Nucleo F303ZE ST STM32 On-board STM32F303ZET6 72MHz 512KB 64KB
ST Nucleo F334R8 ST STM32 On-board STM32F334R8T6 72MHz 64KB 16KB
ST Nucleo F401RE ST STM32 On-board STM32F401RET6 84MHz 512KB 96KB
ST Nucleo F410RB ST STM32 On-board STM32F410RBT6 100MHz 128KB 32KB
ST Nucleo F411RE ST STM32 On-board STM32F411RET6 100MHz 512KB 128KB
ST Nucleo F412ZG ST STM32 On-board STM32F412ZGT6 100MHz 1MB 256KB
ST Nucleo F413ZH ST STM32 On-board STM32F413ZHT6 100MHz 512KB 128KB
ST Nucleo F429ZI ST STM32 On-board STM32F429ZIT6 180MHz 2MB 256KB
ST Nucleo F439ZI ST STM32 On-board STM32F439ZIT6 180MHz 2MB 256KB
ST Nucleo F446RE ST STM32 On-board STM32F446RET6 180MHz 512KB 128KB
ST Nucleo F446ZE ST STM32 On-board STM32F446ZET6 180MHz 512KB 128KB
ST Nucleo F722ZE ST STM32 On-board STM32F722ZET6 216MHz 512KB 256KB
ST Nucleo F746ZG ST STM32 On-board STM32F746ZGT6 216MHz 1MB 320KB
ST Nucleo F756ZG ST STM32 On-board STM32F756ZG 216MHz 1MB 320KB
ST Nucleo F767ZI ST STM32 On-board STM32F767ZIT6 216MHz 2MB 512KB
ST Nucleo H743ZI ST STM32 On-board STM32H743ZIT6 400MHz 2MB 512KB
ST Nucleo L011K4 ST STM32 On-board STM32L011K4T6 32MHz 16KB 2KB
ST Nucleo L031K6 ST STM32 On-board STM32L031K6T6 32MHz 32KB 8KB
ST Nucleo L053R8 ST STM32 On-board STM32L053R8T6 32MHz 64KB 8KB
ST Nucleo L073RZ ST STM32 On-board STM32L073RZ 32MHz 192KB 20KB
ST Nucleo L152RE ST STM32 On-board STM32L152RET6 32MHz 512KB 80KB
ST Nucleo L412KB ST STM32 On-board STM32L412KBU6 80MHz 128KB 40KB
ST Nucleo L432KC ST STM32 On-board STM32L432KCU6 80MHz 256KB 64KB
ST Nucleo L433RC-P ST STM32 On-board STM32L433RC 80MHz 256KB 64KB
ST Nucleo L452RE ST STM32 On-board STM32L452RET6 80MHz 256KB 64KB
ST Nucleo L476RG ST STM32 On-board STM32L476RGT6 80MHz 1MB 128KB
ST Nucleo L486RG ST STM32 On-board STM32L486RGT6 80MHz 1MB 128KB
ST Nucleo L496ZG ST STM32 On-board STM32L496ZGT6 80MHz 1MB 128KB
ST Nucleo L496ZG-P ST STM32 On-board STM32L496ZGT6P 80MHz 1MB 320KB
ST Nucleo L4R5ZI ST STM32 On-board STM32L4R5ZIT6 120MHz 2MB 640KB
ST STM32F0308DISCOVERY ST STM32 On-board STM32F030R8T6 48MHz 64KB 8KB
ST STM32F0DISCOVERY ST STM32 On-board STM32F051R8T6 48MHz 64KB 8KB
ST STM32F3DISCOVERY ST STM32 On-board STM32F303VCT6 72MHz 256KB 48KB
ST STM32F4DISCOVERY ST STM32 On-board STM32F407VGT6 168MHz 1MB 128KB
ST STM32L073Z-EVAL ST STM32 On-board STM32L073VZT6 32MHz 192KB 20KB
ST STM32LDISCOVERY ST STM32 On-board STM32L152RBT6 32MHz 128KB 16KB
ST STM32VLDISCOVERY ST STM32 On-board STM32F100RBT6 24MHz 128KB 8KB
ST STM8S-DISCOVERY ST STM8 On-board STM8S105C6T6 16MHz 32KB 2KB
STEVAL-FCU001V1 Flight controller unit evaluation board ST STM32 External STM32F401CCU6 84MHz 256KB 64KB
STM3210C-EVAL ST STM32 External STM32F107VCT6 72MHz 256KB 64KB
STM32373C-EVAL ST STM32 External STM32F373VCT6 72MHz 256KB 32KB
STM32F072-EVAL ST STM32 External STM32F072VBT6 48MHz 128KB 16KB
STM32F7508-DK ST STM32 On-board STM32F750N8H6 216MHz 64KB 340KB
STM32H747I-DISCO ST STM32 On-board STM32H747XIH6 400MHz 2MB 512KB
SensorTile.box ST STM32 External STM32L4R9ZI 120MHz 2MB 640KB

Name Platform Debug MCU Frequency Flash RAM
SainSmart Due (Programming Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB
SainSmart Due (USB Native Port) Atmel SAM External AT91SAM3X8E 84MHz 512KB 96KB

Name Platform Debug MCU Frequency Flash RAM
Sanguino ATmega1284p (16MHz) Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB
Sanguino ATmega1284p (8MHz) Atmel AVR On-board ATMEGA1284P 8MHz 127KB 16KB
Sanguino ATmega644 or ATmega644A (16 MHz) Atmel AVR On-board ATMEGA644 16MHz 63KB 4KB
Sanguino ATmega644 or ATmega644A (8 MHz) Atmel AVR On-board ATMEGA644 8MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (16 MHz) Atmel AVR On-board ATMEGA644P 16MHz 63KB 4KB
Sanguino ATmega644P or ATmega644PA (8 MHz) Atmel AVR On-board ATMEGA644P 8MHz 63KB 4KB

Name Platform Debug MCU Frequency Flash RAM
Seeeduino LoRaWAN Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Seeed Arch BLE Nordic nRF51 On-board NRF51822 16MHz 128KB 16KB
Seeed Arch Link Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Arch Max ST STM32 On-board STM32F407VET6 168MHz 512KB 192KB
Seeed Arch Pro NXP LPC On-board LPC1768 96MHz 512KB 64KB
Seeed Tiny BLE Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Seeed Wio 3G ST STM32 On-board STM32F439VI 180MHz 2MB 256KB
Seeeduino Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
Wio Lite RISC-V GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB

Name Platform Debug MCU Frequency Flash RAM
NAMote72 ST STM32 External STM32L152RC 32MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
HiFive Unleashed SiFive On-board FU540 1500MHz 32MB 8GB
HiFive1 SiFive On-board FE310 320MHz 16MB 16KB
HiFive1 Rev B SiFive On-board FE310 320MHz 16MB 16KB

Sigma Delta Technologies

Name Platform Debug MCU Frequency Flash RAM
SDT52832B Nordic nRF52 External NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
Silicognition wESP32 Espressif 32 External ESP32 240MHz 4MB 320KB

Silicon Labs

Name Platform Debug MCU Frequency Flash RAM
EFM32GG-STK3700 Giant Gecko Silicon Labs EFM32 On-board EFM32GG990F1024 48MHz 1MB 128KB
EFM32LG-STK3600 Leopard Gecko Silicon Labs EFM32 On-board EFM32LG990F256 48MHz 256KB 32KB
EFM32WG-STK3800 Wonder Gecko Silicon Labs EFM32 On-board EFM32WG990F256 48MHz 256KB 32KB
EFM32ZG-STK3200 Zero Gecko Silicon Labs EFM32 On-board EFM32ZG222F32 24MHz 32KB 4KB
SLSTK3400A USB-enabled Happy Gecko Silicon Labs EFM32 On-board EFM32HG322F64 25MHz 64KB 8KB
SLSTK3401A Pearl Gecko PG1 Silicon Labs EFM32 On-board EFM32PG1B200F256GM48 40MHz 256KB 32KB
Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT Silicon Labs EFM32 On-board EFR32MG12P432F1024 40MHz 1MB 256KB

Name Platform Debug MCU Frequency Flash RAM
GD32VF103V-EVAL GigaDevice GD32V External GD32VF103VBT6 108MHz 128KB 32KB
Sipeed Longan Nano GigaDevice GD32V External GD32VF103CBT6 108MHz 128KB 32KB
Sipeed Longan Nano Lite GigaDevice GD32V External GD32VF103C8T6 108MHz 64KB 20KB
Sipeed MAIX BiT Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX BiT with Mic Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX GO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIX ONE DOCK Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MAIXDUINO Kendryte K210 External K210 400MHz 16MB 6MB
Sipeed MF1 MF1 Kendryte K210 External K210 400MHz 16MB 6MB

Solder Splash Labs

Name Platform Debug MCU Frequency Flash RAM
DipCortex M3 NXP LPC External LPC1347 72MHz 64KB 12KB
Solder Splash Labs DipCortex M0 NXP LPC External LPC11U24 50MHz 32KB 8KB

Name Platform Debug MCU Frequency Flash RAM
SparkFun 9DoF Razor IMU M0 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun ATmega128RFA1 Dev Board Atmel AVR On-board ATMEGA128RFA1 16MHz 16KB 124KB
SparkFun Digital Sandbox Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB
SparkFun Fio V3 3.3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun LoRa Gateway 1-Channel Espressif 32 External ESP32 240MHz 4MB 320KB
SparkFun Makey Makey Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Mega Pro 3.3V/8MHz Atmel AVR On-board ATMEGA2560 8MHz 252KB 8KB
SparkFun Mega Pro 5V/16MHz Atmel AVR On-board ATMEGA2560 16MHz 248KB 8KB
SparkFun Mega Pro Mini 3.3V Atmel AVR On-board ATMEGA2560 8MHz 252KB 8KB
SparkFun MicroView Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
SparkFun Pro Micro 3.3V/8MHz Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Pro Micro 5V/16MHz Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB
SparkFun Qduino Mini Atmel AVR On-board ATMEGA32U4 8MHz 28KB 2.50KB
SparkFun Qwiic Micro Atmel SAM External SAMD21E18A 48MHz 256KB 32KB
SparkFun RED-V RedBoard SiFive On-board FE310 320MHz 16MB 16KB
SparkFun RED-V Thing Plus SiFive On-board FE310 320MHz 16MB 16KB
SparkFun RedBoard Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB
SparkFun RedBoard Turbo Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Dev Breakout Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Mini Breakout Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun SAMD21 Pro RF Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
SparkFun Serial 7-Segment Display Atmel AVR On-board ATMEGA328P 8MHz 31.50KB 2KB

SparkFun Electronics

Name Platform Debug MCU Frequency Flash RAM
SparkFun ESP32 Thing Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
SpellFoundry Sleepy Pi 2 Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB

Switch Science

Name Platform Debug MCU Frequency Flash RAM
Switch Science mbed HRM1017 Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB
Switch Science mbed LPC1114FN28 NXP LPC On-board LPC1114FN28 48MHz 32KB 4KB
Switch Science mbed LPC824 NXP LPC On-board LPC824 30MHz 32KB 8KB
Switch Science mbed TY51822r3 Nordic nRF51 On-board NRF51822 32MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
TI FraunchPad MSP-EXP430FR5739LP TI MSP430 On-board MSP430FR5739 16MHz 15.37KB 1KB
TI LaunchPad (Stellaris) w/ lm4f120 (80MHz) TI TIVA On-board LPLM4F120H5QR 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c123 (80MHz) TI TIVA On-board LPTM4C1230C3PM 80MHz 256KB 32KB
TI LaunchPad (Tiva C) w/ tm4c129 (120MHz) TI TIVA On-board LPTM4C1294NCPDT 120MHz 1MB 256KB
TI LaunchPad MSP-EXP430F5529LP TI MSP430 On-board MSP430F5529 25MHz 47KB 8KB
TI LaunchPad MSP-EXP430FR2311LP TI MSP430 On-board MSP430FR2311 16MHz 3.75KB 1KB
TI LaunchPad MSP-EXP430FR2433LP TI MSP430 On-board MSP430FR2433 8MHz 15KB 4KB
TI LaunchPad MSP-EXP430FR4133LP TI MSP430 On-board MSP430FR4133 8MHz 15KB 2KB
TI LaunchPad MSP-EXP430FR5969LP TI MSP430 On-board MSP430FR5969 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430FR5994LP TI MSP430 On-board MSP430FR5994 16MHz 256KB 4KB
TI LaunchPad MSP-EXP430FR6989LP TI MSP430 On-board MSP430FR6989 8MHz 47KB 2KB
TI LaunchPad MSP-EXP430G2 w/ MSP430G2231 TI MSP430 On-board MSP430G2231 1MHz 2KB 256B
TI LaunchPad MSP-EXP430G2 w/ MSP430G2452 TI MSP430 On-board MSP430G2452 16MHz 8KB 256B
TI LaunchPad MSP-EXP430G2553LP TI MSP430 On-board MSP430G2553 16MHz 16KB 512B

Name Platform Debug MCU Frequency Flash RAM
TTGO LoRa32-OLED V1 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO LoRa32-OLED V2 Espressif 32 External ESP32 240MHz 4MB 320KB
TTGO T-Beam Espressif 32 External ESP32 240MHz 4MB 1.25MB
TTGO T1 Espressif 32 External ESP32 240MHz 4MB 320KB

Taida Century

Name Platform Debug MCU Frequency Flash RAM
Taida Century nRF52 mini board Nordic nRF52 External NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
Sparky V1 F303 ST STM32 External STM32F303CCT6 72MHz 256KB 40KB

Name Platform Debug MCU Frequency Flash RAM
Teensy 3.1 / 3.2 Teensy External MK20DX256 72MHz 256KB 64KB
Teensy 3.5 Teensy External MK64FX512 120MHz 512KB 255.99KB
Teensy 3.6 Teensy External MK66FX1M0 180MHz 1MB 256KB
Teensy 4.0 Teensy External IMXRT1062 600MHz 1.94MB 512KB
Teensy 4.1 Teensy External IMXRT1062 600MHz 7.75MB 512KB
Teensy LC Teensy External MKL26Z64 48MHz 62KB 8KB

Name Platform Debug MCU Frequency Flash RAM
ESPino32 Espressif 32 External ESP32 240MHz 4MB 320KB

The Things Network

Name Platform Debug MCU Frequency Flash RAM
The Things Uno Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
ThunderPack ST STM32 External STM32L072KZ 32MHz 192KB 20KB

Till Harbaum

Name Platform Debug MCU Frequency Flash RAM
ftDuino Atmel AVR On-board ATMEGA32U4 16MHz 28KB 2.50KB

Name Platform Debug MCU Frequency Flash RAM
TinyCircuits TinyDuino Processor Board Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB
TinyCircuits TinyLily Mini Processor Atmel AVR On-board ATMEGA328P 8MHz 30KB 2KB

Name Platform Debug MCU Frequency Flash RAM
ESP32 FM DevKit Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
VAkE v1.0 ST STM32 External STM32F446RET6 180MHz 512KB 128KB

Name Platform Debug MCU Frequency Flash RAM
VNG VBLUNO51 Nordic nRF51 On-board NRF51822 16MHz 128KB 32KB
VNG VBLUno52 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB

Name Platform Debug MCU Frequency Flash RAM
VintLabs ESP32 Devkit Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
WEMOS LOLIN D32 Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN D32 PRO Espressif 32 External ESP32 240MHz 4MB 320KB
WEMOS LOLIN32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos D1 MINI ESP32 Espressif 32 External ESP32 240MHz 4MB 320KB
WeMos WiFi and Bluetooth Battery Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
WIZwiki-W7500 WIZNet W7500 On-board WIZNET7500 48MHz 128KB 48KB
WIZwiki-W7500ECO WIZNet W7500 On-board WIZNET7500ECO 48MHz 128KB 48KB
WIZwiki-W7500P WIZNet W7500 On-board WIZNET7500P 48MHz 128KB 48KB

Name Platform Debug MCU Frequency Flash RAM
Waveshare BLE400 Nordic nRF51 External NRF51822 32MHz 256KB 32KB

Wicked Device

Name Platform Debug MCU Frequency Flash RAM
Wicked Device WildFire V2 Atmel AVR On-board ATMEGA1284P 16MHz 120.00KB 16KB
Wicked Device WildFire V3 Atmel AVR On-board ATMEGA1284P 16MHz 127KB 16KB

Name Platform Debug MCU Frequency Flash RAM
Talk2 Whisper Node Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

Name Platform Debug MCU Frequency Flash RAM
Artix-7 35T Arty FPGA Evaluation Kit Shakti On-board E-CLASS 50MHz 0B 128KB
Arty A7-100: Artix-7 FPGA Development Board Shakti On-board C-CLASS 50MHz 0B 128MB
Arty FPGA Dev Kit SiFive On-board FE310 450MHz 16MB 256MB

Name Platform Debug MCU Frequency Flash RAM
XinaBox CW02 Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
Briki ABC (MBC-WB) - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki ABC (MBC-WB) - Samd21 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB
Briki MBC-WB - ESP32 Espressif 32 External ESP32 240MHz 3.25MB 320KB
Briki MBC-WB - Samd21 Atmel SAM External SAMD21G18A 48MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
ng-beacon Nordic nRF51 External NRF51822 16MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
nicai-systems BOB3 coding bot Atmel AVR On-board ATMEGA88 8MHz 8KB 1KB
nicai-systems NIBO 2 robot Atmel AVR On-board ATMEGA128 16MHz 128KB 4KB
nicai-systems NIBO burger robot Atmel AVR On-board ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBO burger robot with Tuning Kit Atmel AVR On-board ATMEGA1284P 20MHz 128KB 16KB
nicai-systems NIBObee robot Atmel AVR On-board ATMEGA16 15MHz 16KB 1KB
nicai-systems NIBObee robot with Tuning Kit Atmel AVR On-board ATMEGA1284P 20MHz 128KB 16KB

Name Platform Debug MCU Frequency Flash RAM
oddWires IoT-Bus Io Espressif 32 External ESP32 240MHz 4MB 320KB
oddWires IoT-Bus Proteus Espressif 32 External ESP32 240MHz 4MB 320KB

Name Platform Debug MCU Frequency Flash RAM
L476DMW1K ST STM32 On-board STM32L476VGT6 80MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
sakura.io Evaluation Board ST STM32 On-board STM32F411RET6 100MHz 1MB 128KB

Name Platform Debug MCU Frequency Flash RAM
Sino:Bit Nordic nRF51 External NRF51822 32MHz 256KB 32KB

Name Platform Debug MCU Frequency Flash RAM
Mbed Connect Cloud ST STM32 On-board STM32F439ZIY6 168MHz 2MB 256KB
u-blox C027 NXP LPC On-board LPC1768 96MHz 512KB 64KB
u-blox C030-N211 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox C030-R410M IoT ST STM32 On-board STM32F437VG 180MHz 1MB 256KB
u-blox C030-U201 IoT Starter Kit ST STM32 External STM32F437VG 180MHz 1MB 256KB
u-blox EVK-NINA-B1 Nordic nRF52 On-board NRF52832 64MHz 512KB 64KB
u-blox EVK-ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB
u-blox ODIN-W2 ST STM32 External STM32F439ZIY6 168MHz 2MB 256KB

Name Platform Debug MCU Frequency Flash RAM
ubIQio Ardhat Atmel AVR On-board ATMEGA328P 16MHz 31.50KB 2KB

y5 design

Name Platform Debug MCU Frequency Flash RAM
y5 LPC11U35 mbug NXP LPC External LPC11U35 48MHz 64KB 10KB
y5 nRF51822 mbug Nordic nRF51 On-board NRF51822 16MHz 256KB 16KB

PIO Unit Testing allows segregating each part of the firmware/program and testing that the individual parts are working correctly. Using PIO Unit Testing Engine you can execute the same tests on the local host machine (native), on the multiple local embedded devices/boards (connected to local host machine), or on both. When testing both, PlatformIO builds firmware on the host machine, uploads into a target device, starts tests, and collects the test results into test reports. The final information will be shown on the host side with informative output and statistic.

Using PIO Remote you can start unit tests on the Remote Device from anywhere in the world or integrate with Continuous Integration systems.

  • Demo
  • Tutorials and Examples
  • Tutorials
  • Project Examples

  • Configuration
  • Test Types
  • Desktop
  • Embedded

•
Test Runner
  • Local
  • Remote

  • Test Transport
  • Workflow
•
Shared Code

  • API
  • CLI Guide

This is a demo of Local & Embedded: Calculator, which demonstrates running embedded tests on physical hardware (Arduino Uno) and native tests on host machine (desktop).

Learn more about platformio test command. .SS Tutorials and Examples

  • Unit Testing of a "Blink" Project
  • STM32Cube HAL and Nucleo-F401RE: debugging and unit testing
  • ThingForward: Start Embedded Testing with PlatformIO
  • ThingForward: Embedded Testing with PlatformIO - Part 2
  • ThingForward: Embedded Testing with PlatformIO – Part 3: Remoting
  • ThingForward: Embedded Testing with PlatformIO – Part 4: Continuous Integration
  • ThingForward, Webinar: Unit Testing for Embedded with PlatformIO and Qt Creator
  • Xose Pérez: Automated unit testing in the metal

Project Examples

  • Embedded: Wiring Blink
  • Local & Embedded: Calculator
  • PlatformIO Remote Unit Testing Example

For the other examples and source code please follow to PlatformIO Unit Testing Examples repository.

PIO Unit Testing Engine can be configured from "platformio.ini" (Project Configuration File)

PIO Unit Testing Engine builds a test program for a host machine using Native development platform. This test could be run only with the desktop or Continuous Integration VM instance.

NOTE:

PlatformIO does not install any toolchains automatically for Native and requires GCC toolchain to be installed on your host machine. Please open Terminal and check that the gcc command is installed.


PIO Unit Testing Engine builds a special firmware for a target device (board) and programs it. Then, it connects to this device using configured Serial test_port and communicates via test_transport. Finally, it runs tests on the embedded side, collects results, analyzes them, and provides a summary on a host machine side (desktop).

NOTE:

Please note that the PIO Unit Testing Engine uses the first available Serial/UART implementation (depending on a framework) as a communication interface between the PIO Unit Testing Engine and target device. If you use Serial in your project libraries, please wrap/hide Serial-based blocks with #ifndef UNIT_TEST macro.

Also, you can create custom test_transport and implement the base interface.



Test Runner allows you to process specific environments or ignore a test using "Glob patterns". You can also ignore a test for specific environments using a test_ignore option from "platformio.ini" (Project Configuration File).

Allows you to run a test on a host machine or on a target device (board), which is directly connected to the host machine. In this case, you need to use the platformio test command.

Allows you to run test on a remote machine or remote target device (board) without having to depend on OS software, extra software, SSH, VPN or opening network ports. Remote Unit Testing works in pair with PIO Remote. In this case, you need to use the special command platformio remote test.

PlatformIO supports multiple Continuous Integration systems where you can run unit tests at each integration stage. See real PlatformIO Remote Unit Testing Example.

PIO Unit Testing Engine engine uses different transports to communicate with a target device. By default, it uses Serial/UART transport provided by a framework. For example, when "framework = arduino", the first available Serial will be used. When Native dev-platform is used a native transport will be activated automatically. See example below.

Default baudrate/speed is set to test_speed.

You can also define custom transport and implement its interface:

  • unittest_uart_begin();
  • unittest_uart_putchar(char c);
  • unittest_uart_flush();
  • unittest_uart_end();

Examples

1.
Custom transport for Native platform

•
Set test_transport = custom in "platformio.ini" (Project Configuration File)

[env:mycustomtransport]
platform = native
test_transport = custom


•
Create unittest_transport.h file in project/test directory and implement prototypes above

#ifndef UNITTEST_TRANSPORT_H
#define UNITTEST_TRANSPORT_H
#include <stdio.h>
void unittest_uart_begin() {
}
void unittest_uart_putchar(char c) {
  putchar(c);
}
void unittest_uart_flush() {
  fflush(stdout);
}
void unittest_uart_end() {
}
#endif




2.
STM32Cube HAL and Nucleo-F401RE: debugging and unit testing

1.
Create PlatformIO project using the platformio project init command. For Desktop Unit Testing (on a host machine), you need to use Native.

; PlatformIO Project Configuration File
;
;   Build options: build flags, source filter, extra scripting
;   Upload options: custom port, speed and extra flags
;   Library options: dependencies, extra library storages
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
;
; Embedded platforms
;
[env:uno]
platform = atmelavr
framework = arduino
board = uno
[env:nodemcu]
platform = espressif8266
framework = arduino
board = nodemcuv2
;
; Desktop platforms (Win, Mac, Linux, Raspberry Pi, etc)
; See https://platformio.org/platforms/native
;
[env:native]
platform = native


2.
Create a test folder in a root of your project. See test_dir.
3.
Write a test using API. Each test is a small independent program/firmware with its own main() or setup()/loop() functions. Test should start with UNITY_BEGIN() and finish with UNITY_END() calls.

WARNING:

If your board does not support software resetting via Serial.DTR/RTS, you should add at least 2 seconds delay before UNITY_BEGIN(). That time is needed to establish a Serial connection between a host machine and a target device. 

delay(2000); // for Arduino framework
wait(2);     // for ARM mbed framework
UNITY_BEGIN();




4.
Place a test in the test directory. If you have more than one test, split them into sub-folders. For example, test/test_1/*.[c,cpp,h], test_N/*.[c,cpp,h], etc. If there is no such directory in the test folder, then PIO Unit Testing Engine will treat the source code of test folder as SINGLE test.
5.
Run tests using the platformio test command.

PIO Unit Testing Engine does not build source code from src_dir folder by default. If you have a shared/common code between your "main" and "test" programs, you have 2 options:

1.
RECOMMENDED. We recommend splitting the source code into multiple components and placing them into lib_dir (project's private libraries and components). Library Dependency Finder (LDF) will find and include these libraries automatically in the build process. You can include any library/component header file in your test or program source code via #include <MyComponent.h>.

See Local & Embedded: Calculator for an example, where we have a "calculator" component in lib_dir folder and include it in tests and the main program using #include <calculator.h>.

2.
Manually instruct PlatformIO to build source code from src_dir folder using test_build_project_src option in "platformio.ini" (Project Configuration File):

[env:myenv]
platform = ...
test_build_project_src = true


This is very useful if you unit test independent libraries where you can't split source code.

WARNING:

Please note that you will need to use #ifdef UNIT_TEST and #endif guard to hide non-test related source code. For example, own main() or setup() / loop() functions.



Summary of the Unity Test API:

•
Running Tests
•
RUN_TEST(func)

•
Ignoring Tests
  • TEST_IGNORE()
  • TEST_IGNORE_MESSAGE (message)

•
Aborting Tests
  • TEST_PROTECT()
  • TEST_ABORT()

•
Basic Validity Tests
  • TEST_ASSERT_TRUE(condition)
  • TEST_ASSERT_FALSE(condition)
  • TEST_ASSERT(condition)
  • TEST_ASSERT_UNLESS(condition)
  • TEST_FAIL()
  • TEST_FAIL_MESSAGE(message)

•
Numerical Assertions: Integers
  • TEST_ASSERT_EQUAL_INT(expected, actual)
  • TEST_ASSERT_EQUAL_INT8(expected, actual)
  • TEST_ASSERT_EQUAL_INT16(expected, actual)
  • TEST_ASSERT_EQUAL_INT32(expected, actual)
  • TEST_ASSERT_EQUAL_INT64(expected, actual)
  • TEST_ASSERT_EQUAL_UINT(expected, actual)
  • TEST_ASSERT_EQUAL_UINT8(expected, actual)
  • TEST_ASSERT_EQUAL_UINT16(expected, actual)
  • TEST_ASSERT_EQUAL_UINT32(expected, actual)
  • TEST_ASSERT_EQUAL_UINT64(expected, actual)
  • TEST_ASSERT_EQUAL_HEX(expected, actual)
  • TEST_ASSERT_EQUAL_HEX8(expected, actual)
  • TEST_ASSERT_EQUAL_HEX16(expected, actual)
  • TEST_ASSERT_EQUAL_HEX32(expected, actual)
  • TEST_ASSERT_EQUAL_HEX64(expected, actual)
  • TEST_ASSERT_EQUAL_HEX8_ARRAY(expected, actual, elements)
  • TEST_ASSERT_EQUAL(expected, actual)
  • TEST_ASSERT_INT_WITHIN(delta, expected, actual)

•
Numerical Assertions: Bitwise
  • TEST_ASSERT_BITS(mask, expected, actual)
  • TEST_ASSERT_BITS_HIGH(mask, actual)
  • TEST_ASSERT_BITS_LOW(mask, actual)
  • TEST_ASSERT_BIT_HIGH(mask, actual)
  • TEST_ASSERT_BIT_LOW(mask, actual)

•
Numerical Assertions: Floats
  • TEST_ASSERT_FLOAT_WITHIN(delta, expected, actual)
  • TEST_ASSERT_EQUAL_FLOAT(expected, actual)
  • TEST_ASSERT_EQUAL_DOUBLE(expected, actual)

•
String Assertions
  • TEST_ASSERT_EQUAL_STRING(expected, actual)
  • TEST_ASSERT_EQUAL_STRING_LEN(expected, actual, len)
  • TEST_ASSERT_EQUAL_STRING_MESSAGE(expected, actual, message)
  • TEST_ASSERT_EQUAL_STRING_LEN_MESSAGE(expected, actual, len, message)

•
Pointer Assertions
  • TEST_ASSERT_NULL(pointer)
  • TEST_ASSERT_NOT_NULL(pointer)

•
Memory Assertions
•
TEST_ASSERT_EQUAL_MEMORY(expected, actual, len)


CLI Guide

Native extensions and plugins provide official integration with IDEs/Text Editors and contain built-in PlatformIO Core (CLI) and PlatformIO Home. We highly recommend to use the next native integrations for:

  • VSCode
  • CLion (Experimental)

NOTE:

In our experience, VSCode offers better system performance, and users have found it easier to get started


Cloud9 combines a powerful online code editor with a full Ubuntu workspace in the cloud. Workspaces are powered by Docker Ubuntu containers that give you full freedom over your environment, including sudo rights. Do a git push, compile SASS, see server output, and Run apps easily with the built-in Terminal and Runners.

•
Cloud9
  • Demo
  • Integration
  • Quick Start
  • PlatformIO Build System
  • Remote Device Manager
  • Remote Firmware Uploading
  • Remote Serial Port Monitor
  • Multi-Project workspace


NOTE:

1.
Please make sure to read PIO Remote guide first.
2.
You need PIO Account if you don't have it. Registration is FREE.
3.
You should have a running PIO Remote Agent on a remote machine where hardware devices are connected physically or accessible for the remote operations. See PIO Remote Quick Start for details.



.SS Integration

1.
Sign in to Cloud9. A registration is FREE and gives you for FREE 1 private workspace (where you can host multiple PlatformIO Projects) and unlimited public workspaces.
2.
Create a new workspace using Blank template

[image]
3.
Install PlatformIO Core (CLI) using Cloud IDE Terminal. Paste a next command

sudo python -c "$(curl -fsSL https://raw.githubusercontent.com/platformio/platformio/develop/scripts/get-platformio.py)"


[image]
4.
Log in to PIO Account using platformio account login command.

Quick Start

Let's create our first PlatformIO-based Cloud9 Project

1.
Initialize new PlatformIO-based Project. Run a next command in Cloud IDE Terminal:

platformio project init --board <ID>
# initialize project for Arduino Uno
platformio project init --board uno


To get board ID please use platformio boards command or Embedded Boards Explorer.

2.
Create new source file named main.cpp in src folder using Project Tree (left side). Please make right click on src folder, then "New File" and insert a next content:

#include <Arduino.h>
int i = 0;
void setup() {
    Serial.begin(9600);
    Serial.println("Hello Cloud9!");
}
void loop() {
    /*  serial echo */
    while (Serial.available()) {
        Serial.write(Serial.read());
    }
    i++;
    Serial.println(i);
    delay(100);
}



[image]
3.
If you prefer to work with PlatformIO Core (CLI) CLI, then you can process project using Cloud IDE Terminal and the next commands:
  • platformio run - build project locally (using Cloud IDE's virtual machine)
  • pio run -t clean - clean project
  • pio remote run -t upload - upload firmware (program) to a remote device
  • platformio remote device list - list available remote devices
  • platformio remote device monitor - Remote Serial Port Monitor

If you are interested in better integration with Cloud9 and GUI, please read guide below where we will explain how to create custom Build System for PlatformIO and own Runners.


Cloud9 allows one to create own build system and use hotkey or command (Menu: Run > Build) to build a project.

Let's create PlatformIO Build System that will be used for C/C++/H/INO/PDE files by default. Please click on Menu: Run > Build System > New Build System and replace all content with the next:

{
    "cmd" : ["pio", "run", "-d", "$file"],
    "info" : "Building $project_path/$file_name",
    "selector": "^.*\\.(cpp|c|h|hpp|S|ini|ino|pde)$"
}


Save new Build System and give a name PIOBuilder. Now, you can select it as default Build System using Menu: Run > Build System > PIOBuilder.

Remote Device Manager

Remote Device Manager works in pair with PIO Remote. You can list remote devices that are connected to host machine where PIO Remote Agent is started or are visible for it.

Let's create New Run Configuration (shortcut) that will be used for Remote Device Manager. Please click on Menu: Run > Run Configurations > Manage..., then "Add New Config" and specify the next values:

  • First Blank Input: a name of runner. Please set it to "PIO: Remote Devices"
  • Command: set to pio remote device list
  • Runner: set to "Shell command"

[image]

Remote Firmware Uploading

Remote Firmware Uploading works in pair with PIO Remote. You can deploy firmware (program) to any devices which are visible for PIO Remote Agent.

Let's create New Run Configuration (shortcut) that will be used for Remote Firmware Uploading. Please click on Menu: Run > Run Configurations > Manage..., then "Add New Config" and specify the next values:

  • First Blank Input: a name of runner. Please set it to "PIO: Remote Upload"
  • Command: set to pio remote run -t upload
  • Runner: set to "Shell command"

[image]

Remote Serial Port Monitor

Remote Serial Port Monitor works in pair with PIO Remote. You can read or send data to any device that is connected to host machine where PIO Remote Agent is started. To list active agents please use this command platformio remote agent list.

Let's create New Run Configuration (shortcut) that will be used for Remote Serial Port Monitor. Please click on Menu: Run > Run Configurations > Manage..., then "Add New Config" and specify the next values:

  • First Blank Input: a name of runner. Please set it to "PIO: Remote Serial Monitor"
  • Command: set to pio remote device monitor
  • Runner: set to "Shell command"

[image]

Multi-Project workspace

You can have multiple PlatformIO-based Projects in the same workspace. We recommend a next folders structure:

├── project-A
│   ├── lib
│   │   └── README
│   ├── platformio.ini
│   └── src
│       └── main.ino
└── project-B
    ├── lib
    │   └── README
    ├── platformio.ini
    └── src
        ├── main.cpp
        └── main.h


In this case, you need to create 2 "New Run Configuration" for Remote Firmware Uploading with using the next commands:

  • pio remote run --project-dir project-A -t upload for Project-A
  • pio remote run -d project-B -t upload for Project-B

See documentation for platformio remote run --project-dir option.

Codeanywhere is a Cross Platform Cloud IDE and it has all the features of Desktop IDE but with additional features only a cloud application can give you! Codeanywhere is very flexible and you can set up your workflow any way you want it. The elegant development environment will let you focus on building great applications quicker. All the features you will need for any coding task are built into Codeanywhere, making development more productive and fun.

•
Codeanywhere
  • Demo
  • Integration
  • Quick Start
  • Run Button
  • Remote Device Manager
  • Remote Firmware Uploading
  • Remote Serial Port Monitor
  • Multi-Project workspace


NOTE:

1.
Please make sure to read PIO Remote guide first.
2.
You need PIO Account if you don't have it. Registration is FREE.
3.
You should have a running PIO Remote Agent on a remote machine where hardware devices are connected physically or accessible for the remote operations. See PIO Remote Quick Start for details.



.SS Integration

1.
Sign in to Codeanywhere. A registration is FREE and gives you unlimited private projects within the one Container.
2.
Open Dashboard Projects
3.
Create a new Project and open it. In Connection Wizard create new Container:
  • Name set to "PlatformIO"
  • Stack search for Python stack (not Python3) that is based on Ubuntu OS.
  • Click on "Create" button.


[image]
4.
Open SSH-Terminal tab (right click on Container (PlatformIO) > SSH Terminal) and install PlatformIO Core (CLI) using a next command

sudo python -c "$(curl -fsSL https://raw.githubusercontent.com/platformio/platformio/develop/scripts/get-platformio.py)"


[image]
5.
Log in to PIO Account using platformio account login command.

Quick Start

Let's create our first PlatformIO-based Codeanywhere Project

1.
Initialize new PlatformIO-based Project. Run a next command in a Cloud IDE SSH Terminal:

platformio project init --board <ID>
# initialize project for Arduino Uno
platformio project init --board uno


To get board ID please use platformio boards command or Embedded Boards Explorer.

If you do not see created project, please refresh Project Tree using right-click on Container Name (PlatformIO) > Refresh.

2.
Create new source file named main.cpp in src folder using Project Tree (left side). Please make right click on src folder, then "Create File" and insert a next content:

#include <Arduino.h>
int i = 0;
void setup() {
    Serial.begin(9600);
    Serial.println("Hello Codeanywhere!");
}
void loop() {
    /*  serial echo */
    while (Serial.available()) {
        Serial.write(Serial.read());
    }
    i++;
    Serial.println(i);
    delay(100);
}



[image]
3.
If you prefer to work with PlatformIO Core (CLI) CLI, then you can process project using Cloud IDE SSH Terminal and the next commands:
  • platformio run - build project locally (using Cloud IDE's virtual machine)
  • pio run -t clean - clean project
  • pio remote run -t upload - upload firmware (program) to a remote device
  • platformio remote device list - list available remote devices
  • platformio remote device monitor - Remote Serial Port Monitor

4.
We recommend to hide "Hidden Files". You can do that via Cloud IDE Menu: View > Show Hidden Files.

Codeanywhere provides a quick "Run Project" button where you can specify own command. Let's add "PlatformIO Build Project" command:

1.
Open "Project Config" via right click on Container Name (PlatformIO) > Config
2.
Set commands field to

"commands": [
    "pio run"
]




3.
Save configuration file.

Now, try to click on "Run Project" button. You can assign any PlatformIO command to this button. [image]

Remote Device Manager

Remote Device Manager works in pair with PIO Remote. You can list remote devices that are connected to host machine where PIO Remote Agent is started or are visible for it.

1.
Open Cloud IDE SSH Terminal
2.
Paste this command

pio remote device list





[image]

Remote Firmware Uploading

Remote Firmware Uploading works in pair with PIO Remote. You can deploy firmware to any devices which are visible for PIO Remote Agent.

1.
Open Cloud IDE SSH Terminal
2.
Paste this command

pio remote run -t upload





[image]

Remote Serial Port Monitor

Remote Serial Port Monitor works in pair with PIO Remote. You can read or send data to any device that is connected to host machine where PIO Remote Agent is started. To list active agents please use this command platformio remote agent list.

1.
Open Cloud IDE SSH Terminal
2.
Paste this command

pio remote device monitor





[image]

Multi-Project workspace

You can have multiple PlatformIO-based Projects in the same workspace. We recommend a next folders structure:

├── project-A
│   ├── lib
│   │   └── README
│   ├── platformio.ini
│   └── src
│       └── main.ino
└── project-B
    ├── lib
    │   └── README
    ├── platformio.ini
    └── src
        ├── main.cpp
        └── main.h


In this case, you need to use -d, --project-dir option for platformio run or platformio remote run commands:

  • pio remote run --project-dir project-A -t upload build Project-A
using Project-A

•
using Project-B


See documentation for platformio remote run --project-dir option.

Eclipse Che is an open-source Java based developer workspace server and cloud integrated development environment (IDE) which provides a remote development platform for multi-user purpose. The workspace server comes with a RESTful webservice and provides high flexibility. It also contains a SDK which can be used to create plug-ins for languages, frameworks or tools.

•
Eclipse Che
  • Demo
  • Integration
  • Quick Start
  • Multi-Project workspace


NOTE:

1.
Please make sure to read PIO Remote guide first.
2.
You need PIO Account if you don't have it. Registration is FREE.
3.
You should have a running PIO Remote Agent on a remote machine where hardware devices are connected physically or accessible for the remote operations. See PIO Remote Quick Start for details.



[image]

1.
Sign in to Codenvy (based on Eclipse Che). A registration is FREE and gives you unlimited private projects.
2.
Open Workspaces tab
3.
Click on "Add Workspace", then switch to "Runtime" tab.
  • Name set to "PlatformIO"
  • Stack search for PLATFORMIO
  • Click on "Create" button, then "Open".


[image]

4.
Using opened Terminal, please log in to PIO Account using platformio account login command.

Quick Start

Let's create our first PlatformIO-based Codenvy Project

1.
Click on Menu: Workspace > Create New Project and select platformio-arduino-blink sample. Set "Name" to "Arduino Blink" and press "Create".

[image]
2.
Now you can use dropdown Commands menu and process project with "run" command

[image]
3.
If you prefer to work with PlatformIO Core (CLI) CLI, then you can process project using Cloud IDE Terminal and the next commands:
  • platformio run - build project locally (using Cloud IDE's virtual machine)
  • pio run -t clean - clean project
  • pio remote run -t upload - upload firmware (program) to a remote device
  • platformio remote device list - list available remote devices
  • platformio remote device monitor - Remote Serial Port Monitor


Multi-Project workspace

You can have multiple PlatformIO-based Projects in the same workspace. We recommend a next folders structure:

├── project-A
│   ├── lib
│   │   └── README
│   ├── platformio.ini
│   └── src
│       └── main.ino
└── project-B
    ├── lib
    │   └── README
    ├── platformio.ini
    └── src
        ├── main.cpp
        └── main.h


In this case, you need to use -d, --project-dir option for platformio run or platformio remote run commands:

  • pio remote run --project-dir project-A -t upload build Project-A
using Project-A

•
using Project-B


See documentation for platformio remote run --project-dir option.

PlatformIO IDE is the next-generation integrated development environment for IoT.

•
Cross-platform build system without external dependencies to the OS software:
  • 800+ Boards
  • 35+ Development Platforms
  • 20+ Frameworks



  • PIO Unified Debugger
  • PIO Remote
  • PIO Unit Testing
  • C/C++ Intelligent Code Completion
  • C/C++ Smart Code Linter for rapid professional development
  • Library Manager for the hundreds popular libraries
  • Multi-projects workflow with multiple panes
  • Themes support with dark and light colors
  • Serial Port Monitor
  • Built-in Terminal with PlatformIO Core (CLI) and CLI tool (pio, platformio)
  • Built-in PlatformIO Home.


----



Atom is a text editor that's modern, approachable, yet hackable to the core—a tool you can customize to do anything but also use productively without ever touching a config file. .SS Contents

•
Installation
  • I. Atom
  • II. Clang for Intelligent Code Completion

•
Quick Start
  • Launch
  • Setting Up the Project
  • Process Project

  • Menu item PlatformIO
  • PlatformIO Toolbar
  • Building / Uploading / Targets
  • Intelligent Code Completion
  • Smart Code Linter
  • Install Shell Commands
  • Known issues
•
Smart Code Linter is disabled for Arduino files
  • Convert Arduino file to C++ manually
  • Force Arduino file as C++

•
Arch Linux: PlatformIO IDE Terminal issue

•
Frequently Asked Questions
  • Keep build panel visible
  • Automatically save on build
  • Jump to Declaration
  • Code Formatting

•
Uninstall Atom with PlatformIO IDE
  • Windows
  • macOS
  • Linux

  • Articles / Manuals
  • Changelog

NOTE:

Please note that you do not need to install PlatformIO Core (CLI) separately if you are going to use PlatformIO IDE for Atom. PlatformIO Core (CLI) is built into PlatformIO IDE and you will be able to use it within PlatformIO IDE Terminal.

Also, PlatformIO IDE allows one to install PlatformIO Core (CLI) Shell Commands (pio, platformio) globally to your system via Menu: PlatformIO > Install Shell Commands.



0.
Download and install GitHub's official Atom text editor. PlatformIO IDE is built on top of it.
1.
Open Atom Package Manager

  • Mac OS X, Menu: Atom > Preferences > Install
  • Windows, Menu: File > Settings > Install
  • Linux, Menu: Edit > Preferences > Install



2.
Search for the official platformio-ide package
3.
Install PlatformIO IDE.

[image]

PlatformIO IDE uses Clang for the Intelligent Code Completion. To check that clang is available in your system, please open Terminal and run clang --version. If clang is not installed, then install it and restart Atom:

  • Mac OS X: Install the latest Xcode along with the latest Command Line Tools (they are installed automatically when you run clang in Terminal for the first time, or manually by running xcode-select --install
  • Windows: Download Clang 3.9.1 for Windows. Please select "Add LLVM to the system PATH" option on the installation step.
  • Clang 3.9.1 for Windows (32-bit)
  • Clang 3.9.1 for Windows (64-bit)

[image]

WARNING:

PLEASE DO NOT INSTALL CLANG 4.0. TEMPORARILY, WE SUPPORT ONLY CLANG 3.9.

If you see a Failed to find MSBuild toolsets directory error in the installation console, please ignore it and press any key to close this window. PlatformIO IDE uses only the Clang completion engine, which should work after that without any problems.



  • Linux: Using package managers: apt-get install clang or yum install clang.
  • Other Systems: Download the latest Clang for the other systems.

WARNING:

If some libraries are not visible in PlatformIO IDE for Atom and Code Completion or Code Linting does not work properly, please perform Menu: PlatformIO > Rebuild C/C++ Project Index (Autocomplete, Linter)


Quick Start

This tutorial introduces you to the basics of PlatformIO IDE workflow and shows you the creation process for a simple "Blink" example. After finishing, you will have a general understanding of how to work with projects in the IDE.

After installation, launch PlatformIO IDE by opening Atom. Once Atom is opened, the PlatformIO IDE auto installer will continue to install dependent packages and PlatformIO Core (CLI). Please be patient and let the installation complete. Once finished, PlatformIO IDE will ask you to reload the Atom window to apply installed components. Please click on Reload Now. After that, PlatformIO IDE is ready for use. Happy coding!

Setting Up the Project

1.
Click on the "PlatformIO Home" button on the PlatformIO Toolbar

[image]

2.
Click on "New Project", select a board and create a new PlatformIO Project

[image]
3.
Open the main.cpp file in the src folder and replace its contents with the following:

WARNING:

The code below only works with Arduino-based boards. Please visit the PlatformIO Project Examples repository for other pre-configured projects.


/**
 * Blink
 *
 * Turns on an LED on for one second,
 * then off for one second, repeatedly.
 */
#include "Arduino.h"
// Set LED_BUILTIN if it is not defined by Arduino framework
// #define LED_BUILTIN 13
void setup()
{
  // initialize LED digital pin as an output.
  pinMode(LED_BUILTIN, OUTPUT);
}
void loop()
{
  // turn the LED on (HIGH is the voltage level)
  digitalWrite(LED_BUILTIN, HIGH);
  // wait for a second
  delay(1000);
  // turn the LED off by making the voltage LOW
  digitalWrite(LED_BUILTIN, LOW);
   // wait for a second
  delay(1000);
}


[image]

Process Project

PlatformIO IDE proposes different ways to process the project (build, clean, upload firmware, run other targets) using:

  • PlatformIO Toolbar
  • Menu item PlatformIO
  • Building / Uploading / Targets and hotkeys



[image]
5.
Run Build and you should see a green "success" result in the build panel:

[image]

To upload firmware to the board, run Upload.

6.
What is more, you can run specific target or process project environment using Menu: PlatformIO > Run other target... or call targets list from the status bar (bottom, left corner):

And select desired target: .INDENT 0.0

7.
To launch the built-in terminal interface, choose Menu: PlatformIO > Terminal or press the corresponding icon in the PlatformIO toolbar:


This provides you fast access to a set of powerful PlatformIO Core (CLI) CLI commands: .INDENT 0.0

8.
To run the built-in "Serial Monitor", choose Menu: PlatformIO > Serial Monitor or press the corresponding icon in the PlatformIO toolbar:


The monitor has several settings to adjust your connection:

It also allows you to communicate with your board in an easy way: .SS Menu item PlatformIO

platformio-ide package adds to Atom new menu item named Menu: PlatformIO (after Menu: Help item). [image]

PlatformIO Toolbar

PlatformIO IDE Toolbar contains quick access buttons for the popular commands. Each button contains a hint (leave the mouse on it for a moment). [image]

  • PlatformIO Home
  • PlatformIO: Build
  • PlatformIO: Upload
  • PlatformIO: Clean
  • PIO Unified Debugger
  • Run other target (Build environments, PIO Unit Testing)
  • Toggle build panel
  • ||
  • Find in Project...
  • PIO Terminal
  • Serial Monitor
  • ||
  • Atom Settings

  • cmd-alt-b / ctrl-alt-b / f9 builds project without auto-uploading.
  • cmd-alt-u / ctrl-alt-u builds and uploads (if no errors).
  • cmd-alt-c / ctrl-alt-c cleans compiled objects.
  • cmd-alt-t / ctrl-alt-t / f7 run other targets (Upload using Programmer, Upload SPIFFS image, Update platforms and libraries).
  • cmd-alt-g / ctrl-alt-g / f4 cycles through causes of build error.
  • cmd-alt-h / ctrl-alt-h / shift-f4 goes to the first build error.
  • cmd-alt-v / ctrl-alt-v / f8 toggles the build panel.
  • escape terminates build / closes the build window.

More options: Menu: PlatformIO > Settings > Build.

PlatformIO IDE uses clang for the Intelligent Code Completion. To install it or check if it is already installed, please follow see the step II. Clang for Intelligent Code Completion from Installation guide.

WARNING:

The libraries which are added/installed after the initializing process will not be reflected in the code linter. You need Menu: PlatformIO > Rebuild C/C++ Project Index (Autocomplete, Linter).


PlatformIO IDE uses PlatformIO's pre-built GCC toolchains for Smart Code Linter and rapid professional development. The configuration data are located in .gcc-flags.json. This file will be automatically created and preconfigured when you initialize project using Menu: PlatformIO > Initialize new PlatformIO Project or update existing....

WARNING:

If some libraries are not visible in PlatformIO IDE for Atom and Code Completion or Code Linting does not work properly, please perform Menu: PlatformIO > Rebuild C/C++ Project Index (Autocomplete, Linter)


Install Shell Commands

Please navigate to PIO Core Install Shell Commands.

Known issues

Smart Code Linter is disabled by default for Arduino files (*.ino and .pde) because they are not valid C/C++ based source files:

1.
Missing includes such as #include <Arduino.h>
2.
Function declarations are omitted.

There are two solutions:

  • Convert Arduino file to C++ manually
  • Force Arduino file as C++

Convert Arduino file to C++ manually

Recommended! See Convert Arduino file to C++ manually.

To force Smart Code Linter to use Arduino files as C++ please

1.
Open .gcc-flags.json file from the Initialized/Imported project and add -x c++ flag at the beginning of the value of gccDefaultCppFlags field:

{
  "execPath": "...",
  "gccDefaultCFlags": "...",
  "gccDefaultCppFlags": "-x c++ -fsyntax-only ...",
  "gccErrorLimit": 15,
  "gccIncludePaths": "...",
  "gccSuppressWarnings": false
}


2.
Perform all steps from Convert Arduino file to C++ manually (without renaming to .cpp).

WARNING:

Please do not modify other flags here. They will be removed on a next "Project Rebuild C/C++ Index" stage. Please use build_flags for "platformio.ini" (Project Configuration File) instead.


Please read this article Installing PlatformIO on Arch Linux.

Frequently Asked Questions

PlatformIO IDE hides build panel on success by default. Nevertheless, you can keep it visible all time. Please follow to Menu: PlatformIO > Settings > Build and set Panel Visibility to Keep Visible.

Key-bindings (toggle panel):

  • cmd+alt+v - Mac OS X
  • ctrl+alt+v - Windows/Linux

If you want automatically save all edited files when triggering a build, please follow to Menu: PlatformIO > Settings > Build and check Automatically save on build.

Click on a function/include, press F3 and you will be taken directly to the declaration for that function.

You need to install atom-beautify package and C/C++ Uncrustify Code Beautifier.

Here's how to uninstall the PlatformIO IDE for multiple OS.

See Uninstall PIO Core and dependent packages, if you do not need it in a system.

1.
Uninstall Atom using "Start > Control Panel > Programs and Features > Uninstall"
2.
Remove C:\Users\<user name>\.atom folder (settings, packages, etc...)
3.
Remove C:\Users\<user name>\AppData\Local\atom folder (application itself)
4.
Remove C:\Users\<user name>\AppData\Roaming\Atom folder (cache, etc.)
5.
Remove registry records using regedit:
  • HKEY_CLASSES_ROOT\Directory\Background\shell
  • HKEY_CLASSES_ROOT\Directory\shell
  • HKEY_CLASSES_ROOT*\shell


Run these commands in system Terminal

rm -rf ~/.atom
rm /usr/local/bin/atom
rm /usr/local/bin/apm
rm -rf /Applications/Atom.app
rm ~/Library/Preferences/com.github.atom.plist
rm ~/Library/Application\ Support/com.github.atom.ShipIt
rm -rf ~/Library/Application\ Support/Atom
rm -rf ~/Library/Saved\ Application\ State/com.github.atom.savedState
rm -rf ~/Library/Caches/com.github.atom
rm -rf ~/Library/Caches/Atom


Run these commands in system Terminal

rm /usr/local/bin/atom
rm /usr/local/bin/apm
rm -rf ~/atom
rm -rf ~/.atom
rm -rf ~/.config/Atom-Shell
rm -rf /usr/local/share/atom/


Articles / Manuals

  • Mar, 31, 2017 - Robin Reiter - A little guide to PlatformIO. As an Arduino developer, you may want to check that out! (video review)
  • Dec 13, 2016 - Dr. Patrick Mineault - Multi-Arduino projects with PlatformIO
  • Nov 10, 2016 - PiGreek - PlatformIO the new Arduino IDE ?!
  • Aug 18, 2016 - Primal Cortex - Installing PlatformIO on Arch Linux
  • Jul 26, 2016 - Embedded Systems Laboratory - แนะนำการใช้งาน PlatformIO IDE สำหรับบอร์ด Arduino และ ESP8266 (Get started with PlatformIO IDE for Arduino board and ESP8266, Thai)
  • May 30, 2016 - Ron Moerman - IoT Development with PlatformIO
  • May 01, 2016 - Pedro Minatel - PlatformIO – Uma alternativa ao Arduino IDE (PlatformIO - An alternative to the Arduino IDE, Portuguese)
  • Apr 23, 2016 - Al Williams - Hackaday: Atomic Arduino (and Other) Development
  • Apr 16, 2016 - Sathittham Sangthong - [PlatformIO] มาลองเล่น PlatformIO แทน Arduino IDE กัน (Let's play together with PlatformIO IDE [alternative to Arduino IDE], Thai)
  • Apr 11, 2016 - Matjaz Trcek - Top 5 Arduino integrated development environments
  • Apr 06, 2016 - Aleks - PlatformIO ausprobiert (Tried PlatformIO, German)
  • Apr 02, 2016 - Diego Pinto - Você tem coragem de abandonar a IDE do Arduino? PlatformIO + Atom (Do you dare to leave the Arduino IDE? PlatformIO + Atom, Portuguese)
  • Mar 30, 2016 - Brandon Cannaday - Getting Started with PlatformIO and ESP8266 NodeMcu
  • Mar 12, 2016 - Peter Marks - PlatformIO, the Arduino IDE for programmers
  • Mar 05, 2016 - brichacek.net - PlatformIO – otevřený ekosystém pro vývoj IoT (PlatformIO – an open source ecosystem for IoT development, Czech)
  • Mar 04, 2016 - Ricardo Vega - Programa tu Arduino desde Atom (Program your Arduino from Atom, Spanish)
  • Feb 28, 2016 - Alex Bloggt - PlatformIO vorgestellt (Introduction to PlatformIO IDE, German)
  • Feb 25, 2016 - NutDIY - PlatformIO Blink On Nodemcu Dev Kit V1.0 (Thai)

See a full list with Articles about us.

Please visit releases page.

The CLion is a cross-platform C/C++ IDE for Linux, OS X, and Windows. CLion includes such features as a smart editor, code generation, code quality assurance, automated refactorings, on-the-fly code analysis, project manager, integrated version control systems and debugger.

Refer to the CLion Documentation page for more detailed information. [image]

  • Installation
  • Known issues
  • Project configuration and CMake
  • CLion does not load project build environments from "platformio.ini"
  • Arduino .ino files are not supported

•
Quick Start
  • Setting Up the Project
  • Build & Upload
•
Configuration options


  • Device/Serial Monitor
  • Debugging
•
Peripheral Registers

•
PlatformIO Home

1.
Install PlatformIO Core (CLI). See Installation guide

WARNING:

This a temporary step and depends on CLion #CPP-19412: Automatically install PlatformIO Core


2.
Download and install CLion IDE
3.
Install official PlatformIO for CLion plugin. Open "Configure > Plugins" window and go to the "Marketplace" tab. Search for PlatformIO and press the "Install" button. [image]
4.
Restart CLion IDE.

NOTE:

We also recommend to install Ini plugin that provides syntax highlighting, formatting, code folding, and viewing structure for "platformio.ini" (Project Configuration File).


Known issues

PlatformIO does not depend on "CMake" and uses own multi-platform build system. Project configuration, such as build flags, library dependencies, etc., should be declared in "platformio.ini" (Project Configuration File).

WARNING:

Please note that "PlatformIO for CLion" plugin does not update automatically CLion configuration. There is a feature request CLion #CPP-18367: Follow platformio.ini changes and update the project.


Update CLion configuration: "Tools > PlatformIO > Re-Init"

This is a known issue CLion CPP-19478: CLion does not handle "CMAKE_CONFIGURATION_TYPES" from CMakeLists.txt. A temporary solution is to manually configure project profiles in CLion.

Please open CLion Settings and navigate to "Build, Execution, Deployment > CMake". Press "+" button and PlatformIO-based project profiles: [image]

CLion uses "CMake" tool for code completion and code linting. As a result, it doesn't support the Arduino files (*.ino and .pde) because they are not valid C/C++ based source files:

1.
Missing includes such as #include <Arduino.h>
2.
Function declarations are omitted.

See how to Convert Arduino file to C++ manually.

Quick Start

This tutorial introduces you to the basics of PlatformIO for CLion workflow and shows you a creation process of a simple "Blink" example. After finishing you will have a general understanding of how to work with projects in the CLion IDE.

Setting Up the Project

1.
Please open "New Project" wizard, select board and framework, and create a new PlatformIO project. Please USE ONLY Latin characters (a-z) in a project name to avoid further issues with project compilation. Numbers and some symbols are allowed depending on a file system:

[image]

2.
Rename main.c file in src folder to main.cpp (right click on a file main.c, Refactor > Rename...) . Paste the next contents:

WARNING:

The code below works only in pair with Arduino-based boards. Please follow to PlatformIO Project Examples repository for other pre-configured projects.


/**
 * Blink
 *
 * Turns on an LED on for one second,
 * then off for one second, repeatedly.
 */
#include "Arduino.h"
// Set LED_BUILTIN if it is not defined by Arduino framework
// #define LED_BUILTIN 13
void setup()
{
  // initialize LED digital pin as an output.
  pinMode(LED_BUILTIN, OUTPUT);
}
void loop()
{
  // turn the LED on (HIGH is the voltage level)
  digitalWrite(LED_BUILTIN, HIGH);
  // wait for a second
  delay(1000);
  // turn the LED off by making the voltage LOW
  digitalWrite(LED_BUILTIN, LOW);
   // wait for a second
  delay(1000);
}


[image]

1.
Open project configuration wizard and add PlatformIO Upload and PlatformIO Debug configurations (you can add the rest configurations if you need them):

[image]

2.
Remove pre-task ("Build") from PlatformIO Upload and PlatformIO Debug configurations to avoid double project building. You should see "There are no tasks to run before launch".

[image]
3.
Select PlatformIO Upload configuration and use the "Build" button for project compilation or the "Run" for a firmware uploading:

[image]

  • Build options
  • Upload options

Please open CLion terminal and use Device Manager CLI. You can also configure device monitor per project using Monitor options.

Please note that you need to manually close/stop device monitor before firmware uploading.

"PlatformIO for CLion" supports PIO Unified Debugger which allows you to debug your application with 1-Click without extra steps. Please select PlatformIO Debug configuration and press the "Debug" button: [image]

Please navigate to the "Peripheral" tab in a "Debug" view, press the "Configure" icon and select registers to monitor. Close configuration window.

WARNING:

Currently, CLion does not load automatically Peripheral Register Definitions (SVD file) provided by PlatformIO. There is a feature request CLion #CPP-18369: Support CLION_SVD_FILE_PATH CMake variable to auto-find svd file.

A temporary solution is to open CMakeListsPrivate.txt file from a root of PlatformIO project and remember SVD file declared in CLION_SVD_FILE_PATH "CMake" variable. Now press the "+" button in Peripherals Wizard and select SVD file mentioned in CLION_SVD_FILE_PATH.



[image]

PlatformIO Home

Currently, PlatformIO Home is not integrated into "PlatformIO for CLion". See related feature request CLion: CPP-19493 Integrate PlatformIO Home.

Nevertheless, you can start it manually and open in your browser. Please note that some features do not work, such as project opening. Please open CLion terminal and run platformio home command:

platformio -c clion home


[image]


----



Further for reading:

  • Tutorials and Examples (step-by-step tutorials with debugging and unit testing)
  • CLion documentation.

Happy coding with PlatformIO!

Code::Blocks is a free, open-source cross-platform IDE that supports multiple compilers including GCC, Clang and Visual C++. It is developed in C++ using wxWidgets as the GUI toolkit. Using a plugin architecture, its capabilities and features are defined by the provided plugins. Currently, Code::Blocks is oriented towards C, C++, and Fortran.

CodeBlocks IDE can be downloaded from here. .SS Contents

•
CodeBlocks
•
Integration


Integration process consists of these steps:

1.
Open system Terminal and install PlatformIO Core (CLI)
2.
Create new folder for your project and change directory (cd) to it
3.
Generate a project using PIO Core Project Generator (platformio project init --ide)
4.
Import project in IDE.


----



Choose board ID using platformio boards or Embedded Boards Explorer command and generate project via platformio project init --ide command:

platformio project init --ide codeblocks --board <ID>
# For example, generate project for Arduino UNO
platformio project init --ide codeblocks --board uno


Then:

1.
Open this project via Menu: File > Open...
2.
Add new files to src directory (*.c, *.cpp, *.ino, etc.) via Menu: File > New > File...
3.
Build project using Menu: Build > Build
4.
Upload firmware using Menu: Build > Run

WARNING:

The libraries which are added, installed or used in the project after generating process won't be reflected in IDE. To fix it you need to reinitialize project using platformio project init (repeat it).


The Eclipse CDT (C/C++ Development Tooling) Project provides a fully functional C and C++ Integrated Development Environment based on the Eclipse platform. Features include: support for project creation and managed build for various toolchains, standard make build, source navigation, various source knowledge tools, such as type hierarchy, call graph, include browser, macro definition browser, code editor with syntax highlighting, folding and hyperlink navigation, source code refactoring and code generation, visual debugging tools, including memory, registers, and disassembly viewers.

Refer to the CDT Documentation page for more detailed information. .SS Contents

  • Integration
  • Live Integration
  • Debugging
  • Articles / Manuals

Integration process consists of these steps:

1.
Open system Terminal and install PlatformIO Core (CLI)
2.
Create new folder for your project and change directory (cd) to it
3.
Generate a project using PIO Core Project Generator (platformio project init --ide)
4.
Import project in IDE.


----



Choose board ID using platformio boards or Embedded Boards Explorer command and generate project via platformio project init --ide command:

platformio project init --ide eclipse --board <ID>
# For example, generate project for Arduino UNO
platformio project init --ide eclipse --board uno


Then:

1.
Import this project via Menu: File > Import... > General > Existing Projects into Workspace > Next and specify root directory where is located "platformio.ini" (Project Configuration File)
2.
Open source file from src directory (*.c, *.cpp, *.ino, etc.)
3.
Build project using Menu: Project > Build Project or pre-configured Make Targets (see screenshot below):
  • PlatformIO: Build - Build project without auto-uploading
  • PlatformIO: Clean - Clean compiled objects.
  • PlatformIO: Test - PIO Unit Testing
  • PlatformIO: Upload - Build and upload (if no errors)
  • PlatformIO: Upload using Programmer see Upload using Programmer
  • PlatformIO: Upload SPIFFS image see Uploading files to file system SPIFFS
  • PlatformIO: Update platforms and libraries - Update installed platforms and libraries via platformio update
  • PlatformIO: Rebuild C/C++ Project Index - Rebuild C/C++ Index for the Project. Allows one to fix code completion and code linting issues.


If you have some problems with unresolved includes, defines, etc., then

1.
Rebuild PlatformIO Project Index: PlatformIO: Rebuild C/C++ Project Index target
2.
Rebuild Eclipse Project Index: Menu: Project > C/C++ Index > Rebuild
3.
Refresh Project, right click on the project Project > Refresh (F5) or restart Eclipse IDE.

WARNING:

The libraries which are added, installed or used in the project after generating process won't be reflected in IDE. To fix it please run PlatformIO: Rebuild C/C++ Project Index target and right click on the project and Project > Refresh (F5).


WARNING:

The C/C++ GCC Cross Compiler Support package must be installed in Eclipse, otherwise the CDT Cross GCC Built-in Compiler Settings provider will not be available (check the Providers tab in Project > Properties > C/C++ General > Preprocessor Include Paths, Macros etc. for a marked entry named CDT Cross GCC Built-in Compiler Settings).

If this provider is not available, toolchain related includes cannot be resolved.



Eclipse Virtual IoT Meetup: PlatformIO: a cross-platform IoT solution to build them all! .SS Debugging

A debugging feature is provided by PIO Unified Debugger and new debug configuration named "PlatformIO Debugger" is created. No need to do extra configuration steps!

1.
Build a project first time or after "Clean" operation using PlatformIO: Build target
2.
Launch debugger via "Menu: Debug" or "Bug Icon" button on Tool Bar.
3.
Wait for a while, PlatformIO will prepare project for debugging and session will be started soon.

Articles / Manuals

  • May 05, 2016 - Ivan Kravets, Ph.D. / Eclipse Virtual IoT Meetup - PlatformIO: a cross-platform IoT solution to build them all!
  • Sep 01, 2015 - Thomas P. Weldon, Ph.D. - Improvised MBED FRDM-K64F Eclipse/PlatformIO Setup and Software Installation
  • Jul 11, 2015 - TrojanC - Learning Arduino GitHub Repository
  • June 20, 2014 - Ivan Kravets, Ph.D. - Building and debugging Atmel AVR (Arduino-based) project using Eclipse IDE+PlatformIO

See a full list with Articles about us.

GNU Emacs is an extensible, customizable text editor - and more. At its core is an interpreter for Emacs Lisp, a dialect of the Lisp programming language with extensions to support text editing.

Refer to the Emacs Documentation page for more detailed information. .SS Contents

•
Emacs
•
Integration
  • PlatformIO-Mode
  • Project Generator



Integration process consists of these steps:

1.
Open system Terminal and install PlatformIO Core (CLI)
2.
Create new folder for your project and change directory (cd) to it
3.
Generate a project using PIO Core Project Generator (platformio project init --ide)
4.
Import project in IDE.


----



An Emacs minor mode has been written to facilitate building and uploading from within Emacs. It can be installed from the MELPA repository using M-x package-install. See the MELPA Getting Started page for more information.

Setup instructions and an example config can be found at the Github page.

Code completion can optionally be provided by installing irony-mode

Project Generator

Choose board ID using platformio boards or Embedded Boards Explorer command and generate project via platformio project init --ide command:

platformio project init --ide emacs --board <ID>


There are 6 predefined targets for building.

  • platformio_build - Build project without auto-uploading. (C-c i b)
  • platformio_clean - Clean compiled objects. (C-c i c)
  • platformio_upload - Build and upload (if no errors). (C-c i u)
  • platformio_programmer_upload - Build and upload using external programmer (if no errors, see Upload using Programmer). (C-c i p)
  • platformio_spiffs_upload - Upload files to file system SPIFFS (see Uploading files to file system SPIFFS). (C-c i s)
  • platformio_update - Update installed platforms and libraries. (C-c i d)

WARNING:

The libraries which are added, installed or used in the project after generating process won't be reflected in IDE. To fix it you need to reinitialize project using platformio project init (repeat it).


NetBeans is a Java-based integrated development environment (IDE). It provides out-of-the-box code analyzers and editors for working with the latest Java 8 technologies--Java SE 8, Java SE Embedded 8, and Java ME Embedded 8. The IDE also has a range of new tools for HTML5/JavaScript, in particular for Node.js, KnockoutJS, and AngularJS; enhancements that further improve its support for Maven and Java EE with PrimeFaces; and improvements to PHP and C/C++ support.

NetBeans IDE can be downloaded from here. Just make sure you download the C/C++ version (or if you already use NetBeans, install the C/C++ development plugins).

WARNING:

Note that the version of NetBeans IDE provided by some Linux package repositories may be a Flatpak version, which are known to have issues with accessing the PlatformIO CLI installed due to the container nature of this technology. It is recommended that you use the native version of the NetBeans IDE via the above link.


.SS Contents
•
NetBeans
  • Integration
  • Articles / Manuals


Integration process consists of these steps:

1.
Open system Terminal and install PlatformIO Core (CLI)
2.
Create new folder for your project and change directory (cd) to it
3.
Generate a project using PIO Core Project Generator (platformio project init --ide)
4.
Import project in IDE.


----



Choose board ID using platformio boards or Embedded Boards Explorer command and generate project via platformio project init --ide command:

platformio project init --ide netbeans --board <ID>
# For example, generate project for Arduino UNO
platformio project init --ide netbeans --board uno


Then:

1.
Open this project via Menu: File > Open Project...
2.
Add new files to src directory (*.c, *.cpp, *.ino, etc.) via right-click on src folder in the "Projects" pane
3.
Build project using Menu: Run > Build Project
4.
Upload firmware using Menu: Run > Run Project

WARNING:

The libraries which are added, installed or used in the project after generating process won't be reflected in IDE. To fix it you need to reinitialize project using platformio project init (repeat it).


Articles / Manuals

•
Feb 22, 2016 - Grzegorz Hołdys - How to Integrate PlatformIO with Netbeans

See the full list with Articles about us.

The Qt Creator is an open source cross-platform integrated development environment. The editor includes such features as syntax highlighting for various languages, project manager, integrated version control systems, rapid code navigation tools and code autocompletion.

Refer to the Qt-creator Manual page for more detailed information. .SS Contents

•
Qt Creator
•
Integration
  • Project Generator
  • Manual Integration
  • Setup New Project
  • First program in Qt Creator
  • Conclusion




Integration process consists of these steps:

1.
Open system Terminal and install PlatformIO Core (CLI)
2.
Create new folder for your project and change directory (cd) to it
3.
Generate a project using PIO Core Project Generator (platformio project init --ide)
4.
Import project in IDE.

Project Generator

Choose board ID using platformio boards or Embedded Boards Explorer command and generate project via platformio project init --ide command:

platformio project init --ide qtcreator --board <ID>
# For example, generate project for Arduino UNO
platformio project init --ide qtcreator --board uno


Then:

1.
Import project via File > Open File or Project and select platformio.pro from the folder where is located "platformio.ini" (Project Configuration File)
2.
Select default desktop kit and click on Configure Project (Projects mode, left panel)
3.
Set General > Build directory to the project directory where is located "platformio.ini" (Project Configuration File)
4.
Remove all items from Build Steps, click on Build Steps > Add Build Step > Custom Process Step and set:
  • Command: platformio
  • Arguments: -f -c qtcreator run
  • Working directory: %{buildDir}

5.
Remove all items from Clean Steps, click on Clean Steps > Add Clean Step > Custom Process Step and set:
  • Command: platformio
  • Arguments: -f -c qtcreator run --target clean
  • Working directory: %{buildDir}

6.
Update PATH in Build Environment > PATH > EDIT with the result of this command (paste in Terminal):

# Linux, Mac
echo $PATH
# Windows
echo %PATH%


7.
Switch to Edit mode (left panel) and open source file from src directory (*.c, *.cpp, *.ino, etc.)
8.
Build project: Menu: Build > Build All.

.sp WARNING:
The libraries which are added, installed or used in the project after generating process won't be reflected in IDE. To fix it you need to reinitialize project using platformio project init (repeat it).


Manual Integration

Setup New Project

First of all, let's create new project from Qt Creator Start Page: New Project or using Menu: File > New File or Project, then select project with Empty Qt Project type (Other Project > Empty Qt Project), fill Name, Create in.

On the next steps select any available kit and click Finish button. [image]

Secondly, we need to delete default build and clean steps and configure project with PlatformIO Build System (click on Projects label on left menu or Ctrl+5 shortcut):

Thirdly, change project file by adding path to directories with header files. Please edit project file to match the following contents:

win32 {
    HOMEDIR += $$(USERPROFILE)
}
else {
    HOMEDIR += $$(HOME)
}
INCLUDEPATH += "$${HOMEDIR}/.platformio/packages/framework-arduinoavr/cores/arduino"
INCLUDEPATH += "$${HOMEDIR}/.platformio/packages/toolchain-atmelavr/avr/include"


.SS First program in Qt Creator

Simple "Blink" project will consist from two files: 1. In the console, navigate to the root of your project folder and initialize platformio project with platformio project init 2. The main "C" source file named main.c must be located in the src directory. Let's create new text file named main.c using Menu: New File or Project > General > Text File:

Copy the source code which is described below to file main.c.

#include "Arduino.h"
#define WLED    13  // Most Arduino boards already have an LED attached to pin 13 on the board itself
void setup()
{
  pinMode(WLED, OUTPUT);  // set pin as output
}
void loop()
{
  digitalWrite(WLED, HIGH);  // set the LED on
  delay(1000);               // wait for a second
  digitalWrite(WLED, LOW);   // set the LED off
  delay(1000);               // wait for a second
}


3.
Locate the project configuration file named platformio.ini at the root of the project directory and open it.

Edit the content to match the code described below.

; PlatformIO Project Configuration File
;
;   Build options: build flags, source filter, extra scripting
;   Upload options: custom port, speed and extra flags
;   Library options: dependencies, extra library storages
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
[env:arduino_uno]
platform = atmelavr
framework = arduino
board = uno


Taking everything into account, we can build project with shortcut Ctrl+Shift+B or using Menu: Build > Build All.

The Sublime Text is a cross-platform text and source code editor, with a Python application programming interface (API). Sublime Text is proprietary software. Its functionality is extendable with plugins. Most of the extending packages have free-software licenses and are community-built and maintained. Sublime Text lacks graphical setting dialogues and is entirely configured by editing text files.

Refer to the Sublime Text Documentation page for more detailed information. .SS Contents

  • Deviot Plugin
  • Integration
  • Project Generator
  • Manual Integration
•
Initial configuration
•
Command Hotkeys

  • First program in Sublime Text
  • Conclusion


•
Debugging

We are glad to inform you about an awesome Sublime Text plugin for IoT development named Deviot. It is based on PlatformIO Core (CLI) and will automatically install it for you. Please visit official Deviot page for the further installation steps and documentation. .SS Integration

Project Generator

Integration process consists of these steps:

1.
Open system Terminal and install PlatformIO Core (CLI)
2.
Create new folder for your project and change directory (cd) to it
3.
Generate a project using PIO Core Project Generator (platformio project init --ide)
4.
Import project in IDE.


----



Choose board ID using platformio boards or Embedded Boards Explorer command and generate project via platformio project init --ide command:

platformio project init --ide sublimetext --board <ID>
# For example, generate project for Arduino UNO
platformio project init --ide sublimetext --board uno


Then:

1.
Import project via Menu: Project > Open Project... and select platformio.sublime-project from the folder where is located "platformio.ini" (Project Configuration File)
2.
Select PlatformIO as build system: Menu: Tools > Build System > PlatformIO
3.
Open source file from src directory (*.c, *.cpp, *.ino, etc.)
4.
Build project: Menu: Tools > Build.

Also, you can access to all pre-configured targets via Menu: Tools > Builds With... (ST3)

  • PlatformIO - Build - Build project without auto-uploading
  • PlatformIO - Clean - Clean compiled objects.
  • PlatformIO - Test - PIO Unit Testing
  • PlatformIO - Upload - Build and upload (if no errors)
  • PlatformIO - Upload using Programmer see Upload using Programmer
  • PlatformIO - Upload SPIFFS image see Uploading files to file system SPIFFS
  • PlatformIO - Update platforms and libraries - Update installed platforms and libraries via platformio update.

Manual Integration

NOTE:

Please verify that folder where is located platformio program is added to PATH (wiki) environment variable.


First of all, we need to create "New Build System" with name "PlatformIO" from Menu: Tools > Build System > New Build System and fill it like described below:

{
    "cmd": ["platformio", "-f", "-c", "sublimetext", "run"],
    "working_dir": "${project_path:${folder}}",
    "variants":
    [
        {
            "name": "Clean",
            "cmd": ["platformio", "-f", "-c", "sublimetext", "run", "--target", "clean"]
        },
        {
            "name": "Upload",
            "cmd": ["platformio", "-f", "-c", "sublimetext", "run", "--target", "upload"]
        }
    ]
}


Secondly, we need to select "PlatformIO" Build System from a list: [image]

After that, we can use the necessary commands from Menu: Tools > Command Palette or with Ctrl+Shift+P (Windows/Linux) Cmd+Shift+P (Mac) shortcut. [image]

Sublime Text allows one to bind own hotkey per command. Let's setup them for PlatformIO commands using shortcut Menu: Preferences > Key-Bindings - User: [image]

We are going to use these shortcuts:

  • F11 for clean project
  • F12 for upload firmware to target device

In this case, the final code will look like:

[
    { "keys": ["f11"], "command": "build", "args": {"variant": "Clean"} },
    { "keys": ["f12"], "command": "build", "args": {"variant": "Upload"} }
]


Simple "Blink" project will consist from two files:

1. Main "C" source file named main.c must be located in the src directory. Let's create new file named main.c using Menu: File > New File or shortcut Ctrl+N (Windows/Linux) Cmd+N (Mac) with the next contents:

#include "Arduino.h"
#define WLED    13  // Most Arduino boards already have an LED attached to pin 13 on the board itself
void setup()
{
  pinMode(WLED, OUTPUT);  // set pin as output
}
void loop()
{
  digitalWrite(WLED, HIGH);  // set the LED on
  delay(1000);               // wait for a second
  digitalWrite(WLED, LOW);   // set the LED off
  delay(1000);               // wait for a second
}


2. Project Configuration File named platformio.ini must be located in the project root directory. Copy the source code which is described below to it.

; PlatformIO Project Configuration File
;
;   Build options: build flags, source filter, extra scripting
;   Upload options: custom port, speed and extra flags
;   Library options: dependencies, extra library storages
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
[env:arduino_uno]
platform = atmelavr
framework = arduino
board = uno


Taking everything into account, we can open project directory in Sublime Text using Menu: File > Open Folder and build it with shortcut Ctrl+B (Windows/Linux) or Cmd+B (Mac), clean project with shortcut F11 and upload firmware to target with shortcut F12.

A debugging feature is provided by PIO Unified Debugger and new debug configuration named "PlatformIO Debugger" is created. No need to do extra configuration steps!

1.
Install SublimeGDB package
2.
Launch debugger with F5
3.
Wait for a while, PlatformIO will prepare project for debugging and session will be started soon.

Vim is an open-source, powerful and configurable text editor. Vim is designed for use both from a command-line interface and as a standalone application in a graphical user interface. [image]

•
Vim
•
Integration
  • "Neomake-PlatformIO" Plugin
  • Project Generator

•
Articles / Manuals


Integration process consists of these steps:

1.
Open system Terminal and install PlatformIO Core (CLI)
2.
Create new folder for your project and change directory (cd) to it
3.
Generate a project using PIO Core Project Generator (platformio project init --ide)
4.
Import project in IDE.

Please visit neomake-platformio for the further installation steps and documentation.

Project Generator

Choose board ID using platformio boards or Embedded Boards Explorer command and generate project via platformio project init --ide command:

platformio project init --ide vim --board <ID>


Recommended bundles:

  • C/C++/ language server supporting cross references, hierarchies, completion and semantic highlighting - CCLS: vim lsp
  • Syntax highlight - Arduino-syntax-file
  • Code Completion - YouCompleteMe (see configuration example by Anthony Ford PlatformIO/YouCompleteMe Integration)
  • Syntax checking - Syntastic

Put to the project directory Makefile wrapper with contents:

# Uncomment lines below if you have problems with $PATH
#SHELL := /bin/bash
#PATH := /usr/local/bin:$(PATH)
all:
        platformio -f -c vim run
upload:
        platformio -f -c vim run --target upload
clean:
        platformio -f -c vim run --target clean
program:
        platformio -f -c vim run --target program
uploadfs:
        platformio -f -c vim run --target uploadfs
update:
        platformio -f -c vim update


Pre-defined targets:

  • Build - Build project without auto-uploading
  • Clean - Clean compiled objects.
  • Upload - Build and upload (if no errors)
  • Upload using Programmer see Upload using Programmer
  • Upload SPIFFS image see Uploading files to file system SPIFFS
  • Update platforms and libraries - Update installed platforms and libraries via platformio update.

Now, in VIM cd /path/to/this/project and press Ctrl+B or Cmd+B (Mac). PlatformIO should compile your source code from the src directory, make firmware and upload it.

NOTE:

If hotkey doesn't work for you, try to add this line nnoremap <C-b> :make<CR> to ~/.vimrc


Articles / Manuals

•
コマンドラインでArduino開発 : vim + platformio (Arduino development at the command line: VIM + PlatformIO, Japanese)

See a full list with Articles about us.

The Microsoft Visual Studio (Free) is an integrated development environment (IDE) from Microsoft. Visual Studio includes a code editor supporting IntelliSense (the code completion component) as well as code refactoring.

Refer to the Visual Studio Documentation page for more detailed information. .SS Contents

•
Visual Studio
•
Integration
  • Project Generator
  • Manual Integration
  • Setup New Project
  • First program in Visual Studio
  • Conclusion


•
Known issues
•
IntelliSense Errors



Integration process consists of these steps:

1.
Open system Terminal and install PlatformIO Core (CLI)
2.
Create new folder for your project and change directory (cd) to it
3.
Generate a project using PIO Core Project Generator (platformio project init --ide)
4.
Import project in IDE.


----



Project Generator

Choose board ID using platformio boards or Embedded Boards Explorer command and generate project via platformio project init --ide command:

platformio project init --ide visualstudio --board <ID>
# For example, generate project for Arduino UNO
platformio project init --ide visualstudio --board uno


Then:

1.
Import this project via Menu: File > Open > Project/Solution and specify root directory where is located "platformio.ini" (Project Configuration File)
2.
Open source file from src directory (*.c, *.cpp, *.ino, etc.)
3.
Build project: Menu: Build > Build Solution.

WARNING:

The libraries which are added, installed or used in the project after generating process won't be reflected in IDE. To fix it you need to reinitialize project using platformio project init (repeat it).


Manual Integration

Setup New Project

First of all, let's create new project from Visual Studio Start Page: Start > New Project or using Menu: File > New > Project, then select project with Makefile type (Visual C++ > General > Makefile Project), fill Project name, Solution name, Location fields and press OK button. [image]

Secondly, we need to configure project with PlatformIO Build System: [image]

If we want to use native AVR programming, we have to specify additional preprocessor symbol ("Preprocessor definitions" field) about your MCU. For example, an Arduino Uno is based on the ATmega328 MCU. In this case We will add new definition __AVR_ATmega328__. [image]

Release Configuration is the same as Debug, so on the next step we check "Same as Debug Configuration" and click "Finish" button. [image]

Thirdly, we need to add directories with header files using project properties (right click on the project name or Alt-Enter shortcut) and add two directories to Configuration Properties > NMake > Include Search Path:

$(HOMEDRIVE)$(HOMEPATH)\.platformio\packages\toolchain-atmelavr\avr\include
$(HOMEDRIVE)$(HOMEPATH)\.platformio\packages\framework-arduinoavr\cores\arduino


[image]

Simple "Blink" project will consist from two files:

1. Main "C++" source file named main.cpp must be located in the src directory. Let's create new file named main.cpp using Menu: File > New File or shortcut Ctrl+N: [image]

Copy the source code which is described below to file main.cpp.

#include "Arduino.h"
void setup()
{
  pinMode(LED_BUILTIN, OUTPUT);  // set pin as output
}
void loop()
{
  digitalWrite(LED_BUILTIN, HIGH);  // set the LED on
  delay(1000);               // wait for a second
  digitalWrite(LED_BUILTIN, LOW);   // set the LED off
  delay(1000);               // wait for a second
}


2.
Project Configuration File named platformio.ini must be located in the project root directory.

[image]

Copy the source code which is described below to it.

; PlatformIO Project Configuration File
;
;   Build options: build flags, source filter, extra scripting
;   Upload options: custom port, speed and extra flags
;   Library options: dependencies, extra library storages
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
[env:arduino_uno]
platform = atmelavr
framework = arduino
board = uno


Taking everything into account, we can build project with shortcut Ctrl+Shift+B or using Menu: Build > Build Solution.

Known issues

VS Studio does not allow one to specify for project other toolchain which will be used by IntelliSense. In this case, IntelliSense does not understand GCC-specific definitions.

However, these errors does not have any influence on PlatformIO Build System. It means that you can ignore them and rely on PlatformIO Build System messages which will be shown in output console after build.

Nevertheless, you can provide an IntelliSense-friendly definition of problematic GCC constructs and make sure that the GCC will ignore such definitions or disable IntelliSense error reporting at all. See details in issue #543 .SS VSCode

PlatformIO IDE is the next-generation integrated development environment for IoT.

•
Cross-platform build system without external dependencies to the OS software:
  • 800+ Boards
  • 35+ Development Platforms
  • 20+ Frameworks



  • PIO Unified Debugger
  • PIO Remote
  • PIO Unit Testing
  • C/C++ Intelligent Code Completion
  • C/C++ Smart Code Linter for rapid professional development
  • Library Manager for the hundreds popular libraries
  • Multi-projects workflow with multiple panes
  • Themes support with dark and light colors
  • Serial Port Monitor
  • Built-in Terminal with PlatformIO Core (CLI) and CLI tool (pio, platformio)
  • Built-in PlatformIO Home.


----



Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. It comes with built-in support for JavaScript, TypeScript and Node.js and has a rich ecosystem of extensions for other languages (such as C++, C#, Python, PHP, Go) and runtimes (such as .NET and Unity) .SS Contents

  • Installation
  • Quick Start
•
Setting Up the Project

•
PlatformIO Toolbar
•
Custom Build Task

  • Key Bindings
  • Project Tasks
  • Task Explorer
  • Task Runner
  • Custom Tasks

  • Multi-project Workspaces
  • Serial Port Monitor
  • Debugging
  • Variable Format
  • Watchpoints

  • Install Shell Commands
  • Proxy Server Support
  • Settings
  • platformio-ide.activateOnlyOnPlatformIOProject
  • platformio-ide.autoCloseSerialMonitor
  • platformio-ide.autoRebuildAutocompleteIndex
  • platformio-ide.buildTask
  • platformio-ide.customPATH
  • platformio-ide.disableToolbar
  • platformio-ide.forceUploadAndMonitor
  • platformio-ide.reopenSerialMonitorDelay
  • platformio-ide.updateTerminalPathConfiguration
  • platformio-ide.useBuiltinPIOCore
  • platformio-ide.useDevelopmentPIOCore
  • platformio-ide.disablePIOHomeStartup
  • platformio-ide.pioHomeServerHttpPort

•
Known issues
•
PackageManager is unable to install tool

•
Changelog

NOTE:

Please note that you do not need to install PlatformIO Core (CLI) separately if you are going to use VSCode. PlatformIO Core (CLI) is built into PlatformIO IDE and you will be able to use it within PlatformIO IDE Terminal.


0.
Download and install official Microsoft Visual Studio Code. PlatformIO IDE is built on top of it
1.
Open VSCode Package Manager
2.
Search for the official platformio ide extension
3.
Install PlatformIO IDE.

[image]

Quick Start

This tutorial introduces you to the basics of PlatformIO IDE workflow and shows you a creation process of a simple "Blink" example. After finishing you will have a general understanding of how to work with projects in the IDE.

Setting Up the Project

1.
Click on "PlatformIO Home" button on the bottom PlatformIO Toolbar

[image]

2.
Click on "New Project", select a board and create new PlatformIO Project

[image]
3.
Open main.cpp file form src folder and replace its contents with the next:

WARNING:

The code below works only in pair with Arduino-based boards. Please follow to PlatformIO Project Examples repository for other pre-configured projects.


/**
 * Blink
 *
 * Turns on an LED on for one second,
 * then off for one second, repeatedly.
 */
#include "Arduino.h"
// Set LED_BUILTIN if it is not defined by Arduino framework
// #define LED_BUILTIN 13
void setup()
{
  // initialize LED digital pin as an output.
  pinMode(LED_BUILTIN, OUTPUT);
}
void loop()
{
  // turn the LED on (HIGH is the voltage level)
  digitalWrite(LED_BUILTIN, HIGH);
  // wait for a second
  delay(1000);
  // turn the LED off by making the voltage LOW
  digitalWrite(LED_BUILTIN, LOW);
   // wait for a second
  delay(1000);
}


[image]
4.
Build your project with ctrl+alt+b hotkey (see all Key Bindings in "User Guide" section below) or using "Build" button on the PlatformIO Toolbar

[image]


----



Further for reading:

  • Tutorials and Examples (step-by-step tutorials with debugging and unit testing)
  • Learn more about PlatformIO Toolbar and other commands (Upload, Clean, Serial Monitor) below.

Happy coding with PlatformIO!

PlatformIO Toolbar

PlatformIO IDE Toolbar is located in VSCode Status Bar (left corner) and contains quick access buttons for the popular commands. Each button contains hint (delay mouse on it). [image]

1.
PlatformIO Home
2.
PlatformIO: Build
3.
PlatformIO: Upload
4.
PIO Remote
5.
PlatformIO: Clean
6.
PIO Unit Testing
7.
Run a task... (See "Task Runner" below)
8.
Serial Port Monitor
9.
PIO Terminal

You can override default "PlatformIO: Build" task for "Build" command which is used by "Build" button in PlatformIO Toolbar and Key Bindings. See platformio-ide.buildTask setting in Settings for more details.

Built-in PlatformIO tasks are available in "Menu > Terminal > Run Task..." list.

  • ctrl+alt+b / cmd-shift-b / ctrl-shift-b Build Project
  • cmd-shift-d / ctrl-shift-d Debug project
  • ctrl+alt+u Upload Firmware
  • ctrl+alt+s Open Serial Port Monitor

You can override existing key bindings or add a new in VSCode. See official documentation Key Bindings for Visual Studio Code.

PlatformIO provides access to "Project Task Explorer" where you can control the build process of the environments declared in "platformio.ini" (Project Configuration File). Project Task Explorer is located in the VSCode Activity Bar under the branded PlatformIO icon. You can also access it via "VSCode Menu > Open View... > PlatformIO". [image]

PlatformIO IDE provides built-in tasks through the menu Terminal > Run Task... (Build, Upload, Clean, Monitor, etc) and custom tasks per "platformio.ini" (Project Configuration File) environment ([env:***]). The default behavior is to use Terminal Panels for presentation, one panel dedicated to each unique task.

The PlatformIO IDE provides its own Problems Matcher named $platformio. You can use it later if you decide to change base task settings.

You can override existing tasks with your own presentation options. For example, let's configure PlatformIO Task Runner to use a NEW Terminal panel for each "Build" command:

1.
The menu item Terminal > Run Task... opens up a list of VSCode tasks for PlatformIO. In the line PlatformIO: Build, press the gear icon on the far right side of the list. This creates or opens the file .vscode/tasks.json with some template code.
2.
Replace the template in tasks.json with this code

{
    "version": "2.0.0",
    "tasks": [
        {
            "type": "PlatformIO",
            "task": "Monitor",
            "problemMatcher": [
                "$platformio"
            ],
            "presentation": {
                "panel": "new"
            }
        }
    ]
}




See more options in the official VSCode documentation.

Custom tasks can be added to tasks.json file located in the .vscode folder in the root of project. Please read the official documentation Tasks in VSCode.

This simple example demonstrates a custom monitor task which echoes input locally. There are a lot of other commands, please read more about PlatformIO Core (CLI) and its commands (CLI Guide).

{
    "version": "2.0.0",
    "tasks": [
        {
            "type": "shell",
            "command": "platformio",
            "args": [
                "device",
                "monitor",
                "--echo"
            ],
            "problemMatcher": [
                "$platformio"
            ],
            "label": "PlatformIO: Monitor (local echo)"
        }
    ]
}


If the platformio executable file is not in your system environment "PATH", you can provide the full path to the binary folder using the options field for the task. For example, if the platformio binary is located in the home folder "~/.platformio/penv/bin":

{
    "version": "2.0.0",
    "tasks": [
        {
            "type": "shell",
            "command": "platformio",
            "args": [
                "device",
                "monitor",
                "--echo"
            ],
            "problemMatcher": [
                "$platformio"
            ],
            "label": "PlatformIO: Monitor (local echo)",
            "options": {
                "env": {"PATH": "${env:HOME}/.platformio/penv/bin"}
            }
        }
    ]
}


Multi-project Workspaces

You can work with multiple project folders in Visual Studio Code with multi-root workspaces. This can be very helpful when you are working on several related projects at the same time. Read more in the documentation Multi-root Workspaces.

You can customize Serial Port Monitor using Monitor options in "platformio.ini" (Project Configuration File):

  • monitor_port
  • monitor_speed
  • monitor_rts
  • monitor_dtr
  • monitor_flags

Example:

[env:esp32dev]
platform = espressif32
framework = arduino
board = esp32dev
; Custom Serial Monitor port
monitor_port = /dev/ttyUSB1
; Custom Serial Monitor speed (baud rate)
monitor_speed = 115200


Debugging in VSCode works in combination with PIO Unified Debugger. You should have PIO Account to work with it.

VSCode has a separate activity view named "Debug" (accessed by the bug icon on the left toolbar). PIO Unified Debugger extends it with more advanced debugging instruments and features:

  • Local, Global, and Static Variable Explorer
  • Conditional Breakpoints
  • Expressions and Watchpoints
  • Generic Registers
  • Peripheral Registers
  • Memory Viewer
  • Disassembly
  • Multi-thread support
  • A hot restart of an active debugging session.

There are two pre-configured debugging configurations:

Default configuration. PlatformIO runs the Pre-Debug task and builds the project using Debug Configuration. Also, it checks for project changes.
PlatformIO skips the Pre-Debug stage and DOES NOT build or check the project for changes. If you do changes in project source files, they will not be reflected in debug sessions until you switch back to the "PIO Debug" configuration or manually run the "Pre-Debug" task.

This configuration is very useful for quick debug session. It is super fast by skipping several checks, letting you control project changes manually.


NOTE:

Please note that PIO Unified Debugger will use the first declared build environment in "platformio.ini" (Project Configuration File) if the default_envs option is not specified.


[image]

Currently, VSCode does not provide an UI or API to change the variable format. See the related VSCode Issue #28025.

A temporary solution is to set the default numerical base in which the debugger displays numeric output in the Debug Console. (The Debug Console is visible during active debugging sessions). For example, to show variables in hexadecimal format, copy the code below and paste it into "Debug Console":

set output-radix 16


Possible values, listed in decimal base, are: 8, 10, 16.

Please read GDB: Setting Watchpoints first.

Currently, VSCode does not provide an API to change the value format of watchpoints. You can manually cast watchpoint expressions to display the value as specific pointer types:

  • $pc, default decimal integer format
  • *0x10012000, an address, default decimal integer format
  • (void*)$pc, $pc register, hexadecimal format
  • *(void**)0x10012000, an address, hexadecimal format

Install Shell Commands

Please refer to PIO Core Install Shell Commands.

There are two options how to configure a proxy server:

1.
Declare the HTTP_PROXY and HTTPS_PROXY system environment variables (for example HTTP_PROXY=http://user:pass@10.10.1.10:3128/, etc.)
2.
Open VSCode Settings and search for "Proxy". Please set "Http: Proxy" and disable "Http: Proxy Strict SSL".

How to configure VSCode settings?

platformio-ide.activateOnlyOnPlatformIOProject

If true, activate the platformio ide extension only when a PlatformIO-based project (that has a "platformio.ini" (Project Configuration File)) is open in the workspace. The default value is false.

platformio-ide.autoCloseSerialMonitor

If true, automatically close platformio device monitor before uploading/testing. The default value is true.

platformio-ide.autoRebuildAutocompleteIndex

If true, automatically rebuild the C/C++ Project Index when "platformio.ini" (Project Configuration File) is changed or when new libraries are installed. The default value is true.

platformio-ide.buildTask

The build task (label) that is launched by the "Build" button in the PlatformIO Toolbar and Key Bindings. The default is PlatformIO: Build.

You can create custom Custom Tasks and assign one of them to platformio-ide.buildTask.

platformio-ide.customPATH

Custom PATH for the platformio command. Paste here the result of echo $PATH (Unix) / echo %PATH% (Windows) command by typing into your system terminal if you prefer to use a custom version of PlatformIO Core (CLI). The default value is null, meaning PlatformIO looks for the platformio command in the system path.

platformio-ide.disableToolbar

Disable the PlatformIO toolbar. The default value is false.

platformio-ide.forceUploadAndMonitor

If true, the Upload (platformio-ide.upload) command is changed to use the "Upload and Monitor" task. The default value is false.

platformio-ide.reopenSerialMonitorDelay

Configure the time in milliseconds before reopening the Serial Port Monitor. The default value is 0, which means to reopen instantly.

platformio-ide.updateTerminalPathConfiguration

If true, use a patched PATH environment for the Terminal configuration. The default value is true.

platformio-ide.useBuiltinPIOCore

If true, use the built-in PlatformIO Core (CLI). The default value is true.

platformio-ide.useDevelopmentPIOCore

If true, use the development version of PlatformIO Core (CLI). The default value is false.

platformio-ide.disablePIOHomeStartup

Disable showing PIO Home at startup. The default value is false.

platformio-ide.pioHomeServerHttpPort

PIO Home server HTTP port. The default value 0 automatically assigns a free port in the range [8010..8100]).

Known issues

This is a known bug in VSCode Terminal issue #61.

A temporary solution is to install packages using a system terminal (not VSCode Terminal). Please use "Solution 3: Run from Terminal" in FAQ > Package Manager > [Error 5] Access is denied. Afterwards, go back to using the VSCode Terminal.

Please visit the releases page.

Continuous Integration (CI, wiki) is the practice, in software engineering, of merging all developer working copies with a shared mainline several times a day.

platformio ci command is intended to be used in combination with the build servers and the popular Continuous Integration Software.

By integrating regularly, you can detect errors quickly, and locate them more easily.

AppVeyor is an open-source hosted, distributed continuous integration service used to build and test projects hosted at GitHub on Windows family systems.

AppVeyor is configured by adding a file named appveyor.yml, which is a YAML format text file, to the root directory of the GitHub repository.

AppVeyor automatically detects when a commit has been made and pushed to a repository that is using AppVeyor, and each time this happens, it will try to build the project using platformio ci command. This includes commits to all branches, not just to the master branch. AppVeyor will also build and run pull requests. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the build results (showing success or failure), or by posting a message on an IRC channel. It can be configured to build project on a range of different Development Platforms.

•
AppVeyor
•
Integration
  • Using platformio run command
  • Using platformio ci command

•
Examples


Put appveyor.yml to the root directory of the GitHub repository. The contents of this file depends on the project you want to add. There are two possible ways of running PlatformIO in CI services:

Using platformio run command

This variant is default choice for native PlatformIO projects:

build: off
environment:
install:
    - cmd: git submodule update --init --recursive
    - cmd: SET PATH=%PATH%;C:\Python27\Scripts
    - cmd: pip install -U platformio
test_script:
    - cmd: platformio run /path/to/project/dir -e <ID_1> -e <ID_2> -e <ID_N>


Using platformio ci command

This variant is more convenient when project is written as a library (when there are examples or testing code) as it has additional options for specifying extra libraries and boards from command line interface:

build: off
environment:
  matrix:
    - PLATFORMIO_CI_SRC: "path\\to\\source\\file.c"
    - PLATFORMIO_CI_SRC: "path\\to\\source\\file.ino"
    - PLATFORMIO_CI_SRC: "path\\to\\source\\directory"
install:
    - cmd: git submodule update --init --recursive
    - cmd: SET PATH=%PATH%;C:\Python27\Scripts
    - cmd: pip install -U platformio
test_script:
    - cmd: platformio ci --board=<ID_1> --board=<ID_2> --board=<ID_N>


1.
Integration for USB_Host_Shield_2.0 project. The appveyor.yml configuration file:

build: off
environment:
  matrix:
    - PLATFORMIO_CI_SRC: "examples\\Bluetooth\\PS3SPP\\PS3SPP.ino"
    - PLATFORMIO_CI_SRC: "examples\\pl2303\\pl2303_gps\\pl2303_gps.ino"
install:
    - cmd: git submodule update --init --recursive
    - cmd: SET PATH=%PATH%;C:\Python27\Scripts
    - cmd: pip install -U platformio
    - cmd: git clone https://github.com/xxxajk/spi4teensy3.git C:\spi4teensy
test_script:
    - cmd: platformio ci --lib="." --lib="C:\\spi4teensy" --board=uno --board=teensy31 --board=due


CircleCI is a hosted cloud platform that provides hosted continuous integration, deployment, and testing to GitHub repositories.

CircleCI is configured by adding a file named circle.yml, which is a YAML format text file, to the root directory of the GitHub repository.

CircleCI automatically detects when a commit has been made and pushed to a repository that is using CircleCI, and each time this happens, it will try to build the project using platformio ci command. This includes commits to all branches, not just to the master branch. CircleCI will also build and run pull requests. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the build results (showing success or failure), or by posting a message on an IRC channel. It can be configured to build project on a range of different Development Platforms.

•
CircleCI
•
Integration
  • Using platformio run command
  • Using platformio ci command
•
Library dependencies

  • Install dependent library using Library Manager
  • Manually download dependent library and include in build process via --lib option
  • Custom Build Flags
  • Advanced configuration


•
Examples


NOTE:

Please make sure to read CircleCI Getting Started guide first.


There are two possible ways of running PlatformIO in CI services:

Using platformio run command

This variant is default choice for native PlatformIO projects:

dependencies:
    pre:
        # Install the latest stable PlatformIO
        - sudo pip install -U platformio
test:
    override:
        - platformio run /path/to/project/dir -e <ID_1> -e <ID_2> -e <ID_N>


Using platformio ci command

This variant is more convenient when project is written as a library (when there are examples or testing code) as it has additional options for specifying extra libraries and boards from command line interface:

dependencies:
    pre:
        # Install the latest stable PlatformIO
        - sudo pip install -U platformio
test:
    override:
        - platformio ci path/to/test/file.c --board=<ID_1> --board=<ID_2> --board=<ID_N>
        - platformio ci examples/file.ino --board=<ID_1> --board=<ID_2> --board=<ID_N>
        - platformio ci path/to/test/directory --board=<ID_1> --board=<ID_2> --board=<ID_N>


Library dependencies

There 2 options to test source code with dependent libraries:

Install dependent library using Library Manager

dependencies:
    pre:
        # Install the latest stable PlatformIO
        - sudo pip install -U platformio
        # OneWire Library with ID=1 https://platformio.org/lib/show/1/OneWire
        - platformio lib -g install 1
test:
    override:
        - platformio ci path/to/test/file.c --board=<ID_1> --board=<ID_2> --board=<ID_N>


Manually download dependent library and include in build process via --lib option

dependencies:
    pre:
        # Install the latest stable PlatformIO
        - sudo pip install -U platformio
        # download library to the temporary directory
        - wget https://github.com/PaulStoffregen/OneWire/archive/master.zip -O /tmp/onewire_source.zip
        - unzip /tmp/onewire_source.zip -d /tmp/
test:
    override:
        - platformio ci path/to/test/file.c --lib="/tmp/OneWire-master" --board=<ID_1> --board=<ID_2> --board=<ID_N>


Custom Build Flags

PlatformIO allows one to specify own build flags using PLATFORMIO_BUILD_FLAGS environment

machine:
    environment:
        PLATFORMIO_BUILD_FLAGS: -D SPECIFIC_MACROS -I/extra/inc


For the more details, please follow to available build flags/options.

Advanced configuration

PlatformIO allows one to configure multiple build environments for the single source code using "platformio.ini" (Project Configuration File).

Instead of --board option, please use platformio ci --project-conf

test:
    override:
        - platformio ci path/to/test/file.c --project-conf=/path/to/platoformio.ini


1.
Custom build flags

dependencies:
    cache_directories:
        - "~/.platformio"
    pre:
        - sudo pip install -U platformio
        # pre-install PlatformIO development platforms, they will be cached
        - platformio platform install atmelavr atmelsam teensy
        #
        # Libraries from PlatformIO Library Registry:
        #
        # https://platformio.org/lib/show/416/TinyGPS
        # https://platformio.org/lib/show/417/SPI4Teensy3
        - platformio lib -g install 416 417
test:
    override:
        - platformio ci examples/acm/acm_terminal --board=uno --board=teensy31 --board=due --lib="."
        - platformio ci examples/adk/adk_barcode --board=uno --board=teensy31 --board=due --lib="."
        - platformio ci examples/adk/ArduinoBlinkLED --board=uno --board=teensy31 --board=due --lib="."
        - platformio ci examples/adk/demokit_20 --board=uno --board=teensy31 --board=due --lib="."
        # ...
        - platformio ci examples/Xbox/XBOXUSB --board=uno --board=teensy31 --board=due --lib="."


2.
Dependency on external libraries

dependencies:
    pre:
        # Install the latest stable PlatformIO
        - sudo pip install -U platformio
        # download dependent libraries
        - wget https://github.com/jcw/jeelib/archive/master.zip -O /tmp/jeelib.zip
        - unzip /tmp/jeelib.zip -d /tmp
        - wget https://github.com/Rodot/Gamebuino/archive/master.zip  -O /tmp/gamebuino.zip
        - unzip /tmp/gamebuino.zip -d /tmp
test:
    override:
        -  platformio ci examples/backSoon/backSoon.ino --lib="." --lib="/tmp/jeelib-master" --lib="/tmp/Gamebuino-master/libraries/tinyFAT" --board=uno --board=megaatmega2560
        -  platformio ci examples/etherNode/etherNode.ino --lib="." --lib="/tmp/jeelib-master" --lib="/tmp/Gamebuino-master/libraries/tinyFAT" --board=uno --board=megaatmega2560
        -  platformio ci examples/getDHCPandDNS/getDHCPandDNS.ino --lib="." --lib="/tmp/jeelib-master" --lib="/tmp/Gamebuino-master/libraries/tinyFAT" --board=uno --board=megaatmega2560
        -  platformio ci examples/getStaticIP/getStaticIP.ino --lib="." --lib="/tmp/jeelib-master" --lib="/tmp/Gamebuino-master/libraries/tinyFAT" --board=uno --board=megaatmega2560
        # ...
        -  platformio ci examples/twitter/twitter.ino --lib="." --lib="/tmp/jeelib-master" --lib="/tmp/Gamebuino-master/libraries/tinyFAT" --board=uno --board=megaatmega2560
        -  platformio ci examples/udpClientSendOnly/udpClientSendOnly.ino --lib="." --lib="/tmp/jeelib-master" --lib="/tmp/Gamebuino-master/libraries/tinyFAT" --board=uno --board=megaatmega2560
        -  platformio ci examples/udpListener/udpListener.ino --lib="." --lib="/tmp/jeelib-master" --lib="/tmp/Gamebuino-master/libraries/tinyFAT" --board=uno --board=megaatmega2560
        -  platformio ci examples/webClient/webClient.ino --lib="." --lib="/tmp/jeelib-master" --lib="/tmp/Gamebuino-master/libraries/tinyFAT" --board=uno --board=megaatmega2560


  • Configuration file: hhttps://github.com/ivankravets/ethercard/blob/master/circle.yaml
  • Build History: https://circleci.com/gh/ivankravets/ethercard/tree/master

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code to GitHub and BitBucket repositories.

Drone is configured by modifying settings in your project control panel.

Drone automatically detects when a commit has been made and pushed to a repository that is using Drone, and each time this happens, it will try to build the project using platformio ci command. This includes commits to all branches, not just to the master branch. Drone will also build and run pull requests. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the build results (showing success or failure). It can be configured to build project on a range of different Development Platforms.

•
Drone
•
Integration
  • Using platformio run command
  • Using platformio ci command

•
Examples


There are two possible ways of running PlatformIO in CI services:

Using platformio run command

This variant is default choice for native PlatformIO projects (Please fill all fields for your project in the Drone control panel):

Commands:

pip install -U platformio
platformio run /path/to/project/dir -e <ID_1> -e <ID_2> -e <ID_N>


Using platformio ci command

This variant is more convenient when project is written as a library (when there are examples or testing code) as it has additional options for specifying extra libraries and boards from command line interface:

Environment Variables:

PLATFORMIO_CI_SRC=path/to/source/file.c
PLATFORMIO_CI_SRC=path/to/source/file.ino
PLATFORMIO_CI_SRC=path/to/source/directory


Commands:

pip install -U platformio
platformio ci --board=<ID_1> --board=<ID_2> --board=<ID_N>


[image]

1.
Integration for USB_Host_Shield_2.0 project. The circle.yml configuration file:

Environment Variables:

PLATFORMIO_CI_SRC=examples/Bluetooth/PS3SPP/PS3SPP.ino
PLATFORMIO_CI_SRC=examples/pl2303/pl2303_gps/pl2303_gps.ino


Commands:

pip install -U platformio
wget https://github.com/xxxajk/spi4teensy3/archive/master.zip -O /tmp/spi4teensy3.zip
unzip /tmp/spi4teensy3.zip -d /tmp
platformio ci --lib="." --lib="/tmp/spi4teensy3-master" --board=uno --board=teensy31 --board=due


[image]

GitHub Actions enables you to create custom software development life cycle (SDLC) workflows directly in your GitHub repository.

You need to configure GitHub Actions using YAML syntax, and save them as workflow files in your repository. Workflows are custom automated processes that you can set up in your repository to build, test, package, release, or deploy any code project on GitHub. You can write individual tasks, called actions, and combine them to create a custom workflow. Once you've successfully created aYAML workflow file and triggered the workflow, you will see the build logs, tests results, artifacts, and statuses for each step of your workflow. It can be configured to build project on a range of different Development Platforms.

GitHub Actions help you automate your software development workflows in the same place you store code and collaborate on pull requests and issues and each time this happens, it will try to build the project using platformio ci command.

•
GitHub Actions
•
Integration
  • Using platformio run command
  • Using platformio ci command
•
Library dependencies

  • Install dependent library using Library Manager
  • Manually download dependent library and include in build process via --lib option
•
Custom Build Flags


•
Examples


NOTE:

Please make sure to read GitHub Actions Getting Started guide first.


There are two possible ways of running PlatformIO in CI services:

Using platformio run command

This variant is default choice for native PlatformIO projects:

name: PlatformIO CI
on: [push]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1
    - name: Set up Python
      uses: actions/setup-python@v1
    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install platformio
    - name: Run PlatformIO
      run: platformio run /path/to/project/dir -e <ID_1> -e <ID_2> -e <ID_N>


Using platformio ci command

This variant is more convenient when project is written as a library (when there are examples or testing code) as it has additional options for specifying extra libraries and boards from command line interface:

name: PlatformIO CI
on: [push]
jobs:
  build:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        example: [path/to/test/file.c, examples/file.ino, path/to/test/directory]
    steps:
    - uses: actions/checkout@v1
    - name: Set up Python
      uses: actions/setup-python@v1
    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install platformio
    - name: Run PlatformIO
      run: platformio ci --board=<ID_1> --board=<ID_2> --board=<ID_N>
      env:
        PLATFORMIO_CI_SRC: ${{ matrix.example }}


Library dependencies

There 2 options to test source code with dependent libraries:

Install dependent library using Library Manager

- name: Install library dependencies
  run: platformio lib -g install 1
- name: Run PlatformIO
  run: platformio ci path/to/test/file.c --board=<ID_1> --board=<ID_2> --board=<ID_N>


Manually download dependent library and include in build process via --lib option

- name: Install library dependencies
  run: |
    wget https://github.com/PaulStoffregen/OneWire/archive/master.zip -O /tmp/onewire_source.zip
    unzip /tmp/onewire_source.zip -d /tmp/
- name: Run PlatformIO
  run: platformio ci path/to/test/file.c --lib="/tmp/OneWire-master" --board=<ID_1> --board=<ID_2> --board=<ID_N>


Custom Build Flags

PlatformIO allows one to specify own build flags using PLATFORMIO_BUILD_FLAGS environment

- name: Run PlatformIO
  run: platformio ci path/to/test/file.c --lib="/tmp/OneWire-master" --board=<ID_1> --board=<ID_2> --board=<ID_N>
  env:
    PLATFORMIO_BUILD_FLAGS: -D SPECIFIC_MACROS -I/extra/inc


For the more details, please follow to available build flags/options.

Integration for USB_Host_Shield_2.0 project. The workflow.yml configuration file:

name: PlatformIO CI
on: [push]
jobs:
  build:
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [ubuntu-latest, macos-latest, windows-latest]
        example: [examples/Bluetooth/PS3SPP/PS3SPP.ino, examples/pl2303/pl2303_gps/pl2303_gps.ino]
    steps:
    - uses: actions/checkout@v1
    - name: Set up Python
      uses: actions/setup-python@v1
    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install platformio
        wget https://github.com/xxxajk/spi4teensy3/archive/master.zip -O /tmp/spi4teensy3.zip
        unzip /tmp/spi4teensy3.zip -d /tmp
    - name: Run PlatformIO
      run: platformio ci --lib="." --lib="/tmp/spi4teensy3-master" --board=uno --board=teensy31 --board=due
      env:
        PLATFORMIO_CI_SRC: ${{ matrix.example }}


GitLab is a hosted cloud platform that can help you build, test, deploy, and monitor your code from GitLab repositories.

GitLab CI is enabled by default on new projects, so you can start using its features right away. All you need is platformio ci command, a file called .gitlab-ci.yml (where you describe how the build should run) placed in the root directory of your git project, and a configured Runner to perform the actual build (Gitlab has some pre-configured public runners so your CI script should work out of the box). Each project comes with a Builds page where you can follow the output of each build, see the commit that introduced it and other useful information such as the time the build started, how long it lasted and the commiter's name. The statuses for each build are exposed in the GitLab UI, and you can see whether a build succeeded, failed, got canceled or skipped.

•
GitLab
•
Integration
  • Using platformio run command
  • Using platformio ci command

•
Examples


Put .gitlab-ci.yml to the root directory of your repository. The contents of this file depends on the project you want to add. There are two possible ways of running PlatformIO in CI services:

Using platformio run command

This variant is default choice for native PlatformIO projects:

image: python:2.7
stages:
 - test
before_script:
  - "pip install -U platformio"
job:
  stage: test
  script: "platformio run /path/to/project/dir -e <ID_1> -e <ID_2> -e <ID_N>"


Using platformio ci command

This variant is more convenient when project is written as a library (when there are examples or testing code) as it has additional options for specifying extra libraries and boards from command line interface:

image: python:2.7
stages:
 - test
before_script:
  - "pip install -U platformio"
job:
  stage: test
  script: "platformio ci --board=<ID_1> --board=<ID_2> --board=<ID_N>"
  variables: {PLATFORMIO_CI_SRC: "path/to/test/file.c"}


1.
Integration for ArduinoJson library project. The .gitlab-ci.yml configuration file:

image: python:2.7
stages:
 - test
.job_template: &pio_run
  script:
    - "platformio ci --lib='.' --board=uno --board=teensy31 --board=nodemcuv2 $PLATFORMIO_CI_EXTRA_ARGS"
before_script:
  - "pip install -U platformio"
JsonGeneratorExample:
  <<: *pio_run
  variables:
    PLATFORMIO_CI_EXTRA_ARGS: "--board=due"
    PLATFORMIO_CI_SRC: examples/JsonGeneratorExample
JsonHttpClient:
  <<: *pio_run
  variables:
    PLATFORMIO_CI_SRC: examples/JsonHttpClient
JsonParserExample:
  <<: *pio_run
  variables:
    PLATFORMIO_CI_SRC: examples/JsonParserExample
JsonServer:
  <<: *pio_run
  variables:
    PLATFORMIO_CI_SRC: examples/JsonServer
JsonUdpBeacon:
  <<: *pio_run
  variables:
    PLATFORMIO_CI_SRC: examples/JsonUdpBeacon
ProgmemExample:
  stage: test
  <<: *pio_run
  variables:
    PLATFORMIO_CI_SRC: examples/ProgmemExample
StringExample:
  stage: test
  <<: *pio_run
  variables:
    PLATFORMIO_CI_SRC: examples/StringExample


Jenkins is a self-contained, open source automation server which can be used to automate all sorts of tasks related to building, testing, and deploying software.

Jenkins can be installed through native system packages, Docker, or even run standalone by any machine with a Java Runtime Environment (JRE) installed.

It can be configured to build project on a range of different Development Platforms.

•
Jenkins
•
Integration


See step-by-step guide in ThingForward's blog post Setting up a Jenkins CI engine for embedded projects.

Shippable is a hosted cloud platform that provides hosted continuous integration, deployment, and testing to GitHub and BitBucket repositories. Shippable's continuous integration service is built using Docker.

Shippable is configured by adding a file named shippable.yml, which is a YAML format text file, to the root directory of the GitHub repository or you can use your Travis CI configuration file .travis.yml.

Shippable automatically detects when a commit has been made and pushed to a repository that is using Shippable, and each time this happens, it will try to build the project using platformio ci command. This includes commits to all branches, not just to the master branch. Shippable will also build and run pull requests. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the build results (showing success or failure), or by posting a message on an IRC channel. It can be configured to build project on a range of different Development Platforms.

•
Shippable
•
Integration
  • Using platformio run command
  • Using platformio ci command

•
Examples


Put shippable.yml or .travis.yml to the root directory of your repository. The contents of this file depends on the project you want to add. There are two possible ways of running PlatformIO in CI services:

Using platformio run command

This variant is default choice for native PlatformIO projects:

language: python
python:
    - "2.7"
install:
    - pip install -U platformio
script:
    - platformio run /path/to/project/dir -e <ID_1> -e <ID_2> -e <ID_N>


Using platformio ci command

This variant is more convenient when project is written as a library (when there are examples or testing code) as it has additional options for specifying extra libraries and boards from command line interface:

language: python
python:
    - "2.7"
env:
    - PLATFORMIO_CI_SRC=path/to/source/file.c
    - PLATFORMIO_CI_SRC=path/to/source/file.ino
    - PLATFORMIO_CI_SRC=path/to/source/directory
install:
    - pip install -U platformio
script:
    - platformio ci --board=<ID_1> --board=<ID_2> --board=<ID_N>


1.
Integration for USB_Host_Shield_2.0 project. The shippable.yml or .travis.yml configuration file:

language: python
python:
    - "2.7"
env:
    - PLATFORMIO_CI_SRC=examples/Bluetooth/PS3SPP/PS3SPP.ino
    - PLATFORMIO_CI_SRC=examples/pl2303/pl2303_gps/pl2303_gps.ino
install:
    - pip install -U platformio
    - wget https://github.com/xxxajk/spi4teensy3/archive/master.zip -O /tmp/spi4teensy3.zip
    - unzip /tmp/spi4teensy3.zip -d /tmp
script:
    - platformio ci --lib="." --lib="/tmp/spi4teensy3-master" --board=uno --board=teensy31 --board=due


Travis CI officially supports PlatformIO for Embedded Builds.

Travis CI is an open-source hosted, distributed continuous integration service used to build and test projects hosted at GitHub.

Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the GitHub repository.

Travis CI automatically detects when a commit has been made and pushed to a repository that is using Travis CI, and each time this happens, it will try to build the project using platformio ci command. This includes commits to all branches, not just to the master branch. Travis CI will also build and run pull requests. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the build results (showing success or failure), or by posting a message on an IRC channel. It can be configured to build project on a range of different Development Platforms.

•
Travis CI
•
Integration
  • Using platformio run command
  • Using platformio ci command

•
Library dependencies
  • Install dependent library using Library Manager
  • Manually download dependent library and include in build process via --lib option

  • Custom Build Flags
  • Advanced configuration
  • Unit Testing
  • Examples


Please make sure to read Travis CI Getting Started and general build configuration guides first.

NOTE:

If you are going to use PlatformIO PIO Unit Testing or PIO Remote you will need to define PLATFORMIO_AUTH_TOKEN environment variable in project settings. See Defining Variables in Repository Settings guide.


PlatformIO is written in Python and is recommended to be run within Travis CI Python isolated environment. There are two possible ways of running PlatformIO in CI services:

Using platformio run command

This variant is default choice for native PlatformIO projects:

language: python
python:
    - "2.7"
# Cache PlatformIO packages using Travis CI container-based infrastructure
sudo: false
cache:
    directories:
        - "~/.platformio"
install:
    - pip install -U platformio
    - platformio update
script:
    - platformio run /path/to/project/dir -e <ID_1> -e <ID_2> -e <ID_N>


Using platformio ci command

This variant is more convenient when project is written as a library (when there are examples or testing code) as it has additional options for specifying extra libraries and boards from command line interface:

language: python
python:
    - "2.7"
# Cache PlatformIO packages using Travis CI container-based infrastructure
sudo: false
cache:
    directories:
        - "~/.platformio"
env:
    - PLATFORMIO_CI_SRC=path/to/test/file.c
    - PLATFORMIO_CI_SRC=examples/file.ino
    - PLATFORMIO_CI_SRC=path/to/test/directory
install:
    - pip install -U platformio
    - platformio update
script:
    - platformio ci --board=<ID_1> --board=<ID_2> --board=<ID_N>


Then perform steps 1, 2 and 4 from http://docs.travis-ci.com/user/getting-started/

Library dependencies

There 2 options to test source code with dependent libraries:

Install dependent library using Library Manager

install:
    - pip install -U platformio
    #
    # Libraries from PlatformIO Library Registry:
    #
    # https://platformio.org/lib/show/1/OneWire
    - platformio lib -g install 1


Manually download dependent library and include in build process via --lib option

install:
    - pip install -U platformio
    # download library to the temporary directory
    - wget https://github.com/PaulStoffregen/OneWire/archive/master.zip -O /tmp/onewire_source.zip
    - unzip /tmp/onewire_source.zip -d /tmp/
script:
    - platformio ci --lib="/tmp/OneWire-master" --board=<ID_1> --board=<ID_2> --board=<ID_N>


Custom Build Flags

PlatformIO allows one to specify own build flags using PLATFORMIO_BUILD_FLAGS environment

env:
    - PLATFORMIO_CI_SRC=path/to/test/file.c PLATFORMIO_BUILD_FLAGS="-D SPECIFIC_MACROS_PER_TEST_ENV -I/extra/inc"
    - PLATFORMIO_CI_SRC=examples/file.ino
    - PLATFORMIO_CI_SRC=path/to/test/directory
install:
    - pip install -U platformio
    - export PLATFORMIO_BUILD_FLAGS="-D GLOBAL_MACROS_FOR_ALL_TEST_ENV"


For the more details, please follow to available build flags/options.

Advanced configuration

PlatformIO allows one to configure multiple build environments for the single source code using "platformio.ini" (Project Configuration File).

Instead of --board option, please use platformio ci --project-conf

script:
    - platformio ci --project-conf=/path/to/platoformio.ini


See PlatformIO Remote Unit Testing Example.

1.
Custom build flags

language: python
python:
    - "2.7"
# Cache PlatformIO packages using Travis CI container-based infrastructure
sudo: false
cache:
    directories:
        - "~/.platformio"
env:
    - PLATFORMIO_CI_SRC=examples/acm/acm_terminal
    - PLATFORMIO_CI_SRC=examples/Bluetooth/WiiIRCamera PLATFORMIO_BUILD_FLAGS="-DWIICAMERA"
    - PLATFORMIO_CI_SRC=examples/ftdi/USBFTDILoopback
    - PLATFORMIO_CI_SRC=examples/Xbox/XBOXUSB
    # - ...
install:
    - pip install -U platformio
    - platformio update
    #
    # Libraries from PlatformIO Library Registry:
    #
    # https://platformio.org/lib/show/416/TinyGPS
    # https://platformio.org/lib/show/417/SPI4Teensy3
    - platformio lib -g install 416 417
script:
    - platformio ci --board=uno --board=teensy31 --board=due --lib="."


  • Configuration file: https://github.com/felis/USB_Host_Shield_2.0/blob/master/.travis.yml
  • Build History: https://travis-ci.org/felis/USB_Host_Shield_2.0

2.
Dependency on external libraries

language: python
python:
    - "2.7"
# Cache PlatformIO packages using Travis CI container-based infrastructure
sudo: false
cache:
    directories:
        - "~/.platformio"
env:
    - PLATFORMIO_CI_SRC=examples/backSoon/backSoon.ino
    - PLATFORMIO_CI_SRC=examples/etherNode/etherNode.ino
    # -
install:
    - pip install -U platformio
    - platformio update
    - wget https://github.com/jcw/jeelib/archive/master.zip -O /tmp/jeelib.zip
    - unzip /tmp/jeelib.zip -d /tmp
    - wget https://github.com/Rodot/Gamebuino/archive/master.zip  -O /tmp/gamebuino.zip
    - unzip /tmp/gamebuino.zip -d /tmp
script:
    - platformio ci --lib="." --lib="/tmp/jeelib-master" --lib="/tmp/Gamebuino-master/libraries/tinyFAT" --board=uno --board=megaatmega2560


  • Configuration file: https://github.com/jcw/ethercard/blob/master/.travis.yml
  • Build History: https://travis-ci.org/jcw/ethercard

3.
Dynamic testing of the boards

language: python
python:
    - "2.7"
# Cache PlatformIO packages using Travis CI container-based infrastructure
sudo: false
cache:
    directories:
        - "~/.platformio"
env:
    - PLATFORMIO_CI_SRC=examples/TimeArduinoDue PLATFORMIO_CI_EXTRA_ARGS="--board=due"
    - PLATFORMIO_CI_SRC=examples/TimeGPS
    - PLATFORMIO_CI_SRC=examples/TimeNTP
    - PLATFORMIO_CI_SRC=examples/TimeTeensy3 PLATFORMIO_CI_EXTRA_ARGS="--board=teensy31"
    # - ...
install:
    - pip install -U platformio
    - platformio update
    - rm -rf ./linux
    #
    # Libraries from PlatformIO Library Registry:
    #
    # https://platformio.org/lib/show/416/TinyGPS
    - platformio lib -g install 416 421 422
script:
    - platformio ci --lib="." --board=uno --board=teensy20pp $PLATFORMIO_CI_EXTRA_ARGS


  • Configuration file: https://github.com/ivankravets/Time/blob/master/.travis.yml
  • Build History: https://travis-ci.org/ivankravets/Time

4.
Advanced configuration with extra project options and libraries

language: python
python:
    - "2.7"
# Cache PlatformIO packages using Travis CI container-based infrastructure
sudo: false
cache:
    directories:
        - "~/.platformio"
env:
    - PLATFORMIO_CI_SRC=examples/Boards_Bluetooth/Adafruit_Bluefruit_LE
    - PLATFORMIO_CI_SRC=examples/Boards_Bluetooth/Arduino_101_BLE PLATFORMIO_CI_EXTRA_ARGS="--board=genuino101"
    - PLATFORMIO_CI_SRC=examples/Boards_USB_Serial/Blue_Pill_STM32F103C PLATFORMIO_CI_EXTRA_ARGS="--board=bluepill_f103c8 --project-option='framework=arduino'"
    - PLATFORMIO_CI_SRC=examples/Export_Demo/myPlant_ESP8266 PLATFORMIO_CI_EXTRA_ARGS="--board=nodemcuv2 --project-option='lib_ignore=WiFi101'"
    # - ...
install:
    - pip install -U platformio
    - platformio update
    #
    # Libraries from PlatformIO Library Registry:
    #
    # https://platformio.org/lib/show/44/Time
    # https://platformio.org/lib/show/419/SimpleTimer
    #
    # https://platformio.org/lib/show/17/Adafruit-CC3000
    # https://platformio.org/lib/show/28/SPI4Teensy3
    # https://platformio.org/lib/show/91/UIPEthernet
    # https://platformio.org/lib/show/418/WildFireCore
    # https://platformio.org/lib/show/420/WildFire-CC3000
    # https://platformio.org/lib/show/65/WiFlyHQ
    # https://platformio.org/lib/show/19/Adafruit-DHT
    # https://platformio.org/lib/show/299/WiFi101
    # https://platformio.org/lib/show/259/BLEPeripheral
    # https://platformio.org/lib/show/177/Adafruit_BluefruitLE_nRF51
    - platformio lib -g install 17 28 91 418 419 420 65 44 19 299 259 177 https://github.com/vshymanskyy/BlynkESP8266.git https://github.com/cmaglie/FlashStorage.git https://github.com/michael71/Timer5.git
script:
    - make travis-build


  • Configuration file: https://github.com/blynkkk/blynk-library/blob/master/.travis.yml
  • Build History: https://travis-ci.org/blynkkk/blynk-library

New in version 4.2.

A compilation database is a JSON-formatted file named compile_commands.json that contains structured data about every compilation unit in your project.

PlatformIO Core (CLI) supports generating of compilation database using platformio run --target command and compiledb target. For example,

> platformio run -t compiledb


A default path for compile_commands.json is "build_dir/envname". You can override this path with Advanced Scripting and COMPILATIONDB_PATH environment variable. For example, generate compile_commands.json in a root of project:

platformio.ini:

[env:myenv]
platform = ...
board = ...
extra_scripts = post:extra_script.py


extra_script.py:

import os
Import("env")
env.Replace(COMPILATIONDB_PATH=os.path.join("$PROJECT_DIR", "compile_commands.json"))


NOTE:

If you've written article about PlatformIO and would like it listed on this page, please edit this page.


Here are recent articles/reviews about PlatformIO:

  • Mar 28, 2020 - Brian Lough - Use the PlatformIO Debugger on the ESP32 Using an ESP-prog
  • Mar 10, 2020 - James Harton - Augie the Hexapod Robot
  • Mar 05, 2020 - Alex Govorov - PVS-Studio Integration in PlatformIO
  • Feb 2, 2020 - Tommy Desrochers - VS Code et PlatformIO: Mieux que l'IDE Arduino?
  • Jan 15, 2020 - Ivan Kravets, CEO of PlatformIO - Next-generation IDE for your RISC-V Product in 20 Minutes

  • Dec 29, 2019 - Andri Yadi - AI-Powered Magic Wand
  • Oct 31, 2019 - Frank Leon Rose - Minimal FreeRTOS with PlatformIO
  • Aug 18, 2019 - Manuel Bleichenbacher - Arduino In-circuit Debugging with PlatformIO
  • Aug 13, 2019 - Tech Explorations - 6 reasons why PlatformIO is perhaps the best programming environment for the ESP32
  • Jul 04, 2019 - Jean-Claude Wippler - The PlatformIO command line
  • Mar 08, 2019 - Nathan Glover - Amazon Alexa controlled IoT Traffic Lights

  • Dec 27, 2018 - Xose Pérez - Automated unit testing in the metal
  • Dec 20, 2018 - Jean-Claude Wippler - Getting started with the STM32F407VG and STM32Cube
  • Nov 24, 2018 - Martin Fasani - PlatformIO: An alternative to Arduino IDE and a complete ecosystem for IoT
  • Sep 27, 2018 - Lup Yuen Lee - Connect STM32 Blue Pill to Sigfox
  • Aug 27, 2018 - Lup Yuen Lee - Juggling STM32 Blue Pill For Arduino Jugglers
  • Jul 3, 2018 - Andreas Schmidt - IoT for web developers: From zero to firmware, Part II
  • Jun 22, 2018 - Andreas Schmidt - IoT for web developers, Part I
  • Jul 4, 2018 - ThingForward - Screen-cast: First steps with PlatformIO’s Unified Debugger
  • Jun 6, 2018 - Andreas Schmidt - ESP32, WebThing API and PlatformIO-style projects
  • May 21, 2018 - Dentella Luca - ESP32, PlatformIO
  • Mar 27, 2018 - Andreas Schmidt - Building a Web Of Things REST-API on an Arduino MKR1000 with PlatformIO
  • Mar 19, 2018 - ThingForward - Webinar: Unit Testing for Embedded with PlatformIO and Qt Creator
  • Feb 16, 2018 - Alex Corvis - DIY Virtual alike NEST Thermostat with Node-RED
  • Jan 24, 2018 - ThingForward - Embedded and Cloud - Continuous Integration
  • Jan 14, 2018 - IT4nextgen - 5 Best Development Software(IDE) for Internet of Things (IOT) in 2018
  • Jan 13, 2018 - Rui Marinho - Quick start guide to flashing ESP8266-based devices with PlatformIO

  • Dec 26, 2017 - Coyt Barringer - Programming STM32F103 Blue Pill using USB Bootloader and PlatformIO
  • Dec 1, 2017 - ThingForward - Using Cloud IDEs for Embedded Development: CodeAnywhere
  • Nov 13, 2017 - ThingForward - Automating Static and Dynamic Code Analysis with PlatformIO
  • Oct 18, 2017 - ThingForward - Getting Started with SigFox and PlatformIO
  • Sep 18, 2017 - ThingForward - Embedded Testing with PlatformIO – Part 4: Continuous Integration
  • Sep 06, 2017 - ThingForward - Embedded Testing with PlatformIO – Part 3: Remoting
  • Sep 04, 2017 - Dror Gluska - Looking To The IoT Future With PlatformIO And ESP32
  • Aug 23, 2017 - 陳亮 - Develop ESP32 With PlatformIO IDE
  • Aug 08, 2017 - ThingForward - Embedded Testing with PlatformIO - Part 2
  • Jul 25, 2017 - ThingForward - Start Embedded Testing with PlatformIO
  • Jun 23, 2017 - Naresh Krish - Home Automation Using Wiscore, OpenHab and PlatformIO
  • Jun 05, 2017 - Projects DIY - Démarrer avec PlatformIO IDE alternatif pour Arduino, ESP8266, ESP32 et autres micro-contrôleurs (Start with PlatformIO alternative IDE for Arduino, ESP8266, ESP32 and other microcontrollers, French)
  • Apr 12, 2017 - Jane Elizabeth - Let's talk IoT: PlatformIO puts developers back in the driver's seat
  • Apr 07, 2017 - Al Williams - Hackaday: PlatformIO and Visual Studio take over the world
  • Mar 13, 2017 - Ryan Mulligan - Continuous testing for Arduino libraries using PlatformIO and Travis CI
  • Feb 23, 2017 - Bastiaan Visee - Using PlatformIO for your Arduino projects
  • Jan 12, 2017 - Tiest van Gool - OTA: PlatformIO and ESP8266

  • Dec 13, 2016 - Dr. Patrick Mineault - Multi-Arduino projects with PlatformIO
  • Dec 08, 2016 - Cuong Tran Viet - PlatformIO is a solution
  • Nov 10, 2016 - PiGreek - PlatformIO the new Arduino IDE ?!
  • Oct 31, 2016 - Ricardo Quesada - Retro Challenge: announcing Commodore Home
  • Oct 3, 2016 - Xose Pérez - Using the new Bean Loader CLI from PlatformIO
  • Sep 20, 2016 - The Linux Foundation - 21 Open Source Projects for IoT
  • Sep 19, 2016 - Doc Walker - How to automatically test build Arduino libraries
  • Sep 18, 2016 - Kadda Sahnine - LoRaWAN network practice with Objenious, PlatformIO and Node-RED
  • Sep 13, 2016 - Xose Pérez MQTT LED Matrix Display
  • Sep 12, 2016 - Pedro Minatel - OTA – Como programar o ESP8266 pelo WiFi no platformIO (OTA programming for ESP8266 via Wi-Fi using PlatformIO, Portuguese)
  • Sep 2, 2016 - Xose Pérez ESP8266: Optimizing files for SPIFFS with Gulp
  • Aug 28, 2016 - Tom Parker Using the BBC micro:bit with PlatformIO
  • Aug 24, 2016 - Primal Cortex Cloud based continuous integration and delivery for IOT using PlatformIO
  • Aug 18, 2016 - Primal Cortex - Installing PlatformIO on Arch Linux
  • Aug 14, 2016 - Rodrigo Castro - PlataformIO o comó usar Arduino con ATOM (Spanish)
  • Jul 27, 2016 - Francesco Azzola - Arduino Alternative IDE: PlatformIO IoT integrated platform
  • Jul 26, 2016 - Embedded Systems Laboratory - แนะนำการใช้งาน PlatformIO IDE สำหรับบอร์ด Arduino และ ESP8266 (Get started with PlatformIO IDE for Arduino board and ESP8266, Thai)
  • Jul 15, 2016 - Jaime - ESP8266 Mobile Rick Roll Captive Portal
  • Jul 5, 2016 - Ivan Kravets, Ph.D. - Explore the new development instruments for Arduino with PlatformIO ecosystem
  • Jul 5, 2016 - Belinda - Monte Bianco Arduino Developer Summit
  • Jul 1, 2016 - Tam Hanna - Mikrocontroller-Gipfel in den Alpen: Arduino Developer Summit, Tag eins (Microcontroller peaks in the Alps: Arduino Developer Summit, Day One, German)
  • Jun 14, 2016 - Glyn Hudson - OpenEnergyMonitor Part 2/3: Firmware Continuous Test & Build
  • Jun 13, 2016 - Daniel Eichhorn - New Weather Station Demo on Github
  • Jun 12, 2016 - Glyn Hudson - OpenEnergyMonitor Part 1/3: PlatformIO open-source embedded development ecosystem
  • Jun 12, 2016 - Uli Wolf - Nutzung von PlatformIO im Atom Editor zur Entwicklung von Arduino Code (Use PlatformIO and Atom Editor to develop Arduino code, German)
  • Jun 3, 2016 - Daniel Eichhorn - ESP8266: Continuous Delivery Pipeline – Push To Production
  • May 30, 2016 - Ron Moerman - IoT Development with PlatformIO
  • May 29, 2016 - Chris Synan - Reverse Engineer RF Remote Controller for IoT!
  • May 26, 2016 - Charlie Key - 7 Best Developer Tools To Build Your NEXT Internet of Things Application
  • May 22, 2016 - Pedro Minatel - Estação meteorológica com ESP8266 (Weather station with ESP8266, Portuguese)
  • May 16, 2016 - Pedro Minatel - Controle remoto WiFi com ESP8266 (WiFi remote control using ESP8266, Portuguese)
  • May 11, 2016 - Jo Vandeginste - Using PlatformIO to compile for Jeelabs' Jeenode Micro
  • May 08, 2016 - Radoslaw Bob - Touch controlled buzzer (Nodemcu ESP8266)
  • May 06, 2016 - Jean Roux - The IoT building blocks I use for my home-automation projects
  • May 05, 2016 - Ivan Kravets, Ph.D. / Eclipse Virtual IoT Meetup - PlatformIO: a cross-platform IoT solution to build them all!
  • May 01, 2016 - Pedro Minatel - PlatformIO – Uma alternativa ao Arduino IDE (PlatformIO - An alternative to the Arduino IDE, Portuguese)
  • Apr 23, 2016 - Al Williams - Hackaday: Atomic Arduino (and Other) Development
  • Apr 16, 2016 - Sathittham Sangthong - [PlatformIO] มาลองเล่น PlatformIO แทน Arduino IDE กัน (Let's play together with PlatformIO IDE [alternative to Arduino IDE], Thai)
  • Apr 15, 2016 - Daniel Eichhorn - ESP8266: Offline Debugging with the Platformio Environment
  • Apr 11, 2016 - Matjaz Trcek - Top 5 Arduino integrated development environments
  • Apr 06, 2016 - Aleks - PlatformIO ausprobiert (Tried PlatformIO, German)
  • Apr 02, 2016 - Diego Pinto - Você tem coragem de abandonar a IDE do Arduino? PlatformIO + Atom (Do you dare to leave the Arduino IDE? PlatformIO + Atom, Portuguese)
  • Mar 30, 2016 - Brandon Cannaday - Getting Started with PlatformIO and ESP8266 NodeMcu
  • Mar 29, 2016 - Pablo Peñalve - PlatformIO + Geany + Raspberry PI, Spanish
  • Mar 24, 2016 - NAzT - PlatformIO และการปรับแต่ง เพื่อใช้สำหรับพัฒนา Arduino Library (PlatformIO and advanced development for Arduino Library, Thai)
  • Mar 16, 2016 - Jakub Skořepa - Instalace PlatformIO (PlatformIO IDE Installation, Czech)
  • Mar 12, 2016 - Peter Marks - PlatformIO, the Arduino IDE for programmers
  • Mar 12, 2016 - Richard Arthurs - Getting Started With PlatformIO
  • Mar 07, 2016 - Joran Jessurun - Nieuwe wereld met PlatformIO (New world with PlatformIO, Dutch)
  • Mar 05, 2016 - brichacek.net - PlatformIO – otevřený ekosystém pro vývoj IoT (PlatformIO – an open source ecosystem for IoT development, Czech)
  • Mar 04, 2016 - Ricardo Vega - Programa tu Arduino desde Atom (Program your Arduino from Atom, Spanish)
  • Feb 28, 2016 - Alex Bloggt - PlatformIO vorgestellt (Introduction to PlatformIO IDE, German)
  • Feb 25, 2016 - NutDIY - PlatformIO Blink On Nodemcu Dev Kit V1.0 (Thai)
  • Feb 23, 2016 - Ptarmigan Labs - ESP8266 Over The Air updating – what are the options?
  • Feb 22, 2016 - Grzegorz Hołdys - How to Integrate PlatformIO with Netbeans
  • Feb 19, 2016 - Embedds - Develop easier with PlatformIO ecosystem
  • Feb 13, 2016 - Robert Cudmore - Programming an arduino with PlatformIO
  • Jan 24, 2016 - Sergey Prilukin - How to use IntelliJ IDEA to develop and upload software for micro controllers like Arduino
  • Jan 16, 2016 - Dani Eichhorn - ESP8266 Arduino IDE Alternative: PlatformIO
  • Jan 11, 2016 - David Mills, Ph.D. - STM NUCLEOF401RE TIMER IO
  • Jan 05, 2016 - Julien Rodrigues - Internet Of Things: The IDE scandal

  • Dec 22, 2015 - Jan Penninkhof - Over-the-Air ESP8266 programming using PlatformIO
  • Dec 15, 2015 - stastaka - PlatformIOでカスタムボードを使う (Use a custom board for PlatformIO, Japanese)
  • Dec 08, 2015 - Piotr Król - Using PlatformIO with TI MSP430 LunchPads
  • Dec 01, 2015 - Michał Seroczyński - Push Notification from Arduino Yún with motion sensor
  • Dec 01, 2015 - JetBrains CLion Blog - C++ Annotated: Fall 2015. Arduino Support in CLion using PlatformIO
  • Dec 01, 2015 - Tateno Yuichi - ESP8266 を CUI で開発する (Develop a ESP8266 in CUI, Japanese)
  • Nov 29, 2015 - Keith Hughes - Using PlatformIO for Embedded Projects
  • Nov 22, 2015 - Michał Seroczyński - Using PlatformIO to get started with Arduino in CLion IDE
  • Nov 09, 2015 - ÁLvaro García Gómez - Programar con Arduino "The good way" (Programming with Arduino "The good way", Spanish)
  • Nov 06, 2015 - nocd5 - PlatformIOでmbedをオフラインビルドしSTM32 Nucleoボードでmrubyを使う (Use mruby in the offline build for STM32 Nucleo board with mbed and PlatformIO, Japanese)
  • Oct 21, 2015 - Vittorio Zaccaria - Using a cheap STM32 Nucleo to teach remote sensor monitoring
  • Oct 18, 2015 - Nico Coetzee - First Arduino I2C Experience with PlatformIO
  • Oct 10, 2015 - Floyd Hilton - Programming Arduino with Atom
  • Oct 01, 2015 - Mistan - Compile and Upload Arduino Sketch with PlatformIO for Raspberry Pi Running Arch Linux
  • Sep 30, 2015 - Jay Wiggins - PlatformIO Investigation
  • Sep 01, 2015 - Thomas P. Weldon, Ph.D. - Improvised MBED FRDM-K64F Eclipse/PlatformIO Setup and Software Installation
  • Aug 08, 2015 - Josh Glendenning - Armstrap Eagle and PlatformIO
  • Aug 01, 2015 - Russell Davis - PlatformIO on the Raspberry Pi
  • Jul 25, 2015 - DinoTools - Erste Schritte mit PlatformIO (Getting Started with PlatformIO, German)
  • Jul 20, 2015 - Eli Fatsi - Arduino Development in Atom Editor
  • Jul 14, 2015 - ElbinarIO - Programar para Arduino y otros microcontroladores desde la linea de comandos (Program Arguino and other microcontrollers from the command line, Spanish)
  • Jul 11, 2015 - TrojanC - Learning Arduino GitHub Repository
  • Jul 07, 2015 - Sho Hashimoto - PlatformIOでArduino開発する(Arduino development in PlatformIO, Japanese)
  • Jun 02, 2015 - Alejandro Guirao Rodríguez - Discovering PlatformIO: The RaspberryPi / Arduino combo kit is a winner option when prototyping an IoT-style project
  • May 17, 2015 - S.S - コマンドラインでArduino開発 : vim + platformio (Arduino development at the command line: VIM + PlatformIO, Japanese)
  • May 11, 2015 - IT Hare - From Web Developer to Embedded One: Interview with Ivan Kravets, The Guy Behind PlatformIO. Part II
  • May 4, 2015 - IT Hare - From Web Developer to Embedded One: Interview with Ivan Kravets, The Guy Behind PlatformIO. Part I
  • Apr 17, 2015 - Michael Ball - PlatformIO - A Cross-Platform Code Builder and Missing Library Manager
  • Mar 23, 2015 - Atmel - Cross-board and cross-vendor embedded development with PlatformIO
  • Mar 22, 2015 - Mark VandeWettering - Discovered a new tool for embedded development: PlatformIO
  • Feb 25, 2015 - Hendrik Putzek - Use your favourite IDE together with Arduino

  • Oct 7, 2014 - Ivan Kravets, Ph.D. - Integration of PlatformIO library manager to Arduino and Energia IDEs
  • Jun 20, 2014 - Ivan Kravets, Ph.D. - Building and debugging Atmel AVR (Arduino-based) project using Eclipse IDE+PlatformIO
  • Jun 17, 2014 - Ivan Kravets, Ph.D. - How was PlatformIO born or why I love Python World

Frequently Asked Questions

NOTE:

We have a big database with Frequently Asked Questions in our Community Forums. Please have a look at it.


•
General
  • What is PlatformIO?
  • What is .pio directory
  • What is .pioenvs directory
  • Command completion in Terminal

  • Install Python Interpreter
  • Convert Arduino file to C++ manually
  • Program Memory Usage
  • Advanced Serial Monitor with UI
  • Troubleshooting
•
Installation
  • Multiple PIO Cores in a system
  • 'platformio' is not recognized as an internal or external command
  • 99-platformio-udev.rules
  • ImportError: cannot import name _remove_dead_weakref

•
Package Manager
•
[Error 5] Access is denied
  • Solution 1: Remove folder
  • Solution 2: Antivirus
  • Solution 3: Run from Terminal
  • Solution 4: Manual


•
Building
  • UnicodeWarning: Unicode equal comparison failed
  • UnicodeDecodeError: Non-ASCII characters found in build environment
  • ARM toolchain: cc1plus: error while loading shared libraries
  • Archlinux: libncurses.so.5: cannot open shared object file
  • Monitoring a serial port breaks upload



What is PlatformIO?

Please refer to What is PlatformIO?

What is .pio directory

Please refer to workspace_dir.

What is .pioenvs directory

Please refer to build_dir.

Please refer to PlatformIO Shell Completion.

PlatformIO Core (CLI) is written in Python that is installed by default on the all popular OS except Windows.

Please navigate to official website and Download the latest Python and install it. Please READ NOTES BELOW.

Please read the "Important Information" displayed during installation for information about SSL/TLS certificate validation and the running the "Install Certificates.command".

If you do not install SSL/TLS certificates, PlatformIO will not be able to download dependent packages, libraries, and toolchains.

Please select Add Python to Path (see below), otherwise, python command will not be available. [image]

Convert Arduino file to C++ manually

Some Cloud & Desktop IDE doesn't support Arduino files (*.ino and .pde) because they are not valid C/C++ based source files:

1.
Missing includes such as #include <Arduino.h>
2.
Function declarations are omitted.

In this case, code completion and code linting do not work properly or are disabled. To avoid this issue you can manually convert your INO files to CPP.

For example, we have the next Demo.ino file:

void setup () {
    someFunction(13);
}
void loop() {
    delay(1000);
}
void someFunction(int num) {
}


Let's convert it to Demo.cpp:

1.
Add #include <Arduino.h> at the top of the source file
2.
Declare each custom function (excluding built-in, such as setup and loop) before it will be called.

The final Demo.cpp:

#include <Arduino.h>
void someFunction(int num);
void setup () {
    someFunction(13);
}
void loop() {
    delay(1000);
}
void someFunction(int num) {
}


Finish.

PlatformIO calculates firmware/program memory usage based on the next segments:

.text
The code segment, also known as a text segment or simply as text, is where a portion of an object file or the corresponding section of the program's virtual address space that contains executable instructions is stored and is generally read-only and fixed size.
.data
The .data segment contains any global or static variables which have a pre-defined value and can be modified. The values for these variables are initially stored within the read-only memory (typically within .text) and are copied into the .data segment during the start-up routine of the program. Example,

int val = 3;
char string[] = "Hello World";


.bss
Uninitialized data is usually adjacent to the data segment. The BSS segment contains all global variables and static variables that are initialized to zero or do not have explicit initialization in the source code. For instance, a variable defined as static int i; would be contained in the BSS segment.

The rough calculation could be done as:

  • PROGRAM (Flash) = .text + .data
  • DATA (RAM) = .bss + .data

If you need to print all memory sections and addresses, please use platformio run --verbose command.

Recommended for reading:

  • https://en.wikipedia.org/wiki/Data_segment
  • text, data and bss: Code and Data Size Explained

PlatformIO Core provides CLI version (platformio device monitor) of Serial Monitor. If you need advanced instrument with a rich UI, we recommend free and multi-platform CoolTerm serial port terminal application.

WARNING:

Please note that you need to manually disconnect (close serial port connection) in CoolTerm before doing uploading in PlatformIO. PlatformIO can not disconnect/connect to a target device automatically when CoolTerm is used.


Multiple standalone PlatformIO Core (CLI) in a system could lead to the different issues. We highly recommend to keep one instance of PIO Core or use built-in PIO Core in PlatformIO IDE:

  • PlatformIO IDE for Atom - Menu PlatformIO: Settings > PlatformIO IDE > Use built-in PlatformIO Core
  • VSCode - Settings > Set platformio-ide.useBuiltinPIOCore to true.

Finally, if you have a standalone PlatformIO Core (CLI) in a system, please open system Terminal (not PlatformIO IDE Terminal) and uninstall obsolete PIO Core:

pip uninstall platformio
# if you used macOS "brew"
brew uninstall platformio


If you need to have PlatformIO Core (CLI) globally in a system, please Install Shell Commands.

'platformio' is not recognized as an internal or external command

If you use PlatformIO IDE, please check in PlatformIO IDE Settings that "Use built-in PIO Core" is enabled.

If you modify system environment variable PATH in your Bash/Fish/ZSH profile, please do not override global PATH. This line export PATH="/my/custom/path" is incorrect. Use export PATH="/my/custom/path":$PATH instead.

Linux users have to install udev rules for PlatformIO supported boards/devices. The latest version of rules may be found at https://raw.githubusercontent.com/platformio/platformio-core/master/scripts/99-platformio-udev.rules

NOTE:

Please check that your board's PID and VID are listed in the rules. You can list connected devices and their PID/VID using platformio device list command.


This file must be placed at /etc/udev/rules.d/99-platformio-udev.rules (preferred location) or /lib/udev/rules.d/99-platformio-udev.rules (required on some broken systems).

Please open system Terminal and type

# Recommended
curl -fsSL https://raw.githubusercontent.com/platformio/platformio-core/master/scripts/99-platformio-udev.rules | sudo tee /etc/udev/rules.d/99-platformio-udev.rules
# OR, manually download and copy this file to destination folder
sudo cp 99-platformio-udev.rules /etc/udev/rules.d/99-platformio-udev.rules


Restart "udev" management tool:

sudo service udev restart
# or
sudo udevadm control --reload-rules
sudo udevadm trigger


Ubuntu/Debian users may need to add own “username” to the “dialout” group if they are not “root”, doing this issuing

sudo usermod -a -G dialout $USER
sudo usermod -a -G plugdev $USER


Similarly, Arch users may need to add their user to the “uucp” group

sudo usermod -a -G uucp $USER
sudo usermod -a -G lock $USER


NOTE:

You will need to log out and log back in again (or reboot) for the user group changes to take effect.


After this file is installed, physically unplug and reconnect your board.

Windows users can experience this issue when multiple Python interpreters are installed in a system and conflict each other. The easy way to fix this problem is uninstalling all Python interpreters using Windows Programs Manager and installing them manually again.

1.
"Windows > Start Menu > Settings > System > Apps & Features", select Python interpreters and uninstall them.
2.
Install the latest Python interpreter, see Install Python Interpreter guide
3.
Remove C:\Users\YourUserName\.platformio and C:\.platformio folders if exist (do not forget to replace "YourUserName" with the real user name)
4.
Restart PlatformIO IDE.

PlatformIO installs all packages to "core_dir/packages" directory. You MUST HAVE write access to this folder. Please note that PlatformIO does not require "sudo"/administrative privileges.

  • Solution 1: Remove folder
  • Solution 2: Antivirus
  • Solution 3: Run from Terminal
  • Solution 4: Manual

A quick solution is to remove "core_dir/packages" folder and repeat installation/building/uploading again.

Some antivirus tools forbid programs to create files in the background. PlatformIO Package Manager does all work in the background: downloads package, unpacks archive in temporary folder and moves final files to "core_dir/packages" folder.

Antivirus tool can block PlatformIO, that is why you see "[Error 5] Access is denied". Try to disable it for a while or add core_dir directory to exclusion/whitelist.

As we mentioned in "Solution 2", antivirus tools can block background file system operations. Another solution is to run PlatformIO Core (CLI) from a system terminal.

1.
Open System Terminal, on Windows cmd.exe (not PlatformIO IDE Terminal)
2.
Build a project and upload firmware using PlatformIO Core (CLI) which will download and install all dependent packages:

# Change directory to PlatformIO Project where is located "platformio.ini"
cd path/to/platformio/project
# Force PlatformIO to install PIO Home dependencies
platformio home
# Force PlatformIO to install toolchains
platformio run --target upload



If "platformio" command is not globally available in your environment and you use PlatformIO IDE, please use built-in PlatformIO Core (CLI) which is located in:

  • Windows: C:\Users\{username}\.platformio\penv\Scripts\platformio Please replace {username} with a real user name
  • Unix: ~/.platformio/penv/bin/platformio

NOTE:

You can add platformio and pio commands to your system environment. See Install Shell Commands.


If none of the solutions above do work for you, you can download and unpack all packages manually to "core_dir/packages".

Please visit PlatformIO Package Storage and download a package for your platform. A correct package path is "core_dir/packages/{package_name}/package.json".

Full warning message is "UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal".

KNOWN ISSUE. Please move your project to a folder which full path does not contain non-ASCII chars.

KNOWN ISSUE. PlatformIO Core (CLI) currently does not support projects which contain non-ASCII characters (codes) in a full path or depend on the libraries which use non-ASCII characters in their names.

TEMPORARY SOLUTION

1.
Use PlatformIO IDE, it will automatically install PlatformIO Core (CLI) in a root of system disk (%DISK%/.platformio) and avoid an issue when system User contains non-ASCII characters
2.
Do not use non-ASCII characters in project folder name or its parent folders.

Also, if you want to place PlatformIO Core (CLI) in own location, see:

  • Set PLATFORMIO_CORE_DIR environment variable with own path
  • Configure custom location per project using core_dir option in "platformio.ini" (Project Configuration File).

See related answers for error while loading shared libraries.

Answered in issue #291.

Answered in issue #384.

  • Added PlatformIO CLI Shell Completion for Fish, Zsh, Bash, and PowerShell (issue #3435)
  • Automatically build contrib-pysite package on a target machine when pre-built package is not compatible (issue #3482)
  • Fixed an issue on Windows when installing a library dependency from Git repository (issue #2844, issue #3328)

•
Fixed "UnicodeDecodeError: 'utf-8' codec can't decode byte" when non-Latin chars are used in project path (issue #3481)

  • New Account Management System (preview)
  • Open source PIO Remote client
  • Improved PIO Check with more accurate project processing
  • Echo what is typed when send_on_enter device monitor filter is used (issue #3452)
  • Fixed PIO Unit Testing for Zephyr RTOS
  • Fixed UnicodeDecodeError on Windows when network drive (NAS) is used (issue #3417)
  • Fixed an issue when saving libraries in new project results in error "No option 'lib_deps' in section" (issue #3442)
  • Fixed an incorrect node path used for pattern matching when processing middleware nodes
  • Fixed an issue with missing lib_extra_dirs option in SRC_LIST for CLion (issue #3460)

  • Fixed a SyntaxError "'return' with argument inside generator" for PIO Unified Debugger when Python 2.7 is used
  • Fixed an issue when lib_archive = no was not honored in "platformio.ini"
  • Fixed a TypeError "super(type, obj): obj must be an instance or subtype of type" when device monitor is used with a custom dev-platform filter (issue #3431)

•
Initial support for an official PlatformIO for CLion IDE plugin:
  • Smart C and C++ editor
  • Code refactoring
  • On-the-fly code analysis
  • "New PlatformIO Project" wizard
  • Building, Uploading, Testing
  • Integrated debugger (inline variable view, conditional breakpoints, expressions, watchpoints, peripheral registers, multi-thread support, etc.)

•
Device Monitor 2.0
  • Added PlatformIO Device Monitor Filter API (dev-platforms can extend base device monitor with a custom functionality, such as exception decoding) (pull #3383)
  • Configure project device monitor with monitor_filters option
  • Capture device monitor output to a file with log2file filter (issue #670)
  • Show a timestamp for each new line with time filter (issue #981)
  • Send a text to device on ENTER with send_on_enter filter (issue #926)
  • Show a hexadecimal representation of the data (code point of each character) with hexlify filter

  • New standalone (1-script) PlatformIO Core Installer
  • Initial support for Renode simulation framework (issue #3401)
  • Added support for Arm Mbed "module.json" dependencies field (issue #3400)
  • Improved support for Arduino "library.properties" depends field
  • Fixed an issue when quitting from PlatformIO IDE does not shutdown PIO Home server
  • Fixed an issue "the JSON object must be str, not 'bytes'" when PIO Home is used with Python 3.5 (issue #3396)
  • Fixed an issue when Python 2 does not keep encoding when converting ".ino" (issue #3393)
  • Fixed an issue when "libArchive": false in "library.json" does not work (issue #3403)
  • Fixed an issue when not all commands in compilation database "compile_commands.json" use absolute paths (pull #3415)
  • Fixed an issue when unknown transport is used for PIO Unit Testing engine (issue #3422)

  • Improved VSCode template with special forceInclude field for direct includes via -include flag (issue #3379)
  • Improved support of PIO Home on card-sized PC (Raspberry Pi, etc.) (issue #3313)
  • Froze "marshmallow" dependency to 2.X for Python 2 (issue #3380)
  • Fixed "TypeError: unsupported operand type(s)" when system environment variable is used by project configuration parser (issue #3377)
  • Fixed an issue when Library Dependency Finder (LDF) ignores custom "libLDFMode" and "libCompatMode" options in library.json
  • Fixed an issue when generating of compilation database "compile_commands.json" does not work with Python 2.7 (issue #3378)

•
PlatformIO Home 3.1:
  • Project Manager
  • Project Configuration UI for "platformio.ini"

•
PIO Check – automated code analysis without hassle:
•
Added support for PVS-Studio static code analyzer

•
Initial support for Project Manager CLI:
  • Show computed project configuration with a new platformio project config command or dump to JSON with platformio project config --json-output (issue #3335)
  • Moved platformio init command to platformio project init

  • Generate compilation database "compile_commands.json" (issue #2990)
  • Control debug flags and optimization level with a new debug_build_flags option
  • Install a dev-platform with ALL declared packages using a new --with-all-packages option for pio platform install command (issue #3345)
  • Added support for "pythonPackages" in platform.json manifest (PlatformIO Package Manager will install dependent Python packages from PyPi registry automatically when dev-platform is installed)
  • Handle project configuration (monitor, test, and upload options) for PIO Remote commands (issue #2591)
  • Added support for Arduino's library.properties depends field (issue #2781)
  • Autodetect monitor port for boards with specified HWIDs (issue #3349)
  • Updated SCons tool to 3.1.2
  • Updated Unity tool to 2.5.0
  • Made package ManifestSchema compatible with marshmallow >= 3 (issue #3296)
  • Warn about broken library manifest when scanning dependencies (issue #3268)
  • Do not overwrite custom items in VSCode's "extensions.json" (issue #3374)
  • Fixed an issue when env.BoardConfig() does not work for custom boards in extra scripts of libraries (issue #3264)
  • Fixed an issue with "start-group/end-group" linker flags on Native development platform (issue #3282)
  • Fixed default PIO Unified Debugger configuration for J-Link probe
  • Fixed an issue with LDF when header files not found if "libdeps_dir" is within a subdirectory of "lib_extra_dirs" (issue #3311)
  • Fixed an issue "Import of non-existent variable 'projenv''" when development platform does not call "env.BuildProgram()" (issue #3315)
  • Fixed an issue when invalid CLI command does not return non-zero exit code
  • Fixed an issue when Project Inspector crashes when flash use > 100% (issue #3368)
  • Fixed a "UnicodeDecodeError" when listing built-in libraries on macOS with Python 2.7 (issue #3370)
  • Fixed an issue with improperly handled compiler flags with space symbols in VSCode template (issue #3364)
  • Fixed an issue when no error is raised if referred parameter (interpolation) is missing in a project configuration file (issue #3279)

•
PIO Check – automated code analysis without hassle:
  • Potential NULL pointer dereferences
  • Possible indexing beyond array bounds
  • Suspicious assignments
  • Reads of potentially uninitialized objects
  • Unused variables or functions
  • Out of scope memory usage.

•
PlatformIO Home 3.0:
  • Project Inspection
  • Static Code Analysis
  • Firmware File Explorer
  • Firmware Memory Inspection
  • Firmware Sections & Symbols Viewer.

  • Added support for Build Middlewares: configure custom build flags per specific file, skip any build nodes from a framework, replace build file with another on-the-fly, etc.
  • Extend project environment configuration in "platformio.ini" with other sections using a new extends option (issue #2953)
  • Generate .ccls LSP file for Emacs cross references, hierarchies, completion and semantic highlighting
  • Added --no-ansi flag for PIO Core to disable ANSI control characters
  • Added --shutdown-timeout option to PIO Home Server
  • Fixed an issue with project generator for CLion IDE when 2 environments were used (issue #2824)
  • Fixed default PIO Unified Debugger configuration for J-Link probe
  • Fixed an issue when configuration file options partly ignored when using custom --project-conf (issue #3034)
  • Fixed an issue when installing a package using custom Git tag and submodules were not updated correctly (issue #3060)
  • Fixed an issue with linking process when $LDSCRIPT contains a space in path
  • Fixed security issue when extracting items from TAR archive (issue #2995)
  • Fixed an issue with project generator when src_build_flags were not respected (issue #3137)
  • Fixed an issue when booleans in "platformio.ini" are not parsed properly (issue #3022)
  • Fixed an issue with invalid encoding when generating project for Visual Studio (issue #3183)
  • Fixed an issue when Project Config Parser does not remove in-line comments when Python 3 is used (issue #3213)
  • Fixed an issue with a GCC Linter for PlatformIO IDE for Atom (issue #3218)

  • Added support for multi-environment PlatformIO project for CLion IDE (issue #2824)
  • Generate .ccls LSP file for Vim cross references, hierarchies, completion and semantic highlighting (issue #2952)
  • Added support for PLATFORMIO_DISABLE_COLOR system environment variable which disables color ANSI-codes in a terminal output (issue #2956)
  • Updated SCons tool to 3.1.1
  • Remove ProjectConfig cache when "platformio.ini" was modified outside
  • Fixed an issue with PIO Unified Debugger on Windows OS when debug server is piped
  • Fixed an issue when --upload-port CLI flag does not override declared upload_port option in "platformio.ini" (Project Configuration File)

•
Fixed an issue with a broken LDF when checking for framework compatibility (issue #2940)

  • Print debug tool name for the active debugging session
  • Do not shutdown PIO Home Server for "upgrade" operations (issue #2784)
  • Improved computing of project check sum (structure, configuration) and avoid unnecessary rebuilding
  • Improved printing of tabulated results
  • Automatically normalize file system paths to UNIX-style for Project Generator (issue #2857)
  • Ability to set "databaseFilename" for VSCode and C/C++ extension (issue #2825)
  • Renamed "enable_ssl" setting to strict_ssl
  • Fixed an issue with incorrect escaping of Windows slashes when using PIO Unified Debugger and "piped" openOCD
  • Fixed an issue when "debug", "home", "run", and "test" commands were not shown in "platformio --help" CLI
  • Fixed an issue with PIO Home's "No JSON object could be decoded" (issue #2823)
  • Fixed an issue when library.json had priority over project configuration for LDF (issue #2867)

Migration Guide from 3.0 to 4.0.

•
PlatformIO Plus Goes Open Source
  • Built-in PIO Unified Debugger
  • Built-in PIO Unit Testing

•
Project Configuration
  • New project configuration parser with a strict options typing (API)
  • Unified workspace storage (workspace_dir -> .pio) for PlatformIO Build System, Library Manager, and other internal services (issue #1778)
  • Share common (global) options between project environments using [env] section (issue #1643)
  • Include external configuration files with extra_configs option (issue #1590)
  • Custom project ***_dir options declared in platformio section have higher priority than Environment variables
  • Added support for Unix shell-style wildcards for monitor_port option (issue #2541)
  • Added new monitor_flags option which allows passing extra flags and options to platformio device monitor command (issue #2165)
  • Added support for PLATFORMIO_DEFAULT_ENVS system environment variable (issue #1967)
  • Added support for shared_dir where you can place an extra files (extra scripts, LD scripts, etc.) which should be transferred to a PIO Remote machine

•
Library Management
  • Switched to workspace .pio/libdeps folder for project dependencies instead of .piolibdeps
  • Save libraries passed to platformio lib install command into the project dependency list (lib_deps) with a new --save flag (issue #1028)
  • Install all project dependencies declared via lib_deps option using a simple platformio lib install command (issue #2147)
  • Use isolated library dependency storage per project build environment (issue #1696)
  • Look firstly in built-in library storages for a missing dependency instead of PlatformIO Registry (issue #1654)
  • Override default source and include directories for a library via library.json manifest using includeDir and srcDir fields
  • Fixed an issue when library keeps reinstalling for non-latin path (issue #1252)
  • Fixed an issue when lib_compat_mode = strict does not ignore libraries incompatible with a project framework

•
Build System
  • Switched to workspace .pio/build folder for build artifacts instead of .pioenvs
  • Switch between Build Configurations (release and debug) with a new project configuration option build_type
  • Custom platform_packages per a build environment with an option to override default (issue #1367)
  • Print platform package details, such as version, VSC source and commit (issue #2155)
  • Control a number of parallel build jobs with a new -j, --jobs option
  • Override default "platformio.ini" (Project Configuration File) with a custom using -c, --project-conf option for platformio run, platformio debug, or platformio test commands (issue #1913)
  • Override default development platform upload command with a custom upload_command (issue #2599)
  • Configure a shared folder for the derived files (objects, firmwares, ELFs) from a build system using build_cache_dir option (issue #2674)
  • Fixed an issue when -U in build_flags does not remove macro previously defined via -D flag (issue #2508)

•
Infrastructure
  • Python 3 support (issue #895)
  • Significantly speedup back-end for PIO Home. It works super fast now!
  • Added support for the latest Python "Click" package (CLI) (issue #349)
  • Added options to override default locations used by PlatformIO Core (core_dir, globallib_dir, platforms_dir, packages_dir, cache_dir) (issue #1615)
  • Removed line-buffering from platformio run command which was leading to omitting progress bar from upload tools (issue #856)
  • Fixed numerous issues related to "UnicodeDecodeError" and international locales, or when project path contains non-ASCII chars (issue #143, issue #1342, issue #1959, issue #2100)

•
Integration
  • Support custom CMake configuration for CLion IDE using CMakeListsUser.txt file
  • Fixed an issue with hardcoded C standard version when generating project for CLion IDE (issue #2527)
  • Fixed an issue with Project Generator when an include path search order is inconsistent to what passed to the compiler (issue #2509)
  • Fixed an issue when generating invalid "Eclipse CDT Cross GCC Built-in Compiler Settings" if a custom PLATFORMIO_CORE_DIR is used (issue #806)

•
Miscellaneous
  • Deprecated --only-check PlatformIO Core CLI option for "update" sub-commands, please use --dry-run instead
  • Fixed "systemd-udevd" warnings in 99-platformio-udev.rules (issue #2442)
  • Fixed an issue when package cache (Library Manager) expires too fast (issue #2559)


  • PIO Unified Debugger: improved debugging in debug_load_mode = modified and fixed an issue with useless project rebuilding
  • Project Generator: fixed a VSCode C/C++'s "Cannot find" warning when CPPPATH folder does not exist
  • Fixed an "IndexError: list index out of range" for Arduino sketch preprocessor (issue #2268)
  • Fixed an issue when invalid "env_default" in "platformio.ini" (Project Configuration File) results into unhandled errors (issue #2265)

  • Project Generator: fixed a warning "Property !!! WARNING !!! is not allowed" for VSCode (issue #2243)
  • Fixed an issue when PlatformIO Build System does not pick up "mbed_lib.json" files from libraries (issue #2164)
  • Fixed an error with conflicting declaration of a prototype (Arduino sketch preprocessor)
  • Fixed "FileExistsError" when platformio ci command is used in pair with --keep-build-dir option
  • Fixed an issue with incorrect order of project "include" and "src" paths in CPPPATH (issue #1914)

  • Project Generator: added new targets for CLion IDE "BUILD_VERBOSE" and "MONITOR" (serial port monitor) (issue #359)
  • Fixed an issue with slow updating of PlatformIO Core packages on Windows
  • Fixed an issue when platformio ci recompiles project if --keep-build-dir option is passed (issue #2109)
  • Fixed an issue when $PROJECT_HASH template was not expanded for the other directory ***_dir options in "platformio.ini" (Project Configuration File) (issue #2170)

•
Improved Project Generator for IDEs:
  • Use full path to PlatformIO CLI when generating a project (issue #1674)
  • CLion: Improved project portability using "${CMAKE_CURRENT_LIST_DIR}" instead of full path
  • Eclipse: Provide language standard to a project C/C++ indexer (issue #1010)

  • Fixed an issue with incorrect detecting of compatibility (LDF) between generic library and Arduino or ARM mbed frameworks
  • Fixed "Runtime Error: Dictionary size changed during iteration" (issue #2003)
  • Fixed an error "Could not extract item..." when extracting TAR archive with symbolic items on Windows platform (issue #2015)

  • Ignore *.asm and *.ASM files when building Arduino-based library (compatibility with Arduino builder)
  • Fixed spurious project's "Problems" for PlatformIO IDE for VSCode when ARM mbed framework is used
  • Fixed an issue with a broken headers list when generating ".clang_complete" for Emacs (issue #1960)

  • Improved IntelliSense for PlatformIO IDE for VSCode via passing extra compiler information for C/C++ Code Parser (resolves issues with spurious project's "Problems")
  • Fixed an issue with VSCode IntelliSense warning about the missed headers located in include folder
  • Fixed incorrect wording when initializing/updating project
  • Fixed an issue with incorrect order for library dependencies CPPPATH (issue #1914)
  • Fixed an issue when Library Dependency Finder (LDF) does not handle project src_filter (issue #1905)
  • Fixed an issue when Library Dependency Finder (LDF) finds spurious dependencies in chain+ and deep+ modes (issue #1930)

  • Generate an include and test directories with a README file when initializing a new project
  • Support in-line comments for multi-line value (lib_deps, build_flags, etc) in "platformio.ini" (Project Configuration File)
  • Added $PROJECT_HASH template variable for build_dir. One of the use cases is setting a global storage for project artifacts using PLATFORMIO_BUILD_DIR system environment variable. For example, /tmp/pio-build/$PROJECT_HASH (Unix) or $[sysenv.TEMP}/pio-build/$PROJECT_HASH (Windows)
  • Improved a loading speed of PIO Home "Recent News"
  • Improved PIO Unified Debugger for "mbed" framework and fixed issue with missed local variables
  • Introduced "Release" and "Debug" Build Configurations
  • Build project in "Debug Mode" including debugging information with a new debug target using platformio run command or targets option in platformio.ini. The last option allows avoiding project rebuilding between "Run/Debug" modes. (issue #1833)
  • Process build_unflags for the cloned environment when building a static library
  • Report on outdated 99-platformio-udev.rules (issue #1823)
  • Show a valid error when the Internet is off-line while initializing a new project (issue #1784)
  • Do not re-create ".gitignore" and ".travis.yml" files if they were removed from a project
  • Fixed an issue when dynamic build flags were not handled correctly (issue #1799)
  • Fixed an issue when pio run -t monitor always uses the first monitor_port even with multiple environments (issue #1841)
  • Fixed an issue with broken includes when generating .clang_complete and space is used in a path (issue #1873)
  • Fixed an issue with incorrect handling of a custom package name when using platformio lib install or platformio platform install commands

•
Program Memory Usage
  • Print human-readable memory usage information after a build and before uploading
  • Print detailed memory usage information with "sections" and "addresses" in verbose mode
  • Check maximum allowed "program" and "data" sizes before uploading/programming (issue #1412)

•
PIO Unit Testing:
  • Documented Project Shared Code
  • Force building of project source code using test_build_project_src option
  • Fixed missed UNIT_TEST macro for unit test components/libraries

  • Check package structure after unpacking and raise error when antivirus tool blocks PlatformIO package manager (issue #1462)
  • Lock interprocess requests to PlatformIO Package Manager for install/uninstall operations (issue #1594)
  • Fixed an issue with PIO Remote when upload process depends on the source code of a project framework
  • Fixed an issue when srcFilter field in library.json breaks a library build (issue #1735)

  • Improved removing of default build flags using build_unflags option (issue #1712)
  • Export LIBS, LIBPATH, and LINKFLAGS data from project dependent libraries to the global build environment
  • Don't export CPPPATH data of project dependent libraries to framework's build environment (issue #1665)
  • Handle "architectures" data from "library.properties" manifest in lib_compat_mode = strict
  • Added workaround for Python SemVer package's issue #61 with caret range and pre-releases
  • Replaced conflicted "env" pattern by "sysenv" for "platformio.ini" Dynamic Variables" (issue #1705)
  • Removed "date&time" when processing project with platformio run command (issue #1343)
  • Fixed issue with invalid LD script if path contains space
  • Fixed preprocessor for Arduino sketch when function returns certain type (issue #1683)
  • Fixed issue when platformio lib uninstall removes initial source code (issue #1023)

•
PlatformIO Home - interact with PlatformIO ecosystem using modern and cross-platform GUI:
  • "Recent News" block on "Welcome" page
  • Direct import of development platform's example

  • Simplify configuration for PIO Unit Testing: separate main program from a test build process, drop requirement for #ifdef UNIT_TEST guard
  • Override any option from board manifest in "platformio.ini" (Project Configuration File) (issue #1612)
  • Configure a custom path to SVD file using debug_svd_path option
  • Custom project description which will be used by PlatformIO Home
  • Updated Unity tool to 2.4.3
  • Improved support for Black Magic Probe in "uploader" mode
  • Renamed "monitor_baud" option to "monitor_speed"
  • Fixed issue when a custom lib_dir was not handled correctly (issue #1473)
  • Fixed issue with useless project rebuilding for case insensitive file systems (Windows)
  • Fixed issue with build_unflags option when a macro contains value (e.g., -DNAME=VALUE)
  • Fixed issue which did not allow to override runtime build environment using extra POST script
  • Fixed "RuntimeError: maximum recursion depth exceeded" for library manager (issue #1528)

•
PlatformIO Home - interact with PlatformIO ecosystem using modern and cross-platform GUI:
  • Multiple themes (Dark & Light)
  • Ability to specify a name for new project

  • Control PIO Unified Debugger and its firmware loading mode using debug_load_mode option
  • Added aliases (off, light, strict) for LDF Compatibility Mode
  • Search for a library using PIO Library Registry ID id:X (e.g. pio lib search id:13)
  • Show device system information (MCU, Frequency, RAM, Flash, Debugging tools) in a build log
  • Show all available upload protocols before firmware uploading in a build log
  • Handle "os.mbed.com" URL as a Mercurial (hg) repository
  • Improved support for old mbed libraries without manifest
  • Fixed project generator for Qt Creator IDE (issue #1303, issue #1323)
  • Mark project source and library directories for CLion IDE (issue #1359, issue #1345, issue #897)
  • Fixed issue with duplicated "include" records when generating data for IDE (issue #1301)

  • New test_speed option to control a communication baudrate/speed between PIO Unit Testing engine and a target device (issue #1273)
  • Show full library version in "Library Dependency Graph" including VCS information (issue #1274)
  • Configure a custom firmware/program name in build directory (example)
  • Renamed envs_dir option to build_dir in "platformio.ini" (Project Configuration File)
  • Refactored code without "arrow" dependency (resolve issue with "ImportError: No module named backports.functools_lru_cache")
  • Improved support of PIO Unified Debugger for Eclipse Oxygen
  • Improved a work in off-line mode
  • Fixed project generator for CLion and Qt Creator IDE (issue #1299)
  • Fixed PIO Unified Debugger for mbed framework
  • Fixed library updates when a version is declared in VCS format (not SemVer)

•
PlatformIO Home - interact with PlatformIO ecosystem using modern and cross-platform GUI:
•
Library Manager:
  • Search for new libraries in PlatformIO Registry
  • "1-click" library installation, per-project libraries, extra storages
  • List installed libraries in multiple storages
  • List built-in libraries (by frameworks)
  • Updates for installed libraries
  • Multiple examples, trending libraries, and more.

  • PlatformIO Projects
  • PIO Account
  • Development platforms, frameworks and board explorer
  • Device Manager: serial, logical, and multicast DNS services

  • Integration with Jenkins CI
  • New include folder for project's header files (issue #1107)
  • Depend on development platform using VCS URL (Git, Mercurial and Subversion) instead of a name in "platformio.ini" (Project Configuration File). Drop support for *_stage dev/platform names (use VCS URL instead).
  • Reinstall/redownload package with a new -f, --force option for platformio lib install and platformio platform install commands (issue #778)
  • Handle missed dependencies and provide a solution based on PlatformIO Library Registry (issue #781)
  • New setting projects_dir that allows to override a default PIO Home Projects location (issue #1161)
  • Library Dependency Finder (LDF):
  • Search for dependencies used in PIO Unit Testing (issue #953)
  • Parse library source file in pair with a header when they have the same name (issue #1175)
  • Handle library dependencies defined as VCS or SemVer in "platformio.ini" (Project Configuration File) (issue #1155)
  • Added option to configure library Compatible Mode using library.json

•
New options for platformio device list command:
  • --serial list available serial ports (default)
  • --logical list logical devices
  • --mdns discover multicast DNS services (issue #463)

  • Fixed platforms, packages, and libraries updating behind proxy (issue #1061)
  • Fixed missing toolchain include paths for project generator (issue #1154)
  • Fixed "Super-Quick (Mac / Linux)" installation in "get-platformio.py" script (issue #1017)
  • Fixed "get-platformio.py" script which hangs on Windows 10 (issue #1118)
  • Other bug fixes and performance improvements

  • Pre/Post extra scripting for advanced control of PIO Build System (issue #891)
  • New lib_archive option to control library archiving and linking behavior (issue #993)
  • Add "inc" folder automatically to CPPPATH when "src" is available (works for project and library) (issue #1003)
  • Use a root of library when filtering source code using library.json and srcFilter field
  • Added monitor_* options to white-list for "platformio.ini" (Project Configuration File) (issue #982)
  • Do not ask for board ID when initialize project for desktop platform
  • Handle broken PIO Core state and create new one
  • Fixed an issue with a custom transport for PIO Unit Testing when multiple tests are present
  • Fixed an issue when can not upload firmware to SAM-BA based board (Due)

•
PIO Unified Debugger
  • "1-click" solution, zero configuration
  • Support for 100+ embedded boards
  • Multiple architectures and development platforms
  • Windows, MacOS, Linux (+ARMv6-8)
  • Built-in into PlatformIO IDE for Atom and PlatformIO IDE for VScode
  • Integration with Eclipse and Sublime Text

  • Filter PIO Unit Testing tests using a new test_filter option in "platformio.ini" (Project Configuration File) or platformio test --filter command (issue #934)
  • Custom test_transport for PIO Unit Testing Engine
  • Configure Serial Port Monitor in "platformio.ini" (Project Configuration File) (issue #787)
  • New monitor target which allows to launch Serial Monitor automatically after successful "build" or "upload" operations (issue #788)
  • Project generator for VIM
  • Multi-line support for the different options in "platformio.ini" (Project Configuration File), such as: build_flags, build_unflags, etc. (issue #889)
  • Handle dynamic SRC_FILTER environment variable from library.json extra script
  • Notify about multiple installations of PIO Core (issue #961)
  • Improved auto-detecting of mbed-enabled media disks
  • Automatically update Git-submodules for development platforms and libraries that were installed from repository
  • Add support for .*cc extension (issue #939)
  • Handle env_default in "platformio.ini" (Project Configuration File) when re-initializing a project (issue #950)
  • Use root directory for PIO Home when path contains non-ascii characters (issue #951, issue #952)
  • Don't warn about known boards_dir option (pull #949)
  • Escape non-valid file name characters when installing a new package (library) (issue #985)
  • Fixed infinite dependency installing when repository consists of multiple libraries (issue #935)
  • Fixed linter error "unity.h does not exist" for Unit Testing (issue #947)
  • Fixed issue when Library Dependency Finder (LDF) does not handle custom src_dir (issue #942)
  • Fixed cloning a package (library) from a private Git repository with custom user name and SSH port (issue #925)

•
Hotfix for recently updated Python Requests package (2.16.0)

•
PlatformIO Library Registry statistics with new pio lib stats command
  • Recently updated and added libraries
  • Recent and popular keywords
  • Featured libraries (today, week, month)

  • List built-in libraries based on development platforms with a new pio lib builtin command
  • Show detailed info about a library using pio lib show command (issue #430)
  • List supported frameworks, SDKs with a new pio platform frameworks command
  • Visual Studio Code extension for PlatformIO (issue #619)
  • Added new options --no-reset, --monitor-rts and --monitor-dtr to pio test command (allows to avoid automatic board's auto-reset when gathering test results)
  • Added support for templated methods in *.ino to *.cpp converter (pull #858)
  • Package version as "Repository URL" in manifest of development version ("version": "https://github.com/user/repo.git")
  • Produce less noisy output when -s/--silent options are used for platformio init and platformio run commands (issue #850)
  • Use C++11 by default for CLion IDE based projects (pull #873)
  • Escape project path when Glob matching is used
  • Do not overwrite project configuration variables when system environment variables are set
  • Handle dependencies when installing non-registry package/library (VCS, archive, local folder) (issue #913)
  • Fixed package installing with VCS branch for Python 2.7.3 (issue #885)

•
Changed default LDF Mode from chain+ to chain

•
PIO Remote™. Your devices are always with you!
  • Over-The-Air (OTA) Device Manager
  • OTA Serial Port Monitor
  • OTA Firmware Updates
  • Continuous Deployment
  • Continuous Delivery

•
Integration with Cloud IDEs
  • Cloud9
  • Codeanywhere
  • Eclipse Che

  • PIO Account and PLATFORMIO_AUTH_TOKEN environment variable for CI systems (issue #808, issue #467)
  • Inject system environment variables to configuration settings in "platformio.ini" (Project Configuration File) (issue #792)
  • Custom boards per project with boards_dir option in "platformio.ini" (Project Configuration File) (issue #515)
  • Unix shell-style wildcards for upload_port (issue #839)
  • Refactored Library Dependency Finder (LDF) C/C++ Preprocessor for conditional syntax (#ifdef, #if, #else, #elif, #define, etc.) (issue #837)
  • Added new LDF Modes: chain+ and deep+ and set chain+ as default
  • Added global lib_extra_dirs option to [platformio] section for "platformio.ini" (Project Configuration File) (issue #842)
  • Enabled caching by default for API requests and Library Manager (see enable_cache setting)
  • Native integration with VIM/Neovim using neomake-platformio plugin
  • Changed a default exit combination for Device Monitor from Ctrl+] to Ctrl+C
  • Improved detecting of ARM mbed media disk for uploading
  • Improved Project Generator for CLion IDE when source folder contains nested items
  • Improved handling of library dependencies specified in library.json manifest (issue #814)
  • Improved Library Dependency Finder (LDF) for circular dependencies
  • Show vendor version of a package for platformio platform show command (issue #838)
  • Fixed unable to include SSH user in lib_deps repository url (issue #830)
  • Fixed merging of ".gitignore" files when re-initialize project (issue #848)
  • Fixed issue with PATH auto-configuring for upload tools
  • Fixed 99-platformio-udev.rules checker for Linux OS

  • New! Dynamic variables/templates for "platformio.ini" (Project Configuration File) (issue #705)
  • Summary about processed environments (issue #777)
  • Implemented LocalCache system for API and improved a work in off-line mode
  • Improved Project Generator when custom --project-option is passed to platformio init command
  • Deprecated lib_force option, please use lib_deps instead
  • Return valid exit code from plaformio test command
  • Fixed Project Generator for CLion IDE using Windows OS (issue #785)
  • Fixed SSL Server-Name-Indication for Python < 2.7.9 (issue #774)

•
Disabled temporary SSL for PlatformIO services (issue #772)

•
PlatformIO Plus
•
Local and Embedded Unit Testing (issue #408, issue #519)

•
Decentralized Development Platforms
  • Development platform manifest "platform.json" and open source development platforms
  • Semantic Versioning for platform commands, development platforms and dependent packages
  • Custom package repositories
  • External embedded board configuration files, isolated build scripts (issue #479)
  • Embedded Board compatibility with more than one development platform (issue #456)

•
Library Manager 3.0
  • Project dependencies per build environment using lib_deps option (issue #413)
  • Semantic Versioning for library commands and dependencies (issue #410)
  • Multiple library storages: Project's Local, PlatformIO's Global or Custom (issue #475)
  • Install library by name (issue #414)
  • Depend on a library using VCS URL (GitHub, Git, ARM mbed code registry, Hg, SVN) (issue #498)
  • Strict search for library dependencies (issue #588)
  • Allowed library.json to specify sources other than PlatformIO's Repository (issue #461)
  • Search libraries by headers/includes with platformio lib search --header option

•
New Intelligent Library Build System
  • Library Dependency Finder that interprets C/C++ Preprocessor conditional macros with deep search behavior
  • Check library compatibility with project environment before building (issue #415)
  • Control Library Dependency Finder for compatibility using lib_compat_mode option
  • Custom library storages/directories with lib_extra_dirs option (issue #537)
  • Handle extra build flags, source filters and build script from library.json (issue #289)
  • Allowed to disable library archiving (*.ar) (issue #719)
  • Show detailed build information about dependent libraries (issue #617)
  • Support for the 3rd party manifests (Arduino IDE "library.properties" and ARM mbed "module.json")

  • Removed enable_prompts setting. Now, all PlatformIO CLI is non-blocking!
  • Switched to SSL PlatformIO API
  • Renamed platformio serialports command to platformio device
  • Build System: Attach custom Before/Pre and After/Post actions for targets (issue #542)
  • Allowed passing custom project configuration options to platformio ci and platformio init commands using -O, --project-option.
  • Print human-readable information when processing environments without -v, --verbose option (issue #721)
  • Improved INO to CPP converter (issue #659, issue #765)
  • Added license field to library.json (issue #522)
  • Warn about unknown options in project configuration file platformio.ini (issue #740)
  • Fixed wrong line number for INO file when #warning directive is used (issue #742)
  • Stopped supporting Python 2.6

  • Improved support for Microchip PIC32 development platform and ChipKIT boards (issue #438)
  • Added support for Pinoccio Scout board (issue #52)
  • Added support for Teensy USB Features (HID, SERIAL_HID, DISK, DISK_SDFLASH, MIDI, etc.) (issue #722)
  • Switched to built-in GCC LwIP library for Espressif development platform
  • Added support for local --echo for Serial Port Monitor (issue #733)
  • Updated udev rules for the new STM32F407DISCOVERY boards (issue #731)
  • Implemented firmware merging with base firmware for Nordic nRF51 development platform (issue #500, issue #533)
  • Fixed Project Generator for ESP8266 and ARM mbed based projects (resolves incorrect linter errors)
  • Fixed broken LD Script for Element14 chipKIT Pi board (issue #725)
  • Fixed firmware uploading to Atmel SAMD21-XPRO board using ARM mbed framework (issue #732)

  • Added support for Arduino M0, M0 Pro and Tian boards (issue #472)
  • Added support for Microchip chipKIT Lenny board
  • Updated Microchip PIC32 Arduino framework to v1.2.1
  • Documented uploading of EEPROM data (from EEMEM directive)
  • Added Rebuild C/C++ Project Index target to CLion and Eclipse IDEs
  • Improved project generator for CLion IDE
  • Added udev rules for OpenOCD CMSIS-DAP adapters (issue #718)
  • Auto-remove project cache when PlatformIO is upgraded
  • Keep user changes for .gitignore file when re-generate/update project data
  • Ignore [platformio] section from custom project configuration file when platformio ci --project-conf command is used
  • Fixed missed --boot flag for the firmware uploader for ATSAM3X8E Cortex-M3 MCU based boards (Arduino Due, etc) (issue #710)
  • Fixed missing trailing \ for the source files list when generate project for Qt Creator IDE (issue #711)
  • Split source files to HEADERS and SOURCES when generate project for Qt Creator IDE (issue #713)

  • New ESP8266-based boards: Generic ESP8285 Module, Phoenix 1.0 & 2.0, WifInfo
  • Added support for Arduino M0 Pro board (issue #472)
  • Added support for Arduino MKR1000 board (issue #620)
  • Added support for Adafruit Feather M0, SparkFun SAMD21 and SparkFun SAMD21 Mini Breakout boards (issue #520)
  • Updated Arduino ESP8266 core for Espressif platform to 2.3.0
  • Better removing unnecessary flags using build_unflags option (issue #698)
  • Fixed issue with platformio init --ide command for Python 2.6

•
Fixed issue with platformio init --ide command

  • Added support for ST Nucleo L031K6 board to ARM mbed framework
  • Process build_unflags option for ARM mbed framework
  • Updated Intel ARC32 Arduino framework to v1.0.6 (issue #695)
  • Improved a check of program size before uploading to the board
  • Fixed issue with ARM mbed framework -u _printf_float and -u _scanf_float when parsing $LINKFLAGS
  • Fixed issue with ARM mbed framework and extra includes for the custom boards, such as Seeeduino Arch Pro

•
Re-submit a package to PyPI

  • Added support for emonPi, the OpenEnergyMonitor system (issue #687)
  • Added support for SPL framework for STM32F0 boards (issue #683)
  • Added support for Arduboy DevKit, the game system the size of a credit card
  • Updated ARM mbed framework package to v121
  • Check program size before uploading to the board (issue #689)
  • Improved firmware uploading to Arduino Leonardo based boards (issue #691)
  • Fixed issue with -L relative/path when parsing build_flags (issue #688)

•
Show udev warning only for the Linux OS while uploading firmware

  • Added support for Arduboy, the game system the size of a credit card
  • Updated 99-platformio-udev.rules for Linux OS
  • Refactored firmware uploading to the embedded boards with SAM-BA bootloader

  • Simplified Continuous Integration with AppVeyor (issue #671)
  • Automatically add source directory to CPPPATH of Build System
  • Added support for Silicon Labs SLSTK3401A (Pearl Gecko) and MultiTech mDot F411 ARM mbed based boards
  • Added support for MightyCore ATmega8535 board (issue #585)
  • Added stlink as the default uploader for STM32 Discovery boards (issue #665)
  • Use HTTP mirror for Package Manager in a case with SSL errors (issue #645)
  • Improved firmware uploading to Arduino Leonardo/Due based boards
  • Fixed bug with env_default when pio run -e is used
  • Fixed issue with src_filter option for Windows OS (issue #652)
  • Fixed configuration data for TI LaunchPads based on msp430fr4133 and msp430fr6989 MCUs (issue #676)
  • Fixed issue with ARM mbed framework and multiple definition errors on FRDM-KL46Z board (issue #641)
  • Fixed issue with ARM mbed framework when abstract class breaks compile for LPC1768 (issue #666)

•
Handle prototype pointers while converting *.ino to .cpp (issue #639)

  • Project generator for CodeBlocks IDE (issue #600)
  • New Lattice iCE40 FPGA development platform with support for Lattice iCEstick FPGA Evaluation Kit and BQ IceZUM Alhambra FPGA (issue #480)
  • New Intel ARC 32-bit development platform with support for Arduino/Genuino 101 board (issue #535)
  • New Microchip PIC32 development platform with support for 20+ different PIC32 based boards (issue #438)
  • New RTOS and build Framework named Simba (issue #412)
  • New boards for ARM mbed framework: ST Nucleo F410RB, ST Nucleo L073RZ and BBC micro:bit
  • Added support for Arduino.Org boards: Arduino Leonardo ETH, Arduino Yun Mini, Arduino Industrial 101 and Linino One (issue #472)
  • Added support for Generic ATTiny boards: ATTiny13, ATTiny24, ATTiny25, ATTiny45 and ATTiny85 (issue #636)
  • Added support for MightyCore boards: ATmega1284, ATmega644, ATmega324, ATmega164, ATmega32, ATmega16 and ATmega8535 (issue #585)
  • Added support for TI MSP430 boards: TI LaunchPad w/ msp430fr4133 and TI LaunchPad w/ msp430fr6989
  • Updated Arduino core for Espressif platform to 2.2.0 (issue #627)
  • Updated native SDK for ESP8266 to 1.5 (issue #366)
  • PlatformIO Library Registry in JSON format! Implemented --json-output and --page options for platformio lib search command (issue #604)
  • Allowed to specify default environments env_default which should be processed by default with platformio run command (issue #576)
  • Allowed to unflag(remove) base/initial flags using build_unflags option (issue #559)
  • Allowed multiple VID/PID pairs when detecting serial ports (issue #632)
  • Automatically add -DUSB_MANUFACTURER with vendor's name (issue #631)
  • Automatically reboot Teensy board after upload when Teensy Loader GUI is used (issue #609)
  • Refactored source code converter from *.ino to *.cpp (issue #610)
  • Forced -std=gnu++11 for Atmel SAM development platform (issue #601)
  • Don't check OS type for ARM mbed-enabled boards and ST STM32 development platform before uploading to disk (issue #596)
  • Fixed broken compilation for Atmel SAMD based boards except Arduino Due (issue #598)
  • Fixed firmware uploading using serial port with spaces in the path
  • Fixed cache system when project's root directory is used as src_dir (issue #635)

  • Launched PlatformIO Community Forums (issue #530)
  • Added support for ARM mbed-enabled board Seed Arch Max (STM32F407VET6) (issue #572)
  • Improved DNS lookup for PlatformIO API
  • Updated Arduino Wiring-based framework to the latest version for Atmel AVR/SAM development platforms
  • Updated "Teensy Loader CLI" and fixed uploading of large .hex files (issue #568)
  • Updated the support for Sanguino Boards (issue #586)
  • Better handling of used boards when re-initialize/update project
  • Improved support for non-Unicode user profiles for Windows OS
  • Disabled progress bar for download operations when prompts are disabled
  • Fixed multiple definition errors for ST STM32 development platform and ARM mbed framework (issue #571)
  • Fixed invalid board parameters (reset method and baudrate) for a few ESP8266 based boards
  • Fixed "KeyError: 'content-length'" in PlatformIO Download Manager (issue #591)

  • Project generator for NetBeans IDE (issue #541)
  • Created package for Homebrew Mac OS X Package Manager: brew install platformio (issue #395)
  • Updated Arduino core for Espressif platform to 2.1.0 (issue #544)
  • Added support for the ESP8266 ESP-07 board to Espressif (issue #527)
  • Improved handling of String-based CPPDEFINES passed to extra build_flags (issue #526)
  • Generate appropriate project for CLion IDE and CVS (issue #523)
  • Use src_dir directory from Project Configuration File platformio.ini when initializing project otherwise create base src directory (issue #536)
  • Fixed issue with incorrect handling of user's build flags where the base flags were passed after user's flags to GCC compiler (issue #528)
  • Fixed issue with Project Generator when optional build flags were passed using system environment variables: PLATFORMIO_BUILD_FLAGS or PLATFORMIO_BUILD_SRC_FLAGS
  • Fixed invalid detecting of compiler type (issue #550)
  • Fixed issue with updating package which was deleted manually by user (issue #555)
  • Fixed incorrect parsing of GCC -include flag (issue #552)

  • Added support for the new ESP8266-based boards (ESPDuino, ESP-WROOM-02, ESPresso Lite 1.0 & 2.0, SparkFun ESP8266 Thing Dev, ThaiEasyElec ESPino) to Espressif development platform
  • Added board_f_flash option to Project Configuration File platformio.ini which allows to specify custom flash chip frequency for Espressif development platform (issue #501)
  • Added board_flash_mode option to Project Configuration File platformio.ini which allows to specify custom flash chip mode for Espressif development platform
  • Handle new environment variables PLATFORMIO_UPLOAD_PORT and PLATFORMIO_UPLOAD_FLAGS (issue #518)
  • Fixed issue with CPPDEFINES which contain space and break PlatformIO IDE Linter (IDE issue #34)
  • Fixed unable to link C++ standard library to Espressif platform build (issue #503)
  • Fixed issue with pointer (char* myfunc()) while converting from *.ino to *.cpp (issue #506)

  • Better integration of PlatformIO Builder with PlatformIO IDE Linter
  • Fixed issue with removing temporary file while converting *.ino to *.cpp
  • Fixed missing dependency (mbed framework) for Atmel SAM development platform (issue #487)

  • Corrected RAM size for NXP LPC1768 based boards (issue #484)
  • Exclude only test and tests folders from build process
  • Reverted -Wl,-whole-archive hook for ST STM32 and mbed

•
Fixed a bug with Project Initialization in PlatformIO IDE

  • PlatformIO IDE for Atom (issue #470)
  • Added pio command line alias for platformio command (issue #447)
  • Added SPL-Framework support for Nucleo F401RE board (issue #453)
  • Added upload_resetmethod option to Project Configuration File platformio.ini which allows to specify custom upload reset method for Espressif development platform (issue #444)
  • Allowed to force output of color ANSI-codes or to disable progress bar even if the output is a pipe (not a tty) using Environment variables (issue #465)
  • Set 1Mb SPIFFS for Espressif boards by default (issue #458)
  • Exclude test* folder by default from build process
  • Generate project for IDEs with information about installed libraries
  • Fixed builder for mbed framework and ST STM32 platform

  • Initial support for Arduino Zero board (issue #356)
  • Added support for completions to Atom text editor using .clang_complete
  • Generate default targets for supported IDE (CLion, Eclipse IDE, Emacs, Sublime Text, VIM): Build, Clean, Upload, Upload SPIFFS image, Upload using Programmer, Update installed platforms and libraries (issue #427)
  • Updated Teensy Arduino Framework to 1.27 (issue #434)
  • Fixed uploading of EEPROM data using uploadeep target for Atmel AVR development platform
  • Fixed project generator for CLion IDE (issue #422)
  • Fixed package shasum validation on Mac OS X 10.11.2 (issue #429)
  • Fixed CMakeLists.txt add_executable has only one source file (issue #421)

Happy New Year!

  • Moved SCons to PlatformIO packages. PlatformIO does not require SCons to be installed in your system. Significantly simplified installation process of PlatformIO. pip install platformio rocks!
  • Implemented uploading files to file system of ESP8266 SPIFFS (including OTA) (issue #382)
  • Added support for the new Adafruit boards Bluefruit Micro and Feather (issue #403)
  • Added support for RFDuino (issue #319)
  • Project generator for Emacs text editor (pull #404)
  • Updated Arduino framework for Atmel AVR development platform to 1.6.7
  • Documented firmware uploading for Atmel AVR development platform using Programmers: AVR ISP, AVRISP mkII, USBtinyISP, USBasp, Parallel Programmer and Arduino as ISP
  • Fixed issue with current Python interpreter for Python-based tools (issue #417)

  • Restored support for Espressif ESP8266 ESP-01 1MB board (ready for OTA)
  • Fixed invalid ROM size for ESP8266-based boards (issue #396)

  • Removed SCons from requirements list. PlatformIO will try to install it automatically, otherwise users need to install it manually
  • Fixed ChunkedEncodingError when SF connection is broken (issue #356)

  • Added support for the new ESP8266-based boards (SparkFun ESP8266 Thing, NodeMCU 0.9 & 1.0, Olimex MOD-WIFI-ESP8266(-DEV), Adafruit HUZZAH ESP8266, ESPino, SweetPea ESP-210, WeMos D1, WeMos D1 mini) to Espressif development platform
  • Created public platformio-pkg-ldscripts repository for LD scripts. Moved common configuration for ESP8266 MCU to esp8266.flash.common.ld (issue #379)
  • Improved documentation for Espressif development platform: OTA update, custom Flash Size, Upload Speed and CPU frequency
  • Fixed reset method for Espressif NodeMCU (ESP-12E Module) (issue #380)
  • Fixed issue with code builder when build path contains spaces (issue #387)
  • Fixed project generator for Eclipse IDE and "duplicate path entries found in project path" (issue #383)

  • Install only required packages depending on build environment (issue #308)
  • Added support for Raspberry Pi WiringPi framework (issue #372)
  • Implemented Over The Air (OTA) upgrades for Espressif development platform. (issue #365)
  • Updated CMSIS framework and added CMSIS support for Nucleo F401RE board (issue #373)
  • Added support for Espressif ESP8266 ESP-01-1MB board (ready for OTA)
  • Handle upload_flags option in platformio.ini (issue #368)
  • Improved PlatformIO installation on the Mac OS X El Capitan

  • Improved code builder for parallel builds (up to 4 times faster than before)
  • Generate .travis.yml CI and .gitignore files for embedded projects by default (issue #354)
  • Removed prompt with "auto-uploading" from platformio init command and added --enable-auto-uploading option (issue #352)
  • Fixed incorrect behaviour of platformio serialports monitor in pair with PySerial 3.0

•
Restored PLATFORMIO macros with the current version

  • Added support for the new boards: Atmel ATSAMR21-XPRO, Atmel SAML21-XPRO-B, Atmel SAMD21-XPRO, ST 32F469IDISCOVERY, ST 32L476GDISCOVERY, ST Nucleo F031K6, ST Nucleo F042K6, ST Nucleo F303K8 and ST Nucleo L476RG
  • Updated Arduino core for Espressif platform to 2.0.0 (issue #345)
  • Added to FAQ explanation of Can not compile a library that compiles without issue with Arduino IDE (issue #331)
  • Fixed ESP-12E flash size (pull #333)
  • Fixed configuration for LowPowerLab MoteinoMEGA board (issue #335)
  • Fixed "LockFailed: failed to create appstate.json.lock" error for Windows
  • Fixed relative include path for preprocessor using build_flags (issue #271)

  • Added support of libOpenCM3 framework for Nucleo F103RB board (issue #309)
  • Added support for Espressif ESP8266 ESP-12E board (NodeMCU) (issue #310)
  • Added support for pySerial 3.0 (issue #307)
  • Updated Arduino AVR/SAM frameworks to 1.6.6 (issue #321)
  • Upload firmware using external programmer via platformio run --target program target (issue #311)
  • Fixed handling of upload port when board option is not specified in platformio.ini (issue #313)
  • Fixed firmware uploading for nordicrf51 development platform (issue #316)
  • Fixed installation on Mac OS X El Capitan (issue #312)
  • Fixed project generator for CLion IDE under Windows OS with invalid path to executable (issue #326)
  • Fixed empty list with serial ports on Mac OS X (isge #294)
  • Fixed compilation error TWI_Disable not declared for Arduino Due board (issue #329)

  • Full support of CLion IDE including code auto-completion (issue #132)
  • PlatformIO command completion in Terminal for bash and zsh
  • Added support for ubIQio Ardhat board (pull #302)
  • Install SCons automatically and avoid error: option --single-version-externally-managed not recognized (issue #279)
  • Use Teensy CLI Loader for upload of .hex files on Mac OS X (issue #306)
  • Fixed missing framework-mbed package for teensy platform (issue #305)

  • Added support for LightBlue Bean board (pull #292)
  • Added support for ST Nucleo F446RE board (pull #293)
  • Fixed broken lock file for "appstate" storage (issue #288)
  • Fixed ESP8266 compile errors about RAM size when adding 1 library (issue #296)

  • Allowed to use ST-Link uploader for mbed-based projects
  • Explained how to use lib directory from the PlatformIO based project in readme.txt which will be automatically generated using platformio init command (issue #273)
  • Found solution for "pip/scons error: option --single-version-externally-managed not recognized" when install PlatformIO using pip package manager (issue #279)
  • Fixed firmware uploading to Arduino Leonardo board using Mac OS (issue #287)
  • Fixed SConsNotInstalled error for Linux Debian-based distributives

•
Fixed critical issue when platformio init --ide command hangs PlatformIO (issue #283)

  • Added native, linux_arm, linux_i686, linux_x86_64, windows_x86 development platforms (issue #263)
  • Added PlatformIO Demo page to documentation
  • Simplified installation process of PlatformIO (issue #274)
  • Significantly improved Project Generator which allows to integrate with the most popular IDE
  • Added short -h help option for PlatformIO and sub-commands
  • Updated mbed framework
  • Updated tool-teensy package for Teensy platform (issue #268)
  • Added FAQ answer when Program "platformio" not found in PATH (issue #272)
  • Generate "readme.txt" for project "lib" directory (issue #273)
  • Use toolchain's includes pattern include* for Project Generator (issue #277)
  • Added support for Adafruit Gemma board to atmelavr platform (pull #256)
  • Fixed includes list for Windows OS when generating project for Eclipse IDE (issue #270)
  • Fixed AttributeError: 'module' object has no attribute 'packages' (issue #252)

  • Integration with Atom IDE
  • Support for off-line/unpublished/private libraries (issue #260)
  • Disable project auto-clean while building/uploading firmware using platformio run --disable-auto-clean option (issue #255)
  • Show internal errors from "Miniterm" using platformio serialports monitor command (issue #257)
  • Fixed platformio serialports monitor --help information with HEX char for hotkeys (issue #253)
  • Handle "OSError: [Errno 13] Permission denied" for PlatformIO installer script (issue #254)

  • Project generator for CLion IDE (issue #132)
  • Updated tool-bossac package to 1.5 version for atmelsam platform (issue #251)
  • Updated sdk-esp8266 package for espressif platform
  • Fixed incorrect arguments handling for platformio serialports monitor command (issue #248)

  • Allowed to exclude/include source files from build process using src_filter (issue #240)
  • Launch own extra script before firmware building/uploading processes (issue #239)
  • Specify own path to the linker script (ld) using build_flags option (issue #233)
  • Specify library compatibility with the all platforms/frameworks using * symbol in library.json
  • Added support for new embedded boards: ST 32L0538DISCOVERY and Delta DFCM-NNN40 to Framework mbed
  • Updated packages for Framework Arduino (AVR, SAM, Espressif and Teensy cores, Framework mbed, Espressif ESP8266 SDK (issue #246)
  • Fixed stk500v2_command(): command failed (issue #238)
  • Fixed IDE project generator when board is specified (issue #242)
  • Fixed relative path for includes when generating project for IDE (issue #243)
  • Fixed ESP8266 native SDK exception (issue #245)

•
Fixed broken link to SCons installer

  • Automatically detect upload port using VID:PID board settings (issue #231)
  • Improved detection of build changes
  • Avoided LibInstallDependencyError when more than 1 library is found (issue #229)

  • Added Silicon Labs EFM32 siliconlabsefm32 development platform (issue #226)
  • Integrate PlatformIO with Circle CI and Shippable CI
  • Described in documentation how to create/register own board for PlatformIO
  • Disabled "nano.specs" for ARM-based platforms (issue #219)
  • Fixed "ConnectionError" when PlatformIO SF Storage is off-line
  • Fixed resolving of C/C++ std libs by Eclipse IDE (issue #220)
  • Fixed firmware uploading using USB programmer (USBasp) for atmelavr platform (issue #221)

•
Fixed libraries order for "Library Dependency Finder" under Linux OS

  • Handle new environment variable PLATFORMIO_BUILD_FLAGS
  • Pass to API requests information about Continuous Integration system. This information will be used by PlatformIO-API.
  • Use include directories from toolchain when initialising project for IDE (issue #210)
  • Added support for new WildFire boards from Wicked Device to atmelavr platform
  • Updated Arduino Framework to 1.6.4 version (issue #212)
  • Handle Atmel AVR Symbols when initialising project for IDE (issue #216)
  • Fixed bug with converting *.ino to *.cpp
  • Fixed failing with platformio init --ide eclipse without boards (issue #217)

Made in Paradise

  • PlatformIO as Continuous Integration (CI) tool for embedded projects (issue #108)
  • Initialise PlatformIO project for the specified IDE (issue #151)
  • PlatformIO CLI 2.0: "platform" related commands have been moved to platformio platforms subcommand (issue #158)
  • Created PlatformIO gitter.im room (issue #174)
  • Global -f, --force option which will force to accept any confirmation prompts (issue #152)
  • Run project with platformio run --project-dir option without changing the current working directory (issue #192)
  • Control verbosity of platformio run command via -v/--verbose option
  • Add library dependencies for build environment using lib_install option in platformio.ini (issue #134)
  • Specify libraries which are compatible with build environment using lib_use option in platformio.ini (issue #148)
  • Add more boards to PlatformIO project with platformio init --board command (issue #167)
  • Choose which library to update (issue #168)
  • Specify platformio init --env-prefix when initialise/update project (issue #182)
  • Added new Armstrap boards (issue #204)
  • Updated SDK for espressif development platform to v1.1 (issue #179)
  • Disabled automatic updates by default for platforms, packages and libraries (issue #171)
  • Fixed bug with creating copies of source files (issue #177)

  • Added support of Framework mbed for Teensy 3.1 (issue #183)
  • Added GDB as alternative uploader to ststm32 platform (issue #175)
  • Added examples with preconfigured IDE projects (issue #154)
  • Fixed firmware uploading under Linux OS for Arduino Leonardo board (issue #178)
  • Fixed invalid "mbed" firmware for Nucleo F411RE (issue #185)
  • Fixed parsing of includes for PlatformIO Library Dependency Finder (issue #189)
  • Fixed handling symbolic links within source code directory (issue #190)
  • Fixed cancelling any previous definition of name, either built in or provided with a -D option (issue #191)

  • Added espressif development platform with ESP01 board
  • Integrated PlatformIO with AppVeyor Windows based Continuous Integration system (issue #149)
  • Added support for Teensy LC board to teensy platform
  • Added support for new Arduino based boards by SparkFun, BQ, LightUp, LowPowerLab, Quirkbot, RedBearLab, TinyCircuits to atmelavr platform
  • Upgraded Arduino Framework to 1.6.3 version (issue #156)
  • Upgraded Energia Framework to 0101E0015 version (issue #146)
  • Upgraded Arduino Framework with Teensy Core to 1.22 version (issue #162, issue #170)
  • Fixed exceptions with PlatformIO auto-updates when Internet connection isn't active

  • Moved PlatformIO source code and repositories from Ivan Kravets account to PlatformIO Organisation (issue #138)
  • Added support for new Arduino based boards by SparkFun, RepRap, Sanguino to atmelavr platform (issue #127, issue #131)
  • Added integration instructions for Visual Studio and Sublime Text IDEs
  • Improved handling of multi-file *.ino/pde sketches (issue #130)
  • Fixed wrong insertion of function prototypes converting *.ino/pde (issue #137, issue #140)

  • Added full support of mbed framework including libraries: RTOS, Ethernet, DSP, FAT, USB.
  • Added freescalekinetis development platform with Freescale Kinetis Freedom boards
  • Added nordicnrf51 development platform with supported boards from JKSoft, Nordic, RedBearLab, Switch Science
  • Added nxplpc development platform with supported boards from CQ Publishing, Embedded Artists, NGX Technologies, NXP, Outrageous Circuits, SeeedStudio, Solder Splash Labs, Switch Science, u-blox
  • Added support for ST Nucleo boards to ststm32 development platform
  • Created new Frameworks page in documentation and added to PlatformIO Web Site (issue #115)
  • Introduced online Embedded Boards Explorer
  • Automatically append define -DPLATFORMIO=%version% to builder (issue #105)
  • Renamed stm32 development platform to ststm32
  • Renamed opencm3 framework to libopencm3
  • Fixed uploading for atmelsam development platform
  • Fixed re-arranging the *.ino/pde files when converting to *.cpp (issue #100)

  • Implemented PLATFORMIO_* environment variables (issue #102)
  • Added support for SainSmart boards to atmelsam development platform
  • Added Project Configuration option named envs_dir
  • Disabled "prompts" automatically for Continuous Integration systems (issue #103)
  • Fixed firmware uploading for atmelavr boards which work within usbtiny protocol
  • Fixed uploading for Digispark board (issue #106)

PlatformIO 1.0 - recommended for production

  • Changed development status from beta to Production/Stable
  • Added support for ARM-based credit-card sized computers: Raspberry Pi, BeagleBone and CubieBoard
  • Added atmelsam development platform with supported boards: Arduino Due and Digistump DigiX (issue #71)
  • Added ststm32 development platform with supported boards: Discovery kit for STM32L151/152, STM32F303xx, STM32F407/417 lines and libOpenCM3 Framework (issue #73)
  • Added teensy development platform with supported boards: Teensy 2.x & 3.x (issue #72)
  • Added new Arduino boards to atmelavr platform: Arduino NG, Arduino BT, Arduino Esplora, Arduino Ethernet, Arduino Robot Control, Arduino Robot Motor and Arduino Yun
  • Added support for Adafruit boards to atmelavr platform: Adafruit Flora and Adafruit Trinkets (issue #65)
  • Added support for Digispark boards to atmelavr platform: Digispark USB Development Board and Digispark Pro (issue #47)
  • Covered code with tests (issue #2)
  • Refactored Library Dependency Finder (issues #48, #50, #55)
  • Added src_dir option to [platformio] section of platformio.ini which allows to redefine location to project's source directory (issue #83)
  • Added --json-output option to platformio boards and platformio search commands which allows to return the output in JSON format (issue #42)
  • Allowed to ignore some libs from Library Dependency Finder via lib_ignore option
  • Improved platformio run command: asynchronous output for build process, timing and detailed information about environment configuration (issue #74)
  • Output compiled size and static memory usage with platformio run command (issue #59)
  • Updated framework-arduino AVR & SAM to 1.6 stable version
  • Fixed an issue with the libraries that are git repositories (issue #49)
  • Fixed handling of assembly files (issue #58)
  • Fixed compiling error if space is in user's folder (issue #56)
  • Fixed AttributeError: 'module' object has no attribute 'disable_warnings' when a version of requests package is less then 2.4.0
  • Fixed bug with invalid process's "return code" when PlatformIO has internal error (issue #81)
  • Several bug fixes, increased stability and performance improvements

  • Fixed an issue with --json-output (issue #42)
  • Fixed an exception during platformio upgrade under Windows OS (issue #45)

  • Added --json-output option to platformio list, platformio serialports list and platformio lib list commands which allows to return the output in JSON format (issue #42)
  • Fixed missing auto-uploading by default after platformio init command

Happy New Year!

  • Implemented platformio boards command (issue #11)
  • Added support of Engduino boards for atmelavr platform (issue #38)
  • Added --board option to platformio init command which allows to initialise project with the specified embedded boards (issue #21)
  • Added example with uploading firmware via USB programmer (USBasp) for atmelavr MCUs (issue #35)
  • Automatic detection of port on platformio serialports monitor (issue #37)
  • Allowed auto-installation of platforms when prompts are disabled (issue #43)
  • Fixed urllib3's SSL warning under Python <= 2.7.2 (issue #39)
  • Fixed bug with Arduino USB boards (issue #40)

  • Replaced "dark blue" by "cyan" colour for the texts (issue #33)
  • Added new setting enable_prompts and allowed to disable all PlatformIO prompts (useful for cloud compilers) (issue #34)
  • Fixed compilation bug on Windows with installed MSVC (issue #18)

  • Ask user to install platform (when it hasn't been installed yet) within platformio run and platformio show commands
  • Improved main documentation
  • Fixed "OSError: [Errno 2] No such file or directory" within platformio run command when PlatformIO isn't installed properly
  • Fixed example for Eclipse IDE with Tiva board (issue #32)
  • Upgraded Eclipse Project Examples to latest Luna and PlatformIO releases

  • Implemented platformio settings command
  • Improved platformio init command. Added new option --project-dir where you can specify another path to directory where new project will be initialized (issue #31)
  • Added Migration Manager which simplifies process with upgrading to a major release
  • Added Telemetry Service which should help us make PlatformIO better
  • Implemented PlatformIO AppState Manager which allow to have multiple .platformio states.
  • Refactored Package Manager
  • Download Manager: fixed SHA1 verification within Cygwin Environment (issue #26)
  • Fixed bug with code builder and built-in Arduino libraries (issue #28)

  • Avoided trademark issues in library.json with the new fields: frameworks, platforms and dependencies (issue #17)
  • Switched logic from "Library Name" to "Library Registry ID" for all platformio lib commands (install, uninstall, update and etc.)
  • Renamed author field to authors and allowed to setup multiple authors per library in library.json
  • Added option to specify "maintainer" status in authors field
  • New filters/options for platformio lib search command: --framework and --platform

  • Fixed bug with order for includes in conversation from INO/PDE to CPP
  • Automatic detection of port on upload (issue #15)
  • Fixed lib update crashing when no libs are installed (issue #19)

  • Implemented new [platformio] section for Configuration File with home_dir option (issue #14)
  • Implemented Library Manager (issue #6)

  • Implemented platformio serialports monitor (issue #10)
  • Fixed an issue ImportError: No module named platformio.util (issue #9)
  • Fixed bug with auto-conversation from Arduino *.ino to *.cpp

  • Improved nested lookups for libraries
  • Disabled default warning flag "-Wall"
  • Added auto-conversation from *.ino to valid *.cpp for Arduino/Energia frameworks (issue #7)
  • Added Arduino example with external library (Adafruit CC3000)
  • Implemented platformio upgrade command and "auto-check" for the latest version (issue #8)
  • Fixed an issue with "auto-reset" for Raspduino board
  • Fixed a bug with nested libs building

  • Implemented platformio serialports command
  • Allowed to put special build flags only for src files via src_build_flags environment option
  • Allowed to override some of settings via system environment variables such as: PLATFORMIO_SRC_BUILD_FLAGS and PLATFORMIO_ENVS_DIR
  • Added --upload-port option for platformio run command
  • Implemented (especially for SmartAnthill) platformio run -t uploadlazy target (no dependencies to framework libs, ELF and etc.)
  • Allowed to skip default packages via platformio install --skip-default-package option
  • Added tools for Raspberry Pi platform
  • Added support for Microduino and Raspduino boards in atmelavr platform

•
Fixed auto-installer for Windows OS (bug with %PATH% custom installation)

  • Allowed to pass multiple "SomePlatform" to install/uninstall commands
  • Added "IDE Integration" section to README with Eclipse project examples
  • Created auto installer script for PlatformIO (issue #3)
  • Added "Super-Quick" way to Installation section (README)
  • Implemented "build_flags" option for environments (issue #4)

  • Resolved issue #1 "Build referred libraries"
  • Renamed project's "libs" directory to "lib"
  • Added arduino-internal-library example
  • Changed to beta status

•
Birth! First alpha release

Guidance on how to upgrade from PlatformIO Core (CLI) v3.x to v4.x with emphasis on major changes, what is new, and what has been removed.

Please read PlatformIO 4.0 Release Notes before.

  • Compatibility
  • Infrastructure
  • What is new
•
"platformio.ini" (Project Configuration File)
  • Global scope [env]
  • External Configuration Files
  • New Options

  • Library Management
  • Build System
  • Package Dependencies
  • Custom Platform Packages
  • Custom Upload Command
  • Shared Cache Directory


•
What is changed or removed
  • Command Line Interface
  • "platformio.ini" (Project Configuration File)


PlatformIO Core 4.0 is fully backward compatible with v3.x. The only major change is a new location for project build artifacts and library dependencies. The previous .pioenvs (build_dir) and .piolibdeps (libdeps_dir) folders were moved to a new workspace_dir.

NOTE:

If you manually added library dependencies to old .piolibdeps folder, please declare them in lib_deps. We do not recommend modifying any files or folders in workspace_dir. This is an internal location for PlatformIO Core artifacts and temporary files. PlatformIO Core 4.0 may delete/cleanup this folder in a service purpose any time.


Finally, Python 3 interpreter is officially supported! The minimum requirements are Python 2.7 or Python 3.5+.

We also added full support for operating system locales other than UTF-8. So, your project path can contain non-ASCII/non-Latin chars now.

If you are Development Platforms maintainer or you need to show a progress bar (upload progress, connecting status...), PlatformIO Core 4.0 has re-factored target runner where line-buffering was totally removed. Just print any progress information in real time and PlatformIO Core will display it instantly on user the side. For example, a writing progress from Atmel AVR "avrdude" programmer:

...
Looking for upload port...
Auto-detected: /dev/cu.usbmodemFA141
Uploading build/uno/firmware.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
avrdude: Device signature = 0x1e950f (probably m328p)
avrdude: reading input file "build/uno/firmware.hex"
avrdude: writing flash (930 bytes):
Writing | ##########################


In this section, we are going to highlight the most important changes and features introduced in PlatformIO Core (CLI) 4.0. Please visit PlatformIO 4.0 Release Notes for more detailed information.

"platformio.ini" (Project Configuration File)

A project configuration parser was rewritten from scratch. It has strict options typing (API) and helps to avoid issues when option values are invalid (for example, invalid Dependency Finder Mode or non-existing debug_svd_path).

One of the most requested features was a "global" or "common" project environment (Section [env]) where developers can share common configuration between all declared build environments [env:NAME].

The previous solution in PlatformIO Core 3.0 was using Dynamic variables. As practice has shown, this approach was not good and more advanced "platformio.ini" (Project Configuration File) looked so complicated and hard for managing (for example, open source projects MarlinFirmware, Espurna).

PlatformIO Core 4.0 introduces a new global scope named [env] which allows declaring global options that will be shared between all [env:NAME] sections in "platformio.ini" (Project Configuration File). For example,

[env]
platform = ststm32
framework = stm32cube
board = nucleo_l152re
lib_deps = Dep1, Dep2
[env:release]
build_flags = -D RELEASE
lib_deps =
    ${env.lib_deps}
    Dep3
[env:debug]
build_type = debug
build_flags = -D DEBUG
lib_deps = DepCustom


In this example we have 2 build environments release and debug. This is the same if you duplicate all options (PlatformIO Core 3.0 compatible):

[env:release]
platform = ststm32
framework = stm32cube
board = nucleo_l152re
build_flags = -D RELEASE
lib_deps = Dep1, Dep2, Dep3
[env:debug]
platform = ststm32
framework = stm32cube
board = nucleo_l152re
build_type = debug
build_flags = -D DEBUG
lib_deps = DepCustom


To simplify the project configuration process, PlatformIO Core 4.0 adds support for external "platformio.ini" (Project Configuration File). Yes! You can finally extend one configuration file with another or with a list of them. The cool feature is a support for Unix shell-style wildcards. So, you can dynamically generate "platformio.ini" (Project Configuration File) files or load bunch of them from a folder. See extra_configs option for details and a simple example below:

Base "platformio.ini"

[platformio]
extra_configs =
  extra_envs.ini
  extra_debug.ini
[common]
debug_flags = -D RELEASE
lib_flags = -lc -lm
[env:esp-wrover-kit]
platform = espressif32
framework = espidf
board = esp-wrover-kit
build_flags = ${common.debug_flags}


"extra_envs.ini"

[env:esp32dev]
platform = espressif32
framework = espidf
board = esp32dev
build_flags = ${common.lib_flags} ${common.debug_flags}
[env:lolin32]
platform = espressif32
framework = espidf
board = lolin32
build_flags = ${common.debug_flags}


"extra_debug.ini"

# Override base "common.debug_flags"
[common]
debug_flags = -D DEBUG=1
[env:lolin32]
build_flags = -Og


After a parsing process, configuration state will be the next:

[common]
debug_flags = -D DEBUG=1
lib_flags = -lc -lm
[env:esp-wrover-kit]
platform = espressif32
framework = espidf
board = esp-wrover-kit
build_flags = ${common.debug_flags}
[env:esp32dev]
platform = espressif32
framework = espidf
board = esp32dev
build_flags = ${common.lib_flags} ${common.debug_flags}
[env:lolin32]
platform = espressif32
framework = espidf
board = lolin32
build_flags = -Og


We have added new options and changed some existing ones. Here are the new or updated options.

Section Option Description
platformio extra_configs Extend base configuration with external "platformio.ini" (Project Configuration File)
platformio core_dir Directory where PlatformIO stores development platform packages (toolchains, frameworks, SDKs, upload and debug tools), global libraries for Library Dependency Finder (LDF), and other PlatformIO Core service data
platformio globallib_dir Global library storage for PlatfrmIO projects and Library Manager where Library Dependency Finder (LDF) looks for dependencies
platformio platforms_dir Global storage where PlatformIO Package Manager installs Development Platforms
platformio packages_dir Global storage where PlatformIO Package Manager installs Development Platforms dependencies (toolchains, Frameworks, SDKs, upload and debug tools)
platformio cache_dir PlatformIO Core (CLI) uses this folder to store caching information (requests to PlatformIO Registry, downloaded packages and other service information)
platformio workspace_dir A path to a project workspace directory where PlatformIO keeps by default compiled objects, static libraries, firmwares, and external library dependencies
platformio shared_dir PIO Remote uses this folder to synchronize extra files between remote machine
env build_type See extended documentation for Build Configurations
env monitor_flags Pass extra flags and options to platformio device monitor command
env upload_command Override default Development Platforms upload command with a custom one.

Library management brings a few new changes which resolve historical issues presented in PlatformIO 3.0:

1.
.piolibdeps folder was moved to libdeps_dir of project workspace.

If you manually added library dependencies to old .piolibdeps folder, please declare them in lib_deps. We do not recommend modifying any files or folders in workspace_dir. This is an internal location for PlatformIO Core artifacts and temporary files. PlatformIO Core 4.0 may delete/cleanup this folder in a service purpose any time.

2.
Library Dependency Finder (LDF) now uses isolated library dependency storage per project build environment. It resolves conflicts when the libraries from different build environments declared via lib_deps option were installed into the same .piolibdeps folder.

See Library Management section in PlatformIO Core 4 release notes for more details.

PlatformIO Core 4.0 uses a new build_dir instead of .pioenvs for compiled objects, archived libraries, firmware binaries and, other artifacts. A new build_type option allows you to control a build process between "Release" and "Debug" modes (see Build Configurations).

See Build System section in PlatformIO Core 4 release notes for more details.

PlatformIO has decentralized architecture and allows platform maintainers to create Custom Development Platforms for PlatformIO ecosystem. Each development platform depends on a list of packages (toolchains, SDKs, debugging servers, etc). PlatformIO Package Manager installs these packages automatically and PlatformIO Build System uses them later.

Starting from PlatformIO Core 4.0, developers can see which versions of a development platform or its dependent packages will be used. This is a great addition to track changes (Frameworks, SDKs) between Development Platforms updates. See an example with "staging" (Git) version of Espressif 8266 development platform:

Processing nodemcuv2 (platform: https://github.com/platformio/platform-espressif8266.git#feature/stage; board: nodemcuv2; framework: arduino)
-------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif8266/nodemcuv2.html
PLATFORM: Espressif 8266 (Stage) 2.3.0-alpha.1 #990141d > NodeMCU 1.0 (ESP-12E Module)
HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash
PACKAGES: toolchain-xtensa 2.40802.190218 (4.8.2), tool-esptool 1.413.0 (4.13), tool-esptoolpy 1.20600.0 (2.6.0), framework-arduinoespressif8266 78a1a66
LDF: Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain+, Compatibility ~ soft
Found 35 compatible libraries
Scanning dependencies...


Sometimes you need to override default Development Platforms packages or add an extra. PlatformIO Core 4.0 introduces a new configuration option platform_packages per a build environment. Also, using this option you can install external packages and use them later as programmers or upload tools. See a few examples:

[env:override_default_toolchain]
platform = atmelavr
platform_packages =
  ; use GCC AVR 5.0+
  toolchain-gccarmnoneeabi@>1.50000.0
[env:override_framework]
platform = espressif8266
platform_packages =
  ; use upstream Git version
  framework-arduinoespressif8266 @ https://github.com/esp8266/Arduino.git
[env:external_package]
platform = ststm32
platform_packages =
  ; latest openOCD from PlatformIO Package Registry
  tool-openocd
  ; source code of ST-Link
  tool-stlink-source @ https://github.com/texane/stlink.git


PlatformIO's Development Platforms have pre-configured settings to program boards or devices. They depend on a type of bootloader or programming interface. PlatformIO Core 4.0 allows you to override default upload command using upload_command option in "platformio.ini" (Project Configuration File):

[env:custom_upload_cmd]
platform = ...
framework = ...
board = ...
upload_command = /my/flasher arg1 arg2 --flag1 $SOURCE


See real examples for upload_command.

PlatformIO Core 4.0 allows you to configure a shared folder for the derived files (objects, firmwares, ELFs) from a build system using build_cache_dir. You can use it in multi-environments project configuration to avoid multiple compilations of the same source code files.

The example of "platformio.ini" (Project Configuration File) below instructs PlatformIO Build System to check build_cache_dir for already compiled objects for STM32Cube and project source files. The cached object will not be used if the original source file was modified or build environment has a different configuration (new build flags, etc):

[platformio]
; set a path to a cache folder
build_cache_dir = /tmp/platformio-shared-cache
[env:bluepill_f103c6]
platform = ststm32
framework = stm32cube
board = bluepill_f103c6
[env:nucleo_f411re]
platform = ststm32
framework = stm32cube
board = nucleo_f411re


You can also use the same build_cache_dir between different projects if they use the same Development Platforms and Frameworks.

The following commands have been changed in v4.0.

Command Description
platformio run Added platformio run --jobs option
platformio update Replaced -c, --only-check with platformio update --dry-run
platformio lib update Replaced -c, --only-check with platformio lib update --dry-run
platformio platform update Replaced -c, --only-check with platformio platform update --dry-run
platformio remote update Replaced -c, --only-check with platformio remote update --dry-run

"platformio.ini" (Project Configuration File)

The following options have been changed in v4.0.

Section Option Description
platformio env_default Renamed to default_envs
platformio home_dir Renamed to core_dir
env debug_load_cmd Renamed to debug_load_cmds and allowed to pass more than one load command

PlatformIO

2014-present, PlatformIO

November 16, 2022 4.3