• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Relxpert prebert error

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 126
  • Views 15829
  • 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

Relxpert prebert error

Amel
Amel over 13 years ago

Hi, 

I am tryning to run Relxpert for the first time in an interactive mode that is invoking Relxpert from ADE, when I go to prebert stage it fails and I get the following error: RelLink: prebert did not complete successfully. can anyone tell me how to overcome this problem.

thanks

  • Cancel
Parents
  • Amel
    Amel over 13 years ago

    Hi Ashish,

    Thank you for your relpy,  you are right.

    I have added the "simulator lang = spice" statement before the control statements that are written using SPICE language and "simulator lang = spectre" before statements written with spectre languageguided by the general rules given in  Virtuoso RelXpert Reliability Simulator User Guide. but this does not resove the prolem.

    the following is what I have gotten as prebert logfile:

     prebert:

    =========

    *****************************************************************************

    *

    *  Cadence (R) Virtuoso (R) RelXpert Reliability Simulator

    *  RelXpert version sub-version  7.1.1.187  32bit 08/18/2009 21:18 (usim440-8) 

    *  Copyright(C) 2001-2007, Cadence Design Systems, Inc. All rights reserved worldwide.

    *  Cadence and Virtuoso are registered trademarks of Cadence Design Systems, Inc.

    *  All others are the property of their respective holders.

    *  Protected by U.S. Patents:

    *  5,610,847; 5,790,436; 5,812,431; 5,859,785; 5,949,992; 5,987,238; 6,088,523;

    *  6,101,323; 6,151,698; 6,181,754; 6,260,176; 6,278,964; 6,349,272; 6,374,390;

    *  6,493,849; 6,504,885; 6,618,837; 6,636,839; 6,778,025; 6,832,358; 6,851,097;

    *  7,035,782; 7,085,700

    *

    *  USER: chenouf HOST: turquoise HOSTID: 84A1A852 PID: 13253

    *  Memory: available: 588.8409 MB physical: 2.1474 GB

    *  CPU(1 of 2): CPU0 sparcv9 1600Mhz

    *

    *  Netlist file: m6File

    *  Starting time: Wed Mar 14 15:34:31 2012

    *

    *  Command Line Input: prebert -sp -p1 m6File m6File.p1 

    *

    *****************************************************************************

     

    Error(RELXP-198): The RelXpert simulator failed to parse .rawfile1.sp because of the following error:

            The Rexlpert simulator failed to parse the netlist.

            Correct the above errors and run the simulation again.

    . Run the SPICE simulator spectre to make sure the netlist file passes before correcting the statement in file  and running the simulation again.

     
     
    I  tried to run the netlising It passes successfully but when I run prebert again I get the same error. I am confused since this time in the logfile  I can not see why the simulator  fails to parse rawfile.sp.
    regards 
    Amel. 
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Amel
    Amel over 13 years ago

    Hi Ashish,

    Thank you for your relpy,  you are right.

    I have added the "simulator lang = spice" statement before the control statements that are written using SPICE language and "simulator lang = spectre" before statements written with spectre languageguided by the general rules given in  Virtuoso RelXpert Reliability Simulator User Guide. but this does not resove the prolem.

    the following is what I have gotten as prebert logfile:

     prebert:

    =========

    *****************************************************************************

    *

    *  Cadence (R) Virtuoso (R) RelXpert Reliability Simulator

    *  RelXpert version sub-version  7.1.1.187  32bit 08/18/2009 21:18 (usim440-8) 

    *  Copyright(C) 2001-2007, Cadence Design Systems, Inc. All rights reserved worldwide.

    *  Cadence and Virtuoso are registered trademarks of Cadence Design Systems, Inc.

    *  All others are the property of their respective holders.

    *  Protected by U.S. Patents:

    *  5,610,847; 5,790,436; 5,812,431; 5,859,785; 5,949,992; 5,987,238; 6,088,523;

    *  6,101,323; 6,151,698; 6,181,754; 6,260,176; 6,278,964; 6,349,272; 6,374,390;

    *  6,493,849; 6,504,885; 6,618,837; 6,636,839; 6,778,025; 6,832,358; 6,851,097;

    *  7,035,782; 7,085,700

    *

    *  USER: chenouf HOST: turquoise HOSTID: 84A1A852 PID: 13253

    *  Memory: available: 588.8409 MB physical: 2.1474 GB

    *  CPU(1 of 2): CPU0 sparcv9 1600Mhz

    *

    *  Netlist file: m6File

    *  Starting time: Wed Mar 14 15:34:31 2012

    *

    *  Command Line Input: prebert -sp -p1 m6File m6File.p1 

    *

    *****************************************************************************

     

    Error(RELXP-198): The RelXpert simulator failed to parse .rawfile1.sp because of the following error:

            The Rexlpert simulator failed to parse the netlist.

            Correct the above errors and run the simulation again.

    . Run the SPICE simulator spectre to make sure the netlist file passes before correcting the statement in file  and running the simulation again.

     
     
    I  tried to run the netlising It passes successfully but when I run prebert again I get the same error. I am confused since this time in the logfile  I can not see why the simulator  fails to parse rawfile.sp.
    regards 
    Amel. 
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information