Flight Controller MCU
STM32H743 vs STM32G474 for UAV Controllers: Choosing Compute or Motor-Control Integration
STM32H743 and STM32G474 solve different problems. The H743 is the stronger choice for a feature-rich central flight computer; the G474 is often the cleaner choice for deterministic motor-control, power-conversion, or compact control nodes. Choosing by clock speed alone can produce a more expensive board without improving the actual aircraft.
Side-by-side design view
| Criterion | STM32H743 | STM32G474 |
|---|---|---|
| Design focus | High-performance central controller | Motor control and mixed-signal control |
| CPU | Arm Cortex-M7, up to 480 MHz | Arm Cortex-M4, up to 170 MHz |
| Memory profile | Up to 2 MB Flash and 1 MB RAM in the family | Up to 512 KB Flash in common G474 variants |
| Notable strengths | Cache, TCM, broad connectivity, large software headroom | High-resolution timer, analog integration, math accelerators |
| Typical UAV role | Autopilot, payload controller, advanced flight computer | ESC, power node, actuator controller, compact FC |
Start with the UAV architecture
A central flight computer may run attitude estimation, navigation, mission logic, telemetry, storage, safety supervision, and multiple buses at once. In that architecture, memory bandwidth and software headroom matter as much as timer count. STM32H743 gives the team room for larger filters, richer logging, Ethernet or USB functions, and future middleware without immediately redesigning the hardware.
A motor-control node has a different priority. Its critical path is PWM generation, current and voltage acquisition, protection timing, and a control loop that behaves consistently under electrical noise. STM32G474 combines a 170 MHz Cortex-M4 with high-resolution timing and strong analog resources, making it attractive for ESC and power-control boards where determinism is more important than a large application layer.
When STM32H743 is the better fit
Use the H743 when one processor must aggregate several IMUs, GNSS, CAN-FD peripherals, payload interfaces, high-rate logs, and computationally heavier navigation. Its Cortex-M7, cache, TCM, and larger RAM budget give firmware teams more freedom to isolate real-time work from communication and storage tasks.
The trade-off is system complexity. Cache coherency, DMA placement, external-memory routing, power rails, thermal behavior, and a larger package can increase validation effort. A high-end MCU does not fix poor scheduling or noisy sensor layout; it simply gives the design more resources.
When STM32G474 is the better fit
Use the G474 for a dedicated ESC, power-conversion controller, actuator module, or compact aircraft controller whose workload is dominated by control loops. Its high-resolution timer and analog peripherals can reduce the need for external support devices and keep current-sense and PWM timing closely coordinated.
The G474 is not a drop-in replacement for an H743. It has a different core, memory map, peripheral set, and package strategy. Treat migration as a new hardware and firmware validation project, not as a BOM substitution.
Procurement and validation checklist
Freeze the complete manufacturer part number, not only the family name. Confirm temperature grade, package, tray or reel suffix, flash density, pin-compatible alternatives, lifecycle status, and the precise quantity needed for prototypes and production.
Before release, run CPU-load margin, worst-case interrupt latency, DMA contention, sensor-bus saturation, boot and brownout recovery, motor-noise immunity, and thermal tests. The correct MCU is the one that passes the aircraft-level test plan with adequate margin.
Related UAV chip pages
Need a BOM review or quotation?
Send the exact part numbers, package, quantity, target application, and required date. We will reply with availability for review—without presenting unverified stock claims.
Submit a UAV chip RFQFrequently asked questions
Is STM32H743 always better for a drone?
No. It provides more compute and memory, but a dedicated ESC or control node may benefit more from STM32G474 timing and analog integration.
Can the two MCUs share one firmware target?
Not without a deliberate port. Core behavior, memory, peripherals, pinout, and clock configuration differ.
Which part number should purchasing quote?
Quote the complete orderable suffix approved by engineering, including package and temperature grade.
Official technical references
Specifications must be confirmed in the latest manufacturer datasheet for the exact orderable suffix.