STM32G491RCT6
Product Specifications
STM32G491RCT6 — ARM Cortex-M4F Microcontroller by STMicroelectronics
The STM32G491RCT6 is an STMicroelectronics ARM Cortex-M4F MCU in - for Embedded control and general-purpose MCU applications. Supplied by SUPERB Automation.
Part Number Decoded — Field by Field
| Field | Value | Meaning |
|---|---|---|
| STM32G491RCT6 | Full Part Number | STMicroelectronics ARM Cortex-M4F Microcontroller |
| STM32 | Product Family | STMicroelectronics 32-bit ARM-based MCU |
| G4 | Series | ARM Cortex-M4F based MCU — G4 series |
Quick Specifications
| Parameter | Value |
|---|---|
| Manufacturer | STMicroelectronics |
| Part Number | STM32G491RCT6 |
| Core | ARM Cortex-M4F |
| Package | - |
| Temperature Range | −40°C to +85°C |
| Supply Voltage | 1.8V–3.6V |
Product Overview
The STM32G491RCT6 is an STMicroelectronics ARM Cortex-M4F 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-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 STM32G491RCT6 supported by STM32CubeIDE?
Yes, the STM32G491RCT6 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 STM32G491RCT6 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.
STM32G491RCT6: 256 Kbytes, 112 Kbytes of RAM and the math accelerators
The C in this code is 256 Kbytes of flash, R is 64 pins and T is the LQFP body at 10 mm by 10 mm. What separates the G491 from the rest of the G4 line is the pair of hardware accelerators: CORDIC for trigonometric functions and FMAC for filters, both of which run alongside the Cortex-M4F at 170 MHz. On a control loop that computes a Park transform and a pair of biquads every 50 microseconds, those two blocks are worth more than another 100 MHz of core clock.
The analog side of the same die is unusually wide for a 64 pin part: three 12-bit converters at 0.25 microseconds with up to 36 channels across the family, four 12-bit DAC channels, four rail to rail comparators and four operational amplifiers that can be configured as programmable gain stages. The SRAM is 96 Kbytes plus 16 Kbytes of CCM, 112 Kbytes in total. Figures are from DS13122 Rev 4.
The part in figures
| Core | Cortex-M4F at up to 170 MHz, 213 DMIPS, MPU and DSP instructions |
| Accelerators | CORDIC for trigonometric functions, FMAC for filters |
| Supply | 1.71 V to 3.6 V on VDD and VDDA |
| Flash | 256 Kbytes on the C density, with ECC, PCROP, securable area and 1 Kbyte OTP |
| SRAM | 96 Kbytes with parity on the first 32 Kbytes, plus 16 Kbytes of CCM SRAM |
| ADC | Three 12-bit converters at 0.25 microseconds, up to 36 channels, 16 bit by oversampling |
| DAC | Four channels, two buffered external at 1 Msample per second, two internal at 15 Msamples per second |
| Comparators | Four rail to rail, ultra fast |
| Amplifiers | Four operational amplifiers with PGA mode and all terminals accessible |
| Reference | VREFBUF with 2.048 V, 2.5 V and 2.9 V settings |
| Timers | 15, including one 32-bit and two 16-bit advanced motor control timers |
| Fieldbus | Two FDCAN controllers, USB 2.0 full speed with power delivery, five USART or UART, three SPI, three I2C |
| Memory interface | Quad SPI for external flash or RAM |
| Package | LQFP64, 10 mm by 10 mm |
| Temperature | 6 for minus 40 to plus 85 degrees C with a 105 degree junction, 3 for minus 40 to plus 125 degrees C with 130 degree junction |
What CORDIC and FMAC do for a motor loop
A field oriented control loop needs a sine and a cosine of the rotor angle at every PWM period, then two Park transforms and two inverse transforms. Done in software on an M4F at 170 MHz, the trigonometry alone can take a third of the period budget at 20 kHz. The CORDIC block computes sine, cosine, arctangent, hyperbolic functions and a square root in a fixed number of cycles and leaves the core free to run the current regulators.
The filter accelerator has its own coefficient memory and a state machine, so a biquad chain does not have to be unrolled into the core. What it does not do is manage the buffers or the sample rate, which stays in the interrupt. A loop that runs four biquads per channel at 20 kHz spends a few hundred cycles in the accelerator and the rest of the period in the regulators, and the gain shows up as jitter measured in microseconds rather than as peak throughput.
FMAC is a filter accelerator with its own memory and a state machine that reads a coefficient set and a sample buffer, multiplies and accumulates, and writes the result. A three phase current loop with four biquads and a notch runs through it while the core does the coordinate transforms. Together the two blocks turn a 170 MHz part into something that behaves like a much faster one on this exact workload, and they cost less current than raising the clock.
The trade is that the firmware has to be written to use them. A control library that was ported unchanged from an F4 will run, and it will not benefit. That is worth stating in the quotation, because the reason to buy this part over a cheaper G4 without the accelerators only exists if the software uses them. Our MCU cross reference page sets out which members of the line carry CORDIC and FMAC and which do not.
Analog front end without external parts
Four op amps with programmable gain and all terminals accessible means the shunt amplifier, the bus divider buffer and a temperature channel can be built inside the package, with the gain set by the internal resistor network rather than by four external resistors each. Four comparators cover overcurrent, overvoltage and two hardware limits, and they can be routed to the advanced timer's break input so a fault turns the gate drive off in hardware rather than in an interrupt.
The converters run at 0.25 microseconds, which is 4 Msamples per second, and oversampling takes the result to 16 bits at a lower rate for a load cell or a slow sensor. The 36 channels across the family are more than this body brings out, so the channel count on the 64 pin part is the number to check against the application, not the family headline. The ADC and DAC cross reference page lists the alternatives when the pin count and the channel count cannot both be satisfied.
Two FDCAN and a USB port on 64 pins
Two FDCAN controllers cover a drive that talks to a motion bus and to a service tool at the same time, and the USB full speed port with power delivery support covers configuration and firmware update from a laptop. Adding five USARTs, three SPI and three I2C means the pin map is the constraint: on 64 pins, not every peripheral can have its first choice of alternate function, and the revision of the circuit drawing where that is resolved is cheaper than the one made after the board is routed.
The 256 Kbyte density holds a motion application, a CANopen or EtherCAT stack and a bootloader with room for parameters. Where a second image has to sit beside the running one, the E density of the same body doubles the flash without changing the pins. Our pin to pin cross reference page records exactly that step, because the two densities share a body and a land pattern.
The quad SPI interface is the other route to capacity. An external NOR device holds a parameter log or a second image without changing the pin count, and it can be programmed in circuit at the end of the line, which is how a product carries its own calibration data through the assembly process. The kitting service page covers how that device is staged with the rest of the kit, and how the programming step is placed after the functional test rather than before it.
The two advanced timers carry complementary outputs, dead time insertion and a break input that a comparator can drive. That is what protects a three phase inverter in hardware: the comparator trips, the timer disables its outputs within a clock cycle, and the core only has to record what happened. Doing the same in software costs an interrupt latency that a 20 kHz loop cannot always afford.
Questions before the order
Does the 105 degree junction apply to the 85 degree grade? Yes, the 6 suffix is minus 40 to plus 85 degrees C ambient with a 105 degree junction, and the 3 suffix raises both to 125 and 130. On a board where the part sits beside the gate drivers, the junction is the number that binds, and the thermal resistance of the LQFP64 body at 51.1 degrees per watt is what turns dissipation into a temperature rise.
Is the 1 Kbyte OTP page enough for calibration? For a serial number and a gain table it is, and it survives every flash update, which is why it is used for factory constants rather than the last sector. Our supplier quality audit page describes how we confirm the grade, the date code and the packaging on a delivered lot before it enters a build.