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 trying to create procedure trigerred by starting of a simulation in ocean script with many corners using runParam() command.
I found way to do that with the Flowchart fucntions and it works ( I am using IC6.15 and ADE-L is opened), see the code bellow:
procedure(Sim_trigger_PCT() let((sess_local) if(asiGetCurrentSession() != nil then
sess_local = asiGetCurrentSession() asiChangeFlowchartStep(asiGetFlowchart(sess_local) ?name 'asiNetlist ?preFunc 'CCSLoadScript_try ) );;if );;let);;proc
procedure( CCSLoadScript_try(sess) printf("Test\n"));;proc
But I want procedure CCSLoadScript_try to have more arguments, see the same code little bit modified:
procedure(Sim_trigger_PCT() let((sess_local num_local)
num_local = 1 if(asiGetCurrentSession() != nil then
sess_local = asiGetCurrentSession() asiChangeFlowchartStep(asiGetFlowchart(sess_local) ?name 'asiNetlist ?preFunc (CCSLoadScript_try sess_local num_local) ) );;if );;let);;proc
procedure( CCSLoadScript_try(sess num) printf("Test %d\n" num));;proc
In that case the script is trigerred only once (there is only one text note "Test 1" in the log file), and then NO simulation has been done.
Thanks in advance for the help!
The reason why you only got one "Test 1" is because it actually called your function at the time you called asiChangeFlowchartStep, not at netlisting time. It would have tried to use the return value of the function as the preFunc, which is not what you want.
You can't just add arbitrary function signatures - the preFunc will always be called with a single argument in this case - so adding more won't help you. However, you could take advantage of SKILL++ lexical scoping - so for example, if you use the code below (put it in a file with ".ils" as the suffix) - and it will then work. The globalProc is defined within the scope containing num_local and so can access it.
procedure(Sim_trigger_PCT() let((sess_local num_local) globalProc(CCSLoadScript_try(sess) printf("Test %d\n" num_local) ; just for fun, increment the variable num_local++ ) num_local = 1 if(asiGetCurrentSession() != nil then sess_local = asiGetCurrentSession() asiChangeFlowchartStep(asiGetFlowchart(sess_local) ?name 'asiNetlist ?preFunc 'CCSLoadScript_try ) );;if );;let);;proc
In reply to Andrew Beckett:
Thanks for the response, from Cadence Support I received and another workaround also.
So I will try both of them.