• 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. Custom IC SKILL
  3. How to automate simulation of testbench, cycling schematic...

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
JanH over 15 years ago

 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.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    If all your device under tests have equivalent symbols (i.e. same pin out, same positions), then something like the following would do the trick:

    duts='("mycell1" "mycell2" "mycell3")
    tbCV=dbOpenCellView("myLib" "testbench" "schematic")
    ; assume the DUT instance has an instance name of "DUT"
    simulator('spectre)
    design("myLib" "testbench" "schematic")
    ; set up common simulation setup
    analysis(...)
    desVar(...)
    foreach(dut duts
      ; replace the instance with the new symbol, then check and save
      dutInst=dbFindAnyInstByName(tbCV "DUT")
      dutMaster=dbOpenCellViewByType("myLib" dut "symbol")
      dutInst~>master=dutMaster
      schCheck(tbCV)
      dbSave(tbCV)
      ; assume you want to keep the results for each DUT separate
      resultsDir(strcat("/path/to/somewhere/" dut))
      ; this will renetlist, because the top cellView changed
      run()
      ; post processing here
    )

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    If all your device under tests have equivalent symbols (i.e. same pin out, same positions), then something like the following would do the trick:

    duts='("mycell1" "mycell2" "mycell3")
    tbCV=dbOpenCellView("myLib" "testbench" "schematic")
    ; assume the DUT instance has an instance name of "DUT"
    simulator('spectre)
    design("myLib" "testbench" "schematic")
    ; set up common simulation setup
    analysis(...)
    desVar(...)
    foreach(dut duts
      ; replace the instance with the new symbol, then check and save
      dutInst=dbFindAnyInstByName(tbCV "DUT")
      dutMaster=dbOpenCellViewByType("myLib" dut "symbol")
      dutInst~>master=dutMaster
      schCheck(tbCV)
      dbSave(tbCV)
      ; assume you want to keep the results for each DUT separate
      resultsDir(strcat("/path/to/somewhere/" dut))
      ; this will renetlist, because the top cellView changed
      run()
      ; post processing here
    )

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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