STM32F722RET6
Product Specifications
STM32F722RET6 — ARM Cortex-M Microcontroller by STMicroelectronics
The STM32F722RET6 is an STMicroelectronics ARM Cortex-M MCU in LQFP-64_10x10x05P for Embedded control and general-purpose MCU applications. Supplied by SUPERB Automation.
Part Number Decoded — Field by Field
| Field | Value | Meaning |
|---|---|---|
| STM32F722RET6 | Full Part Number | STMicroelectronics ARM Cortex-M Microcontroller |
| STM32 | Product Family | STMicroelectronics 32-bit ARM-based MCU |
| F7 | Series | ARM Cortex-M based MCU — F7 series |
Quick Specifications
| Parameter | Value |
|---|---|
| Manufacturer | STMicroelectronics |
| Part Number | STM32F722RET6 |
| Core | ARM Cortex-M |
| Package | LQFP-64_10x10x05P |
| Temperature Range | −40°C to +85°C |
| Supply Voltage | 1.8V–3.6V |
Product Overview
The STM32F722RET6 is an STMicroelectronics ARM Cortex-M microcontroller in LQFP-64_10x10x05P package. Part of ST's extensive STM32 portfolio, it delivers a high-performance processing platform with integrated Flash, SRAM, and a rich set of communication peripherals for Embedded control and general-purpose MCU applications. Supplied by SUPERB Automation with full traceability and competitive lead times.
Key Features & Benefits
ARM Cortex-M Core — Efficient Processing for Embedded Control
The ARM Cortex-M core provides deterministic real-time performance with hardware multiply/divide and optional FPU, executing control loops, communication stacks, and sensor fusion algorithms efficiently in resource-constrained embedded environments.
Rich Peripheral Set — GPIO, Timers, ADC, Communication Interfaces
Features a comprehensive set of on-chip peripherals including multi-channel DMA, 12/16-bit ADCs, advanced PWM timers for motor control, and multiple USART/SPI/I²C interfaces for sensor and communication module connectivity.
ST Ecosystem — CubeMX, HAL, LL, Middleware
Fully supported by ST's STM32Cube ecosystem including CubeMX graphical configuration, HAL/LL driver libraries, FreeRTOS integration, and extensive middleware stacks (USB, TCP/IP, FATFS, graphics) — accelerating firmware development and reducing time-to-market.
Target Applications
Embedded Control & IoT Systems
Functions as the main processing unit in embedded control systems, IoT endpoints, sensor hubs, motor controllers, and human-machine interfaces — leveraging the Cortex-M architecture for efficient, low-power operation.
Industrial Automation & Motor Control
Powers industrial motor drives, PLCs, sensor transmitters, and factory automation equipment — taking advantage of advanced PWM timers, high-speed ADCs, and CAN/RS-485 communication for distributed control architectures.
Consumer & Portable Electronics
Integrates into consumer devices, wearables, smart home products, and portable instruments — benefiting from the STM32 family's low-power modes, small packages, and extensive third-party firmware ecosystem.
Frequently Asked Questions
Is the STM32F722RET6 supported by STM32CubeIDE?
Yes, the STM32F722RET6 is fully supported in STM32CubeIDE with graphical pinout configuration, clock tree setup, and automatic peripheral initialization code generation — enabling rapid prototyping and production firmware development.
What firmware/RTOS options are available?
The STM32 family is supported by FreeRTOS, Zephyr, NuttX, ChibiOS, and bare-metal HAL programming. For drone applications, Betaflight, iNav, ArduPilot, and PX4 all have STM32 HAL targets.
What is the minimum order quantity (MOQ)?
Contact SUPERB Automation for a tailored quote. We support quantities from prototype tray to full production volumes.
Request a Quote
SUPERB Automation supplies genuine STMicroelectronics STM32F722RET6 MCUs with full traceability and batch-level QA documentation. Whether you need a single tray for prototype builds or pallet-level volumes for production, we source through verified channels with competitive lead times. Contact us with your target quantity and delivery date — we'll respond with a detailed quotation within 24 hours.
STM32F722RET6: 512 Kbytes of flash and an M7 at 216 MHz in 64 pins
The R is the 64 pin LQFP, E is the 512 Kbyte flash density and 6 is the range of minus 40 to plus 85 degrees C. The 722 in the middle is the part of the string that carries a real decision: the datasheet defines 722 as the device without the high speed USB PHY, and 723 as the same core with that PHY inside. Both are Cortex-M7 at 216 MHz with 462 DMIPS, so the choice is about the physical layer and the pin budget, not about computing power.
The memory arrangement is 512 Kbytes of flash, 256 Kbytes of SRAM including 64 Kbytes of data tightly coupled memory, 16 Kbytes of instruction TCM, 4 Kbytes of backup SRAM and 528 bytes of one-time programmable memory. Add an 8 Kbyte data cache and an 8 Kbyte instruction cache on top of the core, and the part behaves like a small applications processor for anything that is not drawing a frame buffer. Figures come from DS11853 Rev 10.
The body in figures
| Core | Cortex-M7 with FPU at up to 216 MHz, 462 DMIPS |
| Cache | 8 Kbytes of data cache and 8 Kbytes of instruction cache |
| Flash | 512 Kbytes on the E density, with PCROP and read and write protection |
| OTP | 528 bytes |
| SRAM | 256 Kbytes including 64 Kbytes of data TCM, plus 16 Kbytes of instruction TCM and 4 Kbytes backup |
| ADC | Three 12-bit converters at 2.4 Msamples per second, 7.2 Msamples per second in triple interleaved mode, up to 24 channels |
| DAC | Two 12-bit channels |
| Timers | Up to 18, including two 32-bit and one low power 16-bit usable in stop mode |
| Communication | 21 interfaces, including USB OTG full speed and high speed, CAN, USART, SPI and I2C |
| USB | OTG HS and FS on the core, high speed PHY only on the 723 |
| Package | LQFP64, 10 mm by 10 mm |
| Temperature | 6 for minus 40 to plus 85 degrees C, 7 for minus 40 to plus 105 degrees C |
The 722 and the 723 are not the same board
A 722 can still run a high speed link, but the PHY has to be outside the package, either as a discrete transceiver on the board or through the on-chip full speed PHY at 12 Mbit per second. A build that assumed the 723 and bought 722 on a shortage list will post, enumerate and then fail to reach 480 Mbit per second, and the failure appears as a link that trains at full speed rather than as a part that does not work. That is the single most common mix-up between the two subfamilies.
The second difference is the ball and pin budget. The high speed PHY needs its own supply pins and its own crystal arrangement, so the 723 in the same body uses lines that the 722 leaves free. A board laid out for one is not automatically a board for the other even when the pin count matches.
Where the application only needs a device port for a service tool or a firmware update, the full speed OTG on the 722 is enough and the external components disappear. Where the product streams video, audio or a fast data log over the cable, the 723 or an external PHY is the honest answer. Our MCU cross reference page records which subfamilies share a body and which only share a pin count, because the two are not the same thing.
Interleaved conversion and the TCM split
Three converters at 2.4 Msamples per second become 7.2 Msamples per second when they are interleaved on one channel, which is how a motor drive samples phase currents at the centre of a PWM period without waiting for three sequential conversions. The 24 channels on this body are enough for two inverters, a resolver pair and a set of diagnostic dividers, and the converters run from 1.8 V to 3.6 V so a 3.3 V analog front end needs no separate rail.
Accuracy over temperature is a separate row from the sample rate. At 12 bits the integral non linearity and the offset drift decide whether a 3.3 V rail measured through a divider is good to 2 mV or to 8 mV, and the document gives those figures at the rated supply. On a current sense channel the practical answer is a two point calibration in the factory with the drift coefficient applied in firmware, which is cheaper than an external reference and a buffer.
The 64 Kbytes of data TCM is where the conversion results and the control loop variables live. Access to that memory is deterministic, so the loop execution time does not depend on whether a network stack is running from flash at the same time. On a 20 kHz loop that determinism is worth more than the extra megahertz, and it is the reason a 216 MHz part with TCM can outperform a faster part without it.
The 4 Kbytes of backup SRAM on VBAT is small, and it is exactly the size of a trip log or a counter that has to survive a supply loss. Together with the low power 16-bit timer that keeps running in stop mode, a product can count events with the core asleep and wake only to move the total into flash, which is the shape of every battery instrument built on this core.
The step from this part to an H7 is a step in core, cache and memory bandwidth, not in pin count, so a product that has outgrown 216 MHz can keep its enclosure and change its board. The component lead time solutions page covers how we stage that kind of transition without stopping the current build.
The ADC and DAC cross reference page lists the converter counts and speeds across the families we quote, and it is the page to read when the channel count on this body is one or two short.
Where 512 Kbytes is more than the application will ever use, the 256 Kbyte member shares the body and the pin map, and the difference in unit price at volume is not trivial. The honest test is to build the image, look at the map file and decide, rather than to buy the larger array against a feature list that may never be written.
What the 512 Kbyte density changes
At 256 Kbytes the flash holds an application, a bootloader and one update image with little room to spare. At 512 Kbytes there is space for a second image and for a parameter region that does not have to be squeezed into the last sectors, which is what makes a field update plan practical without an external memory device. The one-time programmable pages are separate and are the right place for a serial number or a calibration constant that must survive every update.
With 21 communication interfaces, the pin allocation becomes the real constraint at 64 pins. Two CAN channels, a USB port, three USARTs and an SPI for external flash will not all fit with every alternate function in its first position, so the pin map is usually reviewed before the board drawing is released. Our one stop BOM sourcing page covers how we hold a second source against each line of that map so that a single shortage does not stop the build.
Questions before the purchase order
Is the 105 degree grade available on this density? The document lists a 7 suffix for minus 40 to plus 105 degrees C, and it has to be on the order code because the marking on the body carries the full string. Does the part need an external crystal for USB? Yes, the full speed PHY requires the 8 MHz reference, and the high speed path on the 723 requires its own. Our date code management page describes how we track the lot and the date on each reel, which is what an audit asks for when a USB enumeration issue appears on one batch and not on another.