Erling Posted October 17, 2011 Report Share Posted October 17, 2011 In the uvm examples and user guide, a test (derived from uvm_test) is usually just a constructor, it does not actually do any real work during the simulation. I wonder if things could be simplified by having the test component itself participate more actively in the test. A start could be to run sequences in the test run phase instead of storing a reference to the sequence in the config_db to be picked up later on as the default sequence on some sequencer. A more complicated test could, for example, start multiple sequences directly in its run phase, perhaps on multiple sequencers, orchestrate the overall test activity, handle dependencies between sequences to different interfaces, and so on. However, the user guide recommend virtual sequence®s for this purpose, again doing construction and config only in the test itself. Any thoughts on this? Is it best to follow the user guide in this regard to avoid accidents, and if so, what accidents would that be? Erling Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.