Similar to IP Definitions, the IP-XACT bus definition files must be in a repository path for the IP packager and IP integrators to use the files.
Recommended: Structure your
/IP repository to have a single directory with an
/interfaces subdirectory to contain the interface definition
files, and a peer IP subdirectory to contain your IP definition files. A repository path
must be added at, or preceding, the directory that contains the IP definition file. For
example, <repository_path>/IP/interface or
<repository_path>/IP/IP.
To see the interface definition files in the IP catalog, ensure that the catalog is organized to display by repository. See Using the Packager Settings for the display settings. Select your repository with the new interface definition files. A tab displays the names and number of interfaces.
Note: After the interface definitions are recognized in
the projects catalog, the IP packager lets the IP Definition feature create bus
interfaces, based on the bus definition, including the ability to infer the bus
interface port mapping.
Important: The IP packager uses a name-matching
heuristic which is based on the logical port names matching the physical ports in the
IP. IP packager automatically detects AXI interfaces when the names of the HDL modules
ports follow the
<interface_name>_<AXI signal
name> convention. For example, s_axi_awvalid, where
s_axi is the interface name and awvalid is one of the AXI signal names used in the interface. Module ports
with the same <interface_name> are mapped into the named
interface. See the
Vivado Design Suite: AXI Reference
Guide (UG1037) for more
information regarding AXI interfaces.Tip: Use short interface names because the IP block
diagram has limited space.