Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
resources:fpga:docs:util_axis_fifo [11 Oct 2021 14:55] – Edit next page to be Using and modifying the HDL design Iulia Moldovanresources:fpga:docs:util_axis_fifo [12 Oct 2021 16:56] (current) – Edit footer Iulia Moldovan
Line 1: Line 1:
-====== AXI Stream FIFO Core (util_axis_fifo) ======+====== AXI Stream FIFO Core ======
  
 The util_axis_fifo IP core is a simple FIFO (First Input First Output) with AXI streaming interfaces, supporting synchronous and asynchronous operation modes. It can be used to mitigate data rate differences or transfer an AXI stream to a different clock domain.  The util_axis_fifo IP core is a simple FIFO (First Input First Output) with AXI streaming interfaces, supporting synchronous and asynchronous operation modes. It can be used to mitigate data rate differences or transfer an AXI stream to a different clock domain. 
 +
  
 ===== Features ===== ===== Features =====
Line 11: Line 12:
   * Supports FULL/EMPTY and ALMOST_FULL/ALMOST_EMPTY status signals   * Supports FULL/EMPTY and ALMOST_FULL/ALMOST_EMPTY status signals
   * Support zero-deep implementation   * Support zero-deep implementation
 +
  
 ===== Functional Description ===== ===== Functional Description =====
Line 26: Line 28:
  
 <note important>In case of asynchronous mode, because of the delays introduced by the clock domain crossing logic, the ROOM and LEVEL indicators can not reflect the actual state of the FIFO in real time. Source and destination logic should take this into account when controlling the data stream into and from the FIFO. Carefully adjusting the ALMOST_EMPTY/ALMOST_FULL indicators can provide a save operating margin.</note> <note important>In case of asynchronous mode, because of the delays introduced by the clock domain crossing logic, the ROOM and LEVEL indicators can not reflect the actual state of the FIFO in real time. Source and destination logic should take this into account when controlling the data stream into and from the FIFO. Carefully adjusting the ALMOST_EMPTY/ALMOST_FULL indicators can provide a save operating margin.</note>
 +
  
 ===== Parameters ===== ===== Parameters =====
Line 37: Line 40:
 | ''ALMOST_EMPTY_THRESHOLD'' | Defines the offset (in data beats) between the almost empty and empty assertion | 16 | | ''ALMOST_EMPTY_THRESHOLD'' | Defines the offset (in data beats) between the almost empty and empty assertion | 16 |
 | ''ALMOST_FULL_THRESHOLD'' | Defines the offset (in data beats) between the almost full and full assertion | 16 | | ''ALMOST_FULL_THRESHOLD'' | Defines the offset (in data beats) between the almost full and full assertion | 16 |
 +
  
 ===== Interface ===== ===== Interface =====
Line 62: Line 66:
 | '' m_axis_almost_full '' | output | If set the FIFO is almost full | | '' m_axis_almost_full '' | output | If set the FIFO is almost full |
 | '' m_axis_full '' | output | If set the FIFO is full | | '' m_axis_full '' | output | If set the FIFO is full |
 +
  
 ===== Register Map ===== ===== Register Map =====
Line 67: Line 72:
 This core does not have a register map. This core does not have a register map.
  
-{{navigation HDL User Guide#axi_ip|AXI IP cores#hdl|Main page#tips|Using and modifying the HDL design}}+{{navigation HDL User Guide#ip_cores|IP cores#hdl|Main page#tips|Using and modifying the HDL design}}
resources/fpga/docs/util_axis_fifo.txt · Last modified: 12 Oct 2021 16:56 by Iulia Moldovan