Bao'An Shenzhen China

MachXO CPLD Unlock | Feasibility, Cost & Lead Time

Published · About 10 min read · PCB-Copy

On this page
  1. MachXO CPLD Unlock — What Is Actually Possible?
  2. Understanding Lattice MachXO Security Architecture
  3. Feasibility by MachXO Variant
  4. How MachXO CPLD Unlock Works in Practice
  5. What You Receive
  6. Cost and Lead Time for MachXO CPLD Unlock
  7. When MachXO CPLD Unlock Makes Sense
  8. What Can Go Wrong — Honest Constraints
  9. Authorization and Legal Requirements
  10. How MachXO Compares to Other Programmable Logic Unlock
  11. Frequently Asked Questions
  12. Related IC Unlock Services

MachXO CPLD Unlock — What Is Actually Possible?

MachXO CPLD unlock is the authorized recovery of configuration bitstream data from Lattice Semiconductor’s MachXO family of non-volatile CPLDs. When the original design files are lost — due to a departed engineer, a corrupted project archive, or an end-of-life product that still needs maintenance — extracting the locked bitstream may be the only practical path to keeping your hardware alive. Success depends on which MachXO variant you have, which security features were activated during programming, and whether the device is still electrically intact.

Understanding Lattice MachXO Security Architecture

machxo cpld unlock: Lattice MachXO2 CPLD chip soldered on an industrial control board

Lattice’s MachXO line spans four generations: the original MachXO (LCMXO), MachXO2, MachXO3, and MachXO3D. Each generation added progressively stronger protection. Knowing exactly which device sits on your board is the single most important factor in a feasibility assessment.

MachXO (LCMXO) — First Generation

The original MachXO devices (LCMXO256, LCMXO640, LCMXO1200, LCMXO2280) use a relatively simple security model. A single Security Bit can be set to disable external readback of the configuration Flash. When this bit is active, standard JTAG read commands return blank data. However, the underlying Flash cells still hold the bitstream, and physical-layer techniques can often recover it. Our engineers see success rates above 80% on first-generation MachXO parts, provided the device has not been electrically damaged.

MachXO2 — 128-bit AES Encryption

MachXO2 devices (LCMXO2-256 through LCMXO2-7000) introduced 128-bit AES bitstream encryption alongside the security fuse. If AES encryption was not enabled, the recovery path is similar to the first-generation approach — disable or bypass the readback-protect fuse at the silicon level. If AES was enabled, the bitstream stored in Flash is ciphertext, and recovery of a usable design requires either obtaining the original key or decrypting the stream, which is substantially harder and not always feasible.

MachXO3 and MachXO3D — Stronger Barriers

MachXO3 parts add a hardware security engine, one-time-programmable (OTP) key storage, and more robust tamper detection. The MachXO3D further layers on hardware root-of-trust with ECDSA-based secure boot. For MachXO3D devices with full security enabled, bitstream extraction is generally not feasible with current techniques. MachXO3 (non-D) parts fall in a gray zone — feasibility depends on whether the OTP key fuse was actually blown and whether AES was activated.

Feasibility by MachXO Variant

Device Family Security Fuse Only AES Encryption Active Typical Success Rate
MachXO (LCMXO) Recoverable N/A (not supported) ~80–90%
MachXO2 (no AES key) Recoverable — ~70–85%
MachXO2 (AES enabled) — Difficult; case-by-case ~20–40%
MachXO3 (no AES/OTP) Potentially recoverable — ~50–65%
MachXO3 (AES + OTP) — Very difficult <20%
MachXO3D (secure boot) — Not currently feasible ~0%

These figures reflect our lab experience across roughly 120 MachXO-family recovery jobs over the past six years. They are estimates, not guarantees — every device is assessed individually before work begins.

How MachXO CPLD Unlock Works in Practice

Step 1 — Device Identification and Triage

You ship us the target board or the desoldered CPLD. Our engineers read the part marking, confirm the exact variant (package, density, speed grade), and run a non-invasive JTAG scan to check whether the device responds and which security bits report as set. This triage takes 1–2 working days.

Step 2 — Non-Invasive Probing

On devices without AES encryption, we attempt protocol-level exploits — boundary-scan manipulation, undocumented JTAG instructions, and timing-based readback techniques. If the security fuse is the only barrier, this stage often yields the full bitstream without decapping the part.

Step 3 — Semi-Invasive / Invasive Techniques

When non-invasive methods fail, we decap the package using fuming nitric acid or laser decapsulation, then use microprobing or UV/FIB (focused ion beam) techniques to interact directly with the Flash array or reset the security fuse. This is destructive to the package but not necessarily to the die — we can often re-bond and re-package the die afterward if you need the original part back in service.

Step 4 — Bitstream Verification

The recovered bitstream is loaded into Lattice Diamond or Radiant software for functional verification. We compare I/O pin assignments, clock configurations, and logic block utilization against the behavior observed on your original board. You receive the verified JEDEC or bitstream file along with a summary report.

What You Receive

  • Raw bitstream file (.jed or .bit) — ready to program onto a blank replacement CPLD
  • Configuration report — pin mapping, clock tree, and security-fuse status
  • Optional HDL reconstruction — if you need an editable Verilog/VHDL netlist (adds cost and time)
  • Programming instructions — step-by-step for Lattice Diamond Programmer or ispVM

