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

Hard-to-find

XC17V04PC20C: Check the OTP State Before an FPGA Boot-Memory Purchase

Published · Updated

XC17V04PC20C is a 4,194,304-bit, one-time-programmable configuration PROM with a single serial DATA output. It stores an FPGA configuration image; it is neither an FPGA fabric nor a rewritable serial flash. For an obsolete-board purchase, the complete label and package are only part of the requirement. Whether the offered unit is blank, already programmed, or of unknown programming state can change the usefulness of that purchase.

This guide uses the historical full-code list in DS073 v2.0, 7 April 2014 and the exact affected row in XCN12026 v1.0.2, 24 April 2013. It turns those records into a serial-capacity, control-pin and programming-state handoff. The examples are document reading and arithmetic. No actual lot, stored image, programmer operation, powered boot test, present stock, price or delivery has been verified.

Request price and lead time for XC17V04PC20C, 25 pieces on the homepage. Change the example quantity to your actual requirement and state the programming condition you need. The quantity is not a stock claim or minimum order.

Confirm the PROM identity before accepting its programming state

Keep identity and programming state as separate recordsOriginal evidence-led diagram. DS073 v2.0 lists XC17V04PC20C as a valid historical combination: 4,194,304-bit OTP memory, PC20 PLCC, commercial ambient TA 0 to 70°C. XCN12026 v1.0.2 gives LTB 31 May 2013 and LTS 30 September 2014. Actual blank/programmed state is unknown.An exact code does not reveal its contentsXC17V04PC20CXC17V04PC20C4,194,304 bits20-pin PLCCTA 0–70 CBlank / programmed / unknown?This is a separate lot-evidence question.LTBLTS2013-05-312014-09-30Historical dates are not current inventory evidence.
Original evidence-led diagram. DS073 v2.0 lists XC17V04PC20C as a valid historical combination: 4,194,304-bit OTP memory, PC20 PLCC, commercial ambient TA 0 to 70°C. XCN12026 v1.0.2 gives LTB 31 May 2013 and LTS 30 September 2014. Actual blank/programmed state is unknown.

DS073 page14 explicitly lists XC17V04PC20C among the valid historical ordering combinations. Page13 identifies PC20 as a twenty-pin plastic leaded chip carrier and C as the commercial operating range, with ambient temperature TA from 0°C to +70°C. Preserve every field. PC20 and PC44 are different packages, and the I industrial grade is a separate purchasing line. An FPGA carrying the same letter C can have a different temperature definition; do not copy a junction-temperature limit into this PROM record.

The document also explains that small packages may not carry the complete ordering number. Its marking section says the XC prefix is omitted and package information is simplified. A shortened top marking therefore needs a documented mapping to the full requested identity. It is not by itself proof of a false part, a confirmed complete match or a particular programming condition. Retain the label, lot documentation and supplier statement together. The ordering-number tutorial provides the general identity process; this PROM adds a separate stored-content question.

XCN12026 page2 Table1 names XC17V04PC20C and supplies no direct replacement. Page1 gives the last-time-buy date of 31 May 2013 and final shipment on or before 30 September 2014. The notice was initially released on 19 November 2012; page18 records that version1.0.2 corrected an LTB typo on 24 April 2013. Keep the revision date, initial issue and withdrawal deadlines distinct. A later datasheet remaining online does not reopen ordering or establish present supply.

The notice states that orders placed after 31 March 2013 were non-cancellable and non-returnable. That is a historical manufacturer condition, separate from a new supplier quotation and its written terms. The notice also distinguishes the FPGA supplier-line withdrawal from regular pruning of the XC17V00 PROM family. Preserve that scope rather than applying one broad explanation to every affected product. Current availability and suitability remain questions for the exact offered lot and the actual board.

Ask whether the requirement is for unprogrammed devices or for devices carrying an approved image and option settings. For an unprogrammed requirement, agree what blank-state evidence will be supplied and how it is tied to the lot. For programmed material, retain the authorized image identifier, revision and verification record. Unknown is a valid unresolved state; it must not silently become blank. No blank check or content readback was performed for this guide, and a new invoice does not establish a new programming history.

