neulab/tldr huggingface dataset:
│framework_mbed      │ The mbed framework The mbed │ │                    │ SDK has been designed to    │ │                    │ provide enough hardware     │ │                    │ abstraction to be intuitive │ │                    │ and concise, yet powerful   │ │                    │ enough to build complex     │ │                    │ projects. It is built on    │ │                    │ the low-level ARM CMSIS     │ │                    │ APIs, allowing you to code  │ │                    │ down to the metal if        │ │                    │ needed. In addition to      │ │                    │ RTOS, USB and Networking    │ │                    │ libraries, a cookbook of    │ │                    │ hundreds of reusable        │ │                    │ peripheral and module       │ │                    │ libraries have been built   │ │                    │ on top of the SDK by the    │ │                    │ mbed Developer Community.   │ ├────────────────────┼─────────────────────────────┤ │framework_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ └────────────────────┴─────────────────────────────┘
M200 V2 Contents • M200 V2
┌────────────────┬───────────────┐ │Microcontroller │ STM32F070CBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 120KB         │ ├────────────────┼───────────────┤ │RAM             │ 14.81KB       │ ├────────────────┼───────────────┤ │Vendor          │ Malyan        │ └────────────────┴───────────────┘
Configuration Please use malyanm200_f070cb ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f070cbt6
Uploading M200 V2 supports the next uploading protocols:
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.
M300 Contents • M300
Configuration Please use malyanm300_f070cb ID for projectconf_env_board option in projectconf:
[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.
Uploading M300 supports the next uploading protocols:
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.
MKR Sharky Contents • MKR Sharky
┌────────────────┬─────────────┐ │Microcontroller │ STM32WB55CG │ ├────────────────┼─────────────┤ │Frequency       │ 64MHz       │ ├────────────────┼─────────────┤ │Flash           │ 512KB       │ ├────────────────┼─────────────┤ │RAM             │ 192.00KB    │ ├────────────────┼─────────────┤ │Vendor          │ Midatronics │ └────────────────┴─────────────┘
Configuration Please use mkr_sharky ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32wb55cg
Uploading MKR Sharky supports the next uploading protocols:
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.
MTS Dragonfly Contents • MTS Dragonfly
┌────────────────┬───────────────┐ │Microcontroller │ STM32F411RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 100MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ MultiTech     │ └────────────────┴───────────────┘
Configuration Please use mts_dragonfly_f411re ID for projectconf_env_board option in projectconf:
[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.
Uploading MTS Dragonfly supports the next uploading protocols:
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.
Malyan M200 V1 Contents • Malyan M200 V1
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103CBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 120KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Malyan        │ └────────────────┴───────────────┘
Configuration Please use malyanm200_f103cb ID for projectconf_env_board option in projectconf:
[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.
Uploading Malyan M200 V1 supports the next uploading protocols:
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.
Maple Contents • Maple
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 108KB         │ ├────────────────┼───────────────┤ │RAM             │ 17KB          │ ├────────────────┼───────────────┤ │Vendor          │ LeafLabs      │ └────────────────┴───────────────┘
Configuration Please use maple ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f103rbt6
Uploading Maple supports the next uploading protocols:
Default protocol is dfu
upload_protocol = dfu
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.
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_libopencm3 │ The libOpenCM3 framework    │ │                     │ aims to create a            │ │                     │ free/libre/open-source      │ │                     │ firmware library for        │ │                     │ various ARM                 │ │                     │ Cortex-M0(+)/M3/M4          │ │                     │ microcontrollers, including │ │                     │ ST STM32, Ti Tiva and       │ │                     │ Stellaris, NXP LPC 11xx,    │ │                     │ 13xx, 15xx, 17xx parts,     │ │                     │ Atmel SAM3, Energy Micro    │ │                     │ EFM32 and others.           │ ├─────────────────────┼─────────────────────────────┤ │framework_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) Contents • Maple (RET6)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 48KB          │ ├────────────────┼───────────────┤ │Vendor          │ LeafLabs      │ └────────────────┴───────────────┘
Configuration Please use maple_ret6 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f103ret6
Uploading Maple (RET6) supports the next uploading protocols:
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.
Maple Mini Bootloader 2.0 Contents • Maple Mini Bootloader 2.0
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103CBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 120KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ LeafLabs      │ └────────────────┴───────────────┘
Configuration Please use maple_mini_b20 ID for projectconf_env_board option in projectconf:
[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.
Uploading Maple Mini Bootloader 2.0 supports the next uploading protocols:
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.
Maple Mini Original Contents • Maple Mini Original
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103CBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 108KB         │ ├────────────────┼───────────────┤ │RAM             │ 17KB          │ ├────────────────┼───────────────┤ │Vendor          │ LeafLabs      │ └────────────────┴───────────────┘
Configuration Please use maple_mini_origin ID for projectconf_env_board option in projectconf:
[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.
Uploading Maple Mini Original supports the next uploading protocols:
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.
Mbed Connect Cloud Contents • Mbed Connect Cloud
┌────────────────┬───────────────┐ │Microcontroller │ STM32F439ZIY6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 2MB           │ ├────────────────┼───────────────┤ │RAM             │ 256KB         │ ├────────────────┼───────────────┤ │Vendor          │ u-blox        │ └────────────────┴───────────────┘
Configuration Please use mbed_connect_odin ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f439ziy6
Uploading Mbed Connect Cloud supports the next uploading protocols:
Mbed Connect Cloud has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
[env:mxchip_az3166] platform = ststm32 board = mxchip_az3166
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.
MultiTech mDot Contents • MultiTech mDot
Configuration Please use mts_mdot_f405rg ID for projectconf_env_board option in projectconf:
[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.
Uploading MultiTech mDot supports the next uploading protocols:
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.
MultiTech mDot F411 Contents • MultiTech mDot F411
Configuration Please use mts_mdot_f411re ID for projectconf_env_board option in projectconf:
[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.
Uploading MultiTech mDot F411 supports the next uploading protocols:
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.
MultiTech xDot Contents • MultiTech xDot
┌────────────────┬───────────────┐ │Microcontroller │ STM32L151CCU6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ MultiTech     │ └────────────────┴───────────────┘
Configuration Please use xdot_l151cc ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32l151ccu6
Uploading MultiTech xDot supports the next uploading protocols:
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.
Frameworks ┌────────────────────┬─────────────────────────────┐ │Name                │ Description                 │ ├────────────────────┼─────────────────────────────┤ │framework_mbed      │ The mbed framework The mbed │ │                    │ SDK has been designed to    │ │                    │ provide enough hardware     │ │                    │ abstraction to be intuitive │ │                    │ and concise, yet powerful   │ │                    │ enough to build complex     │ │                    │ projects. It is built on    │ │                    │ the low-level ARM CMSIS     │ │                    │ APIs, allowing you to code  │ │                    │ down to the metal if        │ │                    │ needed. In addition to      │ │                    │ RTOS, USB and Networking    │ │                    │ libraries, a cookbook of    │ │                    │ hundreds of reusable        │ │                    │ peripheral and module       │ │                    │ libraries have been built   │ │                    │ on top of the SDK by the    │ │                    │ mbed Developer Community.   │ └────────────────────┴─────────────────────────────┘
N2+ Contents • N2+
┌────────────────┬───────────────┐ │Microcontroller │ STM32F405RGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 192KB         │ ├────────────────┼───────────────┤ │Vendor          │ Netduino      │ └────────────────┴───────────────┘
Configuration Please use netduino2plus ID for projectconf_env_board option in projectconf:
[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.
Uploading N2+ supports the next uploading protocols:
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 │ ├──────────────────────┼──────────┼─────────┤ │debugging_tool_jlink  │          │         │ ├──────────────────────┼──────────┼─────────┤ │debugging_tool_stlink │          │ Yes     │ └──────────────────────┴──────────┴─────────┘
NAMote72 Contents • NAMote72
┌────────────────┬─────────────┐ │Microcontroller │ STM32L152RC │ ├────────────────┼─────────────┤ │Frequency       │ 32MHz       │ ├────────────────┼─────────────┤ │Flash           │ 256KB       │ ├────────────────┼─────────────┤ │RAM             │ 32KB        │ ├────────────────┼─────────────┤ │Vendor          │ Semtech     │ └────────────────┴─────────────┘
Configuration Please use mote_l152rc ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32l152rc
Uploading NAMote72 supports the next uploading protocols:
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.
Nucleo G071RB Contents • Nucleo G071RB
┌────────────────┬───────────────┐ │Microcontroller │ STM32G071RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 64MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 36KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_g071rb ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32g071rbt6
Uploading Nucleo G071RB supports the next uploading protocols:
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.
Nucleo G431KB Contents • Nucleo G431KB
┌────────────────┬───────────────┐ │Microcontroller │ STM32G431KBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 170MHz        │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_g431kb ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32g431kbt6
; change MCU frequency board_build.f_cpu = 170000000L
Uploading Nucleo G431KB supports the next uploading protocols:
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.
Nucleo G431RB Contents • Nucleo G431RB
┌────────────────┬───────────────┐ │Microcontroller │ STM32G431RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 170MHz        │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_g431rb ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32g431rbt6
Uploading Nucleo G431RB supports the next uploading protocols:
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.
Nucleo G474RE Contents • Nucleo G474RE
┌────────────────┬───────────────┐ │Microcontroller │ STM32G474RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 170MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_g474re ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32g474ret6
Uploading Nucleo G474RE supports the next uploading protocols:
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.
OLIMEXINO-STM32 Contents • OLIMEXINO-STM32
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Olimex        │ └────────────────┴───────────────┘
Configuration Please use olimexino ID for projectconf_env_board option in projectconf:
[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.
Uploading OLIMEXINO-STM32 supports the next uploading protocols:
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.
Olimex STM32-P405 Contents • Olimex STM32-P405
┌────────────────┬───────────────┐ │Microcontroller │ STM32F405RGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 192KB         │ ├────────────────┼───────────────┤ │Vendor          │ Olimex        │ └────────────────┴───────────────┘
Configuration Please use olimex_p405 ID for projectconf_env_board option in projectconf:
[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.
Uploading Olimex STM32-P405 supports the next uploading protocols:
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.
P-Nucleo WB55RG Contents • P-Nucleo WB55RG
┌────────────────┬─────────────┐ │Microcontroller │ STM32WB55RG │ ├────────────────┼─────────────┤ │Frequency       │ 64MHz       │ ├────────────────┼─────────────┤ │Flash           │ 512KB       │ ├────────────────┼─────────────┤ │RAM             │ 192.00KB    │ ├────────────────┼─────────────┤ │Vendor          │ ST          │ └────────────────┴─────────────┘
Configuration Please use nucleo_wb55rg_p ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32wb55rg
Uploading P-Nucleo WB55RG supports the next uploading protocols:
P-Nucleo WB55RG has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Piconomix PX-HER0 Contents • Piconomix PX-HER0
┌────────────────┬─────────────┐ │Microcontroller │ STM32L072RB │ ├────────────────┼─────────────┤ │Frequency       │ 32MHz       │ ├────────────────┼─────────────┤ │Flash           │ 128KB       │ ├────────────────┼─────────────┤ │RAM             │ 20KB        │ ├────────────────┼─────────────┤ │Vendor          │ Piconomix   │ └────────────────┴─────────────┘
Configuration Please use piconomix_px_her0 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32l072rb
Uploading Piconomix PX-HER0 supports the next uploading protocols:
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.
PrntrBoard V2 Contents • PrntrBoard V2
┌────────────────┬─────────────┐ │Microcontroller │ STM32F407RE │ ├────────────────┼─────────────┤ │Frequency       │ 168MHz      │ ├────────────────┼─────────────┤ │Flash           │ 512KB       │ ├────────────────┼─────────────┤ │RAM             │ 192KB       │ ├────────────────┼─────────────┤ │Vendor          │ PrntrBoard  │ └────────────────┴─────────────┘
Configuration Please use prntr_v2 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f407re
Uploading PrntrBoard V2 supports the next uploading protocols:
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.
RAK811 LoRa Tracker Contents • RAK811 LoRa Tracker
┌────────────────┬───────────────┐ │Microcontroller │ STM32L151RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ RAK           │ └────────────────┴───────────────┘
Configuration Please use rak811_tracker ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32l151rbt6
Uploading RAK811 LoRa Tracker supports the next uploading protocols:
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.
┌────────────────┬───────────────┐ │Microcontroller │ STM32L151RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ RAK           │ └────────────────┴───────────────┘
Configuration Please use rak811_tracker_32 ID for projectconf_env_board option in projectconf:
[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.
RHF76 052 Contents • RHF76 052
┌────────────────┬───────────────┐ │Microcontroller │ STM32L051C8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 8KB           │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use rhf76_052 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32l051c8t6
Uploading RHF76 052 supports the next uploading protocols:
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.
RushUp Cloud-JAM Contents • RushUp Cloud-JAM
┌────────────────┬───────────────┐ │Microcontroller │ STM32F401RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 84MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 96KB          │ ├────────────────┼───────────────┤ │Vendor          │ RushUp        │ └────────────────┴───────────────┘
Configuration Please use cloud_jam ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f401ret6
Uploading RushUp Cloud-JAM supports the next uploading protocols:
RushUp Cloud-JAM has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
RushUp Cloud-JAM L4 Contents • RushUp Cloud-JAM L4
┌────────────────┬───────────────┐ │Microcontroller │ STM32L476RGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ RushUp        │ └────────────────┴───────────────┘
Configuration Please use cloud_jam_l4 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32l476rgt6
Uploading RushUp Cloud-JAM L4 supports the next uploading protocols:
RushUp Cloud-JAM L4 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST 32F3348DISCOVERY Contents • ST 32F3348DISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F334C8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 12KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f334c8 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f334c8t6
Uploading ST 32F3348DISCOVERY supports the next uploading protocols:
ST 32F3348DISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST 32F401CDISCOVERY Contents • ST 32F401CDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F401VCT6 │ ├────────────────┼───────────────┤ │Frequency       │ 84MHz         │ └────────────────┴───────────────┘
│Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f401vc ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f401vct6
Uploading ST 32F401CDISCOVERY supports the next uploading protocols:
ST 32F401CDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST 32F411EDISCOVERY Contents • ST 32F411EDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F411VET6 │ ├────────────────┼───────────────┤ │Frequency       │ 100MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f411ve ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f411vet6
Uploading ST 32F411EDISCOVERY supports the next uploading protocols:
ST 32F411EDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
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.         │ ├────────────────────┼─────────────────────────────┤ │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.           │ └────────────────────┴─────────────────────────────┘
ST 32F413HDISCOVERY Contents • ST 32F413HDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F413ZHT6 │ ├────────────────┼───────────────┤ │Frequency       │ 100MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f413zh ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f413zht6
Uploading ST 32F413HDISCOVERY supports the next uploading protocols:
ST 32F413HDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST 32F429IDISCOVERY Contents • ST 32F429IDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F429ZIT6 │ ├────────────────┼───────────────┤ │Frequency       │ 180MHz        │ ├────────────────┼───────────────┤ │Flash           │ 2MB           │ ├────────────────┼───────────────┤ │RAM             │ 256KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f429zi ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f429zit6
Uploading ST 32F429IDISCOVERY supports the next uploading protocols:
ST 32F429IDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST 32F469IDISCOVERY Contents • ST 32F469IDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F469NIH6 │ ├────────────────┼───────────────┤ │Frequency       │ 180MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 384KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f469ni ID for projectconf_env_board option in projectconf:
[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.
Uploading ST 32F469IDISCOVERY supports the next uploading protocols:
ST 32F469IDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST 32F746GDISCOVERY Contents • ST 32F746GDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F746NGH6 │ ├────────────────┼───────────────┤ │Frequency       │ 216MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 320KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f746ng ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f746ngh6
Uploading ST 32F746GDISCOVERY supports the next uploading protocols:
ST 32F746GDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
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_mbed      │ The mbed framework The mbed │ │                    │ SDK has been designed to    │ │                    │ provide enough hardware     │ │                    │ abstraction to be intuitive │ │                    │ and concise, yet powerful   │ │                    │ enough to build complex     │ │                    │ projects. It is built on    │ │                    │ the low-level ARM CMSIS     │ │                    │ APIs, allowing you to code  │ │                    │ down to the metal if        │ │                    │ needed. In addition to      │ │                    │ RTOS, USB and Networking    │ │                    │ libraries, a cookbook of    │ │                    │ hundreds of reusable        │ │                    │ peripheral and module       │ │                    │ libraries have been built   │ │                    │ on top of the SDK by the    │ │                    │ mbed Developer Community.   │ ├────────────────────┼─────────────────────────────┤ │framework_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ ├────────────────────┼─────────────────────────────┤ │framework_zephyr    │ The Zephyr Project is a     │ │                    │ scalable real-time          │ │                    │ operating system (RTOS)     │ │                    │ supporting multiple         │ │                    │ hardware architectures,     │ │                    │ optimized for resource      │ │                    │ constrained devices, and    │ │                    │ built with safety and       │ │                    │ security in mind.           │ └────────────────────┴─────────────────────────────┘
ST 32F769IDISCOVERY Contents • ST 32F769IDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F769NIH6 │ ├────────────────┼───────────────┤ │Frequency       │ 216MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 512KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f769ni ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32f769nih6
Uploading ST 32F769IDISCOVERY supports the next uploading protocols:
ST 32F769IDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST 32L0538DISCOVERY Contents • ST 32L0538DISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32L053C8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 8KB           │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_l053c8 ID for projectconf_env_board option in projectconf:
[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.
; change microcontroller board_build.mcu = stm32l053c8t6
Uploading ST 32L0538DISCOVERY supports the next uploading protocols:
ST 32L0538DISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST 32L100DISCOVERY Contents • ST 32L100DISCOVERY