Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 6413
  • 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

runams hangs

Continuum

I don't know what has changed, but runams has started hanging on me. This is killing my verification flow. This now happens every time I use runams.

I run the following command:

runams \
    -cdslib ./.tmp.cds.lib \
    -irunopts '-nocopyright -linedebug -define TESTBENCH=sh_tb' \
    -modelincdir \
    /home/continuum/src/verif/av/tests/case33oa/../design-oa \
    -modelpath 'models.scs(tt):anamodels.scs(tt)' \
    -netlisteropts amsPortConnectionByNameOrOrder=name \
    -log ./.sh.mvm33.netlister.log \
    -lib mylib \
    -cell sh_tb \
    -view mvm33 \
    -netlist all

runams runs and generates the netlist. It then prints a prompt and waits for commands.

...
Running netlist assembly..

End netlisting Aug 25 12:50:35 2023
INFO (AMS-1254): AMS UNL netlisting has completed successfully.
      ...successful.
create cds_globals...
>

At this point it hangs, waiting forever.  I can type commands and it will respond, but I cannot find a command that causes it to terminate.  I have tried quit, quit(), exit, exit() and ctrl-D.  quit and quit() result in error messages. ctrl-d is ignored.  exit and exit() causes program to hang, this time without the command prompt.  Even ctrl-C will not kill the program.  I have to use ctrl-\.  All of this means I can no longer use runams in a script.

Any ideas on what might be causing this or how I can resolve this issue?

Parents

  • Oh, I am using the following versions: IC_06.18.330, SPECTRE_23.10.063, XCELIUMMAIN_23.03.005

    I then switched to IC_23.10.010 and got the same result.

    Switching to XCELIUMMAIN_20.09.002 resolves the runams problem.  Ironically downgrading just xcelium causes the simulator to hang after the simulation.  However, using the latest version of IC while using 2020 versions of both Spectre and Xcelium does seem to work.

  • in reply to Continuum

    That's very odd. It sort-of looks as if it's something causing it to display an invisible dialog box at the end which then can't be pressed - but the fact that the interactive prompt appears is a little strange (I wonder whether it's really interactive or just showing ">").

    I need to check with the specific versions you're using - I was trying but with an older version of XCELIUM (I'd not got anything beyond XCELIUM2203 installed on my local machine), so I'll check that later.

    If you set this:

    setenv RUNAMSDEBUG YES

    then it will keep the virtuoso log file from the slave virtuoso session in the runams run dir (under a dot dir something like AMSexample-top-config/.rams_virtuoso_temp_107671/ ) maybe that will give a clue?

    Andrew.

  • in reply to Andrew Beckett

    The > is a prompt.  I can type a command and it will respond and then provide another prompt.  I will try RUNAMSDEBUG.

Reply Children
  • in reply to Continuum

    I set RUNAMSDEBUG and re-ran the netlisting and there was nothing in the log file that provided any help.  Though I noticed one thing that surprised me.  When the process has hung, it is taking 100% of a CPU.  So it is not simply waiting passively for another command.

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.