Contact Us

STM32G474RBT6

Brand: ST
STM32G474RBT6 is a ARM Cortex-M microcontroller from STMicroelectronics, designed for drone electronics, embedded control systems, and industrial IoT applications. Superb Automation supplies genuine STM32G474RBT6 with full traceability, competitive pricing, and fast global delivery — supporting prototype to production volumes for drone, robotics, and industrial customers worldwide.
quote now

Product Specifications

STM32G474RBT6 — ARM Cortex-M4F Microcontroller by STMicroelectronics

The STM32G474RBT6 is an STMicroelectronics ARM Cortex-M4F MCU in LQFP-64 for Embedded control and general-purpose MCU applications. Supplied by SUPERB Automation.

Part Number Decoded — Field by Field

FieldValueMeaning
STM32G474RBT6Full Part NumberSTMicroelectronics ARM Cortex-M4F Microcontroller
STM32Product FamilySTMicroelectronics 32-bit ARM-based MCU
G4SeriesARM Cortex-M4F based MCU — G4 series

Quick Specifications

ParameterValue
ManufacturerSTMicroelectronics
Part NumberSTM32G474RBT6
CoreARM Cortex-M4F
PackageLQFP-64
Temperature Range−40°C to +85°C
Supply Voltage1.8V–3.6V

Product Overview

The STM32G474RBT6 is an STMicroelectronics ARM Cortex-M4F microcontroller in LQFP-64 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-M4F Core — Efficient Processing for Embedded Control

The ARM Cortex-M4F 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 STM32G474RBT6 supported by STM32CubeIDE?

Yes, the STM32G474RBT6 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 STM32G474RBT6 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.

STM32G474RBT6: 128 Kbytes and 128 Kbytes of RAM in 64 pins

This is the 128 Kbyte density of the 64 pin STM32G474 body. The RAM does not shrink with the flash: every member of the family carries 128 Kbytes of RAM in total, made of 96 Kbytes of SRAM with parity on the first 32 Kbytes and 32 Kbytes of CCM SRAM on the instruction and data bus. That ratio is unusual and it is the reason this part turns up in signal processing work where the buffers are large and the code is small.

The core is an Arm Cortex-M4F at 170 MHz with the CORDIC and FMAC accelerators, five 12-bit converters and the high resolution timer. The flash is a single bank at this density, so a field update cannot run read-while-write as it can on the 512 Kbyte member. Figures are from DS12288 Rev 6.

Where the memory balance sits

Flash128 Kbytes with ECC, single bank, PCROP and 1 Kbyte OTP
RAM128 Kbytes: 96 Kbytes SRAM, 32 Kbytes CCM SRAM
CoreCortex-M4F at 170 MHz, 213 DMIPS, DSP instructions
AcceleratorsCORDIC for trigonometry, FMAC for filter structures
ADCFive 12-bit converters at 0.25 microsecond, up to 42 channels
DAC and analogSeven DAC channels, seven comparators, six op amps with PGA
TimersHRTIM at 184 ps, three advanced motor control, two 32-bit
FieldbusThree FDCAN, five USART plus LPUART, four SPI, four I2C
PackageLQFP64, 10 mm by 10 mm, 0.5 mm pitch
Supply1.71 V to 3.6 V, POR, PDR and BOR on chip
Endurance10 kcycles, 30 years retention at 85 degrees C after 1 kcycle
TemperatureMinus 40 to plus 85 degrees C, 105 degree junction

Buffers, not code, are the constraint

A three channel audio front end at 48 kSamples per second, four buffers of 1 Kbyte and a decimation stage fits in 32 Kbytes of SRAM with room to spare, and the same board would not fit in a part with 32 Kbytes of flash and 8 Kbytes of RAM. The CCM block is the other half: it sits on its own bus, so a filter running from it does not contend with the DMA moving converter results into SRAM1, and the two halves of a control loop stay off each other's cache lines.

The flash budget at 128 Kbytes is where the compromise appears. A bootloader, a fieldbus stack, a motor control library and a calibration page fit, and a graphics stack or a TCP/IP stack does not. Where the application needs both the big buffers and the larger code image, the 512 Kbyte member in the same body is the step, and it does not need a different board. Our MCU cross reference page records that pairing so a change of density is quoted as a part change rather than as a new board.

Single bank flash and the update route

Without read-while-write the loader has one of two routes. It can run from RAM, copy the new image into the array and then jump to it, which needs about 1 Kbyte of loader code and a controlled power sequence. Or the product can be updated on the bench with the application stopped, which is acceptable for equipment that is serviced on site and not for a sealed unit in a ceiling.

A brownout detector and a supply that holds long enough to finish an erase page are the mechanical part of that. The vendor lists a programmable brownout reset, and the page erase time on this array is short enough that a 10 ms hold up capacitor covers it. Our NPI production launch checklist puts the update path and the power interruption test on the first article list, because a field update that fails once is a returned unit.

Questions from the purchase side

Is the RBT6 the same body as RET6? Yes, and the pins match, only the array differs, so a product can move up in density without a board change. Is the date code readable on the reel? It is, and our date code management page describes how we keep mixed date codes out of a single build so that a firmware erratum tied to one wafer lot does not appear in half the shipment.

Does the part need an external crystal? No, the internal 16 MHz RC oscillator is trimmed to one per cent and a PLL takes it to the core clock, which is enough for a control loop. A CAN bus and a USB port are the two places where the internal oscillator is normally not accepted, and those need the external crystal and, for USB, the crystal or the crystal-less mode of the family.