Slave assertions, Example 4-2. slave bfm disable all assertions – Altera Mentor Verification IP Altera Edition AMBA AXI4-Stream User Manual

Page 46

Mentor Verification IP AE AMBA AXI4-Stream User Guide, V10.3

SystemVerilog Slave BFM
Slave Assertions

April 2014

Slave Assertions

The slave BFM performs protocol error checking using built-in assertions.

Note

The built-in BFM assertions are independent of programming language and simulator.

By default, all built-in assertions are enabled in the slave BFM. To globally disable them in the
slave BFM, use the

Example 4-2. Slave BFM Disable All Assertions

set_config(AXI4STREAM_CONFIG_ENABLE_ALL_ASSERTIONS,0)

Alternatively, individual built-in assertions may be disabled by using a sequence of

and

commands on the respective assertion.

assertion checking for the TLAST signal changing between the TVALID and TREADY
handshake signals.

Example 4-3. Slave BFM Individual Assertion Enable/Disable

// Define a local bit vector to hold the value of the assertion bit vector
bit [255:0] config_assert_bitvector;

// Get the current value of the assertion bit vector
config_assert_bitvector =
bfm.get_config(AXI4STREAM_CONFIG_ENABLE_ASSERTION);

// Assign the AXI4STREAM_TLAST_CHANGED_BEFORE_TREADY assertion bit to 0
config_assert_bitvector[AXI4STREAM_TLAST_CHANGED_BEFORE_TREADY] = 0;

// Set the new value of the assertion bit vector
bfm.set_config(AXI4STREAM_CONFIG_ENABLE_ASSERTION,
config_assert_bitvector);

Note

Do not confuse the AXI4STREAM_CONFIG_ENABLE_ASSERTION bit vector with
the AXI4STREAM_CONFIG_ENABLE_ALL_ASSERTIONS global enable/disable.

To re-enable the AXI4STREAM_TLAST_CHANGED_BEFORE_TREADY assertion, follow
the code sequence in

and assign the assertion within the

AXI4STREAM_CONFIG_ENABLE_ASSERTION bit vector to 1.

For a complete listing of AXI4-Stream assertions, refer to “