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
AHB Multilayer
Blogs
Forums
Videos & Files
Help
Jump...
Cancel
New
State
Not Answered
Replies
8 replies
Subscribers
71 subscribers
Views
5816 views
Users
0 members are here
AMBA
Bus Architecture
AHB
Related
AHB Multilayer
Offline
Jesuraj vinoth Joseph
over 7 years ago
Note: This was originally posted on 30th April 2008 at
http://forums.arm.com
In the multilayer environment, i found a interconnect matrix with interface signals on the Master side having a hsel signal. Can anyone specify the significance of it. A basic doubt is that apart from the interconnect matrix do we hav any slave mux and decoder.
Parents
0
Offline
Colin Campbell
over 7 years ago
Note: This was originally posted on 8th May 2008 at
http://forums.arm.com
Hi Ark,
I don't know anything about the Cadence UVC, but assuming they haven't done anything strange with their signals, the HSELS0 input should be driven by your local AHB Decoder. This means the interconnect slave port is just one of the slaves appearing on your master's bus.
However if the interconnect is the only slave connected directly to your AHB master, you won't have a local AHB decoder (because all transfers are routed to the interconnect), and so the HSELS0 input would be tied to 1'b1.
As far as the HREADYS0 and HREADYOUTS0 pins on the interconnect are concerned, this is what you will always see on any AHB slave.
For the scenario where you have lots of local slaves, the HREADYOUTS0 signal is MUXed together with all the other local slave HREADYOUT signals, so that the data phase active HREADYOUT signal is routed to the AHB master HREADY input, and this MUX output is also routed back to ALL the local slaves as the HREADY input (the HREADYSo input on the interconnect).
For the single slave scenario (where HSELS0 is tied to 1'b1), the MUX is not needed. As the interconnect will always be the data phase active slave, its HREADYOUTS0 signal drives the master's HREADY input, and is also directly driven back into the interconnect HREADYS0 input.
Or at least that's how I've seen ARM's AHB interconnect used
JD..
Cancel
Up
0
Down
Reply
Accept answer
Cancel
Reply
0
Offline
Colin Campbell
over 7 years ago
Note: This was originally posted on 8th May 2008 at
http://forums.arm.com
Hi Ark,
I don't know anything about the Cadence UVC, but assuming they haven't done anything strange with their signals, the HSELS0 input should be driven by your local AHB Decoder. This means the interconnect slave port is just one of the slaves appearing on your master's bus.
However if the interconnect is the only slave connected directly to your AHB master, you won't have a local AHB decoder (because all transfers are routed to the interconnect), and so the HSELS0 input would be tied to 1'b1.
As far as the HREADYS0 and HREADYOUTS0 pins on the interconnect are concerned, this is what you will always see on any AHB slave.
For the scenario where you have lots of local slaves, the HREADYOUTS0 signal is MUXed together with all the other local slave HREADYOUT signals, so that the data phase active HREADYOUT signal is routed to the AHB master HREADY input, and this MUX output is also routed back to ALL the local slaves as the HREADY input (the HREADYSo input on the interconnect).
For the single slave scenario (where HSELS0 is tied to 1'b1), the MUX is not needed. As the interconnect will always be the data phase active slave, its HREADYOUTS0 signal drives the master's HREADY input, and is also directly driven back into the interconnect HREADYS0 input.
Or at least that's how I've seen ARM's AHB interconnect used
JD..
Cancel
Up
0
Down
Reply
Accept answer
Cancel
Children
No data
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
Not Answered
Behaviour of CHI Receiver during race condition from RUN to DEACTIVATE
0
AMBA
AMBA 5 CHI
CHI
Bus Architecture
AMBA 5
4181
views
0
replies
Started
4 months ago
by
amit
Not Answered
In APB, Why do we use enable signal? (Don't care about PREADY)
0
4518
views
0
replies
Started
4 months ago
by
INNS
Not Answered
DC/DC Controller SoC
0
5015
views
1
reply
Latest
5 months ago
by
Andy Neil
Not Answered
AMBA 5 CHI : Does Interleaving of TxnID within a Multiple flits message allowed?
+1
System on Chip (SoC)
AMBA 5 CHI
CHI
Cache Architecture
5206
views
1
reply
Latest
5 months ago
by
IPDeveloper
Not Answered
AXI4 transaction attributes
0
5024
views
0
replies
Started
5 months ago
by
Ravi V.
<
>
View all questions in SoC Design forum