Home

VMM 1.2

Blocking and Non-blocking Communication Using the TLI
Posted on Thursday, March 31, 2011 - 10:36 by John Aynsley from the site Verification Martial Arts
John Aynsley, CTO, Doulos In the previous blog post I introduced the VCS TLI Adapters for transaction-level communication between SystemVerilog and SystemC. Now let’s look at the various coding styles supported by the TLI Adapters, and at the same time review the various communication options available in VMM 1.2. We will start with the options for sending transactions from SystemVerilog to SystemC. VMM 1.2 allows transactions to be sent through the classic VMM channel or through the new-style TLM ports, which come in blocking- and non-blocking flavors.
John Aynsley
Posted in
VMM-to-SystemC Communication Using the TLI
Posted on Tuesday, March 22, 2011 - 13:12 by John Aynsley from the site Verification Martial Arts
John Aynsley, CTO, Doulos I have said several times on this blog that the presence of TLM-2.0 features in VMM 1.2 should ease the task of communicating between a SystemVerilog test bench and a SystemC reference model. Now, at last, let’s see how to do this – using the VCS TLI or Transaction Level Interface from Synopsys. The parts of the TLI in question are the VCS TLI Adapters between SystemVerilog and SystemC.
John Aynsley
Posted in
Blocking/Non-blocking Transport Adaption in VMM 1.2
Posted on Wednesday, September 1, 2010 - 19:20 by John Aynsley from the site Verification Martial Arts
John Aynsley, CTO, Doulos One neat feature of the SystemC TLM-2.0 standard is the ability provided by the so-called simple target socket to perform automatic adaption between the blocking and non-blocking transport calls; an initiator that calls b_transport can be connected to a target that implements nb_transport, and vice-versa. VMM 1.2 provides similar functionality using the vmm_connect utility. vmm_connect serves four distinct purposes in VMM 1.2.
John Aynsley
Posted in
Connecting Multiple Analysis Ports to a Single Analysis Export
Posted on Tuesday, February 9, 2010 - 10:24 by JL Gray from the site Verification Martial Arts
Today’s post was written by my colleague Asif Jafri. Enjoy! JL by Asif Jafri Asif Jafri is a verification engineer at Verilab. This post introduces the VMM implementation of the Transaction Level Modeling (TLM) 2.0 specification of how you can connect multiple broadcasting ports to the same receiving export using peer ID’s. Figure 1 shows multiple initiators communicating with the same target. The initiators can be monitors on either side of your DUT passing transaction to a single scoreboard which keeps track of the transactions and does various checks.
JL Gray
Posted in
You get real hierarchy with VMM1.2
Posted on Tuesday, February 9, 2010 - 01:41 by Wei-Hua Han from the site Verification Martial Arts
If you look at VMM1.2 classes, you may find that almost all new() functions have an argument, vmm_object parent. The purpose of this argument is to build a parent-child hierarchy within a VMM1.2 based environment, so that VMM1.2 can provide an infrastructure where users can access the components inside the environment through hierarchical path and name.
Wei-Hua Han
Posted in
Syndicate content