Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13197
  • 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

encLayerEnclosure_2 in fluid guardring is not working.

Venu Ch

In below syntax I given encLayerEnclosure_2 is 0.12. But it is creating 0.085. Please let me know.
addGroup=dbCreateParamInstByMasterName(
  geGetEditCellView()       
   "cmos32lp_Tech"            
  "pFGR"
  "layout"         
  symbolToString(gensym("C"))
    0:0          
  "R0"
1                      ;; orientation
list(list("shapeData" "string" "(0.24 (8.935 6.752) (0.19 6.752) (0.19 0.313) (18.001 0.313) (18.001 6.752) (8.935 6.752))")
 list("xContSpacing" "float" 0.126)
list("numrows" "int" 2) list("xDiffEnclCont" "float" 0.017)
 list("xMetEnclCont" "float" 0.12)

 list("encLayerEnclosure_2" "float" 0.12)
 list("encLayerUse_1"  "boolean" nil)
 list("encLayerUse_2"  "boolean" t)

 list("formalVersion" "int" 1)
 list("decompositionMode" "string" "fill45-path-poly")
list("shapeType" "string" "path")
)
  )

Thank you,

Chandaka

  • Andrew Beckett

    Chandaka,

    This is because the pcell doesn't directly use that parameter - instead it uses one called  enclosingLayers which is derived via a CDF callback.

    So after setting encLayerEnclosure_2 you need to call:

    cdfgData=cdfGetInstCDF(addGroup)
    evalstring(cdfgData->encLayerEnclosure_2->callback)

    Or you could use abInvokeInstCdfCallbacks or CCSinvokeInstCdfCallbacks (which are included with abInvokeCdfCallbacks.il and CCSinvokeCdfCallbacks.il - which can be found either by doing some google searching or the CCS version is on http://support.cadence.com . This will call all the callbacks or just those you want in a specified order.

    Regards,

    Andrew.

  • Venu Ch
    Thanks alot Andrew. Its working Now.

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.