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 am using ic5141 usr6 and mmsim72 with IBM 0.13 PDK and SMIC cmos090 PDK
when i use cmos090 PDK with default configuration,the resulting line of simulation in the wavescan is solid and is very clear.
But when i use IBM PDK with default configuration,the resulting line of simulation is dotted and i have to change it to solid everytime after the result be plotted.How can i set the default line type in the wavescan no matter which PDK i am using?
Hi minciYou can refer to the "trace variables" section of wavescan manual by clicking here. Here is the setting for .cdsinit file:
envSetVal("wavescan.trace" "lineStyle" 'string "solid")In general, you can look for any environment variables for the tools (schematic editor, layout editor, spectre, ade, etc) in the .cdsenv files following directory:$CDSHOME/tools/dfII/etc/toolsE.g. $CDSHOME/tools/dfII/etc/tools/wavescan/.cdsenvIn case the above does not work, we have an internal solution which gives the following suggestion:
1. Open Display Resources Manager in CIW by selecting Tools ->Display Resources Manager...2. Click "Edit..." in Display Resources Tool Box.3. Change "Tech Lib Name" to ABC.4. Search layers "y0" and modify the display style.5. Re-do step 4 to change "y1" "y2" ........ "y9".6. Save the display setup.
In reply to Quek:
hi,Quek,thanks for help!
I have written the following line in my .cdsinit file of my work directory:
envSetVal("wavescan.trace" "lineStyle" 'string "solid")
and i have found in the .cdsenv file in my $CDSHOME/tools/dfII/etc/tools/wavescan/ has already set wavescan.trace to solid.
but it doesn't work.
then i try the last method and this time it works!
but i' wonder whether changing the layers "y0,y1,y2...." like this will change the layout display,or it just changes the line in the wavescan?
In reply to minci:
i find that when i have changed the y0...etc in the Display Resources Tool Box and go to save. It overrides my display.drf file which was copied from the PDK while making my work directory as the PDK instruction said.Does it matter or not for the display.drf file have been changed?
Hi minciI don't quite understand your reply so let me make a guess. You have copied the display.drf file from the pdk directory to your working directory and after modifying and saving the y0,y1,etc packets, you found that the display.drf file in your working directory has changed. So you are wondering if it matters? May I know if this is your question? It does not matter. display.drf is just for viewing the layout so it can be customized according to your preferences.Best regardsQuek
Your guess is right!
now i can change my display.drf file without worry.
But still, i am somewhat confusing that why i have to change display.drf to modify the line type in the wavescan?
Why the envSet cmd in the .cdsinit file didn't work?
When using wavescan with ADE, it plots signals with the same colour and line style as the corresponding probe in the schematic, to make sure it is obvious which signal is which. Since probing and other schematic layers are controlled by layers in the tech file, and their appearance is controlled via the display.drf, that is what sets the appearance of the lines in wavescan within ADE (as well as the probe colours).
When running wavescan standalone, the .cdsenv settings are used; i.e. it doesn't have the colours overridden by ADE.
In reply to Andrew Beckett:
Thanks all for the above information! That helps when change line color and line style from "dash" to "solid".
However, I also want to change default symbol style and symbol count in wavescan.
I set in .cdsenv as follows:
wavescan.trace symbolsOn string "true"
wavescan.trace symbolStyle string "circle"
wavescan.trace symbolCount string "All points"
Only the first command works. Can display.drf change symbol style and symbol count? And where? Thanks again!