Decode NRF52840-QIAA-F-R locked MCU program
When the original build output is lost, decode NRF52840-QIAA-F-R locked MCU program becomes a comparison exercise. The NRF52840-QIAA-F-R provides identification, region sizes and observable radio behaviour, and those three things anchor a defensible report. QIAA is the 7 by 7 mm 73-pin aQFN body and F the revision whose APPROTECT is controlled by hardware and software together; R is the 13-inch reel.
Assessing decode NRF52840-QIAA-F-R locked MCU program on a fitted board
The nRF52840 is the flagship of this generation, combining a 64 MHz 32-bit ARM Cortex-M4 core with a floating-point unit, 1 Mbyte of flash and 256 Kbytes of RAM. A 2.4 GHz multiprotocol radio covers Bluetooth Low Energy 5.x, Thread, Zigbee and proprietary modes, while an NFC-A tag supports touch-to-pair. Forty-eight GPIOs, EasyDMA and the Programmable Peripheral Interconnect complete a platform intended for gateways and complex peripherals. On a wireless SoC the protocol stack version is as identifying as the application code that sits above it.
Flash, RAM and the linker map
Program storage is 1 Mbyte of flash in 4 Kbyte pages with 256 Kbytes of RAM, large enough for a dual-bank DFU bootloader, a SoftDevice and a substantial application. The UICR page holds APPROTECT, the bootloader address and customer configuration words, while the QSPI interface maps external memory into a separate address window. Because the F revision re-enables APPROTECT on reset, an identification report should record the build code before any tool is connected. Further reading on adjacent microcontrollers: NRF52840-QIAA-R firmware documentation.
Protection state and its consequences
| Item | What the data sheet states |
|---|---|
| Core | 64 MHz ARM Cortex-M4 with FPU, 32-bit |
| Program memory | 1 Mbyte of flash, 4 Kbyte page granularity |
| RAM | 256 Kbytes of RAM |
| Radio | 2.4 GHz BLE 5.x / 802.15.4, NFC-A, +8 dBm |
| Package | 73-pin aQFN (7×7 mm), 48 GPIOs |
| Protection | APPROTECT in UICR (hardware + software on -F), CTRL-AP ERASEALL |
| Debug / programming | Serial Wire Debug (SWD), CTRL-AP control access port |
Access port protection is driven by APPROTECT in the UICR, and on the F revision it is enforced by hardware and software together so a reset or wake re-enables it even after a temporary disable. The CryptoCell-310 engine, TrustZone partitions and the secure-boot root of trust are application security features, not a service backdoor into protected memory. The surrounding Cortex-M and wireless material is linked here: NRF52810-QFAA-E-R firmware documentation.
Radio, USB and converter settings
A full-speed USB 2.0 device controller at 12 Mbps, a 32 MHz QSPI interface, a high-speed 32 MHz SPI port and an NFC-A tag with wake-on-field sit alongside four PWM units, I2S, PDM and a 12-bit 200 ksps ADC with eight channels. The CryptoCell-310 subsystem accelerates AES, ChaCha20-Poly1305, SHA, ECC and RSA with a hardware random number generator compliant with NIST SP 800-90A and 800-90B. Endpoint allocation, the QSPI memory map, NFC pairing records and the secure-boot configuration belong in a complete software archive, not just the executable program. Because the FPU and DSP instructions are available, a captured image has a distinctly richer instruction mix than the smaller tiers. Decoding a heximal export is straightforward when regions are labelled; it is unreliable when a flat binary has merged the boot and application areas. Related device notes on this site cover the wider family: NRF52805-CAAA-R firmware documentation.
Body, rails and debug header
The 7 by 7 mm 73-pin aQFN body with 48 GPIOs is the standard package for this flagship, and the QIAA prefix identifies it. Container codes never alter the 1 Mbyte array, the CryptoCell subsystem or the protection behaviour, but the F code genuinely changes how the debug port is guarded. An 8 Kbyte or larger bootloader region supports dual-bank DFU, so its configuration deserves a separate entry in any archive manifest. On the aQFN body the full supply range including high-voltage mode is available, and the ball-free lead frame makes rework notes simpler than a wafer-level part. For background on a neighbouring part, see Attack ARM stm32f205rf microprocessor tamper resistance.
Deliverables, consent and terms
Within the second generation this is the top tier, sharing the 64 MHz Cortex-M4 architecture and the CTRL-AP toolchain with the 192 Kbyte and 256 Kbyte members but adding an FPU, TrustZone and CryptoCell-310. A board built for the flagship cannot simply accept a smaller tier, because the memory map, the QSPI window and the security features differ. The F revision’s hardware-and-software protection is the one case in this family where a suffix changes the security model rather than just the shipping container. Where the array is unlocked we return separate labelled images for the MBR, SoftDevice, application, bootloader and UICR, with the external QSPI window documented explicitly. Where APPROTECT is set we supply an identification and documentation package and state plainly that a CTRL-AP ERASEALL destroys the application, UICR and RAM together. The ARM and Nordic cross-reference is documented in Attack locked stm32f100r8 ARM MCU flash memory.
Every decode NRF52840-QIAA-F-R locked MCU program engagement concludes with a report, not a claim. The report lists the ordering code, the revision or build code, the protection state, the memory regions and the owner’s archive comparison, and it states plainly which outcomes are technically available. We work under NDA for the owner or an appointed repair partner, disclose the erase-all consequence before any destructive action, and do not quote a readout that relies on suppressing a protection state.