3.3. Interface Properties
|Name||Default Value||Legal Values||Description|
|addressUnits||Host - symbols
Specifies the unit for addresses. A symbol is typically a byte.
Refer to the definition of address in the Avalon® Memory-Mapped Interface Signal Types table for the typical use of this property.
|alwaysBurstMaxBurst||false||true, false||When true, indicates that the host always issues the maximum-length burst. The maximum burst length is 2 burstcount_width - 1 . This parameter has no effect for Avalon® -MM agent interfaces.|
|burstcountUnits||words||words, symbols||This property specifies the units for the burstcount signal. For symbols, the burstcount value is interpreted as the number of symbols (bytes) in the burst. For words, the burstcount value is interpreted as the number of word transfers in the burst.|
|burstOnBurstBoundariesOnly||false||true, false||If true, burst transfers presented to this interface begin at addresses which are multiples of the maximum burst size.|
|true, false||Hosts: When true, declares that the host holds address and burstcount constant throughout a burst transaction. When false (default), declares that the host holds address and burstcount constant only for the first beat of a burst.
Agents: When true, declares that the agent expects address and burstcount to be held constant throughout a burst. When false (default), declares that the agent samples address and burstcount only on the first beat of a burst.
|holdTime (1)||0||0 – 1000 cycles||Specifies time in timingUnits between the deassertion of write and the deassertion of address and data. (Only applies to write transactions.)|
|linewrapBursts||false||true, false||Some memory devices implement a wrapping burst instead of an incrementing burst. When a wrapping burst reaches a burst boundary, the address wraps back to the previous burst boundary. Only the low-order bits are required for address counting. For example, a wrapping burst to address 0xC with burst boundaries every 32 bytes across a 32-bit interface writes to the following addresses:
|maximumPendingReadTransactions (1)||1 (2)||1 – 64||
Agents: This parameter is the maximum number of pending reads that the agent can queue. The value must be non-zero for any agent with the readdatavalid signal.
Refer to Pipelined Read Transfer with Variable Latency for a timing diagram that illustrates this property and for additional information about using waitrequest and readdatavalid with multiple outstanding reads.
Hosts: This property is the maximum number of outstanding read transactions that the host can generate.
Note: Do not set this parameter to 0. (For backwards compatibility, the software supports a parameter setting of 0. However, you should not use this setting in new designs).
|maximumPendingWriteTransactions||0||1 – 64||
The maximum number of pending non-posted writes that a agent can accept or a host can issue. A agent asserts waitrequest once the interconnect reaches this limit, and the host stops issuing commands.The default value is 0, which allows unlimited pending write transactions for a host that supports write responses. A agent that supports write responses must set this to a non-zero value.
|minimumResponseLatency||1||For interfaces that support readdatavalid or writeresponsevalid, specifies the minimum number of cycles between a read or write command and the response to the command.|
|readLatency (1)||0||0 – 63||Read latency for fixed-latency Avalon® -MM agents. For a timing diagram that uses a fixed latency read, refer to Pipelined Read Transfers with Fixed Latency.
Avalon® -MM agents that are fixed latency must provide a value for this interface property. Avalon® -MM agents that are variable latency use the readdatavalid signal to specify valid data.
|readWaitTime (1)||1||0 – 1000 cycles||For interfaces that do not use the waitrequest signal. readWaitTime indicates the timing in timingUnits before the agents accepts a read command. The timing is as if the agent asserted waitrequest for readWaitTime cycles.|
|setupTime (1)||0||0 – 1000 cycles||Specifies time in timingUnits between the assertion of address and data and assertion of read or write.|
|Specifies the units for setupTime, holdTime, writeWaitTime and readWaitTime. Use cycles for synchronous devices and nanoseconds for asynchronous devices. Almost all Avalon® -MM agent devices are synchronous.
An Avalon® -MM component that bridges from an Avalon® -MM agent interface to an off-chip device may be asynchronous. That off-chip device might have a fixed settling time for bus turnaround.
Specifies the number of transfers that can be issued or accepted after waitrequest is asserted.
When the waitrequestAllowance is 0, the write, read and waitrequest signals maintain their existing behavior as described in the Avalon® -MM Signal Roles table.
When the waitrequestAllowance is greater than 0, every clock cycle on which write or read is asserted counts as a command transfer. Once waitrequest is asserted, only waitrequestAllowance more command transfers are legal while waitrequest remains asserted. After the waitrequestAllowance is reached, write and read must remain deasserted for as long as waitrequest is asserted.
Once waitrequestdeasserts, transfers may resume at any time without restrictions until waitrequest asserts again. At this time, waitrequestAllowance more transfers may complete while waitrequest remains asserted.
Host: Host can assert read or write signals M times after waitrequest has been asserted. M is the Host's waitrequestAllowance property.
Agent: Agent can accept N transfers after it asserts the waitrequest signal. N is the Agent's waitrequestAllowance property.
|writeWaitTime (1)||0||0 – 1000 Cycles||For interfaces that do not use the waitrequest signal, writeWaitTime specifies the timing in timingUnits before a agent accepts a write. The timing is as if the agent asserted waitrequest for writeWaitTime cycles or nanoseconds.
For a timing diagram that illustrates the use of writeWaitTime, refer to Read and Write Transfers with Fixed Wait-States.
|Interface Relationship Properties|
|associatedClock||N/A||N/A||Name of the clock interface to which this Avalon® -MM interface is synchronous.|
|associatedReset||N/A||N/A||Name of the reset interface which resets the logic on this Avalon® -MM interface.|
|bridgesToHost||0||Avalon® -MM Host name on the same component||An Avalon® -MM bridge consists of a agent and a host, and has the property that an access to the agent requesting a byte or bytes causes the same byte or bytes to be requested by the host. The Avalon® -MM Pipeline Bridge in the Platform Designer component library implements this functionality.|
Did you find the information on this page useful?