Bao'An Shenzhen China

MachXO CPLD Crack | Protection Levels & Recovery

Oct 29, 2026  /  PCB COPY

machxo cpld crack: Lattice MachXO2 CPLD in TQFP-144 package on a PCB with JTAG header

MachXO CPLD Crack — What Is Actually Protected?

A MachXO CPLD crack refers to the authorized extraction or recovery of the configuration bitstream from a Lattice MachXO-family Complex Programmable Logic Device when the original project files have been lost. Lattice implements multiple protection layers—security-bit fuses, password-based JTAG locks, and OTP sector write-protection—that make bitstream readback non-trivial. Recovery feasibility depends entirely on which combination of these protections was enabled at programming time, the specific MachXO variant (MachXO, MachXO2, MachXO3, MachXO3D), and whether the device uses flash or OTP configuration memory.

How Lattice MachXO Security Works

machxo cpld crack: Lattice MachXO2 CPLD in TQFP-144 package on a PCB with JTAG header

Unlike microcontrollers that store linear firmware, CPLDs store a configuration bitstream that defines the logic fabric. Lattice’s protection strategy for the MachXO line centers on three independent mechanisms that can be layered.

1. Security Bit (Readback Disable)

The most common protection. When the security bit is programmed (set to “1”), the JTAG and SPI readback commands return blank or scrambled data. On MachXO2 and MachXO3 devices, this is a one-time-programmable fuse—once set, it cannot be cleared by erasing the device. On the original MachXO (LCMXO series), the security bit resides in flash and can sometimes be cleared with a full device erase, but this also destroys the bitstream you are trying to recover.

2. Password Protection (MachXO2/MachXO3)

MachXO2 and later variants support a 128-bit password lock on the JTAG/I²C/SPI programming interfaces. If the password is unknown, standard programming tools (Lattice Diamond Programmer, Deployment Tool) refuse access. The password is stored in dedicated OTP fuses, not in the main configuration flash. Brute-forcing a 128-bit key space is computationally infeasible with current technology—roughly 3.4 × 10³⁸ combinations.

3. OTP Sector Lock

MachXO2 devices include a dedicated OTP (one-time-programmable) configuration sector alongside the flash sector. If the design was programmed into the OTP sector and the security bit is set, the bitstream is permanently locked. Flash-sector-only designs with the security bit offer slightly more recovery options because the flash itself can sometimes be accessed through non-standard interfaces at the die level.

Protection Levels at a Glance

Protection Combination Device Family Recovery Difficulty Typical Outcome
No protection (security bit = 0, no password) All MachXO variants Trivial Full bitstream readback via JTAG/SPI in minutes
Security bit only (flash sector) LCMXO (original) Moderate Die-level flash analysis may recover bitstream
Security bit only (flash sector) MachXO2 / MachXO3 High Requires physical-layer techniques; 60–75 % success range
Security bit + 128-bit password MachXO2 / MachXO3 Very High Password recovery adds significant time; feasibility case-by-case
OTP sector + security bit MachXO2 Extreme OTP fuses are permanent; recovery is rarely viable
AES-128 encryption + security bit MachXO3D Not feasible Hardware secure element; no known practical attack

What Changes Between MachXO Generations?

Lattice has progressively hardened security across the MachXO line. Understanding the generation matters because the same “security bit set” label hides very different physical implementations.

Original MachXO (LCMXO-640 through LCMXO-2280)

These 130 nm devices use a single flash configuration sector. The security fuse disables JTAG readback but does not encrypt the bitstream. Our engineers have recovered bitstreams from LCMXO parts with the security bit set by accessing the flash array directly—success rates are highest on the larger-die variants (LCMXO-2280) because the flash cells are physically larger and easier to probe.

MachXO2 (LCMXO2-256 through LCMXO2-7000)

Manufactured on a 65 nm process. Adds the 128-bit password, dual configuration sectors (flash + OTP), and TransFR (transparent field reconfiguration). The smaller process node makes physical probing more difficult, and the OTP fuse bank for the security bit is separate from the configuration flash. When only the security bit is set and the design lives in flash, recovery is still possible but requires decapsulation and careful die-level work—typical turnaround is 10–20 working days.

MachXO3 / MachXO3D

MachXO3 (LCMXO3-L/LF series) uses a 65 nm process with enhanced tamper detection. MachXO3D adds a hardware secure element with AES-128 bitstream encryption and a unique device secret. If the MachXO3D’s encryption is active, the bitstream is encrypted at rest in flash—even physical extraction yields ciphertext that cannot be decrypted without the device key. We do not accept MachXO3D encrypted-bitstream recovery requests because there is no realistic path to success.

Realistic MachXO CPLD Crack Process

When a client contacts us for a MachXO CPLD crack, the workflow follows a strict feasibility-first approach. We never proceed without confirming the requester’s ownership or authorization.

  1. Device identification. Client provides the full part number (e.g., LCMXO2-4000HC-4TG144C). This tells us the generation, die size, package, and speed grade.
  2. Protection assessment. We attempt a standard JTAG/SPI readback. If it fails, we check whether a password prompt appears (MachXO2/3) and whether the device responds to erase commands—this indicates flash vs. OTP sector usage.
  3. Feasibility report. Within 2–3 working days we issue a written assessment: which protections are active, estimated success probability, cost range, and turnaround.
  4. Physical recovery (if approved). Decapsulation, die imaging, and flash-cell state extraction using micro-probing or optical fault analysis. Bitstream is reconstructed and verified against the device’s JEDEC file format.
  5. Verification. The recovered bitstream is programmed into a blank MachXO device of the same part number. Functional testing confirms logic behavior matches the original.

