Back to Knowledge CenterTechnical guide

STM32F103C8T6 Alternatives: GD32 and APM32

Compare STM32F103C8T6 with STM32F103CBT6, GD32F103C8T6, and APM32F103CBT6. Check pin assignments, clock setup, memory, and lot details before switching.

Published · Updated · By KETA Sourcing Team

Technical guide

Start with STM32F103CBT6 if the only reason to replace STM32F103C8T6 is a need for more program Flash. Evaluate GD32F103C8T6 if the application fits the existing Flash and SRAM budget and you can qualify the board and rebuild the firmware. If the project needs more Flash and can support a cross-vendor port, evaluate APM32F103CBT6 against a confirmed Geehy silicon version.

Compare the exact ordering codes

Specification STM32F103C8T6 STM32F103CBT6 GD32F103C8T6 APM32F103CBT6
Core Arm Cortex-M3 Arm Cortex-M3 Arm Cortex-M3 Arm Cortex-M3
Maximum core clock 72 MHz 72 MHz 108 MHz 96 MHz
Flash 64 KB 128 KB 64 KB 128 KB (D and E)
SRAM 20 KB 20 KB 20 KB 20 KB (D), 36 KB (E)
Package / pins LQFP48 / 48 LQFP48 / 48 LQFP48 / 48 LQFP48 / 48
Main operating voltage (VDD) 2.0–3.6 V 2.0–3.6 V 2.6–3.6 V 2.0–3.6 V
Operating temperature (ambient) −40 to +85 °C −40 to +85 °C −40 to +85 °C −40 to +85 °C
GPIO count 37 37 37 37
USB 1 full-speed device interface 1 full-speed device interface 1 full-speed device interface 1 usable full-speed device interface at a time
CAN controllers 1 1 1 1 (D), 2 (E)
ADC external channels / resolution 10 / 12-bit 10 / 12-bit 10 / 12-bit 10 / 12-bit
Package pin comparison vs. STM32F103C8T6 Baseline pin-compatible package; firmware changes may be required pin-compatible package; firmware changes may be required pin-compatible package; firmware changes may be required (D and E)

The package comparison uses the vendors’ numbered pin diagrams. Compare the alternate functions and electrical limits for the signals your board actually uses, including oscillator pins, boot straps, and debug. Check the USB and ADC electrical conditions separately from the main supply range. ST datasheet, GigaDevice datasheet, Geehy D datasheet, Geehy E datasheet.

FlashSTM32F103C8T664 KBSTM32F103CBT6128 KBGD32F103C8T664 KBAPM32F103CBT6 · D128 KBAPM32F103CBT6 · E128 KBSRAMSTM32F103C8T620 KBSTM32F103CBT620 KBGD32F103C8T620 KBAPM32F103CBT6 · D20 KBAPM32F103CBT6 · E36 KBMaximum core clockSTM32F103C8T672 MHzSTM32F103CBT672 MHzGD32F103C8T6108 MHzAPM32F103CBT6 · D96 MHzAPM32F103CBT6 · E96 MHz
Memory and clock comparison. The amber rows show the D and E silicon versions of the Geehy ordering code separately. The maximum clock is a device limit.

GD32F103C8T6: verify the clock and peripheral setup

GD32F103C8T6 shares the core family, 64 KB Flash, 20 KB SRAM, and LQFP48 pin count of STM32F103C8T6. Start with the board’s minimum supply during startup and under load. GigaDevice specifies a 2.6 V minimum for VDD. A board designed to run below that threshold needs its supply requirements resolved before firmware testing. GigaDevice datasheet.

Recalculate the PLL and bus prescalers for the target. The 108 MHz maximum core clock is a ceiling. Choose a clock plan that also meets the limits for the peripherals in use. USB needs a 48 MHz peripheral clock. Verify the clock source and divider, then test enumeration, suspend, and resume on the actual host and board. For CAN, verify bit timing with the target peripheral clock and exercise traffic with the installed transceiver. GigaDevice datasheet, GigaDevice user manual.

ST specifies two Flash wait states at 72 MHz. The GD32F103xx datasheet describes zero-wait-state Flash access at 108 MHz, and the GigaDevice user manual documents a separate Flash fetch wait-state control. Confirm the Flash wait-state setting for your target clock and GD32F103C8T6 silicon revision in the GigaDevice user manual, then verify the setting on the target board before qualifying the build. Measure interrupt latency, timer output, bit-banged interfaces, and software delays on the target. Capture the same signals on the original board so you have a timing baseline. ST reference manual, GigaDevice datasheet, GigaDevice user manual.

