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: BQ28Z610 lock & i2C issue

Part Number: BQ28Z610

Hi TI E2E,

I have 2 questions about BQ28Z610 for use.

1st question:I use BQ28Z610 and have I2C SCL lockup issue(we found SCL keep low and SDA keep high). What conditions will cause this phenomenon?

2nd question:What is I2C mode use about BQ28Z610? Standard mode? Fast mode? I see spec about BQ28Z610, it seems that Fast mode.

Thanks!

Kevin 

  • Hello Kevin,

    What conditions cause the SCL to be held low? Are you sure it's the gauge holding the line low? The gauge may be trying to clock stretch, that can cause it to hold SCL low, but it should not be continuous.

    The gauge can operate in 2 modes, if the XL bit is on the gauge can operate at 400KHz.

    Sincerely,

    Wyatt Keller 

  • Hi Keller,

    What reason will occur clock stretch?

    What's difference between BQ28Z610 and BQ28Z610-R1?

    Thanks!

    Kevin

  • Hello Kevin,

    If the gauge needs to fetch data and needs more time it will hold SCL low, the host must recognize this.

    Please check the change list for the differences: www.ti.com/.../sluaa42.pdf

    Sincerely,

    Wyatt Keller

  • Hi Keller,

    About BQ28Z610-R1:

    Hardware reset of the I2C engine when a bus low signal occurs. A bus low signal is generated when the I2C clock line is low for bus low timeout.

    If I2C engine need to reset, the function will automatically enable? or need to external GPIO to control?

    Thanks!

    Kevin

  • Hello Kevin,

    This is a hardware reset for the comm engine, if you hold the lines low for 2 seconds.

    8.3.12 I 2C Timeout The I 2C engine will release both SDA and SCL if the I 2C bus is held low for ~2 seconds. If the BQ28Z610-R1 device were holding the lines, releasing them frees the master to drive the lines. Note: that the low time setting can be under firmware control but the HW default is 2 seconds

    This is only for the R1 hardware.

    Sincerely,

    Wyatt Keller