Short answer: on an unprotected ATF1502AS, ATF1504AS or ATF1508AS, the configuration reads out over JTAG in minutes and you get a verified JEDEC fuse map. Once the security bit is programmed — which is the usual case on production hardware — an ATF15xx CPLD crack becomes a case-by-case job that depends on the exact part, package, and whether the logic inside is combinational glue or a registered state machine.
That distinction is the whole page. Everything below is about how we tell those two situations apart before you spend money, and what the realistic outcome looks like in each.
Why ATF15xx parts land on our bench so often
These are EEPROM-based CPLDs, not SRAM FPGAs. The configuration is non-volatile and sits in the device whether the board has been powered for ten years or ten seconds. So when an industrial controller, a bus interface card, or a motor drive comes in with a dead CPU and no design files, the logic in the ATF1504 is still perfectly intact — it just isn’t in a file anywhere.
The second reason is pin compatibility. The
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