Stats

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

Re: Simulating subcircuit within ADE with view other than spectre

slim5

Hi,

Following the steps listed in this URL, community.cadence.com/cadence_blogs_8/b/rf/archive/2009/01/07/tip-of-the-week-how-to-simulate-a-subcircuit-netlist-with-spectre-in-ade I was able to instantiate a spice netlist and run simulations within ADE.

For the step, "Make a copy of this symbol view and call the new view "spectre.", is it possible to create the steps for a view name to something else other than spectre? For example, is it possible to create a view call "LocalSimViews" instead of "spectre"?

Regards,

S Lim

  • Yes.  You can give it any view name that you want, but then you also need to include that view name in the switch and stop view lists.  The advantage of using spectre as the view name is that it is already defined as a stopping view, assuming you are using the viewlist templates for spectre.

     

    Regards,

    TOM

  • Hi,

    I tried with different names such as SpectreSims and picked this view in my hierarchy config view, but ADE totally ignore this view and I do not see the instance being used in the generated netlist (input.scs). For reference, I am using IC6.1.6

    Regards,

    S Lim

  • Did you add "SpectreSims" into the stop list in the hierarchy editor? If you don't do that, it won't see the view as a stop view and so will try to traverse its hierarchy (of which there is no hierarchy, and so there's nothing to be netlisted).

    As Tom said, you need it in the stop list. Picking it as the view to use is one part, but defining it as a stopping view is also necessary.

    Regards,

    Andrew.

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.