Friday, November 21, 2008     Register | Login | Search | Contact Us
     
   
     
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Forums > Functional Verification > SystemVerilog

Subject: How frequently should Transactor work?
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
davyzhu
Posts: 90
Online: User is Offline
4/16/2007 10:53 PM  
Hi all,

I am always confused with the how frequently should transactor is triggered to work.

For instance, there is a transactor XACTOR_A get a transaction from transactor XACTOR_B, and there is a Mailbox containing transactions connecting these two transactors.

I always using the following simple methods. XACTOR_A check if the Mailbox is not empty every clock (i.e. @posedge clk). If the Mailbox is not empty, XACTOR_A get the transaction from it and run its work sequentially.

When using the upper method, I feel the transactor work on physical layer(because it work depend on clock, and was triggered every clock cycle).

Is there any intuitive explanation about how frequently should Transactor work(especially in CDNS's uRM or SNPS's VMM or MENT's AVM)? Any suggestions will appreciated!

Best regards,
Davy
tpylant
Posts: 87
Online: User is Offline
5/07/2007 3:45 PM  
If you use mailbox.get(), that will block until there is data in the mailbox.

Example:
mailbox mbox = new();
always begin
xactor = mbox.get();
do_something(xactor);
end

The always block will call get() and return a value for xactor and send it to do_something. However, if there is nothing in mbox, then it will stop and wait until there is a put() called from XACTOR_B.

Tim
Posting to forums is available to community members only.
Login or Register
Forums > Functional Verification > SystemVerilog > How frequently should Transactor work?


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.