In reply to chr_sue:
In reply to maaroop:
If you are following the UVM Guidelines both IDs are generated automatically, i.e. you can identify any seq_item as a unique item. The method set_id_info(req) is doing this for you. This is the behavior you need to implement the correct functionality in your scoreboard
Two follow-up questions :
1)
Can we use the same seq id/transaction id method for even in-order transactions between more than one I/O ports on a router, if the port_id is not known?
2)
Is the idea to use the set_id_info in the response from the driver and write to rsp port? If so, could you show an example of how the scoreboard might use this info from the rsp port?
Thanks