Firmware is an asset, and on a connected or cloned-prone product it is worth protecting. AT32, like other Cortex-M4 MCUs, provides read protection, option-byte write protection and a per-device unique ID. This guide explains what those features do and how to use them without painting yourself into a corner.
1. Layers of protection
- Read-out protection (RDP) — raises the cost of extracting firmware via the debug port. Confirm the exact levels for your part.
- Write protection — locks flash regions so they cannot be overwritten, useful for boot or calibration areas.
- Option bytes — store identity and configuration; protect them so they are not changed in the field.
- Unique ID — per-device identity for licensing and traceability.
2. A safe update plan
| Concern | Mitigation |
|---|---|
| Locked out of own device | Keep a documented unlock/update procedure |
| Brick on failed update | Use a bootloader with validation before swap |
| Cloning | RDP + unique ID + server check |
| Lost calibration | Protect option bytes, back up source |
3. What protection is not
These features slow down cloning and casual extraction; they are not a substitute for secure boot or cryptographic attestation on a determined adversary. Design the scheme, then validate it on samples. We carry the AT32F403ACGT7 and can quote AT32 parts for security-sensitive builds. For the broader positioning, see the family overview and AT32 vs GD32 comparison.
Frequently asked questions
What read protection does AT32 offer?
Like most Cortex-M parts, AT32 supports flash read-out protection levels that make it harder to extract firmware through the debug interface. The exact levels and their behaviour vary by part, so confirm against the specific datasheet and reference manual.
How do I protect configuration stored in option bytes?
Use the write-protection and option-byte features to lock regions or store calibration and identity data. Plan a safe update path so that protection does not block your own field firmware updates.
What is a unique device ID used for?
A per-chip unique ID supports licensing, traceability and anti-cloning. It is not a security boundary by itself, but combined with read protection it raises the bar for casual cloning.
Do you supply AT32 for security-sensitive products?
We stock Artery AT32 MCUs as an independent distributor. Send the exact part and quantity; we recommend validating the protection scheme on samples before volume.
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: Power Management ICs · Microcontrollers / MCUs · Memory / Logic Devices.
- Contact our team for hard-to-find or end-of-life components.
