Bao'An Shenzhen China

Microchip IC Unlock | PIC & dsPIC Families We Read

Published · About 8 min read · PCB-Copy

On this page
  1. Why Microchip MCUs Need Specialized Unlock Techniques
  2. Supported Microchip Families for Firmware Recovery
  3. How Does Microchip Code Protection Actually Work?
  4. Our Microchip IC Unlock Process — Step by Step
  5. What Can Go Wrong — Honest Constraints
  6. Microchip vs. Other Vendor Families — Key Differences
  7. Who Qualifies for This Service?
  8. Pricing and Turnaround Signals
  9. Frequently Asked Questions
  10. Related IC Unlock Services by Vendor

Microchip IC unlock is the process of reading protected firmware from Microchip Technology microcontrollers — PIC, dsPIC, and the newer SAM (ex-Atmel) lines — when the original source code or programming files have been lost. Our engineers use a combination of non-invasive electrical techniques and, where necessary, semi-invasive decapping to bypass code-protection fuses and extract a verified binary. The service is available only to authorized owners recovering their own intellectual property, under NDA and with proof of ownership.

Why Microchip MCUs Need Specialized Unlock Techniques

Microchip implements code protection differently across families. A PIC16F877A uses a single CP bit that gates external read access through ICSP, while a PIC18F46K22 offers multi-segment protection (boot block, code blocks 0–3, data EEPROM) that can be set independently. The PIC24 and dsPIC33 families add General Segment and Secure Segment partitions with separate code-guard keys.

Because each generation uses a different flash cell geometry (90 nm on older PIC18, 55 nm on PIC32MZ), the physical and electrical parameters of every unlock attempt must be tuned to the specific die revision. A technique that works on a PIC16F1939 will not transfer directly to a PIC16F18877 — the charge-pump voltages, timing windows, and verification checksums are all different.

This is why a generic “chip reader” service rarely succeeds on Microchip parts. Our lab maintains family-specific tooling and reference decapped dies to calibrate each extraction.

Supported Microchip Families for Firmware Recovery

microchip ic unlock: Microchip PIC18 microcontroller prepared for firmware extraction in the lab
Family Typical Parts Protection Scheme Success Likelihood Turnaround
PIC10 / PIC12 PIC10F200, PIC12F675, PIC12F1822 Single CP bit Very high 3–5 days
PIC16 (baseline & mid-range) PIC16F84A, PIC16F877A, PIC16F1939 CP + CPD bits Very high 3–5 days
PIC16 (enhanced mid-range) PIC16F18326, PIC16F18877 CP per region High 5–8 days
PIC18 PIC18F452, PIC18F46K22, PIC18F57Q43 Multi-block CP + WRT High 5–10 days
PIC24 PIC24FJ128GA010, PIC24EP512GU810 Code Guard (GS, SS) Moderate–High 7–12 days
dsPIC30 dsPIC30F6014A FGS / FSS fuses High 5–8 days
dsPIC33 dsPIC33FJ256GP710, dsPIC33EP512MU810 Code Guard Security Moderate–High 7–14 days
PIC32 (MIPS) PIC32MX795F512L, PIC32MZ2048EFH Code protection + boot flash lock Moderate 10–18 days
SAM (Cortex-M) ATSAMD21, ATSAME54 NVM BOOTPROT + security bit Moderate–High 7–12 days

Note: “Moderate” means the outcome depends on the specific silicon revision and protection configuration. We always run a free feasibility assessment before quoting.

How Does Microchip Code Protection Actually Work?

At the simplest level (PIC10/12/16 baseline), a single configuration bit disables the external read path through the programming interface. The flash contents remain intact on-die; only the ICSP read command is blocked. Our non-invasive methods exploit timing and voltage sensitivities in the read-inhibit logic to recover data without opening the package.

On PIC18 and newer 16-bit parts, Microchip added write-protect bits (WRT), table-read-protect bits (TBLPROT), and boot-block isolation. These create independent zones that each require separate handling. A PIC18F46K22, for example, has four code-protection regions plus a data EEPROM protection bit — all five must be addressed individually.

Code Guard Security on PIC24 / dsPIC33

The Code Guard Security (CGS) module partitions flash into a General Segment and a Secure Segment, each with its own access permissions. The Secure Segment can be set to “high security,” which disables all external read/write and restricts even on-chip code from crossing segment boundaries. Recovery from high-security CGS settings requires semi-invasive work — typically UV-assisted fault injection on the security fuse latch — and takes 10–14 working days with a success rate that varies by die revision.

PIC32 Boot Flash and NVM Protection

PIC32MX and PIC32MZ devices protect firmware through a combination of boot-flash write protection, code-protection configuration bits, and, on MZ-class parts, a Crypto Engine that can encrypt flash contents at rest. We can recover code-protected PIC32MX parts reliably. PIC32MZ devices with active crypto present a harder challenge — feasibility depends on the key-storage mechanism used in that particular revision.

Our Microchip IC Unlock Process — Step by Step

  1. Feasibility review: You submit the full part number (e.g., PIC18F46K22-I/PT), the package type, and proof of ownership. We confirm whether the device is in our supported list and estimate success probability within 24 hours.
  2. Device receipt & inspection: We verify the part marking under magnification, check for remarked or counterfeit parts, and confirm the package is undamaged.
  3. Non-invasive attempt: Our engineers apply family-specific electrical techniques — voltage glitching, timing manipulation of the ICSP/JTAG interface, or debug-port probing — to read the flash contents without decapping.
  4. Semi-invasive recovery (if needed): For parts where non-invasive methods are blocked, we chemically decap the package, expose the die, and use UV or micro-probing to defeat the protection fuse. This is common on PIC24 high-security and PIC32 parts.
  5. Verification: The extracted binary is loaded into an unprotected blank device of the same part number and functionally tested against your reference board or documented behavior.
  6. Delivery: You receive the firmware as a .hex or .bin file, along with the configuration-word map so you can reprogram new devices.

