SNIS217C december 2020 – may 2023 TMP139
PRODUCTION DATA
Refer to the PDF data sheet for device specific package drawings
As shown in Figure 7-13 and Figure 7-14, when the PEC is enabled by the host, an additional byte is added by the host after sending the register address. The format for the additional byte is described in Table 7-5.
CMD | RW | Command Name | Command Description |
---|---|---|---|
000 | 0 | W1R | Write 1 Byte to Register address specified in data packet |
1 | R1R | Read 1 Byte from Register address specified in data packet | |
001 | 0 | W2R | Write 2 Bytes to Register address specified in data packet |
1 | R2R | Read 2 Bytes from Register address specified in data packet | |
010 – 111 | X | RSVD | Reserved |
If the CMD value sent by the host is not valid for TMP139, the device shall not write any data to the register specified.
If there is a parity error during the data transfer, the device shall discard all the bytes including the byte for which parity error was detected and set the parity error condition. If the host attempts to start a new transaction with a Repeated Start to the same device, then TMP139 shall NACK the device address to indicate an error condition to the host. The host must first clear the parity error condition before performing any new transfer to the TMP139.
If there is a PEC error, then the TMP139 shall discard the entire data packet and set the PEC error condition. If the host attempts to start a new transaction with a Repeated Start to the same device, then TMP139 shall NACK the device address to indicate an error condition to the host. The host must first clear the PEC error condition before performing any new transfer to the TMP139.
When IBI is enabled, the device can communicate to the host the error conditions seen, using IBI. However when IBI is not enabled, it is strongly recommended that the host check the error status register to ensure that no parity or PEC error was detected on the bus.