• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 62 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.

BQ25619E: What could prevent charger to terminate the charge and go to charge OFF instead

Pierre Jenard
Prodigy 10 points
Part Number: BQ25619E

Tool/software:

I have a new design with a BQ25619E charging a single LiOn cell at 4.2V 

Register 0 value is 0x0A  

Register 2 value is 0xBF

Register 4 value is 0x42

When it comes near the end of charge , the charge current decrease down to about 200mA with the battery level at 4200 mV

At this time registers 8,9 and 10 gives the following values : 0x34 0x00 0x80 ... The status pin is low, so all is OK, we are in fast charge with a bit more than 200mA 

But a few seconds later the status registers will read 0x24 0x00 0x80 .... indicating that the charge is OFF ... the status pin goes high

I did not receive an INT at the moment of the change.

If I toggle the CE pin, the charger starts again in FAST charge for a few seconds then goes Charge OFF again

Here is an extract of the schematics, the voltage at input is 12V 

Could someone explain this behaviour 

  • 0
    TI__Mastermind 33605 points

    Hello,

    I cannot see any initial issues by schematic.

    Has this happened on multiple units? Do you see it on our EVM? Have you tried an ABA swap?

    Can you please report the full register read out before and after the observation?

    Regards,

    Mike Emanuel

  • 0 in reply to Michael Emanuel35
    Prodigy 10 points

    Hello,

    I have the same behaviour on 3 different prototypes, unfortunately I do not have an eval board at hand ...
    Here is part of a charge log giving in each record

    LOG,355360,3998,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75

    LOG = Type of record, may be either LOG for a regular dump each 10 seconds
    INT = A dump at an interrupt event
    +++ = A dump of only the 3 status registers (8,9 & 10) just after the INT event

    Other values are, in this order :
    A timestamp (in milliseconds)
    The battery voltage (in mV)
    The battery current (in mA , + sign is charge, - sign is discharge)
    The 12 registers of the BQ device

    I programmed the device to have a termination voltage of 4.15V (but the same arises with the default 4.2V)
    I also set a top off timer of 15 minutes (but the device never start this timer !)
    My firmware also monitors the power plug in/out event to set the IINDPM value to 1.1A instead of the 500mA default value

    The log starts with the device in FAST charge with about 1,4A of charge (I charge is 1500mA in register 2)
    I the unplug and replug the input power, so the INT sequence and the re-programming of the register 0 to a value of 0x0A
    After a while, the battery reaches 4.15 V and the charge currents decreases and then suddenly the status shows CHARGE_OFF ... without an INT event !!

    In this state, the only way to trigger a new charge cycle is to toggle the CE pin HIGH then LOW but the charge lasts only for a few seconds
    unplug/re-plug of the input power does not start a new cycle

    Any idea ???

    LOG,355360,3998,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,365361,3999,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,375363,4001,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,385365,4002,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,395367,4003,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,405368,4003,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,415370,4004,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75 <== FAST CHARGE 1431 mA @ 4V
    INT,416241,4004,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0xC0,0x44,0x75 <== Power input unplug
    +++,416243,4004,1431,0x34;0x0;0xC0
    INT,416254,4004,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x20,0x0,0x40,0x44,0x75
    +++,416256,4004,1431,0x20;0x0;0x40
    LOG,425372,3707,-153,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x0,0x0,0x0,0x44,0x75
    LOG,435373,3697,-153,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x0,0x0,0x0,0x44,0x75
    INT,438586,3697,-153,0x4,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75 <== Power input plug
    +++,438588,3697,-153,0x24;0x0;0x80
    INT,438598,3697,-153,0x4,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0xA0,0x44,0x75 <== Device in IINDPM state
    +++,438600,3697,-153,0x34;0x0;0xA0
    LOG,445375,3981,1432,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0xA0,0x44,0x75 <== Programming of IINDPM current @ 1.1A
    LOG,455377,3989,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75 <== Device exits IINDPM state
    LOG,465379,3994,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,475380,3997,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,485382,3999,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,495384,4001,1431,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75

    ..... So far all is OK ....

    .... but then reaching 4.15V ....

    LOG,6725212,4145,291,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,6735214,4145,290,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,6745216,4145,289,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,6755217,4145,288,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,6765219,4145,288,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,6775221,4145,287,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,6785222,4145,286,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,6795224,4145,285,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75
    LOG,6805226,4145,284,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x34,0x0,0x80,0x44,0x75 <== CHG STATUS is '10' (Reg 8 = 0x34)
    LOG,6815228,4145,20,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75 <== CHG STATUS go to '00' (Reg 8 = 0x24)
    LOG,6825229,4100,0,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75 <== No current IN or out of the battery
    LOG,6835231,4100,0,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75 My board is powered by the BQ charger on VSYS
    LOG,6845233,4095,0,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75 All registers keep their values
    LOG,6855234,4095,0,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75
    LOG,6865236,4093,0,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75
    LOG,6875238,4093,0,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75
    LOG,6885239,4091,0,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75
    LOG,6895241,4091,0,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75
    LOG,6905243,4091,0,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75
    LOG,6915245,4090,0,0xA,0x1A,0xBF,0x12,0x3A,0x9E,0xE6,0x4C,0x24,0x0,0x80,0x44,0x75

    BR,

    Pierre

  • 0 in reply to Pierre Jenard
    TI__Mastermind 33605 points

    Hi Pierre,

    Can you try to toggle EN_CHG and see if it terminates?

    Regards,

    Mike Emanuel

  • 0 in reply to Michael Emanuel35
    Prodigy 10 points

    I'm really confused but the problem was on the software side and not on the hardware. I have some code in the background that reads a gauge (BQ27441) and inhibits the charger when the gauge detects a full charge. Sorry for this, but this thread on the forum will not help much people. 

    BR

    Pierre