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 trying to write a generic procedure to plot waveform that takes the plot macro parameters as procedure input arguments.
Basically, I want something like this :
procedure( my_procedure( signal signal_name strip ...stuff... )
plot( sprintf( "%s ?expr '("%s") ?strip "%d" " signal signal_name strip ) )
It seems like I cannot plot something out of a sprintf because sprintf does not return an object, right ?
Is there any way to get that working ?
Well, sprintf returns a string, so you can't just pass that to plot. In general trying to do run-time evaluation of a macro like plot is going to be problematic, so I'd suggest that you do:
procedure(my_procedure(signal signal_name strip) awvPlotWaveform(currentWindow() || newWindow() list(signal) ?expr list(signal_name) ?stripNumber list(strip)) ; hardCopy stuff)
So use the underlying function.
In reply to Andrew Beckett:
Thanks you very much for your answer. It seems to be working !
Do you have any documentation on the awvPlotWaveform function ? I can't find anything in the manual.
What is the difference with the Plot function ?
In reply to The Setlaz:
It's documented. In IC615 it's in <ICinstDir>/doc/vivaxlskill/vivaxlskill.pdf (and cdnshelp would find it). In IC5141 it's in <ICinstDir>/doc/skartistref/skartistref.pdf (I searched in cdsdoc, and found it).
The plot() function has some convient options - it will create a window if one doesn't exist already, and you can just do plot(sig1 sig2 sig3) for example - the awvPlotWaveform() is a bit more verbose.
Alright. Does it mean that the plot() macro is kind of wrapper for awvPlotWaveform() function ?
I will look at the documentation tomorrow - I only looked at OCEAN Refence and SKILL Language Reference and SKILL User's Guide maual. Thanks a lot for your help.
Effectively, yes. It's actually a wrapper around either awvSimplePlotWaveform or awvPlotExpression - which are all very similar to awvPlotWaveform.
Thanks for the details !
I have another question regarding the plot. I would like to change the defaults size of the graph being saved.
I tried creating a window using the syntax you gave a few times :
awvCreatePlotWindow(?bBox list(100:100 1000:600))
But when I open the plot image, it is still a 800 x 600 graph.
I also tweaked my .cdsenv to make Viva to plot to large window using the following settings :
viva.graphFrame width string "1920"viva.graphFrame height string "1152"
It works, when I run OCEAN without the -nograph option, the graph is plotted to a big OCEAN window, but it still saved to a 800 x 600px.
I'm running Cadence 126.96.36.199