PostHeaderIcon Decapsulate Encrypted NRF52833-QIAA-R7 Memory: aQFN73 512 KB Read

The NRF52833-QIAA-R7 carries the full nRF52833 multiprotocol radio in the family’s largest package, a 7 x 7 mm aQFN73 that breaks out 42 GPIO around a 512 KB flash and 128 KB RAM core running an Arm Cortex-M4 with FPU at 64 MHz, and the R7 suffix only names the 7-inch reel it ships on. When the debug port is sealed by APPROTECT and the SoftDevice region is delivered encrypted, the honest path to decapsulate encrypted NRF52833-QIAA-R7 memory is to go past the package rather than past the lock, exposing the silicon while the part stays alive and reading the array straight off the die.

The reel code and the body it rides in

Nordic packs this variant on a 7-inch reel, the R7 container, so a board built around the NRF52833-QIAA-R7 can be sourced in the same small-reel format as its R and T siblings without any change to the die. The silicon, the 512 KB flash, the 128 KB RAM, the package and the temperature rating are identical across those containers, so the recovery work does not depend on which reel the part came from. What changes the job is the aQFN73 outline itself, because a 7 x 7 mm body leaves a generous margin of mould compound around a die that is much smaller, and that margin is what makes a controlled etch practical here.

What the die actually holds

Under the lid the core is an Arm Cortex-M4 with FPU at 64 MHz, scoring 217 EEMBC CoreMark from flash and 52 uA per megahertz from flash or 38 uA from RAM. The radio covers Bluetooth 5.1, mesh, Thread, Zigbee, NFC and proprietary 2.4 GHz, with transmit power programmable from +8 dBm down to -20 dBm in 4 dB steps and receive sensitivity of -103 dBm at 125 kbps long range, -96 dBm at 1 Mbps. There is a full-speed USB 2.0 controller, five 32-bit timers, three 24-bit real-time counters, four PWM units with EasyDMA, a 12-bit 200 ksps ADC and the programmable peripheral interconnect. Recovering memory from a part this capable means accounting for all of it, not just the application flash.

Why decapsulation beats the register route

The debug access port is closed by APPROTECT in the User Information Configuration Registers, and Nordic keeps a control access port, CTRL-AP, available so the device can be mass-erased but not read. Attacks that try to slip the lock through a supply glitch during boot depend on a timing window, and on revisions with the improved two-step APPROTECT they grow harder. Etching the package away and addressing the array on the exposed die avoids that fight entirely, because the protection state lives in the debug logic and the array itself answers once it is reached directly. Our notes on package decapsulation set out the sequence, and the dual probe and flying probe work applies once the pads are bare.

Opening the 7 x 7 mm aQFN73

The etch proceeds in controlled passes under the microscope while the board keeps running, because a live NRF52833-QIAA-R7 is worth more than a dead one when the aim is to read what it holds. The exposed thermal pad and the perimeter pads surface as the compound recedes, and the read then moves onto the die itself. The pass takes the 512 KB array twice and compares the two, so a cell that decodes differently between captures is caught and the image is confirmed clean before anything downstream begins. A careful read also keeps the UICR, which records the APPROTECT state, the customer data area, the pin-reset configuration and the NFC pin setup.

What the encrypted region means

One part of the image cannot be turned into plaintext no matter how the die is reached. The SoftDevice Bluetooth stack area is delivered encrypted and is decrypted into RAM only at boot, so a direct die read of that flash region returns ciphertext rather than code. That region is recorded honestly rather than hidden, because the bounds have to be stated for the next engineer who opens the file.

Region Read from the die Reported as
Application flash yes plaintext image
UICR and pin setup yes documented state
SoftDevice stack yes encrypted cipher

The flash recovery pass and the QDAA-R7 source rebuild both treat that region as out of reach, so the cipher is marked and the rest of the array is delivered whole.

What you get back

You receive the full 512 KB memory image of the NRF52833-QIAA-R7 with the SoftDevice region marked as encrypted, the UICR contents showing the original protection and configuration state, a disassembly-based reconstruction of the application code, and a verification report recording how the die was reached and how the read was checked. The same bench handles the QIAA-R flash attack on the smaller package and the WLCSP data read, while the same technique covers the STM32G474 program on other silicon.

Comments are closed.

Categories