This entire process take 5 cycles and it is pipelined, so in cycle 2 if valid signal again goes high, then u need to start the 2nd transaction
In reply to pghosh:
What is your question? We are not going to do your assignment for you.
In reply to dave_59:
Hi Dave,
This is not an assignment but an interview question and I don’t need the exact monitor code but just the approach for the run phase task for monitor. I had come up with a solution that would look similar to a driver, because as per my understanding, in monitor, we just monitor the transactions, like whatever is coming from the interface, we store it in a new transaction variable and then call the write(txn) api.
but in this question, I was asked to change the signals in monitor. So, this is where i got confused.
Any insights on this?
In reply to pghosh:
In the verification world, we try to eliminate ambiguities. It would have help to explain all the information you had, what you attempted, and what particularly you need help with.
When you say you were “asked to change the signals in monitor”, does that mean they asked you to make the monitor drive a signal change into the DUT?