Arm Community
Site
Search
User
Site
Search
User
Groups
Arm Research
DesignStart
Education Hub
Graphics and Gaming
High Performance Computing
Innovation
Multimedia
Open Source Software and Platforms
Physical
Processors
Security
System
Software Tools
TrustZone for Armv8-M
中文社区
Blog
Announcements
Artificial Intelligence
Automotive
Healthcare
HPC
Infrastructure
Innovation
Internet of Things
Machine Learning
Mobile
Smart Homes
Wearables
Forums
All developer forums
IP Product forums
Tool & Software forums
Pelion IoT Platform
Support
Open a support case
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Developer Community
IP Products
System
Jump...
Cancel
System
SoC Design forum
AXI Cacheable vs. Bufferable
Blogs
Forums
Videos & Files
Help
Jump...
Cancel
New
State
Not Answered
Replies
2 replies
Subscribers
71 subscribers
Views
8025 views
Users
0 members are here
AMBA
AXI
Bus Architecture
Related
AXI Cacheable vs. Bufferable
Offline
Randy Pascarella
over 7 years ago
Note: This was originally posted on 19th November 2007 at
http://forums.arm.com
If an AXI slave acting as a bridge has accepted a bufferable (ACACHE[0]) and cacheable (ACACHE[1]) write and responded with BRESP, is it required to flush this buffered write when later accepting a read from the same AXI master that overlaps but is marked as not cacheable?
In other words, should the cacheable bit be used in determining when bufferable writes should be flushed, or is flushing only required as noted in the spec upon receipt of a non-bufferable write with matching AWID?
0
Offline
Randy Pascarella
over 7 years ago
Note: This was originally posted on 20th November 2007 at
http://forums.arm.com
I was concerned about the ACACHE[C] bit for the read being set to 0 meaning that the read must not be prefetched. I took this to mean that the read must come from the final destination and not an intermediate bridge that was "caching" the data due to a previous bufferable write.
For example, could a device use a read (non-cacheable) to push a previous bufferable write to its final destination to know when it was safe to assert an interrupt, or would that device be required to use a non-bufferable write to achieve this? It seems to me that using a cacheable read would obtain the new data, but that data could be forwarded by an intermediate bridge. An interrupt could cause a processor to read the final destination and not see the new data due to the processor read taking a different path. Does this make sense?
Also, you bring up a point I was not aware of. You're saying that a bridge taking a bufferable write must take ownership of RAW hazards for all masters, not just the issuing master. Is this required behavior for AXI? Statements about ordering in the spec are master-centric, so I assumed that RAW hazards only applied within a master.
Once again, you've been very helpful. Thanks!!!
Cancel
Up
0
Down
Reply
Accept answer
Cancel
0
Offline
Colin Campbell
over 7 years ago
Note: This was originally posted on 20th November 2007 at
http://forums.arm.com
Hi Randy,
I would think that a slave which decides to give a BRESP for a bufferable write before the write data reaches the eventual destination is taking responsibility for any hazard checking for subsequent reads or writes, from the same or different masters.
A non-bufferable write would need to flush the write buffer to maintain the correct system event ordering, but a read could just be handled by forwarding write data from the write buffer if a hit is detected, rather than delaying the master while the write buffer is flushed.
The cacheability (is that a real word ?) of the read shouldn't affect whether the buffer is flushed or not.
Or am I missing a more subtle problem ?
I guess if you wanted to make the system foolproof (and simpler), flushing the write buffer for any subsequent read access would ensure you are accessing the most recent data.
JD
Cancel
Up
0
Down
Reply
Accept answer
Cancel
More questions in this forum
By title
By date
By reply count
By view count
By most asked
By votes
By quality
Descending
Ascending
All recent questions
Unread questions
Questions you've participated in
Questions you've asked
Unanswered questions
Answered questions
Questions with suggested answers
Questions with no replies
Suggested Answer
APB4 PSTRB
0
3925
views
1
reply
Latest
3 months ago
by
Colin Campbell
Not Answered
AHB Lite
0
4880
views
1
reply
Latest
3 months ago
by
Colin Campbell
Not Answered
Ulink pro debugging in custom SoC
0
Custom SoC
ulinkpro
SoC Verification
3461
views
0
replies
Started
4 months ago
by
ronit
Not Answered
Design considerations for implementing flash program download
0
CoreSight Architecture
SWD
Debug Access Port (DAP)
10388
views
3
replies
Latest
4 months ago
by
Mohamed Nasser
Not Answered
Using sram instead of a flash memory in ASIC implementation
0
SoC Implementation
SRAM
SoC FPGA
Debugging
4130
views
0
replies
Started
4 months ago
by
Mohamed Nasser
<
>
View all questions in SoC Design forum