STM32F103C6T6
Product Specifications
STM32F103C6T6
ST — MCU & Embedded Processors
Product Overview
The STM32F103C6T6 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
STM32F103C6T6: the 32 Kbyte Member of the Same 48 Pin Family
STM32F103C6T6 is the 32 Kbyte flash, 10 Kbyte SRAM version of the STM32F103 low density line in the same 48 pin LQFP body as the better known 64 Kbyte part. The core is the same Cortex-M3 at 72 MHz, the supply range is the same 2.0 to 3.6 V, and the pin count is the same 37 usable I/Os, so the two codes differ in memory and in a reduced peripheral count rather than in pinout. The 6 in the code is the industrial grade of minus 40 to plus 85 C.
What the low density line keeps and what it drops
Low density devices carry two general purpose 16 bit timers instead of three, one SPI instead of two, one I2C instead of two and two USARTs instead of three. The advanced control timer with dead time generation, the CAN 2.0B active controller and the USB 2.0 full speed port are all still present. That combination is unusual at 32 Kbytes: it means a small motor drive with a CAN interface, or a USB peripheral that also talks on a field bus, can be built on the smallest memory option in the family.
Values at a glance
| Parameter | Value | Note |
|---|---|---|
| Core and clock | Cortex-M3, 72 MHz, 1.25 DMIPS/MHz | 0 wait state access at 72 MHz within the supply range |
| Flash, SRAM | 32 Kbytes, 10 Kbytes | The 16 Kbyte sibling is the C4 code |
| Package | LQFP48, 7 by 7 mm | Also offered in UFQFPN48 and VFQFPN36 for the T4 and T6 codes |
| I/O | 37 pins | 16 external interrupt vectors, nearly all 5 V tolerant |
| ADC | 2 converters, 12 bit, 10 channels | Dual sample and hold, 0 to 3.6 V conversion range |
| Timers | 2 general purpose, 1 advanced control, 2 watchdog | Advanced timer has dead time and emergency stop |
| Communication | 1 SPI at 18 Mbit/s, 1 I2C, 2 USART, USB FS, CAN | Six communication interfaces in total |
| Temperature | Minus 40 to plus 85 C | Industrial suffix 6 as ordered |
Ten Kbytes is a real budget, not a technicality
A CAN stack that handles a 100 message per second bus with eight mailboxes, a small state machine and a bootloader flag set typically lands between 2 and 3 Kbytes of RAM. Add a UART command parser with a 256 byte ring and a timer driven ADC sampler with 8 channels buffered for 16 samples, and the total is near 5 Kbytes. That leaves about half of the device for the application, which is workable for a sensor node or an actuator controller and tight for anything that buffers a log. If the product needs a flash log or an over the air image, the 64 Kbyte C8 code in the same footprint is the cheaper decision than compressing the firmware later.
Why buyers still order the C6 code
Boards that were sized for 32 Kbytes of code stay on the C6 code because a change to the C8 code, while pin compatible, changes what the production file and the test fixture were validated against. When the C6 is quoted with a longer date than the C8, the paperwork to accept the larger density is usually a formality, and a microcontroller cross reference sheet that records both codes on the same row is what an auditor asks for. Where the part is already obsolete on a supplier list, the obsolete part reference hub explains what an equivalent candidate has to match, and OEM procurement covers how a replacement gets qualified without a full requalification cycle.
Common questions
Is the C6 pin compatible with the C8? Yes, both are LQFP48 parts from the same family with the same pin definition table. The peripheral count is lower on the C6, so functions that exist on the C8 but not on the C6 have to be checked pin by pin, not assumed.
Does it have a DAC? No. The digital to analog converter arrives with the 256 Kbyte and larger high density devices. On this part an external DAC or a PWM plus filter is the only route.
Can the flash be read out? The readout protection levels in the reference manual apply, and the level 1 setting still allows a debugger to attach after a mass erase. For a product that stores calibration, the 96 bit unique ID is there to bind the image to the device.