neulab/tldr huggingface dataset:
You can override default ST Nucleo L486RG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l486rg.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l486rgt6
Uploading ST Nucleo L486RG supports the next uploading protocols:
ST Nucleo L486RG has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L496ZG Contents • ST Nucleo L496ZG
┌────────────────┬───────────────┐ │Microcontroller │ STM32L496ZGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l496zg ID for projectconf_env_board option in projectconf:
[env:nucleo_l496zg] platform = ststm32 board = nucleo_l496zg
You can override default ST Nucleo L496ZG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l496zg.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l496zgt6
Uploading ST Nucleo L496ZG supports the next uploading protocols:
ST Nucleo L496ZG has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L496ZG-P Contents • ST Nucleo L496ZG-P
┌────────────────┬────────────────┐ │Microcontroller │ STM32L496ZGT6P │ ├────────────────┼────────────────┤ │Frequency       │ 80MHz          │ ├────────────────┼────────────────┤ │Flash           │ 1MB            │ ├────────────────┼────────────────┤ │RAM             │ 320KB          │ ├────────────────┼────────────────┤ │Vendor          │ ST             │ └────────────────┴────────────────┘
Configuration Please use nucleo_l496zg_p ID for projectconf_env_board option in projectconf:
[env:nucleo_l496zg_p] platform = ststm32 board = nucleo_l496zg_p
You can override default ST Nucleo L496ZG-P settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l496zg_p.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l496zgt6p
Uploading ST Nucleo L496ZG-P supports the next uploading protocols:
ST Nucleo L496ZG-P has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L4R5ZI Contents • ST Nucleo L4R5ZI
┌────────────────┬───────────────┐ │Microcontroller │ STM32L4R5ZIT6 │ ├────────────────┼───────────────┤ │Frequency       │ 120MHz        │ ├────────────────┼───────────────┤ │Flash           │ 2MB           │ ├────────────────┼───────────────┤ │RAM             │ 640KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l4r5zi ID for projectconf_env_board option in projectconf:
[env:nucleo_l4r5zi] platform = ststm32 board = nucleo_l4r5zi
You can override default ST Nucleo L4R5ZI settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l4r5zi.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l4r5zit6
Uploading ST Nucleo L4R5ZI supports the next uploading protocols:
ST Nucleo L4R5ZI has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST STM32F0308DISCOVERY Contents • ST STM32F0308DISCOVERY
Configuration Please use disco_f030r8 ID for projectconf_env_board option in projectconf:
[env:disco_f030r8] platform = ststm32 board = disco_f030r8
You can override default ST STM32F0308DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f030r8.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST STM32F0308DISCOVERY supports the next uploading protocols:
ST STM32F0308DISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST STM32F0DISCOVERY Contents • ST STM32F0DISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F051R8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 8KB           │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f051r8 ID for projectconf_env_board option in projectconf:
[env:disco_f051r8] platform = ststm32 board = disco_f051r8
You can override default ST STM32F0DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f051r8.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f051r8t6
Uploading ST STM32F0DISCOVERY supports the next uploading protocols:
ST STM32F0DISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST STM32F3DISCOVERY Contents • ST STM32F3DISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F303VCT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 48KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f303vc ID for projectconf_env_board option in projectconf:
[env:disco_f303vc] platform = ststm32 board = disco_f303vc
You can override default ST STM32F3DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f303vc.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f303vct6
Uploading ST STM32F3DISCOVERY supports the next uploading protocols:
ST STM32F3DISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST STM32F4DISCOVERY Contents • ST STM32F4DISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407VGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f407vg ID for projectconf_env_board option in projectconf:
[env:disco_f407vg] platform = ststm32 board = disco_f407vg
You can override default ST STM32F4DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f407vg.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST STM32F4DISCOVERY supports the next uploading protocols:
ST STM32F4DISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST STM32L073Z-EVAL Contents • ST STM32L073Z-EVAL
┌────────────────┬───────────────┐ │Microcontroller │ STM32L073VZT6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 192KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use eval_l073z ID for projectconf_env_board option in projectconf:
[env:eval_l073z] platform = ststm32 board = eval_l073z
You can override default ST STM32L073Z-EVAL settings per build environment using board_*** option, where *** is a JSON object path from board manifest eval_l073z.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l073vzt6
Uploading ST STM32L073Z-EVAL supports the next uploading protocols:
ST STM32L073Z-EVAL has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST STM32LDISCOVERY Contents • ST STM32LDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32L152RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_l152rb ID for projectconf_env_board option in projectconf:
[env:disco_l152rb] platform = ststm32 board = disco_l152rb
You can override default ST STM32LDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l152rb.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l152rbt6
Uploading ST STM32LDISCOVERY supports the next uploading protocols:
ST STM32LDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST STM32VLDISCOVERY Contents • ST STM32VLDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32F100RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 24MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 8KB           │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f100rb ID for projectconf_env_board option in projectconf:
[env:disco_f100rb] platform = ststm32 board = disco_f100rb
You can override default ST STM32VLDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f100rb.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f100rbt6
Uploading ST STM32VLDISCOVERY supports the next uploading protocols:
ST STM32VLDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Sensor Node Contents • ST Sensor Node
┌────────────────┬──────────────┐ │Microcontroller │ STM32L476JG  │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 1MB          │ ├────────────────┼──────────────┤ │RAM             │ 128KB        │ ├────────────────┼──────────────┤ │Vendor          │ Avnet Silica │ └────────────────┴──────────────┘
Configuration Please use silica_sensor_node ID for projectconf_env_board option in projectconf:
[env:silica_sensor_node] platform = ststm32 board = silica_sensor_node
You can override default ST Sensor Node settings per build environment using board_*** option, where *** is a JSON object path from board manifest silica_sensor_node.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l476jg
Uploading ST Sensor Node supports the next uploading protocols:
ST Sensor Node has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
STEVAL-FCU001V1 Flight controller unit evaluation board Contents • STEVAL-FCU001V1 Flight controller unit evaluation board
┌────────────────┬───────────────┐ │Microcontroller │ STM32F401CCU6 │ ├────────────────┼───────────────┤ │Frequency       │ 84MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use steval_fcu001v1 ID for projectconf_env_board option in projectconf:
[env:steval_fcu001v1] platform = ststm32 board = steval_fcu001v1
You can override default STEVAL-FCU001V1 Flight controller unit evaluation board settings per build environment using board_*** option, where *** is a JSON object path from board manifest steval_fcu001v1.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f401ccu6
Uploading STEVAL-FCU001V1 Flight controller unit evaluation board supports the next uploading protocols:
STEVAL-FCU001V1 Flight controller unit evaluation board does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32-E407 Contents • STM32-E407
┌────────────────┬───────────────┐ │Microcontroller │ STM32F407ZGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 168MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ Olimex        │ └────────────────┴───────────────┘
Configuration Please use olimex_e407 ID for projectconf_env_board option in projectconf:
[env:olimex_e407] platform = ststm32 board = olimex_e407
You can override default STM32-E407 settings per build environment using board_*** option, where *** is a JSON object path from board manifest olimex_e407.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading STM32-E407 supports the next uploading protocols:
STM32-E407 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32-H407 Contents • STM32-H407
Configuration Please use olimex_h407 ID for projectconf_env_board option in projectconf:
[env:olimex_h407] platform = ststm32 board = olimex_h407
You can override default STM32-H407 settings per build environment using board_*** option, where *** is a JSON object path from board manifest olimex_h407.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading STM32-H407 supports the next uploading protocols:
STM32-H407 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
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.         │ ├────────────────────┼─────────────────────────────┤ │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.           │ └────────────────────┴─────────────────────────────┘
STM3210C-EVAL Contents • STM3210C-EVAL
┌────────────────┬───────────────┐ │Microcontroller │ STM32F107VCT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use eval_f107vc ID for projectconf_env_board option in projectconf:
[env:eval_f107vc] platform = ststm32 board = eval_f107vc
You can override default STM3210C-EVAL settings per build environment using board_*** option, where *** is a JSON object path from board manifest eval_f107vc.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f107vct6
Uploading STM3210C-EVAL supports the next uploading protocols:
STM3210C-EVAL does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
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.           │ └────────────────────┴─────────────────────────────┘
STM32373C-EVAL Contents • STM32373C-EVAL
┌────────────────┬───────────────┐ │Microcontroller │ STM32F373VCT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use eval_f373vc ID for projectconf_env_board option in projectconf:
[env:eval_f373vc] platform = ststm32 board = eval_f373vc
You can override default STM32373C-EVAL settings per build environment using board_*** option, where *** is a JSON object path from board manifest eval_f373vc.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f373vct6
Uploading STM32373C-EVAL supports the next uploading protocols:
STM32373C-EVAL does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F072-EVAL Contents • STM32F072-EVAL
┌────────────────┬───────────────┐ │Microcontroller │ STM32F072VBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ └────────────────┴───────────────┘
│Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use eval_f072vb ID for projectconf_env_board option in projectconf:
[env:eval_f072vb] platform = ststm32 board = eval_f072vb
You can override default STM32F072-EVAL settings per build environment using board_*** option, where *** is a JSON object path from board manifest eval_f072vb.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f072vbt6
Uploading STM32F072-EVAL supports the next uploading protocols:
STM32F072-EVAL does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103C8 (20k RAM. 64k Flash) Contents • STM32F103C8 (20k RAM. 64k Flash)
Configuration Please use genericSTM32F103C8 ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103C8] platform = ststm32 board = genericSTM32F103C8
You can override default STM32F103C8 (20k RAM. 64k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103C8.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading STM32F103C8 (20k RAM. 64k Flash) supports the next uploading protocols:
STM32F103C8 (20k RAM. 64k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
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_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_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.         │ └─────────────────────┴─────────────────────────────┘
STM32F103CB (20k RAM. 128k Flash) Contents • STM32F103CB (20k RAM. 128k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103CBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103CB ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103CB] platform = ststm32 board = genericSTM32F103CB
You can override default STM32F103CB (20k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103CB.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading STM32F103CB (20k RAM. 128k Flash) supports the next uploading protocols:
STM32F103CB (20k RAM. 128k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
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_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.         │ └─────────────────────┴─────────────────────────────┘
STM32F103R8 (20k RAM. 64 Flash) Contents • STM32F103R8 (20k RAM. 64 Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103R8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ └────────────────┴───────────────┘
│RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103R8 ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103R8] platform = ststm32 board = genericSTM32F103R8
You can override default STM32F103R8 (20k RAM. 64 Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103R8.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103r8t6
Uploading STM32F103R8 (20k RAM. 64 Flash) supports the next uploading protocols:
STM32F103R8 (20k RAM. 64 Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103RB (20k RAM. 128k Flash) Contents • STM32F103RB (20k RAM. 128k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103RB ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103RB] platform = ststm32 board = genericSTM32F103RB
You can override default STM32F103RB (20k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103RB.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading STM32F103RB (20k RAM. 128k Flash) supports the next uploading protocols:
STM32F103RB (20k RAM. 128k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103RE ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103RE] platform = ststm32 board = genericSTM32F103RE
You can override default STM32F103RE (64k RAM. 512k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103RE.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading STM32F103RE (64k RAM. 512k Flash) supports the next uploading protocols:
STM32F103RE (64k RAM. 512k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103T8 (20k RAM. 64k Flash) Contents • STM32F103T8 (20k RAM. 64k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103T8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103T8 ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103T8] platform = ststm32 board = genericSTM32F103T8
You can override default STM32F103T8 (20k RAM. 64k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103T8.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103t8t6
Uploading STM32F103T8 (20k RAM. 64k Flash) supports the next uploading protocols:
STM32F103T8 (20k RAM. 64k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103TB (20k RAM. 128k Flash) Contents • STM32F103TB (20k RAM. 128k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103TBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103TB ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103TB] platform = ststm32 board = genericSTM32F103TB
You can override default STM32F103TB (20k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103TB.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103tbt6
Uploading STM32F103TB (20k RAM. 128k Flash) supports the next uploading protocols:
STM32F103TB (20k RAM. 128k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103VB (20k RAM. 128k Flash) Contents • STM32F103VB (20k RAM. 128k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103VBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103VB ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103VB] platform = ststm32 board = genericSTM32F103VB
You can override default STM32F103VB (20k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103VB.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103vbt6
Uploading STM32F103VB (20k RAM. 128k Flash) supports the next uploading protocols:
STM32F103VB (20k RAM. 128k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103VC (48k RAM. 256k Flash) Contents • STM32F103VC (48k RAM. 256k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103VCT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 48KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103VC ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103VC] platform = ststm32 board = genericSTM32F103VC
You can override default STM32F103VC (48k RAM. 256k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103VC.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103vct6
Uploading STM32F103VC (48k RAM. 256k Flash) supports the next uploading protocols:
STM32F103VC (48k RAM. 256k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103VD (64k RAM. 384k Flash) Contents • STM32F103VD (64k RAM. 384k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103VDT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 384KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103VD ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103VD] platform = ststm32 board = genericSTM32F103VD
You can override default STM32F103VD (64k RAM. 384k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103VD.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103vdt6
Uploading STM32F103VD (64k RAM. 384k Flash) supports the next uploading protocols:
STM32F103VD (64k RAM. 384k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103VE (64k RAM. 512k Flash) Contents • STM32F103VE (64k RAM. 512k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103VET6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103VE ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103VE] platform = ststm32 board = genericSTM32F103VE
You can override default STM32F103VE (64k RAM. 512k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103VE.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103vet6
Uploading STM32F103VE (64k RAM. 512k Flash) supports the next uploading protocols:
STM32F103VE (64k RAM. 512k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103ZC (48k RAM. 256k Flash) Contents • STM32F103ZC (48k RAM. 256k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103ZCT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 48KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103ZC ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103ZC] platform = ststm32 board = genericSTM32F103ZC
You can override default STM32F103ZC (48k RAM. 256k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103ZC.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103zct6
Uploading STM32F103ZC (48k RAM. 256k Flash) supports the next uploading protocols:
STM32F103ZC (48k RAM. 256k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103ZD (64k RAM. 384k Flash) Contents • STM32F103ZD (64k RAM. 384k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103ZDT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 384KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103ZD ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103ZD] platform = ststm32 board = genericSTM32F103ZD
You can override default STM32F103ZD (64k RAM. 384k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103ZD.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103zdt6
Uploading STM32F103ZD (64k RAM. 384k Flash) supports the next uploading protocols:
STM32F103ZD (64k RAM. 384k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F103ZE (64k RAM. 512k Flash) Contents • STM32F103ZE (64k RAM. 512k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103ZET6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F103ZE ID for projectconf_env_board option in projectconf:
[env:genericSTM32F103ZE] platform = ststm32 board = genericSTM32F103ZE
You can override default STM32F103ZE (64k RAM. 512k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F103ZE.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f103zet6
Uploading STM32F103ZE (64k RAM. 512k Flash) supports the next uploading protocols:
STM32F103ZE (64k RAM. 512k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
STM32F303CB (32k RAM. 128k Flash) Contents • STM32F303CB (32k RAM. 128k Flash)
┌────────────────┬───────────────┐ │Microcontroller │ STM32F303CBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ Generic       │ └────────────────┴───────────────┘
Configuration Please use genericSTM32F303CB ID for projectconf_env_board option in projectconf:
[env:genericSTM32F303CB] platform = ststm32 board = genericSTM32F303CB
You can override default STM32F303CB (32k RAM. 128k Flash) settings per build environment using board_*** option, where *** is a JSON object path from board manifest genericSTM32F303CB.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f303cbt6
Uploading STM32F303CB (32k RAM. 128k Flash) supports the next uploading protocols:
STM32F303CB (32k RAM. 128k Flash) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.