User manual

SPI-4.2 v8.5 Getting Started Guide www.xilinx.com 55

UG154 March 24, 2008

Appendix C

Data and Status Monitor Warnings

The Data and Status monitors continuously check data sent to and received from the

demonstration test bench. There are several common warnings that occur when the

Testcase module is modified. The warnings are listed and described below.

TDat Warning: Source is segmenting packets <simulation time>

This warning means that the Source core is sending payload resumes in the middle of

sending a burst. This is acceptable operation if SrcBurstMode = 0. If SrcBurstMode = 1,

this should only occur if the maximum burst length is reached (as defined by

SrcBurstLen).

RStat Info: Sink is out of frame. Expect TDat mismatches <simulation time>

This indicates that the Sink core went out of frame during operation. Unless training or

idles are being sent on RDat when this occurs, there will be data errors on TDat. This is

because what is being sent in on RDat is no longer being transferred to TDat.

RStat Info: Expected DIP2 mismatch received: SnkDip2ErrReqFlag = 1 <simulation

time>

This indicates that a DIP2 error was detected on RStat. It is only a note and not an error

because SnkDip2ErrReq was asserted, which means that a DIP2 error is expected.

RDat Warning: Protocol Violation #4. Idle follows data on a non-credit boundary

This indicates that the SPI-4.2 protocol was violated when data was sent from the

demonstration test bench. The most likely cause is that send_user_data was used to

send data without an EOPS, which ended on a non-credit boundary, then an idle was sent

using send_idles.

RDat Warning: Protocol Violation

Any RDat protocol violation occurred because of incorrectly formatted data transmitted

from the Testcase Module (that is, they are user-created).