Asynchronous FIFO cdc question

promach · Nov 21, 2017

Asynchronous fifo cdc question

For the following asynchronous FIFO, why rinc does not "AND" with !rempty ?

Screenshot extracted from sunburst asynchronous FIFO paper page 9

There is alternative version that does not require the AND gate to generate the signal wclken. Could anyone elaborate ?

Screenshot extracted from sunburst asynchronous FIFO paper page 5

std_match · Nov 24, 2017

Re: Asynchronous fifo cdc question

In FIFO style #1, the FIFO memory can be completely full, so an additional write will overwrite the oldest element.
If you write when the FIFO is full, the correct behavior is to ignore the write. It is not OK to destroy data that is already in the FIFO.
The AND gate prevents the overwrite.

A read will not destroy anything, so no need to AND the read signals. The logic inside "FIFO rptr & empty" will not increment the read pointer when the FIFO is empty.

In FIFO style #2 it is necessary to use "almost full" and "almost empty" signals. This means that there will be some slack, so a write when the FIFO is "almost full" will not destroy anything.
The memory in FIFO style #2 can never be completely full.

Asynchronous FIFO cdc question

promach

Advanced Member level 4

std_match

Advanced Member level 4

Similar threads

Asynchronous FIFO cdc question

promach

Advanced Member level 4

std_match

Advanced Member level 4

Similar threads

Privacy & Transparency

Privacy & Transparency