Hard-to-find
LCMXO1200C-3B256C: 211 I/Os do not settle a lead-finish change
Published · Updated
A maintenance BOM naming LCMXO1200C-3B256C asks for a specific 256-ball MachXO device and conventional lead-finish code. Its historical alternative record contains a negative SnPb-assembly flag, so a matching resource count is not the final purchasing decision.
This dossier separates the exact withdrawal record, supply and temperature conditions, package-level I/O allocation and configuration handoff. Use it to prepare an evidence request for the original part or a separately reviewed change. Current stock, price, delivery and lot acceptance remain unconfirmed.
The two C characters do different jobs
LCMXO1200C-3B256C is a complete MachXO ordering number, not simply a 1,200-LUT description. The C after 1200 identifies the supply-voltage variant, while the final C identifies commercial grade. The intervening B256 identifies a 256-ball caBGA package and -3 is the speed grade. Lattice lists this exact conventional-package code in the commercial ordering table on page 78 of FPGA-DS-02071-3.3, July 2022. The historical withdrawal evidence discussed below applies to the exact code, even though a later family data sheet still includes an ordering-table entry.
A buyer should keep the requested number and the supplier quotation in separate fields. In particular, LCMXO1200C-3BN256C contains an added N inside the package field. The data sheet lists BN256 as lead-free caBGA, while B256 is the conventional caBGA code. That difference is meaningful to an assembly review. Copying the shared 1200 or 256 characters into a comparison worksheet does not resolve the material specification for a maintenance board.
The speed and temperature fields deserve the same care. The part-number explanation describes -3 as the slowest of the listed speed grades; this is a relative grade designation, not a complete statement of usable clock frequency. The recommended-operating table gives commercial operation as 0 to 85 degrees Celsius junction temperature. It does not say that a room or enclosure at 85 degrees is automatically acceptable. Junction temperature and ambient temperature are different inputs to a thermal review.
The manufacturer also describes dual marking, with an exception for the slowest commercial speed grade. This exact order code has that slowest commercial grade, so do not use a generic dual-marking example as permission to reinterpret any additional supplier marking. Request the original label and the manufacturer definition that applies to the offered device. Marking, package identity, lot history and programmed behavior answer different questions and should remain separately reviewable.
For an initial identity exercise, open the complete-order-code comparison in the original ordering-number tutorial and enter the requested B256 code and the proposed BN256 code exactly as received. Inspect the inserted character and save the comparison output. The useful result is a transcription difference that can be taken to the source documents. It does not authenticate the lot, establish solder-joint reliability or approve the second part for the board. Keep a copy of the original quotation beside that output.
Sources: MachXO data sheet FPGA-DS-02071-3.3, July 2022, pages 77–78. Historical records do not establish present factory supply.
An ordering-table row is not a present supply commitment
Lattice PCN02A-15 was issued on June 23,2015. Its affected-order-number workbook, version 3 dated August 12,2015, names LCMXO1200C-3B256C in AffectedOPNs_All row 1972, column C. The row belongs to the SnPb-only group and identifies a 256-ball BGA with SnPb finish. The notice gives December 23,2015 as the last-order date and December 30,2016 as the last-shipment date. These are historical manufacturer milestones, not a forecast of what a present supplier can deliver.
Read the entire alternative record rather than extracting only its part number. That row names LCMXO1200C-3BN256C and records historical yes values for alternative availability, pinout compatibility and voltage compatibility, but no for SnPb-assembly compatibility. The negative assembly flag is a reason to obtain a process review before accepting a changed finish. It is not canceled by the two electrical or pinout flags, nor by a supplier describing the item as the same device.
This evidence concerns the particular conventional-finish order code. It does not justify labeling every MachXO family member discontinued, and the appearance of an order code in a family data sheet does not establish a present factory supply commitment. The notice says orders received after the 2015-12-23 milestone would be accepted on a best-effort basis. Preserve that qualification: the date was not an unconditional prohibition on every later order, and the historical wording is not a current offer. Maintain a lifecycle register with separate entries for the family document, the withdrawal notice, its exact affected row and the date of the supplier offer. A current availability claim needs current evidence of its own.
For a maintenance request, ask whether the released assembly specification permits a lead-finish change and who owns that decision. The answer may involve the repair process, solder materials, reflow limits, storage evidence and applicable customer restrictions. If those records are missing, leave the change unresolved. A purchasing person can gather the documents, but cannot turn the historical workbook flags into a new board qualification by completing a checklist.
An exact-code route remains a valid question to ask a supplier: identify the available lot, actual offered quantity, packaging history and documented commercial terms. A changed-code route needs a separate comparison and authorization. Neither route establishes current stock, price, remaining service life or lead time on this page. Keeping both requests explicit makes it possible to compare real offers without silently changing the maintenance BOM.
Sources: PCN02A-15 and affected workbook v3, AffectedOPNs_All C1972. Historical records do not establish present factory supply.
C-variant core power does not remove auxiliary and bank checks
The C supply variant is associated with 1.8 V,2.5 V and 3.3 V operation in the ordering information. Its recommended core-supply envelope is 1.71 V to 3.465 V in the source table. The E variant instead uses a 1.2 V core, with a recommended 1.14 V to 1.26 V range. A quotation that changes the C after 1200 to E therefore raises a supply-design question even when density, ball count and the final commercial-grade letter remain familiar.
The auxiliary supply is a separate record. The table also requires like power supplies to be tied together; preserve that board-connection condition. Page 30 specifies VCCAUX from 3.135 V to 3.465 V, and its footnote requires VCC to reach the minimum VCC value before VCCAUX reaches 2.5 V. Translate that rule into a board-specific power review with the actual regulator connections, startup behavior and applicable rise conditions. An illustration of the sequence is a reading aid; it is not a measured waveform or proof that a board already meets the requirement.
The same table gives an I/O-driver supply range, but immediately directs the reader to the voltages appropriate to each I/O standard. Record the standard, bank supply and direction for every group of signals. A single board label such as 3.3 V logic is insufficient when some external devices operate at other levels or when differential functions share a bank. Check the actual pin assignments and standard-specific tables before applying an interface assumption.
The package pin summary gives LCMXO1200 eight I/O banks. It also lists dedicated supplies, grounds and test-related resources separately from user I/O. Do not count power balls as spare signals or allocate every physically visible ball to the design. Preserve the manufacturer pin naming and the board netlist in the engineering handoff. This article has not compared all 256 ball locations against a customer board or validated a replacement pin map.
Power or temperature uncertainty should generate a question rather than a zero in a worksheet. Write down the core variant actually required, the auxiliary supply, each bank voltage, the temperature definition and the owner of any unresolved measurement. If a proposed device changes one of those inputs, reopen the relevant review. A positive pin-count margin cannot close a supply-sequencing problem, and a matching supply label cannot close an assembly-material problem.
Sources: MachXO data sheet FPGA-DS-02071-3.3, July 2022, pages 30 and48. Historical records do not establish present factory supply.
Budget 211 user I/Os, then break the total into eight banks
The exact B256 commercial ordering row lists 1,200 LUTs and 211 user I/Os. The family selection guide identifies one embedded-memory block for the 1200 density and one PLL; the density-level embedded-memory figure is 9.2 Kbits. These are resource descriptors, not guarantees that an existing HDL project or timing constraint will fit unchanged. The implementation report, memory organization, clock requirements and pin allocation remain necessary design records.
Page 48 divides the 211 single-ended user I/Os for the 1200 device in the 256-ball package into bank capacities of 26,28,26,28,27,22,28 and 26. Their sum is 211. This distribution is more useful than treating 211 as one interchangeable pool. A design can have spare I/O overall while the bank required by its supply standard, clock location or external connection has no acceptable remaining placement.
Here is a hypothetical planning exercise, not a characterization of a real board. Enter 48 single-ended signals,8 differential pairs,2 additional single-ended clock pins and 10 reserved user I/Os in the User I/O budget tool. Each differential pair uses two user pins, so the counted demand is 48 plus 16 plus 2 plus 10, or 76 pins. Against the published package count, the arithmetic margin is 211 minus 76, or 135. This is a count comparison only.
Put each signal into one category in that exercise. A differential clock already counted as a pair must not also appear among additional single-ended clocks. Count reserved user pins because the project genuinely reserves them, not because every programming, supply or ground connection should be added to that category. Keep the assumptions in the saved output so another reviewer can reproduce the total and identify a changed requirement.
Now replace the example with a bank allocation table for the actual board. For each bank, record capacity, requested signals, applicable voltage, clock or differential restrictions and the source page used. A hypothetical request for 27 signals in a 26-I/O bank has a local count deficit even if other banks are mostly empty. Resolve that constraint through a valid reassignment or a design change, not by subtracting from the aggregate spare count.
The practical output is two records: the browser-local arithmetic report and a separate bank-and-netlist review sheet. The first can reveal an obvious demand problem; the second carries the conditions the total cannot express. Neither is a placement result, timing closure, bitstream validation or permission to buy an electrically different variant. Preserve failed examples as evidence of the unresolved constraint rather than rewriting the inputs until the output looks favorable.
Sources: MachXO data sheet FPGA-DS-02071-3.3, July 2022, pages 6,48 and78. Historical records do not establish present factory supply.
Send the repair team a configuration and assembly dossier
A nonvolatile programmable device still belongs to a particular released design. Before committing a repair build, identify the board revision, configuration file, source project if available, programming instructions and the versioned environment used to produce and load that configuration. The existence of internal configuration storage does not recover a missing customer design, prove that a supplied part is blank or prove that it contains the intended logic.
Use the manufacturing-package tool to organize the handoff around actual files and unresolved requirements. Keep the released BOM, schematic, layout, assembly instructions and programming or test procedure identifiable by revision. Record whether each is supplied, missing or under review. The tool helps organize a document request; it records file-name and presence declarations; it does not upload or inspect those files or provide engineering approval.
For the material side, attach the exact requested and offered codes, original outer-container labels, lot or date-code records, carrier information, reported storage or repackaging history and the lead-finish evidence. Ask the assembler which further inspection or process records are required. Photographs and a readable label can support traceability questions, but cannot by themselves establish authenticity or long-term reliability for a legacy lot.
Keep dimensional questions open until the correct mechanical drawing and board library have been reviewed. The family guide distinguishes the 256-ball caBGA body option from the 256-ball ftBGA option; the same ball count does not make their outlines the same. The package label in this article is not a complete land-pattern specification. Board clearance, soldering constraints, orientation and actual ball assignments must be checked with the applicable original package documentation.
Finish with a short decision record naming the responsible buyer, board engineer and assembly reviewer. State which path is being requested: the original B256 order code, or an explicitly proposed finish change such as BN256. Record the evidence received and the questions still open. Only the project owners can decide whether the combined material, configuration and process evidence is sufficient for their acceptance criteria.
For an exact-part quotation, retain LCMXO1200C-3B256C and enter the real device quantity, required delivery and traceability expectations on the homepage. If the project requires a wider board review, describe that separately and arrange a suitable route for confidential files. Opening a quotation form does not reserve stock, approve a change or submit the request automatically. The useful next step is a documented requirement that can be answered without guessing what the maintenance team intended.
Sources: MachXO data sheet FPGA-DS-02071-3.3, July 2022, pages 6 and77. Historical records do not establish present factory supply.
Watch a complete-order-code comparison concept

Preserve both complete strings, locate a difference, read its manufacturer definition and keep the decision separate from board qualification. Shared concept material, not a physical inspection or device simulation.
Request LCMXO1200C-3B256C — 25 devices Discuss a board review
Prepared with AI-assisted source and manuscript review. Diagrams and numerical examples are explanatory. No human engineering certification, lot inspection, hardware test or substitute approval is represented.