Bao'An Shenzhen China

FPGA Bitstream Extraction | Xilinx, Altera & Lattice

Published · About 9 min read · PCB-Copy

On this page
  1. What Is FPGA Bitstream Extraction?
  2. Why Engineers Need FPGA Bitstream Readback
  3. How FPGA Bitstream Extraction Works
  4. Vendor-Specific Security Levels
  5. What You Get After Extraction
  6. Realistic Constraints and Failure Modes
  7. Our FPGA Bitstream Extraction Process
  8. FPGA Bitstream Extraction vs. MCU Firmware Readout
  9. When External Memory Holds the Key

What Is FPGA Bitstream Extraction?

FPGA bitstream extraction is the process of reading back the configuration data—the bitstream—from a programmed Field-Programmable Gate Array. This bitstream defines the logic, routing, and I/O assignments that make the FPGA behave as its designer intended. Authorized extraction is used for legacy design recovery, failure analysis, IP verification on boards you own, and cloning obsolete systems where original source files have been lost. The feasibility depends heavily on the vendor, device family, and which security fuses have been set.

Why Engineers Need FPGA Bitstream Readback

fpga bitstream extraction: Technician probing JTAG header on an FPGA board for bitstream readback

Source HDL files get lost. Engineers leave companies. Acquisition targets ship hardware with no design archive. When you own the board and the IP but lack the original project files, bitstream extraction is often the only path to recovering the design. Common scenarios include:

  • Legacy equipment maintenance — industrial controllers, medical devices, or military systems running Spartan-3 or Cyclone II parts that are 15+ years old with no surviving Vivado/Quartus project.
  • Failure analysis & quality audit — verifying that a contract manufacturer programmed the correct bitstream onto production boards.
  • Design migration — reading back a bitstream from a discontinued FPGA to begin porting logic to a current-generation device.
  • Prototype recovery — retrieving a one-off configuration from a working prototype when the development laptop was lost or wiped.

Authorization and proof of IP ownership are required before any extraction work begins. Our process mirrors the same legal safeguards we apply to IC readout and break-IC services.

How FPGA Bitstream Extraction Works

JTAG Readback

Most FPGA families expose a JTAG (IEEE 1149.1) port that supports a READBACK command. When security bits are not set, a boundary-scan tool can shift out the entire configuration frame data through TDO. Xilinx devices use the CAPTURE and READBACK instructions; Intel (Altera) devices use a similar JTAG state machine flow. Readback through JTAG is non-destructive and can be performed in-system without desoldering the chip.

SPI / Configuration Memory Dump

Many boards store the bitstream in an external SPI flash (e.g., Winbond W25Q series, Micron N25Q). If the FPGA itself is locked but the flash is not, we desolder or clip onto the flash and read its contents directly. This yields the raw bitstream file. For boards using serial EEPROM configuration memories, the same principle applies—devices like the W25Q64 or AT24C512 are commonly found alongside FPGAs and can often be read without special attack methods.

Side-Channel and Decapping (Advanced)

When encryption fuses are blown, standard readback is blocked. Advanced techniques—power analysis (DPA/SPA), electromagnetic probing, or physical decapping with focused-ion-beam (FIB) editing—may be attempted on older families. Success rates vary widely. Xilinx 7-series AES-256 encryption, for example, has no publicly known practical break. Older Spartan-3AN devices with DES-level protection have documented academic vulnerabilities. We evaluate each case individually and will tell you upfront if extraction is not feasible.

Vendor-Specific Security Levels

Vendor / Family Security Mechanism Readback Difficulty Extraction Notes
Xilinx Spartan-3 No encryption; optional readback disable bit Low–Medium If readback disable is not set, JTAG readback succeeds in minutes. If set, external flash dump is the fallback.
Xilinx Spartan-6 AES-256 bitstream encryption (optional) Medium–High Unencrypted designs: straightforward. Encrypted: key stored in battery-backed SRAM—power interruption erases it.
Xilinx 7-Series (Artix/Kintex/Virtex) AES-256 + HMAC-SHA-256 High–Very High No known practical attack on correctly implemented encryption. Readback only if security bits are clear.
Intel Cyclone II/III No on-chip encryption; volatile SRAM config Low Bitstream must be read from external config flash or captured during boot via logic analyzer.
Intel Cyclone IV/V AES-128/256 (key in OTP fuses) Medium–High Unencrypted: JTAG readback. Encrypted: OTP key is not extractable by standard means.
Intel MAX 10 AES-256 + on-chip flash High Non-volatile internal flash complicates physical access. Encrypted designs resist readback.
Lattice iCE40 No encryption on most variants Low SPI flash readout or JTAG readback typically succeeds. Open-source toolchain (Project IceStorm) aids analysis.
Lattice ECP5 AES-128 (optional) Medium Unencrypted: standard readback. Encrypted: key in non-volatile storage, no public break.
Lattice MachXO2/3 AES-128, OTP/flash key storage Medium–High Feature row and security bits must be assessed per-device.

The table above summarizes general difficulty. Real-world feasibility depends on whether the original designer actually enabled encryption and set the security fuses—many production boards ship with security features left at default (disabled), even on families that support strong encryption.

What You Get After Extraction

