• State Accepted Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 94 subscribers
  • Views 22193 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AXI4 ordering

Hyunkyu

AXI4 document says that when a master issues multiple transactions to same / overlapping address with same ID, the order of arrival at the slave must be the same as the order of issue.

I think it means if transactions are not for the same address, they can be out of order even if they have same ID.

Is it correct?

If so, when transactions have the same ID how can I distinguish whether transactions are reorderable or not?

Parents
  • 0 in reply to Colin Campbell

    Now I understand what it means.

    But I think multiple transactions with SAME ID will always arrive at the target in the same order of issue.

    If not, slave may not be able to respond in order.

    So, order of arrival may be same no matter what the memory type of the target is.

    Is there any reason to distinguish the case for the Device memory and the others?

Reply
  • 0 in reply to Colin Campbell

    Now I understand what it means.

    But I think multiple transactions with SAME ID will always arrive at the target in the same order of issue.

    If not, slave may not be able to respond in order.

    So, order of arrival may be same no matter what the memory type of the target is.

    Is there any reason to distinguish the case for the Device memory and the others?

Children
No data