For context, the process differs significantly from MCU firmware recovery. Where an STM32L1 readout protection bypass targets linear flash memory containing ARM instructions, a CPLD crack targets a bitstream that defines LUT configurations, routing interconnects, and I/O settings. The data format and verification methods are fundamentally different.

What Can Go Wrong

Decapsulated IC die under probe station microscope during firmware recovery

Transparency matters. Here are the failure modes our engineers encounter most often during MachXO CPLD recovery:

  • Die damage during decapsulation. MachXO2 packages (especially TQFP-144 and csBGA) have thin die-attach layers. Aggressive acid decapsulation can crack the die or dissolve bond pads. We use laser decapsulation for BGA packages to minimize risk.
  • Ambiguous flash-cell states. On 65 nm MachXO2 parts, flash cells near threshold voltage boundaries can read as indeterminate. This introduces bit errors in the recovered bitstream—typically 0.01–0.1 % of total bits—that must be corrected through logic analysis.
  • OTP-locked devices. If the configuration resides in the OTP sector, fuse states are permanent and the physical extraction window is narrower. Success drops below 40 %.
  • Encrypted MachXO3D. As noted, we decline these. Any vendor claiming 100 % success on AES-encrypted MachXO3D parts is not being honest.

Who Needs MachXO CPLD Firmware Recovery?

The most common scenarios we handle:

  • Legacy industrial controllers where the original VHDL/Verilog source was lost after a design-house closure. The MachXO CPLD is the only remaining copy of the logic.
  • Obsolete equipment repair where a failed MachXO part must be cloned to a replacement device to keep a production line running.
  • IP audit and documentation where a company acquires hardware assets and needs to understand or re-document the CPLD logic for compliance or redesign.

Similar authorized recovery work applies across programmable logic and MCU families. Engineers working with Microchip parts may also need PIC32MZ firmware extraction or dsPIC33C flash readout under comparable ownership-verified conditions.

MachXO vs. Other CPLD/FPGA Families

Feature Lattice MachXO2 Xilinx CoolRunner-II Intel MAX 10
Configuration memory Flash + OTP Flash only Flash (dual-boot)
Security fuse type OTP (permanent) OTP (permanent) Volatile (SRAM key) + OTP option
Encryption None (MachXO3D: AES-128) None AES-256 (optional)
Password lock 128-bit Not available Not available
Recovery difficulty (security bit only) High Moderate High

This comparison helps engineers assess whether migrating a locked design to a different CPLD family simplifies or complicates future recovery scenarios.

Authorization and Legal Requirements

All MachXO CPLD crack work at our facility requires documented proof of ownership or written authorization from the IP holder. We operate under NDA for every project. Bitstream recovery is performed strictly for the purpose of maintaining, repairing, or re-documenting hardware that the client legally owns. For details on our verification process and legal framework, see our trust and authorization policy.

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
Can a MachXO2 CPLD be read back if the security bit is set?

Standard JTAG/SPI readback is blocked when the security bit is programmed. However, because MachXO2 stores the configuration in on-chip flash (not OTP), physical die-level extraction can recover the bitstream in many cases. Success depends on the specific part number, package type, and whether a 128-bit password is also active. Typical success rates for flash-sector-only, security-bit-only devices fall in the 60–75 % range.

How long does MachXO CPLD firmware recovery take?

Feasibility assessment takes 2–3 working days after we receive the device. If physical recovery is needed, expect 10–20 working days for MachXO2 flash-sector devices. Original LCMXO parts with larger die sizes can sometimes be completed in 7–12 days. OTP-sector devices or password-protected parts may require longer timelines.

Is MachXO3D bitstream recovery possible?

Not with current techniques. The MachXO3D includes a hardware secure element that encrypts the bitstream with AES-128 using a device-unique key. Even if the flash contents are physically extracted, the data is ciphertext. We do not accept MachXO3D encrypted recovery requests and recommend clients maintain source backups for these devices.

What is the difference between MachXO flash and OTP sectors?

MachXO2 devices contain two configuration storage areas: a reprogrammable flash sector and a one-time-programmable (OTP) sector. Flash can be erased and rewritten; OTP is permanent. If the design was written to the OTP sector and the security bit is set, recovery options are extremely limited because the fuse states cannot be reset or probed as reliably as flash cells.

Do you need the original Lattice Diamond project files?

No. The entire point of MachXO CPLD crack service is to recover the bitstream when source files are unavailable. We extract the raw bitstream from the physical device and deliver it as a .jed or .bit file compatible with Lattice Diamond Programmer for reprogramming onto a blank device of the same part number.

Related IC Recovery Services

Working on a board like this?

Send the chip marking or two photos. You get feasibility, lead time and price within 24 hours, and the check costs nothing.

Get a free quote

Related reading

WhatsApp Send board details