Hi
I'd like to ask whether the following BVALID violates the specification when consecutive single writes.
Regarding the two cases of BVALID shown below :
In Case1, BVALID for different BIDs is asserted high consecutively
In Case2, BVALID is asserted one clock later for next BID.
I would like to confirm whether Case1 violates the specification.
From a basic point of view, BVALID just means the slave has fimished handling a write and now has a response ready for the master. it doesn’t really do anything by itself until the master also raises BREADY, and once both are high, the write response is accepted and things move on... I found that thinking of it as a simple “response available” flag makes it easier to follow, rather than getting lost in the full AXI timing diagrams...
BVALID
BREADY