STM32G030K6T6
Product Specifications
STM32G030K6T6 — ARM Cortex-M0+ Microcontroller by STMicroelectronics
The STM32G030K6T6 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 |
|---|---|---|
| STM32G030K6T6 | 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 | STM32G030K6T6 |
| Core | ARM Cortex-M0+ |
| Package | LQFP-32 |
| Temperature Range | −40°C to +85°C |
| Supply Voltage | 1.8V–3.6V |
Product Overview
The STM32G030K6T6 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 STM32G030K6T6 supported by STM32CubeIDE?
Yes, the STM32G030K6T6 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 STM32G030K6T6 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.
STM32G030K6T6: fitting a product into 32 Kbytes
This is the 32 Kbyte density of the same 32 pin body as the K8: Cortex-M0+ at 64 MHz, 8 Kbytes of SRAM with parity, 2.0 V to 3.6 V, a 12-bit converter at 0.4 microseconds and eight timers in a 7 mm by 7 mm LQFP. The flash is the only difference, and it is the difference that decides whether a product fits.
The question this page answers is not what the part can do, it is how much application fits in 32 Kbytes and what has to be cut when it does not. The figures are from the STM32G030x4/x6 family document, and the order code reads K for 32 pins, 6 for 32 Kbytes, T for LQFP and 6 for the industrial range.
The part in figures
| Core | Cortex-M0+ at up to 64 MHz |
| Flash | 32 Kbytes with protection, 64 Kbytes on the x8 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 |
| DMA | Five channels |
| Timers | Eight, including one advanced motor control and two watchdogs |
| Serial | Two I2C at 1 Mbit per second, two USART, two SPI at 32 Mbit per second |
| Package | LQFP32, 7 mm by 7 mm |
| Family bodies | SO8N, TSSOP20, LQFP32 and LQFP48 on the same die |
The arithmetic of a 32 Kbyte application
A Cortex-M0+ instruction is mostly 16 bits, so 32 Kbytes is roughly 16000 instructions of code. A bare metal control loop with a converter, a PWM, a state machine and a small protocol fits in 8 to 12 Kbytes. Adding a Modbus stack costs 6 to 8 Kbytes, a segment display driver 2 to 3 Kbytes, and a bootloader with a checksum and a flash write routine 3 to 4 Kbytes. That is 25 Kbytes before any diagnostic or calibration code, and it leaves about 7 Kbytes for the part of the product that makes it different from the reference board.
The steps that recover space are known ones. Compiling for size and dropping the unused peripheral modules from the library is worth 2 to 4 Kbytes on a typical project. Replacing floating point with fixed point removes the software library and its constants. A table driven state machine replaces a switch with a long tail of handlers. None of them changes the behaviour of the product, and all of them are cheaper than moving the density after the board is built.
What does not shrink is the part of the code that talks to the outside world. A protocol stack written to a standard has a size that is decided by the standard, and a display driver has a size decided by the panel. That is why the honest planning figure for a connected product with a display is 40 Kbytes and not 25, and why the K6 is usually the right part for a product without a display or a fieldbus.
Where the budget is tight, the cuts are known ones. Fixed point arithmetic instead of floating point saves the library. A table driven state machine replaces a switch with a long tail. The protocol is trimmed to the function codes the product actually needs. What does not shrink is the vendor peripheral library if it is linked whole, and compiling with size optimisation and dropping the unused modules is the first step before changing the density.
When the application lands at 30 Kbytes and the next feature will not fit, the answer is the K8 in the same body, and the MCU cross reference page records that step so it is a purchase order change rather than a new board.
What is still on the die at this density
The peripherals do not shrink with the flash. Two SPI ports at 32 Mbit per second, two I2C at 1 Mbit per second with SMBus and PMBus, two USARTs with ISO7816 and LIN, an advanced motor control timer with dead time, four general purpose timers and a five channel DMA are all present on the 32 Kbyte part exactly as on the 64 Kbyte one.
The converter is the same 12-bit 0.4 microsecond block, so a product that samples a mains waveform or a bridge at 100 samples per cycle keeps that ability. Sixteen external channels across the family cover a current, a voltage, two temperature points and a set of dividers, and 16-bit oversampling is available when the signal is slow. The ADC and DAC cross reference page lists the parts we compare when a channel or a resolution is missing.
Where this density is the right answer
A relay timer, a fan controller, a level switch, a small sensor transmitter, a battery gauge with a display: these are products whose firmware is finished and whose cost has to come down. Moving from the K8 to the K6 in the same body takes a few cents off the unit price without touching the board, the stencil or the test fixture, and the firmware only has to be rebuilt against the smaller memory map and re-verified.
The re-verification is the step that gets skipped. A build linked for 64 Kbytes will not fit, and the change is not only the linker script: a bootloader that assumed the application starts at 0x08004000 has to move, and a parameter region placed in the last sector moves with it. Doing that on the bench is routine, and doing it after the order is placed is a schedule problem.
That last step is the one that gets skipped. A build that was linked for 64 Kbytes will not fit, and the change is not only the linker script: a bootloader that assumed the application starts at 0x08004000 has to move, and a parameter region placed in the last sector moves with it. Doing that on the bench is routine, and doing it after the order is placed is a schedule problem. Our date code management page covers how we keep the two densities apart on the shelf so that a line does not receive K6 reels against a K8 build.
Questions before the order
Is the pinout identical to the K8? Yes, same body, same 32 pins, same alternate functions. Is the SO8N body an option at 32 Kbytes? Yes, and it is the cheapest way to put a controller on a small board, with six usable lines. Does the 2.0 V floor rule out a two cell alkaline product? It rules out running to the end of the cells, and the honest answer is to check the G051 subfamily, which goes to 1.7 V on the same core.
Where the product needs a display and a fieldbus, the 48 pin member of the same family is the body to price, and the code moves across with the linker script and the pin map. That is the step this density makes possible: the same die, the same peripherals and the same firmware tree, with the pin count and the flash chosen against the product rather than against the reference board it started from.
That is also the answer when the 32 Kbyte part runs out mid project: the same firmware tree builds for the larger density with the linker script changed, and the re-verification is a bench task rather than a new board bring up.
The test fixture does not change between the two densities, which is the practical reason the step is cheap. The same probe card, the same programming header and the same functional test apply, and only the image that is loaded differs. That is worth confirming before the order, because a product that needs a different fixture for each density has lost the saving the smaller flash was meant to bring.
Our one stop BOM sourcing page covers how we hold both densities and the crystal, the load capacitors and the programming header against a build, so a change of density does not become a second purchase order for passives.