STM32F103ZFT6
Product Specifications
STM32F103ZFT6
ST — MCU & Embedded Processors
Product Overview
The STM32F103ZFT6 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
STM32F103ZFT6: 768 Kbytes and 96 Kbytes of SRAM on 144 Pins
STM32F103ZFT6 is the 144 pin XL density device: 768 Kbytes of flash in two banks, 96 Kbytes of SRAM, 112 I/Os, the memory protection unit, an embedded trace macrocell, seventeen timers and the flexible static memory controller. The body is the 20 by 20 mm LQFP144. Where the 100 pin VF part is limited by its pin count for an external bus, this package brings out ports F and G and all four chip selects, so an external SRAM, a NOR flash and a NAND device can coexist with a display bus.
Two banks, two different jobs
Bank one holds 512 Kbytes and bank two holds 256 Kbytes on this density. Code executes from one bank while the other is programmed, which is what an in application update needs when there is no external memory: the new image is written into the idle bank, verified with the CRC unit, and the boot address is switched. Since the banks are separate regions rather than one flat 768 Kbyte space, the linker script has to describe both, and the vector table has to be relocatable from the first build rather than at the end of the project.
Values at a glance
| Parameter | Value | Note |
|---|---|---|
| Core and clock | Cortex-M3 with MPU, 72 MHz | Trace macrocell present, hardware divide |
| Flash, SRAM | 768 Kbytes dual bank, 96 Kbytes | Bank one 512 Kbytes, bank two 256 Kbytes |
| Package | LQFP144, 20 by 20 mm | LFBGA144 is the 10 by 10 mm alternative |
| I/O | 112 pins | Almost all 5 V tolerant, 16 external interrupt vectors |
| ADC, DAC | 3 converters, 12 bit, 21 channels; 2 DAC channels | 1 microsecond conversion, dual sample and hold |
| External memory | FSMC, four chip selects | LCD interface in 8080 and 6800 modes |
| Communication | 3 SPI, 2 I2S, 2 I2C, 5 USART, SDIO, USB, CAN | Thirteen interfaces counted by the vendor |
| Temperature | Minus 40 to plus 85 C | Junction limit 125 C, code 7 gives 105 C ambient |
96 Kbytes is enough for a real frame buffer
A 320 by 240 panel at 8 bits per pixel needs 76.8 Kbytes, which fits inside the on chip SRAM with about 19 Kbytes left over, and a monochrome 240 by 320 buffer fits four times. That combination, a 144 pin body and 96 Kbytes, is what makes a self contained instrument with a graphical interface possible without an external frame buffer chip. The refresh has to be driven by the application, because the LCD interface is a bus and not a controller, and the timing budget becomes the first thing to check when the panel resolution goes up.
The XL density in a supply plan
The ZF code and the ZG code at 1 Mbyte share the package and the die arrangement, so one substitutes for the other with no board change. The alternative when neither is available is to read the firmware size honestly and step down to the high density ZE part, which loses the second bank and 32 Kbytes of SRAM. Doing either cleanly needs a microcontroller cross reference that separates density from package, a strategic sourcing position on the annual volume, and a BOM consolidation review so that the two densities are not bought as two unrelated lines.
Common questions
Does the trace macrocell need extra pins? Yes, the trace port uses five pins on port B and port D in parallel trace mode, or the serial wire output alone at lower bandwidth. A board that keeps the trace pins on a header pays for them twice in the pin budget.
Can the part run code from the second bank at full speed? Both banks sit behind the same flash interface with two wait states at 72 MHz, so there is no speed difference between them, and the prefetch buffer and caches apply to both.
Is the SRAM split like the high density part? No. The XL density has 96 Kbytes contiguous, so a single buffer can be allocated at full size without the bank boundary that affects the smaller densities.