RF430CL331HIPWR datasheet(16/60 Pages) TI1

16 / 60 page

RF430CL331H

SLASE18A – SEPTEMBER 2015 – REVISED NOVEMBER 2015

www.ti.com

D. An I2C restart was done and device address sent with a read selection.

E. Clock stretching is being used by the RF430CL331H when it needs more time to respond due to

unfinished internal processing.

F. I2C_READY line is now low, new I2C communication should not be started.

G. RF430CL331H drives the SDA line and returns the value of the status register, which is 0001h.

H. I2C_READY signal has returned to high, indicating communication can be started. This occurs after a

short period of time after a STOP condition (in square red). This brief time is necessary for the

RF430CL331H to finish internal processing.

5.6.2

BIP-8 Communication Mode With I

The BIP-8 communication mode is enabled by setting the BIP-8 bit in the General Control register. All

communication after setting this bit uses the following conventions with exactly 2 address bytes (16-bit

address) and 2 data bytes (16-bit data) (see Table 5-4 and Table 5-5).

Table 5-4. Write Access

Address Bits

Master

Data at Addr + 0

Data at Addr + 1

BIP-8

15 to 8

7 to 0

Slave

N/A

The Bit-Interleaved Parity (BIP-8) is calculated using 16-bit address and 16-bit data. If the received BIP-8

does not match with received data, no write is performed. The BIP-8 calculation does not include the I2C

device address.

Table 5-5. Read Access

Address Bits

Master

N/A

15 to 8

7 to 0

Slave

N/A

Data at Addr + 0

Data at Addr + 1

BIP-8

For read access, the Bit-Interleaved Parity (BIP-8) is calculated using the received 16-bit address and the

2 transmitted data bytes, and it is transmitted back to the master. The BIP-8 does not include the device

address.

5.7

NFC Type 4B Tag Platform

This device is an NFC Forum Type 4B Tag Platform and ISO/IEC 14443B-compliant transponder that

operates according to the NFC Forum Tag Type-4 specification and supports NDEF (NFC Data Exchange

Format) data structure. Through the RF interface, the user can read and update the contents in the NDEF

memory. The NDEF message in its entirety would only be present on the memory of the host controller.

The RF430CL331H only has a portion of the NDEF message at any one time.

NOTE

This device does not have nonvolatile memory; therefore, the information stored in the NDEF

memory is lost when power is removed.

This device does not support the peer-to-peer mode or the reader/writer mode. All RF communication

between an NFC forum device and this device is in the passive tag mode. The device responds by load

modulation and is not considered an intentional radiator.

This device is intended to be used in applications where the primary reader/writer is, for example, an NFC-

enabled handset. In this case, the host application can be considered the destination device, and the cell

phone or other type of mobile device is treated as the end-point device.

Detailed Description

Submit Documentation Feedback

Product Folder Links: RF430CL331H

RF430CL331HIPWR Datasheet(PDF) 16 Page - Texas Instruments

RF430CL331HIPWR Datasheet(HTML) 16 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 59 60

Datasheet Download

Link URL