VCS: $stop -> simulator exit instead of going to CLI

[Tom]

All,

I have inherited a testbench with a lot of $stop commands. When they
trigger, VCS (2006.06) goes to the CLI instead of exiting the
simulator. I haven't been able to find a cmd line parameter to get
this behavior. One option is replace everything with $finish, but
$stop will print out nicely where in the code it triggered, while
$finish will not...
$finish(2); did not work for that either.

Suggestions?

Thanks,
Tom

 

[Ajeetha (www.noveldv.com)]

Tom,

On Mar 27, 6:20 am, "Tom" <hom...@gmail.com> wrote:

All,

I have inherited a testbench with a lot of $stop commands. When they
trigger, VCS (2006.06) goes to the CLI instead of exiting the
simulator. I haven't been able to find a cmd line parameter to get
this behavior. One option is replace everything with $finish, but
$stop will print out nicely where in the code it triggered, while
$finish will not...
$finish(2); did not work for that either.

Not sure of that, it does print the line, file info from finish as
well for me IIRC.

If you use the UCLI (instead of old CLI), then do: (BTW, this is
highly recommended, CLI is old)

simv -ucli -do finish.do

// finish.do having:
onbreak {"exit"}

HTH
Ajeetha, CVC
www.noveldv.com

Suggestions?

Thanks,
Tom

 

[Tom]

Hi Ajeetha,

Not sure of that, it does print the line, file info from finish as
well for me IIRC.

If you use the UCLI (instead of old CLI), then do: (BTW, this is
highly recommended, CLI is old)

simv -ucli -do finish.do

// finish.do having:
onbreak {"exit"}

Thanks for the suggestion: it definitely works, but requires the simv
executable to be compiled with the -debug option. Our build system
doesn't allow this for farm based regression simulations.
I assume that this is also the reason why $finish(2) doesn't give the
expect result. Somehow $stop is always able to print out the location,
even when not compiling with -debug.
It looks like I'll have to use the s/$stop/$finish/ option...

Tom