Port Index
$#! · 0-9 · A · B · C · D · E · F · G · H · I · J · K · L · M · N · O · P · Q · R · S · T · U · V · W · X · Y · Z
A
 after_export
 analysis_export
 analysis_export#(T)
B
 before_export
 blocking_put_port
G
 get_ap
 get_peek_export
 get_peek_request_export
 get_peek_response_export
M
 master_export
P
 pair_ap
 put_ap
 put_export
 put_request_export
 put_response_export
R
 req_export
 req_port
 request_ap
 response_ap
 rsp_export
 rsp_port
S
 seq_item_port
 slave_export
T
 transport_export
The export to which a data stream of type AFTER is sent via a connected analysis port.
The export to which the other stream of data is written.
This export provides access to the write method, which derived subscribers must implement.
The analysis_export provides the write method to all connected analysis ports and parent exports:
The export to which a data stream of type BEFORE is sent via a connected analysis port.
The export to which one stream of data is written.
The blocking_put_port is used to send the generated stimulus to the rest of the testbench.
Transactions passed via get, try_get, peek, or try_peek (via any port connected to the get_peek_export) are sent out this port via its write method.
The get_peek_export provides all the blocking and non-blocking get and peek interface methods:
The get_peek_export provides all the blocking and non-blocking get and peek interface methods to the response FIFO:
The get_peek_response_export provides all the blocking and non-blocking get and peek interface methods to the response FIFO:
Exports a single interface that allows a master to put requests and get or peek responses.
The comparator sends out pairs of transactions across this analysis port.
Transactions passed via put or try_put (via any port connected to the put_export) are sent out this port via its write method.
The put_export provides both the blocking and non-blocking put interface methods to any attached port:
The put_export provides both the blocking and non-blocking put interface methods to the request FIFO:
The put_export provides both the blocking and non-blocking put interface methods to the response FIFO:
This export provides the blocking put interface whose default implementation produces an error.
The push sequencer requires access to a blocking put interface.
Transactions passed via put or try_put (via any port connected to the put_request_export) are sent out this port via its write method.
Transactions passed via put or try_put (via any port connected to the put_response_export) are sent out this port via its write method.
Drivers or monitors can connect to this port to send responses to the sequencer.
This port provides an alternate way of sending responses back to the originating sequencer.
This analysis port is used to send response transactions back to the originating sequencer.
Derived driver classes should use this port to request items from the sequencer.
Exports a single interface that allows a slave to get or peek requests and to put responses.
The put_export provides both the blocking and non-blocking transport interface methods to the response FIFO: