Stats

  • Locked Locked
  • Replies 6
  • Subscribers 64
  • Views 16372
  • 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

Transaction level modelling ?

archive

Hi , I have confusion regarding transaction level modelling.can someone explain it with an example? what exactly is transaction level modelling & how it can be achieved using system verilog? -thanks -Manmohan


Originally posted in cdnusers.org by mssajwan
Parents

  • Hello,

    You can build a transaction-level model in any high-level structured programming language, including e, SystemVerilog, SystemC, C/C++ and more.

    A transaction level model is usually a high-speed model that trade-offs speed for cycle accuracy to analyze system-level performance and features. Therefore there isn't a need to build signal level drivers, monitors. The components exchange data using a function call passing objects and synchronizing on high-level system events.

    Users have built transaction level models in e for years mainly for verification (separating data generation, scoreboaring, coverage, from pin-level drivers monitors) as well as for modeling systems. This is the methodology that eRM and now OVM recommends for structuring a verification environment for modularity and reuse.

    In OVM, there is also a TLM api provided to assist with data exchange between components using well defined semantics. For example, blocking/non-blocking requests of data, 0-time broadcast of data, FIFO, etc.

    You can find a couple of TLM examples in OVM distribution in ovm-1.1/examples/tlm. You can get this distribution at http://www.ovmworld.org/downloads.php.

    Thanks,

    Umer


    Originally posted in cdnusers.org by umer
Reply

  • Hello,

    You can build a transaction-level model in any high-level structured programming language, including e, SystemVerilog, SystemC, C/C++ and more.

    A transaction level model is usually a high-speed model that trade-offs speed for cycle accuracy to analyze system-level performance and features. Therefore there isn't a need to build signal level drivers, monitors. The components exchange data using a function call passing objects and synchronizing on high-level system events.

    Users have built transaction level models in e for years mainly for verification (separating data generation, scoreboaring, coverage, from pin-level drivers monitors) as well as for modeling systems. This is the methodology that eRM and now OVM recommends for structuring a verification environment for modularity and reuse.

    In OVM, there is also a TLM api provided to assist with data exchange between components using well defined semantics. For example, blocking/non-blocking requests of data, 0-time broadcast of data, FIFO, etc.

    You can find a couple of TLM examples in OVM distribution in ovm-1.1/examples/tlm. You can get this distribution at http://www.ovmworld.org/downloads.php.

    Thanks,

    Umer


    Originally posted in cdnusers.org by umer
Children
No Data

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.