• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 64 subscribers
  • Views 543 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.

BQ34Z100-G1: Chip bricks after using "bqStudio"

Pranjal Joshi
Prodigy 40 points
Part Number: BQ34Z100-G1
Other Parts Discussed in Thread: BQ34Z100, BQSTUDIO, EV2400

Hello,

I am using BQ34Z100-G1 along with AVR processor for gauging 16S8P Li-Ion battery.

when I solder a new chip on my PCB, everything works fine. AVR is able to read the default data from BQ34Z100 over I2C.

But as soon as I set the following parameters using BQStudio (Batter Management Studio - version 1.3.101) and EV2300 (3.1c), the device bricks!! Both BQstudio and AVR controller can't find the device on I2C bus!

  • Number of series cell = 16
  • VOLTSEL = 1
  • TEMPS = 0
  • Write All to flash
  • RESET command
  • Calibration tab - voltage calibration (Here I got an error: voltage is not in a specified range. the range given is in millivolts.

After getting this calibration error, the device just bricks!! I lost 3 ICs just like this.

Similarly, when I try to flash the golden file generated earlier (.srec) using the programming tab, the device goes into the same bricked state and stops responding over I2C.

Please provide a way to re-flash the device or bring them back into "alive" state!

Notice that I am using 16.5k and 1.2M resistors to divide voltage across BAT pin, But when device is in bricked state, value measured accross 16.5K resistor is coming like 1.3k, 240 Ohm for these bricked chips!

  • 0
    TI__Guru** 105590 points

    Hello Pranjal,

    For the bq34z100-g1 it's recommended to use the EV2400, the EV2300 is no longer supported.

    Can you share your .gg file and schematic for reference? Do you you see this error with an EVM board testing?

    Depending on the voltage on the input pins if you change VOLTSEL and the min flash voltage becomes higher than the voltage measured, the gauge will not allow for DF updates.

    If the gauges were damaged, then there may not be a way to recover the gauges.

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Prodigy 40 points

    Here is the reference schematic.

    GND is VBAT- for the following schematic as per the TI conventions.

    Please provide details for obtaining the .gg files.

    Also, is there any way to validate whether the gauge is damaged or not? I checked REG25 pin of the unresponsive ICs and it provides 2.5V, but the SDA & SCL line voltages appear around 1.5V even though a 4.7K pull-up resistor is connected which is strange. (My VDD is 3.3V)

  • 0 in reply to Pranjal Joshi
    TI__Guru** 105590 points

    Hello Pranjal,

    The .gg is exported from bqStudio in the data memory tab.

    Are there any other devices on the comm lines? I may try increasing the pull-up resistor to 10K. Was the voltage 1.5V on the bricked board?

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Prodigy 40 points

    I have flashed the SLUC580.ZIP (4170 KB) firmware to the fresh gauge IC.

    Please find the attached .gg file.

    FuelGauge.gg.csv

    Here are some screenshots to illustrate the problem:

    1. When the Data Memory tab is open or Read All is pressed, a Similar error appears 3-5 times but then the device gets read in the subsequent attempt.

    2. Error occurred while performing voltage calibration. This error doesn't go away even after multiple attempts.

  • 0 in reply to Pranjal Joshi
    TI__Guru** 105590 points

    Hello Pranjal,

    Are there any other devices on the comm lines?

    I think this is related to something on the bus, can you capture any of the transmissions using a scope or logic analyzer?

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Prodigy 40 points

    Yes! There is an AVR microcontroller present on the I2C bus, but the micro is in sleep mode.

    AVR only wakes up on an external event, communicates to gauge over I2C, and goes back to sleep.

    So while programming the gauge, AVR is on the same bus but not active.

    UPDATE: I tried using another EV2300 with firmware 3.1r and it works fine with calibration and configuring data flash! 

    Can you please send me 3.1r firmware files so I can upgrade my existing firmware?