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.

TPS2547: Evaluate the different settings' influence on daily application

Part Number: TPS2547

Hi team,

My customer is planning to change the BC1.2 Charger Setting on different system status and would like to know if it will cause some limitation or other difference in end-customer daily use.

Mode selection table to use:

CTL1 CTL2 CTL3 ILIM_SEL
CDP 0 1 1 1
DCP_Auto 1 1 1 1

Current setting:

States

Charge Mode

S0

CDP Mode

S3/S4/S5

DCP_auto Mode

 Target setting:

States

Charge Mode

S0/S3

CDP Mode

S4/S5

DCP_auto Mode

It is a workaround to fix other issue and need your kindly help to reply soon.

In my point of view there should be no difference since data line will not be available under S3 also. While there will be no discharge on Vbus, will this influence device recognization when system recover to S0?

Thanks

Max

  • Hi Max,

    I am not sure what you mean by moving from S3/S4/S5 to S4/S5. Can you please define the states by using their CTL pin inputs?

    0111 corresponds to DCP_Auto which correlates to S3. 

    1111 corresponds to CDP which correlates to S0. 

    I am also not sure what issue you are encountering.

    Thanks,

    Emma

  • Hi Emma,

    It is still the auto-wakeup issue we discussed earlier. Customer find that it is USB3 signal related and the issue should disappear if they keep the CDP (0111) setting for both S0 and S3. (previously they set CDP 0111 in S0 and 1111DCP_Auto in S3/S4/S5).

    It will means that the CTL and ILIM pins keep at 0111 during the transition from S0 to S3 when the issue happens, thus no discharge on vbus or re-communication will happen. And it could solve the abnormally wake-up issue.

    And the concern from customer is they are changing the configuration from 1111 DCP_Auto mode in S3 into the 0111CDP mode configuration and they want to know any different behavior let by this change. Especially if end customer will find some difference between a CDP and DCP_Auto port in S3.

    Do you get my idea?

    Thanks

    Max

  • Ah,

    I'm sorry. I mismatched the 1111 and 0111...

    It is still the auto-wakeup issue we discussed earlier. Customer find that it is USB3 signal related and the issue should disappear if they keep the CDP (1111) setting for both S0 and S3. (previously they set CDP 1111 in S0 and 0111DCP_Auto in S3/S4/S5).

    It will means that the CTL and ILIM pins keep at 1111 during the transition from S0 to S3 when the issue happens, thus no discharge on vbus or re-communication will happen. And it could solve the abnormally wake-up issue.

    And the concern from customer is they are changing the configuration from 0111 DCP_Auto mode in S3 into the 1111CDP mode configuration and they want to know any different behavior let by this change. Especially if end customer will find some difference between a CDP and DCP_Auto port in S3.

    Do you get my idea?

    Thanks

    Max

  • Hi Max,

    The main difference between CDP and DCP_auto is that CDP leaves the datalines connected and has a maximum charging current of 1.5A. DCP_auto can cycle through different DCP modes and offer more charging current, but does not have the datalines (DP/DM) connected.

    Thanks,

    Emma

  • Hi Emma,

    Thanks for your explanation. 

    Just one more item to double check with you. If we keep the CDP mode all the time, the data line will actually be idle in S3, will it influence the USB device re-recognition when turning back to S0? Or if a Vbus discharge is a must for the USB device recognition?

    Thanks

    Max

  • Hi Max,

    If you are keeping the CTL inputs the same, then the TPS2547 will not see any difference between the system's S3 and S0. Therefore the USB devices will be recognized normally. 

    The TPS2547 uses a VBUS discharge during mode change (prompted by the CTL inputs), not during device connection or disconnection. Please check out Figure 38. TPS2547 Charging States in the datasheet to see the process of VBUS discharge. 

    Thanks,

    Emma