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# 18008

LogiCORE SPI-4.2 (POS-PHY L4) - Why is my SrcOof clearing before my NumDip2Matches has been met ?


General Description: 

The NumDip2Matches is set to a fixed value in my design. According to the data sheet, the core is supposed to clear the SrcOof (Source Out of frame) signal when a consecutive number of Dip2 matches (defined by the signal NumDip2Matches) is received. In simulation and in the hardware this does not appear to be working correctly.


A specific pattern on TStat [1:0] can cause the internal signal match to count incorrectly. SrcOof will be de-asserted only if match == NumDIP2Matches


When the TStat bus receives a status sequence that is an incorrect length when previously it has already received status sequence with correct DIP2 values, the counter does not reset. 


Due to this reason, the counter does not count all the DIP2s correctly and hence will de-assert the SrcOof at the wrong count value.

AR# 18008
Date 05/16/2014
Status Archive
Type General Article
Page Bookmarked