
File
Directory
Library
altera_primitives.v
220model.v
sgate.v
altera_mf.v
altera_lnsim.sv
cyclonev_atoms.v
arriav_atoms.v
mentor/cyclonev_atoms_ncrypt.v
mentor/arriav_atoms_ncrypt.v
<Device Sim Lib>/
Device Simulation
Library
(The device simulation
library is not needed
with Modelsim-Altera.)
*.vo
*.vho
(Mixed-language simulator is
needed for Verilog HDL and
VHDL mixed design)
<User project directory>/
EDA Netlist Writer
Generated Post-Fit
Simulation Model
*.v
*.sv
*.vhd
(Mixed-language simulator is
needed for Verilog HDL and
VHDL mixed design)
<User project directory>/
User testbench files
BFM API hierarchy Format
For post-fit simulation, you must call the BFM API in your test program with a specific hierarchy. The
hierarchy format is:
<DUT>.\<HPS>|fpga_interfaces|<interface><space>.<BFM>.<API function>
Where:
•
<DUT>
is the instance name of the design under test that you instantiated in your test bench that consists
of the HPS component.
•
<HPS>
is the HPS component instance name that you use in your Qsys system.
•
<interface>
is the instance name for a specific FPGA-to-HPS or HPS-to-FPGA interface. This name can
be found in the fpga_interfaces.sv file located in
<project directory>
/
<Qsys design
name>
/synthesis/submodules.
•
<space>
—You must insert one space character after the interface instance name.
•
<BFM>
is the BFM instance name. In
<ACDS install>
/ip/altera/hps/postfitter_simulation, identify the
SystemVerilog file corresponding to the interface type that you are using. The SystemVerilog file contains
the BFM instance name.
For example, a path for the Lightweight HPS-to-FPGA master interface hierarchy could be formed as follows:
top.dut.\my_hps_component|fpga_interface|hps2fpga_light_weight .h2f_lw_axi_master
HPS Simulation Support
Altera Corporation
cv_54030
BFM API hierarchy Format
29-16
2013.12.30