Xilinx IC Unlock — What Is Actually Possible?
Xilinx IC unlock refers to the authorized recovery of bitstream or configuration data from Xilinx FPGAs and CPLDs when the original design files have been lost, corrupted, or are otherwise unavailable. Our engineers extract this data using a combination of JTAG/boundary-scan probing, decapsulation-based techniques, and non-volatile memory readback — depending on the specific family and its security fuse state. Success depends heavily on the device generation, package type, and which protection bits were set during production programming.
Why Xilinx Devices Need Unlock Services

Xilinx (now part of AMD) has shipped billions of FPGAs and CPLDs across industrial, medical, telecom, and defense applications since the 1980s. When original designers leave a company, when a contract manufacturer goes bankrupt, or when legacy equipment must be maintained past its planned life, the configuration data locked inside a Xilinx part may be the only surviving copy of the design.
Common scenarios we handle:
- Legacy equipment repair — a Spartan-3 on a 15-year-old industrial controller fails; the OEM no longer exists.
- IP recovery for product owners — your contract house programmed the FPGA but never delivered source HDL.
- Obsolescence management — migrating a design off a discontinued XC9500 CPLD requires the original fuse map.
- Second-source verification — confirming that a replacement FPGA carries the correct bitstream before field deployment.
All work requires proof of ownership or written authorization. We operate under NDA and document the chain of custody for every device we process.
Which Xilinx Families Can We Read?
The table below summarizes our current capability across major Xilinx product lines. “Feasibility” means the outcome depends on the specific part number, revision, and security configuration — we evaluate each device individually before quoting.
| Family | Type | Process Node | Security Mechanism | Recovery Status |
|---|---|---|---|---|
| XC9500 / XC9500XL | CPLD | 350–180 nm | Security fuse (single bit) | High success |
| CoolRunner (XPLA3) | CPLD | 180 nm | Security fuse | High success |
| CoolRunner-II | CPLD | 180 nm | Security fuse + read-protect | High success |
| Spartan-II / Spartan-IIE | FPGA | 150 nm | Bitstream encryption (none or DES) | High success |
| Spartan-3 / 3E / 3A / 3AN | FPGA | 90 nm | Bitstream CRC, no encryption | High success |
| Spartan-6 | FPGA | 45 nm | AES-256 (optional), readback disable | Feasibility — depends on security bits |
| Virtex / Virtex-E | FPGA | 220–180 nm | Readback disable bit | High success |
| Virtex-II / Virtex-II Pro | FPGA | 130 nm | Readback disable, optional 3DES | Feasibility — unencrypted: high; encrypted: case-by-case |
| Virtex-4 | FPGA | 90 nm | AES-256, readback disable | Feasibility |
| Virtex-5 | FPGA | 65 nm | AES-256, HMAC | Feasibility — limited |
| Artix-7 / Kintex-7 / Virtex-7 | FPGA (7-series) | 28 nm | AES-256 + HMAC-SHA-256, eFUSE/BBRAM key | Feasibility — encrypted devices rarely recoverable |
| Zynq-7000 | SoC (ARM + FPGA) | 28 nm | AES-256, Secure Boot, RSA authentication | Feasibility — PL bitstream + PS firmware evaluated separately |
| UltraScale / UltraScale+ | FPGA / MPSoC | 20–16 nm | AES-GCM-256, RSA-4096, DPA countermeasures | Not currently supported |
Key takeaway: Older CPLD families (XC9500, CoolRunner) and non-encrypted SRAM FPGAs (Spartan-3, Virtex-E) have the highest recovery rates. Once AES-256 encryption is enabled on 7-series or newer parts, bitstream extraction becomes extremely difficult or impossible with current techniques.
How Xilinx Protection Mechanisms Work
CPLD Fuse Maps — Security Fuse
Xilinx CPLDs like the XC9500XL store configuration in non-volatile flash cells. A single “security fuse” disables JTAG readback. Our decapsulation and microprobing workflow bypasses this fuse at the silicon level. The process is destructive to the package but preserves the die. Typical turnaround: 5–10 working days for XC9500-series parts.
SRAM FPGA Bitstream — Readback Disable
Spartan and Virtex SRAM-based FPGAs load their configuration from an external SPI flash or parallel NOR at every power-up. If the bitstream itself is not encrypted, we can often read the external configuration memory directly — no die-level work needed. When the FPGA’s internal readback-disable bit is set but no encryption is used, the external flash still contains the plaintext bitstream.
AES-Encrypted Bitstream
Starting with Virtex-II Pro (3DES) and Virtex-4 (AES-256), Xilinx offered bitstream encryption. The decryption key is stored either in battery-backed SRAM (BBRAM) or in one-time-programmable eFUSEs on the die. Recovering an encrypted bitstream without the key requires extracting the key from silicon — a process that is expensive, time-consuming, and not guaranteed. For 7-series and newer devices with AES-GCM plus HMAC authentication, we generally advise clients that recovery is not feasible with current methods.
Our Xilinx IC Unlock Process
- Feasibility assessment (free) — Send us the part number (e.g., XC3S400-4PQG208C), a photo of the board, and proof of ownership. We evaluate the security configuration within 1–2 business days.
- Quotation — We provide a fixed-price quote with an estimated success probability. CPLD jobs typically start around $400–$800; FPGA jobs with encryption range from $1,500 upward depending on complexity.
- Device extraction — If the IC is soldered to a board, we desolder it using hot-air rework at the correct profile for the package (BGA reflow at 245 °C peak for Pb-free). Alternatively, clients can ship loose parts.
- Readback / decapsulation — For unencrypted parts, JTAG or external-flash readback. For fuse-protected CPLDs, chemical decapsulation (fuming HNO₃ or H₂SO₄ + H₂O₂) followed by microprobing.
- Verification — Extracted data is programmed onto a blank device of the same part number and functionally tested against the original board’s behavior.
- Delivery — You receive the bitstream file (.bit / .jed / .mcs), a verification report, and optionally a set of pre-programmed replacement ICs.
What Can Go Wrong — Honest Limitations

