• 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 SKILL
  3. How to specify a SPICE source file in Virtuoso hierarchy...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 2625
  • 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 specify a SPICE source file in Virtuoso hierarchy Editor (config view) from SKILL/OCEAN code

MFahmy
MFahmy over 7 years ago

Hi, 

In the virtuoso Hierarchy Editor (config file) one can right click a certain cell and choose set cell view --> Specify SPICE source file and then enters a path to a certain spice netlist file, now my question is how to set this from a SKILL/OCEAN script, is there a skill function like setSourcFile which achieves this functionality ? I looked through the hdb functions but couldn't find something related to specifying a path to a spice file

Virtuoso Version: ICADV12.3-64b.8

Thanks 

Fahmy 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    Fahmy,

    This would need the "hdb" SKILL functions to edit a config view, but unfortunately there is no SKILL function available to set the source file attribute using SKILL. The couple of previous minor requests for this have resulted in R&D saying that they have no plans to implement a SKILL API to do it when you can do it from the hierarchy editor. 

    You could define a stopping view and then include the SPICE source as a model file instead using OCEAN (you'd have to ensure that the CDF termOrder information is in the correct order though).

    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