FPGA DEVICES · ENGINEERING · SOURCING Source-linked information. Clear project requirements.

Hard-to-find

XC2C32A-4PC44C: A 44-Lead Replacement That Changes the Board

Published · Updated

XC2C32A-4PC44C is the historical commercial, −4 speed grade CoolRunner-II CPLD in the 44-lead PC44 carrier. The manufacturer named XC2C32A-4VQ44C as a replacement in its discontinuation notice. A package and lead-number comparison shows why the two codes must remain separate for repair purchasing.

Use this guide when a bill of materials, service manual or photographed board calls for PC44 and a supplier offers VQ44. The immediate result is a documented choice between an exact-part request and a separate board redesign review. It does not establish stock, lot condition, programming access, compatible assembly or circuit performance.

Open an exact-part inquiry for XC2C32A-4PC44C. The 25-piece example is editable. No inquiry is sent by opening the form.

Preserve the affected code and the historical dates

The notice identifies the exact old codeHistorical evidence, not current delivery termsThe notice identifies the exact old codeAffected order codeXC2C32A-4PC44C → XC2C32A-4VQ44C2008-07-28Notice revision2008-11-01Final orders2009-05-01Final deliveriesHistorical evidence, not current delivery terms
Historical evidence, not current delivery terms.

Read page 2, Table 3 of the manufacturer discontinuation notice. The left-hand affected column contains XC2C32A-4PC44C, and the adjacent replacement column names XC2C32A-4VQ44C. The neighboring lead-free PCG44 line is a different ordering identity and has a different VQG44 replacement entry. If a quotation says only “32A 44-pin,” ask for the entire part number before treating either row as applicable. The table tells you the historical relationship between codes; it does not authenticate a label or identify the physical component on your board.

The PDF is XCN07022 v1.0.2, dated July 28, 2008. Its revision history on page 5 records an initial release on December 3, 2007 and later edits. Page 4 gives final order acceptance through November 1, 2008 (2008-11-01) and final deliveries no later than May 1, 2009 (2009-05-01) for the applicable device group. The programmer and adapter group has separate dates. Use the device group dates for this CPLD; none of those dates is a current lead time or a supplier commitment.

DS310 v2.1 removes obsolete PC44 parts from its page 10 ordering table and retains PC44 pin data for legacy support. Its page 13 revision note explains this change. Absence of the original order code in the later table is consistent with the discontinuation; the precise historical identity comes from the notice. The retained technical data answers how the old device was described, while the notice answers which order code was affected. Keep the two documents separate in the source record so an order code is not reconstructed from a family table.

The exact device identification guide explains how to keep the ordering number and documentation together. For a maintenance order, carry the full requested code from the service record into the sourcing line, then record the offered marking and its provenance separately. If those records conflict, leave the identity unresolved. Never assume the VQ44 code merely represents a shortened form of PC44, or that the similar part name shows current factory availability.

Compare outlines before comparing the pin count

Two outlines, one lead countPackage drawing comparison, not a land patternTwo outlines, one lead countPC44 carrier44 leads1.27 mm basic pitchPK006: N = 44 columnVQ44 flat pack44 leads0.8 mm lead spacingDS310: 10 × 10 mm bodyDifferent terminal style and pitchPackage drawing comparison, not a land pattern
Package drawing comparison, not a land pattern.

PC44 is a plastic leaded chip carrier. PK006 v1.2, page 1, covers several terminal counts even though the sheet header names PC84. Use the N equals 44 column and the PC44 entry at the foot of the sheet. It lists a basic lead pitch of 0.050 inch, equivalent to 1.27 mm, and D/E dimensions of 0.685–0.695 inch. These are drawing dimensions, not a copy-ready PCB land pattern. Read the views, datum references and notes before applying any number to a physical component or a socket.

