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

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

Parents
  • Andrew Beckett

    It sounds as if you really want the proper spice view or spectre text view support. Please contact customer support about this, because we need to know that you need this rather than providing cumbersome workarounds...

    I'm reluctant to give you workarounds that will involve some messy SKILL code to include the file during simulation. Note that you don't have to make the filename a full path in ADE - you can give a local path and then use Setup->Simulation files and set the include path (and this can be relative to the working directory, e.g. "./mylib" ).

    The data.reg approach you're taking ought to work, but it depends on which DM tool you're using - which tool is it?

    That said, I think the "right" way to do this is ultimately to have two views - the symbol and then a SPICE/spectre text view which you can switch into using the view list or hierarchy editor.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    It sounds as if you really want the proper spice view or spectre text view support. Please contact customer support about this, because we need to know that you need this rather than providing cumbersome workarounds...

    I'm reluctant to give you workarounds that will involve some messy SKILL code to include the file during simulation. Note that you don't have to make the filename a full path in ADE - you can give a local path and then use Setup->Simulation files and set the include path (and this can be relative to the working directory, e.g. "./mylib" ).

    The data.reg approach you're taking ought to work, but it depends on which DM tool you're using - which tool is it?

    That said, I think the "right" way to do this is ultimately to have two views - the symbol and then a SPICE/spectre text view which you can switch into using the view list or hierarchy editor.

    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.