Datasheet
A AS 0ADDR [6:0] CMD [7:0] Sr 1ADDR [6:0] A DATA [7:0] A DATA [7:0] PN
A AS A0 PADDR [6:0] CMD [7:0] DATA [7:0] DATA [7:0] A 66 sm
A AS 0ADDR [6:0] CMD [7:0] Sr 1ADDR [6:0] A DATA [7:0] A DATA [7:0] A
DATA [7:0] A DATA [7:0] PN
Waiting time inserted between incremental 2-byte write packet for a subcommand and reading results
(acceptable for 100 kHz)f
SCL
£
Waiting time inserted after incremental read
66 sm
66 sm
A AS 0ADDR [6:0] CMD [7:0] Sr 1ADDR [6:0] A DATA [7:0] A DATA [7:0] PN
A AS A0 PADDR [6:0] CMD [7:0] DATA [7:0] 66 sm
Waiting time inserted between two 1-byte write packets for a subcommand and reading results
(required for 100 kHz < f 400 kHz)
SCL
£
66 sm
A AS A0 PADDR [6:0] CMD [7:0] DATA [7:0] 66 sm
bq27530-G1
SLUSAL5 –DECEMBER 2012
www.ti.com
I
2
C Command Waiting Time
To ensure proper operation at 400 kHz, a t
(BUF)
≥ 66 μs bus free waiting time should be inserted between all
packets addressed to the bq27530-G1 . In addition, if the SCL clock frequency (f
SCL
) is > 100 kHz, use individual
1-byte write commands for proper data flow control. The following diagram shows the standard waiting time
required between issuing the control subcommand the reading the status result. A DF_CHECKSUM
subcommand requires 100mS minimum prior to reading the result. An OCV_CMD subcommand requires 1.2
seconds prior to reading the result. For read-write standard command, a minimum of 2 seconds is required to get
the result updated. For read-only standard commands, there is no waiting time required, but the host should not
issue all standard commands more than two times per second. Otherwise, the gauge could result in a reset issue
due to the expiration of the watchdog timer.
I
2
C Clock Stretching
A clock stretch can occur during all modes of fuel gauge operation. In SLEEP and HIBERNATE modes, a short
clock stretch will occur on all I
2
C traffic as the device must wake-up to process the packet. In the other modes (
BAT INSERT CHECK , NORMAL, SLEEP+ ) clock stretching will only occur for packets addressed for the fuel
gauge. The majority of clock stretch periods are small as the I
2
C interface performs normal data flow control.
However, less frequent yet more significant clock stretch periods may occur as blocks of Data Flash are updated.
The following table summarizes the approximate clock stretch duration for various fuel gauge operating
conditions.
Approximate
Gauging Mode Operating Condition / Comment Duration
SLEEP Clock stretch occurs at the beginning of all traffic as the device wakes up. ≤ 4 ms
HIBERNATE
BAT INSERT Clock stretch occurs within the packet for flow control. (after a start bit, ACK or first data bit) ≤ 4 ms
CHECK
Normal Ra table Data Flash updates. 24 ms
NORMAL
Data Flash block writes. 72 ms
SLEEP+
Restored Data Flash block write after loss of power. 116 ms
End of discharge Ra table Data Flash update. 144 ms
14 Submit Documentation Feedback Copyright © 2012, Texas Instruments Incorporated
Product Folder Links :bq27530-G1