• 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. Error During AMS simulation

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 127
  • Views 20099
  • 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

Error During AMS simulation

Arslan
Arslan over 12 years ago

Hi, When I run ams simulator Following error occurs:

E,SPCERR (No source,0|0): The program encountered one or more errors while processing the input SPICE file(s) in the AMSD flow. For details, see the following messages.
------
Irun found errors(s) during the processing of SPICE files in AMSD flow.
These could be fatal simulation front-end (SFE) parsing messages or
errors found during AMS SPICE processing. Correct these errors and
re-run simulation since they will effect the AMS simulation results.

What should I do?

  • Cancel
  • Quek
    Quek over 12 years ago

    Hi Arslan

    This might be the same problem explained in COS article 11808980. You should be able to resolve it by shortening the model path or by upgrading INCISIVE package to any version higher than 11.1.s057.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • swirhun
    swirhun over 11 years ago

    I am encountering this same error and there is no descriptive error message available. I tried copying the model files to a shorter path location, but that didn't work. The tool reports that it is using: irun: 13.20-s006, and the only error message is:

    irun: *E,SPCERR: The program encountered one or more errors while processing the input SPICE file(s) in the AMSD flow. For details, see the following messages.

    amsspice: *Error: terminated with error code 2

    Any ideas?

    Thanks,

    Paul 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 11 years ago

    Hi Paul

    As there are no specific error messages, I think maybe we can start from basic system checking. Would you please post the output of the following cmd?

    terminal>$INCISIVHOME/tools/bin/checkSysConf INCISIV13.2

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • swirhun
    swirhun over 11 years ago

    Quek, 

    Thanks for the quick reply. Maybe not surprisingly, the command you said to try gives a "Fail" output...

    [This post has been updated. If the tool fails to run and display PASS/FAIL reports, then it is running from the wrong location. Use the full path as Quek explains in his response]. 

    Thanks for the help,

    Paul 
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 11 years ago

    Hi Paul

    Would you please substitute "abc" with your actual path?

    terminal>/abc/tools/bin/checkSysConf INCISIV13.2

    You can get the path to ncsim using:

    terminal>which ncsim

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • swirhun
    swirhun over 11 years ago
    I also ran this on a different machine of ours and got a more useful output. I have masked our server names. ============== checkSysConf: Version 3.19 ==================== Date information gathered: Wed Sep 17 22:06:39 PDT 2014 ------------------------------------------------------- Host Name ..............: ... Hostid .................: Operating System .......: Linux / x86_64 OS Version .............: 5.0WS Kernel Version .........: 2.6.18-274.el5 Hardware Type ..........: x86_64 Memory .................: 128956 Megabyte No. of CPUs ............: 32 Total Swap Space........: 130943 Megabyte X Server ...............: X Window System Version 7.1.1 (--) MGA(0): Pseudo-DMA transfer window at 0xDA800000 Patch Data file ........: /apps/cad/cadence/INCISIV132.006/share/patchData/Linux/x86_64/redhat/5.0WS/INCISIV13.2 **************** Now verifying configuration **************** Validating Kernel requirements... Minimum Installed Status Info ------- --------- ------ -------------------- 2.6.18-194.el52.6.18-274.el5 PASS Validating MEMORY requirements MegaByte ... Minimum Installed Status Info ------- --------- ------ -------------------- 1024MB 128956MB PASS Validating SWAP requirements in MegaByte ... Minimum Installed Status Info ------- --------- ------ -------------------- 2048MB 130943MB PASS Validating DISPLAY requirements... Minimum Installed Status Info --------- -------------------- ------ ---- --- --- --- None specified Validating PACKAGE requirements.....12 to check # PACKAGE Release Build Installed Status Info -- ------- ------- ----- --------- ------ -------------------- 1 glibc 2.5 49.el5_5.5 2.5-81.el5_8.4 PASS -> 'GlibC' 2 elfutils-libelf 0.137 3.el5 0.137-3.el5 PASS -> 'Libelf Library' 3 ksh 20100202 1 - FAIL Package not installed. -> ---------------------- -> 'ksh' 4 mesa-libGL 6.5.1 7.8.el5 6.5.1-7.8.el5 PASS -> 'Mesa libGL Library' 5 mesa-libGLU 6.5.1 7.8.el5 6.5.1-7.10.el5 PASS -> 'Mesa libGLU Library' 6 compat-readline434.3 3 4.3-3 PASS -> 'Readline Compat lib' 7 openmotif22 2.2.3 18 2.2.3-20 PASS -> 'RHEL 4 openmotif' 8 libXp 1.0.0 8.1.el5 1.0.0-8.1.el5 PASS -> 'libXp' 9 readline 5.1 3.el5 5.1-3.el5 PASS -> 'Readline Library' 10 ncurses 5.5 24.20060715 5.5-24.20060715 PASS -> 'ncurses library' 11 gdbm 1.8.0 26.2.1 1.8.0-26.2.1 PASS -> 'libgdbm.so.2' 12 glibc-devel 2.5 49.el5_5.5 2.5-81.el5_8.4 PASS -> 'GlibC-devel' Validating FILE existence .....0 to check Validating NOTFILE existence .....0 to check Configuration checks failed on this workstation (...), status is: FAIL This system does not have the correct packages to run INCISIV13.2 Run checkSysConf INCISIV13.2 -P to find out which products require this package. Exiting checkSysConf ... Good-bye
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • swirhun
    swirhun over 11 years ago

    It looks like the configuration checker reports that we are using an outdated ksh library. I will ask our sysadmins to update it and report back tomorrow.

     

    Thanks Quek!

    -Paul 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • swirhun
    swirhun over 11 years ago

    UPDATE: I'm writing my solution here so future frustrated people can try to find a solution more quickly.

    Although there are errors in the configuration-checker report, I was able to get AMS simulation working by checking the box "Run with 64 bit binary" in ADEL -> Setup -> Environment. Nothing new was installed.

    A rudimentary testbench now appears to be working! Gate models and their containing folder are specified in ADEL -> Simulation -> Options -> AMS Simualtor -> "Library files" and "Library directories".

    Make sure the config stop list includes "verilog", I have mine set as "spectre verilog" and the view list is "spectre spice verilog verilogams behavioral functional systemverilog schematic veriloga vhdl vhdlams wreal", which I believe is the default if you load the AMS template.

    -Paul 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 11 years ago

    Hi Paul

    Thank you very much for the update. We really appreciate it very much.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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