DS310 page 10 describes XC2C32A-4VQ44C as a very thin quad flat pack with 0.8 mm pin spacing and a 10 mm by 10 mm package body. Those values belong to the VQ44 ordering row, not the PC44 carrier. Do not compare a lead-span dimension in one outline to a body dimension in another as if they describe the same feature. Even without a complete alternative footprint library, the terminal styles and different pitches already rule out treating the listed alternative as a drop-in fit on the original PC44 land pattern or in its socket.

For a repair ticket, first establish whether the assembly uses a socket or a soldered part, whether the revision matches the reference drawing, and which physical orientation the board uses. Do this from the approved board documentation and inspection record. A replacement purchasing row does not authorize an adapter, revised pad geometry or a new assembly process. A manufactured adapter would itself require a mapping, a power and signal review, mechanical clearance and a qualified procedure; none is provided or approved here.

PK006 distinguishes PC and PCG lead finishes at the package drawing level. This helps explain why a finish suffix is significant; it does not certify the finish of a particular offered lot. Request lot-specific evidence when assembly acceptance depends on it. The board bring-up checklist can help the repair team organize inspection, rail checks and functional evidence. It does not convert an archive outline or an offer photograph into a released manufacturing drawing.

One useful receiving check is to compare a photograph of the actual terminal style with the drawing before counting contacts. Record whether the photograph is of the offered lot or only a catalogue illustration. A label and an image can answer different questions, so preserve both with their source. Neither a vendor stock picture nor the lead count should settle an identity dispute.

Reconcile all forty-four positions by function

Compare numbered leads by roleExamples from the source map, not a wiring diagramCompare numbered leads by roleRolePC44VQ44Core VCC2115Programming VCCAUX4135JTAG TCK1711Bank 1 GCK054333 user positions include one input-only position.Examples from the source map, not a wiring diagram
Examples from the source map, not a wiring diagram.

In DS310 pages 8–9 the PC44 and VQ44 columns map the same macrocell rows to different numbered leads. For example, bank 1 clock function GCK0 appears at PC44 pin 5 and VQ44 pin 43. The page 9 supply and programming table puts core VCC at PC44 pin 21 versus VQ44 pin 15, VCCAUX at 41 versus 35, and TCK at 17 versus 11. These examples are enough to reject a rule that transfers a pin number unchanged. Verify every role against the correct package column and the orientation view on page 11 before implementing any design change.

There are 32 macrocell I/O rows, one separately identified input-only position in bank 2, four JTAG signal positions, four supply positions and three grounds. Together those categories account for 44 physical positions in each package. The manufacturer reports 33 user I/O including dual-function pins; the extra input-only position in the table cannot be counted as a bidirectional output. Treat the dedicated supply, ground and JTAG roles as fixed in this count. They are not unused macrocell signals that can be reassigned when a spreadsheet shows spare capacity.

The page 9 table labels PC44 pin 24 and VQ44 pin 18 as input only. The pinout sketches can look like generic I/O drawings at those positions. Preserve the explicit table restriction rather than treating the diagram label as an output guarantee. The table also marks global clock, set/reset and global output-enable functions on particular I/O rows. They can be ordinary I/O when the design does not use that global role, but a global function and unrelated signal must not both spend the same physical position.

Build a remapping record with logical net, pin role, bank, original lead, proposed lead and an unresolved or verified flag. Look up the source cell instead of inventing a pin offset from a few examples. The I/O budget worksheet can check the aggregate demand but does not resolve any of those fields. The useful deliverable is a reconciliation of the original schematic and package-specific assignments, with a separate orientation and net continuity review, rather than a generic list of spare pins.

Selected source positions, not an approved board remap
RolePC44VQ44Source
VCC2115DS310 p. 9
VCCIO1137DS310 p. 9
VCCIO23226DS310 p. 9
VCCAUX4135DS310 p. 9
TCK1711DS310 p. 9
GCK0543DS310 p. 8
Input only2418DS310 p. 9

Separate core, bank and programming supplies