We turn away or fail roughly 15–20% of Xilinx FPGA jobs, almost always because of encryption. Specific failure modes include:
- BBRAM key loss — If the battery-backed key storage has lost power, the key is gone and the encrypted bitstream on the external flash is unrecoverable.
- Die damage during decap — Aggressive acid etching on fine-pitch 28 nm dies can destroy bond pads. We mitigate this with laser-assisted decapsulation, but the risk is non-zero.
- Partial bitstream corruption — External SPI flash with worn-out sectors may yield an incomplete image. We can sometimes reconstruct missing frames, but not always.
- Anti-tamper eFuse — Some Zynq and 7-series parts blow a “disable” eFuse if tampering is detected, permanently bricking JTAG access.
We always disclose these risks before work begins. If we assess low probability of success, we will tell you upfront rather than charge for a likely failure.
Xilinx vs. Other Programmable Logic Vendors
Xilinx is one of several FPGA/CPLD vendors our lab handles. The protection approaches differ significantly across manufacturers, which affects recovery strategy:
- Altera (Intel) FPGA and CPLD recovery — MAX II/V CPLDs use UFM-based protection; Cyclone and Stratix families use AES with volatile key storage.
- Lattice iCE40 and ECP readback — iCE40 parts often lack encryption entirely; ECP/MachXO families use 128-bit AES.
- Actel / Microsemi flash-based FPGA recovery — ProASIC3 and IGLOO parts use flash-based configuration with AES-128 and FlashLock.
- QuickLogic eFPGA readout — Antifuse-based devices are one-time programmable and require different extraction methods entirely.
Deliverable Formats
| Format | Use Case |
|---|---|
| .BIT | Direct FPGA configuration via JTAG (Vivado / ISE) |
| .JED | CPLD fuse map for ISE iMPACT or third-party programmers |
| .MCS / .BIN | SPI flash image for indirect programming |
| .SVF | Serial Vector Format for production boundary-scan tools |
| Raw binary dump | For client-side analysis or migration to a new platform |
Authorization & Legal Framework
Every Xilinx IC unlock engagement requires documented proof of ownership or a written authorization letter from the IP holder. We operate under mutual NDA and can provide a standard agreement or work under your company’s template. For more detail on our compliance process, review our authorization and trust policies.
Check feasibility for your project
Send the chip marking or board details and tell us what you need to recover. Add clear photos if available.
Request a feasibility reviewCan you recover a bitstream from a Xilinx 7-series FPGA with AES encryption enabled?
In most cases, no. Xilinx 7-series devices (Artix-7, Kintex-7, Virtex-7) use AES-256-GCM encryption with HMAC-SHA-256 authentication. If the encryption key was stored in BBRAM and the battery is dead, the key is permanently lost. If stored in eFUSEs, extraction requires advanced silicon-level techniques with low and unpredictable success rates. We evaluate each device individually but advise clients to expect a low probability of recovery on encrypted 7-series parts.
How long does a Xilinx CPLD unlock typically take?
For XC9500, XC9500XL, and CoolRunner-II CPLDs, our standard turnaround is 5–10 working days from the time we receive the device. Rush service (3 working days) is available at a surcharge. The feasibility assessment itself takes 1–2 business days and is free.
Is it possible to read the external SPI flash instead of unlocking the FPGA itself?
Yes — and this is often the fastest path. Xilinx SRAM FPGAs load configuration from an external flash at every power cycle. If the bitstream stored in that flash is not AES-encrypted, we can desolder the flash chip (typically a Winbond W25Q or Micron N25Q) and read it directly with a standard programmer. This avoids any die-level work on the FPGA entirely.
Do you support Xilinx Zynq UltraScale+ MPSoC recovery?
Not currently. The ZU-series MPSoCs implement RSA-4096 authentication, AES-GCM-256 encryption, and hardware DPA countermeasures that place them beyond our current extraction capabilities. We do support the original Zynq-7000 on a case-by-case basis when the PL bitstream is unencrypted or the PS boot image uses minimal security.
What if my Xilinx part is soldered in a BGA package — can you still extract it?
Yes. We routinely desolder BGA packages (FG256, FG484, FF676, and larger) using profiled hot-air reflow. We use appropriate preheat ramps and peak temperatures (typically 245 °C for Pb-free assemblies) to avoid thermal shock. If you prefer, you can desolder the part yourself and ship it loose — just use proper ESD packaging.
Related IC Unlock Services
Beyond Xilinx programmable logic, our lab handles firmware recovery across a wide range of vendors. If your board contains companion microcontrollers or other programmable ICs alongside a Xilinx FPGA, we can often process them in the same engagement:
Check feasibility for your project
Send the chip marking or board details and tell us what you need to recover. Add clear photos if available.
Request a feasibility reviewWhat do you need to recover?
Send the full marking or board photos, sample condition and required outcome. Ask for an NDA before sharing confidential files. Scope and sample handling are confirmed individually.
The article title is carried into the contact form. Add your own details and review the enquiry before sending.