
SystemVerilog API Overview
Creating Transactions
Mentor Verification IP AE AMBA AXI4-Stream User Guide, V10.3
25
April 2014
The SystemVerilog Master BFM API allows you to create a master transaction by providing
only an optional burst_length argument to indicate the number of transfers within a packet. All
other protocol transaction fields automatically default to legal protocol values to create a master
transaction record. Refer to create_master_transaction() for default protocol transaction field
values.
The SystemVerilog Slave BFM API allows you to create a slave transaction with no arguments.
All protocol transaction fields automatically default to legal protocol values to create a slave
transaction record. Refer to create_slave_transaction() for default protocol transaction field
values.
The SystemVerilog Monitor BFM API allows you to create a monitor transaction with no
arguments. All protocol transaction fields automatically default to legal protocol values to
create a complete monitor transaction record. Refer to create_monitor_transaction() for default
protocol transaction field values.
If you change the default value of a protocol transaction field, it is valid for all future
transactions until you set a new value.
create_*_transaction()
The create_master_transaction(), create_slave_transaction() and create_monitor_transaction()
BFM API functions create a master, a slave, and a monitor transaction, respectively.
Example 2-4 shows a master BFM test program creating a master transaction with a packet
length of 10 transfers.
operation_mode An enumeration to hold the operation mode of the transaction.
The following are two types of operation mode:
AXI4STREAM_TRANSACTION_NON_BLOCKING
AXI4STREAM_TRANSACTION_BLOCKING
The field content is not transferred over the AXI4-Stream
protocol signals during a transaction.
transfer_done An unsized bit array to hold the done flag for each transfer within
a packet. The field content is not transferred over the protocol
signals during a transaction.
transaction_done A bit to hold the done flag for a complete transaction. The field
content is not transferred over the protocol signals during a
transaction.
Table 2-1. Transaction Record Fields (cont.)
Transaction Field Description
Comentarios a estos manuales