Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 14081
  • 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

ASSURA LVS RUN failure: asks OA22.41.010 API

Usama Awais

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 

Parents

  • 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.

     

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.

     

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.