The following figure shows the sequence of events from a
packet of reload data being written to the RELOAD channel (start of first arrow), which
is triggered for use on the arrival and consumption of a packet on the CONFIG channel
(end of first arrow and start of second arrow), and on to the data stream.
Note: Particular care should be taken so that the time between the
start of the first arrow and the end of the first arrow is sufficient to allow the
core to store the new coefficients. When using the Transpose Architecture, this time
should be equal to the time required to process a single data input vector (block of
interleaved channels).
Figure 1. Interface Timing
