A purchase order that says LPC2114FBD64 and a board that behaves like a CAN gateway are describing two different parts. The 4 in the type number marks the variant that ships without a CAN controller; the LPC2119FBD64, one digit away, carries two. Both are 64-pin LQFP ARM7TDMI-S devices at 60 MHz with 128 KB of on-chip flash and 16 KB of static RAM. When the job is to extract locked LPC2114FBD64 firmware, that absent peripheral is not trivia. It tells you which pins to expect, which interrupt sources the vector table actually services, and whether the image you recover contains any bus stack at all.
Reading The Marking Before Applying Power
The suffix decodes cleanly. FBD is the low-profile quad flat package, 64 is the pin count, and the four digits before it identify the memory and peripheral mix. A 128 KB device with no CAN has 17 flash sectors rather than the 27 found on a 512 KB member of the same line. Confirming the marking against the die is the first job, because a board assembled from a substitute part can carry a different sector map, and every later decision about where to stop reading depends on that map.
Where The Protection Actually Lives
Code Read Protection on this family is one 32-bit word in flash at address 0x000001FC. That address sits inside sector 0, in the gap after the ARM exception vectors that was left free so an FIQ handler could be placed there. The boot ROM reads the word on every reset. Any value other than the three published patterns means no protection. Writing 0x12345678 selects CRP1, 0x87654321 selects CRP2, and 0x43218765 selects CRP3.
This is a different scheme from the one used on the Cortex-M LPC parts, where the equivalent word sits at 0x2FC. Mixing the two up is a common and expensive mistake: a tool that probes the wrong address reports an unlocked device that is in fact locked, and the first erase command it issues destroys the only copy of the code.
What Each Level Closes
CRP1 disables JTAG and the ISP read and compare commands, and it refuses any write to sector 0, but sector erase still works. CRP2 removes most of the useful ISP command set, including write-to-RAM, copy-RAM-to-flash and go; only a full-chip erase remains. CRP3 goes further and, when valid user code is present, disables entry into ISP through the P0.14 pin entirely. On this part the serial bootloader is reached by holding P0.14 low during reset, so a CRP3 device with a working application offers almost no external handle.
There is one more condition worth checking first. The boot ROM only considers user code valid when the word at 0x14 is the two’s complement of the sum of the other seven vectors, making the eight add up to zero. If that checksum is wrong the part falls into ISP regardless of the peripheral mix. A damaged or half-erased sector 0 therefore changes the protection behaviour, not just the code.
Why A Full Erase Is Not A Recovery
Every official route out of CRP on this family goes through an erase. That is the wrong direction when the firmware is the thing you need. A non-invasive read has to work with the boot ROM’s decisions rather than against them, and an invasive one has to reproduce the array contents including the check bytes that the flash controller uses. On LPC213x-class arrays with error correction, discarding those bytes produces a file that looks complete and fails verification later.
The 128-bit-wide flash interface and the accelerator are also worth remembering. Code executes at full clock rate directly from the array, which is why these parts need no shadow RAM copy and why a live bus capture rarely shows a clean linear image. Thumb code compresses the program by more than thirty percent, so the same 128 KB can hold considerably more application than an ARM-only build would suggest.
Practical Sequence
We identify the bootloader revision before choosing a path, because early silicon implemented only the single 0x87654321 level while later /00 and /01 devices expose the three-level scheme. CRP changes only take effect after a full power cycle, not a reset, so a part that was programmed with a protection word minutes ago may still be open. Related reading: our service scope covers which device states we accept, how protection layers are ordered explains the sequence from a configuration word to a physical array, and this 32-bit ARM readout case shows the same reasoning on a different core. For the two nearest siblings, see the 256 KB LPC2124FBD64 and the CAN-equipped LPC2129FBD64.