*
*Home|Chinese|Japanese*About ARM|Forums|Events|News|Employment|Contact Us|Investors*
dotted rule
*ARM - the architecture for the digital worldARM - the architecture for the digital world
search
*
*
***
*MARKETS:PRODUCTS & SOLUTIONS:CONNECTED COMMUNITY:TECHNICAL SUPPORT:DOCUMENTATION*
*
technical support
*
*
****
*.Technical Support
*
*
*>>Home Page*
*
*.Obtaining Support*
*
*.FAQs*
*
**Development Tool FAQs*
**IP FAQs*
**Embedded Software FAQs*
**Artisan Physical IP FAQs (Login Required)*
*
*.Downloads*
*
*.Documentation*
*
*.Training*
*
*.Where To Buy*
*
*.Keil MCU Tools*
*
*.What's New*
*
*.ARM Newsgroups*
*
*.Active Assist On-site Services*
*
*
*
technical support FAQsask ARM*
*

Technical Support Search
*     (Advanced Search)
  FAQs   Documentation   Downloads   Forums

*

downarrowHow do you connect an AHB slave to an AHB-lite system?

AHB slaves are fully AHB-lite compatible, so can be connected directly, unless they generate SPLIT or RETRY responses.

If the AHB slave generates RETRY responses, you will need an Ahb2Ahb bridge (there are several examples in ARM's AMBA Design Kit (ADK)) between the AHB slave and the AHB-lite system. This Ahb2Ahb bridge will locally service the RETRY response, while holding HREADY low (1'b0) to the AHB-lite system.

If the AHB slave generates SPLIT responses then in addition to the Ahb2Ahb bridge required for RETRY responses, you would also need a local Dummy master and an Arbiter. SPLIT responses require the arbiter to grant a different master, so we need the dummy master on this local full-AHB bus to drive IDLE cycles until the slave is able to complete the SPLIT transfer.






back to top
*
**
*4 dots*Other ARM Websites
*
shadow *LEGAL STATEMENTshadow