I have an Verification environment with and OCP MASTER eVC connected to a OCP complaint Slave (RTL).
We are trying out simulate multiple read/write transactions using the OCP eVC api methods write() and read_resp() .
There are idle transactions between read/write. But if the idle delay is less than 10 cycles, we are getting an dut_error.
The error basically occurs in the read transaction that is issued after three back to back write transactions. When the read_resp() api is called, the READ sequence is executed but no transaction is appearing on the interface (as viewed on the waveform) as the previous writes are not yet completed but the BFM moves ahead with the read transaction.
I wanted to know if there are any restriction on the number of idle cycles between read/write transactions if we use the api methods or is it possible the issue the back to back read/write transactions without any idle cycles in between using the OCP eVC?