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.