Attack NRF52810-QCAA-E-R protected flash program
Owners who need to attack NRF52810-QCAA-E-R protected flash program often hold a signed build archive but no longer have the programming fixture. With the NRF52810-QCAA-E-R, that archive plus a debug-port identification report is usually the fastest route to a usable answer. The E build code marks revision 3 silicon with factory-enabled access port protection, QCAA the 32-pin QFN body and R the 13-inch reel.
attack NRF52810-QCAA-E-R protected flash program seen from the programming header
This 192 Kbyte class of the second generation runs a 64 MHz 32-bit ARM Cortex-M4 core with a 2.4 GHz multiprotocol radio supporting Bluetooth Low Energy 5.x at 2 Mbps, 1 Mbps and Long Range PHY. EasyDMA lets peripherals move data to and from RAM without CPU involvement, and the Programmable Peripheral Interconnect routes events between the radio, timers and converters. Supply range is 1.7 to 3.6 V with on-chip DC-DC and LDO regulators, and a 64 MHz internal oscillator allows fast wake-up while a 32.768 kHz crystal keeps the RTC running. The M4 core adds a hardware multiply and DSP instructions over the older M0 line, so a captured binary has a noticeably different instruction mix. Attacking a protection field is not a service we offer; assessing what an authorised owner can archive is.
Memory budget of this member
Program storage is 192 Kbytes of flash arranged in 4 Kbyte pages, paired with 24 Kbytes of RAM on a single bank. The UICR sits in a separate page above code flash and holds APPROTECT, the bootloader address and customer configuration words. With 24 Kbytes of RAM the SoftDevice’s reserved block dominates the map, so recording the link configuration is part of documenting the firmware. With 24 Kbytes of RAM, a connection-heavy stack leaves little headroom, so the link configuration is a useful diagnostic clue on a legacy board. Further reading on adjacent microcontrollers: NRF52810-QFAA-E-R firmware documentation.
Protection behaviour under erase-all
| Item | What the data sheet states |
|---|---|
| Core | 64 MHz ARM Cortex-M4, 32-bit |
| Program memory | 192 Kbytes of flash, 4 Kbyte page granularity |
| RAM | 24 Kbytes of RAM |
| Radio | 2.4 GHz BLE 5.x, 2 Mbps / 1 Mbps / Long Range, +4 dBm |
| Package | WLCSP28 (2.48×2.48) / QFN32 / QFN48 / WLCSP33 |
| Protection | APPROTECT in UICR, CTRL-AP ERASEALL |
| Debug / programming | Serial Wire Debug (SWD), CTRL-AP control access port |
Access port protection on this generation is driven by APPROTECT in the UICR: when enabled, the debugger cannot read or write CPU registers or memory-mapped addresses. An external read of a protected array therefore returns no usable instructions, while the CPU still executes its own flash normally. The 128-bit AES engine and the radio crypto support serve application traffic; neither is a service backdoor into the protected array. The surrounding Cortex-M and wireless material is linked here: NRF52820-CFAA-D-R7 firmware documentation.
Peripheral settings worth archiving
The peripheral set includes a 12-bit ADC with eight configurable channels, PDM and PWM for audio, UART, SPI, TWI and a quadrature decoder on selected variants. Direction Finding with angle-of-arrival and angle-of-departure measurement is available on the member that supports Bluetooth 5.1, and its antenna-switching pattern belongs in a complete radio record. A schematic that names the 32.768 kHz crystal and the DC-DC inductor shortens any comparison with an archived build. Decapsulate, decode and retrieve are useful verbs in a keyword, but on a locked integrated circuit only the decode of an unlocked array is technically available. Related device notes on this site cover the wider family: NRF52805-CAAA-R firmware documentation.
Build codes and what they change
Four bodies appear across this 192 Kbyte class: a 2.48 by 2.48 mm 28-ball wafer-level chip-scale package with ten GPIOs, a 5 by 5 mm 32-pin QFN, a 6 by 6 mm 48-pin QFN and a small 33-ball wafer-level option. The CAAA, QCAA and QFAA prefixes distinguish those bodies, while a trailing R, R7 or T marks a 13-inch reel, a 7-inch reel or a tray. The 2.48 by 2.48 mm 28-ball body exposes only ten GPIOs, so a legacy board may offer no spare test point for probing. On a wafer-level body the SWD pads sit beneath the balls, so the ball map and schematic are required before any authorised access is planned. For background on a neighbouring part, see ARM microcontroller stm32f101c4 locked firmware recovery.
Owner consent and final handover
Within the second generation this is the small-memory tier, sharing the 64 MHz Cortex-M4 architecture and the APPROTECT scheme with the 256 Kbyte and 1 Mbyte members. Direction Finding support and the radio feature set vary by member even when the flash and RAM numbers match, which is why the exact part number matters. Where the array is unlocked we return separate labelled images for the MBR, SoftDevice, application and the UICR data region. Where APPROTECT is set we supply an identification and documentation package and state plainly that a CTRL-AP ERASEALL destroys the application, UICR and RAM together. The ARM and Nordic cross-reference is documented in ARM microcontroller stm32f205rg flash code recovery.
Every attack NRF52810-QCAA-E-R protected flash program engagement concludes with a report, not a claim. The report lists the ordering code, the revision or build code, the protection state, the memory regions and the owner’s archive comparison, and it states plainly which outcomes are technically available. We work under NDA for the owner or an appointed repair partner, disclose the erase-all consequence before any destructive action, and do not quote a readout that relies on suppressing a protection state.