Avalon Interface Specifications (PDF) - Altera
Avalon Interface Specifications (PDF) - Altera
Avalon Interface Specifications (PDF) - Altera
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 3: <strong>Avalon</strong> Memory-Mapped <strong>Interface</strong>s 3–9<br />
Transfers<br />
1 waitrequest can be decoupled from the read and write request signals so that it may<br />
be asserted during idle cycles. An <strong>Avalon</strong>-MM master may initiate a transaction when<br />
waitrequest is asserted and wait for that signal to be deasserted. Decoupling<br />
waitrequest from read and write requests may improve system timing by<br />
eliminating a combinational loop including the read, write, and waitrequest signals.<br />
Figure 3–3. Read and Write Transfers with Waitrequest<br />
Notes to Figure 3–3:<br />
clk<br />
address<br />
byteenable<br />
read<br />
write<br />
waitrequest<br />
readdatavalid<br />
readdata<br />
writedata<br />
1 2 3 4 5 6<br />
address<br />
byteenable<br />
readdata<br />
(1) address, read, and begintransfer are asserted after the rising edge of clk. waitrequest is asserted stalling the transfer.<br />
(2) waitrequest is sampled. Because waitrequest is asserted, the cycle becomes a wait-state, and address, read, write, and byteenable<br />
remain constant.<br />
(3) The slave presents valid readdata, asserts readdatavalid, and deasserts waitrequest.<br />
(4) readdata and deasserted waitrequest are sampled, completing the transfer.<br />
(5) address, writedata, byteenable, begintransfer, and write signals are asserted. The slave responds by asserting waitrequest, stalling<br />
the transfer.<br />
(6) The slave captures writedata and deasserts waitrequest, ending the transfer.<br />
3.5.2. Read and Write Transfers with Fixed Wait-States<br />
writedata<br />
Instead of using waitrequest to hold off a transfer, a slave can specify fixed<br />
wait-states using the readWaitTime and writeWaitTime properties. The address and<br />
control signals (byteenable, read, and write) are held constant for the duration of the<br />
transfer. The read/write timing with readWaitTime/writeWaitTime set to is<br />
exactly the same as asserting waitrequest for cycles per transfer.<br />
May 2013 <strong>Altera</strong> Corporation <strong>Avalon</strong> <strong>Interface</strong> <strong>Specifications</strong>