Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 4318
  • 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

Simulate Different Views in ADE Maestro

anurans

I have recently migrated from Cadence IC 6.0.X to IC 23.10.060 and Spectre 23.10.442 for analog simulations. I have a schematic, layout and a calibre views for a circuit and would like to stope the simulation at different views. This I setup in the "environment" option of Maestro:

 

However the simulation only seems to run when the stop is set to "spectre". I am not sure whether this results the calculations/simulation for "schematic only" or "calibre extracted parasitic" view. In old IC6 version, when the calibre is set as the stop view, simulation is run for the circuit with extracted parasitic view, not on the schematic. What I am missing in this setup ? Any input is appreciated.

Thanks in advance 

Parents
  • Andrew Beckett

    This hasn't changed since the dawn of time (at least for the last 30 years!).

    The principle is that as the hierarchy is traversed, when it encounters an instance of a cell, it searches along the Switch View List and picks the first view in that list that is found (so the order matters). If the found view is in the Stop View List then it doesn't expand the hierarchy of that view but just stops there - you'll get an instance but no subckt (the order of the Stop View List doesn't matter).

    In your example, you have calibre after schematic in the Switch View List and hence if you have both views, it will prefer the schematic over the calibre view (which you don't want). It's also highly unlikely that you'd ever want the calibre view to be the point you stop at (especially if that's some kind of extracted stopping view). Typically you'd just have the simulator stop views (i.e. spectre) in the Stop View List. 

    I'd move calibre to before schematic in the Switch View List and change the Stop View List to spectre.

    Andrew

  • anurans
    in reply to Andrew Beckett

    Thanks for your reply Andrew. Selecting Calibre as the first view solves the problem. But what does spectre view mean here ? If the simulator picks the spectre view, does it go to the .subsct level of the netlist ? If the schematic is picked, it only stops at the instance level and no information about the transistors ?

  • Andrew Beckett
    in reply to anurans

    There's no special meaning of the "spectre" view name, but typically any primitive component has a view with the same name as the simulator/netlister - and it's used to indicate a stopping view. If the netlister stops at a particular instance, it will print the instance (using information in the CDF Simulation Information (for spectre in this case)) and not produce a subckt for this cell. The CDF contains information about how to format the device - such as the terminal order, parameters to be netlisted and so on.

    I'm not sure what you mean by "if the schematic is picked"? Do you mean if you put "schematic" in the stop list? I'm not sure that would be of any use - it would just try (assuming there's info in the CDF) to netlist an instance of that block but not actually the contents.

    Andrew

Reply
  • Andrew Beckett
    in reply to anurans

    There's no special meaning of the "spectre" view name, but typically any primitive component has a view with the same name as the simulator/netlister - and it's used to indicate a stopping view. If the netlister stops at a particular instance, it will print the instance (using information in the CDF Simulation Information (for spectre in this case)) and not produce a subckt for this cell. The CDF contains information about how to format the device - such as the terminal order, parameters to be netlisted and so on.

    I'm not sure what you mean by "if the schematic is picked"? Do you mean if you put "schematic" in the stop list? I'm not sure that would be of any use - it would just try (assuming there's info in the CDF) to netlist an instance of that block but not actually the contents.

    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.