An MCU is only as useful as the links it can hold. AT32 devices pack a broad set of interfaces — USB, CAN, CAN-FD, multiple USARTs, RS485 via USART, I2C and SPI — which is why they fit everything from a sensor node to a factory cabinet. This guide maps each interface to its job and the mistakes we see most.
1. Interface map
| Interface | Typical use | Design note |
|---|---|---|
| USB FS/HS | PC config, host, streaming | Match PHY option to cert plan |
| CAN 2.0B | Vehicle / machine bus | Correct termination and bit timing |
| CAN-FD | Higher-payload modern bus | Shared PHY with classic CAN |
| RS485 | Long-distance industrial serial | Termination + TVS + isolation |
| I2C | On-board sensors, EEPROM | Pull-ups, address conflicts |
| SPI | Flash, display, ADC | Clock polarity and CS routing |
2. Building a robust bus
- Terminate CAN and RS485 at both ends with the specified resistor; unterminated buses misbehave under load.
- Protect with TVS diodes and, where grounds differ, isolation between the transceiver and the MCU.
- Clock the bus with a timing budget that holds across temperature and cable length.
- Detect bus-off and error states in firmware so a fault does not silently corrupt data.
3. On-board peripherals
I2C and SPI are for the parts around the MCU — the ADC from the analog front-end guide, external Flash, a display, or a sensor cluster. Keep SPI clock lines short, give each device its own chip-select, and confirm I2C pull-ups suit your bus capacitance.
We carry the AT32F403ACGT7 and can bundle transceivers with it. The AT32F402/F405 USB + CAN-FD guide goes deeper on the high-speed links, and the family overview sets the wider context.
Frequently asked questions
Which AT32 interfaces suit industrial communication?
For industrial links, CAN / CAN-FD and RS485 are the workhorses because they tolerate noise and long cables. USB is for configuration and PC connection, while I2C and SPI are for on-board peripherals such as sensors, memories and displays.
CAN-FD or classic CAN — which should I design for?
Use classic CAN if your network is already CAN 2.0B and the data rate is enough. Choose CAN-FD when you need larger frames or higher data-phase bit rate, for example in newer vehicles, robots or battery systems. The physical layer is largely shared.
How do I protect RS485 and CAN on the bench?
Use a proper transceiver, terminate the bus correctly, add TVS protection, and keep the MCU side isolated where ground loops are possible. Most field failures come from termination, grounding or missing protection, not the MCU.
Do you supply AT32 with the needed transceivers?
We stock Artery AT32 MCUs as an independent distributor and can bundle CAN/RS485 transceivers and protection parts in the same BOM. Send the full list for a consolidated quote.
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: Interface Chips / RF Chips.
- Contact our team for hard-to-find or end-of-life components.
