PIC17 Unlock — Recovering Firmware from Microchip’s Legacy 8-Bit MCUs
PIC17 unlock is the process of reading protected firmware out of Microchip’s PIC17C-series microcontrollers — a family that shipped in the mid-1990s and is now long discontinued. Because these devices used relatively simple one-time-programmable (OTP) or windowed-EPROM code protection, authorized recovery is feasible in most cases. Our lab maintains the programmers, UV sources, and micro-probing rigs needed to handle PIC17C42, PIC17C43, PIC17C44, PIC17C752, PIC17C756, PIC17C762, and PIC17C766 parts, with typical turnaround of 5–10 working days and costs starting around USD 300–500 per device.
What Is the PIC17 Family?

The PIC17 series sits between PIC16 and PIC18 in Microchip’s historical product line. It introduced a 16-bit-wide instruction word, hardware multiply, and a deeper stack than PIC16 — features that made it popular in industrial controllers, motor drives, and instrumentation during the late 1990s. All PIC17 parts are Harvard-architecture, 8-bit-data devices fabricated on older CMOS process nodes (typically 0.7–1.0 µm).
Microchip marked the entire PIC17 family as “not recommended for new designs” years ago. No flash-based variants were ever released; every PIC17 stores its program in either mask ROM, OTP EPROM, or UV-erasable windowed EPROM. This has direct implications for how PIC17 unlock is performed.
Key PIC17 Sub-Families
| Sub-Family | Example Parts | Program Memory | Package Options | Code-Protect Bits |
|---|---|---|---|---|
| PIC17C4x | PIC17C42, PIC17C43, PIC17C44 | 2 K–8 K words OTP/Windowed | 40/44-pin DIP/PLCC | 1 CP bit (all-or-nothing) |
| PIC17C7xx | PIC17C752, PIC17C756, PIC17C766 | 8 K–16 K words OTP/Windowed | 64-pin TQFP/PLCC | 2 CP bits (block-selectable) |
How Does PIC17 Code Protection Work?
PIC17 code protection is implemented through one or two configuration bits that, once programmed, disable external read access via the standard ICSP interface. On PIC17C4x devices, a single CP bit protects the entire program space. On PIC17C7xx parts, two bits allow protection of the upper and lower halves independently.
Unlike modern flash MCUs that layer multiple security mechanisms — encrypted debug ports, tamper-detect circuits, or secure boot chains — PIC17 relies solely on blocking the external read path at the configuration level. The actual program data remains intact in the EPROM array. This architectural simplicity is precisely why PIC17 unlock success rates are high compared to newer families.
Protection Levels at a Glance
- CP = OFF: Full read/verify access via ICSP — no unlock needed.
- CP = ON (PIC17C4x): All program memory read-blocked; configuration word still partially readable.
- CP = ON (PIC17C7xx, both bits): Both halves blocked; similar constraint.
Because the protection is a single-layer electrical gate, it does not survive certain micro-invasive techniques that target the configuration latch directly. Our engineers have documented repeatable procedures for every PIC17C part number currently in circulation.
PIC17 Unlock Techniques Our Lab Uses
We combine three approaches depending on the specific part and its packaging:
1. UV-Assisted Reset (Windowed Parts Only)
Windowed (JW-suffix) PIC17 devices expose the die through a quartz window. Controlled UV exposure at 254 nm can selectively erase the configuration bits — including the CP bit — without fully erasing program memory, provided exposure time is tightly controlled (typically 5–30 seconds versus the 15–20 minutes needed for full erasure). This is the least invasive method and preserves data integrity when conditions are right.
2. Micro-Probing / FIB-Assisted Access
For OTP (plastic-packaged) parts where UV access is impossible without decapsulation, we chemically decap the package using fuming nitric acid, then either micro-probe the internal bus or use a focused ion beam (FIB) to sever or bypass the CP latch. This requires a die map for the specific PIC17 revision — our lab maintains reference maps for all common stepping codes.
3. Glitch / Voltage Fault Injection
On certain PIC17C7xx revisions, a precisely timed VDD glitch during the ICSP entry sequence can cause the configuration latch to load in an unprotected state, allowing a normal read cycle. This technique is silicon-revision-dependent and does not work on all lots. We test feasibility before quoting.
What Does PIC17 Unlock Cost?
Pricing depends on the part number, packaging, and technique required. The table below gives realistic ranges — not guaranteed fixed prices, because each device must be assessed individually.
| Scenario | Typical Cost (USD) | Turnaround | Success Likelihood |
|---|---|---|---|
| Windowed PIC17C (JW) — UV method | 300–450 | 5–7 working days | High (≥ 90 %) |
| OTP PIC17C4x — decap + micro-probe | 500–900 | 7–12 working days | Moderate-High (75–90 %) |
| OTP PIC17C7xx — decap + FIB | 800–1 500 | 10–15 working days | Moderate (70–85 %) |
| Glitch injection (revision-dependent) | 400–600 | 5–10 working days | Variable — assessed first |
We charge a non-refundable evaluation fee (typically USD 50–100) that covers initial inspection, die identification, and a go/no-go recommendation. If we proceed and the read fails, you pay only the evaluation fee.
When Does PIC17 Unlock Make Sense?
Authorized PIC17 unlock is justified in a handful of common scenarios:
- Legacy equipment maintenance: The original source code is lost, the developer is unreachable, and the machine must stay in production.
- End-of-life migration: You need to port firmware to a PIC18 or PIC24 replacement and require a verified binary to start from.
- Failure analysis: A field return needs its firmware verified against the golden image.
- IP recovery: You own the design and the only copy lives inside a programmed part.
In every case, we require proof of device ownership or written authorization from the IP holder before work begins. Read more about our PIC24E unlock procedures if you are also dealing with newer Microchip 16-bit parts in the same legacy system.
Risks, Failure Modes, and Honest Caveats

