PostHeaderIcon Duplicate NRF52820-QDAA-R protected MCU software

Engineers who duplicate NRF52820-QDAA-R protected MCU software on a radio-equipped board should record the SoftDevice version before anything else. The NRF52820-QDAA-R reserves flash and RAM for that stack, and the reserve changes how an image is laid out. QDAA selects the 5 by 5 mm 40-pin QFN package with the full-speed USB controller, and R is the 13-inch reel.

A datasheet view of duplicate NRF52820-QDAA-R protected MCU software

The nRF52820 pairs a 64 MHz 32-bit ARM Cortex-M4 core with a 2.4 GHz multiprotocol radio and an on-chip full-speed USB 2.0 device controller running at 12 Mbps. It is aimed at wired dongles, keyboards and industrial interfaces where a USB endpoint replaces the wireless link as the host connection. EasyDMA and the Programmable Peripheral Interconnect move data between the USB controller, the radio and RAM without CPU intervention. A 64 MHz internal oscillator gives fast wake-up, while an external crystal supplies the accurate timing that full-speed USB signalling requires. Region labels in a heximal export are what make a later rebuild possible; a single flat binary discards them.

Page size, regions and addresses

Program storage is 256 Kbytes of flash arranged in 4 Kbyte pages, paired with 32 Kbytes of RAM, with no on-chip ADC or floating-point unit on this derivative. A Nordic SoftDevice such as S140 occupies the lower flash region and reserves a RAM block, so the application link address sits above the Master Boot Record. The UICR page holds APPROTECT, the bootloader address and customer configuration words, and USB descriptor strings are stored in application flash rather than in a separate ROM. The -40 to 105 C rating and 1.7 to 5.5 V supply window make this part common on industrial USB interfaces, which shapes the board-level rework notes. A usable heximal names the MBR, SoftDevice, application, bootloader pointer and UICR regions; a single flat binary loses the boundaries a rebuild needs. For background on a neighbouring part, see NRF52820-CFAA-D-R firmware documentation.

The control access port in practice

Item What the data sheet states
Core 64 MHz ARM Cortex-M4, 32-bit
Program memory 256 Kbytes of flash, 4 Kbyte page granularity
RAM 32 Kbytes of RAM
Radio 2.4 GHz BLE 5.2 / 802.15.4, +8 dBm, -95 dBm sensitivity
Package 40-pin QFN (5×5) / 44-ball WLCSP (2.53×2.53)
Protection APPROTECT in UICR, CTRL-AP ERASEALL
Debug / programming Serial Wire Debug (SWD), CTRL-AP control access port

Access port protection is controlled by APPROTECT in the UICR: when enabled, the debugger is blocked from reading or writing CPU registers and memory-mapped addresses. A USB bootloader that happens to be present is application code written by the board maker, not a factory route around the protection field. The ARM and Nordic cross-reference is documented in NRF52805-CAAA-R firmware documentation.

Descriptor tables and endpoint buffers

The defining peripheral is a full-speed USB 2.0 device controller at 12 Mbps, joined by UART, SPI, TWI and a quadrature decoder for human-interface devices. Eighteen GPIOs on the QFN body and a reduced set on the wafer-level option cover the usual keyboard, trackpad and LED matrix wiring. The radio supports Bluetooth 5.2 features such as Direction Finding, Long Range and 2 Mbps throughput alongside Thread and Zigbee on the 802.15.4 PHY. Endpoint allocation, descriptor strings and the SoftDevice version belong in any complete software archive, not just the executable program. Break, duplicate and clone are common words in a request, yet the deliverable on a protected sample is a written comparison, not an extracted binary. A comparable recovery note is NRF52810-QCAA-E-R firmware documentation.

Container codes versus build codes

Two bodies are orderable: a 5 by 5 mm 40-pin QFN under the QDAA prefix and a 2.53 by 2.53 mm 44-ball wafer-level chip-scale package under CFAA, the latter carrying a D build code. None of those codes changes the 256 Kbyte array, the USB controller or the APPROTECT behaviour; confusing a container code with a silicon revision is an avoidable record-keeping error. The absence of an ADC and floating-point unit is a useful fingerprint: a captured image contains no converter setup code. Supply decoupling and the DC-DC inductor dominate the rework notes on both bodies. Further reading on adjacent microcontrollers: ARM stm32f071rb microcontroller locked bit breaking.

Feasibility notes and NDA terms

Within the second generation this is the USB-centric mid-range tier, sharing the 64 MHz Cortex-M4 architecture and the APPROTECT scheme with the 192 Kbyte and 1 Mbyte members. On an unlocked sample we return separate labelled images for the MBR, SoftDevice, application and the UICR data region, with the USB descriptor called out explicitly. When APPROTECT is set the deliverable is documentation rather than a claimed bypass, because a CTRL-AP ERASEALL removes the application, UICR and RAM together. The surrounding Cortex-M and wireless material is linked here: ARM stm32f072cb microcomputer firmware restoration.

Any duplicate NRF52820-QDAA-R protected MCU software request is handled the same way on every board: identify the fitted member, record the memory map and clock tree, then compare the customer’s archived build output with what the debug port reports. Where the array is unprotected a labelled program heximal and a separate configuration data file can be returned; where it is protected we supply an identification and documentation package instead. All work is scoped in writing for the owner or an authorised agent, with the erase consequence stated up front.

Comments are closed.