• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 65 subscribers
  • Views 482 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.

BQ27500-V130 is getting disabled

Jay Fayer
Prodigy 10 points
Other Parts Discussed in Thread: BQ27500-V130, BQ27500, BQ27500-V120

We're just beginning production on a product we've design the BQ27500-V130 into. And we're modifying the upper battery temperature limit in-circuit using the EV2300 and your development software. But this process is somehow disabling about 20-30% of the chips. Our board vendor replaces the 'bad' chip and the board's okay again.

Help.

  • 0
    TI__Intellectual 2100 points

    Jay,

    When you say that it is "disabling the chips," does this mean that they are not communicating at all? 

    How are you programming the upper temperature limit?  Are you updating the flash image by going into ROM mode or are you just using firmware commands to pick the specific values to update?

    Thanks,

    Charles

  • 0 in reply to Charles Herder
    Prodigy 10 points

    Charles,

    Let me continue for Jay.......  We program the BQ27500 device using the Evaluation Software, going into Data Flash, importing a .gg file, and then using Write_All / Preserve.  We do not seal the chip. 

    On the chips that do not work after programming, they read all batteries as being 100% charged, but with 0 capacity; and the BAT_GD line oscillates about every 2 seconds.  We verified that the circuit for the thermistor is correct, and replacing the BQ27500 chip on a "failed" board will solve the issue.  We attempted to re-program some failed chips, but it is not possible, although they do communicate.  Are we damaging the chip or is the programming corrupting some data?

    Thanks,

    Ignacio

  • 0 in reply to Ignacio Michel
    TI__Intellectual 2100 points

    Ignacio,

    If the gauge is reading 100% and 0 capacity, I would check the status flags to see if BAT_DET is set (red).  If it is cleared (green), then the gauge doesn't see the battery as connected, and the gauge will not report correct values.

    Thanks,

    Charles

  • 0 in reply to Ignacio Michel
    TI__Genius 14985 points

    Let me also add another thing to check.  Please confirm that the ICs you are updating have the same firmware version as the EVSW and GG file that you are using.  You could theoretically be writing to some wrong dataflash locations if the ICs were actually bq27500-V120, for example, but you are using the software and GG file for bq27500-V130.  Make sure your vendor is only ordering bq27500-V130, or else has upgraded older material to that version.