Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 14033
  • 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

End-of-test in SVCB

archive

Hi,
I am Using URM-IPCM SVCB for the uVC.
For End of the Simulation, I am using the Following code,
task run();
      begin
           #10000  `message(LOW, ("User  activated end of simulation"))
           // Global method - asks to tell all run() phases to end.
           // this will end the simulation.
           global_stop_request();
      end
  endtask : run
This is Ok for me as the Generated  transactions are limited to 30-50 in count Which will take less than 10000 ns simulation time.But if i want more 100+ transactions then i have to call global_stop_request() after ,say some 30000ns.
In this way when i configure the no.of transactions i need to change the delay of global_stop_request() call..rite!!

In eRM, we had an End_of_test mechanism in which objection are raised and dropped automatically calling the End of Simulation.

I want to Know Can we do this type of End_of_test in SVCB also?

Regards,
Ramesh Pal


Originally posted in cdnusers.org by ramesh_pal_yadav

  • I have a similar issue, I think. I don't want to call global_stop_request(), and thought I didn't need to: I figured my sim would stop when there are no more events to process. In fact, it does, and the last line I see is:


    ncsim: *W,RNQUIE: Simulation is complete.
    ncsim> exit

    nchelp ncsim RNQUIE says

    nchelp: 06.20-s003: (c) Copyright 1995-2007 Cadence Design Systems, Inc.
    ncsim/RNQUIE =
    Simulation is complete when there are no future events
    scheduled. This warning indicates that a run command has
    been executed and all current events have been processed.
    Unfortunately, I don't think that my report() function gets called when the sim ends this way ...


    Originally posted in cdnusers.org by vertreko

  • I got a solution that works for me, after talking to some Cadence engineers.  Instead of putting global_stop_request() into the run task, where it has no context to understand whether your simulation is really finished, it can be put into the body task of a sequence, as follows:

      virtual task body();
        `message(MEDIUM,("Starting sequence with wr_rd_eeprom_seq"))
        `urm_do_with(wr_seq, { count ==  64; offset ==   0; })
        `urm_do_with(wr_seq, { count ==  64; offset ==  64; })
        `urm_do_with(wr_seq, { count ==  64; offset == 128; })
        `urm_do_with(wr_seq, { count ==  64; offset == 192; })
        `urm_do_with(rd_seq, { count == 128; offset ==   0; })
        `urm_do_with(cr_seq, { count == 128; })
         urm_unit::global_stop_request;
      endtask : body


    Originally posted in cdnusers.org by vertreko

  • Hi Vertreko
    Thanks a Lot , It Worked!!
     


    Originally posted in cdnusers.org by ramesh_pal_yadav

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.