RF430CL331HIPW datasheet(24/63 Pages) TI2

24 / 63 page

Data Requested

1. PCD ± ReadBinary Request

Fill block with data

2. Host ± Service Request

Data Requested

3. PCD ± Next ReadBinary

N (<255 bytes)

Entire Buffer Space (not to scale)

Previous block cleared

and new data starts at

buffer_start_index of 0

4. Next Request: Cycle repeats

RF430CL331H

SLASE18A – SEPTEMBER 2015 – REVISED NOVEMBER 2015

www.ti.com

(d) When there is a General Type 4 request, the Status register (see Section 5.11.2) must be read

and the Type 4 Command field examined to determine what Type 4 command has been received.

(e) The result is a Read Binary command.

(f) The NDEF File Identifier register (see Section 5.11.7) may be read, but it is not necessary as it is

always the file that the last Select command selected.

(g) Read the Buffer Start register (see Section 5.11.11) to determine where in the buffer of the

RF430CL331H to begin storing the data.

(h) Read the NDEF File Offset register (see Section 5.11.10) to determine at which index in the NDEF

or CC file to begin supplying the data to the RF430CL331H.

(i) Read the NDEF Block Length register (see Section 5.11.9) to determine what block length the

PCD is requesting.

(j) Check if the request is valid:

(i) If it is valid, write the data into the buffer of the RF430CL331H starting at Buffer Start index for

NDEF Block Length bytes.

(ii) If it is not valid, assert the Custom Status Word option in the Host Response register (see

Section 5.11.8) and write the custom word in the Custom Status Word Response register (see

Section 5.11.13). Only the status word response supplied will be sent out.

(k) If caching is desirable, extra sequential data can be written to the RF430CL331H buffer, up to the

maximum RF430CL331H buffer length (length is 3000 bytes, highest index is 2999).

NOTE

To improve the Read Binary performance of the RF430CL331H , a caching feature may

be used. After writing the requested Read Binary request data into the RF430CL331H

buffer, extra sequential data may be written. If on the next Read Binary request, all of the

requested data is in the buffer, the RF430CL331H automatically responds and services

that request without any intervention of the host controller; that is, no interrupt is issued.

(l) Update the NDEF Block Length register (see Section 5.11.9) with the number of bytes written into

the buffer.

(m) The interrupt must be cleared by writing to the Interrupt Flag register. This step must be done

before setting the Interrupt Serviced field in the Host Response register.

(n) To complete servicing the Read Binary command interrupt, set the Interrupt Serviced field in the

Host Response register.

4. RF430CL331H procedure:

(a) Only the requested data (even if extra was supplied) is included in the response packet to the

PCD. The status words are appended to the response packet per NFC Type 4 specification.

(b) If the command was valid, the status words are SW1 = 90h and SW2 = 00h.

Custom Status Word Response register.

5.9.2.1

NDEF Read Command Internal Buffer Handling

Figure 5-9. Read Buffer Flow (no extra data)

Detailed Description

Submit Documentation Feedback

Product Folder Links: RF430CL331H

RF430CL331HIPW Datasheet(PDF) 24 Page - Texas Instruments

RF430CL331HIPW Datasheet(HTML) 24 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 61 62 63

Datasheet Download

Link URL