User Manual 557 of 562 V 1.0
2021-08-25
XDPP1100 technical reference manual
Digital power controller
Central processing unit subsystem
Register name Field name
Access Address
Bits
Description
system. In this case
UARTPCellID[31:0] = 0xB105F00D.
UARTPCellID2 UARTPCellID2
R
700C_0FF8h [7:0]
UARTPCellID[23:16]. Together with
the other cell ID registers,
UARTPCellID[31:0] is used as a
standard cross-peripheral ID
system. In this case
UARTPCellID[31:0] = 0xB105F00D.
UARTPCellID3 UARTPCellID3
R
700C_0FFCh [7:0]
UARTPCellID[31:24]. Together with
the other cell ID registers,
UARTPCellID[31:0] is used as a
standard cross-peripheral ID
system. In this case
UARTPCellID[31:0] = 0xB105F00D.
15.14
Debugger port
The debugger port on the XDPP1100 is implemented through the Cortex®-M0 serial wire debugger (SWD)
interface, a two-wire serial protocol that is used to access the Cortex® debug access point (DAP).
Cortex® DAP is a specific HW, integrated into the M0 microcontroller, that can take the control of the execution
flow to allow an external debugger to access every register (on the Cortex®-M0 memory map), to
halt/step/resume any code execution, to dump every memory (ROM, RAM, OTP), to write any writable memory
(RAM, OTP) or to insert code breakpoints.
XDPP1100 registers can also be accessed using an I
2
C interface. The main difference between these two
methodologies is that while SWD is HW decoded by the DAP (no FW required), I
2
C is interpreted by the FW, so in
this case, the success of the access depends on the FW status (for example FW boot needs to be completed,
internal tasks have to permit the I
2
C driver to run, latency cannot be guaranteed).
Cortex® DAP structure, at high level, is shown in
Figure 124
Arm® DAP structure
ARM® debug interface v5
Debug access port (DAP)
Debug port
(DP)
Access port
(AP)
AP access
Physical
connection
Resource-
specific
transport
Resource
System being
debugged