• 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 Design
  3. Hierarchy editor - Implication of "stop point" on netli...

Stats

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

Hierarchy editor - Implication of "stop point" on netlist

tito80
tito80 over 11 years ago

Hi, I am using Virtuoso hierarchy editor (config view) in IC6.1.5. As per the documentation, I am setting stop point on a particular instance so that the netlister does not desced further into that instance's schematic hierarchically. But I am seeing no change in the netlist produced with that config. For e.g., it was earlier:

subckt subckt_A

...

ends sunckt_A 

I1 (n1 n2) subckt_A

And after putting stop point on I1, it is still the same. So what does the "stop point" actually do? 

 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    That shouldn't happen. Are you definitely running ADE with the config view? Look in the banner of the ADE window and make sure it says that the view name is the config. If you create a config but simulate with the schematic, it won't use anything from the config.

    I just tried this (adding a stop point), and the underlying subckt did not get netlisted.

    However, since you said that you put the stop point on a particular instance (I first tried it on a particular cell), then you need to make sure you've got all instances of the subckt in question marked as stop points. Otherwise it will continue to expand the hierarchy for one of them and netlist the subckt definition.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tito80
    tito80 over 11 years ago

    Andrew,

    Thanks for the help. My responses would be:

    1)  Yes, I did ensure that config view for the top_design is used.

    2) Note that I am trying to do it on an instance basis -- say instance 'my_inst' of subckt definition 'my_subckt'. Cadence HE UG says: "You can specify a stop point on a single instantiation of a cell that prevents the instance from being expanded when the hierarchy is expanded.". So I have absolutely no problem if my_subckt gets expanded (to cater to other instances), but 'my_inst' should probably not point to that my_subct any more. 

    3) As per your advice, I tried the stop-point on a cell-basis keeping everything else undisturbed (viewnames to be used, etc.). But there, I face this error:

    Netlist Error: Cannot find any info on instance "my_inst" in cell-view "my_lib" "parent_cell_of_my_inst" "schematic"

    Netlist Error: Some cell-views used inside this block could not be netlisted in analog context

    Look forward to your help.

    - Tito 

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Point 2. The problem with "probably not point to that my_subct any more" is there is no definition of what it should be netlisted as. There's no point having an instantiation of a block that is not defined somewhere - it will fail in simulation. So you'd have to have a definition somewhere (e.g. in an include file). If it was not well defined what the subckt name would end up being referenced as, you wouldn't know what to do with it. So whilst in theory you can add a stop point on one instance only, I'm not sure how useful that would be in practice.

    Point 3. You have to have CDF defined for the cell, so that it knows how to netlist it. Easiest way is to go into the schematic for the block, and do Create->CellView->From Cellview and create the symbol - but do so in "Modify" mode - which means it won't clobber your symbol -  maybe it might add some text onto it but you can delete that. It should recreate the CDF if it was missing though - it's the spectre simInfo that is key here.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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