Contact Us

STM32F100CBT6

Brand: ST
ST STM32F100CBT6 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

STM32F100CBT6 — MCU & Embedded Processors | Superb Automation

STM32F100CBT6

ST — MCU & Embedded Processors

Product Overview

The STM32F100CBT6 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

STM32F100CBT6: 128 Kbyte, LQFP48 body

STM32F100CBT6 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 LQFP48 body at 7 x 7 mm with 48 pins, 37 general purpose I/O and 10 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 codeSTM32F100CBT6
Program Flash128 Kbytes
SRAM8 Kbytes
PackageLQFP48, 7 x 7 mm, 48 pins
Maximum general purpose I/O37
Analog input channels10 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 ambient55 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

128 Kbytes of Flash in a 7 x 7 mm body is the reason this code exists. Table 2 puts the medium density set behind it, so the 48 pin body carries two SPI blocks, two I2C blocks, three USARTs, the HDMI CEC channel, one advanced-control timer, up to six general purpose timers and the two 12 bit DAC channels. The memory column, not the package, is what unlocks the interfaces, which is why a board revision that changes only the memory size still has to be re-checked against the pin table.

The 8 Kbytes of SRAM is unchanged from the 64 Kbyte code, and on a part with three USARTs that is the number that limits throughput. Three ports at 115200 baud with a 512 byte buffer each is 1.5 Kbytes, the converter scan buffer and its DMA descriptors take another block, and the stack for a Cortex-M3 with floating point emulation needs 1 Kbyte or more. That leaves roughly 4 Kbytes for the application, which is workable but not generous.

The 48 pin body still has 10 converter channels and 37 general purpose I/O. A board that wants three USARTs, two SPI blocks, the CEC line and the two DAC outputs is asking a lot of one 48 pin package, because the serial interfaces and the analog pins come out of the same port A, B and C pins. The pin table decides whether the combination is possible, and the answer is often that one interface has to move to a 64 pin body.

The 55 C/W thermal figure gives about 360 mW between an 85 C ambient and the 105 C junction limit. On a 128 Kbyte part the core current at 24 MHz is the same as on the smaller codes, so the memory size does not change the thermal answer; what changes it is how many interfaces are active and how much current the I/O sinks. A board that drives a display or a set of LEDs spends the budget on the pins rather than on the core.

Because this is the top of the low and medium density range, it is also the code most likely to be compared against the F101 access line and the F103 performance line. The F101 high density parts bring the external memory controller and five USARTs, and the F103 parts bring USB and a 72 MHz core. Those comparisons are pin count decisions as much as they are feature decisions, and the cross reference list is where the matching figures are collected.

Flash endurance on the line is 10 kcycles at minus 40 to plus 85 C and 1 kcycle at 105 C, with 30 years of retention at 85 C after one kcycle. A 128 Kbyte part with read out protection and a bootloader in the first pages is a common arrangement, and it works only if the option bytes are set before the board leaves the line, because a blank option byte state leaves the protection off and the boot pins in their default position.

The two basic timers, TIM6 and TIM7, exist to trigger the converters and generate a timebase without consuming a general purpose timer. On a part this size that is worth using: the control loop can run from a general purpose timer while a basic timer paces the converter scan, so a scan overrun does not disturb the loop timing and the DMA completes a block on a fixed schedule.

Where this order code fits

It is the largest memory in the 48 pin body, used where the firmware is the reason for the part and the board has no room for a 64 pin 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 Obsolescence Management page. Both list the figures that have to match before a substitute goes on a BOM.

Questions buyers ask

Which serial interfaces does the 128 Kbyte code have on 48 pins? Two SPI blocks, two I2C blocks and three USARTs, plus the HDMI CEC channel, which is the medium density set in Table 2 of DocID16455 Rev 9. The 16 and 32 Kbyte codes in the same package have one SPI, one I2C and two USARTs.

Is there any external memory option on this part? No. The external memory controller belongs to the high density parts in the 100 and 144 pin bodies on this line. A 48 pin part that needs more storage uses an SPI serial Flash or an I2C EEPROM on one of the two SPI or two I2C blocks, which is also the cheaper arrangement for logging.

Can this part replace a 32 Kbyte code without a board change? Electrically and mechanically yes, because the package and pin out are the same, and the extra interfaces appear on pins that were general purpose I/O on the smaller code. The firmware has to be rebuilt for the memory map and the board file has to record the new string, and any pin that was used as plain I/O and is now a serial interface has to be re-checked.

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.