Break Locked NRF52833-CIAA-R7 Software: WLCSP 512 KB Extract
The NRF52833-CIAA-R7 is the 7-inch reel variant of the nRF52833 wafer-level package, a 3.2 x 3.2 mm WLCSP carrying 512 KB of flash and 128 KB of RAM behind an Arm Cortex-M4 with FPU at 64 MHz, and the R7 suffix only names the reel it ships on. When the debug port is closed by APPROTECT and the application software is the only asset left, the work is to break locked NRF52833-CIAA-R7 software and pull the image out intact, whether that means faulting the lock or reaching the die past the package.
The reel code and the thin package
The R7 container is the 7-inch reel, distinct from the 13-inch R and the tray T only in shipping format, so the die, memory and package are unchanged across them. The WLCSP at 3.2 x 3.2 mm and 42 GPIO is the smallest body in the family, with balls close to the die and no exposed pad, which shapes both the fault-injection and the physical routes. Under the lid the core is an Arm Cortex-M4 with FPU at 64 MHz with the full Bluetooth 5.1 radio, USB 2.0, the ADC and the PWM blocks, so the software worth extracting is substantial.
How the lock is built
The nRF52 does not use the STM32 RDP ladder. The lock is APPROTECT in the UICR, which closes the debug access port in hardware when set to Enabled, 0x00, while a CTRL-AP stays open so the part can be mass-erased. The lock is two-step: the hardware close plus a firmware write of APPROTECT.FORCEPROTECT at startup, and if that second half is skipped the part can look locked while being only partly protected. Both FORCEPROTECT and APPROTECT.DISABLE are cleared by a pin, power, brownout, watchdog or System OFF reset, so any window has to be caught in a single pass. Our power glitch notes cover the timing discipline for that work.
The revision window for a glitch
On revisions with the improved two-step APPROTECT, among them nRF52833 revision 2 under build codes Bx0, the check is tightened, and a precisely timed voltage glitch on the supply during boot is the practical way to slip past it without triggering the erase that would otherwise destroy the image. Earlier revisions implement the hardware step alone, and on those the glitch window is wider. The unlock runs the other way when an erase is acceptable: a CTRL-AP ERASEALL wipes flash, UICR and RAM, code compiled without ENABLE_APPROTECT writes HwDisabled, 0x5A, and the firmware then writes APPROTECT.DISABLE.
| Method | Image preserved | Effort | When used |
|---|---|---|---|
| Supply glitch at boot | yes | medium | revision 2, build codes Bx0 |
| Targeted fault at reset | yes | medium | partly protected units |
| Etch-back and die read | yes | high | fully locked, no register route |
| CTRL-AP ERASEALL | no | high | only when loss is acceptable |
Pulling the software out
Once the port is open the 512 KB array streams out, taken twice with the passes compared so a port closing mid-capture is caught and repeated. The UICR comes with it, recording the APPROTECT state, the customer data area and the pin configuration. The SoftDevice stack area is delivered encrypted and decrypted into RAM at boot, so a debugger read of that region returns ciphertext rather than code, and it is reported as ciphertext rather than shipped as recovered software. A flash recovery pass confirms the image is whole before any rebuild.
Rebuilding the software image
The image starts with a vector table that bounds the RAM and points at the reset handler, and from there the call graph and the literal pools mark the function edges and reveal the peripheral registers each routine drives. The nRF52 peripheral map is fixed, so PWM, SAADC, SPIM, TWIM, UART, TIMER and GPIO accesses identify themselves by address, turning a column of constants into a map of what the firmware controls. Where the aim is a working copy, the same verified image seeds a clone of the firmware and the data read on the R part, and the STM32G030 clone uses the same discipline on other silicon.
What you get back
You receive the extracted software of the NRF52833-CIAA-R7 as a 512 KB binary with the SoftDevice area marked as encrypted, the UICR contents showing the original APPROTECT and configuration state, a disassembly-based reconstruction of the application code, and a verification report with the read checksums. The bench also handles the CIAA-R data retrieval and the QIAA-R7 memory decapsulation.