Duplicate NRF51802-QCAA-R7 locked EEPROM data
A technician asked to duplicate NRF51802-QCAA-R7 locked EEPROM data should begin with the package marking and the supply rails. On the NRF51802-QCAA-R7 the die is shared across several ordering codes, so the suffix is the first thing worth recording. QCAA is the 32-pin QFN body of the cost-reduced member, and R7 is the 7-inch reel packing code.
Where duplicate NRF51802-QCAA-R7 locked EEPROM data meets the datasheet
The nRF51802 is the cost-sensitive member of the first-generation family, built around the same 16 MHz 32-bit ARM Cortex-M0 core and 2.4 GHz Bluetooth Low Energy 4.2 radio. It targets high-volume beacons and simple sensors where the full peripheral and GPIO budget of the general-purpose part is not needed. A Programmable Peripheral Interconnect still lets events trigger tasks without CPU involvement, so radio timing remains deterministic on a small power budget. Retrieving configuration data from a secured MCU is a separate task from reconstructing the program that once used it.
Separating program and data memory
The memory map is a single 256 Kbyte flash array with 1 Kbyte pages and 16 Kbytes of RAM, with no second flash-density option in this derivative. The UICR page is separate from code flash and stores the readback protection fields together with customer configuration words. A usable heximal names the SoftDevice, the application, the bootloader pointer and the UICR regions explicitly; a flat binary loses the boundaries that a rebuild depends on. Since there is only one flash density, the reported array size over SWD is less informative here than the fitted SoftDevice version. Related device notes on this site cover the wider family: NRF51802-QCAA-T firmware documentation.
Debug-port identification on a locked device
| Item | What the data sheet states |
|---|---|
| Core | 16 MHz ARM Cortex-M0, 32-bit |
| Program memory | 256 Kbytes of flash, 1 Kbyte page granularity |
| RAM | 16 Kbytes of RAM |
| Radio | 2.4 GHz BLE 4.2, 2 / 1 / 0.25 Mbps, +4 dBm |
| Package | 32-pin QFN (5×5) / 48-pin QFN (6×6) |
| Protection | RBPCONF (PALL / PR0) in UICR, SWD debug port |
| Debug / programming | Serial Wire Debug (SWD), ERASEALL through the debug port |
Protection on this cost-reduced part follows the same RBPCONF scheme as the rest of the generation: PALL locks the whole array and PR0 guards the lower code region. When PALL is enabled an external SWD read of the protected flash returns no usable instructions, while the CPU still runs its own application normally. Because only one flash density exists, the SoftDevice version rather than the array size distinguishes two otherwise identical boards. Where a signed release archive exists, comparing its checksum with the board’s observable radio behaviour is the reliable reconstruction route. For background on a neighbouring part, see NRF52810-QFAA-E-R firmware documentation.
The analogue and serial blocks
The peripheral set is deliberately lean: a 10-bit ADC with eight channels, three 16-bit timers, an RTC, UART, SPI, TWI and a reduced GPIO count on the smaller body. PPI still connects radio and timer events without CPU service, and the Cortex-M0 core keeps binaries compact enough that the vector table is a useful archive fingerprint. On the 32-pin QFN option fewer I/O lines reach the board, which constrains how many test points a technician can probe during an identification exercise. A schematic that names the crystal and the reset source shortens any comparison with an archived build considerably. An attack on the lock field is explicitly out of scope; what remains is documenting the microprocessor, its flash geometry and its program file. The ARM and Nordic cross-reference is documented in NRF52820-CFAA-D-R7 firmware documentation.
Footprints, rails and debug pads
Two QFN bodies are orderable: a 5 by 5 mm 32-pin package under the QCAA prefix and a 6 by 6 mm 48-pin package under QFAA, both with the same 256 Kbyte die. The reduced pin count on the 32-pin option is the practical constraint for board access, and it should be recorded before a probe is attached. Supply decoupling needs 100 nF ceramics near each rail pin plus a bulk capacitor, and the exposed pad carries both ground and heat during rework. A comparable recovery note is ARM locked cpu stm32f071rb flash data recovery.
Deliverables for a legitimate owner
Within the first-generation line this is the value option, sharing the Cortex-M0 core, the SoftDevice convention and the SWD interface with the general-purpose and automotive members. On the 32-pin QFN body the exposed pad and the reduced pin-out both constrain rework, which is worth noting in a service quotation. A board laid out for the 48-pin option cannot simply accept the 32-pin body, so the package code is a real design constraint rather than a paperwork detail. On an unlocked sample we return a labelled SoftDevice image, an application heximal and a separate UICR data file. Further reading on adjacent microcontrollers: ARM MCU stm32f031c4 flash memory breaking.
If you need to duplicate NRF51802-QCAA-R7 locked EEPROM data, the practical first step is a written identification report: package marking, full ordering code, debug-port identification, protection state and reported memory sizes, followed by a comparison with any build archive you hold. Our engineers document those findings, explain whether a clean read is possible, and state the erase-all limit before any destructive work is authorised. We work under NDA for legitimate owners and their appointed repair partners, and we do not quote a readout that depends on suppressing a protection state.