Microcontrollers
An exact MCU match starts with the complete ordering code. Send your approved device, required quantity and production date for a supply review through our China inventory and supply network.
Start with your approved part numbers
For production, repair or an established design, preserve the MCU identity already approved by your engineering team. Family names such as STM32 or RX72M are a useful starting point, but can cover different memory capacities, packages and operating grades.
We focus the commercial review on the exact device and available lot. A family resemblance is not an approval to substitute another MCU or a different ordering suffix.
Ordering details that matter
Keep device identity and offered-lot details separate.
The most useful RFQ starts with an approved full manufacturer part number, then adds your commercial and acceptance requirements. Use the checks below to make those requirements clear.
| Check | Why it matters | What to send |
|---|---|---|
| Device and memory option | Code Flash and RAM options may vary within a family. | Provide the full MPN and your approved datasheet or BOM reference. |
| Package and operating grade | Pin count, footprint and temperature options can differ. | Retain all package and grade characters; do not shorten to a family name. |
| Programming status | Factory device identity and your firmware are separate acceptance questions. | State any blank-device, programming, security or firmware restrictions. |
| Carrier and date code | A manufacturer tray option does not describe the condition of a particular lot. | Specify packaging, mixed-date-code and partial-tray acceptance. |
Lot evidence and inspection
Define what needs to be verified before the order.
Before accepting an MCU lot, agree the documents, marking and packaging checks you need. Programming, firmware verification, security configuration and functional testing require a separately defined method and suitable fixtures.
A visual inspection report does not demonstrate that the device contains your firmware or will operate correctly in your application. Engineering approval remains tied to the exact device and your design.
Inspection methods & laboratoriesSource documentation & traceability
Manufacturer references
Use the original technical documents to check device identity. These links are not an indication of authorization or current stock.
ST STM32 microcontroller familiesUse the family information to locate the exact device documentation.Manufacturer website · opens a new tabRenesas RX72M familyReview the relevant device and package option before purchase.Manufacturer website · opens a new tabReferences reviewed 2026-10-14.
Find the right product information
Browse related procurement guidance or send an unlisted requirement.
Use these related pages to narrow the device identity and the evidence needed for your order. If your exact part is not listed, send the complete MPN and quantity. We review available stock and additional supply options against your requirements.
Pricing, lot details and delivery are confirmed in the quotation. For multiple parts, send your BOM with one ordering code per line.
Before you enquire
Can you quote an alternative MCU?
You may include engineering-approved alternatives as separate BOM lines. We will distinguish them in the quotation; a similar family or package is not treated as interchangeable.
Does inspection include programming my firmware?
Only if that work is explicitly agreed with the laboratory and included in the scope. Ordinary visual or identity checks do not include firmware programming.
Bring us your exact requirement.
Full part number. Quantity. Required date.
We will review the supply options and the evidence your order needs.