Login

Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

ARM websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.

ARM Community: AHB2AHB Bridge Signal Description - ARM Community

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

AHB2AHB Bridge Signal Description More details about the AHB2AHB Brigde signals Rate Topic: ****- 1 Votes

#1 User is offline   Rashesh 

  • Member
  • Pip
  • Group: Members
  • Posts: 1
  • Joined: 02-March 12

Posted 02 March 2012 - 11:42 AM

Can somebody explain me the details of the following signals?
1. HBUSREQM (Output from Bridge), but goes to whom?
2. HGRANTM (Input to Bridge), comes from whom?
3. HMASTLOCKS (Input to Bridge), comes from whom?
4. HSELS (Input to Bridge), comes from whom?
Please let me know these details.

This post has been edited by Rashesh: 02 March 2012 - 11:43 AM

2

#2 User is offline   JD 

  • Regular Contributor
  • PipPipPip
  • Group: Members.
  • Posts: 260
  • Joined: 17-November 06

Posted 02 March 2012 - 12:25 PM

From your posting it is almost certain that you are looking at a specific implementation of an AHB2AHB bridge, so as such you really should send your questions about that component to the component provider, rather than an open Forum such as this where we might not have access to the same bridge you are looking at.

However just referring to the standard AHB protocol...

1. HBUSREQ(M) - if this is an output from the bridge, the bridge is the master on the M interface, and masters send their bus request to the AHB Arbiter.

2. HGRANT(M) - as above, if this is an input, the bridge is the master on the M interface, and masters receive the bus grant signal from the AHB Arbiter.

3. HMASTLOCK(S) - following the same arguments, HMASTLOCK as an input makes the S interface a slave, and the slave HMASTLOCK input is driven from the AHB arbiter.

4. HSEL(S) - again an input, meaning this is the slave connected to the bus, and the slave HSEL input is an output from the AHB decoder.

I would recommend having a read through the AHB spec to understand where these signals are used and what they indicate.

Regards,

JD
1

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic