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 Write Bursts

These rules apply when a write burst begins with burstcount greater than one:

  • When a burstcount of <n> is presented at the beginning of the burst, the agent must accept <n> successive units of writedata to complete the burst. Arbitration between the host-agent pair remains locked until the burst completes. This lock guarantees that no other host can execute transactions on the agent until the write burst completes.
  • The agent must only capture writedata when write asserts. During the burst, the host can deassert write indicating that writedata is invalid. Deasserting write does not terminate the burst. The write deassertion delays the burst and no other host can access the agent, reducing the transfer efficiency.
  • The agent delays a transfer by asserting waitrequest forcing writedata, write, burstcount, and byteenable to be held constant.
  • The functionality of the byteenable signal is the same for bursting and non-bursting agents. For a 32-bit host burst-writing to a 64-bit agent, starting at byte address 4, the first write transfer seen by the agent is at its address 0, with byteenable = 8'b11110000. The byteenables can change for different words of the burst.
  • The byteenable signals do not all have to be asserted. A burst host writing partial words can use the byteenable signal to identify the data being written.
  • Writes with byteenable signals being all 0's are simply passed on to the Avalon® -MM agent as valid transactions.
  • The constantBurstBehavior property specifies the behavior of the burst signals.
    • When constantBurstBehavior is true for a host, the host holds address and burstcount stable throughout a burst. When true for a agent, constantBurstBehavior declares that the agent expects address and burstcount to be held stable throughout a burst.
    • When constantBurstBehavior is false, the host holds address and burstcount stable only for the first transaction of a burst. When constantBurstBehavior is false, the agent samples address and burstcount only on the first transaction of a burst.
Figure 14. Write Burst with constantBurstBehavior Set to False for Host and AgentThe following figure demonstrates a agent write burst of length 4. In this example, the agent asserts waitrequest twice delaying the burst.

The numbers in this timing diagram mark the following transitions:

  1. The host asserts address, burstcount, write, and drives the first unit of writedata.
  2. The agent immediately asserts waitrequest, indicating that the agent is not ready to proceed with the transfer.
  3. waitrequest is low. The agent captures addr1, burstcount, and the first unit of writedata. On subsequent cycles of the transfer, address and burstcount are ignored.
  4. The agent captures the second unit of data at the rising edge of clk.
  5. The burst is paused while write is deasserted.
  6. The agent captures the third unit of data at the rising edge of clk.
  7. The agent asserts waitrequest. In response, all outputs are held constant through another clock cycle.
  8. The agent captures the last unit of data on this rising edge of clk. The agent write burst ends.

In the figure above, the beginbursttransfer signal is asserted for the first clock cycle of a burst and is deasserted on the next clock cycle. Even if the agent asserts waitrequest, the beginbursttransfer signal is only asserted for the first clock cycle.