Follow four supply positionsNamed rails and modes, not a sequencing diagramFollow four supply positionsLogic and programmingVCC: 1.7–1.9 VVCCAUX: 1.7–3.6 VCommercial TA: 0–70 °CBank output suppliesVCCIO1 and VCCIO2Choose the I/O modeLVCMOS15: Schmitt inputsVerify each rail and receiver separately.Named rails and modes, not a sequencing diagram
Named rails and modes, not a sequencing diagram.

DS310 page 3 defines commercial operation by ambient temperature TA from 0 °C through 70 °C and VCC from 1.7 V through 1.9 V. The nominal core voltage does not imply a single board supply for the package. VCCIO1 and VCCIO2 are separate output supply positions for their respective banks, and VCCAUX serves the programming pins. The same page gives a recommended range of 1.7 V through 3.6 V for VCCAUX. Use the recommended conditions table rather than treating absolute maximum values as design targets.

The output supply ranges are 1.4–1.6 V, 1.7–1.9 V, 2.3–2.7 V and 3.0–3.6 V for nominal 1.5 V, 1.8 V, 2.5 V and 3.3 V operation respectively. The supported I/O standards table on page 2 specifically conditions LVCMOS15 on Schmitt-trigger inputs. A compatibility review must include the chosen input mode and the driving and receiving limits; supply labels and the word “multivoltage” do not guarantee interoperability. Avoid copying a voltage assumption from a different CoolRunner density or a later FPGA family.

A board with one bank at 3.3 V and the other at 1.8 V needs its bank assignments and rail connections reviewed together. A correctly numbered signal in the wrong bank may still be an electrical mismatch. A restored programming header likewise needs the proper VCCAUX domain and JTAG assignments. The power rails worksheet can record currents and efficiencies supplied by the designer. It cannot supply a missing current budget or approve a power sequence, probe connection or programming operation.

Use an explicit missing-value marker if the old board rails are not yet verified. The page 3 standby and dynamic current entries refer to defined conditions and do not characterize the unknown repaired system. Budgeting with an assumed zero current simply hides the open question. If the job needs any powered measurement, retain the measurement setup and limits in the review record. This dossier uses archived documents only and makes no measurement or certification claim for a board or a purchased lot.

For a repair review, annotate which schematic nets actually reach each rail pin. Measure only as part of an approved diagnostic procedure, and distinguish a measured board voltage from a documented allowed device voltage. A recorded rail being within range does not show that the associated signals are within limits. Keep the connector reference and the programmed input mode in the same record so the next reviewer can reproduce the comparison.

Count the bank demand and scope the timing claim

Aggregate fits; one bank does notHypothetical count, not a placed designAggregate fits; one bank does notOverall I/O count23 signals + 3 clocks+ 5 reserves = 3132 bidirectional positionsBank 1 check17 positions required16 macrocell positionsOne assignment overInput-only bank 2 position is outside the output pool.Hypothetical count, not a placed design
Hypothetical count, not a placed design.

Try a deliberately hypothetical allocation in the I/O budget worksheet: 23 ordinary single-ended signals, zero differential pairs, three separately counted clock-capable positions and five reserved bidirectional positions. The aggregate output should be 31. The zero pairs is an explicit assumption for this example, not a claim that a missing input means zero. Do not enter the same clock net again under single-ended signals. Compare 31 to the 32 macrocell I/O positions, while keeping the additional input-only position outside the output pool.

Now suppose 17 of the hypothetical assignments must stay in bank 1 because of voltage or board connectivity. The macrocell table gives 16 bank 1 positions; the input-only extra is in bank 2. The aggregate count still leaves one bidirectional position overall, but this particular bank assignment is over by one. The arithmetic is a screen for a specific allocation conflict, not a fitter result. It explains why a small board change cannot be signed off by a single total or by renumbering a package without checking the nets.

For timing, DS310 page 5 gives a −4 maximum propagation delay of 3.8 ns for the single product-term path and 4.0 ns for the OR-array path, under its stated recommended operating scope. The table also lists internal toggle, internal system and external frequency figures with different definitions. Neither reciprocal propagation delay nor the fastest published toggle number is the board clock limit. Identify the actual logic path, input standard and load, and review the applicable timing conditions and any adjustments. A package replacement entry does not preserve a placed design or a verified timing report.

