Inferring AXI Signals - 2024.1 English

Vivado Design Suite User Guide: Creating and Packaging Custom IP (UG1118)

Document ID
UG1118
Release Date
2024-06-19
Version
2024.1 English

AMD has adopted the Advanced eXtensible Interface (AXI) protocol for its IP cores, the use of the protocol in your custom IP gives the flexibility to connect with other IP in the Vivado IP catalog. If the port signals of your custom IP adhere to the AXI naming conventions, the Vivado IP packager automatically infers the AXI interface.

The proper nomenclature to infer the AXI interface is to ensure that the port name consists of an interface name followed by the AXI signal name. Any name can be used for the interface as long as the name is consistent for each port. The following table is an example naming convention for inferring an AXI4-Stream interface with interface name s0_axis.

  • s0_axis_tdata
  • s0_axis_tvalid
  • s0_axis_tready
  • s0_axis_tstrb
  • s0_axis_tkeep
  • s0_axis_tlast
  • s0_axis_tid
  • s0_axis_tdest
  • s0_axis_tuser

For more information regarding the AXI interface, see the Vivado Design Suite: AXI Reference Guide (UG1037).