--- Quote Start ---
originally posted by smcnutt@Mar 14 2006, 08:34 AM
hi queisser,
> and the rising edge after that starts the next cycle?
that depends on the state of the control signals ... and how you define "next cycle".
basically, the rising edge where waitrequest is negated completes the current
"bus cycle" (the data is latched, for example on a read). the rising edge that
completes one bus cycle can be the start of the next. if read remains asserted,
the _following_ rising edge can potentially complete the next cycle (if waitrequest
is negated).
regards,
--scott
<div align='right'><{post_snapback}> (index.php?act=findpost&pid=13413)
--- quote end ---
--- Quote End ---
Ok, thanks, that confirms what I thought. I think I'm back to using flow control since I can never know when my peripheral (the FTDI USB fifo chip) will be able to produce data. I don't really want to hold off the transfer for minutes at a time with waitrequest so I think I'll use flow control instead. From the manual it appears that that's the recommended way of doing it.
Andrew