• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. "Hidden" parameters in Pcell

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 144
  • Views 2554
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

"Hidden" parameters in Pcell

RVERP
RVERP over 12 years ago

Hello,

 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))
 ...
))

 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    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=20
    val2=30
    lst=`(a b ,val1 c ,val2)

    then lst will contain (a b 20 c 30)

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RVERP
    RVERP over 12 years ago

    Ok, thanks, this seems to work, with one exception.  If I use backquotes in a for loop, this doesn't seem to work.

     example:

     procedure(makeACell(arg1 arg2)
    eval(`pcDefinePCell(
      ...
      ...
      w=,arg1*,arg2
    for( n 1 ,arg1
    do something
    ) ;for
    ) ;pcDefinePCell
    ) ; eval
    ) ; procedure

    It looks like that he still needs the arg1 in the for loop.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RVERP
    RVERP over 12 years ago

     I tried something in the ciw, if I enter:

    y=1

    and then:

     '(x ,y z)

    I still get:

    (x y z)            I expected (x 1 z)

    What's wrong here??

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • berndfi
    berndfi over 12 years ago

     The way you build your list is worng if you want y to be evaluated do it that way

    list(y)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RVERP
    RVERP over 12 years ago

     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.)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    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 1
    w is 12, n is 2
    w 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.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information