STM32L100RBT6
Product Specifications
STM32L100RBT6
ST — MCU & Embedded Processors
Product Overview
The STM32L100RBT6 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
STM32L100RBT6: 128 Kbyte, LQFP64 body
STM32L100RBT6 is a member of the STM32L100C6 and STM32L100R8/RB access line described by DocID024295 Rev 6. The order code fixes 128 Kbytes of Flash, 10 Kbytes of SRAM, the LQFP64 body at 10 x 10 mm with 64 pins, 51 general purpose I/O and 20 analog channels, and the core runs at up to 32 MHz from a 1.8 to 3.6 V supply.
Order code and memory
| Order code | STM32L100RBT6 |
| Program Flash | 128 Kbytes |
| SRAM | 10 Kbytes |
| Data EEPROM | 2 Kbytes with ECC |
| Package | LQFP64, 10 x 10 mm, 64 pins |
| Maximum general purpose I/O | 51 |
| Analog input channels | 20 channels on the 12 bit converter |
| Digital to analog converter | 2 channels of 12 bits |
| Segment LCD driver | 4x32 or 8x28 segments |
| Supply voltage | 1.8 to 3.6 V |
| Maximum CPU clock | 32 MHz |
| Temperature grade | suffix 6, minus 40 to plus 85 C ambient |
| Datasheet | DocID024295 Rev 6 |
Peripheral and electrical parameters
| Core | ARM Cortex-M3 at up to 32 MHz, 1.25 DMIPS per MHz, memory protection unit |
| Clock sources | 1 to 24 MHz crystal oscillator, 32 kHz oscillator for the RTC with calibration, 16 MHz internal RC, internal 37 kHz low power RC, internal multispeed 65 kHz to 4.2 MHz RC and a PLL for the 48 MHz USB clock |
| Low power modes | 214 microamps per MHz in Run mode, 9 microamps in Low power run, 1.2 microamps in Stop with the RTC, 0.9 microamps in Standby with the RTC and 10 nanoamps of I/O leakage |
| Timers | ten timers: six 16 bit general purpose timers with up to four compare channels, two 16 bit basic timers and the independent and window watchdogs |
| Serial interfaces | two SPI blocks at 16 Mbit/s, two I2C blocks with SMBus and PMBus, three USARTs with ISO 7816 and IrDA support and one USB 2.0 device port |
| Analog | one 12 bit ADC at 1 Msps, two 12 bit DAC channels and two ultra low power comparators |
| Memory interface | not present on this body |
| Flash and EEPROM endurance | flash rated 10 kcycles with retention stated after 100 kcycles at 85 C in the same table |
| Thermal resistance junction to ambient | 45 C/W on LQFP64 |
| Input tolerance | 42 of the 51 I/O on the 64 pin body are 5 V tolerant, all mappable on 16 external interrupt vectors |
| Debug port | serial wire debug on two pins and JTAG on five, with the trace port sharing low order port bits |
| Backup domain | the VBAT domain keeps the RTC and the backup registers alive with the main rail off |
| Status | full production per the datasheet cover |
Points to check before this part goes on a BOM
The order code is R for 64 pins, B for 128 Kbytes of Flash, T for the LQFP body and 6 for the industrial range. Flash doubles from the R8 code while the SRAM moves from 8 to 10 Kbytes and the EEPROM stays at 2 Kbytes, which is the one place in the line where flash and RAM do not scale together.
10 Kbytes of SRAM with 128 Kbytes of flash is an unusual ratio, and it is the number to check before a firmware port. A display map, a calibration table and one serial buffer fit, and a second protocol stack or a record buffer does not, so the image has to be written for the RAM rather than for the flash.
The 2 Kbytes of EEPROM are enough for a calibration record and a device identity, and not enough to be the only log. At four bytes per record there are 512 records per full cycle, so anything that writes every reading needs either a wear levelling scheme or an external memory part.
The display driver is the same 4x32 or 8x28 block as the smaller code, and it shares port C with the analog channels. A product that uses a full glass and also samples eight sensors has to give up either segment lines or channels, and the conflict is in the pin table rather than in the silicon.
The LQFP64 is rated 45 C/W junction to ambient, so 444 mW at an 85 C ambient against a 105 C junction. The part is identical to the 64 Kbyte code thermally and in current, so a thermal review done for the smaller code carries over without a new measurement.
1.2 microamps in Stop with the RTC and 0.9 microamps in Standby, plus 10 nanoamps of I/O leakage, are the same figures as the rest of the access line. 9 microamps in Low power run is where a device that wakes every second and computes briefly actually sits.
The USB port on this part takes its 48 MHz clock from the PLL and there is no crystal-less option, so a board that enumerates needs a crystal and two load capacitors. On a thermostat that only uses the UART for a service port those parts can be left off and the internal RC runs the core.
The pin compatible alternative is R8T6 at 64 Kbytes, and nothing above this density exists in the access line document. A product that needs both 128 Kbytes and 10 Kbytes of RAM has reached the top of the line, and the next step is the STM32L151 document with 128 Kbytes and 16 Kbytes.
Where this order code fits
It is the 128 Kbyte access line part, used where the glass driver and the low cost matter but the firmware needs more program space than 64 Kbytes. Boards weighing it against a neighbouring density 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
Why does the SRAM only go to 10 Kbytes at 128 Kbytes of flash? That is how the access line is defined: the flash column scales with the density and the RAM column does not. A firmware image that needs both belongs in the STM32L151 line, where 128 Kbytes comes with 16 Kbytes of SRAM.
Is the display driver the same as on the smaller code? Yes, 4x32 or 8x28 segments on this body. What changes with the density is the flash and a little SRAM, not the glass driver or the pin allocation.
How does it compare with STM32L151RBT6? Same pin count and the same 128 Kbytes of flash. The 151 part adds 6 Kbytes of SRAM, 2 Kbytes of EEPROM, multispeed RC, capacitive sensing and a larger serial set, at a higher part cost.
Can it be programmed over the UART? The line carries a pre-programmed bootloader that works over USART, I2C and SPI, so a service port does not need a separate programming header. Production programming over serial wire debug is the faster route at volume.
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 Pin to Pin Cross Reference page sets out the checks that keep a substitute from failing on the bench.