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.
When I generate a Pcell using a function and it's arguments, my pcells do not generate correctly.
I understand why, once the pcell is compiled, he has unknown variables, the one that where passed by the function. IfI replace this variables with a parameter of the pcell, the functions arguments are stored and the pcell compiles.
I don't want to use variables for this to prevent having a long list.
Is there another way of doing this, some sort of hidden parameter or property?
So this doesn't work:
procedure( makeAcell(arg1 arg2)
pcDefinePcell( ... ...w = arg1*arg2
This does work, but it's not what I want:
procedure( makeAcell(arg1 arg2) ...;PCELL PARAMETERS((Arg1 int arg1) (Arg2 int arg2)) ...))
The problem is that the variables arg1 and arg2 are out of scope when the body of the pcell is evaluated. You might think that you could solve this with SKILL++ (which has lexical scoping), but pcDefinePCell is not supported in SKILL++ (it can call SKILL++ functions, but can't be used in SKILL++ - mainly because the pcell wouldn't be able to store information about the lexical environment in which it was called). One way is to store the arguments on the cellView somewhere (as properties say), but another might just be to do:
procedure(makeACell(arg1 arg2)eval(`pcDefinePCell( ... ... w=,arg1*,arg2) ;pcDefinePCell) ; eval) ; procedure
The quote before the pcDefinePCell is a backquote. This means that the code is not evaluated - but a list of the code - but rather than a normal quote, backquote allows selective evaluation. You precede the variable with a comma to selectively evaluate it.
To illustrate what I mean:
val1=20val2=30lst=`(a b ,val1 c ,val2)
then lst will contain (a b 20 c 30)
In reply to Andrew Beckett:
Ok, thanks, this seems to work, with one exception. If I use backquotes in a for loop, this doesn't seem to work.
procedure(makeACell(arg1 arg2)eval(`pcDefinePCell( ... ... w=,arg1*,arg2for( n 1 ,arg1do something) ;for) ;pcDefinePCell) ; eval) ; procedure
It looks like that he still needs the arg1 in the for loop.
In reply to RVERP:
I tried something in the ciw, if I enter:
'(x ,y z)
I still get:
(x y z) I expected (x 1 z)
What's wrong here??
The way you build your list is worng if you want y to be evaluated do it that way
In reply to berndfi:
In the example I want to build a list with x y z, where only y is evaluated. This should be the way to do it (it's exactly the same example as in the cadence manual, only I have a different outcome as in the manual.)
In your first example, this code worked perfectly:
procedure(makeACell(arg1 arg2)eval(`pcDefinePCell( list(ddGetObj("BBDlib") "mypcell" "layout") ( (myp 1) ) w=,arg1*,arg2 for( n 1 ,arg1 fprintf(stderr "w is %L, n is %L\n" w n) ) ;for ) ;pcDefinePCell) ; eval) ; procedure
It output this when the pcell evaluated:
makeACell(3 4)Generating Pcell for 'mypcell layout'.w is 12, n is 1w is 12, n is 2w is 12, n is 3
As for the second case, it's because you have the wrong quotation mark. It should be a backquote not a normal single quote. So ` not '
Check your pcell code in case you've used the wrong quote. Normal single quote prevents evaluation completely, whereas backquote allows selective evaluation when expressions are preceded by comma.