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.

TMS320C6678: SRIO Interrupt Timing for posted WRITE operations

Part Number: TMS320C6678

For posted WRITE operations (e.g. NWRITE and SWRITE transactions) that do not require a RapidIO response packet, I would like to know more about when the peripheral sets the completion code status register and appropriate interrupt bit of the ICSR. It is described as follows in the User's Guide (SPRUGW1B).

Serial RapidIO (SRIO) for KeyStone Devices User's Guide (Rev. B)
http://www.ti.com/lit/ug/sprugw1b/sprugw1b.pdf
2.3.2.2.1 WRITE Transactions (Page 61)

"For posted WRITE operations that do not require a RapidIO response packet, a core
 may submit multiple outstanding requests. For instance, a single core may have many
 streaming write packets buffered at any given time, given out-going resources. In this
 application, the LSU can be released to the shadow registers as soon as the packet is
 written into the shared TX buffer pool. If the request has been flow controlled, the
 peripheral will set the completion code status register and appropriate interrupt bit of
 the ICSR. The control/command registers can be released after the interrupt service
 routine completes."

In the transaction that spans multiple packets, when the peripheral sets the completion code status register and appropriate interrupt bit of the ICSR, has the acknowledge control symbol for the last packet been received? Or has only the acknowledge control symbol for the first packet been received?

Best regards,

Daisuke

  • Hi Daisuke,

    The team is notified. They will post their feedback directly here.

    BR
    Tsvetolin Shulev
  • Hi Daisuke,

    I could not find the detail in SRIO spec 2.2 that Keystone SRIO IP complies with but the following info in spec 3.1 section 6.6.2 "Acknowledgment Identifier" may help ( )

    When transmitting control symbols, devices operating with Control Symbol

    24 or Control Symbol 48 shall support a default configuration in which they send

    one Packet Accepted control symbol for each received packet. Devices operating

    with Control Symbol 24 or Control Symbol 48 may optionally support a

    configuration in which they may transmit one Packet Accepted control symbol for

    multiple received packets. Devices operating with Control Symbol 64 may transmit

    one Packet Accepted control symbol for multiple received packets.

    When the peripheral sets the completion code status register and appropriate interrupt bit of the ICSR, the acknowledge control symbol received appears to be from the last packet.

    Regards, Garrett

  • Hi-Garrett-san,

    Thank you for your reply.

    Our customer measured for NWRITE operations the internal interrupt timing on the C6678 side and the interrupt timing on the destination device side. They are shown less than 20usec on the the C6678 side and approximately 400usec on the destination device side. C6678 seems to not wait receiving the acknowledge control symbol for the last packet.

    I think the detail of the SRIO spec that you shows are not supported by the SRIO spec 2.2 or earlier.

    Best regards,

    Daisuke

  • Hi Garrett-san,

    I have a new question for posted WRITE operations here: http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/667261

    Our customer may be incorrect in how to use SRIO for posted WRITE operations.

    Best regards,

    Daisuke

  • Hi Daisuke,

    Ok, we can discuss the new question in that thread. I am closing this.

    Regards,
    Garrett
  • Hi Garrett-san

    Thank you for your reply.

    Please close this.

    Best regards,

    Daisuke