• 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 override netlisting mapping of instance names and...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 15221
  • 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 override netlisting mapping of instance names and node names?

SharksFan
SharksFan over 14 years ago

Hi,

I'm using IC6.1.5 and an external simulator.  It has a predefined set of mapping functions that convert schematic names to netlist names.  For example, if I name a node in my schematic to begin with a "." (like .monitor for example), this name get converted to _net0 during netlisting.

I want to override this default behavior so that I can control the mapping, but my attempts so far have been unsuccessful.

Here's what I did:

I defined the $SIMRC to point to a directory in which I have my own .simrc file.  In my .simrc file, I defined

hnlSetDef('mapNetFirstChar
    list('("." "net_")
    )
)

After this, I have completely exited IC and restarted.  I reopen my saved state for the external simulator and from the ADE menu I do a Simulation > Netlist > Recreate.  However, my netlist still contains _net0 instead of the desired net_monitor for the net named .monitor in my schematic.

What am I missing?  Do I need to force unbinding somehow since mapNetFirstChar has been previously defined by the external simulator?  How do I do the unbinding?

Thanks in advance for all tips and help.

SharksFan

  • Cancel
Parents
  • SharksFan
    SharksFan over 14 years ago

    Hi Andrew,

    Yes, the simulator is not a Cadence product, but has been integrated into Cadence and appears as a choice in ADE (the default choice, in fact).  I believe the context file for this simulator defines the mapping which I wish to alter.

    I will have a look at the soultions you have listed and see if I can make some progress using them.  Thank you.

    I assume from your response that the .simrc file contents would only come into play if the coding of the netlisting for the external simulator has been written to account for entries in the .simrc, otherwise it is basically ignored.  Is that correct?

    The real issue I'm trying to solve is that different versions of this non-Cadence product use inconsistent mapping and this breaks the OCEAN scripts that people have made as they are forced to move to updated versions.  I'm looking for a way to add a layer on top which redefines the mapping back to the original version and still allows use of the updated versions.

    SharksFan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • SharksFan
    SharksFan over 14 years ago

    Hi Andrew,

    Yes, the simulator is not a Cadence product, but has been integrated into Cadence and appears as a choice in ADE (the default choice, in fact).  I believe the context file for this simulator defines the mapping which I wish to alter.

    I will have a look at the soultions you have listed and see if I can make some progress using them.  Thank you.

    I assume from your response that the .simrc file contents would only come into play if the coding of the netlisting for the external simulator has been written to account for entries in the .simrc, otherwise it is basically ignored.  Is that correct?

    The real issue I'm trying to solve is that different versions of this non-Cadence product use inconsistent mapping and this breaks the OCEAN scripts that people have made as they are forced to move to updated versions.  I'm looking for a way to add a layer on top which redefines the mapping back to the original version and still allows use of the updated versions.

    SharksFan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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