neulab/tldr huggingface dataset:
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_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ └────────────────────┴─────────────────────────────┘
3D Printer control board Contents • 3D Printer control board
┌────────────────┬───────────────┐ │Microcontroller │ STM32F446RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 180MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ RUMBA         │ └────────────────┴───────────────┘
Configuration Please use rumba32_f446ve ID for projectconf_env_board option in projectconf:
[env:rumba32_f446ve] platform = ststm32 board = rumba32_f446ve
You can override default 3D Printer control board settings per build environment using board_*** option, where *** is a JSON object path from board manifest rumba32_f446ve.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f446ret6
Uploading 3D Printer control board supports the next uploading protocols:
3D Printer control board does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
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_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ └────────────────────┴─────────────────────────────┘
3D printer controller Contents • 3D printer controller
┌────────────────┬───────────────┐ │Microcontroller │ STM32F765VIT6 │ ├────────────────┼───────────────┤ │Frequency       │ 216MHz        │ ├────────────────┼───────────────┤ │Flash           │ 2MB           │ ├────────────────┼───────────────┤ │RAM             │ 512KB         │ ├────────────────┼───────────────┤ │Vendor          │ RemRam        │ └────────────────┴───────────────┘
Configuration Please use remram_v1 ID for projectconf_env_board option in projectconf:
[env:remram_v1] platform = ststm32 board = remram_v1
You can override default 3D printer controller settings per build environment using board_*** option, where *** is a JSON object path from board manifest remram_v1.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f765vit6
Uploading 3D printer controller supports the next uploading protocols:
3D printer controller has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
3DP001V1 Evaluation board for 3D printer Contents • 3DP001V1 Evaluation board for 3D printer
┌────────────────┬───────────────┐ │Microcontroller │ STM32F401VGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 84MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 96KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use st3dp001_eval ID for projectconf_env_board option in projectconf:
[env:st3dp001_eval] platform = ststm32 board = st3dp001_eval
You can override default 3DP001V1 Evaluation board for 3D printer settings per build environment using board_*** option, where *** is a JSON object path from board manifest st3dp001_eval.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f401vgt6
Uploading 3DP001V1 Evaluation board for 3D printer supports the next uploading protocols:
3DP001V1 Evaluation board for 3D printer has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
│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_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ └────────────────────┴─────────────────────────────┘
96Boards Argonkey (STEVAL-MKI187V1) Contents • 96Boards Argonkey (STEVAL-MKI187V1)
┌────────────────┬─────────────┐ │Microcontroller │ STM32F412CG │ ├────────────────┼─────────────┤ │Frequency       │ 100MHz      │ ├────────────────┼─────────────┤ │Flash           │ 1MB         │ ├────────────────┼─────────────┤ │RAM             │ 256KB       │ ├────────────────┼─────────────┤ │Vendor          │ 96Boards    │ └────────────────┴─────────────┘
Configuration Please use b96b_argonkey ID for projectconf_env_board option in projectconf:
[env:b96b_argonkey] platform = ststm32 board = b96b_argonkey
You can override default 96Boards Argonkey (STEVAL-MKI187V1) settings per build environment using board_*** option, where *** is a JSON object path from board manifest b96b_argonkey.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f412cg
Uploading 96Boards Argonkey (STEVAL-MKI187V1) supports the next uploading protocols:
96Boards Argonkey (STEVAL-MKI187V1) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
96Boards B96B-F446VE Contents • 96Boards B96B-F446VE
┌────────────────┬───────────────┐ │Microcontroller │ STM32F446VET6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ 96Boards      │ └────────────────┴───────────────┘
Configuration Please use b96b_f446ve ID for projectconf_env_board option in projectconf:
[env:b96b_f446ve] platform = ststm32 board = b96b_f446ve
You can override default 96Boards B96B-F446VE settings per build environment using board_*** option, where *** is a JSON object path from board manifest b96b_f446ve.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f446vet6
Uploading 96Boards B96B-F446VE supports the next uploading protocols:
96Boards B96B-F446VE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Frameworks ┌────────────────────┬─────────────────────────────┐ │Name                │ Description                 │ ├────────────────────┼─────────────────────────────┤ │framework_mbed      │ The mbed framework The mbed │ │                    │ SDK has been designed to    │ │                    │ provide enough hardware     │ │                    │ abstraction to be intuitive │ │                    │ and concise, yet powerful   │ │                    │ enough to build complex     │ │                    │ projects. It is built on    │ │                    │ the low-level ARM CMSIS     │ │                    │ APIs, allowing you to code  │ │                    │ down to the metal if        │ │                    │ needed. In addition to      │ │                    │ RTOS, USB and Networking    │ │                    │ libraries, a cookbook of    │ │                    │ hundreds of reusable        │ │                    │ peripheral and module       │ │                    │ libraries have been built   │ │                    │ on top of the SDK by the    │ │                    │ mbed Developer Community.   │ ├────────────────────┼─────────────────────────────┤ │framework_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ ├────────────────────┼─────────────────────────────┤ │framework_zephyr    │ The Zephyr Project is a     │ │                    │ scalable real-time          │ │                    │ operating system (RTOS)     │ │                    │ supporting multiple         │ │                    │ hardware architectures,     │ │                    │ optimized for resource      │ │                    │ constrained devices, and    │ │                    │ built with safety and       │ │                    │ security in mind.           │ └────────────────────┴─────────────────────────────┘
96Boards Neonkey Contents • 96Boards Neonkey
┌────────────────┬─────────────┐ │Microcontroller │ STM32F411CE │ ├────────────────┼─────────────┤ │Frequency       │ 100MHz      │ ├────────────────┼─────────────┤ │Flash           │ 512KB       │ ├────────────────┼─────────────┤ │RAM             │ 128KB       │ ├────────────────┼─────────────┤ │Vendor          │ 96Boards    │ └────────────────┴─────────────┘
Configuration Please use b96b_neonkey ID for projectconf_env_board option in projectconf:
[env:b96b_neonkey] platform = ststm32 board = b96b_neonkey
You can override default 96Boards Neonkey settings per build environment using board_*** option, where *** is a JSON object path from board manifest b96b_neonkey.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f411ce
Uploading 96Boards Neonkey supports the next uploading protocols:
96Boards Neonkey does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Adafruit Feather STM32F405 Contents • Adafruit Feather STM32F405
┌────────────────┬───────────────┐ │Microcontroller │ STM32F405RGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ Adafruit      │ └────────────────┴───────────────┘
Configuration Please use adafruit_feather_f405 ID for projectconf_env_board option in projectconf:
[env:adafruit_feather_f405] platform = ststm32 board = adafruit_feather_f405
You can override default Adafruit Feather STM32F405 settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_f405.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f405rgt6
Uploading Adafruit Feather STM32F405 supports the next uploading protocols:
• dfu
Adafruit Feather STM32F405 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
AfroFlight Rev5 (8MHz) Contents • AfroFlight Rev5 (8MHz)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103CBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ AfroFlight    │ └────────────────┴───────────────┘
Configuration Please use afroflight_f103cb ID for projectconf_env_board option in projectconf:
[env:afroflight_f103cb] platform = ststm32 board = afroflight_f103cb
You can override default AfroFlight Rev5 (8MHz) settings per build environment using board_*** option, where *** is a JSON object path from board manifest afroflight_f103cb.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103cbt6
Uploading AfroFlight Rev5 (8MHz) supports the next uploading protocols:
AfroFlight Rev5 (8MHz) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
│debugging_tool_blackmagic │          │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_stlink     │          │         │ └──────────────────────────┴──────────┴─────────┘
Armstrap Eagle 1024 Contents • Armstrap Eagle 1024
┌────────────────┬───────────────┐ │Microcontroller │ STM32F417VGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 192KB         │ ├────────────────┼───────────────┤ │Vendor          │ Armstrap      │ └────────────────┴───────────────┘
Configuration Please use armstrap_eagle1024 ID for projectconf_env_board option in projectconf:
[env:armstrap_eagle1024] platform = ststm32 board = armstrap_eagle1024
You can override default Armstrap Eagle 1024 settings per build environment using board_*** option, where *** is a JSON object path from board manifest armstrap_eagle1024.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f417vgt6
Uploading Armstrap Eagle 1024 supports the next uploading protocols:
Armstrap Eagle 1024 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
┌──────────────────────────┬──────────┬─────────┐ │Compatible Tools          │ On-board │ Default │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_blackmagic │ Yes      │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_stlink     │          │         │ └──────────────────────────┴──────────┴─────────┘
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_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.         │ └────────────────────┴─────────────────────────────┘
Armstrap Eagle 2048 Contents • Armstrap Eagle 2048
┌────────────────┬───────────────┐ │Microcontroller │ STM32F427VIT6 │ └────────────────┴───────────────┘
│Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1.99MB        │ ├────────────────┼───────────────┤ │RAM             │ 256KB         │ ├────────────────┼───────────────┤ │Vendor          │ Armstrap      │ └────────────────┴───────────────┘
Configuration Please use armstrap_eagle2048 ID for projectconf_env_board option in projectconf:
[env:armstrap_eagle2048] platform = ststm32 board = armstrap_eagle2048
You can override default Armstrap Eagle 2048 settings per build environment using board_*** option, where *** is a JSON object path from board manifest armstrap_eagle2048.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f427vit6
Uploading Armstrap Eagle 2048 supports the next uploading protocols:
Armstrap Eagle 2048 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Armstrap Eagle 512 Contents • Armstrap Eagle 512
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407VET6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 192KB         │ ├────────────────┼───────────────┤ │Vendor          │ Armstrap      │ └────────────────┴───────────────┘
Configuration Please use armstrap_eagle512 ID for projectconf_env_board option in projectconf:
[env:armstrap_eagle512] platform = ststm32 board = armstrap_eagle512
You can override default Armstrap Eagle 512 settings per build environment using board_*** option, where *** is a JSON object path from board manifest armstrap_eagle512.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Armstrap Eagle 512 supports the next uploading protocols:
Armstrap Eagle 512 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
│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.         │ └────────────────────┴─────────────────────────────┘
Black STM32F407VE Contents • Black STM32F407VE
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407VET6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use black_f407ve ID for projectconf_env_board option in projectconf:
[env:black_f407ve] platform = ststm32 board = black_f407ve
You can override default Black STM32F407VE settings per build environment using board_*** option, where *** is a JSON object path from board manifest black_f407ve.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Black STM32F407VE supports the next uploading protocols:
Black STM32F407VE does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Black STM32F407VG Contents • Black STM32F407VG
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407VGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use black_f407vg ID for projectconf_env_board option in projectconf:
[env:black_f407vg] platform = ststm32 board = black_f407vg
You can override default Black STM32F407VG settings per build environment using board_*** option, where *** is a JSON object path from board manifest black_f407vg.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f407vgt6
Uploading Black STM32F407VG supports the next uploading protocols:
Black STM32F407VG does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Black STM32F407ZE Contents • Black STM32F407ZE
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407ZET6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use black_f407ze ID for projectconf_env_board option in projectconf:
[env:black_f407ze] platform = ststm32 board = black_f407ze
You can override default Black STM32F407ZE settings per build environment using board_*** option, where *** is a JSON object path from board manifest black_f407ze.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f407zet6
Uploading Black STM32F407ZE supports the next uploading protocols:
Black STM32F407ZE does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
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_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.         │ └────────────────────┴─────────────────────────────┘
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407ZGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use black_f407zg ID for projectconf_env_board option in projectconf:
[env:black_f407zg] platform = ststm32 board = black_f407zg
You can override default Black STM32F407ZE settings per build environment using board_*** option, where *** is a JSON object path from board manifest black_f407zg.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f407zgt6
BlackPill F103C8 Contents • BlackPill F103C8
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103C8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use blackpill_f103c8 ID for projectconf_env_board option in projectconf:
[env:blackpill_f103c8] platform = ststm32 board = blackpill_f103c8
You can override default BlackPill F103C8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest blackpill_f103c8.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103c8t6
Uploading BlackPill F103C8 supports the next uploading protocols:
BlackPill F103C8 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
BlackPill F103C8 (128k) Contents • BlackPill F103C8 (128k)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103C8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use blackpill_f103c8_128 ID for projectconf_env_board option in projectconf:
[env:blackpill_f103c8_128] platform = ststm32 board = blackpill_f103c8_128
You can override default BlackPill F103C8 (128k) settings per build environment using board_*** option, where *** is a JSON object path from board manifest blackpill_f103c8_128.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading BlackPill F103C8 (128k) supports the next uploading protocols:
BlackPill F103C8 (128k) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
[env:blackpill_f401cc] platform = ststm32 board = blackpill_f401cc
You can override default BlackPill F401CC settings per build environment using board_*** option, where *** is a JSON object path from board manifest blackpill_f401cc.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f401cct6
Uploading BlackPill F401CC supports the next uploading protocols:
BlackPill F401CC does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Blue STM32F407VE Mini Contents • Blue STM32F407VE Mini
Configuration Please use blue_f407ve_mini ID for projectconf_env_board option in projectconf:
[env:blue_f407ve_mini] platform = ststm32 board = blue_f407ve_mini
You can override default Blue STM32F407VE Mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest blue_f407ve_mini.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Blue STM32F407VE Mini supports the next uploading protocols:
Blue STM32F407VE Mini does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
BluePill F103C6 Contents • BluePill F103C6
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103C6T6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 32KB          │ ├────────────────┼───────────────┤ │RAM             │ 10KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use bluepill_f103c6 ID for projectconf_env_board option in projectconf:
[env:bluepill_f103c6] platform = ststm32 board = bluepill_f103c6
You can override default BluePill F103C6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluepill_f103c6.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103c6t6
Uploading BluePill F103C6 supports the next uploading protocols:
BluePill F103C6 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
BluePill F103C8 Contents • BluePill F103C8
Configuration Please use bluepill_f103c8 ID for projectconf_env_board option in projectconf:
[env:bluepill_f103c8] platform = ststm32 board = bluepill_f103c8
You can override default BluePill F103C8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluepill_f103c8.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading BluePill F103C8 supports the next uploading protocols:
BluePill F103C8 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
BluePill F103C8 (128k) Contents • BluePill F103C8 (128k)
Configuration Please use bluepill_f103c8_128k ID for projectconf_env_board option in projectconf:
[env:bluepill_f103c8_128k] platform = ststm32 board = bluepill_f103c8_128k
You can override default BluePill F103C8 (128k) settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluepill_f103c8_128k.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading BluePill F103C8 (128k) supports the next uploading protocols:
BluePill F103C8 (128k) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Core board F401RCT6 Contents • Core board F401RCT6
┌────────────────┬───────────────┐ │Microcontroller │ STM32F401RCT6 │ ├────────────────┼───────────────┤ │Frequency       │ 84MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use coreboard_f401rc ID for projectconf_env_board option in projectconf:
[env:coreboard_f401rc] platform = ststm32 board = coreboard_f401rc
You can override default Core board F401RCT6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest coreboard_f401rc.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f401rct6
Uploading Core board F401RCT6 supports the next uploading protocols:
• hid
Core board F401RCT6 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
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_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ └────────────────────┴─────────────────────────────┘
Demo F030F4 Contents • Demo F030F4
┌────────────────┬───────────────┐ │Microcontroller │ STM32F030F4P6 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 16KB          │ ├────────────────┼───────────────┤ │RAM             │ 4KB           │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use demo_f030f4 ID for projectconf_env_board option in projectconf:
[env:demo_f030f4] platform = ststm32 board = demo_f030f4
You can override default Demo F030F4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest demo_f030f4.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f030f4p6
Uploading Demo F030F4 supports the next uploading protocols:
Demo F030F4 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Espotel LoRa Module Contents • Espotel LoRa Module
┌────────────────┬───────────────┐ │Microcontroller │ STM32F411RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 100MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ Espotel       │ └────────────────┴───────────────┘
Configuration Please use elmo_f411re ID for projectconf_env_board option in projectconf:
[env:elmo_f411re] platform = ststm32 board = elmo_f411re
You can override default Espotel LoRa Module settings per build environment using board_*** option, where *** is a JSON object path from board manifest elmo_f411re.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f411ret6
Uploading Espotel LoRa Module supports the next uploading protocols:
Espotel LoRa Module does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Frameworks ┌────────────────────┬─────────────────────────────┐ │Name                │ Description                 │ ├────────────────────┼─────────────────────────────┤ │framework_mbed      │ The mbed framework The mbed │ │                    │ SDK has been designed to    │ │                    │ provide enough hardware     │ │                    │ abstraction to be intuitive │ │                    │ and concise, yet powerful   │ │                    │ enough to build complex     │ │                    │ projects. It is built on    │ │                    │ the low-level ARM CMSIS     │ │                    │ APIs, allowing you to code  │ │                    │ down to the metal if        │ │                    │ needed. In addition to      │ │                    │ RTOS, USB and Networking    │ │                    │ libraries, a cookbook of    │ │                    │ hundreds of reusable        │ │                    │ peripheral and module       │ │                    │ libraries have been built   │ │                    │ on top of the SDK by the    │ │                    │ mbed Developer Community.   │ ├────────────────────┼─────────────────────────────┤ │framework_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ └────────────────────┴─────────────────────────────┘
F407VG Contents • F407VG
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407VGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ Diymore       │ └────────────────┴───────────────┘
Configuration Please use diymore_f407vgt ID for projectconf_env_board option in projectconf:
[env:diymore_f407vgt] platform = ststm32 board = diymore_f407vgt
You can override default F407VG settings per build environment using board_*** option, where *** is a JSON object path from board manifest diymore_f407vgt.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading F407VG supports the next uploading protocols:
F407VG does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
FK407M1 Contents • FK407M1
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407VET6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use fk407m1 ID for projectconf_env_board option in projectconf:
[env:fk407m1] platform = ststm32 board = fk407m1
You can override default FK407M1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest fk407m1.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading FK407M1 supports the next uploading protocols:
FK407M1 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
L476DMW1K Contents • L476DMW1K
┌────────────────┬───────────────┐ │Microcontroller │ STM32L476VGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ rhomb.io      │ └────────────────┴───────────────┘
Configuration Please use rhombio_l476dmw1k ID for projectconf_env_board option in projectconf:
[env:rhombio_l476dmw1k] platform = ststm32 board = rhombio_l476dmw1k
You can override default L476DMW1K settings per build environment using board_*** option, where *** is a JSON object path from board manifest rhombio_l476dmw1k.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l476vgt6
Uploading L476DMW1K supports the next uploading protocols:
L476DMW1K has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.