STM32G0B1CBU6
Product Specifications
STM32G0B1CBU6 — ARM Cortex-M0+ Microcontroller by STMicroelectronics
The STM32G0B1CBU6 is an STMicroelectronics ARM Cortex-M0+ MCU in - for Embedded control and general-purpose MCU applications. Supplied by SUPERB Automation.
Part Number Decoded — Field by Field
| Field | Value | Meaning |
|---|---|---|
| STM32G0B1CBU6 | 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 | STM32G0B1CBU6 |
| Core | ARM Cortex-M0+ |
| Package | - |
| Temperature Range | −40°C to +85°C |
| Supply Voltage | 1.8V–3.6V |
Product Overview
The STM32G0B1CBU6 is an STMicroelectronics ARM Cortex-M0+ microcontroller in - 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 STM32G0B1CBU6 supported by STM32CubeIDE?
Yes, the STM32G0B1CBU6 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 STM32G0B1CBU6 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.
STM32G0B1CBU6: the 48 pin QFN of the G0B1 line
The C is 48 pins, the B is 128 Kbytes and the U the UFQFPN body at 7 mm by 7 mm with a 0.5 mm pitch and an exposed pad. It is the smallest body in the STM32G0B1 family that still brings out both CAN controllers and the USB port, which makes it the compact option for a gateway or a charger rather than a cut down one.
The core is the Cortex-M0+ at 64 MHz, the RAM is 144 Kbytes with parity on 128, and the peripheral set includes the crystal-less USB device and host port, the Type-C Power Delivery controller, six USARTs, two low power UARTs and a 12-bit converter at 0.4 microsecond. Figures are from DS13560 Rev 6.
The compact member
| Package | UFQFPN48, 7 mm by 7 mm, 0.5 mm pitch, exposed pad |
| Flash | 128 Kbytes, two banks with read-while-write |
| RAM | 144 Kbytes, 128 Kbytes with parity |
| Core | Cortex-M0+ at 64 MHz |
| USB | Full speed device and host, crystal-less, Type-C Power Delivery |
| Fieldbus | Two FDCAN controllers |
| Serial | Six USART, two LPUART, three SPI |
| ADC and DAC | 12-bit at 0.4 microsecond, two 12-bit DACs |
| Timers | Fifteen, two capable of 128 MHz |
| I/O | Up to 42 fast lines on this body |
| Supply | 1.7 V to 3.6 V, separate I/O rail from 1.65 V |
| Temperature | Minus 40 to plus 85 degrees C |
Small body, big memory
144 Kbytes of RAM against 128 Kbytes of flash is an unusual ratio, and it is deliberate: the Type-C stack and the USB stack both want buffers, and a product that logs to RAM before writing to flash needs more working memory than code. A dock that buffers a firmware image for a downstream device, a charger that keeps a transaction log, a gateway that queues CAN frames through a lossy link: these are RAM bound and not code bound, and this member suits them.
Two banks at 128 Kbytes total means 64 Kbytes per bank, so the update image has to fit in that half. Where the application image is larger, the C or E density in the same family is the answer, and the pinout stays the same in the 48 pin body. Our MCU cross reference page sets out those density steps.
QFN handling on a small board
A 7 mm QFN with an exposed pad needs the via field and the windowed paste aperture that this package family always needs, and it needs the pad connected to a plane that can carry the heat. On a 48 pin part running at 64 MHz the dissipation is modest, and the pad is still the main path, so a board that ignores it runs warmer than it should in a sealed enclosure.
Moisture handling follows the bag label, and a reel that has been open beyond its floor life is baked before reflow. Our kitting service page describes how the reels and the dry pack are staged per build, and the incoming inspection plan records the marking, the date code and the packing form at goods in so a substituted body does not reach the line.
Questions from a charger project
Can the Type-C controller run a 100 W contract? The Power Delivery block supports the protocol, and the power path itself is external, so the answer depends on the FETs and the sense resistor rather than on the microcontroller. Does the part need a crystal for USB? No, the crystal-less mode is supported at full speed, and a crystal is needed only where the application requires an accurate time base.
Is the 48 pin body available in the 105 C grade? Yes, under the string ending in 7, and the junction limit rises with it. Our component traceability report keeps the grade and the lot together for each shipment, which is what a customer audit asks for when the product carries a safety function.