In reply to cgales:
In reply to vivekbalanandan:
You should not be using the config_db to pass information between sequences. The config_db should only be used to pass configuration items between components during the build phase only. Trying to use the config_db to pass data can significantly impact your simulation performance.
There is nothing that prevents you from using virtual sequences with only one agent. The purpose of a virtual sequence is to coordinate the behavior between multiple sequences, even if they are being used on one sequencer.
Also, don’t use the `uvm_do* macros. They are very limiting and severely restrict your ability to control your sequences/sequence_items. You should create/start your items directly.
Okay cgales. I had a reference to the thread Can we set a config db in sequence body() method and get it in scoreboard? - UVM - Verification Academy and a similar one.
Also could you please elaborate with one example where we can use virtual_sequence and a single sequencer-driver pair? I have seen some examples in stack overflow where they tried starting 2 sequencers inside virtual sequence and after randomization of first sequence trying to access those variable in seq2 as seq1.field_name. How we can access seq1 variable by dot operator from seq2. It won’t work. Do you think any other way we can access seq1 variable from seq2 after it is completed if at all virtual sequence with a single sequencer-driver pair work? Also please try to share how we can wait exactly until first sequence completed for the next sequence to start.