Tutorials

Protocols

Learn More

AHB signals are prefixed with H. The signal set can be understood in groups: global signals, Manager address/control signals, Manager write-data signals, Subordinate response signals, decoder signals, muxed response signals, and optional AHB5 features.

ahb-signal-groups

Global signals

SignalSourceDescription
HCLKClock sourceBus clock. All protocol timing is related to the rising edge.
HRESETnReset controllerActive-low reset. This is the only active-low protocol signal.

Manager-driven signals

A Manager provides address and control information to initiate read and write operations

ahb-manager-interface
SignalDescription
HADDRByte address of the transfer. Address width is configurable.
HWRITETransfer direction. HIGH means write, LOW means read.
HSIZETransfer size, such as byte, halfword, word, or wider.
HBURSTBurst type and burst length.
HTRANSTransfer type: IDLEBUSYNONSEQ, or SEQ.
HPROTProtection and memory attribute information.
HMASTLOCKIndicates a locked transfer sequence.
HWDATAWrite data driven by the Manager during the data phase.
HWSTRBOptional write strobes. One bit per write-data byte lane.

Subordinate response signals

A Subordinate responds to transfers initiated by the Manager, using the HSELx select signal from the decoder to determine when to act.

To communicate the transfer’s status back to the Manager, the Subordinate signals:

  • Status/Extension: Whether the transfer is complete or needs to be extended.

  • Outcome: Whether the transfer succeeded or failed.

SignalDescription
HRDATARead data from the selected Subordinate.
HREADYOUTSubordinate output that indicates whether its data phase is complete.
HRESPTransfer response. LOW is OKAY, HIGH is ERROR.

Decoder and muxed interconnect signals

The interconnect component manages the connectivity between Managers and Subordinates. The system architecture scales based on the number of Managers:

  • Single-Manager Systems: Require only a centralized Decoder and Multiplexor (detailed below).

  • Multi-Manager Systems: Require an interconnect that handles arbitration and signal routing (address, control, and write data) from multiple Managers to the appropriate Subordinates.

SignalDescription
HSELxDecoder-generated select signal for a Subordinate.
HREADYMuxed ready signal returned to the Manager and Subordinates. It is derived from the selected Subordinate response path.
  • Decoder: Decodes transfer addresses to select the active Subordinate and outputs control signaling to the multiplexor.

  • Multiplexor: Routes the read data bus and response signals from the selected Subordinate back to the Manager, guided by the decoder’s control signals.

Optional AHB5 signals

These signals are present only when the corresponding interface feature is implemented, such as secure transfers, exclusive transfers, user sideband signaling, or interface protection using parity/check signals.

SignalPurpose
HNONSECMarks Secure or Non-secure transfers when secure transfers are supported.
HEXCLMarks an exclusive transfer.
HMASTERManager identifier used with exclusive transfers.
HEXOKAYIndicates success or failure of an exclusive transfer.
HAUSERUser-defined request attribute.
HWUSERUser-defined write-data attribute.
HRUSERUser-defined read-data attribute.
HBUSERUser-defined response attribute.
*CHK signalsOptional parity/check signals for interface protection.

Signal width properties

Current AHB specifications describe many signal widths using properties. For example:

PropertyApplies toPractical note
ADDR_WIDTHHADDRCommonly 32 bits, but configurable.
DATA_WIDTHHWDATAHRDATACan be wider than 32 bits in high-bandwidth systems.
HPROT_WIDTHHPROTCan be absent, 4 bits, or extended to 7 bits.
HMASTER_WIDTHHMASTERUsed when exclusive transfer support needs Manager identity.
USER_*_WIDTHUser signalsWidth 0 means the signal is not present.

For RTL, treat these as parameters. Do not hard-code 32-bit address or data assumptions unless the local interface contract explicitly fixes those widths.