• 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. How to Manage External Netlist Files

Stats

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

How to Manage External Netlist Files

twen
twen over 9 years ago

I am able to simulate with external Spice netlist with similar approach in "How to Simulate a Subcircuit (Netlist) With Spectre in ADE"  what I did is to set the model to the full path name of the simulated netlist file in the newly created symbol view and this work fine.I can also create a separate text or spice view like "myspice", "mydspf" to hold the netlist files and let the design manager to checkin the netlist file. This requires me to create one symbol view like "mysymbolview" and another spice view like "myspiceview." I am trying to combine these two views into a single one. I now have two new questions:

(1) Can I set the value of the component parameter "model" to a skill function that returns the concatenation of the absolute full path name of this symbol view and a file name like this "fullpathto/mylibpath/mycell/mysymbolview/spice.spi?" The benefit of this is that we do not need to update the hard coded full path name once this cell is copied to another library.

(2) Can I let the third party library design manager to check in "mylibpath/mycell/mysymbolview/spice.spi" to mysymbolview.I tried putting a data.reg in my home directory:

+DataFormat schematicSymbol {
    Co_Managed = master.tag thumbnail_128x128.png symbol.oa spice.spi;
}

and the design manager does not seem to pay attention to this registration file after I restarted Virtuoso. I am new to how the data manager works by the way. If you can confirm that (2) can only be done by the third party design manager, I can ask our tool support engineer to relay this question to the library design manager vendor.

Any help to solve the above two questions is greatly appreciated.

getVersion

"@(#)$CDS: virtuoso version 6.1.6-64b 12/07/2015 20:18 (sjfbm186) $"

TJ

  • Cancel
Parents
  • twen
    twen over 9 years ago

    Hi, Andrew,

    Thank you for the response on Sunday! I just created case 46006238 for the netlister to natively support the spectre/spice/dspf textual views.

    We are currently using Cliosoft and I could not make it automatically check in the spice file inside the "shadow" symbol view directory. I won't spend time trying to make this work as it only simplifies things.

    Before the nestlister natively supports spice/spectre/dspf text views, I am still interested in a skill or other functions that I can put in the value field of an view's CDF/cell view property that returns the path name of the view so that I do not need to manually modify it after I copy this view to another library or rename it.

    Thanks,

    Tingjun

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • twen
    twen over 9 years ago

    Hi, Andrew,

    Thank you for the response on Sunday! I just created case 46006238 for the netlister to natively support the spectre/spice/dspf textual views.

    We are currently using Cliosoft and I could not make it automatically check in the spice file inside the "shadow" symbol view directory. I won't spend time trying to make this work as it only simplifies things.

    Before the nestlister natively supports spice/spectre/dspf text views, I am still interested in a skill or other functions that I can put in the value field of an view's CDF/cell view property that returns the path name of the view so that I do not need to manually modify it after I copy this view to another library or rename it.

    Thanks,

    Tingjun

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information