DS824 Datasheet, PDF (47/55 Pages) Xilinx, Inc – LogiCORE IP AXI Bus Functional Models (v3.00.a)

LogiCORE IP AXI Bus Functional Models (v3.00.a)
Determining Fully-Qualified Instance Name
One design challenge is to determine the fully-qualified instance name for EDK AXI BFM pcores for use in the API
commands. In general, the path in a standalone XPS project resembles:
<Project Instance>.<MHS Instance>. <MHS Instance>.<BFM Core Name>
where:
• <Project Instance> is the instance name of the EDK system, not including the test bench name
• <MHS Instance> is the instance name given to the AXI BFM core name in the user MHS file
• < BFM Core Name > is the core name of the AXI BFM pcore in EDK. Options include:
• cdn_axi4_master_bfm_wrap
• cdn_axi4_slave_bfm_wrap
• cdn_axi4_lite_master_bfm_wrap
• cdn_axi4_lite_slave_bfm_wrap
• cdn_axi4_streaming_master_bfm_wrap
• cdn_axi4_streaming_slave_bfm_wrap
• cdn_axi3_master_bfm_wrap
• cdn_axi3_slave_bfm_wrap
Any additional levels of hierarchy, such as when using with ISE Project Navigator, are added to the left of the path.
To determine the fully-qualified name of the AXI BFM core in EDK, elaborate the design in a simulator, before
specifying the API function calls. This is shown in Figure 5 for the example above, using ModelSim.
X-Ref Target - Figure 5
Figure 5: ModelSim Example Hierarchy
DS824 July 25, 2012
www.xilinx.com
47
Product Specification