Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 13589
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Help Needed for multiple transactions

archive

Hello Friends,

    I'm coding a UVC(Universal Verification Component) in System Verilog Class Based methodology. For the protocol, which I've coded, I could successfully get one complete transaction. But I couldn't get second transaction or any successive transactions.

   I'm getting struck at "get_next_item"(for second trasaction)....I tried to debug but couldn't proceed further.

So, could someone help me in removing this problem so that I could get multiple transactions.

Thanks in advance,
Jalli


Originally posted in cdnusers.org by jaally

  • I think you are not creating custom sequence and setting default_sequence of the sequencer. Please look at the xbus uVC example on how to create custom sequence and use it by calling set_config_string() call.

    e.g.
          set_config_string("*tx_agent.driver", "default_sequence", "cdn_pack_tlm_sequence");


    By default, the sequencer will run a simple sequence which only creates one transaction.



    Originally posted in cdnusers.org by pjigar

  • Thanks PJigar!
    It did help me!
    Regards,
    Jalli


    Originally posted in cdnusers.org by jaally

  • Hi Jally,
    I guess you Want to get Conigure Count  to Get Multiple transactions.
    "urm_driver" has a int Variable 'count' with which u can have Multiple Transactions just as in eRM,
    Use  set_config_int("*.driver","count",5);  in the Main_sve Class. you will get 5 Transactions for this Config.This will Solve your Problem.

    Regards,
    Ramesh Pal


    Originally posted in cdnusers.org by ramesh_pal_yadav

  • Hi Pal,

    This is even cool! Anyway, thanks for that additional point.

    Regards,
    Jalli


    Originally posted in cdnusers.org by jaally

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.