Every quarter someone asks us to substitute a microcontroller to cut BOM cost or to get out of an allocation. Both are reasonable, and both frequently get approved on the first line of the comparison sheet. This is the checklist we run with customers before any substitution is quoted, written as it applies to the AT32 family and to the alternatives engineers usually look at.
Name the problem first
Availability and unit cost are different projects with different risk profiles. Availability has a hard deadline and justifies a fast decision. Unit cost has a softer case and deserves a slower one. Naming the driver makes every later step easier.
The six-line comparison
| Line | What to price | Commonly forgotten |
|---|---|---|
| Silicon unit price | At your real volume and package | Price at the volume you will ship, not the last one |
| Board area | Footprint plus keep-out plus routing | The area you can no longer use |
| Assembly | Land pattern, pitch, test | X-ray or rework cost of a QFN |
| Support parts | What the new part removes or adds | External EEPROM, crystal, bridge ICs |
| Engineering | Porting, bench comparison, re-spin | The week of work and the re-spin if the board must change |
| Risk | Second source and continuity | What a change notice costs you |
On the AT32 side, an entry-tier alternative such as AT32F421K8U7 or AT32F423RCT7 often wins the first line and loses the fifth. A mainstream alternative such as AT32F413RBT7 or AT32F415CCT7 frequently wins on the third line by letting you delete a chip, which is the substitution that pays back fastest.
Board-level checks before you quote
- Package and land pattern: same package code and same land pattern?
- Pinout: are the pins you actually use a subset of the new part's?
- Boot and reset: does the boot strapping behave the same at power-on?
- Clock: internal oscillator, external crystal, or both — and what accuracy does the serial interface need?
- Flash and RAM: enough now, and enough after the next two feature releases?
Any "no" on the first three implies a board change, which implies a re-spin. Price that before you approve anything.
The second-source question
A part with exactly one source and a different footprint is not a saving. Ask three questions of any substitution: can a second source supply the same package at the same volume, is the pinout the same, and what is the planned discontinuation position. If the answers are unclear, the substitution's risk cost is higher than its unit saving.
Where substitution pays back fastest
In our experience the order of payback is:
- Replacing an external part your MCU can absorb — an EEPROM, a bridge IC, a small CPLD. Fastest, no re-spin if the pins allow.
- Consolidating onto a wireless part and deleting the split MCU plus radio. Fast, plus a firmware consolidation.
- Moving one tier down within the AT32 family. Moderate, needs firmware work but rarely a board change.
- Cross-family substitution with a different pinout. Slowest, and the re-spin dominates.
Related reading
Microcontrollers and MCUs · AT32F435RGT7 · AT32F425C8T7
Frequently asked questions
What is the most common hidden cost when substituting an MCU?
The board. Teams quote the new part, then discover the land pattern differs, the boot pins differ, or the pinout means a re-route. A re-spin costs tooling and time, and if the product is already in production it costs a line-down event. Confirm package, pinout and boot behaviour before you quote.
Why do BOM comparisons go wrong?
Because they compare part prices and stop. A defensible comparison covers unit price, board area, assembly, second-source position, engineering time and the risk of a re-spin. Projects that win the internal argument are the ones that show all six lines.
Should I always check whether a cheaper part is second-sourceable?
Yes, and treat it as a design requirement rather than a procurement afterthought. A cheap part with one source and a different footprint is not cheaper once you count the risk it carries into a product line that must ship for years.
How much engineering time should I budget for a substitution?
For a like-for-like part with the same package and a familiar peripheral set, a few days. For a different package, a different pinout or an unfamiliar SDK, a week plus a bench comparison, and more if the design needs qualification. Budget it up front and the business case stops looking so attractive that nobody checks it.
What is the question I should ask before starting a substitution?
Which problem am I solving: availability or unit cost? Those two have different timelines, different approval paths and different risks. Naming it first makes the rest of the decision much faster.
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.