A successful FPGA bitstream extraction delivers:

  • Raw bitstream file — .bit (Xilinx), .sof/.rbf (Intel), .jed/.bit (Lattice) — suitable for reprogramming identical or compatible devices.
  • Configuration memory image — if extracted from external flash, a .bin dump that can be written back to a replacement flash IC.
  • Partial netlist recovery (optional) — using tools like Project X-Ray (Xilinx 7-series) or Project IceStorm (Lattice iCE40), we can reverse-engineer the bitstream into a gate-level netlist for analysis or migration. This adds 5–15 working days depending on design complexity.

Netlist recovery is not the same as recovering the original HDL source code. The output is a flattened gate-level representation. Reconstructing readable RTL from that requires significant manual engineering effort and is quoted separately.

Realistic Constraints and Failure Modes

PCB showing BGA FPGA alongside external SPI configuration flash memory

We are transparent about what can go wrong:

  • Encryption with intact keys — if AES encryption is enabled and the key has not been compromised (e.g., battery-backed SRAM key is still powered), extraction of meaningful data is not possible with current methods on modern families.
  • Anti-tamper fuses — some devices (Xilinx UltraScale+, Intel Stratix 10) include eFuse-based tamper detection that permanently disables JTAG after a threshold of failed attempts.
  • Bitstream format changes — even within a vendor family, bitstream formats differ between speed grades, package variants, and silicon revisions. A bitstream from an XC7A35T-1CPG236 will not program an XC7A35T-2CPG236 without modification.
  • Partial reads — power glitches during readback, corroded JTAG pads, or damaged configuration flash can yield incomplete data. We verify CRC/checksum integrity before delivering.

Our FPGA Bitstream Extraction Process

  1. Feasibility assessment (free) — send us the FPGA part number, board photos, and a description of your ownership/authorization. We identify the security level and estimate success probability within 1–2 business days.
  2. Non-destructive attempt — JTAG readback and/or external flash dump. Turnaround: 3–7 working days for standard cases.
  3. Advanced recovery (if needed) — side-channel analysis or decapping on older devices. Turnaround: 10–25 working days. Quoted only after feasibility confirms a reasonable chance of success.
  4. Verification — we reprogram a blank FPGA (same part) with the extracted bitstream and verify functional equivalence on a test bench or your board.
  5. Delivery — bitstream file, configuration image, extraction report, and optional netlist delivered under NDA.

This workflow parallels the approach we use for microcontroller firmware recovery. If your board also contains locked MCUs—such as an nRF52840 or GD32E230—we handle both the FPGA and MCU extraction in a single project to reduce turnaround and cost.

FPGA Bitstream Extraction vs. MCU Firmware Readout

Factor FPGA Bitstream MCU Firmware
Data type Configuration frames (LUTs, routing, I/O) Machine code (ARM, MIPS, etc.)
Storage Volatile SRAM (most) or on-chip flash (some) On-chip flash / OTP
Encryption AES-128/256 per vendor Read-protection levels (RDP, CRP, etc.)
Readback interface JTAG / SPI config flash SWD / JTAG / bootloader
Netlist recovery possible? Yes (bitstream → gates) Yes (binary → disassembly)
Typical turnaround 3–25 working days 2–15 working days

When External Memory Holds the Key

On many production boards, the FPGA bitstream lives in an SPI or I²C EEPROM that sits right next to the FPGA. These configuration memories—93C46, M95080, or larger SPI NOR flash parts—are often unprotected even when the FPGA itself has readback disabled. Reading the external memory is the fastest, lowest-risk extraction path and succeeds in a large percentage of cases we handle.

Is FPGA bitstream extraction legal?

Yes, when performed on devices and designs you own or are authorized to access. Common legal bases include original IP ownership, legacy maintenance contracts, and authorized failure analysis. We require proof of ownership or written authorization before starting work, and all projects are covered by NDA. We never assist with extracting third-party proprietary IP without authorization.

Can you extract an AES-encrypted bitstream from a Xilinx 7-series FPGA?

If AES-256 encryption is enabled and the key is intact, no practical extraction method exists for Xilinx 7-series devices as of 2024. However, many boards that could use encryption were shipped without it enabled. We check the security register during our free feasibility assessment—roughly 40% of “encrypted family” boards we receive actually have security bits clear.

What if my FPGA is soldered down and I cannot access JTAG?

We can probe JTAG test points on the PCB, solder fine-pitch fly wires to BGA pads, or read the external configuration flash directly. If the board has no accessible JTAG and no external flash, we evaluate whether decapping or interposer-based probing is viable for your specific device and package.

How much does FPGA bitstream extraction cost?

Pricing depends on the FPGA family, security level, and whether netlist recovery is needed. Non-encrypted readback from external flash typically starts around $300–$600 USD. Encrypted or advanced-attack cases range from $1,500 to $5,000+. We provide a binding quote after the free feasibility check—no charge if we determine extraction is not possible.

Can you convert the extracted bitstream back to Verilog or VHDL?

We can produce a gate-level netlist from the bitstream for supported families (Xilinx 7-series via Project X-Ray, Lattice iCE40 via Project IceStorm, and others with proprietary tools). Converting that netlist into clean, readable RTL-level Verilog/VHDL is a separate reverse-engineering effort that we quote on a per-project basis, typically adding 2–4 weeks.

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 review
TURN THE GUIDE INTO A PROJECT QUESTION

What 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.

WhatsApp Send board details