Traffic control between sequencer and driver

UVM
1

Hello Sir,

I have AXI traffic generator through VIP.
AXI traffic is generated back2back from the sequence without waiting for their response.

I used “grab” method in my test to stop the AXI traffic on AXI interface.
But AXI traffic is still seen for sometime on AXI interface after “grab” method is called and then AXI traffic stopped.
Looks like sequencer already has many AXI requests before grab called and hence this behavior is seen.

My requirement is such that AXI traffic should be stopped on AXI interface when user request for it.
On other end, AXI traffic should resume back on AXI interface when user request for it.

Can you please help to suggest/propose some method/mechanism to do the same?

Regards,
Ankit

2

In reply to AnkitSheth:
You can stop the seq_item generation in the driver when stopping the driver execution - avoiding to do a get or get_next_item. This is a very safe method.

3

In reply to chr_sue:

Thanks for the reply.

If the vip is from the EDA vendor, then user does not have control of get_next_item.

In that case can you please suggest?

Regards,
Ankit

4

In reply to AnkitSheth:

Such a VIP is useless. You can extend a component from the VIP to add more functionality.

5

In reply to chr_sue:

Thanks. I will check with VIP vendor if they have such control.

Appreciate your help

6

In reply to AnkitSheth:

You do not have to modify the VIP, but you can extend the driver class to implement your intended behavior. Then you can override this driver. The object-oriented behavior is allowing this.