STM32G030K8T6
Product Specifications
STM32G030K8T6 — ARM Cortex-M0+ Microcontroller by STMicroelectronics
The STM32G030K8T6 is an STMicroelectronics ARM Cortex-M0+ MCU in LQFP-32 for Embedded control and general-purpose MCU applications. Supplied by SUPERB Automation.
Part Number Decoded — Field by Field
| Field | Value | Meaning |
|---|---|---|
| STM32G030K8T6 | Full Part Number | STMicroelectronics ARM Cortex-M0+ Microcontroller |
| STM32 | Product Family | STMicroelectronics 32-bit ARM-based MCU |
| G0 | Series | ARM Cortex-M0+ based MCU — G0 series |
Quick Specifications
| Parameter | Value |
|---|---|
| Manufacturer | STMicroelectronics |
| Part Number | STM32G030K8T6 |
| Core | ARM Cortex-M0+ |
| Package | LQFP-32 |
| Temperature Range | −40°C to +85°C |
| Supply Voltage | 1.8V–3.6V |
Product Overview
The STM32G030K8T6 is an STMicroelectronics ARM Cortex-M0+ microcontroller in LQFP-32 package. Part of ST's extensive STM32 portfolio, it delivers a high-performance processing platform with integrated Flash, SRAM, and a rich set of communication peripherals for Embedded control and general-purpose MCU applications. Supplied by SUPERB Automation with full traceability and competitive lead times.
Key Features & Benefits
ARM Cortex-M0+ Core — Efficient Processing for Embedded Control
The ARM Cortex-M0+ core provides deterministic real-time performance with hardware multiply/divide and optional FPU, executing control loops, communication stacks, and sensor fusion algorithms efficiently in resource-constrained embedded environments.
Rich Peripheral Set — GPIO, Timers, ADC, Communication Interfaces
Features a comprehensive set of on-chip peripherals including multi-channel DMA, 12/16-bit ADCs, advanced PWM timers for motor control, and multiple USART/SPI/I²C interfaces for sensor and communication module connectivity.
ST Ecosystem — CubeMX, HAL, LL, Middleware
Fully supported by ST's STM32Cube ecosystem including CubeMX graphical configuration, HAL/LL driver libraries, FreeRTOS integration, and extensive middleware stacks (USB, TCP/IP, FATFS, graphics) — accelerating firmware development and reducing time-to-market.
Target Applications
Embedded Control & IoT Systems
Functions as the main processing unit in embedded control systems, IoT endpoints, sensor hubs, motor controllers, and human-machine interfaces — leveraging the Cortex-M architecture for efficient, low-power operation.
Industrial Automation & Motor Control
Powers industrial motor drives, PLCs, sensor transmitters, and factory automation equipment — taking advantage of advanced PWM timers, high-speed ADCs, and CAN/RS-485 communication for distributed control architectures.
Consumer & Portable Electronics
Integrates into consumer devices, wearables, smart home products, and portable instruments — benefiting from the STM32 family's low-power modes, small packages, and extensive third-party firmware ecosystem.
Frequently Asked Questions
Is the STM32G030K8T6 supported by STM32CubeIDE?
Yes, the STM32G030K8T6 is fully supported in STM32CubeIDE with graphical pinout configuration, clock tree setup, and automatic peripheral initialization code generation — enabling rapid prototyping and production firmware development.
What firmware/RTOS options are available?
The STM32 family is supported by FreeRTOS, Zephyr, NuttX, ChibiOS, and bare-metal HAL programming. For drone applications, Betaflight, iNav, ArduPilot, and PX4 all have STM32 HAL targets.
What is the minimum order quantity (MOQ)?
Contact SUPERB Automation for a tailored quote. We support quantities from prototype tray to full production volumes.
Request a Quote
SUPERB Automation supplies genuine STMicroelectronics STM32G030K8T6 MCUs with full traceability and batch-level QA documentation. Whether you need a single tray for prototype builds or pallet-level volumes for production, we source through verified channels with competitive lead times. Contact us with your target quantity and delivery date — we'll respond with a detailed quotation within 24 hours.
STM32G030K8T6: 64 Kbytes of flash in a 32 pin LQFP
The code reads G for general purpose, 030 for the value line, K for 32 pins, 8 for 64 Kbytes of flash, T for the LQFP body and 6 for the range of minus 40 to plus 85 degrees C with a 105 degree junction. In 7 mm by 7 mm that is a complete microcontroller with a converter, two comparators' worth of analog support, two USARTs and two SPI ports, for a board that has to fit behind a panel or inside a sensor housing.
The core is a Cortex-M0+ at up to 64 MHz with 8 Kbytes of SRAM carrying a hardware parity check, a voltage range of 2.0 V to 3.6 V, a 12-bit converter at 0.4 microseconds with up to 16 external channels, and eight timers. Every figure in this page is read from the STM32G030x6/x8 data sheet.
The small body in figures
| Core | Cortex-M0+ at up to 64 MHz |
| Flash | 64 Kbytes with protection, 32 Kbytes on the x6 density |
| SRAM | 8 Kbytes with hardware parity check |
| Supply | 2.0 V to 3.6 V |
| Temperature | Minus 40 to plus 85 degrees C, 105 degree junction |
| ADC | 12 bit at 0.4 microseconds, up to 16 external channels, 16 bit by oversampling, 0 to 3.6 V range |
| DMA | Five channels with flexible mapping |
| Timers | Eight, one 16-bit advanced motor control, four 16-bit general purpose, two watchdogs |
| Serial | Two I2C at 1 Mbit per second with SMBus and PMBus support, two USART with ISO7816 and LIN, two SPI at 32 Mbit per second |
| I/O | Up to 44 fast lines across the family, several 5 V tolerant |
| Low power | Sleep, stop and standby, with VBAT for the RTC and backup registers |
| Package | LQFP32, 7 mm by 7 mm; the family also ships in LQFP48, TSSOP20 and SO8N |
What 32 pins can hold
An LQFP32 gives 30 usable lines after the supply and the ground, and the arithmetic of a small product usually runs out before the flash does. A typical allocation is six lines for a display or a keypad, two for a UART to a host, two for an I2C sensor bus, three for an analog front end, four for a relay and two status outputs, and the rest for a programming header and a couple of diagnostic points. That leaves nothing spare, which is why the pin map is the first document to write and not the last.
The 64 Kbyte density is what makes that bearable. A Modbus or a small command protocol, a display driver and a control loop fit in about 30 Kbytes, which leaves half the array for a bootloader and for parameters stored in the last sectors. On the 32 Kbyte member of the same body the same application leaves very little room, and that is the decision this page is about: the flash size steps inside one package, with no change to the board and no change to the pin map.
The programming path is worth fixing early as well. Serial wire debug needs two lines, and those two lines are usually shared with a GPIO that the application wants, so the pin map has to leave them accessible on the header even when the product is closed. A bootloader in the first 8 Kbytes, entered by holding one line during reset, is what allows a firmware update over the same UART that the product uses for its host, and it costs a few Kbytes of the 64 that the density buys.
Where the product is expected to grow, the 48 pin member gives the same die with more lines and the same code. Our MCU cross reference page records which members of a value line share a body so that a change of plan is a change of order code rather than a new board.
The converter and the timers are the reason to pay for more than a comparator
A 12-bit converter at 0.4 microseconds converts fast enough to sample a mains waveform 100 times a cycle, which is what a small energy meter or a dimmer needs in order to compute an RMS value or a phase angle. Sixteen external channels across the family means the 32 pin body brings out enough of them to measure a current, a voltage, a temperature and two reference dividers at the same time. Oversampling to 16 bits is how a load cell or a pressure bridge gets its resolution without an external amplifier.
The advanced motor control timer carries the complementary outputs and the dead time for a half bridge, which is the difference between driving a small pump or a fan directly and adding a gate driver with its own timing. The four general purpose timers cover the rest: a pulse counter for a flow sensor, a periodic interrupt for the control loop, and a PWM for a backlight.
Two SPI ports at 32 Mbit per second are enough for an external flash or a radio module, and two I2C ports at 1 Mbit per second with SMBus support cover a battery gauge or a PMBus rail monitor. The power management cross reference page lists the rails and monitors we pair with a controller of this size, since a 32 pin part usually sits beside a supply that talks over the same bus. On a 7 mm body the two I2C ports are often the whole management interface of a product, one to the rail monitor and one to a sensor, which is why the SMBus timing matters more here than the headline 1 Mbit per second. A rail monitor and a sensor on the same two wires also means the bus has to survive a hot plug at the connector, and that is where the 5 V tolerance on the data and clock lines earns its place on a board with no room for a translator.
Parity on the SRAM and what it detects
Eight Kbytes with a hardware parity check is a small feature that changes the failure mode of a product. A single bit flip from a supply transient or a cosmic ray is detected on read and raises a fault instead of being used as a value. On a pump controller or a valve actuator that matters, because the alternative is a control loop acting on a corrupted setpoint with no record of why. The check is not correction, and the firmware still has to decide what to do, but the event is at least visible.
The 2.0 V floor is the other constraint to plan around. A product running from a 3.3 V rail has margin, and one running from two alkaline cells loses the bottom of the discharge curve: at 1.9 V the part is out of specification even though the cells still have energy. Where that matters, the G051 subfamily goes down to 1.7 V on the same core, and the difference is the reason the two lines are quoted side by side. Our pin to pin cross reference page records which of them share a footprint.
Questions before the first order
Is the 64 Kbyte part the same body as the 32 Kbyte one? Yes, K8 and K6 are the same LQFP32, and the density is the only difference. Is the SO8N body usable for production? It is, and it is the cheapest way to put a controller on a small board, but it has six usable lines, so it fits a sensor node rather than a product with a display.
Does the part need an external crystal? The internal 16 MHz RC with a PLL option is accurate to about 1 per cent, which is enough for a UART at 115200 baud and not enough for a USB or a radio. A 4 to 48 MHz crystal is the answer where the timing has to hold, and the 32 kHz crystal with calibration is what keeps the RTC honest over temperature. Our kitting service page describes how we stage the crystal, the load capacitors and the programming header with the rest of the kit so that the line receives one package rather than a set of partial deliveries.