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
Support
Open a support case
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Developer Community
Tools and Software
Software Tools
Jump...
Cancel
Software Tools
Arm Development Studio forum
AXI ID problem for cascaded interconnect design
Tools, Software and IDEs blog
Forums
Videos & Files
Help
Jump...
Cancel
New
Replies
2 replies
Subscribers
126 subscribers
Views
2354 views
Users
0 members are here
Related
AXI ID problem for cascaded interconnect design
Offline
Nan Kou
over 7 years ago
Note: This was originally posted on 18th December 2010 at http://forums.arm.com
As we know, the interconnect can add bits to ID fields to indentify the master issuing the transaction. In the SoC design, it is common that cascaded interconnects , like hierarchical architecture, compose the interconnect network. for that the ID width of the master interface of the cascaded design would be extended to many bits, however, some slave cannot support too many ID bits. Is there any recommendations or discussions about handling this problem? Hope for your kind help:)
Offline
Nan Kou
over 7 years ago
Note: This was originally posted on 27th December 2010 at
http://forums.arm.com
It helps. Thanks for JD's kind and patient reply every time.
Cancel
Up
0
Down
Reply
Cancel
Online
Colin Campbell
over 7 years ago
Note: This was originally posted on 21st December 2010 at
http://forums.arm.com
If there is no way of reducing the number of active ID bits seen at a slave (i.e. looking at all the potential ID encodings that could physical reach this slave might highlight a few bits that remain static, and so could be tied off or left unconnected), then you will need to implement some sort of ID compression logic.
This compression logic would perhaps need to contain a memory of "interconnect ID" width and "slave combined acceptance capability" depth, and this memory will store the real ID value for a transaction, and will generate a narrower ID value (width determined by the acceptance capability of the slave) for the slave to use, expanding the ID back to the original value for the RID and BID returns.
The logic is not simple because there are AXI ordering issues to take into account, and issues for exclusive accesses, but it would then reduce the number of ID bits needed at the slave if it has been designed (incorrectly) to not have a configurable ID width.
That is how I'd think you would need to attack this problem.
JD
Cancel
Up
0
Down
Reply
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
Answered
Can't get a 30-day Gold Edition evalution license
+1
704
views
7
replies
Latest
1 month ago
by
KokoBongo
Answered
Failure to get an evaluation license with error Unable to execute API call /api/v1/connect
0
7074
views
5
replies
Latest
1 month ago
by
Ronan Synnott
Answered
error encountered when try to connect FVP
0
4336
views
18
replies
Latest
1 month ago
by
MattB
Suggested Answer
ARM DStudio can't detect Juno CPU core via DStream
0
345
views
2
replies
Latest
1 month ago
by
QiangHuang
Answered
ARM Development Studio IDE 2020.1 and DE10-NANO --> Linker and debugging issue
+1
1027
views
3
replies
Latest
1 month ago
by
Ronan Synnott
<
>
View all questions in Arm Development Studio forum