Debug
ARM DDI 0301H
Copyright © 2004-2009 ARM Limited. All rights reserved.
13-10
ID012310
Non-Confidential, Unrestricted Access
[8]
R
RC
0
Sticky Undefined flag:
0 = No Undefined exception trap occurred in Debug state since the last
time this bit was cleared.
1 = An undefined exception occurred while in Debug state since the
last time this bit was cleared.
This bit is cleared on reads of a DBGTAP debugger to the DSCR. The
Sticky Undefined bit does not prevent additional instructions from
being issued.
The Sticky Undefined bit is not set by Undefined exceptions occurring
when not in Debug state.
[7]
R
RC
0
Sticky imprecise Data Aborts flag:
0 = No imprecise Data Aborts occurred since the last time this bit was
cleared
1 = An imprecise Data Abort has occurred since the last time this bit
was cleared.
It is cleared on reads of a DBGTAP debugger to the DSCR.
The sticky imprecise data abort bit is only set by imprecise data aborts
occurring when in Debug state.
Note
In previous versions of the debug architecture, the sticky imprecise
data abort was set when the processor took an imprecise data abort. In
version 6.1, it is set when an imprecise data abort is detected.
[6]
R
RC
0
Sticky precise Data Abort flag:
0 = No precise Data Abort occurred since the last time this bit was
cleared
1 = A precise Data Abort has occurred since the last time this bit was
cleared.
This flag is meant to detect Data Aborts generated by instructions
issued to the processor using the Debug Test Access Port. Therefore,
if the DSCR[13] execute ARM instruction enable bit is a 0, the value
of the sticky precise Data Abort bit is architecturally Unpredictable.
For ARM1176JZF-S processors the sticky precise Data Abort bit is
set regardless of DSCR[13]. It is cleared on reads of a DBGTAP
debugger to the DSCR.
The sticky precise data abort bit is only set by precise data aborts
occurring when in Debug state.
Table 13-4 Debug Status and Control Register bit field definitions (continued)
Bits
Core view
External
view
Reset
value
Description