The PIC16F1717 carries the intelligent-analogue direction of the PIC16 generation into a 28- or 44-pin body: 14 KB of flash, 1024 bytes of SRAM, two operational amplifiers, two high-speed comparators and a 10-bit ADC across seventeen channels on the 28-pin build or twenty-eight channels on the 44-pin build. When its configuration-word protection is engaged, our copy encrypted PIC16F1717 heximal service recovers the image from hardware you own, without touching the destructive paths that would erase it.

One die, two footprints

Microchip publishes this part in both a 28-pin package with twenty-five I/O lines and a 44-pin TQFP or QFN with thirty-six, and the silicon is the same underneath. That matters for recovery work because the flash image does not change between footprints: a heximal read from a 44-pin donor programs directly into a 28-pin replacement and vice versa, provided the application does not probe device identifiers at boot. We record the donor package, the ADC channel count it exposes, and the configuration words verbatim in the recovery report, so the swap decision is made from facts rather than assumptions. The internal-memory reasoning behind this is set out in the microcontroller internal storage structure analysis reference.

What the encryption actually closes

On this generation the protection lives in the configuration words: a code-protect bit that, once set, refuses external reads of program flash. Clearing it requires a bulk erase, which destroys the firmware the owner is trying to save, so a disciplined copy encrypted PIC16F1717 heximal job reads the array in its protected state through whatever legitimate channel remains and leaves the erase permanently out of the plan. The two op amps add a second dimension: their gain and feedback settings are register values initialised from constants in flash, and an image verified only by checksum can still mis-bias a sensor front end. Our bench fixture therefore replays representative inputs through the analogue chain and compares the clone’s behaviour against the donor before anything ships. Lawful-access framing is in the unlock microcontroller embedded memory guide.

Peripheral pin selection deserves its own paragraph on this part, because it is the most common source of silent clone failures. The PPS matrix lets the firmware attach the EUSART, PWM outputs or CLC gates to almost any digital pin, so two units running different image generations can disagree about which physical pad carries the transmit line even though the schematic never changed. When we recover a heximal we also record the pin-selection registers captured in their powered state, which lets an engineer prove at a glance that the replacement routes the same signals to the same pads. That single page of notes has shortened more than one acceptance test from an afternoon to a coffee break.

Programming access on the 171x generation is the two-wire ICSP scheme – data and clock – shared with the debug pins, which is convenient for production fixtures and equally convenient for our bench: the same header that flashed the original device reads it back in our capture sequence. We keep the programming voltage requirements of the generation in mind during handling, since the MCLR pin doubles as the high-voltage entry and a marginal socket contact there is the usual reason a read reports empty on a part that is actually protected but healthy.

Duplication and records

Verified images are written into blank parts with configuration words restored and read-back comparison on every unit, through the MCU flash EEPROM data cloning pipeline. Bounded-scope work is described on the partial microcontroller chip cloning page.

Silicon revisions matter on this generation more than on its predecessors, because errata sheets for the 171x family describe oscillator and CLC behaviours that changed between mask steps. Our report records the part marking and revision letter alongside the image, so a re-programmed replacement matches not just the code but the stepping it was written against – a detail that has explained more than one “identical file, different behaviour” puzzle.

Family links

The 28 KB sibling in the same packages is on the PIC16F1718 firmware page, the 40-pin member on the PIC16F1719 flash recovery, and the newer 180xx generation on the PIC16F18046 memory page.

Scope and next step

We accept only units you own or are authorised to service, with the entitlement recorded per job. Send the locked PIC16F1717 and we will confirm the package, quote a fixed fee, and return a verified heximal with its protection map and analogue notes.