In reply to dave_59:
- Looking to do it without using an assertion.
- “Valid transaction” defined when both ready and valid signals of the interface are set to ‘1’.
- There might be cases when the ready signal is high ‘1’, but valid signal is ‘0’.
- From beginning of test, ideally would be great if this checker could be breathing and active during the whole test.
- The ready signal should be de-asserted after the 64th valid transaction.
Honestly, there might be many buffers and flops in the DUT (from experience of verifying other designs), so I wonder how this checker could be tight and correct.