# Debug LCP-DARE authentication errors

Capture LCP-DARE syndrome information from TrustZone and read the authentication error log registers to locate the failing access.

When an authentication error is fatal, LCP-DARE reports it through error fatal interrupts. Use the captured syndrome data and the error log registers to identify the region and address where the authentication check failed.

## LCP-DARE error handling

LCP-DARE registers the authentication error fatal interrupts for TrustZone. When an authentication error fatal occurs, the interrupt handlers in TrustZone capture the syndrome information. The dump of the syndrome registers in on-chip internal memory (OCIMEM) is part of minidumps, full dumps, and non-secure dumps. The LCP-DARE syndrome registers are also added to the secure register list, a debug hardware block that runs during a crash.

## LCP-DARE error log registers

The authentication error log registers record whether the log data is valid and capture the address and length of the failing main access. The following table lists the status register and the main-access log
registers for regions configured for a secure interrupt.

| **Register** | **Field** | **Bits** | **Description** |
| --- | --- | --- | --- |
| <br>`LLCC0_LLCC_LCP_SECURE_AUTH_ERR_LOG_STATUS` (Address: 0x21A89004)<br><br><br>“Status Register to indicate if the Authentication Error Logs are valid for regions configured for Secure Interrupt” | `AUTH_ERR_LOG_L3_ARCMD_ACCESS_VALID` | 7 | Indicates that transaction information of the L3 ARC metadata in Authentication Error Logging Registers is valid |
| <br>`LLCC0_LLCC_LCP_SECURE_AUTH_ERR_LOG_STATUS` (Address: 0x21A89004)<br><br><br>“Status Register to indicate if the Authentication Error Logs are valid for regions configured for Secure Interrupt” | `AUTH_ERR_LOG_L2_ARCMD_ACCESS_VALID` | 6 | Indicates that transaction information of the L2 ARC metadata in Authentication Error Logging Registers is valid |
| <br>`LLCC0_LLCC_LCP_SECURE_AUTH_ERR_LOG_STATUS` (Address: 0x21A89004)<br><br><br>“Status Register to indicate if the Authentication Error Logs are valid for regions configured for Secure Interrupt” | `AUTH_ERR_LOG_L1_ARCMD_ACCESS_VALID` | 5 | Indicates that transaction information of the L1 ARC metadata in Authentication Error Logging Registers is valid |
| <br>`LLCC0_LLCC_LCP_SECURE_AUTH_ERR_LOG_STATUS` (Address: 0x21A89004)<br><br><br>“Status Register to indicate if the Authentication Error Logs are valid for regions configured for Secure Interrupt” | `AUTH_ERR_LOG_L0_ARCMD_ACC ESS_VALID` | 4 | Indicates that transaction information of the L0 ARC metadata in Authentication Error Logging Registers is valid |
| <br>`LLCC0_LLCC_LCP_SECURE_AUTH_ERR_LOG_STATUS` (Address: 0x21A89004)<br><br><br>“Status Register to indicate if the Authentication Error Logs are valid for regions configured for Secure Interrupt” | `AUTH_ERR_LOG_MAIN_ACCESS_V ALID` | 0 | Indicates that transaction information of the main access in Authentication Error Logging Registers is valid |
| `LLCC0_LLCC_LCP_SECURE_AUTH_ERR_LOG0` (Address: 0x21A89020)<br><br><br>“Authentication Error Logging Register 0 for main access transaction for regions configured for Secure Interrupt” | ADDR | 31:0 | Lower 32-bit Address of the main access on which an authentication error was detected. Main access would be authentication of the payload cache line itself. |
| `LLCC0_LLCC_LCP_SECURE_AUTH_ERR_LOG1` (Address: 0x21A89024)<br><br><br>“Authentication Error Logging Register 1 for main access transaction for regions configured for Secure Interrupt” | ADDR | 31:0 | Higher 32-bit Address of the main access on which an authentication error was detected. |
| Register | Field | Bits | Description |
| `LLCC0_LLCC_LCP_SECURE_AUTH_ERR_Ln_AARCMD_LOG0` (Address: 0x21A89040 + 0x10n. Where n =0 to 3, represents ARC level (L0, L1, L2, L3 levels) )<br><br><br>“Authentication Error Logging Register n for Ln ARC metadata access transaction for regions configured for Secure Interrupt” | ADDR | 31:0 | Lower 32-bit Address of the Ln ARC metadata access on which an authentication error was detected |
| `LLCC0_LLCC_LCP_SECURE_AUTH_ERR_Ln_AARCMD_LOG1` (Address: 0x21A89044 + 0x10n. Where n =0 to 3, represents ARC level (L0, L1, L2, L3 levels) )<br><br><br>“Authentication Error Logging Register n for Ln ARC metadata access transaction for regions configured for Secure Interrupt” | ADDR | 31:0 | Higher 32-bit Address of the L0 ARC metadata access on which an authentication error was detected |
|  |  |  |  |
|  |  |  |  |
|  |  |  |  |
|  |  |  |  |

### Related

- [LCP-DARE architecture](https://docs.qualcomm.com/doc/80-A0399-49/topic/lcp-dare-architecture.html)

Last Published: Sep 08, 2026

[Previous Topic
Configure LCP-DARE regions with QDUTT](https://docs.qualcomm.com/bundle/publicresource/80-A0399-49/topics/configure-lcp-dare-regions-with-qdutt.md) [Next Topic
Assess total memory encryption performance](https://docs.qualcomm.com/bundle/publicresource/80-A0399-49/topics/assess-total-memory-encryption-performance.md)

Source: [https://docs.qualcomm.com/doc/80-A0399-49/topic/debug-lcp-dare-authentication-errors.html](https://docs.qualcomm.com/doc/80-A0399-49/topic/debug-lcp-dare-authentication-errors.html)