• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 63 subscribers
  • Views 671 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

BQ25895: About D+/D- detection time & flow question

Yang Ken
Intellectual 500 points
Part Number: BQ25895

Hi Sir,

The client met the same problem likes the following issue and they want to know about D+/D- detection time & flow detail, could you please help to support that?

e2e.ti.com/.../628921

Q1. What's the maximum charging port detection time?

Q2. What's each type detection period & sequential order?

Q3. Could you provide a reference FW process for use DSEL pin to control USB D+/D- switch?

Q4. Could you provide a reference FW process for use MCU's I/O pin to control USB D+/D- switch?

Q5. Is there other way to judge detection complete or not if INT can't receive by MCU?

Q6. Does it necessary delay time during read/write the registers? If yes, how long is it?

Thanks

Regards,

Ken

 

  • 0
    TI__Guru**** 167196 points

    Regarding Q1 and Q2:

    Power up to REGN ON - 220ms

    Poor Source Detection - +30ms

    1st INT PULSE - VBUS_GD @ ~250ms from power up

    USB BC1.2 (SDP/CDP/DCP) - +80ms min up to 580ms max (addt'l 500ms for Data Contact Detection if needed)

    Non Standard Adapter Detection - +500ms

    If enabled, HVDCP Detection - +1700-2200ms

    2nd INT PULSE - IINDPM register is auto set, VBUS_STAT, PG_STAT are updated @~220ms+30ms+80ms if fast BC1.2 identification to 220ms+30ms+500ms+2200ms if HVDCP detection from power up

    3rd INT pulse - Relative VINDPM is updated following VBUS @ no load measurement

    Regarding Q3, the e2e post you reference above summarizes the setup for DSEL to drive the USB switch and how to work around the CDP limitation.

    Regarding Q4, the simplest solution for the MCU I/O to control the switch would be to wait for 3 seconds after power up to remove the charger D+/D- pins from the USB lines and prevent the USB host from communicating on those lines during the same time.

    Regarding Q5, the MCU can read the VBUS_STAT and/or PG_STAT registers to confirm detection is complete.

    Regarding Q6, the charger registers are compatible with I2C up to 400kHz. 

  • 0 in reply to Jeff F
    Intellectual 500 points

    Hi Jeff,

    Thanks for you promptly and kindly support this case and detail description each questions.

    Let me check out whether there something else question by them.

    Regards,

    Ken

  • 0 in reply to Jeff F
    Intellectual 500 points

    Hi Jeff,

    The customer asked if this part has other limitations?

    Could you please share your experience as you knew?

    Thanks

    Ken