Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
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.
By "external simulator" I assume you don't mean a Cadence simulator? ADE netlisters use a wrapper around the underlying OSS capability, and so initialize these kind of settings per simulator.
You have to do it by customizing the netlister so that the new settings get done within nlInitialize for the netlister you're using. Similar examples are shown in these two solutions:
If you're using hspiceD or spectre there may be variables to do what you want - not 100% sure - but if you state if it's one of these I can check.
In reply to Andrew Beckett:
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.
In reply to SharksFan: