• 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 SKILL
  3. Whats wrong with including this file in the simulation files...

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 143
  • Views 13113
  • 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

Whats wrong with including this file in the simulation files in the tests for Assembler?

greywanderer
greywanderer over 4 years ago

File contents

"

parameters ac_vsig=1

tran tran stop=14u errpreset=conservative maxiters=5 skipdc=no write="spectre.ic" writefinal="spectre.fc" annotate=status oppoint=logfile \\
               actime_pair=no actimes=\[10.3543255u\] acnames=\[stb_main stb_sec\]

stb_main stb start=1k stop=100M dec=100 probe=ux1.ux2.ux3.vim_n localgnd=gnda

stb_sec stb start=1k stop=100M dec=100 probe=ux1.ux2.ux3.vstb localgnd=gnda

"

The error seen is,

ERROR (SFE-874):  6: 14: Unexpected equals "=". Cannot run the simulation because of syntax error. Correct the error and rerun the simulation.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    I don't see that error (I'm assuming you've used stimulus file, given all the extra backslashes).

    One thing you need to be careful of when editing the file when using stimulus file is that it may not detect the change in the file unless you edit it via the button on the simulation files form (mainly because the stimulus file is processed to allow special sequences to be mapped from schematic names to netlist names), and then copied into the netlist directory. You can check that by following the actual included file from the hyperlink in the spectre log file.

    My suggestion is simple to remove all the extra backslashes and reference it as a "definition file" instead. That's simpler.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • greywanderer
    greywanderer over 4 years ago in reply to Andrew Beckett

    Yes, I checked the hyperlink. The changes seem to be detected.

    I will try the definition file instead and see if it works. Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • greywanderer
    greywanderer over 4 years ago in reply to greywanderer

    It did not work with definition file either.

    "

    parameters ac_vsig=1

    tran tran stop=14u errpreset=conservative maxiters=5 skipdc=no write="spectre.ic" writefinal="spectre.fc" \
    method=euler annotate=status oppoint=logfile \
    infotime_pair=no infotimes=[10.3543255u] infonames=[dcInfo] \
    actime_pair=no actimes=[10.3543255u] acnames=[stb_sec]

    dcInfo info what=oppoint where=rawfile
    stb_sec stb start=1k stop=100M dec=100 probe=ux1.ux2.ux3.vstb localgnd=gnda

    "

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to greywanderer

    It works for me (I had to change the path to the probe, but that was it). No errors. 

    What exactly does the spectre log file show? I get that sort of error if I omit the backslash (continuation character) at the end of one of the lines:

        ERROR (SFE-874): "/export/home/andrewb/demos/OCEAN/forum2.scs" 6: Cannot run the simulation because syntax error `Unexpected equals "="' was encountered at line 6, column 11. Correct the syntax error and rerun the simulation.

    Which spectre version are you using? Your message appears slightly different to mine.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • greywanderer
    greywanderer over 4 years ago in reply to Andrew Beckett

    Error found by spectre during circuit read-in.
    ERROR (SFE-874): "/path_to_test_bench/namedStimuli/file.scs" 7: 14: Unexpected equals "=". Cannot run the simulation because of syntax error. Correct the error and rerun the simulation.

    The spectre version is,

    getVersion(t)
    "sub-version IC6.1.8-64b.500.9 "

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to greywanderer

    That's the IC version, not the spectre version. The spectre version will appear at the top of the spectre log file.

    It would help to know what exactly is at line 7 of the file and character 14 (and also what is on line 6).

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • greywanderer
    greywanderer over 4 years ago in reply to Andrew Beckett

    Sorry for the delay. Been a bit busy. Will get back to you on this by end of day.

    Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • greywanderer
    greywanderer over 4 years ago in reply to Andrew Beckett

    "

    parameters ac_vsig=1

    tran tran stop=14u errpreset=conservative maxiters=5 skipdc=no write="spectre.ic" writefinal="spectre.fc" \
    method=euler annotate=status oppoint=logfile \
    infotime_pair=no infotimes=[10.3543255u] infonames=[dcInfo] \

    //actime_pair = no actimes = [10.3543255u] acnames=[noise1]
    actime_pair=no actimes=[10.3543255u] acnames=[stb_sec]

    dcInfo info what=oppoint where=rawfile
    stb_sec stb start=1k stop=100M dec=100 probe=ux1.ux2.ux3.vstb localgnd=gnda

    "

    The above does not work. If you remove "//actime_pair = no actimes = [10.3543255u] acnames=[noise1]" ie the commented line, it works fine.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to greywanderer

    Not surprising - commented lines get removed and hence are like a blank line with no continuation character - so the subsequent line isn't seen as a continuation of the previous (non-commented) line (the line starting with infotime_pair).

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to greywanderer

    Not surprising - commented lines get removed and hence are like a blank line with no continuation character - so the subsequent line isn't seen as a continuation of the previous (non-commented) line (the line starting with infotime_pair).

    Andrew

    • Cancel
    • Vote Up +1 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