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.

TUSB216-Q1: Android auto disconnect issue

Part Number: TUSB216-Q1
Other Parts Discussed in Thread: TUSB211, TUSB216

Dear TI experts,

My customer changed USB redriver from TUSB211 to TUSB216 due to apple carplay disconnect issue about 1 year ago.

This time they have a problem with Android auto.

old android phone seems okay, but new phone (Samsung Galaxy S21 and newer - S22, S23 series) have disconnect issue while using.

They checked eye diagram, and they saw that newer phones have higher DC voltage level. (about 500mV or more)

old android phones and iphones have lower DC voltage level. (about 400~450mV)

Did you have any silmilar issues to other customers? and how can we fix it?

I have a measured eye diagram but it is confidential. I can send it to you if you want. (please send me the friendship request.)

Please check this issue. Thanks.

Best regards,

Chase

  • Hi Chase,

    If possible, yes, I would appreciate it if you could send over those eye diagrams, as well as a schematic if possible to see what their settings are at.

    If they are only seeing this issue in the newer android phones and there is a noticeable difference in the DC voltage being provided, then my initial belief is that they are exceeding the max voltage threshold of USB2 HS connections, so depending on what their current settings are, one way to resolve this would be to lower the value of BOOST and/or RX_SEN to a lower level.

    Please let me know me when you can send over those eyes.

    Thanks,

    Ryan

  • Hi Chase,

    Replying to your E2E DM here for team visibility:

    Just confirming, you tested at EQ0 and saw the same issues at every level, correct?

    If you hold the redriver in reset, is the issue still present, or does the issue disappear? Does adding a cable longer than 2M help reduce this issue, I.E 5M.

    Looking at the eye you sent, it seems like the DC level of the eye is either at or exceeding the disconnect threshold, prompting the HS connection to be terminated. 

    Please let me know.

    Thanks,

    Ryan

  • Dear Ryan,

    Thank you for your support.

    Just confirming, you tested at EQ0 and saw the same issues at every level, correct?

    -> YES.

    If you hold the redriver in reset, is the issue still present, or does the issue disappear? Does adding a cable longer than 2M help reduce this issue, I.E 5M.

    -> I will ask these 2 question to customer, and reply to you asap.

    I sent additional information through private message. Please check it.

    Best regards,

    Chase

  • Hi Chase,

    Looking at the schematic, just to confirm, NA indicated not applicable or floating, correct? If so, then that would align with RX_SEN being floating. Otherwise, I see nothing else of immediate note. 

    Please let me know what the customer sees on their end once testing is complete. 

    Thanks,

    Ryan

  • Dear Ryan,

    Thank you for your support.

    As you said, RX_SEN is floating so the setting is medium RX sensitivity.

    I also asked to test changing RX sensitivity to low, I will tell you the results asap.

    Best regards,

    Chase

  • Hi Chase,

    Sounds good. I appreciate it.

    Thanks,

    Ryan

  • Dear Ryan,

    I have 2 questions from customer.

    1. Did you have any similar issues from other customer? (Android auto disconnect issue)

    2. Do you have any solution to decrease DC level using other ICs or circuits?

    Best regards,

    Chase

  • Hi Chase,

    Ryan is out today so I am helping to support.  One question that may have been answered through DM that is important:

    "If you hold the redriver in reset, is the issue still present?" - What was the answer to this?  

    1. Did you have any similar issues from other customer? (Android auto disconnect issue)
    Not that I am aware of. 

    2. Do you have any solution to decrease DC level using other ICs or circuits?
    I will need to follow-up with external component recommendations if this is needed; however, I think we should confirm if the issue is solvable through the TUSB216 or a FW change before changing the hardware.  Does the issue still occur with the TUSB216 is in reset?

    Regards,

    Nicholaus