The device has two 16-macrocell function blocks. The same nominal macrocell count does not establish that the existing implementation can be moved unchanged. For a redesign, preserve the source logic, constraint file, bank selections, fitted pins and versioned programming artifact. A budget result is useful before fitting, and a verified fit is useful before testing, but neither proves lot authenticity, successful programming or safe behavior in the system. Keep these acceptance steps distinct in the release notes.

An inventory count and a logic constraint are also different kinds of evidence. A quantity can cover the repair plan even when the proposed alternative fails the selected bank allocation. Conversely, finding a legal assignment does not produce any stock or change the authorized part number. Keep the sourcing quantity, acceptance criteria and board-change review as separate lines so each can be signed off by its own owner.

Hand off an exact quote or a redesign, with the evidence attached

Keep the repair and redesign separateProcurement handoff, not a qualification decisionKeep the repair and redesign separateKeep the old assemblyExact PC44 codeLot and marking evidenceActual repair quantityReview a board changeHistorical VQ44 candidatePin, rail and layout remapFit, program and verifyChoose one path before combining quote lines.Procurement handoff, not a qualification decision
Procurement handoff, not a qualification decision.

For a board that must keep its PC44 footprint, preserve the exact XC2C32A-4PC44C requirement in the sourcing request. Ask for the full marking record, lot and date traceability, storage and handling evidence and the quantity the repair plan actually needs. An offered lot with incomplete identity should remain open for investigation. The status in an old manufacturer notice cannot confirm what a seller has, how a lot was stored, or whether the material will work in the intended product.

If the board can be revised, record XC2C32A-4VQ44C as the historical replacement candidate from XCN07022. Make a separate engineering ticket with the proposed package drawing, full pin and bank remap, programming plan, verification evidence and manufacturing checks. Require the drawing and layout owner to approve any new footprint and clearances. This guide establishes clear differences and an actionable comparison. It does not establish current lifecycle or supply of the alternative, a compatible replacement program or an approved adapter.

For an illustrative repair of 25 boards with one affected position per board, the BOM checker should retain the exact MPN and calculate 25 pieces for a 25-board lot using one piece at U7. Revise the quantity to match the real repair, and account separately for destructive inspection samples, spares or rejected parts. Do not silently aggregate the VQ44 candidate into the original repair line. The amount computed by a worksheet is a planning quantity, not a quantity available or reserved for purchase.

Use the Hard-to-find directory to return to the documented lifecycle records. Keep the private schematic, chain details and supplier documents in the engineering and procurement records; only the exact part and chosen quantity need to pass into the website inquiry. The final output for the team is either a precise PC44 inquiry that preserves the old assembly or a separate VQ44 design review with named acceptance gates. A single alternative field on a quote cannot serve both purposes.

Play the package review concept animationThree explanatory panels: same lead count, different terminal pitch and lead functions, separate repair inquiry from board redesign.

Static explanation: compare the package outlines first. Then compare the core supply and programming pin numbers. Keep the exact repair request separate from any proposed board change. The animation illustrates this decision, not an actual device or test.

Take the full MPN and example quantity to the homepage inquiry. The 25-piece example is editable. No inquiry is sent by opening the form.

This page was prepared with AI assistance. Source evidence and this manuscript received independent AI review. It is not a human engineering sign-off or a hardware test.

Back to Hard-to-find →

Source addresses and citation trail

Full source addresses are retained below. Read each citation with its document revision, page, table and applicability conditions above.

  1. https://docs.amd.com/api/khub/documents/APoebodiTfDPqUjvecA3iw/content
  2. https://docs.amd.com/api/khub/documents/Jk6jWOFmqdQSpKxDkJy6Ww/content
  3. https://docs.amd.com/api/khub/documents/kdlsy~nzOTClXn~2NfEPwQ/content