neulab/tldr huggingface dataset:
┌────────────────┬───────────────┐ │Microcontroller │ STM32L100RCT6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_l100rc ID for projectconf_env_board option in projectconf:
[env:disco_l100rc] platform = ststm32 board = disco_l100rc
You can override default ST 32L100DISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l100rc.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l100rct6
Uploading ST 32L100DISCOVERY supports the next uploading protocols:
ST 32L100DISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Frameworks ┌────────────────────┬─────────────────────────────┐ │Name                │ Description                 │ ├────────────────────┼─────────────────────────────┤ │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.         │ └────────────────────┴─────────────────────────────┘
ST 32L476GDISCOVERY Contents • ST 32L476GDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32L476VGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_l476vg ID for projectconf_env_board option in projectconf:
[env:disco_l476vg] platform = ststm32 board = disco_l476vg
You can override default ST 32L476GDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l476vg.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST 32L476GDISCOVERY supports the next uploading protocols:
ST 32L476GDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST 32L496GDISCOVERY Contents • ST 32L496GDISCOVERY
┌────────────────┬───────────────┐ │Microcontroller │ STM32L496AGI6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 320KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_l496ag ID for projectconf_env_board option in projectconf:
[env:disco_l496ag] platform = ststm32 board = disco_l496ag
You can override default ST 32L496GDISCOVERY settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l496ag.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l496agi6
Uploading ST 32L496GDISCOVERY supports the next uploading protocols:
ST 32L496GDISCOVERY has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST B-L475E-IOT01A Discovery kit Contents • ST B-L475E-IOT01A Discovery kit
┌────────────────┬───────────────┐ │Microcontroller │ STM32L475VGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_l475vg_iot01a ID for projectconf_env_board option in projectconf:
[env:disco_l475vg_iot01a] platform = ststm32 board = disco_l475vg_iot01a
You can override default ST B-L475E-IOT01A Discovery kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l475vg_iot01a.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l475vgt6
Uploading ST B-L475E-IOT01A Discovery kit supports the next uploading protocols:
ST B-L475E-IOT01A Discovery kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST DISCO-L072CZ-LRWAN1 Contents • ST DISCO-L072CZ-LRWAN1
┌────────────────┬─────────────┐ │Microcontroller │ STM32L072CZ │ ├────────────────┼─────────────┤ │Frequency       │ 32MHz       │ ├────────────────┼─────────────┤ │Flash           │ 192KB       │ ├────────────────┼─────────────┤ │RAM             │ 20KB        │ ├────────────────┼─────────────┤ │Vendor          │ ST          │ └────────────────┴─────────────┘
Configuration Please use disco_l072cz_lrwan1 ID for projectconf_env_board option in projectconf:
[env:disco_l072cz_lrwan1] platform = ststm32 board = disco_l072cz_lrwan1
You can override default ST DISCO-L072CZ-LRWAN1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_l072cz_lrwan1.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l072cz
Uploading ST DISCO-L072CZ-LRWAN1 supports the next uploading protocols:
ST DISCO-L072CZ-LRWAN1 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Discovery F072RB Contents • ST Discovery F072RB
┌────────────────┬───────────────┐ │Microcontroller │ STM32F072RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use disco_f072rb ID for projectconf_env_board option in projectconf:
[env:disco_f072rb] platform = ststm32 board = disco_f072rb
You can override default ST Discovery F072RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest disco_f072rb.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f072rbt6
Uploading ST Discovery F072RB supports the next uploading protocols:
ST Discovery F072RB has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F030R8 Contents • ST Nucleo F030R8
┌────────────────┬───────────────┐ │Microcontroller │ STM32F030R8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 8KB           │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f030r8 ID for projectconf_env_board option in projectconf:
[env:nucleo_f030r8] platform = ststm32 board = nucleo_f030r8
You can override default ST Nucleo F030R8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f030r8.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f030r8t6
Uploading ST Nucleo F030R8 supports the next uploading protocols:
ST Nucleo F030R8 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F031K6 Contents • ST Nucleo F031K6
┌────────────────┬───────────────┐ │Microcontroller │ STM32F031K6T6 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 32KB          │ ├────────────────┼───────────────┤ │RAM             │ 4KB           │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f031k6 ID for projectconf_env_board option in projectconf:
[env:nucleo_f031k6] platform = ststm32 board = nucleo_f031k6
You can override default ST Nucleo F031K6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f031k6.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f031k6t6
Uploading ST Nucleo F031K6 supports the next uploading protocols:
ST Nucleo F031K6 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F042K6 Contents • ST Nucleo F042K6
┌────────────────┬───────────────┐ │Microcontroller │ STM32F042K6T6 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 32KB          │ ├────────────────┼───────────────┤ │RAM             │ 6KB           │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f042k6 ID for projectconf_env_board option in projectconf:
[env:nucleo_f042k6] platform = ststm32 board = nucleo_f042k6
You can override default ST Nucleo F042K6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f042k6.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f042k6t6
Uploading ST Nucleo F042K6 supports the next uploading protocols:
ST Nucleo F042K6 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F070RB Contents • ST Nucleo F070RB
┌────────────────┬───────────────┐ │Microcontroller │ STM32F070RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f070rb ID for projectconf_env_board option in projectconf:
[env:nucleo_f070rb] platform = ststm32 board = nucleo_f070rb
You can override default ST Nucleo F070RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f070rb.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f070rbt6
Uploading ST Nucleo F070RB supports the next uploading protocols:
ST Nucleo F070RB has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F072RB Contents • ST Nucleo F072RB
Configuration Please use nucleo_f072rb ID for projectconf_env_board option in projectconf:
[env:nucleo_f072rb] platform = ststm32 board = nucleo_f072rb
You can override default ST Nucleo F072RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f072rb.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST Nucleo F072RB supports the next uploading protocols:
ST Nucleo F072RB has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F091RC Contents • ST Nucleo F091RC
┌────────────────┬───────────────┐ │Microcontroller │ STM32F091RCT6 │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f091rc ID for projectconf_env_board option in projectconf:
[env:nucleo_f091rc] platform = ststm32 board = nucleo_f091rc
You can override default ST Nucleo F091RC settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f091rc.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f091rct6
Uploading ST Nucleo F091RC supports the next uploading protocols:
ST Nucleo F091RC has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F103RB Contents • ST Nucleo F103RB
┌────────────────┬───────────────┐ │Microcontroller │ STM32F103RBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 20KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f103rb ID for projectconf_env_board option in projectconf:
[env:nucleo_f103rb] platform = ststm32 board = nucleo_f103rb
You can override default ST Nucleo F103RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f103rb.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST Nucleo F103RB supports the next uploading protocols:
ST Nucleo F103RB has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
│debugging_tool_stlink     │ Yes      │ Yes     │ └──────────────────────────┴──────────┴─────────┘
ST Nucleo F207ZG Contents • ST Nucleo F207ZG
┌────────────────┬───────────────┐ │Microcontroller │ STM32F207ZGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 120MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f207zg ID for projectconf_env_board option in projectconf:
[env:nucleo_f207zg] platform = ststm32 board = nucleo_f207zg
You can override default ST Nucleo F207ZG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f207zg.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f207zgt6
Uploading ST Nucleo F207ZG supports the next uploading protocols:
ST Nucleo F207ZG has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F302R8 Contents • ST Nucleo F302R8
┌────────────────┬───────────────┐ │Microcontroller │ STM32F302R8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f302r8 ID for projectconf_env_board option in projectconf:
[env:nucleo_f302r8] platform = ststm32 board = nucleo_f302r8
You can override default ST Nucleo F302R8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f302r8.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f302r8t6
Uploading ST Nucleo F302R8 supports the next uploading protocols:
ST Nucleo F302R8 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F303K8 Contents • ST Nucleo F303K8
┌────────────────┬───────────────┐ │Microcontroller │ STM32F303K8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 12KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f303k8 ID for projectconf_env_board option in projectconf:
[env:nucleo_f303k8] platform = ststm32 board = nucleo_f303k8
You can override default ST Nucleo F303K8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f303k8.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f303k8t6
Uploading ST Nucleo F303K8 supports the next uploading protocols:
ST Nucleo F303K8 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Frameworks ┌────────────────────┬─────────────────────────────┐ │Name                │ Description                 │ ├────────────────────┼─────────────────────────────┤ │framework_arduino   │ Arduino Wiring-based        │ │                    │ Framework allows writing    │ │                    │ cross-platform software to  │ │                    │ control devices attached to │ │                    │ a wide range of Arduino     │ │                    │ boards to create all kinds  │ │                    │ of creative coding,         │ │                    │ interactive objects, spaces │ │                    │ or physical experiences.    │ ├────────────────────┼─────────────────────────────┤ │framework_mbed      │ The mbed framework The mbed │ │                    │ SDK has been designed to    │ │                    │ provide enough hardware     │ │                    │ abstraction to be intuitive │ │                    │ and concise, yet powerful   │ │                    │ enough to build complex     │ │                    │ projects. It is built on    │ │                    │ the low-level ARM CMSIS     │ │                    │ APIs, allowing you to code  │ │                    │ down to the metal if        │ │                    │ needed. In addition to      │ │                    │ RTOS, USB and Networking    │ │                    │ libraries, a cookbook of    │ │                    │ hundreds of reusable        │ │                    │ peripheral and module       │ │                    │ libraries have been built   │ │                    │ on top of the SDK by the    │ │                    │ mbed Developer Community.   │ ├────────────────────┼─────────────────────────────┤ │framework_stm32cube │ STM32Cube embedded software │ │                    │ libraries, including: The   │ │                    │ HAL hardware abstraction    │ │                    │ layer, enabling portability │ │                    │ between different STM32     │ │                    │ devices via standardized    │ │                    │ API calls; The Low-Layer    │ │                    │ (LL) APIs, a light-weight,  │ │                    │ optimized, expert oriented  │ │                    │ set of APIs designed for    │ │                    │ both performance and        │ │                    │ runtime efficiency.         │ └────────────────────┴─────────────────────────────┘
ST Nucleo F303RE Contents • ST Nucleo F303RE
┌────────────────┬───────────────┐ │Microcontroller │ STM32F303RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f303re ID for projectconf_env_board option in projectconf:
[env:nucleo_f303re] platform = ststm32 board = nucleo_f303re
You can override default ST Nucleo F303RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f303re.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f303ret6
Uploading ST Nucleo F303RE supports the next uploading protocols:
ST Nucleo F303RE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F303ZE Contents • ST Nucleo F303ZE
┌────────────────┬───────────────┐ │Microcontroller │ STM32F303ZET6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ └────────────────┴───────────────┘
│RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f303ze ID for projectconf_env_board option in projectconf:
[env:nucleo_f303ze] platform = ststm32 board = nucleo_f303ze
You can override default ST Nucleo F303ZE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f303ze.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f303zet6
Uploading ST Nucleo F303ZE supports the next uploading protocols:
ST Nucleo F303ZE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F334R8 Contents • ST Nucleo F334R8
┌────────────────┬───────────────┐ │Microcontroller │ STM32F334R8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 72MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 16KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f334r8 ID for projectconf_env_board option in projectconf:
[env:nucleo_f334r8] platform = ststm32 board = nucleo_f334r8
You can override default ST Nucleo F334R8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f334r8.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f334r8t6
Uploading ST Nucleo F334R8 supports the next uploading protocols:
ST Nucleo F334R8 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F401RE Contents • ST Nucleo F401RE
┌────────────────┬───────────────┐ │Microcontroller │ STM32F401RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 84MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 96KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f401re ID for projectconf_env_board option in projectconf:
[env:nucleo_f401re] platform = ststm32 board = nucleo_f401re
You can override default ST Nucleo F401RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f401re.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST Nucleo F401RE supports the next uploading protocols:
ST Nucleo F401RE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F410RB Contents • ST Nucleo F410RB
┌────────────────┬───────────────┐ │Microcontroller │ STM32F410RBT6 │ └────────────────┴───────────────┘
│Frequency       │ 100MHz        │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f410rb ID for projectconf_env_board option in projectconf:
[env:nucleo_f410rb] platform = ststm32 board = nucleo_f410rb
You can override default ST Nucleo F410RB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f410rb.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f410rbt6
Uploading ST Nucleo F410RB supports the next uploading protocols:
ST Nucleo F410RB has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F411RE Contents • ST Nucleo F411RE
┌────────────────┬───────────────┐ │Microcontroller │ STM32F411RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 100MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f411re ID for projectconf_env_board option in projectconf:
[env:nucleo_f411re] platform = ststm32 board = nucleo_f411re
You can override default ST Nucleo F411RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f411re.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST Nucleo F411RE supports the next uploading protocols:
ST Nucleo F411RE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F412ZG Contents • ST Nucleo F412ZG
Configuration Please use nucleo_f412zg ID for projectconf_env_board option in projectconf:
[env:nucleo_f412zg] platform = ststm32 board = nucleo_f412zg
You can override default ST Nucleo F412ZG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f412zg.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST Nucleo F412ZG supports the next uploading protocols:
ST Nucleo F412ZG has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F413ZH Contents • ST Nucleo F413ZH
Configuration Please use nucleo_f413zh ID for projectconf_env_board option in projectconf:
[env:nucleo_f413zh] platform = ststm32 board = nucleo_f413zh
You can override default ST Nucleo F413ZH settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f413zh.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST Nucleo F413ZH supports the next uploading protocols:
ST Nucleo F413ZH has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F429ZI Contents • ST Nucleo F429ZI
Configuration Please use nucleo_f429zi ID for projectconf_env_board option in projectconf:
[env:nucleo_f429zi] platform = ststm32 board = nucleo_f429zi
You can override default ST Nucleo F429ZI settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f429zi.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST Nucleo F429ZI supports the next uploading protocols:
ST Nucleo F429ZI has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Frameworks ┌────────────────────┬─────────────────────────────┐ │Name                │ Description                 │ ├────────────────────┼─────────────────────────────┤ │framework_arduino   │ Arduino Wiring-based        │ │                    │ Framework allows writing    │ │                    │ cross-platform software to  │ │                    │ control devices attached to │ │                    │ a wide range of Arduino     │ │                    │ boards to create all kinds  │ │                    │ of creative coding,         │ │                    │ interactive objects, spaces │ │                    │ or physical experiences.    │ ├────────────────────┼─────────────────────────────┤ │framework_mbed      │ The mbed framework The mbed │ │                    │ SDK has been designed to    │ │                    │ provide enough hardware     │ │                    │ abstraction to be intuitive │ │                    │ and concise, yet powerful   │ │                    │ enough to build complex     │ │                    │ projects. It is built on    │ │                    │ the low-level ARM CMSIS     │ │                    │ APIs, allowing you to code  │ │                    │ down to the metal if        │ │                    │ needed. In addition to      │ │                    │ RTOS, USB and Networking    │ │                    │ libraries, a cookbook of    │ │                    │ hundreds of reusable        │ │                    │ peripheral and module       │ │                    │ libraries have been built   │ │                    │ on top of the SDK by the    │ │                    │ mbed Developer Community.   │ └────────────────────┴─────────────────────────────┘
ST Nucleo F439ZI Contents • ST Nucleo F439ZI
┌────────────────┬───────────────┐ │Microcontroller │ STM32F439ZIT6 │ ├────────────────┼───────────────┤ │Frequency       │ 180MHz        │ ├────────────────┼───────────────┤ │Flash           │ 2MB           │ ├────────────────┼───────────────┤ │RAM             │ 256KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f439zi ID for projectconf_env_board option in projectconf:
[env:nucleo_f439zi] platform = ststm32 board = nucleo_f439zi
You can override default ST Nucleo F439ZI settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f439zi.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f439zit6
Uploading ST Nucleo F439ZI supports the next uploading protocols:
ST Nucleo F439ZI has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F446RE Contents • ST Nucleo F446RE
┌────────────────┬───────────────┐ │Microcontroller │ STM32F446RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 180MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f446re ID for projectconf_env_board option in projectconf:
[env:nucleo_f446re] platform = ststm32 board = nucleo_f446re
You can override default ST Nucleo F446RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f446re.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST Nucleo F446RE supports the next uploading protocols:
ST Nucleo F446RE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F446ZE Contents • ST Nucleo F446ZE
┌────────────────┬───────────────┐ │Microcontroller │ STM32F446ZET6 │ ├────────────────┼───────────────┤ │Frequency       │ 180MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f446ze ID for projectconf_env_board option in projectconf:
[env:nucleo_f446ze] platform = ststm32 board = nucleo_f446ze
You can override default ST Nucleo F446ZE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f446ze.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f446zet6
Uploading ST Nucleo F446ZE supports the next uploading protocols:
ST Nucleo F446ZE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Frameworks ┌────────────────────┬─────────────────────────────┐ │Name                │ Description                 │ ├────────────────────┼─────────────────────────────┤ │framework_cmsis     │ The ARM Cortex              │ │                    │ Microcontroller Software    │ │                    │ Interface Standard (CMSIS)  │ │                    │ is a vendor-independent     │ │                    │ hardware abstraction layer  │ │                    │ for the Cortex-M processor  │ │                    │ series and specifies        │ │                    │ debugger interfaces. The    │ │                    │ CMSIS enables consistent    │ │                    │ and simple software         │ │                    │ interfaces to the processor │ │                    │ for interface peripherals,  │ │                    │ real-time operating         │ │                    │ systems, and middleware. It │ │                    │ simplifies software re-use, │ │                    │ reducing the learning curve │ │                    │ for new microcontroller     │ │                    │ developers and cutting the  │ │                    │ time-to-market for devices. │ ├────────────────────┼─────────────────────────────┤ │framework_mbed      │ The mbed framework The mbed │ │                    │ SDK has been designed to    │ │                    │ provide enough hardware     │ │                    │ abstraction to be intuitive │ │                    │ and concise, yet powerful   │ │                    │ enough to build complex     │ │                    │ projects. It is built on    │ │                    │ the low-level ARM CMSIS     │ │                    │ APIs, allowing you to code  │ │                    │ down to the metal if        │ │                    │ needed. In addition to      │ │                    │ RTOS, USB and Networking    │ │                    │ libraries, a cookbook of    │ │                    │ hundreds of reusable        │ │                    │ peripheral and module       │ │                    │ libraries have been built   │ │                    │ on top of the SDK by the    │ │                    │ mbed Developer Community.   │ └────────────────────┴─────────────────────────────┘
ST Nucleo F722ZE Contents • ST Nucleo F722ZE
┌────────────────┬───────────────┐ │Microcontroller │ STM32F722ZET6 │ ├────────────────┼───────────────┤ │Frequency       │ 216MHz        │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 256KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f722ze ID for projectconf_env_board option in projectconf:
[env:nucleo_f722ze] platform = ststm32 board = nucleo_f722ze
You can override default ST Nucleo F722ZE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f722ze.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f722zet6
Uploading ST Nucleo F722ZE supports the next uploading protocols:
ST Nucleo F722ZE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo F746ZG Contents • ST Nucleo F746ZG
┌────────────────┬───────────────┐ │Microcontroller │ STM32F746ZGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 216MHz        │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 320KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_f746zg ID for projectconf_env_board option in projectconf:
[env:nucleo_f746zg] platform = ststm32 board = nucleo_f746zg
You can override default ST Nucleo F746ZG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_f746zg.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32f746zgt6
Uploading ST Nucleo F746ZG supports the next uploading protocols:
ST Nucleo F746ZG has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
[env:nucleo_f767zi] platform = ststm32 board = nucleo_f767zi
; change microcontroller board_build.mcu = stm32f767zit6
Uploading ST Nucleo F767ZI supports the next uploading protocols:
ST Nucleo F767ZI has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo H743ZI Contents • ST Nucleo H743ZI
┌────────────────┬───────────────┐ │Microcontroller │ STM32H743ZIT6 │ ├────────────────┼───────────────┤ │Frequency       │ 400MHz        │ ├────────────────┼───────────────┤ │Flash           │ 2MB           │ ├────────────────┼───────────────┤ │RAM             │ 512KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_h743zi ID for projectconf_env_board option in projectconf:
[env:nucleo_h743zi] platform = ststm32 board = nucleo_h743zi
You can override default ST Nucleo H743ZI settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_h743zi.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32h743zit6
Uploading ST Nucleo H743ZI supports the next uploading protocols:
ST Nucleo H743ZI has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L011K4 Contents • ST Nucleo L011K4
┌────────────────┬───────────────┐ │Microcontroller │ STM32L011K4T6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 16KB          │ ├────────────────┼───────────────┤ │RAM             │ 2KB           │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l011k4 ID for projectconf_env_board option in projectconf:
[env:nucleo_l011k4] platform = ststm32 board = nucleo_l011k4
You can override default ST Nucleo L011K4 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l011k4.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l011k4t6
Uploading ST Nucleo L011K4 supports the next uploading protocols:
ST Nucleo L011K4 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L031K6 Contents • ST Nucleo L031K6
┌────────────────┬───────────────┐ │Microcontroller │ STM32L031K6T6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 32KB          │ ├────────────────┼───────────────┤ │RAM             │ 8KB           │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l031k6 ID for projectconf_env_board option in projectconf:
[env:nucleo_l031k6] platform = ststm32 board = nucleo_l031k6
You can override default ST Nucleo L031K6 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l031k6.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l031k6t6
Uploading ST Nucleo L031K6 supports the next uploading protocols:
ST Nucleo L031K6 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L053R8 Contents • ST Nucleo L053R8
┌────────────────┬───────────────┐ │Microcontroller │ STM32L053R8T6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 8KB           │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l053r8 ID for projectconf_env_board option in projectconf:
[env:nucleo_l053r8] platform = ststm32 board = nucleo_l053r8
You can override default ST Nucleo L053R8 settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l053r8.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l053r8t6
Uploading ST Nucleo L053R8 supports the next uploading protocols:
ST Nucleo L053R8 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L073RZ Contents • ST Nucleo L073RZ
┌────────────────┬─────────────┐ │Microcontroller │ STM32L073RZ │ ├────────────────┼─────────────┤ │Frequency       │ 32MHz       │ ├────────────────┼─────────────┤ │Flash           │ 192KB       │ ├────────────────┼─────────────┤ │RAM             │ 20KB        │ ├────────────────┼─────────────┤ │Vendor          │ ST          │ └────────────────┴─────────────┘
Configuration Please use nucleo_l073rz ID for projectconf_env_board option in projectconf:
[env:nucleo_l073rz] platform = ststm32 board = nucleo_l073rz
You can override default ST Nucleo L073RZ settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l073rz.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l073rz
Uploading ST Nucleo L073RZ supports the next uploading protocols:
ST Nucleo L073RZ has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L152RE Contents • ST Nucleo L152RE
┌────────────────┬───────────────┐ │Microcontroller │ STM32L152RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 32MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 80KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l152re ID for projectconf_env_board option in projectconf:
[env:nucleo_l152re] platform = ststm32 board = nucleo_l152re
You can override default ST Nucleo L152RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l152re.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l152ret6
Uploading ST Nucleo L152RE supports the next uploading protocols:
ST Nucleo L152RE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L412KB Contents • ST Nucleo L412KB
┌────────────────┬───────────────┐ │Microcontroller │ STM32L412KBU6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 40KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l412kb ID for projectconf_env_board option in projectconf:
[env:nucleo_l412kb] platform = ststm32 board = nucleo_l412kb
You can override default ST Nucleo L412KB settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l412kb.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l412kbu6
Uploading ST Nucleo L412KB supports the next uploading protocols:
ST Nucleo L412KB has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L432KC Contents • ST Nucleo L432KC
┌────────────────┬───────────────┐ │Microcontroller │ STM32L432KCU6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l432kc ID for projectconf_env_board option in projectconf:
[env:nucleo_l432kc] platform = ststm32 board = nucleo_l432kc
You can override default ST Nucleo L432KC settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l432kc.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l432kcu6
Uploading ST Nucleo L432KC supports the next uploading protocols:
ST Nucleo L432KC has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L433RC-P Contents • ST Nucleo L433RC-P
┌────────────────┬─────────────┐ │Microcontroller │ STM32L433RC │ ├────────────────┼─────────────┤ │Frequency       │ 80MHz       │ ├────────────────┼─────────────┤ │Flash           │ 256KB       │ ├────────────────┼─────────────┤ │RAM             │ 64KB        │ ├────────────────┼─────────────┤ │Vendor          │ ST          │ └────────────────┴─────────────┘
Configuration Please use nucleo_l433rc_p ID for projectconf_env_board option in projectconf:
[env:nucleo_l433rc_p] platform = ststm32 board = nucleo_l433rc_p
You can override default ST Nucleo L433RC-P settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l433rc_p.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l433rc
Uploading ST Nucleo L433RC-P supports the next uploading protocols:
ST Nucleo L433RC-P has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L452RE Contents • ST Nucleo L452RE
┌────────────────┬───────────────┐ │Microcontroller │ STM32L452RET6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 256KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l452re ID for projectconf_env_board option in projectconf:
[env:nucleo_l452re] platform = ststm32 board = nucleo_l452re
You can override default ST Nucleo L452RE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l452re.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = stm32l452ret6
Uploading ST Nucleo L452RE supports the next uploading protocols:
ST Nucleo L452RE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L476RG Contents • ST Nucleo L476RG
┌────────────────┬───────────────┐ │Microcontroller │ STM32L476RGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l476rg ID for projectconf_env_board option in projectconf:
[env:nucleo_l476rg] platform = ststm32 board = nucleo_l476rg
You can override default ST Nucleo L476RG settings per build environment using board_*** option, where *** is a JSON object path from board manifest nucleo_l476rg.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ST Nucleo L476RG supports the next uploading protocols:
ST Nucleo L476RG has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ST Nucleo L486RG Contents • ST Nucleo L486RG
┌────────────────┬───────────────┐ │Microcontroller │ STM32L486RGT6 │ ├────────────────┼───────────────┤ │Frequency       │ 80MHz         │ ├────────────────┼───────────────┤ │Flash           │ 1MB           │ ├────────────────┼───────────────┤ │RAM             │ 128KB         │ ├────────────────┼───────────────┤ │Vendor          │ ST            │ └────────────────┴───────────────┘
Configuration Please use nucleo_l486rg ID for projectconf_env_board option in projectconf:
[env:nucleo_l486rg] platform = ststm32 board = nucleo_l486rg