CAN vs CAN-FD and MCU Selection: Which GD32 Parts Actually Integrate CAN-FD
CAN-FD grows the per-frame payload from 8 to 64 bytes and speeds up the data phase, but it does not transparently coexist with classical CAN. This guide clarifies the differences and compatibility reality, verifies per-part which GD32 actually integrate CAN-FD (GD32G5/H7/F5 do; GD32L235 is classical CAN only), and shows how to pick by core and CAN-FD channel count.
What CAN-FD adds over classical CAN
CAN-FD (Flexible Data-rate; Bosch 2012, ISO 11898-1:2015) adds two main things over classical CAN: first, the per-frame payload grows from 8 bytes to up to 64 bytes; second, a dual bit rate — the arbitration phase stays at the classical ≤1 Mbit/s (for bus-arbitration compatibility), but the data phase can switch to a higher rate via the BRS bit (commonly up to about 5 Mbit/s in practice; reaching 8 Mbit/s needs a CAN SIC transceiver). It also has a stronger CRC (17/21-bit). So on the same network, CAN-FD moves more data per frame and faster — ideal for UDS diagnostics, bootloader/OTA firmware updates and sensor-data aggregation.
⚠️ Compatibility: classical CAN and CAN-FD don’t transparently mix
A reality most articles skip but it matters: classical CAN and CAN-FD do not transparently coexist. When a CAN-FD frame is sent, a controller that only supports classical CAN produces an error frame after the FDF bit (disturbing the whole bus), unless that legacy controller is “CAN-FD tolerant” (recognizes and ignores FD frames). So a bus must be either all CAN-FD or have the FD nodes fall back to classical mode — you cannot mix a classical-only legacy node into the same segment. To connect an old segment, a gateway / bridge is the usual solution.
Physical layer: same bus, but the transceiver must match
Good news: the physical layer needs no major change. CAN-FD uses the same 2-wire differential bus, the same ISO 11898-2, and the same 120Ω termination at both ends. But note: to run the fast data phase, the transceiver (PHY) must be rated for that rate — e.g. a CAN-FD transceiver guaranteed to 5 Mbit/s, or a SIC transceiver for 8 Mbit/s; a 1 Mbit/s-only legacy transceiver is not adequate for the fast phase. In other words, the MCU’s integrated CAN-FD controller is only half — the external transceiver must be chosen for the matching data rate.
Which GD32 integrate CAN-FD (verified per part)
Here is the crux — don’t take a vague “GD32 supports CAN-FD”; verify per part: the parts with CAN-FD are the high-performance lines — GD32G5 (e.g. GD32G553, Cortex-M33 @216MHz) and GD32H7 (Cortex-M7 @600MHz) each with 3× CAN-FD; GD32F5 (M33 @280MHz) and GD32F503/505 each with 2× CAN-FD. Classical CAN 2.0B only (NOT CAN-FD): the GD32F1 / F3 / F4 families, and — a specific caution — the GD32L235 (Cortex-M23, with only 1× classical CAN 2.0B, not CAN-FD). When selecting, always read whether the datasheet’s CAN field says “CAN-FD” or “CAN 2.0B”; don’t guess from the series name.
How to choose (payload/bandwidth + core + CAN-FD channels)
When to use CAN-FD: when you need a larger per-frame payload (64B — good for UDS diagnostics, bootloader/OTA, sensor aggregation) or more bandwidth; automotive ECUs and industrial gateways upgrading from CAN should prefer CAN-FD (same physical layer, incremental migration). Purely low-speed nodes where 8 bytes suffice and cost matters can stay on classical CAN. Pick a GD32 on two axes — core class + CAN-FD channel count: need 3× CAN-FD + high compute (multi-segment gateway, motor + comms) → GD32H7 (M7@600MHz) or GD32G553 (M33@216MHz, with HRTimer, real-time-control oriented); need 2× → GD32F5 or GD32F503/505; need only classical CAN / low power → GD32L235 (M23) or GD32F4. Don’t forget the external transceiver must match the data rate (5 Mbit/s class, or SIC for 8 Mbit/s) and the 120Ω termination. JLink Technology is an authorized GigaDevice distributor supplying the full GD32 line; tell us your CAN-FD channel count, core and volumes and we will help with selection and reply with samples, datasheets and pricing.
Products mentioned
GD32G553 Cortex-M33 Digital-Power MCU
The GD32G553 is a high-performance Arm Cortex-M33 (with DSP and single-precision FPU) MCU in GigaDevice’s GD32G5 series at 216MHz, with 256~512KB dual-bank flash and 128KB SRAM (incl. TCMRAM). It integrates four 12-bit ADCs (up to 5.3MSPS), four DACs, eight high-speed comparators, three CAN-FD, a 16-channel high-resolution timer (145ps), and TMU/FAC/FFT math accelerators, with secure boot/AES and IEC 61508 SIL2 — for digital power, EV charging, energy-storage inverters, and servo motor control.
GD32L235 Cortex-M23 Ultra-Low-Power MCU
The GD32L235 is an ultra-low-power 32-bit Arm Cortex-M23 MCU from GigaDevice at 64MHz, with 64~128KB flash / 12~24KB SRAM. Power is very low: ~66µA/MHz run, 1.8µA deep-sleep (<2µs wake), 0.26µA standby, with low-power LPUART and LPTIMER for always-on tasks. It integrates a 12-bit ADC, DAC and two comparators, USB 2.0 FS and CAN 2.0, in LQFP/QFN and WLCSP25. Versus the cataloged GD32L233, the L235 adds CAN and richer peripherals — for smart locks, metering, wearables, and battery management.
GD32F407 Arm Cortex-M4 High-Performance MCU
The GD32F407 is a high-performance 32-bit MCU from GigaDevice with an Arm Cortex-M4 core (FPU/DSP) at 168MHz, up to 1MB Flash and 192KB SRAM, integrating USB OTG (FS+HS), 10/100 Ethernet MAC, and CAN. With packages aligned to the STM32F407 (LQFP100/144), it is commonly used as an STM32F407-class alternative.
Need these components or design help?
JLink Technology provides parts, datasheets, and engineering support.
Request a Quote