Arm Community
Site
Search
User
Site
Search
User
Groups
Education Hub
Distinguished Ambassadors
Open Source Software and Platforms
Research Collaboration and Enablement
Forums
AI and ML forum
Architectures and Processors forum
Arm Development Platforms forum
Arm Development Studio forum
Arm Virtual Hardware forum
Automotive forum
Compilers and Libraries forum
Graphics, Gaming, and VR forum
High Performance Computing (HPC) forum
Infrastructure Solutions forum
Internet of Things (IoT) forum
Keil forum
Morello forum
Operating Systems forum
SoC Design and Simulation forum
SystemReady Forum
Blogs
AI and ML blog
Announcements
Architectures and Processors blog
Automotive blog
Graphics, Gaming, and VR blog
High Performance Computing (HPC) blog
Infrastructure Solutions blog
Internet of Things (IoT) blog
Operating Systems blog
SoC Design and Simulation blog
Tools, Software and IDEs blog
Support
Arm Support Services
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Support forums
SoC Design and Simulation forum
AXI
Jump...
Cancel
State
Not Answered
Locked
Locked
Replies
3 replies
Subscribers
90 subscribers
Views
6123 views
Users
0 members are here
AMBA
AXI
Interface
Options
Share
More actions
Cancel
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
over 7 years ago
Why burst must not cross 4kb in AXI ?
0
Ninjaseek
over 7 years ago
Hi Venketesh,
Below factors controls the burst:
Burst_length: AxLEN[7:0]
Burst_size : AxSIZE[3:0]
Burst_type : AxBURST[1:0]
While length can be 1 to 256 for an INCR, size could be 1 to 16, the max burst can be 256*16 giving a size of 4KB.
I hope this helps.
Regards,
Nishant
Cancel
Up
0
Down
Cancel
0
Muthuvenkatesh
over 7 years ago
in reply to
Ninjaseek
Hi Nishant,
I understand what you are saying, But what is the reason for that.
Axsize is also 3bit not 4 bit.
Thanks
Muthuvenkatesh
Cancel
Up
0
Down
Cancel
0
Simone Secchi
over 7 years ago
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
Cancel
Up
0
Down
Cancel