The DBGBCR<n> characteristics are:
Holds control information for a breakpoint. Forms breakpoint n together with value register DBGBVR<n>. If EL2 is implemented and this breakpoint supports Context matching, DBGBVR<n> can be associated with a Breakpoint Extended Value Register DBGBXVR<n> for VMID matching.
This register is part of the Debug registers functional group.
There is one instance of this register that is used in both Secure and Non-secure states.
AArch32 System register DBGBCR<n> is architecturally mapped to AArch64 System register DBGBCR<n>_EL1.
AArch32 System register DBGBCR<n> is architecturally mapped to External register DBGBCR<n>_EL1.
If breakpoint n is not implemented then this register is unallocated.
This register is in the Cold reset domain. On a Cold reset RW fields in this register reset to architecturally UNKNOWN values. The register is not affected by a Warm reset.
DBGBCR<n> is a 32-bit register.
The DBGBCR<n> bit assignments are:
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 |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | BT | LBN | SSC | HMC | 0 | 0 | 0 | 0 | BAS | 0 | 0 | PMC | E |
When the E field is zero, all the other fields in the register are ignored.
Reserved, RES0.
Breakpoint Type. Possible values are:
BT | Meaning |
---|---|
0000 |
Unlinked instruction address match. |
0001 |
Linked instruction address match. |
0010 |
Unlinked Context ID match. |
0011 |
Linked Context ID match. |
0100 |
Unlinked instruction address mismatch. |
0101 |
Linked instruction address mismatch. |
0110 |
Unlinked CONTEXTIDR_EL1 match (introduced in ARMv8.1). |
0111 |
Linked CONTEXTIDR_EL1 match (introduced in ARMv8.1). |
1000 |
Unlinked VMID match. |
1001 |
Linked VMID match. |
1010 |
Unlinked VMID and Context ID match. |
1011 |
Linked VMID and Context ID match. |
1100 |
Unlinked CONTEXTIDR_EL2 match (introduced in ARMv8.1). |
1101 |
Linked CONTEXTIDR_EL2 match (introduced in ARMv8.1). |
1110 |
Unlinked Full Context ID match (introduced in ARMv8.1). |
1111 |
Linked Full Context ID match (introduced in ARMv8.1). |
The field breaks down as follows:
Constraints on breakpoint programming mean some values are reserved under certain conditions. For more information, see 'Reserved DBGBCR<n>.BT values' in the ARMv8 ARM, section G2 (AArch32 Self-hosted Debug).
When this register has an architecturally-defined reset value, this field resets to a value that is architecturally UNKNOWN.
Linked breakpoint number. For Linked address matching breakpoints, this specifies the index of the Context-matching breakpoint linked to.
For all other breakpoint types this field is ignored and reads of the register return an UNKNOWN value.
This field is ignored when the value of DBGBCR<n>.E is 0.
When this register has an architecturally-defined reset value, this field resets to a value that is architecturally UNKNOWN.
Security state control. Determines the Security states under which a Breakpoint debug event for breakpoint n is generated. This field must be interpreted along with the HMC and PMC fields, and there are constraints on the permitted values of the {HMC, SSC, PMC} fields. For more information, including the effect of programming the fields to a reserved set of values, see 'Reserved DBGBCR<n>.{HMC, SSC, PMC} values' in the ARMv8 ARM, section G2 (AArch32 Self-hosted Debug).
For more information on the operation of the SSC, HMC, and PMC fields, see 'Execution conditions for which a breakpoint generates Breakpoint exceptions' in the ARMv8 ARM, section G2 (AArch32 Self-hosted Debug).
When this register has an architecturally-defined reset value, this field resets to a value that is architecturally UNKNOWN.
Higher mode control. Determines the debug perspective for deciding when a Breakpoint debug event for breakpoint n is generated. This field must be interpreted along with the SSC and PMC fields, and there are constraints on the permitted values of the {HMC, SSC, PMC} fields. For more information see the SSC, bits [15:14] description.
For more information on the operation of the SSC, HMC, and PMC fields, see 'Execution conditions for which a breakpoint generates Breakpoint exceptions' in the ARMv8 ARM, section G2 (AArch32 Self-hosted Debug).
When this register has an architecturally-defined reset value, this field resets to a value that is architecturally UNKNOWN.
Reserved, RES0.
Byte address select. Defines which half-words an address-matching breakpoint matches, regardless of the instruction set and Execution state.
The permitted values depend on the breakpoint type.
For Address match breakpoints, the permitted values are:
BAS | Match instruction at | Constraint for debuggers |
---|---|---|
0011 | DBGBVR<n> | Use for T32 instructions. |
1100 | DBGBVR<n>+2 | Use for T32 instructions. |
1111 | DBGBVR<n> | Use for A32 instructions. |
All other values are reserved. For more information, see 'Reserved DBGBCR<n>.BAS values' in the ARMv8 ARM, section G2 (AArch32 Self-hosted Debug).
For more information on using the BAS field in Address Match breakpoints, see 'Using the BAS field in Address Match breakpoints' in the ARMv8 ARM, section G2 (AArch32 Self-hosted Debug).
For Address mismatch breakpoints in an AArch32 stage 1 translation regime, the permitted values are:
BAS | Step instruction at | Constraint for debuggers |
---|---|---|
0000 | - | Use for a match anywhere breakpoint. |
0011 | DBGBVR<n> | Use for stepping T32 instructions. |
1100 | DBGBVR<n>+2 | Use for stepping T32 instructions. |
1111 | DBGBVR<n> | Use for stepping A32 instructions. |
All other values are reserved. For more information, see 'Reserved DBGBCR<n>.BAS values' in the ARMv8 ARM, section G2 (AArch32 Self-hosted Debug).
For more information on using the BAS field in address mismatch breakpoints, see 'Using the BAS field in Address Match breakpoints' in the ARMv8 ARM, section G2 (AArch32 Self-hosted Debug).
For Context matching breakpoints, this field is RES1 and ignored.
When this register has an architecturally-defined reset value, if this field is implemented as an RW field, it resets to a value that is architecturally UNKNOWN.
Reserved, RES0.
Privilege mode control. Determines the Exception level or levels at which a Breakpoint debug event for breakpoint n is generated. This field must be interpreted along with the SSC and HMC fields, and there are constraints on the permitted values of the {HMC, SSC, PMC} fields. For more information see the DBGBCR<n>.SSC description.
For more information on the operation of the SSC, HMC, and PMC fields, see 'Execution conditions for which a breakpoint generates Breakpoint exceptions' in the ARMv8 ARM, section G2 (AArch32 Self-hosted Debug).
When this register has an architecturally-defined reset value, this field resets to a value that is architecturally UNKNOWN.
Enable breakpoint DBGBVR<n>. Possible values are:
E | Meaning |
---|---|
0 |
Breakpoint disabled. |
1 |
Breakpoint enabled. |
When this register has an architecturally-defined reset value, this field resets to a value that is architecturally UNKNOWN.
This register can be read using MRC with the following syntax:
MRC <syntax>
This register can be written using MCR with the following syntax:
MCR <syntax>
This syntax uses the following encoding in the System instruction encoding space:
<syntax> | opc1 | opc2 | CRn | coproc | CRm |
---|---|---|---|---|---|
p14, 0, <Rt>, c0, <CRm>, 5 | 000 | 101 | 0000 | 1110 | n<3:0> |
The register is accessible as follows:
Control | Accessibility | |||||
---|---|---|---|---|---|---|
E2H | TGE | NS | EL0 | EL1 | EL2 | EL3 |
x | x | 0 | - | RW | n/a | RW |
x | 0 | 1 | - | RW | RW | RW |
x | 1 | 1 | - | n/a | RW | RW |
This table applies to all instructions that can access this register.
For a description of the prioritization of any generated exceptions, see section G1.11.2 (Exception priority order) in the ARM® Architecture Reference Manual, ARMv8, for ARMv8-A architecture profile for exceptions taken to AArch32 state, and section D1.13.2 (Synchronous exception prioritization) for exceptions taken to AArch64 state. Subject to the prioritization rules, the following traps and enables are applicable when accessing this register.
In both Security states, and not dependent on other configuration bits:
If EDSCR.TDA==1, and DBGOSLSR.OSLK==0, accesses to this register from PL1 and PL2 are trapped to Debug state.
When EL2 is implemented and is using AArch64 and SCR_EL3.NS==1 :
If MDCR_EL2.TDA==1, Non-secure accesses to this register from EL1 are trapped to EL2.
When EL2 is implemented and is using AArch32 and SCR_EL3.NS==1 :
If HDCR.TDA==1, Non-secure accesses to this register from EL1 are trapped to Hyp mode.
When EL3 is implemented and is using AArch64 :
If MDCR_EL3.TDA==1, accesses to this register from EL1 and EL2 are trapped to EL3.
18/04/2017 17:00
Copyright © 2010-2017 ARM Limited or its affiliates. All rights reserved. This document is Confidential.