STM32F103RDT6
Product Specifications
STM32F103RDT6
ST — MCU & Embedded Processors
Product Overview
The STM32F103RDT6 from ST is a microcontroller / embedded processor engineered for real-time control, signal processing, and connectivity. STMicroelectronics is a European semiconductor leader with a strong portfolio in MCUs, power management, sensors, and analog ICs.
Superb Automation partners with leading brands including Qorvo, TI, ADI, XILINX, NVIDIA, Intel, ST, MACOM, Renesas, and Coilcraft to provide complete BOM and supply-chain solutions.
Key Features
- ARM Cortex / RISC-V / proprietary core with high-performance real-time processing
- Integrated flash memory and SRAM for efficient code execution
- Rich peripheral set: UART, SPI, I2C, ADC, timers, PWM
- Low-power modes for battery-operated and energy-sensitive applications
- Hardware security features: secure boot, crypto accelerator, TRNG
- Extensive development ecosystem with IDE, HAL, and RTOS support
Key Specifications
| Core | — |
| Max Frequency | MHz |
| Flash | KB |
| SRAM | KB |
| GPIO | — |
| ADC | bits |
| Interfaces | — |
| Supply Voltage | V |
| Operating Temp | °C |
| Package | — |
Applications
Request Quote — In Stock, 100% New & Original, Full Warranty
STM32F103RDT6: 384 Kbytes, FSMC and Three Converters in 64 Pins
STM32F103RDT6 is a high density member of the STM32F103 line: 384 Kbytes of flash, 64 Kbytes of SRAM, an external memory controller, three 12 bit converters, two 12 bit DAC channels and eleven timers, all inside the 64 pin LQFP that the medium density parts also use. The core is still Cortex-M3 at 72 MHz and the supply is still 2.0 to 3.6 V, so the step up in this family is memory and peripherals, not clock. The D in the code is the 384 Kbyte density; C is 256 Kbytes and E is 512 Kbytes, both in the same body.
What high density adds
The high density line brings the flexible static memory controller, three SPI ports with two I2S channels, two I2C ports, five USARTs, an SDIO interface, a USB 2.0 full speed port and a CAN controller, which the datasheet counts as thirteen communication interfaces. Timers grow to four general purpose, two advanced control and two basic units. On the analog side there are three converters that can be interleaved, a two channel DAC, and a temperature sensor. The practical consequence for a 64 pin board is that the part can drive an external SRAM, run audio through I2S and still keep a CAN bus and a USB port, which the medium density devices cannot do at the same time.
Values at a glance
| Parameter | Value | Note |
|---|---|---|
| Core and clock | Cortex-M3, 72 MHz | Two APB buses, 1.25 DMIPS/MHz |
| Flash, SRAM | 384 Kbytes, 64 Kbytes | 256 Kbyte C and 512 Kbyte E codes share the body |
| Package | LQFP64, 10 by 10 mm | WLCSP64 is the alternate body for the same density |
| I/O | 51 pins | Same pin count as the medium density 64 pin part |
| ADC, DAC | 3 converters, 12 bit, 16 channels; 2 DAC channels | ADC at 1 microsecond conversion, range 0 to 3.6 V |
| External memory | FSMC, Bank1 and Bank2 | On 64 pin bodies only NAND style bank use is realistic |
| Communication | 3 SPI, 2 I2S, 2 I2C, 5 USART, SDIO, USB, CAN | Thirteen interfaces counted by the vendor |
| Temperature | Minus 40 to plus 85 C | Junction limit 125 C, extended ambient code 7 to 105 C |
The FSMC on 64 pins is a narrow tool
The external memory controller needs address, data and control pins, and a 16 bit multiplexed bus plus chip selects is around 25 pins. On a 64 pin body that leaves very little for the rest of the board, so the memory interface that a 100 pin or 144 pin high density part uses for a parallel LCD or a large SRAM is mostly out of reach here. What the controller does buy on this body is a small NAND or a latch interface for a few extra registers, which is useful but not the reason most boards choose this density.
Why the RD code persists in bills of material
Projects that started when 384 Kbytes was the largest sensible flash size still carry the RD code, and the firmware binary that fills 300 Kbytes will not fit into a 256 Kbyte C part. Reaching for the 512 Kbyte E code is possible in the same body and is often better supplied, but it changes the approved part list. Where the exact code is not available, the options are a microcontroller cross reference against the C and E densities, a strategic sourcing plan that buys the build quantity early, or an incoming inspection plan for parts that come from the open market rather than the franchise channel.
Common questions
Does the DAC need an external reference? The DAC output range follows VDDA unless VREF+ is available, and on the 64 pin body VREF+ shares a pin with the analog input group. A precise output needs a reference on that pin rather than the noisy 3.3 V rail.
Can the three converters sample at the same instant? Two of them can work in dual regular simultaneous mode with a common trigger, and the third runs independently. Triple simultaneous sampling is not available on this family.
Is the SDIO interface usable at 3.0 V? The SDIO pins are on the 3.3 V I/O ring and support the high capacity card interface, but the card supply itself has to be switched separately for full compliance with the SD specification.