Stats

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

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

Parents
  • Andrew Beckett

    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.

  • DavidLou
    in reply to Andrew Beckett

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

Reply
  • DavidLou
    in reply to Andrew Beckett

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

Children
No Data

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.