A microcontroller is only as good as the toolchain around it. The reason Cortex-M alternatives gained traction is that they plug into the same Arm ecosystem most teams already run: Keil, IAR, GCC, and the usual debug probes. Artery's AT32 is no exception. This guide covers the AT32 development story and the in-stock reference parts worth keeping on the bench.
1. The toolchain you already know
- Keil MDK / IAR EWARM — commercial Arm flows with device packs for AT32.
- GCC + Eclipse / VS Code — open flows via an AT32 Work Bench or standard Cortex-M setup.
- Debug probes — J-Link, CMSIS-DAP and ST-Link-class probes all speak Cortex-M SWD.
2. Porting from STM32 to AT32
Because both are Cortex-M, a lot of code carries over — but the clock tree, Flash algorithm, device pack and peripheral registers differ. Re-target those explicitly and validate. The AT32F403ACGT7 we stock is offered as an STM32F103C8T6 alternative, so it is a natural first porting exercise.
3. Reference MCUs on the bench
| Part | Notes | Link |
|---|---|---|
| AT32F403ACGT7 | Artery AT32F4, the part under evaluation | AT32F403ACGT7 |
| STM32F103C8T6 | The F103 reference your AT32 target mirrors | STM32F103C8T6 |
| STM32F407ZGT6 | F4-class reference for toolchain checks | STM32F407ZGT6 |
| RP2040 | Dual-Cortex-M0+ dev platform for comparison | RP2040 |
| STM32H743VIT6 | High-end Cortex-M7 reference | STM32H743VIT6 |
4. A sane bring-up order
- Install the AT32 device pack and a known-good clock/blink example.
- Confirm the debug probe connects and Flash downloads.
- Port one peripheral at a time; validate clock tree and ADC before the application.
- Keep an in-stock STM32 reference on the same bench to diff behaviour.
Browse the microcontroller range. Send the part you are porting and your toolchain for a quote on the real devices.
Frequently asked questions
What toolchains support Artery AT32?
AT32 development is supported by the mainstream Arm toolchains — Keil MDK, IAR EWARM, and GCC-based flows (e.g. with an AT32 Work Bench or standard Eclipse/VS Code setups) — plus standard debug probes such as J-Link and CMSIS-DAP. Confirm the exact pack and probe support for your chosen part.
Can I port STM32 code to AT32?
Often, because both are Cortex-M and the peripheral concepts overlap, but you must re-target the device support pack, clock tree, Flash algorithm and any peripheral register differences. Treat porting as real work, not a copy-paste; budget validation time.
Do I need special hardware to start?
A standard Cortex-M debug probe (J-Link / CMSIS-DAP / ST-Link-class) and a board with the part is enough to begin. The bigger task is the software pack and a known-good blink/clock reference before layering your application.
Which MCUs do you stock for a reference bench?
We stock the Artery AT32F403ACGT7 plus in-stock STM32 F1/F4/H7 and RP2040 parts you can use as reference platforms while building out the toolchain.
About us & trademarks: JTDZ Tech (Shenzhen Jingteng Electronics Technology Co., Ltd.) is an independent distributor of electronic components. We are not an authorised distributor or representative of the manufacturers named in this article. Manufacturer and part names are used for indicative purposes only, to help identify the components discussed; all trademarks remain the property of their respective owners. Always verify specifications against the official datasheet before design-in or purchase.
Recommended next steps
If you are sourcing any of the parts mentioned in this guide, we can help you confirm stock, pricing, and lead times quickly.
- Upload your BOM — send your full parts list and receive a consolidated quote within 2 business hours.
- Browse related in-stock lines: Microcontrollers / MCUs.
- Contact our team for hard-to-find or end-of-life components.
