Avalon® Interface Specifications

ID 683091
Date 1/24/2022

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents waitrequestAllowance Equals Two - Not Recommended

The following diagram illustrates timing for an Avalon® -MM> host that can send two transfers after waitrequest is asserted.

This timing is legal, but not recommended. In this example the host counts the number of transactions instead of the number of clock cycles. This approach requires a counter that makes the implementation more complex and may affect timing closure. When the host determines when to drive transactions with the waitrequest signal and a constant number of cycles, the host starts or stops transactions based on the registered signals.

Figure 10. waitrequestAllowance Equals Two Transfers

The numbers in this figure mark the following events:

  1. The Avalon® -MM> host asserts write and drives data.
  2. The Avalon® -MM> agent asserts waitrequest.
  3. The Avalon® -MM> host drives write and data. Because the waitrequestAllowance is 2, the host drives data in 2 consecutive cycles.
  4. The Avalon® -MM> host deasserts write because the host has spent the 2-transfer waitrequestAllowance.
  5. The Avalon® -MM> host issues a write as soon as waitrequest is deasserted.
  6. The Avalon® -MM> host drives write and data. The agent asserts waitrequest for 1 cycle.
  7. In response to waitrequest, the Avalon® -MM> host holds data for 2 cycles.