Stats

  • Locked Locked
  • Replies 7
  • Subscribers 144
  • Views 18531
  • 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

How to automate simulation of testbench, cycling schematic DUT in it.

JanH

 Hi,

 I'd like to automate the process of simulating a testbench (always the same toplevel testbench) in which the DUT's schematic view gets replaced automatically. 

We have a library with lots of DUT's (we don't know how many at this point but probably a lot, that's why we want to automate this), all with the same symbol but different topology in it. 

We would like to simulate all these DUT's with the same testbench using the same set of stimuli and post process the results afterwards. This is a very time consuming and repetitive action which we'd like to automate.

The problem I'm facing however is that I have no idea on how to automate this:

Taking care that for each DUT present in a library we can force the recreation of a netlist (using a config view as we intend to use extracted views for some of the cells instantiated in those DUT's), start the simulation on this recreated netlist, post-process the results (store it and/or merge it with the previous results) and when finished start over again with a new DUT.

 Any advise on how to accomplish this would be great!

Thank you.

 

Jan.

Parents

  • Hi Jan,

    OK. So the way to do that would be to use the tree view in the HED, and specify for instance DUT that you want the view to use to be "schematic", but the inherited view list to be "extracted ..." (i.e. extracted at the beginning). This means that it will pick up schematic for the DUT itself, but any instantiated cells will prefer extracted over schematic.

    And because you used the tree view, which is an instance binding, your config would not need to change from one DUT to the next.

    You'd set the design() in your OCEAN script to be design("myLib" "testbench" "config")

    Does that help?

    Regards,

    Andrew.

Reply

  • Hi Jan,

    OK. So the way to do that would be to use the tree view in the HED, and specify for instance DUT that you want the view to use to be "schematic", but the inherited view list to be "extracted ..." (i.e. extracted at the beginning). This means that it will pick up schematic for the DUT itself, but any instantiated cells will prefer extracted over schematic.

    And because you used the tree view, which is an instance binding, your config would not need to change from one DUT to the next.

    You'd set the design() in your OCEAN script to be design("myLib" "testbench" "config")

    Does that help?

    Regards,

    Andrew.

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.