Table 1. Standard Commands

Table 2. Control( ) Subcommands

Table 3. Extended Commands

9.5.4.1 I²C Interface

The fuel gauge supports the standard I²C read, incremental read, quick read, one-byte write, and incremental write functions. The 7-bit device address (ADDR) is the most significant 7 bits of the hex address and is fixed as 1010101. The first 8 bits of the I²C protocol are, therefore, 0xAA or 0xAB for write or read, respectively.

The quick read returns data at the address indicated by the address pointer. The address pointer, a register internal to the I²C communication engine, increments whenever data is acknowledged by the fuel gauge or the I²C master. “Quick writes” function in the same manner and are a convenient means of sending multiple bytes to consecutive command locations (such as two-byte commands that require two bytes of data).

The following command sequences are not supported:

Attempt to write a read-only address (NACK after data sent by master):

Attempt to read an address above 0x6B (NACK command):

9.5.4.2 I²C Time Out

The I²C engine releases both SDA and SCL if the I²C bus is held low for 2 seconds. If the fuel gauge is holding the lines, releasing them frees them for the master to drive the lines. If an external condition is holding either of the lines low, the I²C engine enters the low-power sleep mode.

9.5.4.3 I²C Command Waiting Time

To ensure proper operation at 400 kHz, a t_(BUF) ≥ 66 μs bus-free waiting time must be inserted between all packets addressed to the fuel gauge. 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. 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 must not issue any standard command more than two times per second. Otherwise, the gauge could result in a reset issue due to the expiration of the watchdog timer.

9.5.4.4 I²C Clock Stretching

A clock stretch can occur during all modes of fuel gauge operation. In SLEEP and HIBERNATE modes, a short ≤ 100-µs clock stretch occurs on all I²C traffic as the device must wake-up to process the packet. In the other modes (INITIALIZATION, NORMAL) a ≤ 4-ms clock stretching period may occur within packets addressed for the fuel gauge as the I²C interface performs normal data flow control.