Altera Avalon Verification IP Suite - Manual (Page 128)

2–2 Chapter 2: Tri-State Conduit BFM
Parameters
Avalon Verification IP Suite User Guide May 2011 Altera Corporation
An Avalon-TC interface can have an arbitrary number of ports. Each port has an
associated role name. This role name is an arbitrary string. The difference between
conduit interfaces and Avalon-TC interface is the way in which bidirectional ports are
handled. In Avalon-TC interfaces, a bidirectional port is decomposed into three
distinct unidirectional port signals with role names having the following suffixes:
■ <role name>_in
■ <role name>_out
■ <role name>_outen
The set of bidirectional ports in the Avalon-TC interface are grouped together. The
Avalon-TC interface also includes the
request port, the grant port, and an associated
clock. These request and grant signals are the control signals to and from the arbiter
that controls access to the shared media.
The following port combinations are not legal:
■ In and out roles (without a <role name> _ outen role)
■ In and outen roles (without a <role name> _ out role)
■ Only an outen role (without a <role name>_out role)
Parameters
The Tri-State Conduit BFM supports signals that interface to multiple external
memory devices.
1
For more information about the Avalon-TC interface supported in Qsys, refer to the
Avalon Interface Specifications (version 2.0) .
Table 2–1 lists the parameter settings for the Tri-State Conduit BFM.
Table 2–1. Tri-State Conduit BFM Parameter Settings
Option Default Value Legal Values Description
Role — Any string Specifies the role name of each port.
Width 1 1–1024 Specifies the port width.
USE_INPUT 1 0 or 1 Specifies an input port.
USE_OUTPUT 1 0 or 1 Specifies an output port.
USE_OUTPUTENABLE 1 0 or 1 Specifies an output enable port.
MAX_MULTIPLE_TRANSACTION 1024 —
Specifies the maximum transactions of data
while request and grant signals are asserted.
The value is constraint by the number of roles.