The following information concerns transaction attributes logging depending on the transaction match:
- Data watchpoint match: When a data watchpoint matches, the following transaction attributes are logged irrespective of the target of the transaction (not all attributes may be applicable for all targets):
- 40-bit AXI physical address of the transaction
- 128-bit data associated to the n-th beat of the burst transaction, where n is configured by the user (before enabling the watchpoint) in the DBG_HWWP0_MAIN_CNTL[23:20] BEAT_SEL bit field
- Byte Enable: Specifies the 16 data byte enables associated with the up to 128-bit data captured
- Initiator Info: Specifies which initiator generated the transaction
- Response Info: Specifies whether the response indicates transaction success or failure
- Target Info: Specifies the target of the access
- Transaction Type: Specifies the type of the transaction which matches
- Burst Length (1..63)
- Burst Type: Specifies the type of the burst (only relevant if Burst Length > 1)
- Additional attributes, such as:
- Memory barrier watchpoint match: When a memory barrier watchpoint matches, transaction attributes logged are those of the transaction immediately following the memory barrier
- Chained watchpoint match: When a chained watchpoint matches (which implies that both memory barrier and data watchpoint have matched), transaction attributes logged are those of the transaction of the matching data watchpoint