NRF52811-QCAA-R datasheet(41/444 Pages) NORDIC

41 / 444 page

Core components

Bit number

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

E E E E D D D D C C C C C C C B B B B

A A A A A A A A

Reset 0x02880000

0 0 0 0 0 0 1 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Access

Field

Value ID

Value

Description

APID

AP identification

CLASS

Access port (AP) class

NotDefined

0x0

No defined class

MEMAP

0x8

Memory access port

JEP106ID

JEDEC JEP106 identity code

JEP106CONT

JEDEC JEP106 continuation code

REVISION

Revision

4.8.2.2 Electrical specification

4.8.2.2.1 Control access port

Symbol

Description

Min.

Typ.

Max.

Units

Rpull

Internal SWDIO and SWDCLK pull up/down resistance

kΩ

fSWDCLK

SWDCLK frequency

0.125

MHz

4.8.3 Debug interface mode

Before an external debugger can access either CPU's access port (AHB-AP) or the control access port

(CTRL-AP), the debugger must first request the device to power up via CxxxPWRUPREQ in the SWJ-DP.

If the device is in System OFF when power is requested via CxxxPWRUPREQ, the system will wake up and

the DIF flag in RESETREAS on page 57 will be set. The device is in the debug interface mode as long

as the debugger is requesting power via CxxxPWRUPREQ. Once the debugger stops requesting power

via CxxxPWRUPREQ, the device is back in normal mode. Some peripherals behave differently in Debug

Interface mode compared to normal mode. These differences are described in more detail in the chapters

of the peripherals that are affected.

When a debug session is over, the external debugger must make sure to put the device back into normal

mode since the overall power consumption is higher in debug interface mode than in normal mode.

For details on how to use the debug capabilities, read the debug documentation of your IDE.

4.8.4 Real-time debug

The nRF52811 supports real-time debugging.

Real-time debugging allows interrupts to execute to completion in real time when breakpoints are set

in thread mode or lower priority interrupts. This enables developers to set breakpoints and single-step

through the code without the risk of real-time event-driven threads running at higher priority failing.

For example, this enables the device to continue to service the high-priority interrupts of an external

controller or sensor without failure or loss of state synchronization while the developer steps through

code in a low-priority thread.

4454_140 v1.0

NRF52811-QCAA-R bảng dữ liệu(PDF) 41 Page - Nordic Semiconductor

NRF52811-QCAA-R bảng dữ liệu(HTML) 41 Page - Nordic Semiconductor

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

bảng dữ liệu tải về

Link URL