Altera Mentor Verification IP Altera Edition AMBA AXI4-Li Manual de usuario Pagina 143

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 413
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 142
VHDL API Overview
Creating Transactions
Mentor Verification IP AE AXI4-Lite User Guide, V10.3
143
April 2014
The master BFM API allows you to create a master transaction by providing only the address
argument for a read, or write, transaction. All other protocol transaction fields automatically
default to legal protocol values to create a complete master transaction record. Refer to the
create_read_transaction() and create_write_transaction() procedures for default protocol read
and write transaction field values.
The slave BFM API allows you to create a slave transaction by providing no arguments. All
protocol transaction fields automatically default to legal protocol values to create a complete
slave transaction record. Refer to the create_slave_transaction() procedure for default protocol
transaction field values.
The monitor BFM API allows you to create a slave transaction by providing no arguments. All
protocol transaction fields automatically default to legal protocol values to create a complete
slave transaction record. Refer to the create_monitor_transaction() procedure for default
protocol transaction field values.
Note
If you change a protocol transaction field value from its default, it is then valid for all
future transactions until a new value is set.
create*_transaction()
There are two master BFM API procedures available to create transactions,
create_read_transaction() and create_write_transaction(), a create_slave_transaction() slave
BFM API procedure, and a create_monitor_transaction() monitor BFM API procedure.
For example, to create a simple write transaction with a start address of 1, and a single data
phase with a data value of 2, the master BFM test program would contain the following code:
operation_mode An enumeration to hold the operation mode of the
transaction. The two types of operation_mode are:
AXI4_TRANSACTION_NON_BLOCKING
AXI4_TRANSACTION_BLOCKING
write_data_mode An enumeration to hold the write data mode control flag.
The types of write_data_mode are as follows:
AXI4_DATA_AFTER_ADDRESS
AXI4_DATA_WITH_ADDRESS
transaction_done A bit to hold the done flag for a transaction when it has
completed.
Table 7-1. Transaction Fields (cont.)
Transaction Field Description
Vista de pagina 142
1 2 ... 138 139 140 141 142 143 144 145 146 147 148 ... 412 413

Comentarios a estos manuales

Sin comentarios