Contact Us

STM32F100R4T6B

Brand: ST
ST STM32F100R4T6B is a mcu & embedded component designed for general electronics and related applications. In stock at Superb Automation — request a quote for competitive pricing and fast delivery.
quote now

Product Specifications

STM32F100R4T6B — MCU & Embedded Processors | Superb Automation

STM32F100R4T6B

ST — MCU & Embedded Processors

Product Overview

The STM32F100R4T6B 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 FrequencyMHz
FlashKB
SRAMKB
GPIO—
ADCbits
Interfaces—
Supply VoltageV
Operating Temp°C
Package—

Applications

Industrial Motor Control IoT Edge Nodes Consumer Electronics Automotive Body Control Smart Home & Appliances Medical Portable Devices

Request Quote — In Stock, 100% New & Original, Full Warranty

STM32F100R4T6B: 16 Kbyte, LQFP64 body

STM32F100R4T6B 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 codeSTM32F100R4T6B
Program Flash16 Kbytes
SRAM4 Kbytes
PackageLQFP64, 10 x 10 mm, 64 pins
Maximum general purpose I/O51
Analog input channels16 of the 12 bit converter
Digital to analog converter2 channels of 12 bits
External memory controllernot present on this body
Supply voltage2.0 to 3.6 V
Maximum CPU clock24 MHz
Temperature gradesuffix 6, minus 40 to plus 85 C ambient, 105 C junction
DatasheetDocID16455 Rev 9

Peripheral and electrical parameters

CoreARM Cortex-M3 at up to 24 MHz, 1.25 DMIPS per MHz, single cycle multiply and divide
Clock sources8 MHz factory trimmed internal RC, PLL up to the 24 MHz core clock, external crystal range 4 to 24 MHz
Timersone 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 interfacesup to two SPI blocks, two I2C blocks and three USARTs, plus one HDMI CEC channel
DMA7 channel DMA controller
ADC12 bit successive approximation, 1 microsecond conversion, 10 channels on 48 pins and 16 channels on 64 and 100 pins
DAC2 channels of 12 bits with output buffers
Programmable voltage detectoreight falling thresholds from 2.00 V to 2.88 V nominal, each with a rising edge about 100 mV higher
Debug portserial wire debug on two pins and JTAG on five, with the trace port sharing low order port bits
Backup domainVBAT domain keeps the RTC, the backup registers and the tamper input alive with the main rail off
Flash endurance and retention10 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 ambient45 C/W on this package
Input tolerancealmost all inputs 5 V tolerant
USBnot present, USB full speed is the STM32F102 line
Statusproduction data per the datasheet cover

Points to check before this part goes on a BOM

The B after the temperature digit is an internal code, and on this line it is the difference between two orderable strings that share a datasheet. Everything a buyer cares about is the same: 16 Kbytes of Flash, 4 Kbytes of SRAM, LQFP64 at 10 x 10 mm, 51 general purpose I/O, 16 converter channels and the two 12 bit DAC channels. What is not the same is the record, so a receiving inspection that checks a bag against a drawing should compare the whole string rather than the family and the memory size.

A board qualified on the lettered code can usually be built with the unlettered one, but the change is a revision change and not a purchase option. The practical test is the same for either: power the board, run the converter across all 16 channels, exercise both USARTs and a timer output, and confirm the current draw is inside the budget. Mixing the two strings inside one production lot is what should be avoided, because a field failure then cannot be traced to a single revision.

The interface set belongs to the low density memory column: one SPI block, one I2C block and two USARTs, plus the HDMI CEC channel. The 64 Kbyte and 128 Kbyte codes in the identical package bring the second SPI, the second I2C and the third USART. A substitute chosen by package and pin count alone can therefore be short of an interface, which is the failure mode this line produces most often when a buyer sources from a list of equivalents.

Sixteen converter channels on a 64 pin body is the reason this code is bought, and it also means the analog supply has to be treated as an analog supply. The reference pin, the analog supply pin and the ground return all sit in the same package, and a board that ties them to a noisy 3.3 V rail with a switching regulator on it will see the 12 bit result move with the load even though the converter itself is in specification. A ferrite and a local capacitor at each supply pin is the usual remedy.

The 4 Kbytes of SRAM is the number to check against a 16 channel scan. A double buffer of 16 results is 64 bytes, which is nothing, but the descriptors, the stack, the two serial buffers and any table of calibration coefficients are not. Firmware that keeps a 512 byte frame buffer per USART and a 1 Kbyte look up table has spent half the SRAM before the application variables are counted.

At 45 C/W the LQFP64 body allows about 440 mW from an 85 C ambient to a 105 C junction. The 51 general purpose I/O make that budget a pin question as much as a core question, and the two DAC channels add about 0.5 mA of analog supply current when they are enabled. A board that uses the DACs and drives twenty outputs is the case where the sum has to be done rather than assumed.

The part is production data in DocID16455 Rev 9, and its 10 kcycle Flash endurance is measured at minus 40 to plus 85 C. Any application that stores a counter in Flash has to convert the write rate into cycles before that number means anything: one write a minute is 525 thousand cycles a year, which is far outside the rating, while one write a day is inside it for the life of the product.

Where this order code fits

It is the same 16 Kbyte, 64 pin part with the internal letter, used where the bill of materials was qualified against that revision and the unlettered string is not an acceptable substitute without paperwork. 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 How to Verify a Drop in Replacement page. Both list the figures that have to match before a substitute goes on a BOM.

Questions buyers ask

Is the lettered part a different die from the unlettered one? ST does not publish a die revision map in the datasheet. What the document does establish is that both strings share one datasheet, the same memory size, the same package and the same peripheral set. Treating them as interchangeable is a procurement decision that should be recorded, not an assumption to make silently.

How many USARTs does this part have on 64 pins? Two. The third USART belongs to the 64 Kbyte and 128 Kbyte codes in the same package. A board that needs three ports has to move up the memory column, not the pin count.

Can the 16 converter channels be scanned continuously? Yes, the converter can be driven from the DMA controller and a timer, so a scan runs without the core touching each result. The limit is the conversion time of 1 microsecond per channel plus the sample time, so a 16 channel scan takes at least 16 microseconds plus overhead, which sets the scan rate the firmware can rely on.

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 Obsolete Part Cross Reference Hub page sets out the checks that keep a substitute from failing on the bench.