1. Identify the Device and Its Known Programming State
Record the complete manufacturer ordering code, package variant and available lot identifiers. Keep an internal firmware reference separate from the semiconductor code. A label carrying a customer programme number may describe the application assigned to the stock rather than the underlying device that another reviewer needs to identify.
Use terms that match the evidence. Keep stock described as unprogrammed by its source, customer-programmed units with records, and units of unknown programming state distinguishable. Record removal from equipment as a separate history field. Unused packaging is not a blank-memory result, and one declaration should not be extended across packs with different or unknown programming histories.
Identify where the declaration came from and what it covers. A contract manufacturer's programming log, a production release record and a seller's recollection have different scope. Retain the available references with the affected lots, stating missing records explicitly. This guide concerns disclosure for review; it does not report a blank check or functional test performed by ICULTRA.
2. Keep Memory and Protection Details Separate
Microchip's MCU memory guidance distinguishes program flash, data EEPROM and volatile memory, and directs readers to device documentation for feature availability. Its code-protection discussion explains why external reading or editing can be restricted. The existence of flash memory therefore does not identify the actual state of a particular surplus unit.
Microchip also describes Programming and Debugging Interface Disable as an irreversible feature on supported devices. This product-specific example shows why a general promise of erase or reprogramming is insufficient. It does not establish that an unidentified MCU has PDID enabled or that every Microchip device provides the same options.
Keep known configuration, protection and bootloader information as separate disclosures. Leave unknown settings unresolved. A firmware identifier, an available programming record and evidence about an interface restriction describe different things. Do not infer a blank or unrestricted device because its normal part number remains visible, and do not propose bypassing protection as part of a sales inquiry.
3. Define the Records That May Be Shared
Ask the owner which non-sensitive records can support identification of the stock. A dated reference to the authorised programming job and affected lot may be sufficient for an initial review. Avoid including customer code images, security keys or unrelated design files merely to make an inquiry appear complete.
If a relevant record cannot be disclosed, state the limitation and discuss an authorised review arrangement. Authority to sell physical components should be resolved separately from permission to share application information. This checklist does not determine intellectual-property rights, contractual restrictions or legal permission for a particular customer's programme.
Keep an existing verification report distinct from a programming declaration. Record the units or samples covered, method, date and reported result. A record for a subset cannot silently become evidence that all units are blank, erased or functional. If the only known fact is prior installation, report that history without inventing what code, data or settings remain inside.
4. Request Review of the Disclosed MCU Groups
Prepare a lot-level inquiry listing the exact devices, quantities, physical condition and programming-state evidence. Identify groups whose state is unknown and those whose documentation indicates restrictions. This enables a reviewer to decide which questions remain open before considering the material, without implying that every disclosed group can be accepted.
Do not modify the devices just to support a quote request. Erasure or reprogramming can change the offered item and may not be available in its actual state. Any such work requires a separate authorised decision and qualified process based on the exact device and application. No erasure, code extraction or programming service is offered by this article.
For an ICULTRA buyback review, submit the permitted identification and history records and explain unresolved programming questions. The outgoing-file guide can help limit unrelated disclosure, while the general stock-list guide supports the lot structure. Purchase eligibility, any verification arrangements and commercial terms require written confirmation for the specified material.
Sources and further reading
Manufacturer documents support the technical guidance above. They do not confirm our stock, authorisation or the condition of any offered lot.