• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 103 subscribers
  • Views 1180 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 srcTID/targetTID fields - TMS320C6472

Marton Feher
Prodigy 70 points
Other Parts Discussed in Thread: TMS320C6472

Hi All,

I have trouble finding information what value the srcTID/targetTID fields will be set for SRIO packets sent by the DSP.
I have checked the following documents so far: "TMS320C6472/TMS320TCI648x DSP Serial RapidIO (SRIO) User's Guide" and "TMS320C6472 Chip Support Library API Reference Guide"

Page 37 of the SRIO user gide states: “Some fields, such as the RapidIO srcTID/targetTID field, are assigned by hardware and do not have a corresponding command register field”, which implies this might be a random number assigned by hardware.

I can also only assume that targetTID will take the value of the corresponding request packet’s source transaction ID, but haven't found any confirmation on that either.

I'm happy to dig further if pointed to the right direction, but a direct answer is also more than welcome. Thanks in advance,

Marton

  • 0
    TI__Guru* 81335 points

    Hi Marton,

    Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages (for processor issues). Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics (e2e.ti.com).

    We will get back to you on the above query shortly. Thank you for your patience.

  • 0
    TI__Mastermind 28085 points
    Hi,

    Yes, RapidIO srcTID/targetTID field, are assigned by hardware and do not have a corresponding command register field. Refer Figure 2-11 Example Burst NWRITE_R on SRIO user guide to understand the flow.

    Each LSU can support up to 16 SRCTIDs. Thus LSU0 can generate transactions with SRCTID 0-15, LSU1 from SRCTIDs 16-31 and so on. Every time a new command is started from an LSU, it starts back at the starting SRCTID. Thus for LSU1, every new command will start at 16.

    The targetTID field of the packet is examined to determine which core and corresponding set of registers are waiting for the response. Remember, there can be only one outstanding request per core.

    Thanks,
  • 0 in reply to Ganapathi Dhandapani95
    Prodigy 70 points
    Hi Ganapathi,

    Thanks for your answer, it basically answers my question to almost all extent.
    How is the tragetTID generated in response packets sent from the DSP? Am I right thinking that it will match the associated request srcTID?

    Can I also ask you to point me to the documentation containing this information in detail?
    Thank you in advance, best regards,

    Marton
  • 0 in reply to Marton Feher
    Prodigy 70 points

    Hi Ganapathi,

    I've found the source where you take the answer from:
    http://www.ti.com/lit/ug/sprugw1b/sprugw1b.pdf

    I will accept the answer now.

    Can you answer this very last question for me please?

    "How is the tragetTID generated in response packets sent from the DSP? Am I right thinking that it will match the associated request srcTID? (As per SRIO standard definition)"

    Best regards,

    Marton