In reply to Karan:
Hi Karen, All of the above are correct, but I organize them in a way I found useful:
Your “test” class sets the uvm_config_db as “kerulmodi” correctly described. But take
note, here you setting a “Virtual Sequence” on a “Virtual SequencER”. Also, any parms that are
needed for the sequence are set here in your test class.
Then I like to code a Virtual sequence, which instantiates the sequence in question, and declares the virtual sequencer using the macro you mentioned : `uvm_declare_p_sequencer. You would need to have coded a virtual sequencer prior to this of course.
Then, finally, in this virtual sequence, you can use the various "do(..)" macros to call (start) the sequence on the sequencer in question. The sequencER in the do(…) macro is called as a component of the p_sequencer, as you would have needed to defined previously.
What’s nice about this approach is that the virtual sequence is completely extendable to calling other sequences and running them on any sequencer that’s part of your virtual sequencer.
Hope this helps!