Altera Mentor Verification IP Altera Edition AMBA AXI3/4TM - Manual (Page 32)

Mentor VIP AE AXI3/4 User Guide, V10.2b 14
SystemVerilog API Overview
Configuration
September 2013
Configuration
Configuration sets timeout delays, error reporting, and other attributes of the BFM. Each BFM
has a
set_config() function that sets the configuration of the BFM. Refer to the individual BFM
APIs for details.
Each BFM also has a get_config() function that returns the configuration of the BFM. Refer to
the individual BFM APIs for details.
set_config()
The following test program code sets the burst timeout factor for a transaction in the master
BFM.
// Setting the burst timeoutfactor to 1000
master_bfm.set_config(AXI_CONFIG_BURST_TIMEOUT_FACTOR, 1000);
Note
The above test program code segment is for AXI3 BFMs. Substitute the
AXI_CONFIG_BURST_TIMEOUT_FACTOR enumeration with
AXI4_CONFIG_BURST_TIMEOUT_FACTOR for AXI4 BFMs.
get_config()
The following test program code gets the protocol signal hold time in the master BFM.
// Getting hold time value
hold_time = master_bfm.get_config(AXI_CONFIG_HOLD_TIME);
Note
The above test program code segment is for AXI3 BFMs. Substitute the
AXI_CONFIG_HOLD_TIME enumeration with AXI4_CONFIG_HOLD_TIME for AXI4
BFMs.
Creating Transactions
To transfer information between a master BFM and slave DUT over the protocol signals, a
transaction must be created in the master test program. Similarly, to transfer information
between a master DUT and a slave BFM, a transaction must be created in the slave test
program. To monitor the transfer of information using a monitor BFM, a transaction must be
created in the monitor test program.
When you create a transaction, a Transaction Record is created and exists for the life of the
transaction. This transaction record can be accessed by the BFM test programs during the life of
the transaction as it transfers information between the master and slave.