• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 388 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

C6474 sRIO Error Info Questions

TommySong
Genius 9520 points

There is a sRIO failure case that has below error info:

  1. Logical/Transport Layer Error Detect CSR register (offset 2008) value: 0x01800000. That indicates there are PKT_RSPNS_TIMEOUT and UNSOLICITED_RSPNS.
  2. Port 0 Error Detect CSR register (offset 2040) value: 0x80500005. That indicates there are ERR_IMP_SPECIFIC, CORRUPT_CNTL_SYM, RCVD_PKT_NOT_ACCPT, DELINEATION_ERROR and LINK_TIMEOUT errors.

I want to know what UNSOLICITED_RSPNS and ERR_IMP_SPECIFIC mean.  

Thank you very much.

  • 0
    TI__Mastermind 23525 points

    1.  Unsolicited responses occur when a response is received by a device that doesn't expect it. Each transmitted message request or non-posted directIO packet is saved in a scoreboard system. The scoreboard monitors and checks off the individual response packets for each request packet. In all practicality random unsolicited responses do not happen since a device isn't going to send a message response unless it received a message request packet. So, in order for a response to be considered unsolicited, the scoreboard entries have been deleted. There are two scenarios where the scoreboard can be deleted after a request has been sent, but before receiving the response. First, if a request message segment fails to get outbound credit, the TX descriptor is completed with a CC= 7 and scoreboard is erased. Second, if a response timeout occurs the TX descriptor or LSU is completed with a CC=3 or 1 respectively and scoreboard is erased.
     
     
    2.  See below ERR_IMP_SPECIFIC bit description from the user's guide.

    This bit covers errors that are a result of

    an illegal field in a maintenance packet, an illegal destination ID, an

    unsupported transaction, and an ingress UDI timeout condition.

    Here, an illegal field in the maintenance packet is basically the

    maintenance packet having ttypes that are reserved for maintenance

    packets. An illegal destination ID is a destination ID that is not

    supported. Unsupported transactions are transactions with a ttype that

    is reserved.

     
    Also if  there is an ingress UDI timeout, then the bit 26 of the SPn_ERR_STAT in addition to the ERR_IMP_SPECIFIC bit here.  That will help you determine if that is the reason.

    "For ingress traffic, if there is congestion at the UDI which prevents the a

    packet from being passed from the RX physical layer to the logical layer

    within 2^15 SRIO_CLK cycles, the OUTPUT_PKT_DROP bit is set. In this

    case, the ERR_IMP_SPECIFIC bit of the Port Error Detect CSR n is also

    set to indicate this condition. No ingress or egress packets are dropped

    under this scenario."

     

    Regards,

    Travis