AMBA and AXI
AMBA and AXI
The AHB protocol is part of the AMBA 2 standard, introduced to provide a high-performance,
system-level bus for communication between different components of a SoC (System-on-Chip).
Features of AHB
o AHB operates on a single clock edge for simplicity and better performance.
2. High Bandwidth:
3. Burst Transfers:
o At any time, only one master has access to the bus, simplifying arbitration.
o Increases bus efficiency by overlapping the address and data phases of successive
transfers.
o The slave can deassert its response (e.g., when busy), allowing retries.
1. Master: Initiates read/write operations and controls the address and data phases.
3. Arbiter: Determines which master can access the bus when multiple masters are requesting.
4. Decoder: Decodes the address from the master and routes the request to the appropriate
slave.
1. Address Phase:
2. Data Phase:
3. Response Phase:
AHB-Lite
The ASB protocol is part of the AMBA 1 specification, introduced in the late 1990s. It was designed
as a high-performance bus for communication between components in a System-on-Chip (SoC).
Although ASB has been largely replaced by AHB and AXI in modern designs, it was a significant step
forward in enabling synchronous, efficient data transfers.
Features of ASB
2. Multiple Masters:
3. Burst Transfers:
o Both address and data transfers occur in a synchronous manner, improving bus
performance.
o The slave can introduce wait states if it is not ready to respond, enabling slower
peripherals to interface.
3. Arbiter: Controls which master gains access to the bus in multi-master systems.
4. Decoder: Decodes the address from the master and selects the appropriate slave.
ASB Operation
1. Address Phase:
o The master places the address and control signals on the bus.
2. Data Phase:
o Burst transfers allow multiple data words to be sent after a single address phase.
3. Wait States:
o If the slave cannot respond immediately, it can introduce wait states to delay the
transfer.
ASB Limitations
1. No Pipelining:
o ASB does not support pipelining, limiting its efficiency compared to AHB and AXI.
o Burst transfers are supported but are less flexible than those in AHB and AXI.
The APB protocol is part of the AMBA (Advanced Microcontroller Bus Architecture) standard. It is
designed for low-bandwidth, low-power, and simple peripheral communication in a System-on-
Chip (SoC). APB is commonly used to connect peripherals such as timers, UARTs, and GPIOs to the
main bus system.
1. Low Complexity:
o APB is designed for simplicity, with minimal control signals and no pipelining.
2. Single-Clock Operation:
o All transfers occur on the rising edge of a single clock signal, reducing complexity.
o APB's simplicity and lack of high-speed operation make it ideal for power-sensitive
applications.
4. No Burst Support:
o APB supports single data transfers only—it does not allow bursts.
o Each APB transfer consists of two distinct phases: an address phase followed by a
data phase.
o Supports simple read and write operations between the master and slave.
1. Master:
2. Slave:
3. Bridge:
APB Operation
o The master drives the address and control signals onto the bus.
2. Data Phase:
o The master transfers data for a write operation or receives data from the slave for a
read operation.
The transfer is complete when PENABLE is asserted by the master and the slave responds with valid
data.
AXI
o AXI separates read and write data channels for parallel operation, increasing
efficiency.
3. Burst Transfers:
5. Out-of-Order Completion:
o Designed for high bandwidth and low latency with minimal arbitration delays.
AXI Signals
1. Write Transaction
2. Read Transaction
Advantages of AXI
1. High Performance:
2. Scalability:
3. Flexibility:
4. Low Latency: