Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 1761
  • 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

"m" multiplier not picked up when LVS

DavidLou

hello experts,

it was working really well until I'm at LVS stage. I created a wrapper cell with multiplier defined like bellow:

cdfCreateParam( cdfId
    ?name "m"
   ?prompt "Multiplier"
   ?type "string"

   ?defValue "1"
   ?storeDefault "yes"
   ?parseAsNumber "yes"
   ?parseAsCEL "yes"
)

the simulator can accept that and interpenetrate, layout generator can use that and generate multiple instances of that device accordingly. but when I run LVS (sorry Calibre though), it doesn't seem to understand the schematic is asking for multiple of them so it complains why layout side has so many devices missing at schematic side.

anything I could make LVS understand this Multiplier?

thanks,

David

Parents
  • Andrew Beckett

    David,

    See: auCDL: Netlister does not include m-factor on hierarchical blocks

    You just need to set:

    auCdlPrintMultiplicityFactor=t

    in your .simrc file.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    David,

    See: auCDL: Netlister does not include m-factor on hierarchical blocks

    You just need to set:

    auCdlPrintMultiplicityFactor=t

    in your .simrc file.

    Regards,

    Andrew.

Children
  • DavidLou
    in reply to Andrew Beckett

    thanks Andrew, I'll try that out.

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.