Cost and Lead Time for MachXO CPLD Unlock

Scenario Typical Cost (USD) Lead Time (Working Days)
MachXO / MachXO2 — security fuse only, non-invasive $400 – $800 5 – 8
MachXO2 — AES enabled, semi-invasive $1,200 – $2,500 10 – 15
MachXO3 — case-by-case assessment $1,500 – $3,500 10 – 20
HDL netlist reconstruction (add-on) +$600 – $2,000 +5 – 10

Pricing depends on device density (a 7000-LUT MachXO2 costs more than a 256-LUT part), security level, and whether invasive decapping is required. We provide a firm quote after the triage stage — you pay only the triage fee if we determine the job is not feasible.

When MachXO CPLD Unlock Makes Sense

Decapped IC die under probe station microscope during firmware recovery

The most common scenarios our engineers handle involve legacy industrial controllers, telecom line cards, and medical instrument front-end boards where a MachXO CPLD performs glue logic or I/O multiplexing. The original design house is gone, the product is out of warranty, and the OEM needs to manufacture replacement boards or repair fielded units. In these cases, recovering the CPLD bitstream is far cheaper than a full redesign — especially when the logic is tightly coupled to a specific FPGA or MCU on the same board.

If your board also contains a locked microcontroller alongside the CPLD, we handle multi-device recovery projects regularly. For example, boards pairing a MachXO2 with an STM32 or PIC-family MCU are common in industrial designs. We can recover both devices in parallel — see our guides on STM32L5 firmware recovery and PIC12 MCU unlock for details on those families.

What Can Go Wrong — Honest Constraints

  • Blown OTP fuses: On MachXO3 parts with OTP-stored AES keys, there is no way to “unburn” the fuse. If the key is not recoverable, neither is the plaintext bitstream.
  • Die damage during decap: Roughly 5–8% of invasive jobs result in unrecoverable die damage, especially on older devices with corroded bond pads. Sending two samples when possible reduces risk.
  • Partial bitstream: Occasionally we recover 95%+ of the Flash contents but a few sectors are degraded. This can sometimes be patched if the affected logic is non-critical; otherwise the bitstream may be unusable.
  • AES key space: Brute-forcing a 128-bit AES key is computationally infeasible. If the key cannot be extracted from silicon, AES-encrypted MachXO2/3 devices remain locked.

Authorization and Legal Requirements

We perform MachXO CPLD unlock only for authorized parties — the original IP owner, a licensed manufacturer, or an end-user recovering firmware from hardware they own. Every project requires a signed NDA and a declaration of ownership or authorization before work begins. This protects both parties and ensures compliance with applicable IP law. If you have questions about what qualifies, review our trust and authorization policy.

How MachXO Compares to Other Programmable Logic Unlock

CPLDs and FPGAs differ fundamentally in how configuration data is stored and protected. MachXO devices use on-chip non-volatile Flash, which means the bitstream persists without external memory — a simpler attack surface than SRAM-based FPGAs that load from an external SPI Flash at boot. However, Lattice’s AES implementation on MachXO2/3 is well-regarded and does not have the known weaknesses found in some older Xilinx Spartan-6 or Altera MAX II security schemes.

For engineers dealing with other locked programmable devices on the same board, our lab also handles microcontroller families from Microchip and STMicroelectronics. Recovery approaches for an Atmel AT90 series MCU or a STM32WL wireless MCU follow different techniques but can run concurrently with CPLD work to shorten overall project timelines.

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

Frequently Asked Questions

Can a MachXO2 CPLD be unlocked if AES encryption is enabled?

It depends on whether the AES key can be physically extracted from the device’s key storage cells. If the key is recoverable via microprobing, we can decrypt the bitstream. If the key fuse block is fully protected or degraded, the 128-bit AES cipher cannot be broken computationally. We assess this during triage and give you a clear go/no-go before charging for the full job.

Do I need to desolder the MachXO CPLD before sending it?

No. Ship the entire board — our technicians desolder the device using controlled hot-air rework stations calibrated for BGA and QFP packages. This avoids the risk of damage from improper removal. If you prefer to desolder it yourself, use a thermocouple-monitored profile and pack the bare die in an ESD-safe container.

Is the recovered bitstream identical to the original?

For non-encrypted devices, the recovered bitstream is a bit-exact copy of what was programmed. For AES-encrypted devices where we successfully extract the key, we decrypt to produce the original plaintext bitstream. In both cases we verify functionality against your reference board before delivery.

How does MachXO unlock pricing compare to MCU firmware recovery?

CPLD unlock typically costs more than basic MCU readout because the bitstream is stored in a proprietary Flash architecture rather than standard program memory. A simple PIC14 unlock might start at $150, while a MachXO2 recovery starts around $400. AES-encrypted MachXO jobs approach the $1,200–$2,500 range due to the invasive lab work required.

Can the recovered bitstream be converted back to Verilog or VHDL?

Yes, as an optional add-on. We use commercial and proprietary netlist-extraction tools to reverse the bitstream into a gate-level netlist, then manually clean it into readable RTL. Turnaround adds 5–10 working days depending on device density. The result is an editable HDL source you can re-synthesize and modify.

Related IC Unlock Services

If your project involves multiple locked devices or you are evaluating recovery options across different chip families, these guides cover related work our lab performs:

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