• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 90 subscribers
  • Views 6122 views
  • Users 0 members are here
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

AXI

Muthuvenkatesh

Why burst must not cross 4kb  in AXI ?

Parents
  • 0
    Hello Muthuvenkatesh,

    The 4KB boundary size is essentially a trade-off between supporting a large enough minimum slave size (which could be covered entirely with a single burst and also simplifies address decoders) and wasting too much space for slaves that do not require large address ranges.

    Also, although the AXI protocol is independent from the ARM processor architecture, the 4KB boundary size conveniently matches the smallest granule size supported in the ARM VMSA (v7LPAEs, v8 onwards). This guarantees that bursts will never cross the boundary that is described by the smallest virtual to physical address translation page table.

    Hope this helps.

    Kind regards,
    Simone
Reply
  • 0
    Hello Muthuvenkatesh,

    The 4KB boundary size is essentially a trade-off between supporting a large enough minimum slave size (which could be covered entirely with a single burst and also simplifies address decoders) and wasting too much space for slaves that do not require large address ranges.

    Also, although the AXI protocol is independent from the ARM processor architecture, the 4KB boundary size conveniently matches the smallest granule size supported in the ARM VMSA (v7LPAEs, v8 onwards). This guarantees that bursts will never cross the boundary that is described by the smallest virtual to physical address translation page table.

    Hope this helps.

    Kind regards,
    Simone
Children
No data