What Can Go Wrong — Honest Constraints

Not every Microchip IC unlock attempt succeeds. Here are the real-world failure modes our lab encounters:

  • Die damage during decap: Aggressive acid exposure or mechanical stress can sever bond wires or etch active layers. Our failure rate from decap damage is under 3%, but it is not zero — we always request a spare device when available.
  • Encrypted flash (PIC32MZ Crypto Engine): If the OEM used AES-encrypted boot with a device-unique key, the extracted binary is ciphertext. Without the key, the firmware is unrecoverable.
  • Counterfeit or remarked parts: We occasionally receive parts marked as PIC18F4550 that are actually recycled PIC18F2550 or blank die. Inspection catches this before work begins, but it means the original firmware was never on that physical chip.
  • Fuse-blown OTP devices: Some older PIC16C-series OTP (one-time programmable) parts have physically destroyed fuse links. Recovery requires micro-probing individual memory cells — possible but slow (15–20 days) and expensive.

Microchip vs. Other Vendor Families — Key Differences

Decapped microcontroller die under microscope showing internal flash memory array

Engineers often ask how Microchip compares to other MCU vendors in terms of unlock difficulty. The short answer: Microchip’s 8-bit PIC parts are among the most recoverable devices we handle, while their 32-bit PIC32MZ parts approach the difficulty of modern ARM Cortex-M4 devices from other vendors.

For comparison, Renesas RX and RL78 firmware recovery typically involves a different fuse architecture, and Infineon Tricore and XMC unlock requires vendor-specific debug authentication bypass. If your design uses multiple MCU vendors, we can handle the full BOM — see our pages on Freescale and NXP Kinetis extraction and Holtek HT-series readout for details on those families.

Who Qualifies for This Service?

We perform Microchip IC unlock exclusively for authorized parties. Typical clients include:

  • OEMs who lost source code or build files after a developer departure or server failure.
  • Maintenance teams supporting legacy equipment where the original PIC-based controller board is obsolete and no firmware backup exists.
  • Design houses recovering prototypes for re-spin or audit, where the programmed device is the only remaining copy of the firmware.

We require a signed NDA and a declaration of ownership before starting any work. For details on our legal framework and IP-protection policy, review our Atmel and SAM-series IC unlock page (SAM parts are now under Microchip) or contact us directly.

Pricing and Turnaround Signals

Pricing depends on the family, protection level, and whether semi-invasive work is required:

Category Starting Price (USD) Typical Turnaround
PIC10/12/16 (single CP bit) $150–$300 3–5 working days
PIC18 (multi-block CP) $300–$600 5–10 working days
PIC24 / dsPIC (Code Guard) $500–$1,200 7–14 working days
PIC32MX $600–$1,500 10–18 working days
PIC32MZ (non-encrypted) $1,000–$2,500 14–21 working days
SAM D/E/S (Cortex-M) $400–$1,000 7–12 working days

We charge a flat evaluation fee (applied toward the final cost) and operate on a no-read, reduced-fee policy — if we cannot extract a verified binary, you pay only the evaluation portion.

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 you unlock a PIC with the code-protect bit set if I don’t have the original .hex file?

Yes. The entire purpose of Microchip IC unlock is to recover the firmware when no backup exists. We extract the binary directly from the flash array on the die, bypassing the code-protect fuse. You do not need the original hex file, source code, or programmer — just the physical chip and proof that you own the design.

Will the original chip be destroyed during the unlock process?

Non-invasive extraction leaves the device fully functional. Semi-invasive methods (decapping) destroy the package but read the die. We always recommend sending two devices when possible — one for extraction and one as a functional reference. If only one device exists, we attempt non-invasive methods first.

Is Microchip IC unlock legal?

Recovering firmware from a microcontroller you own or are authorized to service is legal in most jurisdictions, including under the DMCA §1201(f) interoperability and maintenance provisions. We require a signed ownership declaration and NDA before starting. We do not extract firmware for the purpose of cloning or pirating a third party’s proprietary design.

Do you support the newer PIC18-Q and PIC16-Q series?

We have confirmed extraction capability on PIC18F-Q43, PIC18F-Q83, and PIC16F188xx Q-series parts. Newer Q-series revisions are evaluated on a case-by-case basis — submit your exact part number through our feasibility request form and we will confirm within 24 hours.

Can you also extract the EEPROM data, not just the program flash?

Yes. On PIC devices with separate data EEPROM (PIC16F, PIC18F families), we extract both the program memory and the EEPROM contents. The data EEPROM protection bit (CPD) is addressed as part of the same unlock procedure. Both are delivered in the final .hex file.

Related IC Unlock Services by Vendor

If your board uses chips from multiple manufacturers, we likely cover them. Explore our vendor-specific pages for detailed family support:

  • Freescale HCS08, HCS12 & Kinetis readout
  • Renesas RL78, RX, and legacy H8 extraction
  • Infineon XMC and Tricore unlock service
  • Holtek HT-series MCU firmware recovery

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
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