A reviewable acceptance record can keep four entries separate: physical identity, programming state, reset-polarity options and image verification. For each entry, name the evidence file or report, its revision, the lot or unit it covers, the expected result and the person responsible for acceptance. A confirmed label can coexist with an unknown programming state; combining them into one pass mark would hide the unresolved requirement. If the supplier can provide only package photographs, record what those photographs actually show and leave the remaining entries open. Request the missing report rather than inferring a stored image from a model number. This is a proposed record structure, not a completed inspection record or a report about material currently offered by FPGA.io.

Count stored bits without borrowing the parallel-mode headline

Capacity arithmetic does not create a parallel interfaceOriginal capacity example. DS073 pages3 and5 identify one serial DATA output and 4,194,304 configuration bits for XC17V04. A hypothetical 4,000,000-bit image requires 500,000 bytes with zero extra reserve; two copies exceed one device. Diagram is not a programmed image, timing result or proof of boot compatibility.One serial bit per clock, not an 8-bit portXC17V04: single DATA outputNo parallel-mode or BUSY feature is inherited.Example: 4,000,000 payload bits1 image, 0% additional reserve500,000 / 524,288 bytes24,288 bytes arithmetic headroomTwo such images: 1,000,000 bytesOne device is short by 475,712 bytes.Hypothetical payload; no boot image or fit is approved.
Original capacity example. DS073 pages3 and5 identify one serial DATA output and 4,194,304 configuration bits for XC17V04. A hypothetical 4,000,000-bit image requires 500,000 bytes with zero extra reserve; two copies exceed one device. Diagram is not a programmed image, timing result or proof of boot compatibility.

The XC17V04 capacity is 4,194,304 configuration bits in DS073 page5 Table4. Dividing by eight gives 524,288 bytes, or 512 KiB. This binary capacity is not four megabytes. Keep the exact bit count in the record so a payload budget cannot drift between marketing megabits, decimal bytes and binary units. The number is an array capacity; it does not tell you the contents of a physical PROM or whether an existing image belongs to your board revision.

Pages1 and3 separate the serial XC17V04 behavior from the dual serial/parallel modes of XC17V08 and XC17V16. XC17V04 has one DATA output, not an eight-bit SelectMAP output port. The family headline about parallel transfer at twenty megahertz belongs to the larger dual-mode subset. The XC17V04 block diagram does not inherit its BUSY input or D1-through-D7 connections. A quoted density or a similar package name cannot supply an interface feature that this device does not have.

For a deliberately hypothetical image of four million payload bits, enter 4,000,000 bits, one complete image and zero percent additional reserve in the configuration-storage calculator. The output is 500,000 bytes. Comparing that arithmetic with the documented 524,288-byte capacity leaves 24,288 bytes. Zero reserve is an explicit example input, not permission to treat an unknown overhead as zero. Replace the example with the generated configuration payload and the actual storage method before making a device-fit decision.

Changing the same example to two images returns 1,000,000 bytes, exceeding one XC17V04 by 475,712 bytes. Neither a positive nor negative capacity result configures a multi-image boot mechanism. The source describes sequential output and cascaded PROMs; it does not turn this part into randomly addressable flash. A chain must preserve control and timing requirements, image order and the applicable FPGA configuration procedure. Adding nominal capacities alone is insufficient evidence for a working chain.

Keep the payload definition separate from the host file representation. A textual programming file can contain addressing, records or other encoding beyond the configuration payload. Record which generated artifact and measurement produced the bit count instead of using an unexplained file-size number. Keep proprietary images and their contents private; a controlled filename, revision and hash can identify the approved artifact in the engineering record. This guide does not publish a customer bitstream, program an actual unit or approve a particular FPGA-and-PROM pairing.

Read the PC20 column and keep read-mode power distinct from programming

