STM32F100RBT6
Product Specifications
STM32F100RBT6
ST — MCU & Embedded Processors
Product Overview
The STM32F100RBT6 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
STM32F100RBT6: 128 Kbyte, LQFP64 body
STM32F100RBT6 is a member of the STM32F100 value line low and medium density described by DocID16455 Rev 9. The order code fixes 128 Kbytes of Flash, 8 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 | STM32F100RBT6 |
| Program Flash | 128 Kbytes |
| SRAM | 8 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 choice between this code and the 100 pin 128 Kbyte part is a mechanical and pin count decision, not a feature decision: both carry the same 128 Kbytes of Flash, 8 Kbytes of SRAM, 16 converter channels and medium density interface set, and the difference is 51 general purpose I/O in a 10 x 10 mm body against 80 in a 14 x 14 mm one. A board that has already used its space budget usually finds 51 I/O is enough once the serial interfaces are counted.
The 8 Kbytes of SRAM is the tight figure at this memory size. A 128 Kbyte image suggests a substantial application, and a substantial application with three USARTs, a converter scan and a protocol stack will use most of the 8 Kbytes before the heap. Firmware that has to hold a full firmware image in RAM for a self update does not fit at all, which is why field update on this part is usually a page by page write from an external memory or from the host.
Two SPI blocks and two I2C blocks mean an external serial Flash and an EEPROM can both be on the board without sharing a bus, and the three USARTs cover a host link, a service port and a field bus. The HDMI CEC channel is separate from all of them. On a 64 pin body the pin table decides which of these can be brought out together, because the SPI, I2C and USART signals are spread across port A, B and C and several of them collide.
The two basic timers, TIM6 and TIM7, are worth keeping for the converter and the DAC rather than spending a general purpose timer on them. A general purpose timer then runs the control loop or the encoder interface with its full four compare channels intact. On a 128 Kbyte part with several active peripherals, the timer budget runs out before the memory does, and this is where that shows up.
At 45 C/W the LQFP64 body allows about 440 mW from 85 C ambient to 105 C junction. A 128 Kbyte part in a 10 x 10 mm package on a dense board is the case where the copper area under the package is the deciding factor: the thermal resistance in the datasheet is measured on a defined test board, and a real board with less copper runs hotter for the same dissipation. Adding vias under the pad is cheaper than derating the ambient.
The Flash endurance figure of 10 kcycles at minus 40 to plus 85 C is measured over the whole temperature range, and the retention figure of 30 years at 85 C applies after one kcycle. A parameter store that writes a few hundred times over the life of the product is far inside both. A data logger is not, and the two I2C blocks give it an EEPROM or a FRAM as a better home for the data than the program Flash.
Because the memory is at the top of this range, a buyer comparing it against the STM32F101 high density line should look at the interface count rather than the core: the F101 high density part brings five USARTs, the external memory controller on the 100 pin body and a 36 MHz core, which is a different board rather than a different memory size.
Where this order code fits
It is the 128 Kbyte code in the 10 x 10 mm body, used where the firmware image is large and the mechanical space does not allow a 14 x 14 mm package. 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 Component Lead Time Solutions page. Both list the figures that have to match before a substitute goes on a BOM.
Questions buyers ask
How many I/O are available here against the 100 pin 128 Kbyte code? 51 against 80. Everything else about the two codes is the same, including the memory, the converter channel count, the interface set and the clock ceiling, so the decision is how many pins the board needs and how much space it has.
Can this part drive an external memory bus? No. The value line low and medium density parts have no flexible static memory controller at any pin count. External memory is an SPI serial Flash or an I2C EEPROM on the blocks that are available, or a move to the high density part.
What happens to the two DAC channels if both converters are in use? They share pins with converter inputs, so enabling both DAC outputs costs two of the 16 analog channels. A board that needs all 16 converter inputs and both DAC outputs at the same time is outside the pin map of this package and needs an external converter.
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 How to Verify a Drop in Replacement page sets out the checks that keep a substitute from failing on the bench.