Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 14587
  • 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

ELC : Simulation status : FAIL during db_spice

Hemal93

When I execute step 2 in ELC means spice simulation then find simulation status fail for all #ID as shown below.


Command : db_spice -s spectre -p typical -keep_log -keep_wave

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
               Simulation Summary                
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
-------------+-------------+----------+--------------+-----------
-------------+-------------+----------+------------+-----------+------------
   DESIGN    |   PROCESS   |   #ID    |   STAGE    |  STATUS   |    IPDB
-------------+-------------+----------+------------+-----------+------------
CELEM1R        typical       D0000     VERIFICATE   FAIL        newcell     
CELEM1R        typical       D0001     VERIFICATE   FAIL        newcell     
CELEM1R        typical       D0002     VERIFICATE   FAIL        newcell     
CELEM1R        typical       D0003     VERIFICATE   FAIL        newcell     
CELEM1R        typical       D0004     VERIFICATE   FAIL        newcell     
CELEM1R        typical       D0005     VERIFICATE   FAIL        newcell     
CELEM1R        typical       D0006     VERIFICATE   FAIL        newcell     
CELEM1R        typical       D0007     VERIFICATE   FAIL        newcell     

[INFO(db_spice)] Check the encounterlc.log/<ipdb_name>.log/<DESIGN>.log/<DESIGN>_<PROCESS>_<ID>.log file to determine the cause of the failure. The SPICE simulation log file can be found in the /home/raminder/hemal_asic/lib_13_5_16_cp/encounterlc.work/<ipdb_name>/<DESIGN>.work/<DESIGN>_<PROCESS>_<ID>/ directory.

//////////////////////////////////////////////////////////////////

I have checked both the directories. 
----->There is no any warning or error in encounterlc.log/.....

----->But in encounterlc.work/......./typical_D0005_tr.lis has some warnnings like,


WARNING (SFE-30):
        "/home/raminder/hemal_asic/lib_13_5_16_cp/newcell.ipdb/CELEM1R.design/simulate/subckt"
        3: X_CELEM1R_D0005.+3: `mis_flag' is not a valid parameter for an
        instance of `n_12_llrvt'.  Ignored.

 WARNING (SPECTRE-8511): Error in opening shared
        object:/home/Cadence_tools/SPB/tools.lnx86/mdl/lib/libeh_sh.so:
        undefined symbol:
        _ZNK8srrValue20compareWithSortOrderEPKS_PK23srrStringGroupAttribute.

Warning from spectre.
    WARNING (SPECTRE-134): No analysis specified.

Can you help to solve this problem?
Thanks in advance.....

Parents
  • Andrew Beckett

    OK, that doesn't make sense - I can't see how it can pick up a shared library from the SPB installation without knowing something about where to find it. 

    So, can you do the following (in the terminal where you've unset things) and post the results:

    echo $LD_LIBRARY_PATH
    echo $PATH
    which spectre

    (it's possible you have spectre as a wrapper script which is setting LD_LIBRARY_PATH).

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    OK, that doesn't make sense - I can't see how it can pick up a shared library from the SPB installation without knowing something about where to find it. 

    So, can you do the following (in the terminal where you've unset things) and post the results:

    echo $LD_LIBRARY_PATH
    echo $PATH
    which spectre

    (it's possible you have spectre as a wrapper script which is setting LD_LIBRARY_PATH).

    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.