Altera Avalon Verification IP Suite - Manual (Page 49)

3–6 Chapter 3: Avalon-MM Slave BFM
Functional Description
Avalon Verification IP Suite User Guide May 2011 Altera Corporation
Block Diagram
Figure 3–4 shows a block diagram of the Avalon-MM Slave BFM. The BFM includes
the following major blocks:
■ Avalon-MM Slave API—Provides methods to get commands and create responses
to commands from the Avalon-MM master (DUT).
■ Command Descriptor—Accumulates the fields of a command sent by the
Avalon-MM master and sends completed commands to the Avalon-MM Slave
BFM when requested.
■ Avalon-MM Interface Monitor—Monitors activity coming from the Avalon-MM
Master (DUT) and stores commands in the Client Command Queue.
■ Response Generator and Data Cache— In memory_mode the Slave BFM models a
single port RAM. A write operation stores the data in an associative array and
generates no response. A read operation fetches data from the array and drives it
on the response side of the Avalon interface. This mode simplifies loopback
testing.
■ Avalon-MM Slave Interface Driver—Drives responses to the system interconnect
fabric. For burst transfers, there is a separate transfer for each word of the burst.
The client testbench can instruct the Slave BFM to assert
waitrequest for each
word of the burst to test the functionality of the Avalon-MM master.
■ Public Events—Provides status response that arrives together with the data. The
public event signals indicate the status of the Master’s request such as successful
completion, timeout, or error.
S
rc_1
Signals the first read response. The event name is signal_response_complete.
S
atc
Signals the end of the test. The event name is signal_all_transactions_complete
Table 3–2. Key to Annotations in Figure 3–3 (Part 2 of 2)
Symbol Description