Document Number: 001-68336 Rev. *F Page 8 of 32
Flow-through mailbox Register
This register transfers data from input to output directly
bypassing the FIFO sequence. When MB signal is asserte d the
data present on D[35:0] will be available on Q[35:0] after two
WCLK cycles. Normal read and write operations are not allowed
during flow-through mailbox operation. Before starting
Flow-through mailbox operation FIFO read should be completed
to make data valid (DVal) high in order to avoid data loss from
FIFO. The width of flow-through mailbox register always
corresponds to port size.
Flag Operation
This device provides two flags to indicate the condition of the
FIFO Queues.
Full Flag
Full Flag (FF) LOW indicates whether the queue accessed by
WQSEL[2:0] is full and it operates on double wo rd (burst length
of two) boundaries. Write operations are inhibited whene ver FF
is LOW regardless of the state of WEN. FF is synchronized to
WCLK, that is, it is exclusively updated by each rising edge of
WCLK. The worst case assertion latency for Full Flag is four. As
the user cannot know that the FIFO is full for four clock cycles, it
is possible that user continues writing data during this time. In
this case, the four data words written will be stored to prevent
data loss and these words have to be read ba ck in order fo r full
flag to get de-asserted. In 2Q or 4Q or 8Q mode, FF indicates
the status of the queue sele cted by W QSEL[2:0]. Th e mini mum
number of reads required to de-assert full-flag are two and the
maximum number of reads required to de-assert full flag are six.
The assertion and de-assertion latencies of Full Fla g are given
in Latency Table on page 15.
Empty Flag
Empty Flag (EF) LOW indicates that the queue accessed by
RQSEL[2:0] is empty and its de-assertion depends on burst
writes. Read operations are inhibited whenever EF is LOW,
regardless of the state of REN. EF is synchronized to RCLK, i.e.,
it is exclusively updated by each rising edge of RCLK. In
2Q/4Q/8Q mode, EF indicates the status of the queue selected
by RQSEL[2:0]. The assertion and de-assertion latencies of
Empty Flag are given in Latency Table on page 15.
Retransmit from Mark Operation
The retransmit feature is useful fo r transferring packets of data
repeatedly. It enables the receipt of data to be acknowledged by
the receiver and retransmitted if necessary. Initiation of a
retransmit operation (using RT pin) resets the internal read
pointer to a physical l ocation of the FIFO that is marked by the
user (using the MARK pin).
The retransmit feature can be used when two or more data words
have been written to the queue. When the MARK pin is asserted,
the memory location corresponding to valid data (DVal signal
LOW) present on the output bus is marked. QV al[2:0] signals can
be used to validate the queue for which the mark operation is
being performed. A mark operation is mandated prior to initiating
a retransmit operation for a queue.
In this device the RT signal is validated with RQSEL[2:0], i.e.,
Retransmit function will be performed for the Queue that is
selected by RQSEL[2:0]. With every valid read cycle after
retransmit, previously accessed data is read until the queue
becomes empty. Data written to the queue (Queue on which
retransmit operation is being performed) after activation of RT
are also transmitted. The full depth of the queue can be
repeatedly retransmitted. Flags are governed by the relative
locations of the read and write pointers and are updated during
a retransmit cycle. Refer to the latency table for the associated
flag update latencies after initiation of a retransmit cycle [4].
A retransmit operation should not be initiated when reads or
writes are in progress. User should wait for four RCLK cycles
after disabling reads before RT is asserted to ensure that the
reads are completed.
On initiation of RT the ‘marked’ location becomes the new Full
Boundary. If user continues to write the data after initiati on of a
retransmit operation, FF will be asserted when this boundary is
reached i.e. FF is asserted once the write pointer reaches the
marked location.This prevents overwriting and data-loss. During
RT reads the full boundary remains frozen to the marked location
and is released when the FIFO becomes empty. i.e. FF remains
LOW until the entire FIFO is read. Full flag is deasserted
LFF_RELEASE cycles after the EF is asserted. Full boundary is
also released on a reset operation (MRS) [4].
Refer to Latency Table on page 15 for more details.
Programming Configuration Registers
The CYF2072V has ten 8-bit user configurable registers. These
registers are used to configure the number of queues & to set the
Fast CLK Bit.
These registers can be programmed in one of two ways: serial
loading or parallel loading method. The loading method is
selected using the SPI_SEN (Serial Enabl e) pin. A LOW on the
SPI_SEN selects the serial method for writing into the reg isters
whereas a HIGH on SPI_SEN selects parallel loading method.
For serial programming, there i s a separate SCLK and a Serial
Input (SI). In parallel mode, the load (LD) pin is used to perform
write and read operations on these registers. The write and read
operations are performed in a sequence from the first
location(0x1) to the last location (0xA) when the LD pin is held
LOW. If LD is HIGH, the FIFO queues are written or read.
Register values can be read through the parallel output port
regardless of the programming mode selected (serial or parallel).
Register values cannot be read serially. The configuration
registers should be programmed only once after master reset to
ensure accurate flag operation, regardless of whether serial or
parallel programming is selected.
See Table 4 on page 10 and Table 5 on page 11 for access to
configuration registers in serial and parallel modes.
In parallel mode, the read an d write operations loop back when
the maximum address location of the configuration registers is
reached. Simultaneous read and write operations must be
avoided on the configuration registers. Any change in
configuration registers will take effect after eight write clock
cycles (WCLK) cycles.
Notes
4. Errata: Refer to Errata on page 30 for details on flag operation and full boundary freezing during mark and retransmit operation.