
• A conduit port can also have a specific role named export. Ports with this role name are exported from
the current system design module to the Conduit BFM module I/O.
The conduit API constructs or deconstructs transactions. Transactions are driven out on the physical conduit
interface.
To simulating conduit interfaces, you must understand the following points:
1. At the beginning of the simulation, registers that store data sent to the output ports are empty.
2. The Conduit BFM drives ‘x’ to the output ports until you rewrite the registers by calling the set_<role
name> API.
3. Initially, bidirectional ports work as input ports. You can change conduit port functionality by calling
the set_<role name>_oe API.
4. The Conduit BFM prints a message when a bidirectional port changes from an input to an output, and
vice versa.
5. Bidirectional ports drive register values to the interface when this API is set to 1. Otherwise, bidirectional
ports work as input ports.
6. You can call the get_<role name> API to obtain the value coming from the input and bidirectional ports.
Parameters
Table 11-1: Conduit BFM Parameter Settings
DescriptionLegal ValuesDefault ValueOption
Specifies the role name of each port.Any stringN/ARole
Specifies the port width.1–10241Width
Specifies the direction of the signal.input, output,
bidir
inputDirection
Conduit BFM API
event_input_<role name>_change
event_input_<role name>_changePrototype:
Verilog HDL: N.A.
VHDL: None
Arguments:
voidReturns:
Notifies the testbench when a port changes its value<role name>. For a bidirec-
tional port, this event is only triggered if its input value defers from its last input
value.
Description:
VHDLLanguage support:
Conduit BFM
Altera Corporation
Send Feedback
Parameters
11-2
Commenti su questo manuale