Check the target’s register definitions, interrupt assignments, DMA requests, and pin remaps for each enabled peripheral. Keep the original ST workarounds documented and decide whether the new target needs its own. Ask your supplier or a GigaDevice field application engineer (FAE) for the latest errata sheet that applies to the specific lot you plan to use. For a worked example of organizing a clock and peripheral review, see the STM32F405RGT6 migration assessment. GigaDevice user manual, ST errata.

APM32F103CBT6: a candidate when the firmware needs more Flash

APM32F103CBT6 has 128 KB Flash, matching STM32F103CBT6 and increasing the program space available compared with the 64 KB of STM32F103C8T6. Geehy lists the same complete ordering code in the D and E datasheets. The D version has 20 KB SRAM and one CAN controller. The E version has 36 KB SRAM and two CAN controllers. Before placing an order, confirm in writing whether the lot uses D or E silicon and how to identify that version on the packaging or labels. Tie your qualification evidence to the confirmed version. Geehy D datasheet, Geehy E datasheet.

Use the target linker map to confirm that application code, bootloader, and reserved update or settings space all fit. If you plan to qualify both versions, size the common build to the lower SRAM capacity or qualify a build for each version. Test programming, option bytes, firmware updates, and peripheral behavior on the version supplied. For example, Geehy flags a conflict on E1 when PB5 is remapped for SPI1 and the I2C1 clock is enabled. Test that configuration if your design uses it. Geehy user manual, Geehy errata.

Migration checklist

  • Map every used board net to the candidate pin table. Record its reset state, configured function, voltage limits, and any remap. Check the clock circuit, boot straps, analog supply, and programming connector.
  • Build a target-specific image. Review the startup file, vector table, linker regions, peripheral clock tree, and programmer settings. Confirm that the production fixture can erase, program, verify, and reset the device.
  • Compare the original and candidate boards at startup, across the intended operating range, and under the expected workload. Exercise reset and recovery, sleep and wake, communications, ADC sampling, and updates where used.
  • Record the board revision, approved ordering code, silicon revision, firmware build, and acceptance criteria. Repeat the affected tests when the incoming silicon revision changes.
  1. 1PinsMap the board nets.Check reset states,limits and remaps.
  2. 2Clock and bootCheck the oscillatorand boot straps.Verify the clock plan.
  3. 3Flash and SRAMReview the linker mapfor application, bootand update space.
  4. 4Firmware and I/ORebuild for the target.Review clocks, interrupts,registers and DMA.
  5. 5Pilot validationTest program, resetand recovery.Record build and lot.
Migration review sequence. Apply the checklist to the actual board and firmware. Preserve the orderable part, silicon revision and test evidence with the approved build.

Procurement: preserve lot traceability

Put the complete ordering code on the purchase order. Ask for the date code, lot identifier, packaging format, and legible photos of the package markings and outer label before approving a sample. At receipt, reconcile the labels with the purchase order and keep the inspected lot tied to its programming and bench results.

Treat missing traceability, conflicting markings, or mixed lots as reasons to hold the material for inspection. Ask for samples from the lot that will ship and agree in advance how discrepancies will be handled. Use the small-batch component QC process and anti-counterfeit guidance to define the receiving checks.

FAQ

Which part should I try first if only Flash is tight?

Evaluate STM32F103CBT6 first. ST specifies 128 KB Flash and the same 20 KB SRAM as STM32F103C8T6. Review the linker layout and confirm your programming and update flow. ST datasheet.

Can I reuse the compiled STM32 firmware on the other brands?

Plan to rebuild it for the target. Audit startup and clock setup, register access, interrupts, the bootloader, and programmer support. Use the original firmware’s behavior as the baseline for the port.

Does the Geehy ordering code tell me how much SRAM I will receive?

Ask for the silicon version. The D and E datasheets list the same APM32F103CBT6 code and specify different SRAM capacities. Tie the version you qualify to the lot you receive. Geehy D datasheet, Geehy E datasheet.

Parts mentioned in this article

Request a quote
Send RFQUpload BOM
WhatsApp