Hard-to-find
ispGDX160V-5B208: recover the routing file before choosing an alternate
Published · Updated
An offer for ispGDX160V-5B208 is not ready for a maintenance build merely because the ordering number matches. This discontinued Lattice programmable interconnect links component identity to a particular board and its programmed routing. Buyers need the exact affected code, the historical withdrawal dates and a clear boundary between purchasing the original device and redesigning the board.
This dossier brings together the original notice, ordering table, V-specific electrical conditions, package outline and boundary-scan pin map. It helps a buyer prepare evidence questions for an offer and an engineer locate the correct source scope. No stock, price, delivery promise, lot authentication or replacement qualification is established here. All illustrations describe concepts or cited documents; no hardware test is represented.
The routing file belongs beside the purchase order
An ispGDX160V-5B208 purchase starts with a question that a stock listing cannot answer: what was the original device programmed to connect? This Lattice part is a programmable interconnect device. Its architecture does not contain the programmable logic arrays associated with a conventional FPGA. The useful purchasing record therefore includes the released board revision and the configuration used in that board, alongside the full ordering number. A replacement package with convincing lettering does not recover a missing design file.
The commercial ordering table identifies ispGDX160V-5B208 as the V device, speed grade -5, in a 208-ball fpBGA package. Keep all of those fields together. In the same manufacturer literature, V and VA share portions of their description and pin-location tables, but other specifications are explicitly separated. The first-page 3.5 ns and 250 MHz claims marked for VA must not be assigned to this V order code. Even a familiar family name can lead a buyer to the wrong electrical table.
Begin with the maintenance BOM exactly as released. Record the supplier’s proposed order code separately, preserving any added or omitted letters. Ask for the original outer-container label, a clear view of the device marking and an explanation of how those records relate to the quoted lot. Those records help connect an offer to a manufacturer identity. They do not independently prove authenticity, storage quality or successful operation. A text match should produce further evidence questions, not an automatic acceptance decision.
Next, ask the board owner for the released configuration, its revision identifier and the corresponding source project if one exists. Record the programming process and its versioned instructions. Do not assume that a purchased part is blank, correctly programmed or recoverable from an installed device. If the configuration history is missing, keep that gap visible in the repair plan. It may change the work from procuring a component into reconstructing and validating the intended interconnect behavior.
The manufacturer provides a BSDL model for the 208-ball V package. This is useful boundary-scan documentation, but it is not the customer’s application configuration. The model describes test-related ports and pin mapping; it cannot establish which signals the deployed board intended to connect. Reading a BSDL file also is not the same as executing a boundary-scan test. Keep the file, the board configuration and any real test results as different evidence categories.
For example, a hypothetical offer might reproduce the requested code perfectly while the maintenance team cannot identify the routing-file revision. That offer has passed a literal identity comparison only. The missing configuration remains a separate engineering task. Conversely, a complete design archive cannot resolve a supplier quote for a different suffix. Treat both dependencies independently so that progress on one does not silently close the other. The immediate output is a two-part record: material identity and released design identity.
Original ispGDX160V/VA data sheet, architecture and commercial ordering table, PDF pp. 3–4 and 35.
Four dates explain the old Active label
The June 2010 data sheet still presents this ordering code as Active / Orderable. A later manufacturer withdrawal record changes the purchasing interpretation. Lattice PCN 02A-15 was issued on June 23, 2015. The associated affected-ordering-number workbook, version 3 dated August 12, 2015, names ispGDX160V-5B208 in the AffectedOPNs_All sheet, row 30, column C. A current sourcing decision should preserve that chronology instead of treating an old data-sheet label as evidence of present factory availability.
The notice gives December 23, 2015 as the last-time-buy date and December 30, 2016 as the last shipment date. Last order and last shipment are different events. An accepted order could have been placed before the order cutoff and delivered during the later shipment period. Neither date states how much material any supplier holds today. A present quotation needs its own date, quantity, traceability and commercial terms; it does not reopen the historical manufacturer order window.
The affected workbook describes the package as a 208-ball BGA with SnPb finish and places the row in the full-family withdrawal group. Those are historical attributes of the affected ordering number. They are not a solderability report for a particular lot, and they do not establish how that lot has been stored or repackaged. The buyer should preserve the original record and ask the assembler which material and process evidence is needed for the intended maintenance build.
The same row contains the text MachXO or MachXO2 in its alternative information, while the alternative-available field says No and the pinout, voltage and assembly compatibility fields are N/A. Read the entire row together. Selecting the family names and dropping the qualification fields would turn a historical redesign direction into an unsupported replacement promise. The record does not identify a complete, approved replacement ordering number for this board.
A useful lifecycle register contains the data-sheet date, notice identifier, affected-row location, last-order date and last-shipment date. Add the date of any new supplier offer in a separate column. Keep original document versions rather than replacing an old file with a differently named download. If an original source becomes temporarily unavailable, that access problem alone does not prove that the notice was withdrawn or revised. Retain the known evidence and state the verification gap explicitly.
PCN 02A-15; affected-order workbook, AffectedOPNs_All C30, v3 dated 2015-08-12.
B208 requires three checks: ball map, outline and operating conditions
The correct package reference is 208-ball fpBGA. The manufacturer’s Package Diagrams document also contains an adjacent 208-ball ftBGA drawing. Similar names and the same ball count are insufficient to choose between them. The fpBGA drawing on page 78 gives D and E as 17.00 mm basic dimensions, a 1.00 mm basic ball pitch, and package height A from 1.30 to 2.10 mm with a nominal value of 1.70 mm. These values describe the cited outline; they are not a complete PCB land-pattern specification.
The neighboring ftBGA drawing on page 77 has a maximum height of 1.55 mm and different ball-diameter limits. That difference is a practical warning against finding a drawing by ball count alone. A service board may have clearance, solder-joint and assembly constraints that are absent from a procurement table. Use the released board library and the applicable manufacturer outline together. A package drawing does not, by itself, specify the solder stencil, reflow process, allowable storage condition or qualification of a substitute.
The document also has an internal version-label discrepancy: its November 2017 first page carries the footer pkg_5.4, while the revision history lists November 2017 as version 5.5. Preserve both labels in the evidence register. The relevant package page and the actual downloaded file should identify the source used for review. Silently selecting one version label would make later audits harder without resolving any physical uncertainty about a supplied device.
For electrical pin identification, use the 208-ball column in the data sheet rather than the adjacent 208-pin PQFP or 272-ball BGA columns. The dedicated 208-ball signal diagram is a bottom view. It is not a PCB footprint and should not be overlaid on a top-side board drawing without resolving orientation. In that package, E13 is VCC for ispGDX160V but VCCIO for ispGDX160VA. A shared position in a family drawing therefore does not mean that a different family member has the same power-rail requirements.
The data sheet identifies A10, P7 and T7 as no-connect positions and states that these must not be tied to active signals, VCC or ground. Its signal-location table and the original V-package BSDL file agree across the 208 positions compared for this dossier. That source agreement is useful for locating the manufacturer’s references. It is not a comparison against your board netlist, an executed boundary-scan result, or evidence that another device can occupy the footprint. Those remain separate engineering checks.
The V-specific recommended operating table specifies VCC from 3.0 to 3.6 V. The commercial entry applicable to this ordering-table row uses ambient TA from 0 to 70 °C. Ambient temperature must not be relabeled as junction temperature, and the absolute maximum ratings printed above the table must not be used as normal operating conditions. A 3.3 V label is only a starting point: loading, input thresholds, output behavior, power distribution and the actual operating environment still require review.
Timing needs its own scope. For the -5 grade, the external timing table gives a maximum 5.0 ns data propagation delay through a 4:1 multiplexer from an I/O pin to an I/O pin. The MUX-select-to-output path is separately listed at a maximum 6.5 ns. Both use condition A, including a 35 pF load with fixture and probe capacitance, one output switching and the stated fast-slew setting. The test uses 1.5 V timing references and the specified input transition conditions. Neither number guarantees every programmed path or a finished board’s clock rate.
Build the engineering handoff around the actual operating case: rail limits, ambient temperature, selected input and output paths, loading, timing margin, board revision and assembly constraints. Record an unanswered item as unknown. A purchasing worksheet should help locate these questions, but it should not turn a matching package name or a completed checklist into design approval. The responsible engineer needs the real circuit and its validation criteria before accepting a change.
V-specific data sheet, PDF pp. 17–19, 28–29 and 33; Package Diagrams, pp. 77–78 and 126. Package source version discrepancy is retained above.
Keep exact-part buying separate from a MachXO redesign
Exact-part sourcing and a redesigned interconnect solve different problems. If the service requirement is to maintain the released BOM, the purchasing request should remain ispGDX160V-5B208 unless the board owner authorizes a change. Ask suppliers to identify their complete offered code and any deviation explicitly. A vague promise of an equivalent device is not enough to evaluate packaging, configuration or qualification effort. Current price, inventory and delivery remain unknown until the offer is documented.
For that exact-part route, assemble a concise evidence request: required device quantity, complete order code, board revision, traceability expectations, label photographs, lot or date-code information, packaging condition and any reported repackaging. Specify the intended delivery requirement without presenting it as a confirmed lead time. Keep private board files and contact details out of link query strings. Use the website’s enquiry fields to describe the requirement, and provide sensitive project material only through a separately agreed channel.
For a redesign route, MachXO or MachXO2 is a family-level starting point in the historical record, not a selected part. An engineer must first define the original routing functions, any registered paths, signal directions, voltage conditions and startup behavior. Then a complete proposed ordering number can be evaluated against package, resource, timing, configuration, tooling and manufacturing requirements. Do not inherit the old part’s qualification just because the proposed family contains programmable logic.
Consider a hypothetical maintenance decision with an exact-code offer and an alternative-family suggestion. The exact-code offer still needs lot evidence and a recoverable released configuration. The family suggestion needs a specific device choice and a new design review before even its pin and power requirements can be compared. These are not two prices for an already equivalent solution. Quotation, engineering effort, validation and manufacturing changes belong in separate entries when estimating the total cost of each route.
The evidence worksheet below is a way to keep those routes visible. Preserve the requested code and supplier code separately, then note whether configuration history and lot documentation have been supplied. Missing evidence should generate a question for the appropriate owner. Completed fields should remain documentary statements, not a green approval badge. If new information changes an input, review the resulting questions again before reusing the record for another offer or another board revision.
Manufacturer family support references; historical alternative fields come from the affected workbook, not a new qualification.
Watch the concept order-code comparison

Text explanation: preserve the requested and offered codes, locate their differences and consult the manufacturer’s ordering definition. Matching text does not establish lot authenticity or board compatibility. The animation is shared explanatory material, not a test of this device.
Request the exact part or a separate board review
Start an enquiry for ispGDX160V-5B208 on the homepage and enter your actual device quantity, delivery requirement and traceability needs. For a wider board project, describe the scope in the homepage form. No availability or engineering acceptance is implied by opening the enquiry.
Prepared with AI-assisted review of original manufacturer sources. Illustrations and examples are explanatory. This is not human engineering certification, a lot inspection or a compatibility approval.