STM32G0B1RCT6
Product Specifications
STM32G0B1RCT6 — ARM Cortex-M0+ Microcontroller by STMicroelectronics
The STM32G0B1RCT6 is an STMicroelectronics ARM Cortex-M0+ MCU in LQFP-64(10x10) for Embedded control and general-purpose MCU applications. Supplied by SUPERB Automation.
Part Number Decoded — Field by Field
| Field | Value | Meaning |
|---|---|---|
| STM32G0B1RCT6 | 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 | STM32G0B1RCT6 |
| Core | ARM Cortex-M0+ |
| Package | LQFP-64(10x10) |
| Temperature Range | −40°C to +85°C |
| Supply Voltage | 1.8V–3.6V |
Product Overview
The STM32G0B1RCT6 is an STMicroelectronics ARM Cortex-M0+ microcontroller in LQFP-64(10x10) 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 STM32G0B1RCT6 supported by STM32CubeIDE?
Yes, the STM32G0B1RCT6 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 STM32G0B1RCT6 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.
STM32G0B1RCT6: 256 Kbytes in the same 64 pin body
The C in this order code is 256 Kbytes of flash where the E of its sibling is 512. The body, the pinout and the peripheral set are otherwise identical: 64 pin LQFP, Cortex-M0+ at 64 MHz, 144 Kbytes of SRAM with parity on 128 of them, two FDCAN controllers, the crystal-less USB port with the Type-C Power Delivery controller, six USARTs and two low power UARTs.
The choice between this part and the 512 Kbyte member is a code budget question and nothing else, which makes it one of the easier decisions in a bill of materials. Figures are from DS13560 Rev 6.
Same body, smaller array
| Flash | 256 Kbytes, two banks with read-while-write |
| RAM | 144 Kbytes, 128 Kbytes with parity |
| Core | Cortex-M0+ at 64 MHz |
| Package | LQFP64, 10 mm by 10 mm |
| USB | Full speed device and host, crystal-less, Type-C Power Delivery |
| Fieldbus | Two FDCAN controllers |
| Serial | Six USART, two LPUART, three SPI, I2C at 1 Mbit/s |
| ADC | 12-bit at 0.4 microsecond, up to 16 external channels |
| Timers | Fifteen, two capable of 128 MHz |
| Supply | 1.7 V to 3.6 V, separate I/O rail |
| I/O | Up to 60 fast lines |
| Temperature | Minus 40 to plus 85 degrees C |
What 256 Kbytes holds in practice
A CANopen stack, a USB device stack with the Power Delivery negotiation, a bootloader and an application with a parameter area fits in 256 Kbytes with margin, and the same set on a second protocol or a display library does not. That is the line most customers are standing on when they ask us to quote both densities, and the answer usually comes from the linker map rather than from a preference.
The two bank arrangement survives at this density, so the field update behaviour is the same as on the larger part. That matters because a decision to save cost by dropping to 256 Kbytes should not also cost the ability to update the product without a service visit. Where the application needs the larger array, the E member is a part change on the same footprint, and the pin to pin cross reference page records that pairing.
Availability and the lifetime question
A 64 MHz M0+ part with this peripheral set sits in a crowded part of the market, and the density most often in stock is not always the one the firmware was written around. A product that can run in 256 Kbytes and is qualified for both densities is more resilient than one that only accepts the larger part, and the difference is a linker file and a test run rather than a new board.
The other side of availability is the end of life notice. A part with a long production history is more likely to be discontinued than a recent one, and a customer building equipment with a ten year support commitment should plan a last time buy rather than discover the notice at the wrong moment. Our last time buy and LTB planning page describes how we size that order and how the stock is stored.
Ordering notes
Is the RCT6 the same die as RET6? Yes, and the same body, with the array cut to 256 Kbytes. Does the temperature grade differ? The 6 suffix is minus 40 to plus 85 degrees C with a 105 degree junction; the 7 suffix raises the ambient to 105 degrees C with a 125 degree junction and the 3 suffix to 125 degrees C with a 130 degree junction.
Packing is tray or tube unless a reel suffix is named, and the reel size differs between bodies in this family, so the quantity on the purchase order should state the packing form. The MCU cross reference page keeps the density, body and grade combinations in one place so a quote request does not need a string decoded by hand.