• 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. SpiceIn terminal name mapping

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 13654
  • 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

SpiceIn terminal name mapping

caver456
caver456 over 7 years ago

We need to use SpiceIn to build a Cadence schematic from a CDL netlist that was generated from a different schematic entry tool.  Terminal names for primitive devices are not always the same between the netlist generated from the other tool and the existing Cadence symbol.

For example, the rsicr30k Cadence symbol has terminals 'PLUS' and 'MINUS'.  In the other schematic entry tool and in the netlist it generates which we want to read in to Cadence using spiceIn, the terminal names are 'T1' and 'T2'.

CDF provides for this in the termMapping field, but, it does not look like the SpiceIn Device Map file provides for terminal name mapping.  It seems like we could do this by modifying the CDF, but we would need to do so temporarily, i.e. discard these CDF terminal mapping changes after SpiceIn is complete.  Is there an easy way to accomplish this terminal name mapping, preferably without touching the CDF?

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    Mapping of a primitive device is done via the termOrder not by names, so I wouldn't expect the names to matter here. However, it's quite likely I've misunderstood your problem and seeing what an instance line in the CDL netlist looks like might help clarify.

    Perhaps it would be better to ask customer support (providing them with the details of what the CDL netlist looks like)?

    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