Short answer: most classic Atmel parts are readable. The 8051-based AT89C and AT89S line, the AVR families (ATtiny, ATmega, AT90S), the ATF15xx CPLDs and older AT91/SAM7 ARM parts are the bulk of the Atmel IC unlock work that comes through our lab. Newer Microchip-era SAM D/L parts with a set security bit and a chip-erase-protected DSU are the hard end — sometimes not feasible at all.
This page is written for the person with a dead board or a lost hex file, not for someone browsing definitions. It tells you which families behave predictably, what changes the answer, and what we need from you before we can quote.
Which Atmel families we can usually read
Atmel’s protection mechanisms changed a lot between 1995 and the Microchip acquisition, so “Atmel” is not one problem — it’s five or six different ones. Here’s how they group in practice.
AT89C and AT89S (8051 core)
These are the parts that show up in industrial timers, motor controllers, access panels and elevator boards from the late 90s and 2000s. Protection is a small set of lock bits, and the process nodes are large and old. AT89C51, AT89C52, AT89C2051, AT89S52 and the AT89C51CC01 CAN variant are all routine work for us. The AT89C51 family in particular is one of the most requested parts we see.
AVR — ATtiny, ATmega, AT90S
The AVR line uses lock bits (LB1/LB2) plus fuse bytes to block SPI and parallel programming access to flash and EEPROM. ATmega8, ATmega16, ATmega32, ATmega128, ATmega328/328P, ATtiny13, ATtiny85 and ATtiny2313 are the ones we handle most often. One thing worth flagging: on AVR the EEPROM contents often matter as much as the flash. Calibration values, run hours, unit serial numbers — if you only get the flash back, the board may boot but behave like a factory-fresh unit. We read both.
ATF15xx and ATF750 CPLDs
The ATF1502, ATF1504 and ATF1508 turn up as glue logic on old test equipment and PLC I/O cards. What comes back here is a JEDEC fuse map, not C source — enough to reprogram a fresh device and keep the board alive, not enough to hand a software team a readable design.
AT91 / SAM7 / SAM9 ARM
Older AT91SAM7 parts with the security bit set are workable in many cases. Anything running from external SDRAM with an on-board serial flash is often a different job entirely: the code lives off-chip, and reading a serial flash is far less involved than attacking a locked MCU.
Serial EEPROM and flash on Atmel-marked parts
AT24Cxx and AT25xx devices are usually not protected in a meaningful way. If your board’s parameter data sits in an AT24C02 next to the MCU, say so — that’s frequently the cheap half of the job.
Feasibility by family, honestly
| Family | Protection mechanism | Typical outcome |
|---|---|---|
| AT89C / AT89S (8051) | Lock bits | Usually readable; well-trodden ground |
| ATtiny / ATmega / AT90S | Lock bits + fuses | Usually readable, flash and EEPROM both |
| ATF15xx CPLD | Security fuse | Usually readable as a JEDEC fuse map |
| AT91SAM7 / SAM9 | Security bit, external boot | Case by case; often easier if code is off-chip |
| SAM D / SAM L (Microchip era) | NVMCTRL security bit, DSU lock | Difficult; sometimes not feasible |
| AT24C / AT25 memory | Usually none, or write protect only | Straightforward read |
We will tell you which row your part sits in before you ship anything. If it’s the SAM D/L row, you’ll hear that plainly rather than after two weeks of silence.
What actually changes the answer on an Atmel job
Two chips with the same marking can be different jobs. These are the variables that move the quote and the odds:
- Date code and die revision. An ATmega128 from 2003 and one from 2016 can be different silicon behind the same part number. The revision letter on the package matters.
- Package. DIP and PLCC are the easiest to work with. TQFP is fine. A QFN or a BGA on a SAM part narrows the options and raises cost.
- Whether EEPROM is needed. Flash-only is one job. Flash plus EEPROM plus the fuse and lock byte settings is a fuller one, and it’s what you need if the goal is a drop-in working replacement.
- How many samples you can supply. One irreplaceable chip means we work conservatively and slowly. Two or three identical units means we can be more direct, and it usually shortens the schedule.
- Whether the part is dead. A chip that took an overvoltage event on its I/O may still be readable. One that’s been through a reflow oven twice or has a cracked die usually isn’t. Send it anyway if it’s all you have — but expect a candid assessment.
- Conformal coating or potting. Removing the chip from a potted module is extra work before the interesting part even starts.
What we won’t do is quote a success percentage. Anyone publishing a fixed number across a range this wide is guessing. We’ll tell you whether we’ve done that exact part recently, and if we haven’t, we’ll say that too.
What to send us, and what comes back
Feasibility checks go fast when the first message is complete. Send this:
- The full chip marking — every line on the package top, including date code and revision letter. A sharp macro photo beats retyping it.
- Photos of both sides of the board on a dark background, whole board in frame, no flash glare across the silkscreen.
- Board dimensions and a note on whether the chip is socketed, through-hole, or surface mount.
- How many identical units you have and whether any are expendable.
- One line on deliverables — flash binary only, flash plus EEPROM, fuse settings, or pre-programmed replacement chips.
- What the board does, in a sentence. It helps us guess where the code lives and what to verify against.
What comes back from us: a feasibility read on your specific part, a lead time, and a price. If we think the job is marginal, you get that in writing before you commit. Pricing on Atmel IC unlock work tracks family, package, sample count, whether EEPROM is included, and whether you want programmed chips rather than a file — which is why a real number needs the part in front of us rather than a table on a web page.
Delivery format
Standard output is a binary or Intel HEX of program flash, a separate EEPROM image where one exists, and the fuse and lock byte values as read. For CPLDs it’s a JEDEC file. If you want us to program blank devices and functionally check them in your board, we can do that too — bring or ship a working reference unit so there’s something to compare against.
Why engineers ask for this in the first place
The three cases that fill our queue: the original developer left and took the source with them; the toolchain that built the hex ran on a machine that died in 2011; and the part itself went end-of-life and the replacement needs the same firmware to keep a fleet of installed machines running. Failure analysis is the fourth — you can’t diagnose an intermittent watchdog reset without the code that’s running.
Legacy Atmel parts also come up constantly in obsolescence work. If the plan is to migrate an AT89C52 design to a current part, having the original binary as a behavioral reference is worth more than a specification document written from memory. The same logic applies to STC 8051 derivatives, which is often where these old Atmel designs end up moving.
You need to hold the rights to the firmware you’re asking us to recover, and to comply with the IP law that applies where you operate. Every project runs under NDA, and we don’t retain client code once delivery is confirmed.
Frequently asked questions
Can you unlock an ATmega328P?
Usually, yes — it’s one of the more common AVR parts we handle. Send the full package marking including the revision letter, because different die revisions behave differently. Tell us whether you need the EEPROM as well as the flash; Arduino-derived designs often store calibration or configuration there, and flash alone can leave the board running but misconfigured.
Do you support non-Atmel chips on the same board?
Yes. Mixed boards are normal. We routinely handle a locked Atmel MCU alongside a Xilinx CPLD or FPGA or a second-processor part from another vendor on the same assembly. Quote the whole board in one message rather than opening separate threads, so we can tell you which chip is the real obstacle.
Will the chip still work afterward?
Depends on the approach. Non-invasive methods leave the device intact and usable. Anything that involves opening the package does not — the die is exposed and the part is a one-way sample. We tell you which path we’re planning before we start, so you know whether the chip you ship is coming back alive.
How long does an Atmel job take?
An AT89C or common ATmega part we’ve handled before is typically a few days from receipt. An unusual date code, a SAM part, or a chip that has to come off a potted module runs meaningfully longer because the first stage is characterization rather than reading. We give you a date with the quote and tell you if it slips.
Get your part assessed
Photograph the chip marking and both sides of the board, note how many units you have, and
Send the chip marking or two photos. You get feasibility, lead time and price within 24 hours, and the check costs nothing.Working on a board like this?
Related reading