No lab should promise 100 % success on any IC unlock engagement. Here are the specific risks with PIC17:
Die Damage During Decapsulation
Older CMOS metallization (aluminum, not copper) is more susceptible to acid attack. If the bond wires or passivation layer are compromised, micro-probing becomes impossible. We mitigate this with laser-decap for critical specimens, but it adds cost.
EPROM Charge Degradation
OTP EPROM cells lose charge over decades — especially devices stored in high-temperature environments. If the floating-gate charge has decayed below the read threshold, the data is physically gone. We can sometimes recover partial images and flag suspect bytes, but full recovery is not guaranteed on parts older than 25 years.
Unmarked or Remarked Parts
Counterfeit or remarked PIC17 devices occasionally surface in the surplus market. If the die inside does not match the labeled part number, our die map will not apply, and additional reverse-engineering time is required.
How PIC17 Compares to Other Microchip Families
If you are evaluating unlock feasibility across multiple Microchip devices in a single system, this comparison helps set expectations:
| Family | Memory Type | Protection Complexity | Unlock Difficulty |
|---|---|---|---|
| PIC17C | OTP / EPROM | Low (1–2 CP bits) | Low–Moderate |
| PIC24H (flash) | Flash | Medium (GCP, GSS, CSS bits) | Moderate |
| PIC32MZ (flash) | Flash | High (boot flash protection, code-guard) | High |
| dsPIC33C (flash) | Flash | Medium-High | Moderate–High |
For PIC24H unlock or PIC32MZ unlock, the techniques differ significantly because flash-based devices support re-lock and have more granular protection partitions. The PIC17’s EPROM-based architecture is, paradoxically, easier to work with precisely because it is older and simpler.
Our PIC17 Unlock Process — Step by Step
- Submit your request — provide the exact part number (including revision suffix), quantity, and a brief description of why the firmware is needed.
- Evaluation — we inspect the device under magnification, verify the die marking, and determine which technique applies. You receive a go/no-go report within 2–3 working days.
- Quotation — if feasible, we issue a fixed-price quote with an estimated success probability and turnaround.
- Unlock & verification — firmware is read out, checksummed, and (where possible) loaded into a blank device for functional verification.
- Delivery — you receive the binary file (.hex or .bin), a read log, and optional programmed replacement parts.
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 reviewFrequently Asked Questions About PIC17 Unlock
Can you unlock a PIC17C44 in a plastic DIP package?
Yes. Plastic (OTP) PIC17C44 parts require chemical or laser decapsulation to expose the die, followed by micro-probing or FIB work to bypass the CP bit. Success rates are typically 75–90 %, and turnaround is 7–12 working days. The evaluation step confirms feasibility before you commit.
Is PIC17 unlock legal?
Firmware recovery is legal when performed on devices you own or when authorized by the IP holder. Common lawful scenarios include legacy maintenance, failure analysis, and end-of-life migration. We require written proof of ownership or authorization before starting any work. Unauthorized copying of third-party firmware is not a service we provide.
What if the EPROM data has degraded after 25+ years?
Charge loss is a real risk with aged OTP EPROM. We perform a marginal-read sweep at multiple VDD levels to maximize bit recovery. If degradation is detected, we flag suspect addresses in the output file. Partial recovery is sometimes possible even when full recovery is not.
Do you also handle dsPIC and PIC32 parts?
Yes. Our lab supports a wide range of Microchip families, including dsPIC33C devices and PIC32MM parts. Each family uses different protection schemes, so techniques and pricing vary. Submit a feasibility request with your specific part numbers for an accurate assessment.
Can you program the recovered firmware into a new chip?
For PIC17, replacement programming is only possible if you supply blank windowed (JW) parts or NOS OTP stock, since the family is discontinued. Alternatively, we can assist with porting the binary to a pin-compatible PIC18 variant for long-term production continuity.
Related IC Unlock Services
Working across multiple legacy boards often means dealing with more than one locked MCU. These related pages cover other families our engineers handle regularly:
- dsPIC33E-CH unlock — Microchip’s high-performance DSC family
- AT90 unlock — Atmel/Microchip AVR legacy parts
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 reviewWorking 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