neulab/tldr huggingface dataset:
Frameworks ┌────────────────────┬─────────────────────────────┐ │Name                │ Description                 │ ├────────────────────┼─────────────────────────────┤ │framework_cmsis     │ The ARM Cortex              │ │                    │ Microcontroller Software    │ │                    │ Interface Standard (CMSIS)  │ │                    │ is a vendor-independent     │ │                    │ hardware abstraction layer  │ │                    │ for the Cortex-M processor  │ │                    │ series and specifies        │ │                    │ debugger interfaces. The    │ │                    │ CMSIS enables consistent    │ │                    │ and simple software         │ │                    │ interfaces to the processor │ │                    │ for interface peripherals,  │ │                    │ real-time operating         │ │                    │ systems, and middleware. It │ │                    │ simplifies software re-use, │ │                    │ reducing the learning curve │ │                    │ for new microcontroller     │ │                    │ developers and cutting the  │ │                    │ time-to-market for devices. │ ├────────────────────┼─────────────────────────────┤ │framework_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) Contents • STM32F401RB (64k RAM. 128k Flash)
┌────────────────┬─────────────┐ │Microcontroller │ STM32F401RB │ ├────────────────┼─────────────┤ │Frequency       │ 84MHz       │ ├────────────────┼─────────────┤ │Flash           │ 128KB       │ ├────────────────┼─────────────┤ │RAM             │ 64KB        │ ├────────────────┼─────────────┤ │Vendor          │ Generic     │ └────────────────┴─────────────┘
Configuration Please use genericSTM32F401RB ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f401rb
Uploading STM32F401RB (64k RAM. 128k Flash) supports the next uploading protocols:
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.
Frameworks ┌────────────────────┬─────────────────────────────┐ │Name                │ Description                 │ ├────────────────────┼─────────────────────────────┤ │framework_arduino   │ Arduino Wiring-based        │ │                    │ Framework allows writing    │ │                    │ cross-platform software to  │ │                    │ control devices attached to │ │                    │ a wide range of Arduino     │ │                    │ boards to create all kinds  │ │                    │ of creative coding,         │ │                    │ interactive objects, spaces │ │                    │ or physical experiences.    │ ├────────────────────┼─────────────────────────────┤ │framework_cmsis     │ The ARM Cortex              │ │                    │ Microcontroller Software    │ │                    │ Interface Standard (CMSIS)  │ │                    │ is a vendor-independent     │ │                    │ hardware abstraction layer  │ │                    │ for the Cortex-M processor  │ │                    │ series and specifies        │ │                    │ debugger interfaces. The    │ │                    │ CMSIS enables consistent    │ │                    │ and simple software         │ │                    │ interfaces to the processor │ │                    │ for interface peripherals,  │ │                    │ real-time operating         │ │                    │ systems, and middleware. It │ │                    │ simplifies software re-use, │ │                    │ reducing the learning curve │ │                    │ for new microcontroller     │ │                    │ developers and cutting the  │ │                    │ time-to-market for devices. │ ├────────────────────┼─────────────────────────────┤ │framework_spl       │ The ST Standard Peripheral  │ │                    │ Library provides a set of   │ │                    │ functions for handling the  │ │                    │ peripherals on the STM32    │ │                    │ Cortex-M3 family. The idea  │ │                    │ is to save the user (the    │ │                    │ new user, in particular)    │ │                    │ having to deal directly     │ │                    │ with the registers.         │ ├────────────────────┼─────────────────────────────┤ │framework_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ └────────────────────┴─────────────────────────────┘
STM32F401RC (64k RAM. 256k Flash) Contents • STM32F401RC (64k RAM. 256k Flash)
┌────────────────┬─────────────┐ │Microcontroller │ STM32F401RC │ ├────────────────┼─────────────┤ │Frequency       │ 84MHz       │ ├────────────────┼─────────────┤ │Flash           │ 256KB       │ └────────────────┴─────────────┘
│RAM             │ 64KB        │ ├────────────────┼─────────────┤ │Vendor          │ Generic     │ └────────────────┴─────────────┘
Configuration Please use genericSTM32F401RC ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f401rc
Uploading STM32F401RC (64k RAM. 256k Flash) supports the next uploading protocols:
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.
STM32F401RE (96k RAM. 512k Flash) Contents • STM32F401RE (96k RAM. 512k Flash)
┌────────────────┬─────────────┐ │Microcontroller │ STM32F401RE │ ├────────────────┼─────────────┤ │Frequency       │ 84MHz       │ ├────────────────┼─────────────┤ │Flash           │ 512KB       │ ├────────────────┼─────────────┤ │RAM             │ 96KB        │ ├────────────────┼─────────────┤ │Vendor          │ Generic     │ └────────────────┴─────────────┘
Configuration Please use genericSTM32F401RE ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f401re
Uploading STM32F401RE (96k RAM. 512k Flash) supports the next uploading protocols:
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.
│framework_arduino   │ Arduino Wiring-based        │ │                    │ Framework allows writing    │ │                    │ cross-platform software to  │ │                    │ control devices attached to │ │                    │ a wide range of Arduino     │ │                    │ boards to create all kinds  │ │                    │ of creative coding,         │ │                    │ interactive objects, spaces │ │                    │ or physical experiences.    │ ├────────────────────┼─────────────────────────────┤ │framework_cmsis     │ The ARM Cortex              │ │                    │ Microcontroller Software    │ │                    │ Interface Standard (CMSIS)  │ │                    │ is a vendor-independent     │ │                    │ hardware abstraction layer  │ │                    │ for the Cortex-M processor  │ │                    │ series and specifies        │ │                    │ debugger interfaces. The    │ │                    │ CMSIS enables consistent    │ │                    │ and simple software         │ │                    │ interfaces to the processor │ │                    │ for interface peripherals,  │ │                    │ real-time operating         │ │                    │ systems, and middleware. It │ │                    │ simplifies software re-use, │ │                    │ reducing the learning curve │ │                    │ for new microcontroller     │ │                    │ developers and cutting the  │ │                    │ time-to-market for devices. │ ├────────────────────┼─────────────────────────────┤ │framework_spl       │ The ST Standard Peripheral  │ │                    │ Library provides a set of   │ │                    │ functions for handling the  │ │                    │ peripherals on the STM32    │ │                    │ Cortex-M3 family. The idea  │ │                    │ is to save the user (the    │ │                    │ new user, in particular)    │ │                    │ having to deal directly     │ │                    │ with the registers.         │ ├────────────────────┼─────────────────────────────┤ │framework_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ └────────────────────┴─────────────────────────────┘
STM32F407VE (192k RAM. 512k Flash) Contents • STM32F407VE (192k RAM. 512k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407VET6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 502.23KB      │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F407VET6 ID for projectconf_env_board option in projectconf:
[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.
Uploading STM32F407VE (192k RAM. 512k Flash) supports the next uploading protocols:
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.
STM32F407VG (192k RAM. 1024k Flash) Contents • STM32F407VG (192k RAM. 1024k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407VGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 192KB         │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F407VGT6 ID for projectconf_env_board option in projectconf:
[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.
Uploading STM32F407VG (192k RAM. 1024k Flash) supports the next uploading protocols:
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.
STM32F4Stamp F405 Contents • STM32F4Stamp F405
┌────────────────┬───────────────┐ │Microcontroller │ STM32F405RGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 192KB         │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use stm32f4stamp ID for projectconf_env_board option in projectconf:
[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.
Uploading STM32F4Stamp F405 supports the next uploading protocols:
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.
STM32F7508-DK Contents • STM32F7508-DK
┌────────────────┬───────────────┐ │Microcontroller │ STM32F750N8H6 │ ├────────────────┼───────────────┤ │Frequency       │ 216MHz        │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 340KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f750n8 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f750n8h6
Uploading STM32F7508-DK supports the next uploading protocols:
STM32F7508-DK has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
STM32H747I-DISCO Contents • STM32H747I-DISCO
┌────────────────┬───────────────┐ │Microcontroller │ STM32H747XIH6 │ ├────────────────┼───────────────┤ │Frequency       │ 400MHz        │ ├────────────────┼───────────────┤ │Flash           │ 2MB           │ ├────────────────┼───────────────┤ │RAM             │ 512KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_h743xi ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32h747xih6
Uploading STM32H747I-DISCO supports the next uploading protocols:
STM32H747I-DISCO has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Seeed Arch Max Contents • Seeed Arch Max
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407VET6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 192KB         │ ├────────────────┼───────────────┤ │Vendor          │ SeeedStudio   │ └────────────────┴───────────────┘
Configuration Please use seeedArchMax ID for projectconf_env_board option in projectconf:
[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.
Uploading Seeed Arch Max supports the next uploading protocols:
Seeed Arch Max has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Seeed Wio 3G Contents • Seeed Wio 3G
┌────────────────┬─────────────┐ │Microcontroller │ STM32F439VI │ ├────────────────┼─────────────┤ │Frequency       │ 180MHz      │ ├────────────────┼─────────────┤ │Flash           │ 2MB         │ ├────────────────┼─────────────┤ │RAM             │ 256KB       │ ├────────────────┼─────────────┤ │Vendor          │ SeeedStudio │ └────────────────┴─────────────┘
Configuration Please use wio_3g ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f439vi
Uploading Seeed Wio 3G supports the next uploading protocols:
Seeed Wio 3G has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SensorTile.box Contents • SensorTile.box
┌────────────────┬─────────────┐ │Microcontroller │ STM32L4R9ZI │ ├────────────────┼─────────────┤ │Frequency       │ 120MHz      │ ├────────────────┼─────────────┤ │Flash           │ 2MB         │ ├────────────────┼─────────────┤ │RAM             │ 640KB       │ ├────────────────┼─────────────┤ │Vendor          │ ST          │ └────────────────┴─────────────┘
Configuration Please use steval_mksboxv1 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32l4r9zi
Uploading SensorTile.box supports the next uploading protocols:
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.
Sparky V1 F303 Contents • Sparky V1 F303
┌────────────────┬───────────────┐ │Microcontroller │ STM32F303CCT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 40KB          │ ├────────────────┼───────────────┤ │Vendor          │ TauLabs       │ └────────────────┴───────────────┘
Configuration Please use sparky_v1 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f303cct6
Uploading Sparky V1 F303 supports the next uploading protocols:
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.
ThunderPack Contents • ThunderPack
┌────────────────┬─────────────┐ │Microcontroller │ STM32L072KZ │ ├────────────────┼─────────────┤ │Frequency       │ 32MHz       │ ├────────────────┼─────────────┤ │Flash           │ 192KB       │ ├────────────────┼─────────────┤ │RAM             │ 20KB        │ ├────────────────┼─────────────┤ │Vendor          │ ThunderPack │ └────────────────┴─────────────┘
Configuration Please use thunder_pack ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32l072kz
Uploading ThunderPack supports the next uploading protocols:
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.
Tiny STM103T Contents • Tiny STM103T
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103TBU6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ HY            │ └────────────────┴───────────────┘
Configuration Please use hy_tinystm103tb ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f103tbu6
Uploading Tiny STM103T supports the next uploading protocols:
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.
VAkE v1.0 Contents • VAkE v1.0
┌────────────────┬───────────────┐ │Microcontroller │ STM32F446RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 180MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ VAE           │ └────────────────┴───────────────┘
Configuration Please use vake_v1 ID for projectconf_env_board option in projectconf:
[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.
Uploading VAkE v1.0 supports the next uploading protocols:
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.
Wraith V1 ESC Contents • Wraith V1 ESC
┌────────────────┬─────────────┐ │Microcontroller │ STM32F051K6 │ ├────────────────┼─────────────┤ │Frequency       │ 48MHz       │ ├────────────────┼─────────────┤ │Flash           │ 32KB        │ ├────────────────┼─────────────┤ │RAM             │ 7.75KB      │ ├────────────────┼─────────────┤ │Vendor          │ Airbot      │ └────────────────┴─────────────┘
Configuration Please use wraith32_v1 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f051k6
Uploading Wraith V1 ESC supports the next uploading protocols:
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.
sakura.io Evaluation Board Contents • sakura.io Evaluation Board
┌────────────────┬───────────────┐ │Microcontroller │ STM32F411RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 100MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ sakura.io     │ └────────────────┴───────────────┘
Configuration Please use sakuraio_evb_01 ID for projectconf_env_board option in projectconf:
[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.
Uploading sakura.io Evaluation Board supports the next uploading protocols:
sakura.io Evaluation Board has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
u-blox C030-N211 IoT Starter Kit Contents • u-blox C030-N211 IoT Starter Kit
┌────────────────┬─────────────┐ │Microcontroller │ STM32F437VG │ ├────────────────┼─────────────┤ │Frequency       │ 180MHz      │ ├────────────────┼─────────────┤ │Flash           │ 1MB         │ ├────────────────┼─────────────┤ │RAM             │ 256KB       │ ├────────────────┼─────────────┤ │Vendor          │ u-blox      │ └────────────────┴─────────────┘
Configuration Please use ublox_c030_n211 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f437vg
Uploading u-blox C030-N211 IoT Starter Kit supports the next uploading protocols:
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.
u-blox C030-R410M IoT Contents • u-blox C030-R410M IoT
Configuration Please use ublox_c030_r410m ID for projectconf_env_board option in projectconf:
[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.
Uploading u-blox C030-R410M IoT supports the next uploading protocols:
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.
u-blox C030-U201 IoT Starter Kit Contents • u-blox C030-U201 IoT Starter Kit
Configuration Please use ublox_c030_u201 ID for projectconf_env_board option in projectconf:
[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.
Uploading u-blox C030-U201 IoT Starter Kit supports the next uploading protocols:
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.
u-blox EVK-ODIN-W2 Contents • u-blox EVK-ODIN-W2
Configuration Please use ublox_evk_odin_w2 ID for projectconf_env_board option in projectconf:
[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.
Uploading u-blox EVK-ODIN-W2 supports the next uploading protocols:
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.
u-blox ODIN-W2 Contents • u-blox ODIN-W2
Configuration Please use mtb_ublox_odin_w2 ID for projectconf_env_board option in projectconf:
[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.
Uploading u-blox ODIN-W2 supports the next uploading protocols:
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.
ST STM8 ST STM8S-DISCOVERY Contents • ST STM8S-DISCOVERY
Hardware Platform 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.
┌────────────────┬──────────────┐ │Microcontroller │ STM8S105C6T6 │ ├────────────────┼──────────────┤ │Frequency       │ 16MHz        │ ├────────────────┼──────────────┤ │Flash           │ 32KB         │ ├────────────────┼──────────────┤ │RAM             │ 2KB          │ ├────────────────┼──────────────┤ │Vendor          │ ST           │ └────────────────┴──────────────┘
Configuration Please use stm8sdisco ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm8s105c6t6
Uploading ST STM8S-DISCOVERY supports the next uploading protocols:
• stlinkv2
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 │ ├──────────────────────┼──────────┼─────────┤ │debugging_tool_stlink │ Yes      │ Yes     │ └──────────────────────┴──────────┴─────────┘
ST STM8S103F3 Breakout Board Contents • ST STM8S103F3 Breakout Board
┌────────────────┬──────────────┐ │Microcontroller │ STM8S103F3P6 │ ├────────────────┼──────────────┤ │Frequency       │ 16MHz        │ ├────────────────┼──────────────┤ │Flash           │ 8KB          │ ├────────────────┼──────────────┤ │RAM             │ 1KB          │ ├────────────────┼──────────────┤ │Vendor          │ ST           │ └────────────────┴──────────────┘
Configuration Please use stm8sblue ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm8s103f3p6
Uploading ST STM8S103F3 Breakout Board supports the next uploading protocols:
Debugging piodebug currently does not support ST STM8S103F3 Breakout Board board.
ST STM8S105K4T6 Breakout Board Contents • ST STM8S105K4T6 Breakout Board
┌────────────────┬──────────────┐ │Microcontroller │ STM8S105K4T6 │ ├────────────────┼──────────────┤ │Frequency       │ 16MHz        │ ├────────────────┼──────────────┤ │Flash           │ 16KB         │ ├────────────────┼──────────────┤ │RAM             │ 2KB          │ ├────────────────┼──────────────┤ │Vendor          │ ST           │ └────────────────┴──────────────┘
Configuration Please use stm8sblack ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm8s105k4t6
Uploading ST STM8S105K4T6 Breakout Board supports the next uploading protocols:
Debugging piodebug currently does not support ST STM8S105K4T6 Breakout Board board.
│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.         │ └──────────────────┴─────────────────────────────┘
sduino MB (STM8S208MBT6B) Contents • sduino MB (STM8S208MBT6B)
┌────────────────┬──────────────┐ │Microcontroller │ STM8S208MBT6 │ ├────────────────┼──────────────┤ │Frequency       │ 16MHz        │ ├────────────────┼──────────────┤ │Flash           │ 128KB        │ ├────────────────┼──────────────┤ │RAM             │ 6KB          │ ├────────────────┼──────────────┤ │Vendor          │ sduino       │ └────────────────┴──────────────┘
Configuration Please use mb208 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm8s208mbt6
Uploading sduino MB (STM8S208MBT6B) supports the next uploading protocols:
Debugging piodebug currently does not support sduino MB (STM8S208MBT6B) board.
sduino UNO (STM8S105K6) Contents • sduino UNO (STM8S105K6)
┌────────────────┬──────────────┐ │Microcontroller │ STM8S105K6T6 │ ├────────────────┼──────────────┤ │Frequency       │ 16MHz        │ ├────────────────┼──────────────┤ │Flash           │ 32KB         │ ├────────────────┼──────────────┤ │RAM             │ 2KB          │ ├────────────────┼──────────────┤ │Vendor          │ sduino       │ └────────────────┴──────────────┘
Configuration Please use s8uno ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm8s105k6t6
Uploading sduino UNO (STM8S105K6) supports the next uploading protocols:
Debugging piodebug currently does not support sduino UNO (STM8S105K6) board.
Teensy Teensy 2.0 Contents • Teensy 2.0
Hardware Platform 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     │ └────────────────┴────────────┘
Configuration Please use teensy2 ID for projectconf_env_board option in projectconf:
[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.
Uploading Teensy 2.0 supports the next uploading protocols:
• teensy-cli
• teensy-gui
Default protocol is teensy-gui
upload_protocol = teensy-gui
Debugging piodebug currently does not support Teensy 2.0 board.
Teensy 3.0 Contents • Teensy 3.0
┌────────────────┬───────────┐ │Microcontroller │ MK20DX128 │ ├────────────────┼───────────┤ │Frequency       │ 48MHz     │ ├────────────────┼───────────┤ │Flash           │ 128KB     │ ├────────────────┼───────────┤ │RAM             │ 16KB      │ ├────────────────┼───────────┤ │Vendor          │ Teensy    │ └────────────────┴───────────┘
Configuration Please use teensy30 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = mk20dx128
Uploading Teensy 3.0 supports the next uploading protocols:
Debugging piodebug currently does not support Teensy 3.0 board.
Teensy 3.1 / 3.2 Contents • Teensy 3.1 / 3.2
┌────────────────┬───────────┐ │Microcontroller │ MK20DX256 │ ├────────────────┼───────────┤ │Frequency       │ 72MHz     │ ├────────────────┼───────────┤ │Flash           │ 256KB     │ ├────────────────┼───────────┤ │RAM             │ 64KB      │ ├────────────────┼───────────┤ │Vendor          │ Teensy    │ └────────────────┴───────────┘
Configuration Please use teensy31 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = mk20dx256
Uploading Teensy 3.1 / 3.2 supports the next uploading protocols:
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.
│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.   │ └──────────────────┴─────────────────────────────┘
Teensy 3.5 Contents • Teensy 3.5
┌────────────────┬───────────┐ │Microcontroller │ MK64FX512 │ ├────────────────┼───────────┤ │Frequency       │ 120MHz    │ ├────────────────┼───────────┤ │Flash           │ 512KB     │ ├────────────────┼───────────┤ │RAM             │ 255.99KB  │ ├────────────────┼───────────┤ │Vendor          │ Teensy    │ └────────────────┴───────────┘
Configuration Please use teensy35 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = mk64fx512
Uploading Teensy 3.5 supports the next uploading protocols:
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.
Teensy 3.6 Contents • Teensy 3.6
┌────────────────┬───────────┐ │Microcontroller │ MK66FX1M0 │ ├────────────────┼───────────┤ │Frequency       │ 180MHz    │ ├────────────────┼───────────┤ │Flash           │ 1MB       │ ├────────────────┼───────────┤ │RAM             │ 256KB     │ ├────────────────┼───────────┤ │Vendor          │ Teensy    │ └────────────────┴───────────┘
Configuration Please use teensy36 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = mk66fx1m0
Uploading Teensy 3.6 supports the next uploading protocols:
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.
Teensy 4.0 Contents • Teensy 4.0
┌────────────────┬───────────┐ │Microcontroller │ IMXRT1062 │ ├────────────────┼───────────┤ │Frequency       │ 600MHz    │ ├────────────────┼───────────┤ │Flash           │ 1.94MB    │ ├────────────────┼───────────┤ │RAM             │ 512KB     │ ├────────────────┼───────────┤ │Vendor          │ Teensy    │ └────────────────┴───────────┘
Configuration Please use teensy40 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = imxrt1062
Uploading Teensy 4.0 supports the next uploading protocols:
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.
Teensy 4.1 Contents • Teensy 4.1
┌────────────────┬───────────┐ │Microcontroller │ IMXRT1062 │ ├────────────────┼───────────┤ │Frequency       │ 600MHz    │ ├────────────────┼───────────┤ │Flash           │ 7.75MB    │ ├────────────────┼───────────┤ │RAM             │ 512KB     │ ├────────────────┼───────────┤ │Vendor          │ Teensy    │ └────────────────┴───────────┘
Configuration Please use teensy41 ID for projectconf_env_board option in projectconf:
[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.
Uploading Teensy 4.1 supports the next uploading protocols:
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.
Teensy LC Contents • Teensy LC
┌────────────────┬──────────┐ │Microcontroller │ MKL26Z64 │ ├────────────────┼──────────┤ │Frequency       │ 48MHz    │ ├────────────────┼──────────┤ │Flash           │ 62KB     │ ├────────────────┼──────────┤ │RAM             │ 8KB      │ ├────────────────┼──────────┤ │Vendor          │ Teensy   │ └────────────────┴──────────┘
Configuration Please use teensylc ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = mkl26z64
Uploading Teensy LC supports the next uploading protocols:
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.
Teensy++ 2.0 Contents • Teensy++ 2.0
┌────────────────┬─────────────┐ │Microcontroller │ AT90USB1286 │ ├────────────────┼─────────────┤ │Frequency       │ 16MHz       │ ├────────────────┼─────────────┤ │Flash           │ 127KB       │ ├────────────────┼─────────────┤ │RAM             │ 8KB         │ ├────────────────┼─────────────┤ │Vendor          │ Teensy      │ └────────────────┴─────────────┘
Configuration Please use teensy2pp ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = at90usb1286
Uploading Teensy++ 2.0 supports the next uploading protocols:
Debugging piodebug currently does not support Teensy++ 2.0 board.
TI MSP430 TI FraunchPad MSP-EXP430FR5739LP Contents • TI FraunchPad MSP-EXP430FR5739LP
Hardware Platform 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.
┌────────────────┬──────────────┐ │Microcontroller │ MSP430FR5739 │ ├────────────────┼──────────────┤ │Frequency       │ 16MHz        │ ├────────────────┼──────────────┤ │Flash           │ 15.37KB      │ ├────────────────┼──────────────┤ │RAM             │ 1KB          │ ├────────────────┼──────────────┤ │Vendor          │ TI           │ └────────────────┴──────────────┘
Configuration Please use lpmsp430fr5739 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = msp430fr5739
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 │ ├────────────────────────┼──────────┼─────────┤ │debugging_tool_mspdebug │ Yes      │ Yes     │ └────────────────────────┴──────────┴─────────┘
TI LaunchPad MSP-EXP430F5529LP Contents • TI LaunchPad MSP-EXP430F5529LP
┌────────────────┬─────────────┐ │Microcontroller │ MSP430F5529 │ ├────────────────┼─────────────┤ │Frequency       │ 25MHz       │ ├────────────────┼─────────────┤ │Flash           │ 47KB        │ ├────────────────┼─────────────┤ │RAM             │ 8KB         │ ├────────────────┼─────────────┤ │Vendor          │ TI          │ └────────────────┴─────────────┘
Configuration Please use lpmsp430f5529 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = msp430f5529
TI LaunchPad MSP-EXP430F5529LP has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
TI LaunchPad MSP-EXP430FR2311LP Contents • TI LaunchPad MSP-EXP430FR2311LP
┌────────────────┬──────────────┐ │Microcontroller │ MSP430FR2311 │ ├────────────────┼──────────────┤ │Frequency       │ 16MHz        │ ├────────────────┼──────────────┤ │Flash           │ 3.75KB       │ ├────────────────┼──────────────┤ │RAM             │ 1KB          │ ├────────────────┼──────────────┤ │Vendor          │ TI           │ └────────────────┴──────────────┘
Configuration Please use lpmsp430fr2311 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = msp430fr2311