TMP139AIYAHT datasheet(23/58 Pages) TI

23 / 58 page

HID2

HID1

HID0

R/W=1

ACK/NACK

MDB = 0x0

MR51[7:0]

T=1

MR52[7:0]

T=0

Figure 7-23. IBI Payload Packet with PEC Disabled

If PEC is enabled, then after MR52 register value, the PEC byte is sent with the T-bit set as 0. Again, the host

must send a Stop condition on the bus.

HID2

HID1

HID0

R/W=1

ACK/NACK

MDB = 0x0

MR51[7:0]

T=1

PEC

T=0

MR52[7:0]

T=1

Figure 7-24. IBI Payload Packet with PEC Enabled

When an IBI is asserted by the device and it successfully transmits the IBI, including the MDB, MR51, MR52 and

PEC (if PEC mode is enabled) bytes, the device shall automatically clear the IBI_STATUS bit in MR48 register.

7.4.6 Common Command Codes Support

The TMP139 supports a subset of the CCC as listed in the I3C basic specification and shown in Table 7-6. Only

CCC specified in the JESD302-1 are supported and the TMP139 shall either NACK unsupported CCC (if

possible) or ignore the actions when on a generic I3C bus. Similarly, for supported CCC—depending on whether

the TMP139 is in I2C or I3C mode—if a non-applicable CCC is sent, the device shall ignore the actions.

The TMP139 requires a Stop condition on the bus after receiving any CCC before it can process a device

specific read or write operation. Similarly, when processing a device specific read or write condition, a Stop on

the bus should follow before any CCC can be issued.

The TMP139 can receive a direct CCC with a Repeated Start condition after another direct CCC. Similarly, it is

valid to send a broadcast CCC following another broadcast CCC with a Repeated Start in between. In such a

case, the action taken by the device will only be updated following a Stop condition on the bus. The behavior of

TMP139 is not defined if a direct CCC is followed by a broadcast CCC or vice-versa with a Repeated Start. For

example, it is a legal combination in I2C mode to send a SETHID CCC, followed by a Repeated Start, then a

SETAASA CCC followed by a Stop condition. However, in I3C mode, sending a direct ENEC CCC followed by

Repeated Start and then a broadcast DEVCTRL CCC is not a valid condition for the TMP139. The host must

issue a Stop after ENEC CCC, before it sends a broadcast DEVCTRL CCC.

The CCC sent to the TMP139 may either be a broadcast code or a direct code. All CCC operations require the

host to send 7'h7E with R/W = 0, followed by the CCC and payload bytes specific to the CCC. For a direct CCC,

the host shall issue a Repeated Start on the bus after the CCC byte followed by the payload bytes.

Table 7-6. Supported CCC

CCC

Mode

Code

Description

Applicable in I2C Mode

Applicable in I3C

Mode

ENEC

Broadcast

0x00

Enable Event Interrupts

Yes

Direct

0x80

DISEC

Broadcast

0x01

Disable Event Interrupts

Yes

Direct

0x81

RSTDAA

Broadcast

0x06

Put the device in I2C mode

Yes

www.ti.com

TMP139

SNIS217 – DECEMBER 2020

Submit Document Feedback

Product Folder Links: TMP139

TMP139AIYAHT Datasheet(PDF) 23 Page - Texas Instruments

TMP139AIYAHT Datasheet(HTML) 23 Page - Texas Instruments

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58

Datasheet Download

Link URL