• 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. PCell Instance inside PCell Callback Issues

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
snee over 8 years ago

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.

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

    You may be able to workaround this with this:

    unless(isCallable('aelSuffixNotation)
      procedure(aelSuffixNotation(num @optional _precision)
        let((numStr)
          numStr=case(type(num)
            ((string symbol) num)
            ((fixnum flonum) sprintf(nil "%N" num))
            (t warn("argument must be a fixnum, flonum, or strnum") nil)
          )
          when(numStr
            cdfFormatFloatString(numStr "auto")
          )
        )
      )
    )

    If this is defined in your libInit.il for your library, it would hopefully solve the problem. It provides an alternative (not identical) implementation of aelSuffixNotation (it ignores the precision) - but may be good enough for the callbacks to function correctly.

    Regards,

    Andrew.

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

    You may be able to workaround this with this:

    unless(isCallable('aelSuffixNotation)
      procedure(aelSuffixNotation(num @optional _precision)
        let((numStr)
          numStr=case(type(num)
            ((string symbol) num)
            ((fixnum flonum) sprintf(nil "%N" num))
            (t warn("argument must be a fixnum, flonum, or strnum") nil)
          )
          when(numStr
            cdfFormatFloatString(numStr "auto")
          )
        )
      )
    )

    If this is defined in your libInit.il for your library, it would hopefully solve the problem. It provides an alternative (not identical) implementation of aelSuffixNotation (it ignores the precision) - but may be good enough for the callbacks to function correctly.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information