When simulating, the AXI Protocol Checker can be configured to print display messages in the form of:
<time>ns : <instance_path> : BIT( <bit_number>) : <log_level> : <violation_message>| Message Field | Description |
|---|---|
| <instance_path> | The simulation hierarchy to the protocol checker instance that is issuing the message. |
| <bit_number> | Indicates which bit is asserted in the pc_status vector. This bit can be used to look up the violation in AXI Protocol Checks and Descriptions and AMD-Specific Configuration Checks and Descriptions. |
| <log_level> | Messaging level text that can be one of the following values: INFO, WARNING, or ERROR with the ability to stop or finish the simulation. This value is set in the configuration AMD Vivado™ IDE. |
| <violation_message> | Descriptive message indicating the name of the violation (for example, AXI_ERRS_RID) and violation. In most cases, this includes the location in the AXI specification where the protocol is described. The violation message name can be used to look up the violation in AXI Protocol Checks and Descriptions and AMD-Specific Configuration Checks and Descriptions. |
For example:
73717.00ns : tb.top.AXI4_0.REP : BIT(59) : ERROR : AXI_ERRS_RID. A slave can only give read data with an ID to match an outstanding read transaction. Spec: section 8.3 on page 8-4.In this example, the core provides a debugging capability for simulation where the AXI Protocol Checker can either finish or stop the simulation at the point of detecting the violation.