

There is an MCU part number in the alternate column of your BOM. Nobody has built a board with it, nobody has run it through qualification, and nobody knows whether it would boot. At many companies, that column is the entire second-source strategy, and it works until the day it has to.
When that day comes, the replacement has to come from somewhere, and there are fewer options than you might think. Omdia put Infineon at the top of the global MCU market in 2025 with a 23.2 percent share, up from 21.4 percent the year before, in a market that shrank slightly. Behind Infineon are NXP, Renesas, ST, and Microchip, and the five together account for roughly 80 percent of an MCU market worth about $22 billion. TechInsights data put Infineon's automotive MCU share at 36.0 percent.
Odds are, the part in your MCU alternate column comes from one of those five companies.
The situation gets worse when you learn where the advanced parts are being built. Each of the five MCU leaders keeps its own mix of internal fabs, but the advanced product families often rely on external foundries. Infineon builds its AURIX TC4x family on TSMC’s 28 nm process. NXP has long used TSMC for advanced S32 processors, and its S32N5 and S32N7 central-compute families both use TSMC’s 5 nm process.
Renesas builds its flagship RA8 family on TSMC’s 22 nm ultra-low-leakage process. ST co-developed its 18 nm process with embedded phase-change memory alongside Samsung Foundry, with the first product on it, the STM32V8, built both in ST’s Crolles fab and in partnership with Samsung. ST is also adding regional manufacturing redundancy for customers in China: its locally made STM32s reached volume production this year using 40 nm wafers that are produced by Hua Hong.
Packaging adds another layer of correlated risk. TrendForce shows ASE with a 44.6 percent share of the top ten outsourced semiconductor assembly and test (OSAT) firms’ 2024 revenue, with ASE and Amkor together accounting for nearly 60 percent. That concentration means a supplier change can leave assembly-test exposure largely unchanged when alternates depend on the same OSAT ecosystem or manufacturing region.
Add it up, and a second source can change the supplier without changing the foundry, the packaging house, or the region. The real test is whether the alternate moves any of those.
For sourcing teams running supplier diversification programs, this matters: approving two MCU vendors from the same foundry node does not diversify wafer supply risk. A meaningful second source changes the foundry or the manufacturing region, not just the vendor name on the purchase order.
On September 30, 2025, the Dutch government invoked a 1952 law it had never used before and essentially took control of Nexperia. It’s a good example of how quickly a concentrated semiconductor supply chain can become a production problem. The affected components were mostly ordinary transistors and diodes, not MCUs, but the downstream effects were substantial.
When the intervention and related restrictions on the company’s Chinese operations disrupted shipments, Honda estimated an impact of roughly $969 million and cut North American production by about 110,000 vehicles. Bosch reduced hours at electronic control unit (ECU) plants in Germany and Portugal.
The lesson for MCUs is the dependency map behind the top vendors. Suppliers that appear independent can still rely on the same wafer fabs, assembly-test operations, or manufacturing regions, so if a shared upstream node fails, several approved sources can tighten simultaneously. For MCUs – where firmware migration and qualification can take months – identifying those common dependencies before a disruption is part of a real second-source strategy.
Companies that had qualified alternatives already on their AVL and in their ERP were able to redirect purchase orders within days. Companies that hadn't done that work spent those days starting it.

A cross-reference table tells you whether two parts share the footprint. It doesn't tell you whether they share a qualification. The gap between those two things is measured in months and budget.
Within the same vendor family, a swap usually involves modest firmware changes and a target requalification of what changed. The engineering lift is manageable and the timeline is shorter. Cross-vendor moves carry a larger porting effort and typically trigger a more extensive requalification process, because more has changed: the silicon, the peripheral set, and often the assembly or test flow.
In automotive, the hurdle is higher and the timeline becomes a procurement variable. AEC-Q100 requalification requirements depend on the scope of the change, and standing up a genuinely qualified alternative is a safety-critical application can take six to eighteen months. Functional safety adds another layer: an ASIL-rated replacement requires updated safety documentation – including failure modes, effects, and diagnostic analysis (FMEDA) – and the system-level safety case has to be revalidated for the new device. That revalidation is a gate that determines when procurement can place a production purchase order.
A cross-reference can confirm the footprint. Procurement needs to know which one it has before committing supply against an alternative.
Not all alternates require the same qualification work, and the STM32-compatible ecosystem offers a useful illustration of how much that work can vary.
Supplier certification is a meaningful first filter for procurement. GigaDevice holds ISO 26262 ASIL D development-process certification and its GD32F5xx and GD32G5xx software test libraries received TUV Rheinland IEC 61508 certification for SIL 2 and SIL3 applications in 2025. That level of foundational safety work is important when evaluating whether a supplier is a realistic candidate for safety-critical STM32 replacement. It does not eliminate the qualification requirement, but it signals the supplier has cleared a significant bar before your engineering team starts part-by-part verification. Other suppliers in the ecosystem are at different points on the readiness curve.
Before adding any STM32-compatible alternate to your AVL, confirm its regulatory status matches your design’s certification requirements. That determines the scope of the qualification work ahead, and therefore the timeline and cost procurement needs to plan against it before committing to a second source.
Before a second source earns a place on the approved BOM, a genuine sign-off is required from both engineering and procurement.
Engineering verifies:
Procurement owns:
Before the engineering qualification work starts, you need to know what’s actually available to qualify. Octopart shows you lifecycle status, authorized distributor stock, lead times, and alternative parts across 670+ distributors for every MCU on your BOM.