STM32F100R4T6
Product Specifications
STM32F100R4T6
ST — MCU & Embedded Processors
Product Overview
The STM32F100R4T6 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
STM32F100R4T6: 16 Kbyte, LQFP64 body
STM32F100R4T6 is a member of the STM32F100 value line low and medium density described by DocID16455 Rev 9. The order code fixes 16 Kbytes of Flash, 4 Kbytes of SRAM, the LQFP64 body at 10 x 10 mm with 64 pins, 51 general purpose I/O and 16 channels of the 12 bit converter, and the core runs at up to 24 MHz from a 2.0 to 3.6 V supply.
Order code and memory
| Order code | STM32F100R4T6 |
| Program Flash | 16 Kbytes |
| SRAM | 4 Kbytes |
| Package | LQFP64, 10 x 10 mm, 64 pins |
| Maximum general purpose I/O | 51 |
| Analog input channels | 16 of the 12 bit converter |
| Digital to analog converter | 2 channels of 12 bits |
| External memory controller | not present on this body |
| Supply voltage | 2.0 to 3.6 V |
| Maximum CPU clock | 24 MHz |
| Temperature grade | suffix 6, minus 40 to plus 85 C ambient, 105 C junction |
| Datasheet | DocID16455 Rev 9 |
Peripheral and electrical parameters
| Core | ARM Cortex-M3 at up to 24 MHz, 1.25 DMIPS per MHz, single cycle multiply and divide |
| Clock sources | 8 MHz factory trimmed internal RC, PLL up to the 24 MHz core clock, external crystal range 4 to 24 MHz |
| Timers | one advanced-control 16 bit timer with four channels and complementary outputs with dead time, up to six general-purpose 16 bit timers with four compare channels each, and two basic timers that trigger the converter |
| Serial interfaces | up to two SPI blocks, two I2C blocks and three USARTs, plus one HDMI CEC channel |
| DMA | 7 channel DMA controller |
| ADC | 12 bit successive approximation, 1 microsecond conversion, 10 channels on 48 pins and 16 channels on 64 and 100 pins |
| DAC | 2 channels of 12 bits with output buffers |
| Programmable voltage detector | eight falling thresholds from 2.00 V to 2.88 V nominal, each with a rising edge about 100 mV higher |
| Debug port | serial wire debug on two pins and JTAG on five, with the trace port sharing low order port bits |
| Backup domain | VBAT domain keeps the RTC, the backup registers and the tamper input alive with the main rail off |
| Flash endurance and retention | 10 kcycles at minus 40 to plus 85 C, 1 kcycle at 105 C, 30 years of retention at 85 C after one kcycle and 10 years at 105 C |
| Thermal resistance junction to ambient | 45 C/W on this package |
| Input tolerance | almost all inputs 5 V tolerant |
| USB | not present, USB full speed is the STM32F102 line |
| Status | production data per the datasheet cover |
Points to check before this part goes on a BOM
The 64 pin body brings out 16 converter channels and 51 general purpose I/O on the same 16 Kbyte of Flash that the 48 pin code carries with 10 channels and 37 I/O. That is the whole reason to pick this order code: the analog front end grew and the firmware did not. Boards that need a second sensor group, a current sense on three phases plus a bus voltage plus two thermistors, land on this part rather than on a 48 pin body with an external multiplexer.
At 16 Kbytes the interface set is the low density one: one SPI block, one I2C block and two of the three USARTs, with the second SPI, the second I2C and the third USART arriving only with the 64 and 128 Kbyte codes in the same package. This is the trap on the line, because a 64 pin part looks like it should have everything. The memory column of Table 2 of DocID16455 Rev 9 decides the interfaces, and the package decides only how many pins are available to them.
The 4 Kbytes of SRAM has to hold the converter buffers for a 16 channel scan. A single conversion buffer of 16 results is 32 bytes at 12 bits, which is small, but a double buffer for continuous scanning plus the DMA descriptors plus the stack and the calibration table is what fills the 4 Kbytes. Firmware that scans all 16 channels continuously and also runs two serial ports is the case where the SRAM, not the Flash, is the reason to move up a memory size.
At 45 C/W on the LQFP64 body the junction rises 20 C above an 85 C ambient at about 440 mW, which is more thermal room than the 48 pin code offers for the same silicon. That difference is usually spent on the I/O rather than on the core: a 64 pin board drives more outputs, and each output that sinks current adds to the same budget. A part with 51 I/O driving a display and a keypad matrix gets closer to the limit than its clock rate suggests.
The two DAC channels are buffered, so they drive a load without an external amplifier, and they share pins with converter inputs. On a body with 16 channels that trade costs two of them, which still leaves 14, and the alternative is an external DAC on the SPI block with its own reference. For a setpoint or a bias voltage the internal pair is normally the cheaper answer and the accuracy is set by the analog supply rather than by the converter.
Flash endurance and retention are the same across the line: 10 kcycles at minus 40 to plus 85 C, 1 kcycle at 105 C, 30 years of retention at 85 C after one kcycle. On a 16 Kbyte part the option of keeping counters in the backup registers matters more, because losing a page to a failed write costs a larger share of the total image. The backup domain runs from VBAT and holds the RTC, the registers and the tamper input with the main rail off.
The internal RC oscillator is within 1.1 percent at 25 C and 2.2 percent over the full range, which is fine for the converter and marginal for two USARTs. A board that expects both ports to work at 115200 baud over a metre of cable should fit a crystal in the 4 to 24 MHz range and run the PLL from it, and should decide that before the two oscillator pins are assigned to something else on a 51 I/O body.
Where this order code fits
It is the 16 Kbyte code in the 64 pin body, which is the arrangement used when the analog count matters more than the memory size and the board needs 16 converter channels with a small firmware image. Boards comparing it against a neighbouring memory size or pin count start from our MCU Cross Reference page, and boards replacing a line that has gone end of life start from the Pin to Pin Cross Reference page. Both list the figures that have to match before a substitute goes on a BOM.
Questions buyers ask
Why choose the 64 pin 16 Kbyte code over the 48 pin one? For the analog and digital pin count. It brings 16 converter channels instead of 10 and 51 general purpose I/O instead of 37, on the same 16 Kbytes of Flash and 4 Kbytes of SRAM, with the same interface set and the same clock ceiling.
Does this part have the external memory controller? No. The flexible static memory controller is not present anywhere in the STM32F100 low and medium density line, including the 64 pin and 100 pin bodies. It appears only on the high density parts, where the pin count can also carry an address and data bus.
What is the difference between STM32F100R4T6 and STM32F100R4T6B? The trailing letter is an internal code, so the memory size, the package and the pin count are the same. The two strings are separate orderable parts, which matters when a board file or a qualification report has to name exactly what was built.
SUPERB holds and sources ST microcontroller lines including this order code for production and repair demand, quoted against the exact ordering string with date codes and packing stated. When a line is changing, the Component Lead Time Solutions page sets out the checks that keep a substitute from failing on the bench.