• 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. termMapping

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 144
  • Views 14165
  • 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

termMapping

jmss
jmss over 13 years ago

Hi,

What is the meaning of the \, in this termMapping example:

  termMapping = (nil D \,d)

This is usualy found in simInfo->hspiceD, I think.

Thanks.

João M. S. Silva

  • Cancel
  • Quek
    Quek over 13 years ago

    Hi Joao M S Silva

    This is a disembodied properties list (DPL) for mapping current data from the relevant terminals. You can refer to appendix B in $CDSHOME/doc/cdfuser/cdfuser.pdf for more details. Alternatively, open up cdnshelp using "$CDSHOME/tools/bin/cdnshelp &" cmd and search for "accessing subcircuit simulation data".

    It means that terminal D in the model files is mapped to pin d in the symbol. The first item is usually "nil" because it is a DPL. The comma (,) is the instance terminal delimiter.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jmss
    jmss over 13 years ago

    Thanks Quek.

    Quek said:

    It means that terminal D in the model files is mapped to pin d in the symbol. The first item is usually "nil" because it is a DPL. The comma (,) is the instance terminal delimiter.

    But the symbol has pin cdsTerm("D"). Why is it mapped to "d"?

    And how do I know that a comma must be used? Sometimes a : is used.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 13 years ago

    Hi João M. S. Silva

    Hspice netlist is usually created in lowercase and so lowercase should be used in termMapping field too. You can refer to COS solution 1815106 for more details. Spectre termMapping uses colon. HspiceD uses comma.


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jmss
    jmss over 13 years ago

    Hi Quek,

    Thanks.

    Maybe I was confusing termMapping with propMapping. In propMapping, (nil A B) means A=<value(B)> will appear in the netlist, right?

    But in termMapping, (nil A B) means terminal A will appear as simulator's terminal B, is that it?

    In HSPICE, \,d is the drain terminal, so we map it to cdsTerm("D") with (nil D \,d).

    It seems like propMapping and termMapping order logic is different: in propMapping the first refers to the netlist and the second to the database, while in termMapping the first refers to the database and the second to the netlist.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 13 years ago

    Hi João M. S. Silva

    Actually it is the opposite. "D" is the drain terminal which is mapped to the pin "D" in the symbol. Lowercase is usually used so pin "D" is written as "d". You can refer to the spectre termMapping example in cdfuser. I think it will clear things up. : )


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jmss
    jmss over 13 years ago

    Hi Quek,

    Yes, with the help of Jean-Baptiste Lasherme I realized this is not only used for netlisting but for result analysis.

    It is all clear now, I hope :)

    Thanks and best regards,

    João M. S. Silva

    • 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