Clone Protected NRF52832-CIAA-R7 Program: WLCSP50 512 KB Copy
A copy job on the NRF52832-CIAA-R7 is not a single file transfer, because a Bluetooth SoC image is really three artifacts wearing one package. The R7 again marks only the 7-inch reel container and says nothing about the silicon, which is the same die as the R version with 512 KB of flash and 64 KB of RAM under a 3.0 x 3.2 mm WLCSP50 body. To clone protected NRF52832-CIAA-R7 program is therefore a three-part job, and every part has to be described honestly.
The same die behind a different reel
The container code sits at the end of the Nordic ordering string, and the tray and tape-and-reel options carry the same silicon as the 7-inch reel. Nothing about the R7 suffix changes the flash density, the RAM size, the package outline or the temperature grade, so the reel size has no bearing on the cloning task itself. What does matter is that the NRF52832-CIAA-R7 is the 512 KB member of the family, running an Arm Cortex-M4 with FPU at 64 MHz with the radio stack alongside it, and that a 3.0 x 3.2 mm body has to be opened to read anything at all.
| Artifact | Where it lives | What a copy can contain |
|---|---|---|
| Application code | main flash area | full image, read and verified |
| SoftDevice area | reserved flash region | encrypted, decrypted to RAM at boot |
| UICR | separate configuration block | writable fields only |
The SoftDevice area is not readable code
Nordic delivers the Bluetooth stack in a reserved region of flash, and that region is stored encrypted. At boot the firmware decrypts it into RAM, so a debugger read of the flash location returns ciphertext rather than a stack image. A clone report that shows a flat block of high-entropy bytes and calls it a soft device copy is misleading, and any honest recovery separates the artifacts and labels the SoftDevice area as an encrypted region of known size rather than pretending it was disassembled. The application code sits outside that reservation and reads as normal code.
The UICR carries the identity
The User Information Configuration Registers are the part that makes two BLE devices look different on the same network. The customer data area holds the device address and the fields the product owner writes there, the PSELRESET register defines which pin resets the part, and the NFC pin configuration decides which pins are offered to an external reader. Some of these fields are one-time programmable and some can be rewritten, so a faithful copy can only carry the parts that are still writable. A clone that skips the customer data area produces a radio that advertises with an address nobody owns.
Copying the code without losing the setup
Reading the application code follows the same route as any other nRF52 recovery. The debug access port can be closed in hardware by writing Enabled, the value 0x00, into UICR.APPROTECT, while the control access port stays available, and the lock is a two-step affair because firmware separately writes APPROTECT.FORCEPROTECT as Force at startup. Opening it again takes a CTRL-AP ERASEALL, which clears flash, UICR and RAM, then code compiled without ENABLE_APPROTECT writing HwDisabled, the value 0x5A, to UICR.APPROTECT. On the small body the practical route is decapsulation and fine-pitch probing, described in our package decapsulation notes, and the flash read is taken twice with the passes compared before anything is written back.
Rebuilding a working replacement
Once the artifacts are in hand the replacement part is programmed in a defined order, and the details matter more than on a plain microcontroller. To clone protected NRF52832-CIAA-R7 program means writing the application image first, applying the writable UICR fields afterwards, and setting the APPROTECT state at the end if the copy is meant to look protected from the outside. The SoftDevice area is not rewritten from the copy, since it is delivered encrypted and the device decrypts it at boot from the factory region. Nordic also offers secure boot ready, a flash access control list and secure erase as further layers, and a device intended to behave like the original needs those left in a state the original firmware expects. Our notes on protected firmware cloning set out the same reasoning on other silicon, and a general firmware clone workflow covers the programming sequence used here.
What you get back
You receive the flash binary image of the NRF52832-CIAA-R7 with the application code separated from the encrypted SoftDevice region, a disassembly-based source reconstruction of the application code, the recovered UICR contents with the writable fields identified and the one-time fields marked as such, and a verification report with the read checksums. The same bench handles the WLCSP50 nRF52832 binary read, the QFN48 nRF52832 firmware break and the STM32G030K8T6 protected binary.