GigaDevice GD32

GigaDevice Semiconductor (兆易创新) sits at an unusual intersection of the MCU market: an Arm licensee that builds its own peripheral IP, packages it into chips that are footprint-compatible with STMicroelectronics' STM32 catalogue, and sells them at a 20-40% discount with a faster lead time. The company is best known outside China for its serial NOR flash business — the GD25 family is in roughly every other consumer device — but inside China the GD32 MCU portfolio has become the default 32-bit choice for cost-sensitive industrial, white-goods, and consumer designs. The company has shipped well over a billion GD32 units since the line launched in 2013.

Company and positioning

GigaDevice was founded in 2005 by Shu Qingming and Cheng Taiyi, both alumni of Spansion / Cypress. The original business was specialty memory — SPI NOR flash, then NAND, then DRAM. The MCU line started in 2013 with the GD32F103, an unmistakable clone of the STM32F103: same QFP-48 / QFP-64 / QFP-100 pinout, same peripheral register addresses, the same internal flash organisation. The 2013 part swapped the 90 nm STM32F103 process for 55 nm, which let GigaDevice push the clock from 72 MHz to 108 MHz on identical silicon area, and added a built-in serial flash controller because flash is what the company actually builds.

That formula — match the STM32 pinout and register map, swap the process, add one or two peripherals the STM32 part doesn't have, undercut the price — has produced ten generations of mainstream MCUs. The pitch is straightforward: take your existing STM32F103 firmware, change the device header, recompile, and the board works. In practice the migration is usually that simple for legacy parts, with caveats around USB enumeration, ADC sample timing, and clock-tree differences that this site documents on each family page.

The Cortex-R52 line (GD32R) marks a departure: a real-time multicore safety-island processor aimed at functional-safety automotive and industrial drives, not STM32-compatible at all.

Product family map

The mainstream volume is in GD32F1, GD32F3, GD32F4, GD32E50x — those four cover the majority of design wins.

The STM32-compatibility trick

The compatibility story is the headline feature, and the level of compatibility varies by family. Three useful tiers:

• Drop-in compatible — same package, same pinout, same peripheral base addresses, identical register layouts, identical bootloader. Most of GD32F1 → STM32F1 swaps fall here, as do many GD32F3 → STM32F4 swaps. Recompile against the GD32 device header and the firmware boots.
• Source-compatible — same peripheral semantics but different register addresses or bit layouts. The HAL or LL drivers diverge, but porting against the GigaDevice firmware library is mechanical. Most GD32F4 → STM32F4 falls here for advanced peripherals.
• Incompatible — same core, different IP block. USB OTG is the most common gotcha (GD32 uses its own USB controller, not Synopsys DWC2), as is the Ethernet MAC on some variants and the entire RCC (Reset & Clock Control) on the GD32H7.

Software ecosystem

The GD32 firmware library mirrors the structure of the STM32 Standard Peripheral Library (the pre-HAL ST library): gd32f4xx_gpio.c, gd32f4xx_usart.c, and so on. The function names are similar (gpio_init, usart_enable) but not identical to STM32 HAL — straightforward to port from the legacy STM32 SPL, more work from STM32 HAL.

GigaDevice also publishes:

• GD32 Embedded Builder — Eclipse CDT based IDE, free, bundles GCC and OpenOCD with a GD-Link debug probe driver.
• Keil MDK device family pack (DFP) and IAR EWARM device packs — official, free downloads, full register browser support.
• Segger Embedded Studio — Nordic-style support, free for non-commercial use.
• CMSIS-DAP compatible GD-Link — under $10 hardware probe; pyOCD and OpenOCD work.

The community ecosystem is smaller than STM32's but real. PlatformIO has board definitions for the popular GD32F103, GD32F303, GD32F407, GD32F450, and the W515 chips. Zephyr added GD32 support in version 3.3 (covers GD32F4 and GD32F3 with growing peripheral coverage). Rust embedded-hal crates exist for GD32F1 and GD32F3.

// GD32F4 GPIO blink — note the gigadevice firmware library style
#include "gd32f4xx.h"
 
int main(void) {
    rcu_periph_clock_enable(RCU_GPIOA);
 
    gpio_mode_set(GPIOA, GPIO_MODE_OUTPUT, GPIO_PUPD_NONE, GPIO_PIN_5);
    gpio_output_options_set(GPIOA, GPIO_OTYPE_PP, GPIO_OSPEED_50MHZ, GPIO_PIN_5);
 
    while (1) {
        gpio_bit_toggle(GPIOA, GPIO_PIN_5);
        for (volatile uint32_t i = 0; i < 1000000; i++);
    }
}

The same code on STM32 LL would be LL_GPIO_TogglePin(GPIOA, LL_GPIO_PIN_5). Semantically identical, syntactically different — a sed script handles 90% of a port.

Manufacturing, supply, and the global story

GigaDevice fabs at TSMC for most modern parts (55 nm and 40 nm) and at SMIC for legacy 110 nm parts. Packaging is mostly done in mainland China through subcontractors. The 2021-2022 STM32 shortages — when STM32F1 lead times stretched to 50+ weeks — were the single biggest boost to the GD32 line. Procurement engineers who had never considered a second source flipped boards to GD32F103 in a quarter; many never went back.

Distribution outside China runs through Mouser, Digi-Key, LCSC (the dominant Chinese distributor), and a network of regional reps. Lead times have stabilised around 8-12 weeks for mainstream parts, comparable to or better than ST's.

Cross-references

• GD32F mainstream (M3/M4/M7) — the workhorse families.
• GD32L low-power (Cortex-M23) — battery-powered IoT line.
• GD32W wireless (Cortex-M33) — Wi-Fi 4 + BLE 5.x.
• Artery AT32 — the other major Chinese STM32-alternative vendor.
• STM32 mainstream — the family being cloned.
• Cortex-M4 — the core inside most GD32F parts.
• Cortex-M7 — the core inside GD32F7 and GD32H7.
• OpenOCD — debugger setup for GD32 targets.

External links

• GigaDevice corporate site
• GD32 MCU product portal (English)
• GD32 firmware library on GitHub
• GD32 product selector
• GD32 application notes
• GD32 community forum
• Zephyr GigaDevice HAL