STM32 Replacement: The GD32 Cross-Selection Master Guide
What drops in vs what needs design-in — GD32 mapped to STM32 on one page
Facing STM32 shortages or cost pressure, GigaDevice GD32 is a common second source. But "can I just swap it" depends on the part: a few are footprint+register compatible (near drop-in), most are functional alternatives needing firmware/timing re-validation. Below maps JLink-distributed GD32 parts to STM32, each linking to its cross-reference page.
① Footprint-compatible, near drop-in
Same package and largely register-compatible; on porting mainly recheck clock, Flash wait-states, and a few HAL settings.
Maps to STM32F103, the most common pin-compatible swap (108MHz core).
② Functional alternatives, design-in
Packages/pinout broadly align, but device ID, clock tree, and peripheral registers differ — recompile with the GD32 library and re-validate.
Maps to STM32F407 (high-perf M4; also covers STM32F405).
Maps to STM32F207 (both have an Ethernet MAC).
Maps to STM32F205 (USB, dual CAN).
Positioned against STM32F0 value line (note M3 vs M0 core).
Maps to STM32L0 ultra-low-power (M23 vs M0+ core).
Maps to STM32F429/F437 high-end M4 (240MHz).
⚠️ Naming trap: GD32F303 maps to STM32F103
Do not be misled by the number: the GD32F303 is Cortex-M4 but carries the STM32F103 (GD32F103) peripheral set — it replaces the STM32F103, NOT the STM32F3xx.
Cortex-M4 performance, but maps to STM32F103 (not STM32F303).
Cross-references
Related guides
Frequently asked questions
Can GD32 directly replace STM32? ▾
It depends on the part. GD32F103↔STM32F103 is pin-compatible and near drop-in (but the core runs to 108MHz — recheck clock and Flash wait-states); most others are functional alternatives — packages align but recompile with the GD32 library and re-validate timing.
Which STM32 does the GD32F303 correspond to? ▾
It corresponds to the STM32F103, not the STM32F303. Despite being Cortex-M4, the GD32F303 retains the STM32F103/GD32F103 peripheral set, so it is not a drop-in for STM32F3xx.
What changes when switching from STM32? ▾
Typically: recompile with the GD32 firmware library, verify clock-tree/PLL startup and Flash wait-states, update device-ID checks, and validate peripheral timing on hardware. Pin-compatible parts (e.g. GD32F103) keep the PCB; for functional alternatives, compare the pinout per package.
Not sure which part fits?
Tell us your application and constraints — our engineers will recommend a part and quote stock, pricing, and lead time.
Request a Quote