Eight named connections, with VPP tied for normal readOriginal functional connection map from DS073 page4 Table3 and page6 PC20 top view. DATA1, CLK3, RESET/OE8, CE10, GND11, CEO13, VPP18 and VCC20 are the eight named PC20 connections; other positions are NC. VPP-to-VCC connection applies to normal read, not a programming algorithm. Not a physical pinout, footprint or wiring release.PC20: control, data and read-mode powerXC17V04PC20 PLCCSerial OTP PROMCLK 3RESET/OE 8CE 10DATA 1CEO 13VCC 20VPP 18READ MODEGND 1112 other positions are NC in this PC20 column.Functional map only. Not a pinout or footprint.
Original functional connection map from DS073 page4 Table3 and page6 PC20 top view. DATA1, CLK3, RESET/OE8, CE10, GND11, CEO13, VPP18 and VCC20 are the eight named PC20 connections; other positions are NC. VPP-to-VCC connection applies to normal read, not a programming algorithm. Not a physical pinout, footprint or wiring release.
ConnectionPC20 pinRead-mode role
DATA1Single serial data output
CLK3Counter/read clock
RESET/OE8Polarity is a programmed option
CE10High inhibits output and resets counter
GND11Ground
CEO13Chain enable output
VPP18Connect to VCC during normal read
VCC203.0–3.6 V operating supply

DS073 page4 Table3 and page6 PC20 top view. The twelve unlisted PC20 positions are no-connects. This is not a footprint or a programming-voltage recipe.

Table3 on page4 lists separate columns for VO8, SO20, PC20, VQ44 and PC44. Read PC20 even where SO20 happens to share some pin numbers; shared numbers do not establish the same body outline or assembly process. For PC20 the eight named connections are DATA1, CLK3, RESET/OE8, CE10, GND11, CEO13, VPP18 and VCC20. The other twelve positions are marked no-connect by the table rule. Twenty leads are not twenty general-purpose I/Os. The functional diagram above is deliberately not a physical placement or PCB footprint.

The PC20 top-view sketch on page6 supports the orientation and numbering check. It does not supply a complete dimensioned component outline, pad pattern, clearance or reflow approval in this guide. Compare the actual board library and orientation against released package data before an assembly change. For existing boards, retain the board revision, socket or soldered-mount arrangement and any handling or inspection scope. A visual resemblance to another twenty-pin package cannot settle those requirements, and no dimensional inspection or assembly qualification is claimed here.

Page10 specifies a normal operating supply from 3.0 V to 3.6 V for commercial TA of 0°C to +70°C. It requires VPP to be connected to VCC during normal read operation and warns against a floating VPP pin. This read condition is separate from programming, for which the correct device algorithm and programmer support must be established. Do not treat the absolute-maximum VPP number as an operating instruction or apply a programming supply to an assembled board on the strength of this article.

The same operating table requires a monotonic rise from zero to nominal VCC within one to fifty milliseconds. It warns that a supply outside that requirement may not give a proper power-on reset. Check the actual power-up waveform and system reset behavior through the responsible project engineer; none was measured here. A steady-state multimeter reading near the nominal rail does not record the rise shape, startup timing or reset sequence that the source is discussing.

DS073 page3 says that reset polarity is programmed and defaults to active-high RESET, while compatibility with the stated Xilinx FPGA arrangements requires active-low RESET. The option record therefore belongs with the programmed image. Page3 explains that a high CE holds the counter reset; page8 separately shows disabled DATA and standby while CE is high; a low CE is not by itself a complete ready-to-read condition. Preserve reset, enable and clock relationships from the actual design. Missing option settings should remain unresolved rather than being inferred from the package label.

Bound clock arithmetic and prepare an evidence-based request

Keep serial read delay, startup and board timing separateOriginal conditional timing illustration. DS073 page11 lists a 67 ns minimum clock period and 45 ns maximum CLK-to-DATA delay for XC17V04 under the stated 50 pF AC test load. A hypothetical 100 ns period leaves 55 ns before board and receiver requirements; it does not approve startup, read timing or boot time.Clock arithmetic does not prove boot timeHypothetical 10 MHz clock → 100 ns period45 ns55 nsCLK-to-DATA maximum: 45 ns100 − 45 = 55 ns before other delaysSubtract FPGA setup, trace delay and skew.Initial enable/reset and ramp time remain separate.Source: XC17V04 table, 50 pF AC test load.Concept intervals. Not a measured or simulated waveform.
Original conditional timing illustration. DS073 page11 lists a 67 ns minimum clock period and 45 ns maximum CLK-to-DATA delay for XC17V04 under the stated 50 pF AC test load. A hypothetical 100 ns period leaves 55 ns before board and receiver requirements; it does not approve startup, read timing or boot time.

