This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SRIO Delineation Error

Hi:

the SRIO delineation error bit is set after running for a period of time.

Does anybody know that how the SRIO Delineation Error generate?

I think the delineation error generates becasue the signal is not good eoough. but which kind of signal will cause the delineation error?

and another question, how to recover after this error? thank you very much!

 

  • Which device are you using?

  • Hi RandyP:

    we use Faraday. there are 3 DSPs, each SRIO of DSP is connect with SRIO switch, and there are aonther 2 SRIO in FPGA connect with SRIO switch.

    so there are 5 SRIO port communicate through a SRIO switch.

  • King Wang,

    Other than the brief comment in the SRIO User's Guide about alignment issues, there is nothing I see in the TI documentation about this.

    To learn more about the delineation error, you will have to find the SRIO Standard specification documents that are referenced in section 1.3 or the SRIO User's Guide.

    This sounds like a serious problem, because connecting these SRIO ports through switches and to other compatible devices should be quite possible. There could be noise issues or interconnect errors or interoperability problems.

    There are companies that make SRIO bus analysis test equipment, and these may be needed to figure out what is causing this problem. Or experiments on the board with different signal routing combinations to isolate a failing path or device.

    Regards,
    RandyP

  • Delineation errors are not real common, but these are HW recoverable.  The delineation error would have to be caused by a multiple bit error.  It happens when the SRIO peripheral receives an unaligned /SC/ or /PD/ or undefined 8b/10b code-group after synchronization has already been achieved.  What version of C6474 silicon do you have?  Advisory 1.3.3 could cause this, but it only applies to older versions.  Another possible cause is if the ENFTP setting in CFGTXn is wrong.  For the C6474, this bit must be set to 0b0.

    Regards,

    Travis

  • thank you, Travis and Randy.

    I will check the problem base on your suggestions.