STM32G071G8U6
Product Specifications
STM32G071G8U6 — ARM Cortex-M0+ Microcontroller by STMicroelectronics
The STM32G071G8U6 is an STMicroelectronics ARM Cortex-M0+ MCU in UFQFPN-28 for Embedded control and general-purpose MCU applications. Supplied by SUPERB Automation.
Part Number Decoded — Field by Field
| Field | Value | Meaning |
|---|---|---|
| STM32G071G8U6 | 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 | STM32G071G8U6 |
| Core | ARM Cortex-M0+ |
| Package | UFQFPN-28 |
| Temperature Range | −40°C to +85°C |
| Supply Voltage | 1.8V–3.6V |
Product Overview
The STM32G071G8U6 is an STMicroelectronics ARM Cortex-M0+ microcontroller in UFQFPN-28 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 STM32G071G8U6 supported by STM32CubeIDE?
Yes, the STM32G071G8U6 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 STM32G071G8U6 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.
STM32G071G8U6: the same 64 MHz core in a 28 pin 5 mm package
This is the small body of the G071 subfamily and the two characters that change are the pin count and the flash density. G is the product line, 071 the subfamily with the USB Type-C Power Delivery controller, G is the 28 pin body, 8 is 64 Kbytes of flash, U is the ultra thin quad flat package with no leads at 5 mm by 5 mm and 0.55 mm tall, and 6 is the industrial range. The core, the SRAM and the analog block do not change with the body, which is why the same firmware can move between a 28 pin and a 48 pin board with a different pin map rather than a different code base.
The die still runs to 64 MHz from 1.7 to 3.6 V with 36 Kbytes of SRAM, of which 32 Kbytes carry hardware parity. The flash is 64 Kbytes with read protection, write protection and a securable area, which at a 512 byte page is 128 pages. Fourteen timers remain, two of them at 128 MHz, and the 12 bit converter still converts in 0.4 microseconds with hardware oversampling to 16 bits. What the 28 pin body takes away is pins, not peripherals: the port count is what falls, so the four USARTs, two SPI ports and two I2C ports cannot all be brought out at once.
The order code, character by character
| Product family | STM32, 32 bit Arm microcontroller |
| Product line | G0, mainstream Cortex-M0+ |
| Subfamily | 071, Power Delivery and HDMI CEC on chip |
| Pin count | G, 28 pins |
| Flash density | 8, 64 Kbytes |
| Package | U, UFQFPN 5 mm by 5 mm, 0.55 mm body |
| Temperature | 6, minus 40 to plus 85 degrees C ambient |
| Core clock | 64 MHz Cortex-M0+ |
| SRAM | 36 Kbytes, 32 Kbytes with hardware parity |
| Flash pages | 128 pages at 512 bytes |
| Analog | 12 bit ADC, 0.4 us per conversion, two 12 bit DACs |
| Timers | 14, two rated to 128 MHz |
| Supply | 1.7 to 3.6 V, VBAT pin for the RTC and backup registers |
| Identification | 96 bit unique ID, serial wire debug on two pins |
What 28 pins costs a product
Twenty eight pins sounds like a toy until the power, ground, reset and debug pins are subtracted. Serial wire debug takes two, the reset and boot pins take two more, and a 5 mm package needs at least two ground pins and one supply pin per rail. That leaves roughly twenty usable signals, and a product that wants a crystal, four USARTs, two SPI ports, a USB port and an eight channel ADC cannot have all of them. The practical answer is the internal 16 MHz RC oscillator trimmed to plus or minus one percent, which releases the two crystal pins, and remapping the second USART onto pins that the first one does not use.
The other cost is thermal and mechanical. A 5 mm by 5 mm body with no leads has an exposed pad that is the only path for heat and the only path for a good ground, and the paste window on that pad decides both. A 0.55 mm body also limits the decoupling that fits under the part, so the 100 nF capacitor has to sit outside the footprint within a few millimetres of the supply pin. On a four layer board that is a straight run; on a two layer board it is the first thing that fails an EMC scan.
Questions that arrive with a shortage quote
Is the 64 Kbyte part a subset of the 128 Kbyte part? Functionally yes, the peripheral set is the same, but the flash density changes the linker map and the page count, so a firmware image built for the B density has to be re-linked. The 36 Kbytes of SRAM do not change between densities, so code that already fills the RAM will not gain headroom on the larger part either.
Can this replace the 48 pin part during a shortage? Only if the product was written with the pin map abstracted. The electrical ratings and the peripheral set match, so the change is a board change and a pin map change, and the 28 pin body will not carry every signal the 48 pin board used.
Why is the U suffix used for two different packages? The letter marks the package family, not the exact outline: U covers the ultra thin quad flat pack with no leads, and the pin count plus the datasheet outline drawing together give the body size. A 5 mm and a 7 mm part can both carry a U, so the size is read from the datasheet table, not from the letter.
What to send with an enquiry
Four fields decide the price and the date: quantity, target date, the full order code with the temperature suffix, and the packing format. Send the string and we check it on the MCU cross reference page, then confirm date codes and origin on the quotation. Small bodies are usually ordered in reels and cut tape through our kitting service, and the date code management note explains how older stock is held and labelled.