• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 99 subscribers
  • Views 571 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.

C6678 - SRIO Multicast response checking

one and zero
Mastermind 18256 points


Hi Champs,

I have a question with regards to Multicast response checking (Doorbell) on the C6678.

It seems that DSP and FPGA IP bhave differently, which causes an issue. Here's the scenario. The DSP is sending a multicast doorbell to the FPGA. The FPGA is sending back the response but it's not accepted by the DSP. The reason seems because the FPGA IP is not swapping SourceID and DestID (as defined in SRIO standard). Instead it's filling in it's own ID into SourceID. This means we're seeing a response timeout on the DSP.

The question is: Can we disable SourceID checking on the Doorbell response in the DSP? I believe checking DestID and TransactionID would be sufficient according to the SRIO standard.

Kind regards,

one and zero

  • 0
    TI__Mastermind 23525 points

    Why is the DSP not just using the FPGA's deviceID for the DESTID sending the doorbell request?  That would fix the problem.  Also, it is not legal to send a packet type (including doorbell) to a multicast ID because then there would be multiple responses back to the DSP, which it can not handle. 

    To answer your question though, no, you can't disable the SourceID checking on the doorbell response.  The LSU hardware tracks this info and it can't be disabled.  So besides the timeout you see for the expected response, you will also find that you are getting a logical/transport error for unsolicited response for the doorbell response with the wrong sourceID.

    Regards,

    Travis