• TI Thinks Resolved

TPS65987D: extend the tSenderResponse timeou for 101 Hard_Reset issue

Prodigy 590 points

Replies: 13

Views: 233

Part Number: TPS65987D

Hi all,

   Here need your help to have the suggestion that my customer ask if we help extend the tSenderResponse timeout? Maybe from 30ms to 300ms?

   Due to my customer would like to check whether this issue can be solved by extending the tSenderResponse timeout.

   Note. 

        1. The Issue  : Checked a 0x40 register and it's report 101 timeout issue. 

        2. From my customer : Chip vendor Qualcomm checked the log and confirmed that it was due to request packet. Source did not receive the request packet within " tSenderResponse” time and send out the hard reset. My customer have tried several solutions with Qualcomm but it still cannot solve this timeout issue.

Best regards,

Albert Lee.

  • Hi Albert,

    The TPS65987D is PD compliant and follows the specification for these timings. Unfortunately, these timings cannot be modified as it would cause compliance issues with the TPS65987D. I would suggest working with the customer to ensure their attached device can respond to the Source Capabilities message in the spec allotted time.

    Thank you,
    Eric

  • In reply to Eric Beljaars:

    Hi Eric,

       Thanks your replying and understood this one. Because of my customer will use TPS65987D to interface with QCOM chipset built-in their  products and customize TPS65987D code to meet their HW design. That means they want us don’t need to consider to meet PD compliant in their application.

      They did need us to support this TPS65987D FW customization request. Due to in currently, their set will run into problem if TI don’t support this FW change request in TPS65987D code, they can’t deliver product due to the issue. Could we support it?

     

    Best regards,

    Albert Lee.

  • In reply to user4782171:

    Hi Albert,

    Does the customer have an I2C master in their system controlling the TPS65987D? If that's the case, we can come up with a workaround that might work for them. Please let me know.

    Thank you,
    Eric

  • In reply to Eric Beljaars:

    Hi Eric,

       Yes and thanks. They have it checked with the RD. Please help to share the detail workaround proposals & method to us. We need to have a update to my customer in early of next Monday.

    Best regards,

    Albert Lee.

     

  • In reply to user4782171:

    Hi Albert,

    I am checking with the team on this and will get back to you as soon as possible.

    Thanks,

    Eric

  • In reply to Eric Beljaars:

    Hi Albert,

    I spoke with the team on this item. We can't support custom firmware for this. However, if you provide PD logs and more details on the issue then we can suggest if the customer can do MCU based workaround for this item.

    Thanks,

    Eric

  • In reply to Eric Beljaars:

    Hi Eric,

      Thanks your replying. I can't catch what you need for the workaround proposal. Would provide more description and items you needed  or we can have a con-call with customer FW team for this one?

    Best regards,

    Albert Lee.

  • In reply to user4782171:

    Hi Albert,

    If you can provide PD logs of the timing you want to be changed, that will be helpful. However, it sounds like you are asking for a PD behavioral change which we can NOT support. There will be no MCU workaround for a PD behavioral change either. Custom FW is not supported by TPS65987D.

    Thanks,
    Eric

  • In reply to user4782171:

    Hi Eric,

        Need your help for this one : To provide more specific & description and items you needed?

    Best regards,

    Albert Lee.

  • In reply to user4782171:

    Albert,

    Like I said in my last two posts, we need PD Logs to determine what it is you are asking to change.

    However, as I said, from your previous description, this does not sound like something that can be changed with an MCU. This cannot be supported by TPS65987D.

    Eric