In AXI protocol we have write response at the end of write transactions.
Whereas in read transaction we are providing response in each beat of transfer why is so?
Can we provide the read response at the end of the transaction same as write response?
It depends on the settings. You can provide a read response at the end of the transaction if you set this feature in the settings. I made the following settings for the page. Everything worked.
There is no setting to determine when a read response is returned in the AXI protocol. The protocol requires that a response is returned for EVERY transfer.
Are you referring to a specific AXI slave design in this reply TimothyPolini ?
- If yes, the AXI protocol would still require a response to be returned for every transfer in the transaction, but your slave implementation might then be giving a default OKAY response for all but the final transfer response, when a response for the overall transaction is generated by the slave, which is what I suggested in my first reply to this question.
- But to support this the AXI master requesting this transaction must also need to understand what this response means, so it isn't a standard solution applicable to all designs.