In reply to chrisspear:
In reply to tonyyalfred:
Each agent handles a specific protocol. Reset is often asynchronous, so it does not make sense to group it with other data and control signals.
I’ve worked with testbenches where reset is part of the protocol and it never feels right. A reset transaction has don’t care for all the rest of the field.
I see, and in order to orchestrate between the reset sequencer and data sequencer, we must use virtual sequence?
And how would the timing of the reset be determined? I am aware that good testbenchs require the ability to apply reset after sequences end, and even while the sequences haven’t finished.
And also that would require our components to be reset aware as I learned, I found that this isn’t standardized in the industry, and there different methods applied, like on the fly reset, reset phase jump and so on, which one do you recommend comitting to?
I don’t have much experience but if there are any complete environments that apply this, I would be grateful for a link.
Thank you greatly.