Stats

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

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
Parents

  • 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
Reply

  • 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
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.