PostHeaderIcon Break Secured NRF52832-QFAB-R7 Firmware: QFN48 256 KB Recovery

The NRF52832-QFAB-R7 arrives with a suffix that misleads before any instrument is connected. That R7 says only that the parts shipped on a 7-inch reel, and nothing about the silicon or the protection state, so the useful work is to break secured NRF52832-QFAB-R7 firmware on a 256 KB QFN48 device that Nordic sealed with its own UICR-based APPROTECT arrangement rather than the STM32-style ladder many readers expect.

What the R7 suffix actually means

The trailing characters in a Nordic ordering code describe the container, not the function. R is 13-inch tape-and-reel holding roughly 3000 pieces, R7 is the 7-inch reel holding 700 to 1000, and T is a tray. For a given variant code the die, flash density, RAM size, package and temperature grade are identical across those containers.

Container code Reel format Typical pieces Effect on the die
R 13-inch tape-and-reel about 3000 none
R7 7-inch reel 700 to 1000 none
T tray varies none
G or B die revision marker not a container silicon generation only

A build-revision letter such as G or B does mark a die revision, and that can matter for protection behaviour, but it does not change the feature set or the memory map of the NRF52832-QFAB-R7.

The silicon under the lid

The QFAB density of the NRF52832-QFAB-R7 is the 256 KB half of the family, the split point between the 512 KB and 256 KB flash parts, and it ships in the 48-lead QFN 6 x 6 mm body. Flash is 256 KB and RAM is 32 KB, so a 512 KB image will not fit here. The core is an Arm Cortex-M4 with FPU at 64 MHz, rated 215 EEMBC CoreMark from flash and 58 uA per megahertz. The 2.4 GHz transceiver handles Bluetooth LE at 1 Mbps and 2 Mbps, mesh, ANT and proprietary modes, with up to +4 dBm output and -96 dBm sensitivity.

APPROTECT is not a three-level RDP

Readback protection on nRF52 differs from the STM32 RDP ladder, and that difference decides how the unlock is planned. There is no RDP0 to RDP3 chain on this silicon. The lock lives in the User Information Configuration Registers as an APPROTECT field, and the control access port stays available while the debug access port is closed. Writing Enabled, the value 0x00, into UICR.APPROTECT closes the debug port in hardware, and the hardware fetches that value at reset, so the lock survives a power cycle but still answers a reset.

The lock has two halves

Enabling the lock is deliberately a two-step operation. The hardware step is the register write above; the firmware step is separate, with application code at startup writing APPROTECT.FORCEPROTECT as Force, the value 0x00. When that second half is missing the device can look locked while being only partly protected, a useful finding on partly configured units. The unlock runs the other way: a CTRL-AP ERASEALL operation clears flash, UICR and RAM, then code compiled without ENABLE_APPROTECT writes HwDisabled, the value 0x5A, to UICR.APPROTECT, and after a reset the firmware writes APPROTECT.DISABLE.

Where the silicon revision matters

nRF52832 revision 3, the build codes Gx0, implements the improved two-step APPROTECT described above. Earlier revisions implement the hardware step alone, and on those a precisely timed voltage glitch on the supply during boot can slip past the check without triggering the erase that would otherwise destroy the image. APPROTECT.DISABLE and FORCEPROTECT are reset by a pin, power, brownout or watchdog reset, or a wake from System OFF, so the unlock sequence has to respect those sources. Our notes on supply glitching set out that technique.

Reading the 256 KB array out

Once the port is open the array streams out, and the read is 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. Nordic also seals the SoftDevice stack area, delivered encrypted and decrypted into RAM at boot, so a debugger read of that region returns ciphertext rather than code. To break secured NRF52832-QFAB-R7 firmware honestly, that region is reported as ciphertext, not plaintext, and a flash recovery pass confirms the image is whole.

What you get back

You receive the complete 256 KB flash binary image of the NRF52832-QFAB-R7 with the SoftDevice area marked as encrypted, the UICR contents showing the original APPROTECT and configuration state, a disassembly-based source reconstruction of the application code, and a verification report with the read checksums. Where the aim is a replacement, the same verified image seeds a firmware clone. The bench also handles the WLCSP50 nRF52832 binary read and the nRF52832 program clone, and the same workflow covers the STM32G030C6T6 recovery.

Comments are closed.

Categories