We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 62568

MIG UltraScale DDR3/DDR4 - How are the app_wdf_end and app_rd_data_end signals used?


(PG150) states that the user interface signals app_wdf_end and app_rd_data_end are used to indicate that the current clock cycle is the last cycle of data on the corresponding app_wdf_data or app_rd_data bus. 

With a 2:1 (1/2 rate) controller to PHY clock ratio each Burst Length 8 (BL8) command requires two data words sent over two clock cycles with the corresponding *_end signal asserted on the second clock cycle to indicate the last cycle of data. 

However, MIG UltraScale only supports a 4:1 (1/4 rate) controller to PHY clock ratio which means for each BL8 command all of the data is sent on one cycle and the *_end signal is always asserted with the data and no longer relevant.


While the *_end signals are no longer relevant, the MIG UltraScale controller still requires that app_wdf_end is driven high along with app_wdf_wren to properly load the write data FIFO.

However, to simplify the user logic, app_wdf_end and app_wdf_wren can be tied together to ensure that they are always driven together.

App_rd_data_end is no longer needed for user logic detection of the end of the read data.

All of this information will be updated in (PG150) in a future software release.

Revision History
10/27/2014 - Initial release
AR# 62568
Date 01/07/2015
Status Active
Type General Article
  • Kintex UltraScale
  • Virtex UltraScale
  • MIG UltraScale
Page Bookmarked