• State Resolved
  • Replies 4 replies
  • Subscribers 63 subscribers
  • Views 69 views
  • Users 0 members are here
Support feedback
Options
Options
Related

BQ25672: VBUS_STAT on using 12V custom adapter

Vasyl Vorobei
Intellectual 470 points
Part Number: BQ25672

Tool/software:

Hi.

We're using the simplest input scheme for the PMIC, with a 12V input source, and IINLIM=2.5 A:

The actual result we observe is that after connecting the source, the PMIC returns "Not qualified adaptor" state.

Is it an expected behavior? The "not qualified adaptor" message is a bit confusing here; one would expect to receive "unknown adaptor" or "non-standard adaptor".

Regards, Vasyl.

  • 0
    TI__Expert 6315 points

    Hi Vasyl,

    Are you using the D+/D- pins? VBUS stat is set from the D+/D- detection.

    Is the current limit being set too low for the application because of this?

    Best regards,
    Michael

  • 0 in reply to Michael Bradbourne
    Intellectual 470 points

    Hi Michael.

    We're not using D+/D- pins, and we're setting AUTO_INDET=0 at startup.

    We're setting IINLIM=2.5 A, which in our case yields 30 W, covering the maximum peak consumption with a good margin. The average consumption from SYS is significantly lower, approximately 0.3 A without charging and 1.2 A with a charger.

    Additionally, we didn't observe that DPM active statuses changed after detection, which also suggests that the current limit is sufficient. I can provide the register values if it'll help.

    BR, Vasyl.

  • 0 in reply to Vasyl Vorobei
    TI__Expert 6315 points

    Hi Vasyl,

    TI is on a US holiday. I think that the "not qualified adaptor" message is because there is no D+/D- detection. I will look into this further tomorrow.

    Best regards,
    Michael

  • +1 in reply to Michael Bradbourne
    TI__Expert 6315 points

    Hi Vasyl,

    It seems like the not qualified adaptor message is the default state of the register before D+/D- detection. Setting AUTO_INDET = 0 at startup will not allow the D+/D- detection which is why that message appears.

    Best regards,
    Michael Bradbourne