Visible to Intel only — GUID: ygy1572912674732
Ixiasoft
Visible to Intel only — GUID: ygy1572912674732
Ixiasoft
4.3. Avalon® Memory-Mapped Master Interfaces
Each mm_master argument of a component results in an input conduit for the address. That input conduit is associated with the component start and busy signals. In addition to this input conduit, a unique Avalon® MM Master interface is created for each address space. Master interfaces that share the same address space are arbitrated on the same interface.
For more information about Avalon® MM Master interfaces, refer to "Avalon Memory-Mapped Interfaces" in Avalon Interface Specifications.
Template Object or Argument | Description |
---|---|
ihc::mm_master | The underlying pointer type. |
ihc::dwidth | The width of the memory-mapped data bus in bits |
ihc::awidth | The width of the memory-mapped address bus in bits. |
ihc::aspace | The address space of the interface that associates with the master. |
ihc::latency | The guaranteed latency from when a read command exits the component when the external memory returns valid read data. |
ihc::maxburst | The maximum number of data transfers that can associate with a read or write transaction. |
ihc::align | The alignment of the base pointer address in bytes. |
ihc::readwrite_mode | The port direction of the interface. |
ihc::waitrequest | Adds the waitrequest signal that is asserted by the slave when it is unable to respond to a read or write request. |
getInterfaceAtIndex | This testbench function is used to index into an mm_master object. |