The AMBA VIP Release Notes are installed at:

• Synopsys AMBA VIP Release Notes (PDF)

The AHB SVT Verification Plan is installed in $DESIGNWARE_HOME/vip/svt/amba_svt/latest/doc/VerificationPlans. The README file is installed at $DESIGNWARE_HOME/vip/svt/amba_svt/latest/doc/VerificationPlans/AMBA4/README

The Synopsys VIP for AHB is a suite of advanced verification components and data objects based on SystemVerilog UVM-compliant technology. This on-line help contains information about the classes, functions, and member variables. It shows class hierarchy and contents and it provides links you can use to navigate to more details. Below is the summary of the components and the user interface of the Synopsys AHB VIP.

AHB VIP Components

• svt_ahb_master_agent Defines an agent for the AHB Master component. The master agent encapsulates master sequencer, master driver, and port monitor. The master agent can be configured to operate in active and passive mode.
• svt_ahb_slave_agent Defines an agent for the AHB Slave component. The slave agent encapsulates slave sequencer, slave driver, and port monitor. The slave agent can be configured to operate in active and passive mode. Slave memory is represented by class svt_mem . Slave memory is instantiated in slave agent. In active mode, the slave memory is updated by the slave memory sequence. Refer to slave sequence svt_ahb_slave_memory_sequence in file $DESIGNWARE_HOME/vip/svt/amba_svt/latest/ahb_slave_agent_svt/sverilog/src/vcs/svt_ahb_slave_sequence_collection.svp. A reference to the slave memory instantiated in the slave agent is provided in the slave base sequence. Using the API of this slave memory, you can read or write into the slave memory through the base sequence, or sequence extended from this base sequence. In passive mode, the slave agent updates the slave memory automatically.
• svt_ahb_bus_env Defines Env for AHB Bus component. The Bus Env component is instantiated within the AHB System Env component. The Bus Env currently supports maximum of 16 masters and 16 slaves, including Dummy master and Default slave which are built into the Bus Env. Bus Env component consists of following components:
  • Dummy master
  • Default slave
  • Arbiter
  • Control signals multiplexer
  • Write data multiplexer
  • Read data/response multiplexer
  • Decoder
• svt_ahb_system_monitor Observes transactions across the ports of a single Bus and performs checks between the transactions of these ports. For the list of system checks supported by the system monitor, click on the "Protocol Checks" tab in this class reference documentation.
• svt_ahb_system_env Defines a System ENV for the AHB SVT suite. The AHB System ENV encapsulates AHB master agents, AHB slave agents, system sequencer, AHB System Monitor and AHB system configuration. The number of master and slave agents is configured based on the system configuration provided by the user.

AHB VIP User Interface
Configuration Objects:
Configuration data objects convey the system level and port level testbench configuration. The configuration data objects contain built-in constraints, which come into effect when the configuration objects are randomized. If the configuration needs to be changed later, it can be done through reconfigure() method of the master, slave, or system components. The AHB VIP defines following configuration classes:

• svt_ahb_configuration (AHB Base configuration)
• svt_ahb_system_configuration (AHB System configuration)
• svt_ahb_master_configuration (AHB Master configuration)
• svt_ahb_slave_configuration (AHB Slave configuration)
• svt_ahb_bus_configuration (AHB Bus configuration)

Transaction Objects:
Transaction objects, which are extended from the uvm_transaction base class, define a unit of AHB protocol information that is passed across the bus. The attributes of transaction objects are public and are accessed directly for setting and getting values. Most transaction attributes can be randomized. The transaction object can represent the desired activity to be simulated on the bus, or the actual bus activity that was monitored. AHB VIP defines following transaction classes:

• svt_ahb_transaction (AHB Base transaction)
• svt_ahb_master_transaction (AHB Master transaction)
• svt_ahb_slave_transaction (AHB Slave transaction)

Analysis port:
The port monitor in the Master & Slave agents provides an analysis port. At the end of the transaction, the port monitor within the Master & Slave agents provides the completed svt_ahb_transaction from their analysis port.
The analysis port used by port monitor within Master agent and Slave agent is:

• svt_monitor :: item_observed_port

Callbacks:
Callbacks are an access mechanism that enable the insertion of user-defined code and allow access to objects for scoreboarding and functional coverage. Each master and slave component is associated with a callback class that contains a set of callback methods. AHB VIP provides following callbacks classes:

• svt_ahb_master_callback (Master callback class)
• svt_ahb_slave_callback (Slave callback class)
• svt_ahb_master_monitor_callback (Master monitor callback class)
• svt_ahb_slave_monitor_callback (Slave monitor callback class)
• svt_ahb_system_monitor_callback (System monitor callback class)

Interfaces and modports:
SystemVerilog models signal connections using interfaces and modports. Interfaces define the set of signals which make up a port connection. Modports define collection of signals for a given port, the direction of the signals, and the clock with respect to which these signals are driven and sampled. AHB VIP provides below interfaces:

• svt_ahb_if (Top level interface, which contains an array of master & slave port sub-interfaces)
• svt_ahb_master_if (sub-interface for master ports)
• svt_ahb_slave_if (sub-interface for slave ports)

• svt_ahb_slave_modport (Modport used to connect master VIP component to slave DUT port)
• svt_ahb_master_modport (Modport used to connect slave VIP component to master DUT port)
• svt_ahb_debug_modport (Modport used to access the debug port signals)

AHB sequence collection:
For a complete list of sequences provided with the AHB VIP, please click on the "Sequences" tab in this class reference documentation.