Can anyone describe a practical application of try_next_item ? What scenario would cause the uvm_sequencer to not have any sequence items to be sent ? As far as I know, a sequence can not have delays in sending a sequence item.
In reply to nikhilac@nvidia.com:
A sequence can have delays within it but it is not generally recommended. But it is possible to have a sequence block waiting on other sequences in a hierarchical or layered sequence scenario. In that case it could be many cycles in-between sequence_items sent to the driver. Sometimes that other sequence is just a timer counting off clock cycles to spread traffic out.
Hi Vivek, The main difference between get() and get_next_item() is the way the request handled. In get_next_item() the request are
space bar clicker pushed to …There is not very much difference between get() and get_next_item(). The only difference is that get() will automatically call item_done() for you after it gets the next item. With get_next_item(), you must call item_done() yourself. Your sequences will be blocked until item_done() is called.