STM32
STM32 is a portfolio, not one interchangeable chip. ST groups devices by performance, power and connectivity needs. Examples include Cortex-M7-based STM32F7 and H7 and Cortex-M55-based STM32N6, alongside low-power and wireless families. A peripheral listed for one family is not automatically present on another.
A Cortex-M processor runs firmware and interacts with the chip's memory and peripherals. STM32Cube tools help configure and develop that firmware, but different cores and families have different instruction capabilities, clock trees, memory maps and peripherals. Porting requires checking the target hardware and software rather than merely changing pin numbers.
In plain terms
A modular Cortex-M core wrapped in ST's library of peripherals — like an a-la-carte MCU menu where you pick the CPU horsepower and the radio/USB/Ethernet glue you need.
Why designers use it
- A wide selection of performance, power and peripheral combinations.
- Vendor development tools and supporting software.
- Product families for wired connectivity, wireless connectivity and control applications, with exact capabilities determined by the selected part.
Best for
- Drones
- Lab gear
- USB/Ethernet/CAN designs
Key specifications
- STM32F7 example: Cortex-M7, up to 216 MHz
- STM32H7 example: Cortex-M7 options up to 600 MHz (Not the specification of every H7 device.)
- STM32N6 example: Cortex-M55, 800 MHz
- Wireless options: Dedicated families such as STM32WB, WBA and WB0 (Check the exact device and supported protocol stack.)
- Memory, voltage and package: Read the complete ordering-code datasheet
When not to use it
- When the selected part does not meet the actual power, cost or peripheral requirements.
- When a migration assumes pin, binary or peripheral compatibility that the target datasheet does not establish.
Common mistakes
- Copying a clock speed or peripheral specification from a different STM32 family.
- Assuming every STM32 has a radio or the same bootloader interfaces.
- Treating a software abstraction layer as a guarantee that firmware ports unchanged.
- Ignoring the exact device's supply, analog-reference, reset, boot and debug requirements.
Where you will find it
- A controller can select an STM32 with suitable timers and communication peripherals, then use the vendor tools to configure its board-specific clocks and pins.
- A wireless design must select an appropriate wireless STM32 or add a separate radio. A non-wireless MCU family name alone does not provide Bluetooth.
A short history
The STM32 portfolio has expanded into general-purpose, high-performance, ultra-low-power and wireless groups. ST's portfolio comparison and STM32Cube development tools help narrow the choice, but the individual device datasheet remains the authority for the actual hardware.
Good to know
- Two STM32 devices can use different Cortex-M cores and have very different peripherals.
- A family-level headline is a starting point for selection, not a substitute for the complete part number.