I'm a graduate student living in south Korea. I'm studying about AMBA 3.0 AXI.
recently, i read "AMBA® AXI Protocol.pdf". but i have two questions about AXI after reading.
i wonder about interleaving and out-of order.
AXI supports out-of order and interleaving. read transaction and write transaction enable out-of order.
does interleaving be enable only write transaction?
also, the masters have slave interface including write interleaving depth. if a salve interface attaching a master(M0) has write interleaving depth of two, can the master(M0) process write data interleaving about write data having different ID filed?
Thank you very much.
yasuhikokoumoto wrote: Hello Cao Phi, In the example, if slave have write interleaving depth are 2 then slave will accept only first two AW1 and AW2. After that slave will deassert AWREADY. Therefore, W3 will not issue. I think it would not be correct. Because AWREADY and WREADY are independent, W(3) could come before AW(3) although AWREADY was de-asserted. How does a slave act in this case? If the slave de-asserts WREADY for W3, no more W(1) or W(2) can be gotten. What mean "the data comes before the corresponding address"?? Can you give me a example?? It is the meaning just as written. I am afraid about the following case. Best regards, Yasuhiko Koumoto.
yasuhikokoumoto wrote:
Hello Cao Phi,
In the example, if slave have write interleaving depth are 2 then slave will accept only first two AW1 and AW2. After that slave will deassert AWREADY. Therefore, W3 will not issue.
I think it would not be correct.
Because AWREADY and WREADY are independent, W(3) could come before AW(3) although AWREADY was de-asserted.
How does a slave act in this case?
If the slave de-asserts WREADY for W3, no more W(1) or W(2) can be gotten.
What mean "the data comes before the corresponding address"?? Can you give me a example??
What mean "the data comes before the corresponding address"??
Can you give me a example??
It is the meaning just as written.
I am afraid about the following case.
Best regards,
Yasuhiko Koumoto.