• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. TB Simplification

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 64
  • Views 13790
  • 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

TB Simplification

archive
archive over 18 years ago

Hello All, In the process of verification, we develop many TestBenches those are useful for the module-level verification only. Once the module is verified, a new TB is developed for another module. Is there any alternative way to this approach, wherein we can reduce the time spent on the development of TB for each and every module? Is there any reusable approach for this? Any ideas or suggestions are welcome. -Vivek


Originally posted in cdnusers.org by prasad_vc
  • Cancel
  • archive
    archive over 18 years ago

    Hi Vivek.

    That's a very good question! Fortunately the URM (Universal Reuse Methodology) is designed specifically for this problem.
    Whether you choose to code in e, SystemVerilog or SustemC, the methodology guides you through building a reusable testbench based on modular components. These guidelines have been developed through very close cooperation between Cadence and many customers over several years, so they really work.

    The idea is to build everything in component form (e.g. bus interface components, sequence generators, protocol layering).
    Each component is then used in a "testbench" that itself is designed to be plugged into a higher level testbench if needed.

    You should take a look at http://myipcm.cadence.com/ for the online books that describe the methodology.
    Also, get in touch with your local Cadence AE who can help you plan you verification.


    Originally posted in cdnusers.org by stephenh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    To add to what Steve just said, with recent OVM announcement, hopefully we will see more easily accessible guidelines soon. Having gone through VMM & AVM, I've been longing to learn eRM/URM, hopefully OVM will provide that opportunity.

    Ajeetha, CVC
    www.noveldv.com


    Originally posted in cdnusers.org by ajeetha
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    I have not used AVM myself, but I believe it shares many principles with URM, so the merge of these two is a natural one.
    I think perhaps that OVM will bring a lot of great automation to the very solid base laid down by the two methodology libraries.

    Of course there is a lot more to good re-use than simply using a library such as URM, and the full Cadence Plan to Closure Methodology addresses the higher level concerns such as how to make integrate the different technologies (formal, coverage-driven, emulation etc), and how to use executable plans to automate so much of the day-to-day reporting and analysis that we (alas) have to do.


    Originally posted in cdnusers.org by stephenh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Thanks Steve, I'll go through the "myipcm" and also contact the cadence AE. -Vivek


    Originally posted in cdnusers.org by prasad_vc
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Cool. You can of course ask questions here in the forum too, but I think if you're just starting down the road of re-use methodology, then a couple of hours spent with an experienced AE will give you the most value :-)
    Good luck!


    Originally posted in cdnusers.org by stephenh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information