User Guidelines Specific to AXI4 - 1.0 English

• Read, Write, and Wait are each considered to be one instruction.
• If the transaction count per CSV command is less than 8 maximum bandwidth is not guaranteed from the TG.
• Supported axi_size and axi_len combinations are shown in the following table.

  Table 1. Supported Combinations of AXI Length and AXI Size

  axi_size in Bytes	Supported Number of Beats per Transaction (axi_len + 1)
  128	≤32
  64	≤64
  32	≤128
  16	≤256
  8	Any value supported by AXI protocol
  4	Any value supported by AXI protocol
  2	Any value supported by AXI protocol
  1	Any value supported by AXI protocol

• If data integrity is selected as Constant Id in the Vivado IDE, the CSV field for ID selection (axi_id) is ignored. In this case, transactions are sent out with the ID value as 0.
• When Data Integrity checks are enabled with mixed write read traffic patterns, the user needs to take care that the memory is written before it is read.  This can be done by running simulations and observing how long it takes to get BRESPs and adjust the CSV start_delay value for the Read traffic accordingly.
• If data integrity is enabled, Write/Read coherency must be maintained in the traffic specification itself. Writes must happen before reads and a data integrity error results if this does not happen. A Wait instruction must be used after Write instructions and before Read instructions.
• If data integrity is enabled Write and Read requests must have the same data pattern selected.
• Slave error or decode error responses from the AXI slave are also reported as a data integrity failure.
• Latency is expected for reads from the TG if the CSV has a few Write instructions followed by Read instructions.