Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I'm using the EX-USB FX3 SDK's SLAVE FIFO interface to design.
I'm not sure ,if FLAGA and FLAGB can only be used for the Slave FIFO write operation,or FLAGA and FLAGB can also be used for the Slave FIFO read operation. If FLAGA and FLAGB need to be configured as to indicate the availability of read operation or write operation fist?
By the way, there is a mistake in the manual's Table 1. Synchronous Slave FIIFO Interface Signals (An65974 , P3). FLAGC and FLAGD is not in the Figure 4. Synchronous Slave FIFO Write Sequence(An65974 , P7) as you described in Table 1. Synchronous Slave FIIFO Interface Signals.
FLAGA and FLAGB are used for the Slave FIFO write operation and FLAGC and FLAGD are used for the Slave FIFO read operation.
For write we have Flag A & B. One tell if there is a empty buffer on the DMA side (ready flag), other says if the buffer is about to be full (watermark flag). These are needed for flow control. Similar is the case for read operation where the FPGA tries to read from the slave with the help of flag C&D.
Figure 4 is Synchronous Slave FIFO Write. For write we need to check FLAGA and FLAGB only. So, we have not given the diagram of Flag C&d as we do not care about them during the write sequence.
Can I only use FLAGA and FLAGB to design? I'll configure FLAGA to thread0 for Slave FIFO write operation,and configure FLAGB to thread3 for Slave FIFO read operation.For we know the deepth of the Slave FIFO,we can count to be sure when the Slave FIFO is FULL/EMPTY. Is that available？