Use the XC17V04 timing table on page11, not the XC17V16/XC17V08 table on page12. The former gives a minimum clock period of sixty-seven nanoseconds and a maximum CLK-to-DATA delay of forty-five nanoseconds. The source AC test load is fifty picofarads, and the listed input measurement levels are zero and three volts. The larger-device table has different limits. These are conditional source specifications, not an observed boot rate or proof that every receiver and board can use a chosen clock.

Consider a hypothetical ten-megahertz clock, equivalent to a hundred-nanosecond period. Subtracting the forty-five-nanosecond CLK-to-DATA maximum leaves fifty-five nanoseconds before the next nominal edge, before accounting for receiver setup, trace propagation, clock skew and uncertainty. This deliberately incomplete interval is not a certified timing margin. The applicable FPGA sampling rule and actual clock relationships still need review. In particular, the first data after enable or reset has its own conditions; the continuous-clock subtraction does not approve startup.

For the four-million-bit hypothetical payload, ten million serial clocks per second would account for 0.4 seconds of payload clocks. That number excludes power ramp, reset, initial enable, protocol and device startup overhead. DS073 explicitly says its timing illustration is not the actual FPGA signal sequence. Retain that distinction when quoting an expected startup time. No waveform was captured, no simulation was run and no board was configured during this content review.

The original animation below separates the evidence records rather than imitating a boot waveform. Its static transcript is: preserve the exact PROM identity, establish blank or programmed state with option and image records, then retain the agreed verification output. Opening the animation is optional. Its sequence does not report a completed blank check, programmer cycle, authenticity decision or successful startup. A clearly documented unknown is more useful than a completed-looking checklist that conceals missing lot evidence.

Play the original PROM evidence concept
Original conceptual sequence for exact PROM identity, programming-state evidence and verification records; not a hardware or programmer test
Original FPGA.io document-review concept. Not a measured boot waveform, programming operation, blank check or authenticity verdict. The preceding paragraph supplies the static transcript.

For material quantity, suppose one XC17V04PC20C at U2 is required on each of twenty-five boards. The BOM checker should return twenty-five devices from the one-per-board row below. Replace the board quantity and reference with the released design, and keep agreed spares separate. A correct count does not confirm blank state, stored content, programmer compatibility, MOQ, available inventory or a suitable substitute. The full PROM number stays separate from the FPGA and any other memory on the board.

MPN	Qty	Ref
XC17V04PC20C	1	U2

DS073 page7 requires the appropriate device algorithm and suitable programmer software, warning that a wrong choice can permanently damage a unit. Preserve the approved programmer model, software/algorithm revision, image identifier, option settings and verification report in the real work order. This guide endorses no particular programmer or release and supplies no programming-voltage procedure. For lot-history questions, use the legacy IC evidence guide; its documentation questions do not generate an authenticity score or replace agreed inspection.

The Hard-to-find directory organizes withdrawal evidence rather than stock. The Virtex-II Pro sourcing guide illustrates why a processor-bearing FPGA has its own infrastructure and junction-temperature record; that reading link is not a claim that this PROM configures that device. For manufacturing changes, the assembly review needs the actual board files, package evidence and agreed programming/test scope. Bring the missing records forward with an owner instead of allowing a quote to become an engineering approval.

Get price and lead time for XC17V04PC20C, 25 pieces. Set the actual quantity on the homepage and specify the required programming state, delivery, destination and lot evidence. Keep any alternate proposal and its approval separate. No present stock, delivery commitment, programmed content, direct replacement or human engineering certification is implied.

Prepared with AI-assisted manufacturer-document analysis. A separate AI source, full-text and visual review was completed before release. No human engineering sign-off, programmer test or board validation is represented.

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/zeVecxGWTzd3iIaH3DvWzg/content
  2. https://docs.amd.com/api/khub/documents/Sp4erNTxXQgkdXNG9j8SwA/content