TPS65987D: Some questions

Part Number: TPS65987D

Tool/software:

Hi team,

  • Is there a way to ensure Source Capabilities are sent even after a hard reset?
    Once a hard reset occurs, Source Capabilities are not sent, preventing charging and communication from resuming. (HT4P_A9Plus Restart_20250826)

  • With the following settings, communication with the iPad will be disabled. (Charging will still work.)
    Other tablets (such as Galaxy or Surface) can charge and communicate without any issues.
    Setting either option prevents the iPad from communicating.
    1. Disable the modal operation port [34] at address 0x47
    2. Disable the display port SVID [0] at register 0x51
    Are there any possible causes?

Best Regards,
Ryu.

  • Hi Ryu,

    Thanks for reaching out on E2E!

    Is there a way to ensure Source Capabilities are sent even after a hard reset?
    Once a hard reset occurs, Source Capabilities are not sent, preventing charging and communication from resuming. (HT4P_A9Plus Restart_20250826)

    Do you have a PD log of this case? We should always see us send source cap messages after a hard reset if we connect as a source. If your device is a DRP, there could be a chance you are connecting as a SINK.

    With the following settings, communication with the iPad will be disabled. (Charging will still work.)
    Other tablets (such as Galaxy or Surface) can charge and communicate without any issues.
    Setting either option prevents the iPad from communicating.
    1. Disable the modal operation port [34] at address 0x47
    2. Disable the display port SVID [0] at register 0x51
    Are there any possible causes?

    Does your product support ALT modes? Looks like the IPAD is entering DP alt mode. Removing those bits will cause the iPad to not enter any alternate modes and my assumption is that it would only work in USB2/USB3. Can you send me a PD log of the ipad connection and the samsung tablet?

    Thank you,

    Kevin

  • Hi Kevin,

    Thank you for your reply.

    Do you have a PD log of this case? We should always see us send source cap messages after a hard reset if we connect as a source. If your device is a DRP, there could be a chance you are connecting as a SINK.

    I switched from DRP to DFP, but it had no effect.


    The log file could not be attached to the thread.
    I would like to contact you via private message or email.

    Best Regards,
    Ryu.

  • Hi Ryu,

    I am out of office until Wednesday please feel free to private message me the log file!

    thank you,

    Kevin

  • Hi Kevin,

    Thank you for your reply.
    Please allow friend requests to send private messages.

    Best Regards,
    Ryu.

  • Hi Ryu,

    Will send now!

    Thank you,

    Kevin

  • Hi Ryu,

    Thanks for the logs. I took a look and it does look like we are sending source caps after a hard reset. For a soft reset, we are not which is expected. This is because we are rejecting VCONN swaps since we are switching data roles. Can you try the following PJT file where I went ahead and enabled VCONN swaps?

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/Galaxy-A9Plus-Restart_5F00_V100.wmc

    Thank you,

    Kevin

  • Hi Kevin,

    Thank you for your reply.
    I'll try the project file too.
    One thing I'd like to ask.
    Line 165 of the log ends with a hard reset, and it appears the source cap was not transmitted.
    What are your thoughts on this?

    The issue is that after sending and retrying Source Capabilities 150 times (approximately 10 seconds), a hard reset is issued and the process stops.
    Please advise if any of the following methods are possible:
    1. Can the 150-retry cycle be restarted?
    2. Can the 150-retry interval (approximately 10 seconds) be extended to 20 seconds or longer?
    3. Are there any other countermeasure plans?

    Best Regards,
    Ryu.

  • Hi Ryu,

    For Non-PD devices we will send multiple source caps until the far end responds followed by a hard reset. I am not sure if we can resend that burst without a disconnect, but if you have an external EC attached to the system you can issue a send source cap command, or you can emulate a disconnect by sending the DISC 4CC command in the TRM.

    Please let me know of the latest results!

    Thank you,

    Kevin

  • Hi Kevin,

    Thank you for your reply.
    Does this mean I need to process it externally to resend after a hard reset?
    I want to send again after a hard reset following multiple transmissions.
    Is there no way to do that?

    2. Can the 150-retry interval (approximately 10 seconds) be extended to 20 seconds or longer?

    Please also tell me whether this is possible or not.

    Changing the VCON settings had no effect.

    Best Regards,
    Ryu.

  • Hi Ryu,

    Thanks for the update!

    Give me a day to take a look at this.

    Thank you,

    Kevin

  • Hi Kevin,

    May I have your reply?

    Best Regards,
    Ryu.