Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 14679
  • 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

About gpdk045 ver4.0 and Assura

analogy

So we recently updated to gpdk045 version 4.0 .With the same update since we would need QRC, we would have to update from ASSURA41 to ASSURA616. The question is, where exactly do we have to make changes to integrate ASSURA616 with Cadence Virtuoso IC616 ?

  • Also, does anybody make anything out of this log file (this is with Assura41 as we haven't fully integrated  Assura616 with existing Cadence IC616)?


                Assura (tm) Physical Verification Version av4.1:Production:dfII6.1.3:IC6.1.3.500.10
                Release 4.1

    Copyright (c) Cadence Design Systems. All rights reserved.
    @(#)$CDS: assura version av4.1:Production:dfII6.1.3:IC6.1.3.500.10 06/09/2009 14:40 (sfrh259) $
    sub-version 4.1, integ signature 2009-06-09-1330

    run on eecad12.engr.xxxx.edu from /apps/cadence/ASSURA616/tools.lnx86/assura/bin/32bit/assura on Thu Mar 26 01:46:18 2015


    Loading tech rule set file : /home/sh/shah6834/RFIC/gpdk045-B/assura/techRuleSets
    Checking out 1 license for Assura_RCX 3.10
    ERROR (LMF-02015): License call failed for feature Assura_RCX, version 3.100 and quantity 1. The license server search path is defined as 5280@innersanctum.engr.xxxx.edu:/apps/cadence/license-current:27000@innersanctum.engr.xxxx.edu:/apps/synopsys/license/current-license-key:27001@innersanctum.engr.xxxx.edu. The FLEXnet error message is as follows,
        FLEXnet ERROR(-15, 0, 0): Cannot connect to license server system.

    Run 'lic_error LMF-02015' for more information.
    ERROR (LMF-02015): License call failed for feature Assura_RCX, version 3.100 and quantity 1. The license server search path is defined as 5280@innersanctum.engr.xxxx.edu:/apps/cadence/license-current:27000@innersanctum.engr.xxxx.edu:/apps/synopsys/license/current-license-key:27001@innersanctum.engr.xxxx.edu. The FLEXnet error message is as follows,
        FLEXnet ERROR(-15, 0, 0): Cannot connect to license server system.

    Run 'lic_error LMF-02015' for more information.
    ERROR (LMF-02015): License call failed for feature Virtuoso_QRC_Extraction_L, version 3.100 and quantity 1. The license server search path is defined as 5280@innersanctum.engr.xxxx.edu:/apps/cadence/license-current:27000@innersanctum.engr.xxxx.edu:/apps/synopsys/license/current-license-key:27001@innersanctum.engr.xxxx.edu. The FLEXnet error message is as follows,
        FLEXnet ERROR(-15, 0, 0): Cannot connect to license server system.

    Run 'lic_error LMF-02015' for more information.
    ERROR (LMF-02015): License call failed for feature Encounter_QRC_Extraction_L, version 3.100 and quantity 1. The license server search path is defined as 5280@innersanctum.engr.xxxx.edu:/apps/cadence/license-current:27000@innersanctum.engr.xxxx.edu:/apps/synopsys/license/current-license-key:27001@innersanctum.engr.xxxx.edu. The FLEXnet error message is as follows,
        FLEXnet ERROR(-15, 0, 0): Cannot connect to license server system.

    Run 'lic_error LMF-02015' for more information.

    Starting /apps/cadence/ASSURA616/tools/assura/bin/avRCXxref /home/sh/shah6834/45/rcx.1-Tx.rsf
    @(#)$CDS: avRCXxref version av4.1:Production:dfII6.1.3:IC6.1.3.500.10 06/09/2009 14:41 (sfrh259) $
    sub-version 4.1, integ signature 2009-06-09-1330
    run on eecad12.engr.xxxx.edu at Thu Mar 26 01:46:51 2015
    Reading rsf

    Finished /apps/cadence/ASSURA616/tools/assura/bin/avRCXxref
    Constructing the RCX run script
    Could not open file /home/sh/shah6834/RFIC/gpdk045-B/assura/../qrc/RCXspiceINIT for reading
    *WARNING* Bad return status from RCX script generator. Status 256

  • I'm assuming you've got beyond this now since it was a while ago, but it simply looks as if there was a problem with the license setup.

  • And for the first question (I'm reading these in reverse, sorry), it's just a matter of ensuring that the ASSURA41-616 version is in your UNIX path first, and $ASSURAHOME points to the root of the ASSURA41-616 installation. Nothing special other than that (that's the same process for any release of ASSURA).

    Regards,

    Andrew.

  • Yes.We had to reboot our daemon license machine. We ended up using Assura41 since one of our senior Professor thought - " If it ain't broke , don't fix it"

  • I assume you mean that you didn't update to ASSURA41-616 (and stuck with ASSURA41-615)? There is only ASSURA41 currently - but there are different versions built to match the corresponding IC version. Generally it's recommended to make sure they match, but you can often get away with it if they don't...

    Regards,

    Andrew.

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.