• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 62 subscribers
  • Views 333 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

BQ24032A: Field defect lock-up

CHO SR
Genius 3335 points
Part Number: BQ24032A
Other Parts Discussed in Thread: BQ51020

Hi,

The customer is using the BQ24032A for a Portable 7-inch display product.

System reset and lockup failure occurred during wireless charging, and Log check shows excessive connected/disconnected.

It is reproduced in wireless charging. (charging method uses wireless & USB charging.)

Waveform checked whenever Interrupt occurs in WAKE_IRQ pin.

3CH(Purple): WAKE_IRQ, 1CH(Yellow): DC_IN

It is confirmed that the system is reset or locked up due to excessive Charger Connected/Disconnected occurrence.

Please advise what causes this problem to occur.

  • 0
    TI__Mastermind 23220 points

    Hi Cho,

    Would you be able to share what the battery voltage is at this time? Are you also able to measure the max input current when this occurs?

    Best Regards,

    Anthony Pham

  • 0 in reply to Anthony P Pham
    Genius 3335 points

    Hi Anthony,

    Battery voltage: 4.2V

    Max input current : 1A

    Wireless charger spec : 

    Wireless Receiver : BQ51020

    System Load : BQ24032

  • 0 in reply to CHO SR
    TI__Mastermind 23220 points

    Hi Cho,

    This looks like the device entering and exiting sleep mode. Can you share a plot of VIN and VBAT?

    Best Regards,

    Anthony Pham

  • 0 in reply to Anthony P Pham
    Genius 3335 points

    Hi Anthony,

    Sorry, I'm late because it's hard to reproduce the current situation.

    There is no waveform because the phenomenon has not yet been reproduced.

    Instead, created a block diagram.

    block diagram_230616.pptx

  • 0 in reply to CHO SR
    TI__Mastermind 23220 points

    Hi Cho,

    Appreciate the block diagram. Let me know when the behavior can be duplicated. 

    Best Regards,

    Anthony Pham

  • 0 in reply to Anthony P Pham
    Genius 3335 points

    Hi Anthony,

    The customer is expecting about 2-3 weeks.

    I'm sorry, but please guide me on the conditions to enter and exit sleep mode on the block diagram.

    I think it will help reduce the time to reproduce the phenomenon.

  • 0 in reply to CHO SR
    TI__Mastermind 23220 points

    Hi Cho,

    Increasing the VIN slowly from below VBAT to VBAT + 300 mV you will see the device switch VOUT from VBAT to VIN power. This is based on the V_SLPENT threshold. The exit threshold is VSLPEXIT. 

    Let me know if there are any questions. 

    Best Regards,

    Anthony Pham

  • 0 in reply to Anthony P Pham
    Genius 3335 points

    Hi Anthony,

    The customer recreated a similar phenomenon.

    Please refer to the report.

    Customer Report_230620(R00).pptx

    Interrupts occur, but no system reboot & locks-up occur.

    Please advise what else we should check.

  • 0 in reply to CHO SR
    TI__Mastermind 23220 points

    Cho,

    Sleep mode can happen if there are fluctuations in the input and it's unable to charge the battery. It's recommended to ensure that the device does not enter sleep mode to prevent these interrupts and to allow the device to charge. You can try and disable charge and see if this behavior improves. 

    Best Regards,

    Anthony Pham

  • 0 in reply to Anthony P Pham
    Genius 3335 points

    Anthony,

    Thank you. Please reply to the customer's question.

    Q1. How can I force myself to stop entering sleep mode?

    Q2. How can I force myself to escape if already in sleep mode?

    Q3. Why does WAKE_IRQ (pin 18) occur every 50uS in sleep mode?

  • +1 in reply to CHO SR
    TI__Mastermind 23220 points

    Hi Cho,

    CHO SR said:
    Q1. How can I force myself to stop entering sleep mode?

    Ensure that the DC_IN voltage is higher than VBAT + VSLP_ENT.

    In some cases, this may be due to an overload on the input that is intense that regulation loops such as VINDPM or DPPM are not enough to prevent it. Based on that, one item you can try is lowering the charge current.

    CHO SR said:
    Q2. How can I force myself to escape if already in sleep mode?

    Increase DC_IN voltage above VBAT + VSLP_ENT. There is no way to bypass this as this is the charger determining it has an input but not one that is sufficient for charging. 

    What can be done to combat it is to reduce charge or disable charge based on the interrupts. If there are interrupts, reduction in current is needed until /ACPG is low. 

    The other option is to disable charge and then re-enable charge periodically and monitor the interrupts. If the /ACPG is still going to behave as shown, the input is not technically capable of charging. Can only fully charge when there is no interrupt on the /ACPG pin (which is the WAKE_IRQ). 

    CHO SR said:
    Q3. Why does WAKE_IRQ (pin 18) occur every 50uS in sleep mode?

    It is not that the device is providing an interrupt every 50uS due to sleep mode. The device is providing an interrupt every time it changes states because it is constantly entering and exiting sleep mode. The /ACPG pin will be low when it exits sleep mode and will be open-drain in sleep mode. So each time it is seen going HIGH, it is entering sleep mode. When in sleep mode, the DC_IN voltage can most likely be less loaded and so it increases just enough so that it exits sleep mode. When it exits sleep mode, it becomes more loaded to the point that it enters sleep mode again, creating a cycle of entering and exiting sleep mode. 

    Based on the waveform provided, the period of DC_IN being lower than the battery is about every 40-50us. 

    Best Regards,

    Anthony Pham