Home > Community > Forums > Custom IC Design > ASSURA LVS RUN failure: asks OA22.41.010 API

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 ASSURA LVS RUN failure: asks OA22.41.010 API 

Last post Mon, Feb 10 2014 8:43 AM by Andrew Beckett. 1 replies.
Started by Usama Awais 08 Feb 2014 11:49 AM. Topic has 1 replies and 2268 views
Page 1 of 1 (2 items)
Sort Posts:
  • Sat, Feb 8 2014 11:49 AM

    • Usama Awais
    • Not Ranked
    • Joined on Fri, Aug 16 2013
    • Lahore, Pakistan
    • Posts 1
    • Points 20
    ASSURA LVS RUN failure: asks OA22.41.010 API Reply

    Hi everyone,

    I have been struggling with ASSURA LVS, The DRC runs fine however when LVS is run, the following error appears in the error log:

    Error: failed to initialize OpenAccess because:

    Requested minor API version '202' which is supported by OpenAccess build '22.41.010' is newer than the minor API version '201' of the shared library of OpenAccess build '22.41.004'

    I tried searching for the Open Access version of 22.41.010 and had no luck. I have tried to search the cadence forum and support is under temporary unavailability.

    I remember doing one thing before running the LVS but I doubt the reason might have been that. Since Open Acess allows objects and doesnt have typical via definitions as in cdb such as "M1_PSUB" or "M1_NWELL", I went to the Constraints manager and allowed all Vias as Valid Vias in all tech file values since I needed some of those for my basic inverter layout which were not available in default standiard vias. Thereafter after completing the design got no DRC but got prompted for this error as LVS failed to run.

    I am also attaching the text file of the error log.

    Regards

    Usama Awais 

    • Post Points: 20
  • Mon, Feb 10 2014 8:43 AM

    Re: ASSURA LVS RUN failure: asks OA22.41.010 API Reply

    My guess is that you have the $OA_HOME UNIX Environment variable set, pointing to an older installation of OpenAccess. You should really have each tool use the OpenAccess version that it is shipped with.

    Looking at the versions mentioned in the log files, they both appear to use 22.41.010 - so I'm not sure what you can have this set to.

    I would recommend doing:

    unsetenv OA_HOME   (if using csh)

    or

    unset OA_HOME  (if using ksh or bash)

    before starting Assura (or Virtuoso).

    There's also a possibility that your installations were configured incorrectly - so maybe you can check the "share/oa" link in $ASSURAHOME and $CDSHOME (or wherever "cds_root virtuoso" points) to see that it's pointing to:

    UNIX_183> ls -l $ASSURAHOME/share/oa
    lrwxrwxrwx 1 ccops ccusers 16 Nov 16  2011 /apps/ASSURA41/615/04.12.011/share/oa -> ../oa_v22.41.010/
    UNIX_184> ls -l $CDSHOME/share/oa
    lrwxrwxrwx 1 ccops ccusers 16 Jul 29  2011 /apps/IC615/06.15.505/share/oa -> ../oa_v22.41.010/
    UNIX_185> assura -W
    sub-version 4.1_USR2_HF11
    UNIX_186> virtuoso -W
    sub-version  IC6.1.5.500.5 

    Regards,

    Andrew.

     

    • Post Points: 5
Page 1 of 1 (2 items)
Sort Posts:
Started by Usama Awais at 08 Feb 2014 11:49 AM. Topic has 1 replies.