Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 15877
  • 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

PCell Instance inside PCell Callback Issues

snee

Hello all,

I have created a PCell of an inverter, by placing instances of N-MOS and P-MOS devices. Each of these primitives have pPar values for their width and length, and allows my Inverter PCell to have custom CDF properties to change the lower level instances, for example pPar("NW") for N width,pPar(" PW") for P width etc.

Once the primitives are instantiated, I refresh the callback functions of those primitives to update reliant CDF properties to the new values. Everything works great and my PCell functions properly.

However, when I run DRC/LVS, it errors with
"ERROR (XSTRM-231): Pcell evaluation has failed. This is because of either a syntax error or the usage of an unsupported XStream function in Pcell SKILL code."

I have found that while DRC generates the PCell, it is attempting to run the callback functions of the primitives and failing.
 Specifically, DRC complains that aelSuffixNotation() is an unknown function.

The only way to get DRC to run properly, is by disabling call-back refresh of the primitives in my inverter PCell.

Any tips on how to handle this?

Thanks.

Parents
  • snee

    Thank you,

    It would solve the problem for aelSuffixNotation, but some of the callbacks are also using aelNumber, aelEnvCreate, aelEnvSetGlobalList and aelEnvInterpret.

    Thinking outside the box here, assume I am building an Inverter PCell from an N and P primitive. Once a Inverter CDF property has been changed, and the primitive values updated, can the PCell (pcDefinepcell) return the two dbObject instances to the Inverter callback such that this callback can run the callbacks of the primitives?

    Example:

    Inverter CDF property N-Length changed

     -> PCell changes nInstance "Length" value

     -> PCell returns nInstance and pInstance dbObjects

     -> N-Length calls its callback receives nInstance and pInstance dbObject

        -> Callback calls all nInstance and pInstance callbacks.

    This way, I avoid these functions being hierarchically ran during stream out.

Reply
  • snee

    Thank you,

    It would solve the problem for aelSuffixNotation, but some of the callbacks are also using aelNumber, aelEnvCreate, aelEnvSetGlobalList and aelEnvInterpret.

    Thinking outside the box here, assume I am building an Inverter PCell from an N and P primitive. Once a Inverter CDF property has been changed, and the primitive values updated, can the PCell (pcDefinepcell) return the two dbObject instances to the Inverter callback such that this callback can run the callbacks of the primitives?

    Example:

    Inverter CDF property N-Length changed

     -> PCell changes nInstance "Length" value

     -> PCell returns nInstance and pInstance dbObjects

     -> N-Length calls its callback receives nInstance and pInstance dbObject

        -> Callback calls all nInstance and pInstance callbacks.

    This way, I avoid these functions being hierarchically ran during stream out.

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.