Slave assertions, Axi3 assertion configuration – Altera Mentor Verification IP Altera Edition AMBA AXI3/4TM User Manual
Page 91
SystemVerilog AXI3 and AXI4 Slave BFMs
Slave Assertions
Mentor VIP AE AXI3/4 User Guide, V10.2b
73
September 2013
1.
Refer to
for details of simulator time-steps.
Slave Assertions
Each slave BFM performs protocol error checking using the built-in assertions.
Note
The built-in BFM assertions are independent of programming language and simulator.
AXI3 Assertion Configuration
By default, all built-in assertions are enabled in the slave BFM. To globally disable them in the
slave BFM, use the
command as the following example illustrates:
set_config(AXI_CONFIG_ENABLE_ALL_ASSERTIONS,0)
Alternatively, individual built-in assertions can be disabled by using a sequence of
and
commands on the respective assertion. For example, to disable assertion
**_CONFIG_SLAVE_END_ADDR
Configures the end address map for the
slave.
**_CONFIG_READ_DATA_REORDERING_DEPTH
The slave read reordering depth. Refer to
the AMBA AXI Protocol specification for
more details. Default: 1.
**_CONFIG_MAX_OUTSTANDING_WR
Configures the maximum number of
outstanding write requests from the
master that can be processed by the
slave. The slave back-pressures the
master by setting the signal
AWREADY=0b0 if this value is exceeded.
**_CONFIG_MAX_OUTSTANDING_RD
Configures the maximum number of
outstanding read requests from the
master that can be processed by the
slave. The slave back-pressures the
master by setting the signal
ARREADY=0b0 if this value is exceeded.
Error Detection
**_CONFIG_ENABLE_ALL_ASSERTIONS
Global enable/disable of all assertion
checks in the BFM.
0 = disabled
1 = enabled (default)
**_CONFIG_ENABLE_ASSERTION
Individual enable/disable of assertion
check in the BFM.
0 = disabled
1 = enabled (default)
Table 4-2. Slave BFM Configuration (cont.)
Configuration Field
Description