• 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 Design
  3. Global net name mapping for spectre netlist

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 14822
  • 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

Global net name mapping for spectre netlist

Amar Kumar
Amar Kumar over 5 years ago

Hi,

I have generated a spectre netlist where it has below global nets.

global 0 vss! vdd!

Now, I want to get rid off the "!" sign and want something like "global 0 vdd vss" to appear it in my spectre netlist.

I have explored a bit and found with added below lines in .simrc , it does what I want exactly.

"hnlMapNetInName = list(list("+" nil) list("(" nil) list(")" nil) list("," nil) list("/" nil) list("." nil) list("$" nil) list("[" nil) list("]" nil) list("<" "[") list(">" "]") list("!" nil) )"

But the above method works for CDL netlist. 

Is there any way to get similar thing done in spectre netlist also ?

Thanks In Advance!

Regards,

Amar

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Hi Amar,

    I'm not sure this is a good idea, but you could use a different variable to do this specifically for spectre. See Name mapping for spectre netlisting has changed in IC61X

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Amar Kumar
    Amar Kumar over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    The "hnlSpectreMapNetInName" variable worked great with old mechanism.

    Thank you very much for your continuous help.

    Regards,

    Amar

    • 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