ST and NXP MCU Surplus: Ordering Codes, Programming and Lot Records

For STM32, NXP and other MCU surplus, include package, lot and programming status alongside exact part codes and counts. Explicitly identify unknown programming or protection instead of assuming unused condition.

Separate families, devices and boards

STM32, NXP i.MX RT and S32K describe different portfolios. Check actual codes against manufacturer information and labels. Separate loose ICs, modules and development boards; a board name is not a component ordering code.

Keep suffixes and programming history

Copy capacity, package, grade and packing suffixes from labels. Disclose programming, mounting, read protection and unknown lock state. Mark uncertainty and do not promise unlocking or recovery.

Prepare canceled-project stock

Confirm ownership and saleable scope, and remove unrelated customer BOM details. Preserve original seals. Match lots to labels, counts and storage records; discuss confidentiality for sensitive program content.

Confirm quotation scope

Agree accepted condition, quoted codes, sampling, whole-lot or partial handling, acceptance and settlement. Obsolescence, popularity or an automotive family name does not guarantee acceptance or value.

Manufacturer references and scope

These references identify product families and public guidance. They do not establish our authorization, certification or testing capability.

• ST STM32 产品资料
• NXP MCU / MPU 产品资料

After preparing your stock list

Submit branded IC stock for assessment · Content and evidence information