• 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. create a pCell with m-factor

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 143
  • Views 16541
  • 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

create a pCell with m-factor

DavidLou
DavidLou over 6 years ago

hello experts,

I guess this could be very silly/easy question but puzzles me a couple days now. 

I have a customized cell and want to duplicate its instances. if I just make them as instance array (e.g., cell<1000:1>), it'll slow down my simulation dramatically. So I wonder if I can make it pCell with m-factor so that it'll be seen as single instance for the simulator. but I haven't done any pCell work yet. 

I came up following code from some examples I can find but still compliant there's something wrong. any idea or any better ways to achieve this would be greatly appreciated. 

pcDefinePCell(
list( ddGetObj("cell") "cell" "layout"
) ; end of list for first argument

(
( m "int" 1 )
) ; end of parameter list

prog(
let( lp )

; check parameters
m = if( (m<1) 1 m )

for( lp 0 count-1
  inst = dbCreateInst( d_cellView d_master nil 0:lp*1 "R0" 1 )

return(t)

) ; end of body-of-SKILL-code prog

) ; ; end of pcDefinePCell

thanks,

David

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    Hi David,

    If you're using VLS XL, you don't really need to do anything. You can have the parameter m in the CDF (and passed to the simulator as an m-factor) and VLS XL will automatically generate that number of instances in parallel. You can then place them, abut them, use them in modgens as you see fit. There are controls in VLS XL to define the parameter used to represent m, but the default includes the parameter name m.

    Coding inside the PCell itself is probably not the best option as then it removes the flexibility to place or interleave devices to improve matching.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    Hi David,

    If you're using VLS XL, you don't really need to do anything. You can have the parameter m in the CDF (and passed to the simulator as an m-factor) and VLS XL will automatically generate that number of instances in parallel. You can then place them, abut them, use them in modgens as you see fit. There are controls in VLS XL to define the parameter used to represent m, but the default includes the parameter name m.

    Coding inside the PCell itself is probably not the best option as then it removes the flexibility to place or interleave devices to improve matching.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • DavidLou
    DavidLou over 6 years ago in reply to Andrew Beckett

    wow, so straightforward. almost too good to believe. thanks a lot. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidLou
    DavidLou over 6 years ago in reply to Andrew Beckett

    hi Andrew,

    a following up question: I had this cell with "m" parameter and behavioral schematic model, Spectre complains that "m" should be reserved and so ignored. Is there a way not to ignore that? seems my behavioral VerilogA model still works with "m" parameter. 

         Warning from spectre in `cell', during circuit read-in.
         WARNING (SFE-57): "input.scs" 55: Parameter name `m' is reserved for the
         subcircuit multiplicity factor. So a formal parameter of that name is ignored. 

    thanks,

    David

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to DavidLou

    Hi David,

    With spectre, setting m on a hierarchical instance automatically passes that m to all the components underneath - multiplying it with any m on those components. The result is that m ends up on the leaf devices and is handled there (you have to specifically give a special attribute on the definition of m in veriloga to have that pick up the m factor).

    i’m guessing that you’re using pPar to pass the m-factor through the hierarchy - you don’t need to do that, and it’s probably that which is causing the message. 

    This is a bit of guesswork as I can’t see your setup. Perhaps it would be best to go via customer support so we can look at your data?

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidLou
    DavidLou over 6 years ago in reply to Andrew Beckett

    hi Andrew,

    in behavioral schematic, yes I had pPar("m") and it's working now after I remove pPar("m").

    in veriloga model, I have parameter m and apply it to the code as needed. 

     

    working great now. 

    thanks,

    David

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidLou
    DavidLou over 6 years ago in reply to DavidLou

    hi Andrew,

    one more question again although it's about Calibre: when I run LVS by Calibre, it doesn't recognize the m-factor we put in here so it sees less instances in schematic than in Layout thus fails LVS. 

    is there something we can do here for Calibre to recognize the m-factor?

    thanks,

    David

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to DavidLou

    First question - are you seeing m in the CDL netlist?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidLou
    DavidLou over 6 years ago in reply to Andrew Beckett

    hi Andrew, 

    quick answer is no. I don't see m parameter from LVS/cell_extract.src.net. 

    maybe worth mentioning this cell is metal based custom design so I have “LVS BOX unitcap” configured. would this mask the m-factor off?

    thanks,

    David

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to DavidLou

    For the purpose of LVS netlisting (I.e. CDL netlisting) does this end up as a simple instance in the CDL netlist or does a subckt get output ? If there’s an auCdl view of the component, it’s probably just a matter of adding “m” into the instParameters section of the auCdl simulation information in the Base CDF for the component. If that doesn’t work please share what the auCdl sim info looks like in the CDF and whether you have an auCdl stopping view for the cell. 

    I cant answer about “LVS BOX unitcap” because I don’t have access to Calibre (a Mentor product).

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidLou
    DavidLou over 6 years ago in reply to Andrew Beckett

    hi Andrew,

    just feedback after we tried a couple things. after we created new marker layers to recognize the cell in LVS without blackbox, we can see the Multiplier now so no worry.

    thanks,

    David

    • 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