• 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. Modifying an extracted view for post layout simulation.

Stats

  • Locked Locked
  • Replies 16
  • Subscribers 128
  • Views 23372
  • 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

Modifying an extracted view for post layout simulation.

ghrshomali
ghrshomali over 13 years ago

I am using IC 5.1.41 and Calibre 2010.4. I have an extracted view which is extracted by Calibre and I want to use it for post-layout simulation. When I modify the extracted view, Analog environment gives the following error:

ERROR: Netlister: the cellview **** was modified since last extraction.

Is there any way to modify an extracted view and use it for post layout simulation?

Thank you very much.
 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    You can use:

    dbSetConnCurrent(geGetEditCellView())

    and then save it. Note that this should obviously be done with caution because you may be destroying the integrity of the connectivity when you are editing the extracted view.

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • ghrshomali
    ghrshomali over 13 years ago

     Thank you very much Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • pirateKing08
    pirateKing08 over 12 years ago

    wow fantastic trick!

     This saves editing the extracted netlist and doing a command line run simulation. Could this not be incorporated into the Parasitic Aware Design flow? With a health warning I agree. I found it useful as my layout effort is in a different time zone and when I found the extracted view was damaging my performance more than expected  I wanted to alter the design to make it more robust against the layout effects. A quick change to a device parameter within the extracted view then seeing if this has helped the extracted simulation result before issuing the change to layout is so useful

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

    The idea is that you ought to be able to use the parameterisation flow to (e.g. the Variables and Parameters) assistant to do these "what if" experiments, but currently it's not possible with extracted views. But it's being looked into...

    Andrew.

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

     Hi Andrew,

    what's the equivalent command in ic6?

    Thank you.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    It's the same. dbSetConnCurrent(geGetEditCellView())

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kamel ACHOUR
    Kamel ACHOUR over 11 years ago

     Hi Andrew,

     I would like to know if there is another ( new??) possibility to simulate an extracted view which was modified by me. In fact, I use Cadence 5 because I use an old version of PDK technology and, when I choose to delete some parasitics on the extracted view, a message appear which is :  "ERROR (OSSHNL): Error(s) found during netlisting. The netlist may be corrupt or may not be produced at all. To generate correct netlist, fix the errors and re-netlist." I 've seen on your previous topic that we can use the command "dbSetConnCurrent(geGetEditCellView())" to solve this probleme but it doesn't work in my case. Besides, It appear a new error message : " Message: *Error* dbSetConnCurrent: argument #1 should be a database object (type template = "d") at line 20 of file "*ciwInPort*" Entering new debug toplevel due to error ". So, I would like to know if I can fix that problem.

     Regards

     Kamel

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

    Kamel,

    For the dbSetConnCurrent call I suggested to work, geGetEditCellView() needs to return the dbId of the cellView. This means that you must have the extracted view open, editable, and also the window must be the current window (select one of the pulldown menus in the window to force this). I suspect it isn't the current window, and so maybe geGetEditCellView() is returning nil.

    Also bear in mind that removing the parasitics might leave the circuit open-circuit (if it is resistors that you have removed).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kamel ACHOUR
    Kamel ACHOUR over 11 years ago

    Andrew,

    Thanks for the reply. Now, I can simulate my modified extracted view without problems. In reality, the problem was that the extracted view was not opened/editable during the simulation.

    Appreciate your help.

    Regards

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

     Hi Andrew,

    Do you know how to probe an extracted view after a simulation? 

    I'm simulating a cct including an extracted sub-block.  Clearly, it's possible to probe the t op level schematic to look at signals going into and coming out of this sub-block. Is there an easy way of probing the inside of this block on the extracted view?

    I have tried saving the nodes and paths I'm interested in on the schematic view of this sub-block, but don't seem to be able to select or save nodes and paths on the extracted view.

    Could you help?

    Thank you.

     

    • 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