• 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. Invoke Callbacks in Pcell and PVS

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 15088
  • 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

Invoke Callbacks in Pcell and PVS

TobiasMrks
TobiasMrks over 8 years ago

Hello,

I am building a PCell which includes a transistor of a PDK and to invoke the callbacks I am using the CCSinvokedCallbacks function recommended in "How to call CDF callbacks procedurally from SKILL?".

I am loading the CCSinvokedCallbacks file:

load("CCSinvokeCdfCallbacks.il")

    I call the CCSinvokedCallbacks in my PCell code and when I include my PCell in the layout, it works!


    But when I am now using PVS to check for drc errors I get the following errors:

    *WARNING* (DB-270001): Pcell evaluation for TESTS/test/layout has the following error(s):

    *WARNING* (DB-270002): ("eval" 0 t nil ("*Error* eval: undefined function" CCSinvokeCdfCallbacks))

    *WARNING* (DB-270003): Error kept in "errorDesc" property of the label "pcellEvalFailed" on layer/purpose "marker/error" in the submaster.

    ERROR (XSTRM-231): Pcell evaluation failed for 'TESTS/test/layout' because the pcell SKILL code contains either a syntax error or an unsupported XStream function. Check the standard output or the Virtuoso log file for more information. Either correct the pcell SKILL code or ignore the error by enabling the 'ignorePcellEvalFail' option for XStream Out.

    INFO (XSTRM-273): Translation failed. '1' error(s) and '6' warning(s) found.

    What is the recommanded way to get around this?
    Thank you in advance.

    Best regards

    Tobias

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

      Tobias,

      Happy to see you using my code to good effect!

      Anyway, what you should do is to add a file called "libInit.il" inside the library containing the pcell. This file should then load the CCSinvokeCdfCallbacks.il file. 

      The idea is that the first time the library is accessed in Virtuoso, in the stream interface or any other application that reads the database, it will load the libInit.il which will in turn load the callback-calling code. This means you wouldn't need to load the code from your .cdsinit as it would be auto-loaded from the libInit.il file.

      Hope that helps,

      Regards,

      Andrew.

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

      Tobias,

      Happy to see you using my code to good effect!

      Anyway, what you should do is to add a file called "libInit.il" inside the library containing the pcell. This file should then load the CCSinvokeCdfCallbacks.il file. 

      The idea is that the first time the library is accessed in Virtuoso, in the stream interface or any other application that reads the database, it will load the libInit.il which will in turn load the callback-calling code. This means you wouldn't need to load the code from your .cdsinit as it would be auto-loaded from the libInit.il file.

      Hope that helps,

      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