C1.3
Debug events
A debug event can be a software debug event or a halting debug event.
A core responds to a debug event in one of the following ways:
• Ignores the debug event.
• Takes a debug exception.
• Enters debug state.
See the
Arm
®
Architecture Reference Manual Armv8, for Armv8-A architecture profile
for more
information about the debug events.
C1.3.1
Watchpoint debug events
In the Cortex-A76 core, watchpoint debug events are always synchronous.
Memory hint instructions and cache clean operations, except
DC ZVA
and
DC IVAC
, do not generate
watchpoint debug events. Store exclusive instructions generate a watchpoint debug event even when the
check for the control of exclusive monitor fails. Atomic CAS instructions generate a watchpoint debug
event even when the compare operation fails.
C1.3.2
Debug OS Lock
Debug OS Lock is set by the powerup reset,
nCPUPORESET
.
For normal behavior of debug events and debug register accesses, Debug OS Lock must be cleared. For
more information, see the
Arm
®
Architecture Reference Manual Armv8, for Armv8-A architecture profile
.
Related references
C1.4 External debug interface
on page C1-370
A3.1 About clocks, resets, and input synchronization
on page A3-42
C1 Debug
C1.3 Debug events
100798_0300_00_en
Copyright © 2016–2018 Arm Limited or its affiliates. All rights
reserved.
C1-369
Non-Confidential
Summary of Contents for Cortex-A76 Core
Page 4: ......
Page 22: ......
Page 23: ...Part A Functional description ...
Page 24: ......
Page 119: ...Part B Register descriptions ...
Page 120: ......
Page 363: ...Part C Debug descriptions ...
Page 364: ......
Page 401: ...Part D Debug registers ...
Page 402: ......
Page 589: ...Part E Appendices ...
Page 590: ......