Stats

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

spp is not working

marklin

I need to convert from spice model to spectre model.    When I type spp,  I got   

/cadence/cds/IC5141-usr6/tools/lib/libgcc_s.so.1: version `GCC_3.3' not found (required by /usr/lib/libstdc++.so.5)

When I check the libgcc_s.so.1 in either /lib  or /cadence/cds/IC5141-usr6/tools/lib, 

strings /cadence/cds/IC5141-usr6/tools/lib/libgcc_s.so.1 | grep "GCC"    comes up   GCC_3.0

strings  /lib/libgcc_s.so.1 | grep "GCC"  comes up

GCC_3.0
GCC_3.3
GCC_3.3.1
GCC_3.4
GCC_3.4.2
GCC_4.0.0
GCC_4.2.0

Why spp has to use /cadence/cds/IC5141-usr6/tools/lib/libgcc_s.so.1 instead of /lib/libgcc_s.so.1?

Thanks.

Parents

  • Hi Mark,

    No, spectre should be able to natively read the model without you having to convert it. The fact that you are using IC5141 is irrelevant because it's the simulator that's reading it (assuming you really are using spectre from MMSIM141 which should be clear from the log file). Make sure that the file has a suffix other than ".scs" (.scs implies spectre syntax, anything else implies SPICE).

    Perhaps you should contact customer support so that we can take a look at the problems via a webex session with you?

    Regards,

    Andrew.

Reply

  • Hi Mark,

    No, spectre should be able to natively read the model without you having to convert it. The fact that you are using IC5141 is irrelevant because it's the simulator that's reading it (assuming you really are using spectre from MMSIM141 which should be clear from the log file). Make sure that the file has a suffix other than ".scs" (.scs implies spectre syntax, anything else implies SPICE).

    Perhaps you should contact customer support so that we can take a look at the problems via a webex session with you?

    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.