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.

BQ28Z610 - I2C communication with charger not working

Other Parts Discussed in Thread: BQ28Z610, BQSTUDIO

Hi team,

my customer is using BQ28Z610 together with an LTC4100 charger. 

The problem he is facing is that he is not able to get the I2C communication working between the gauge and the charger. The bq28z610 doesn’t appear to be even trying to broadcast voltage/current levels to the charger chip (SCL & SDA show no activity on either). The BCAST flag is set to high as well. He is able though to communicate with the gauge using BqStudio.

Please find attached the flash file.

Do you have any suggestions on that? 

Thanks a lot.

Sergio Iannace

P998-001-TEST (02-Nov-16).gg.csv

  • Hi team,
    any news on that?

    Thanks a lot.

    Sergio
  • Hi Sergio,
    Can you have your customer verify that he correctly programmed his charger device address, voltage and current register? Can he keep the broadcast pacing at default which is 15?

    Also, Are both devices properly connected to the clock and data lines?

    Can he put a scope to the com lines so we see the transactions?

    thanks
    Onyx
  • Hi,

    I know a long time has passed since this was first posted, but my company was the originator of the question, and I have just picked up the job.
    We have a bq28z610 connected to our I2C bus. I can easily use a host device to read the charge current and voltage from the bq28z610 then write it to our charger in a loop. This all functions correctly. However if the bcast bit is set and all other I2C communication on the bus is terminated with the lines left high the bq28z610 does not send any I2C transmisions. I have tried with the pacing set anywhere between 1 and 15s and even higher. I have tried toggling the bcast bit but I do not see any transactions on an oscilloscope coming form the bq28z610 at all. Do you have any idea if there is a setting or something I am missing.

    Thanks very much
    Steve
  • Hi Steve,
    Let's look into this and get back to you. I know for sure that i have tested this functionality in the past with a charger and it worked fine. I currently no longer support this product but i will pull in the product specialist to look into this and get back to you.

    thanks
    Onyx
  • Hi Onyx,

    Thank you very much any help will be valued.

    Thanks Steve
  • Steve,

    Is your device address correct? Is it 0x12? Also, please increase the bcast time to 15 from 5. If you weren't setting BCAST, are you able to read all data from the gauge? RSOC etc?

  • Hi,

    My device address is correct and I have tried a few different ones. I have also tried BCAST time values of 0 - 15 and 30 and 60. None of that worked. When using a host micro I can read everything I have tried from the gas gauge, I currently send through my serial port. The requested voltage and charge. The actual battery level and % charged, the actual current into the battery and a status register. They all work correctly. But the gas guage doesn't broadcast on it's own. I have a scope attached and I never see any transaction not even to the wrong address or anything.

    Thanks

    Steve

  • OK, Steve. I'm going to try and check this out with one of our evm's. I'll get back to you on this before Friday evening.
  • Ok thanks for the help.
  • Steve,

    Broadcasting was removed as a feature on v0.17.

  • Hi,

    Is that definite, because I can't see any reference to that in the datasheet for the device ?

    Steve

  • Yeah, we checked it with our device firmware engineers and confirmed it. Our ds lags development. Sorry for the trouble.

  • Hi,

    Thank you for your help with this, I know it's not your fault you have been personally very helpful. However this is a very poor show for TI. It's not like a minor tweak to the firmware, it's one of the headline features on the datasheet right at the top. To remove that without even mentioning it anywhere is not really acceptable. My company have spent significant man hours trying to get the feature working assuming that we were making a mistake somewhere. Has TI never heard of producing an Errata sheet, or any document just to let their customers know, why on earth would they do something like that ?

    Cheers

    Steve

  • Hello Steve,
    We are working to re-introduce the broadcast functionality back on the bq28z610. The firmware update would be placed ti.com once available.

    thanks
    Onyx