The TRCAUTHSTATUS characteristics are:
Provides information about the state of the IMPLEMENTATION DEFINED authentication interface for debug.
For additional information, see the CoreSight Architecture Specification.
External register TRCAUTHSTATUS bits [31:0] are architecturally mapped to AArch64 System register TRCAUTHSTATUS[31:0].
This register is present only when FEAT_ETE is implemented and FEAT_TRC_EXT is implemented. Otherwise, direct accesses to TRCAUTHSTATUS are RES0.
TRCAUTHSTATUS is a 32-bit register.
| 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 |
| RES0 | RTNID | RTID | RES0 | RLNID | RLID | HNID | HID | SNID | SID | NSNID | NSID | ||||||||||||||||||||
Reserved, RES0.
Root non-invasive debug.
This field has the same value as DBGAUTHSTATUS_EL1.RTNID.
This field has an IMPLEMENTATION DEFINED value.
Access to this field is RO.
Root invasive debug.
| RTID | Meaning |
|---|---|
| 0b00 |
Not implemented. |
Reserved, RES0.
Realm non-invasive debug.
This field has the same value as DBGAUTHSTATUS_EL1.RLNID.
This field has an IMPLEMENTATION DEFINED value.
Access to this field is RO.
Realm invasive debug.
| RLID | Meaning |
|---|---|
| 0b00 |
Not implemented. |
Hyp Non-invasive Debug. Indicates whether a separate enable control for EL2 non-invasive debug features is implemented and enabled.
| HNID | Meaning |
|---|---|
| 0b00 |
Separate Hyp non-invasive debug enable not implemented, or EL2 non-invasive debug features not implemented. |
| 0b10 |
Implemented and disabled. |
| 0b11 |
Implemented and enabled. |
All other values are reserved.
This field reads as 0b00.
Hyp Invasive Debug. Indicates whether a separate enable control for EL2 invasive debug features is implemented and enabled.
| HID | Meaning |
|---|---|
| 0b00 |
Separate Hyp invasive debug enable not implemented, or EL2 invasive debug features not implemented. |
| 0b10 |
Implemented and disabled. |
| 0b11 |
Implemented and enabled. |
All other values are reserved.
This field reads as 0b00.
Secure Non-invasive Debug. Indicates whether Secure non-invasive debug features are implemented and enabled.
| SNID | Meaning |
|---|---|
| 0b00 |
Secure non-invasive debug features not implemented. |
| 0b10 |
Implemented and disabled. |
| 0b11 |
Implemented and enabled. |
All other values are reserved.
When Secure state is implemented, this field reads as 0b10 or 0b11 depending whether Secure non-invasive debug is enabled.
When Secure state is not implemented, this field reads as 0b00.
Secure Invasive Debug. Indicates whether Secure invasive debug features are implemented and enabled.
The value of this field is an IMPLEMENTATION DEFINED choice of:
| SID | Meaning |
|---|---|
| 0b00 |
Secure invasive debug features not implemented. |
| 0b10 |
Implemented and disabled. |
| 0b11 |
Implemented and enabled. |
All other values are reserved.
This field reads as 0b00.
Access to this field is RO.
Non-secure Non-invasive Debug. Indicates whether Non-secure non-invasive debug features are implemented and enabled.
The value of this field is an IMPLEMENTATION DEFINED choice of:
| NSNID | Meaning |
|---|---|
| 0b00 |
Non-secure non-invasive debug features not implemented. |
| 0b10 |
Implemented and disabled. |
| 0b11 |
Implemented and enabled. |
All other values are reserved.
When Non-secure state is implemented, this field reads as 0b11.
When Non-secure state is not implemented, this field reads as 0b00.
Access to this field is RO.
Non-secure Invasive Debug. Indicates whether Non-secure invasive debug features are implemented and enabled.
The value of this field is an IMPLEMENTATION DEFINED choice of:
| NSID | Meaning |
|---|---|
| 0b00 |
Non-secure invasive debug features not implemented. |
| 0b10 |
Implemented and disabled. |
| 0b11 |
Implemented and enabled. |
All other values are reserved.
This field reads as 0b00.
Access to this field is RO.
For implementations that support multiple access mechanisms, different access mechanisms can return different values for reads of TRCAUTHSTATUS if the authentication signals have changed and that change has not yet been synchronized by a Context synchronization event. This scenario can happen if, for example, the external debugger view is implemented separately from the system instruction view to allow for separate power domains, and so observes changes on the signals differently.
External debugger accesses to this register are unaffected by the OS Lock.
| Component | Offset | Instance |
|---|---|---|
| ETE | 0xFB8 | TRCAUTHSTATUS |
This interface is accessible as follows:
26/03/2024 09:49; 67c0ae5282a7629ba0ea0ba7267b43cd4f7939f6
Copyright © 2010-2024 Arm Limited or its affiliates. All rights reserved. This document is Non-Confidential.