• 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. ihdl symbol template or post-import skill trigger?

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13430
  • 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

ihdl symbol template or post-import skill trigger?

drdanmc
drdanmc over 7 years ago

Is there a way to either specify a symbol template to be used when ihdl creates a symbol (like the tsgTemplateMasters and schSetEnv("tsgTemplateType" "MySymbol") in Virtuoso) or alternatively a way to specify a skill procedure to be executed afterwards?

Currently we call ihdl from the command line to create the symbol but would like to have things like cdsTerm() labels and [@libName] [@cellName] [@instanceName] labels be generated as well.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    Doesn't seem to be possible. A number of discussion about it which hint that it ought to be possible, but the AEs in some other CCRs (plus me trying it just now) suggest that it doesn't work.

    There are (at least) CCRs 733468 and 939584. Both seem to have ended up in a status where not a lot of attention is going to be paid to them - so you probably will have to request this yourself. 

    You may need to write some code to do something like this for each symbol in Virtuoso afterwards:

    schPinListToSymbol("opamp090" "mystrinv" "symbol" schSymbolToPinList("opamp090" "mystrinv" "symbol"))

    (having set the tsgTemplate env var first).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • drdanmc
    drdanmc over 7 years ago
    Thanks for looking into it. I filed a case to request this.

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