In reply to MERUGU PRASHANTH:
In reply to chr_sue:
In theory, you can extend the type of the seq_item_export port (you need to create a class which inherits uvm_port_base #(uvm_sqr_if_base #(REQ, RSP))) to allow multiple connections to it, this can be done by overriding the new method. You must create a custom sequencer class which inherits the uvm_sequencer_param_base #(REQ, RSP) class. This custom sequencer class will instantiate a seq_item_export port whose type will be the newly port type. Your sequencers must inherit the custom sequencer class and after that you can connect two sequencers to a single driver.
just explain me this.if u dont mine
I do not understand what you mean with ‘a class which inherits uvm_port_base #(uvm_sqr_if_base #(REQ, RSP))) to allow multiple connections’. Because this descibes only a bidirectional interface, request - response.
The only thing you can do is to extend your uvm_sequencer and adding a second uvm_seq_item_pull_export #(REQ,RSP) and extending the uvm_driver adding a second uvm_seq_item_pull_port #(REQ, RSP). But then you have to arbitrate in your driver both TLM ports ia special way. It is a solution generating more problems than solving them.