Retrieve Secured NRF52833-CIAA-R Data: WLCSP 512 KB Read
The NRF52833-CIAA-R is the wafer-level chip-scale package of the nRF52833 family, a 3.2 x 3.2 mm WLCSP that still carries the full 512 KB flash and 128 KB RAM behind an Arm Cortex-M4 with FPU at 64 MHz, and the R suffix only names the 13-inch reel it ships on. When the part is locked by APPROTECT and the only copy of the configuration lives in the User Information Configuration Registers, the work is to retrieve secured NRF52833-CIAA-R data without guessing at what the original held, reading the UICR and the application array straight from the silicon.
A thin part on a long reel
The R container is the 13-inch tape-and-reel, holding roughly 3000 pieces, and it carries the same die as the R7 and T parts, so the recovery does not change with the container. The WLCSP body is the smallest in the family at 3.2 x 3.2 mm with 42 GPIO brought out on a ball grid, and that small footprint is the real constraint: there is no exposed thermal pad to land on and the balls sit close to the die, so the physical route has to be gentle. The part still runs 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 data set worth retrieving is large. The radio reaches +8 dBm with -103 dBm sensitivity at 125 kbps long range, and the part is rated across -40 to 105 C on a 1.7 to 5.5 V supply, which is why it appears in professional lighting and industrial tracking as well as consumer boards.
The secured state on this silicon
nRF52 readback protection is not the STM32 three-level RDP ladder. The lock is APPROTECT in the UICR, and Nordic keeps a CTRL-AP available so the device can be erased but not read through the debug port. The lock is two-step: the hardware closes the debug port when UICR.APPROTECT is Enabled, 0x00, and the firmware is expected to write APPROTECT.FORCEPROTECT at startup. When that firmware half is skipped the part can look locked without being fully protected, which is often the first finding once the configuration area is reached. Our notes on package decapsulation cover reaching such a die, and the power glitch route is the alternative when the register doors stay shut.
A gentler route for a ball-grid part
Because the WLCSP has no exposed pad and a tight ball pitch, the etch is stopped as soon as the die is visible rather than taken to the pad frame, and the read is taken on the live die through the ball contacts. The 512 KB array and the UICR are read together in two passes that are compared, which catches any cell that decodes differently and confirms the data is clean. Keeping the part alive matters most on a WLCSP, where a dead die is far harder to re-land than on a QFN.
The data that actually matters
Most of what makes the original behave as it does lives outside the application flash. The UICR customer data area carries product and calibration values, the PSELRESET registers set which pins act as reset, and the NFC pin configuration decides which balls are repurposed for the NFC antenna. Some of that UICR is re-writable and some is one-time programmable, so the state has to be captured accurately rather than rebuilt approximately, and because APPROTECT also sits in the UICR the protection state recorded alongside the data has to match the original. Calibration values here can include the temperature sensor offset and the RC oscillator tuning, both of which the firmware relies on at boot, so dropping them changes behaviour even when every byte of application flash is correct. The NFC routing is easy to miss because the same balls serve GPIO until the NFC function is enabled, and a copy that forgets that mapping will not come up with the antenna attached.
| Data region | What it holds | Recovered or reported |
|---|---|---|
| UICR customer area | Product and calibration data | recovered, byte for byte |
| PSELRESET and NFC pins | Reset and antenna configuration | recovered |
| Application flash | The functional firmware | recovered |
| Protection state | APPROTECT and ACL settings | documented to match |
What you get back
You receive the application data of the NRF52833-CIAA-R as a 512 KB image with the UICR region separated out, the configuration bytes documented, a disassembly-based reconstruction of the application code, and a verification report recording how the die was reached and how each region was checked. The same bench handles the CIAA-R7 software read on the short reel and the QIAA-R7 memory decapsulation, while the same technique applies to the STM32G473 data on other silicon.