STM32F103ZCT6
Product Specifications
STM32F103ZCT6
ST — MCU & Embedded Processors
Product Overview
The STM32F103ZCT6 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
STM32F103ZCT6: 256 Kbytes, 112 I/Os and the Smallest High Density SRAM
STM32F103ZCT6 is the entry density of the 144 pin high density line: 256 Kbytes of flash with 48 Kbytes of SRAM, in the 20 by 20 mm LQFP144 body. The pin count is the same as the 512 Kbyte ZE part and the peripheral set is the same, so the difference is memory and nothing else. It is the code to pick when a board needs the pins and the memory controller but the firmware image is known to be under 200 Kbytes, and it is the code that catches teams out when the image grows past the limit late in a project.
Tracing the pin budget on 144 pins
Ports A through G give 112 usable I/Os. The memory controller in multiplexed 16 bit mode takes about 25 of them, and a display interface on the same bus adds its own control lines. What remains covers six USARTs worth of connections, two CAN transceivers, the USB pair, an SD card, the crystal, the debug port and still leaves more than 40 pins for relays, sensors, encoders and LEDs. That headroom is why 144 pin parts are common in machine control and in building automation panels, where a single board drives many small loads.
Values at a glance
| Parameter | Value | Note |
|---|---|---|
| Core and clock | Cortex-M3, 72 MHz | Single cycle multiply, hardware divide |
| Flash, SRAM | 256 Kbytes, 48 Kbytes | The only high density code at 48 Kbytes of SRAM |
| Package | LQFP144, 20 by 20 mm | LFBGA144 body available at the same pin count |
| I/O | 112 pins | 16 external interrupt vectors, nearly all 5 V tolerant |
| ADC, DAC | 3 converters, 12 bit, 21 channels; 2 DAC channels | 1 microsecond conversion, dual sample and hold |
| External memory | FSMC, four chip selects | Multiplexed NOR, PSRAM, NAND |
| Communication | 3 SPI, 2 I2S, 2 I2C, 5 USART, SDIO, USB, CAN | Thirteen interfaces in total |
| Temperature | Minus 40 to plus 85 C | Junction limit 125 C, code 7 gives 105 C ambient |
48 Kbytes of SRAM is the real constraint
The peripheral set is the same as on the 512 Kbyte part, which invites the same firmware ambitions, but the SRAM is 48 Kbytes rather than 64. A USB device stack, a CAN stack, an SD card file system with a 512 byte sector buffer and a 4 Kbyte ring, plus an RTOS with five tasks, lands close to 20 Kbytes before the application starts. Adding an external SRAM through the memory controller is the standard answer, and at that point the board is paying for the memory controller and the 144 pins anyway, so the C density is a deliberate choice rather than a saving.
Why the C density still ships in volume
Programmable logic controllers, weighing terminals and older instrument platforms were written for 256 Kbytes and stay there because their validation is complete. When the ZC code is short, the two options are the ZD code at 384 Kbytes or the ZE code at 512 Kbytes, both in the same body and both electrically compatible, with the second bank absent and the SRAM rising to 64 Kbytes. A documented microcontroller cross reference between the three codes, a procurement plan written for the change, and a drop in verification record that includes the SRAM difference are what make the substitution defensible at audit.
Common questions
Is the ZC part pin compatible with the ZE part? Yes, the pin definition table is identical. The SRAM size differs, which matters for any firmware that sizes a buffer from the linker memory map at compile time.
Does a bigger flash part draw more current? Not meaningfully in run mode, where the core and the peripherals dominate. In stop and standby the difference is in the noise, and the supply current tables in the datasheet are the authority for both codes.
Can the memory controller run an SRAM at 72 MHz? The bus timing allows it with a fast enough device; most external SRAM parts need one or two wait states at full speed, which the controller generates from its programmed timing registers.