Stats

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

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? 

 

Parents

  • 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.

Reply

  • 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.

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.