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.

TPS2546: TPS2546 can not charge to IPHONEX when phone's screen was locked

Part Number: TPS2546

Hi Team:

We configured TPS2546 as CDP in notebook system, when plug IphoneX into this charging port, notice that Iphone X can’t be charged if phone's screen was locked, while can be charged if phones's screen was unlocked.

We have tested this with iPhone7 whiledidn’t see such this issue.

 

Have you ever seen such issue in other application? please kindly advise possible causes of this issue

 

 

Screen Locked

Screen Unlocked

Smart phone Product

Iphone 7

Iphone X

IPhone7

Iphone X

Charging status

Pass

Fail(cannot charge)

Pass

Pass

  • I have not seen this particular issue before.

    Can you get a capture of the D_/D- and VBUS lines in both test cases and tell me the CTRL and ILIM configuration of the TPS2546?

    I cannot determine if the issue is with the Iphone or the TPS2546 without being able to see the communication between them.

    Regards,
    Chuck
  • Hi Chuck:

    Thanks for the help

    I attached the capture of D+/D- VBUS when Iphone X plug in, which have clarified that CDP detection have been completed, and charging have been established

    but, looks something goes wrong on D+/D- communication line, during this period, there is no state change on CTRL and ILIM

    Can you tell what is the cause of this issue?

    I can recall that, after the BC1.2 advertising, our TPS2546 would no longer occupy the USB2.0 data line and return it baack to USB TX/RX, but could you kindly share with me here what is the sequence for this? will our TPS2546 impact USB2.0 communication? if yes, how

    thanks and regards

    iphoneX (4).tif

  • The TPS2546 is not impacting the communication in any way in this capture. It shows a correct CDP negotiation on constant current and voltage availability and no impact to the data lines.

    Based on this capture, it is no the TPS2546 that is causing this issue.