The ST25TA512 device is an NFC tag that can be accessed from the RF interface, based on the ISO/IEC 14443 Type A standard. The ST25TA512 is compatible with the NFC Forum

Type 4 Tag specifications and supports all corresponding commands.

Figure 1 displays the block diagram of the ST25TA512 device.

Figure 1. ST25TA512 block diagram

5)LQWHUIDFH

EDVHGRQ

,62,(&

7\SH$

VWDQGDUG

$QDORJ)URQWHQG

EDVHGRQ

,62,(&

7\SH$VWDQGDUG

,QWHUQDOWXQLQJ

FDSDFLWDQFH

3RZHU

PDQDJHPHQW

XQLW h/ΘƐǇƐƚĞŵ

ĂƌĞĂ hƐĞƌŵĞŵŽƌǇ

'LJLWDOXQLW

1)&)RUXP

7\SH7DJ

SURWRFRO

Signal name

AC0, AC1

Table 1. Signal names

Function

Antenna coils

Direction

06Y9

8/52 DocID027776 Rev 4

ST25TA512 Functional description

The ST25TA512 has just one functional mode available (see

Table 2

Mode

Tag mode

Supply source

Table 2. Functional mode

Comments

RF field only The RF interface operates only when RF field level is sufficient.

The ST25TA512 is supplied by the RF field and can communicate with an RF host (RFID reader or an NFC phone). The User memory can be accessed by the RF commands.

DocID027776 Rev 4 9/52

Signal descriptions ST25TA512

2.1 Antenna coil (AC0, AC1)

These inputs are used to connect the device to an external coil exclusively. It is advised not to connect any other DC or AC path to AC0 or AC1.

When correctly tuned, the coil is used to access the device using NFC Forum Type 4 commands.

10/52 DocID027776 Rev 4

ST25TA512

3

ST25TA512 memory management

ST25TA512 memory management

The ST25TA512 supports the NDEF Tag Application as defined in the NFC Forum Type 4

Tag. The ST25TA512 is composed of three files:

• a Capability Container (CC) file

• an NDEF file

• a System file: this is an ST-proprietary file

The System file contains some information on the configuration of the ST25TA512 device.

The CC file gives some information about the ST25TA512 itself and the NDEF file. The

NDEF file contains the User data.

The file identifier is the value used in the Select command to select a file.

File identifier

0xE101

0xE103

0x0001

System file

CC file

NDEF file

Table 3. File identifier

Meaning

The CC file gives some information about the ST25TA512 and the NDEF file. This file is a read-only file for the RF host and cannot be modified by issuing a write command.

The T field, Read Access and Write Access fields can be changed by the RF host by issuing a specific process (refer to

Section 7: Functional procedures

File offset

Table 4. CC file layout for 1 NDEF file

Meaning Value

0x0000 Length CC file

0x0002 Mapping version

(1)

0x0003 Maximum number of bytes that can be read

0x000F

0x20 or 0x10

0x0040

0x0005 Maximum number of bytes that can be written 0x0036

Comments

15 bytes

V 2.0 or V 1.0

64 bytes

54 bytes

DocID027776 Rev 4 11/52

ST25TA512 memory management ST25TA512

File offset

0x0007

0x0008

0x0009

0x000B

0x000D

0x000E

Table 4. CC file layout for 1 NDEF file (continued)

Meaning Value

0x04

(2)

0x06

0x0001

NDEF file control TLV

0x0040

0x00

(2)

0x00

(2)

Comments

T field

L field

FileID

Maximum NDEF file size in Bytes

Read access

Write access

1. According to the reader command format ST25TA512 will automatically align to the corresponding NFC

Forum version.

2. Delivery state.

The NDEF file contains the NDEF message which contains the User data. The RF host can read and write data inside the file. The first two bytes named NDEF Message Length define the size of the NDEF message. The NDEF Message Length shall be managed by the application and the ST25TA512 device does not check if its value is relevant vs the data written by the RF host. The ST25TA512 device uses the NDEF Message Length, e. g. the standard read can be processed only inside the NDEF message; otherwise, the ST25TA512 device returns an error code. For more details about the read command, refer to

Section 5.6.7: ReadBinary command

File offset

0x0000

0x0004

...

0x003C

Table 5. NDEF file layout

Byte 0 Byte 1

NDEF Message Length

User data User data

...

Byte 2

User data

...

Byte 3

User data

...

User data

12/52 DocID027776 Rev 4

ST25TA512 ST25TA512 memory management

3.2

The system file specifies the configuration of the ST25TA512. Table 6 lists the different

fields.

File offset Field name

Table 6. Field list

No. of bytes Read access Write access Delivery state

0x0000 Length system file

0x0002 ST reserved

0x0003 Event Counter Config

0x0004

20 bits counter

(MS nibble 0x0)

0x0007 Product version

Yes

None

Yes

(1)

None

0x0012

0x80

0x00

0x000000

0x0008 UID

0x000F Memory Size - 1

0x0011 IC reference code

Yes

None

0x13

(2)

0x02E5 xx xx xx xx xx

(3)

0x003F

0xE5

1. Configuration bytes can be locked by setting the Most significant bit to 1. Once locked, these bytes cannot be changed anymore.

2. ST reserved.

3. x values are defined by ST to ensure UID unicity.

File offset

0x0003

Counter config lock bit:

0b0: unlocked

0b1: locked

0b00000: ST reserved

Counter enable:

0b0: disable

0b1: enable

Counter increment:

0b0: on Read

0b1: on Write

Table 7. Details about the Counter config field b7 b6-b2 b1 b0

Read and write access rights to the NDEF File

The NDEF file can be locked for read or write accesses. It is also protected by a 128-bit password that the host shall present before accessing the NDEF file. There are two 128-bit passwords, one for the read access and the other one for the write access.

An NDEF file can be permanently locked for read or write accesses. Thus, the host cannot access the NDEF file.

DocID027776 Rev 4 13/52

ST25TA512 memory management

3.2.1

ST25TA512

The read password shall be sent to the ST25TA512 device before reading a read-locked

NDEF file.

The write password shall be present on the ST25TA512 device before writing a write-locked NDEF file. The write password shall be sent to change the read or write access. The read or write access right is defined for the NDEF file.

State of the Read and Write access rights

Two bytes in the CC file are used to define the Read and Write access rights to the NDEF file. For more details, refer to

Section 3.1.2: CC file layout .

Value

Table 8. Read access right

Meaning

0x00

0x80

0xFE

Read access without any security

Locked

(1)

Read not authorized

1. The read password shall be sent before reading in the NDEF file.

Value

Table 9. Write access right

Meaning

0x00

0x80

0xFF

Write access without any security

Locked

(1)

Write not authorized

1. The write password shall be sent before writing in the NDEF file.

The state 0xFF and 0xFE cannot be changed by using the Read or Write passwords.

The state diagram of Figure 2

shows how to change the access right to read an NDEF file.

14/52 DocID027776 Rev 4

ST25TA512 ST25TA512 memory management

Figure 2. Changing the read access right to an NDEF file

[

/RFNWKH1'()ILOH

8QORFNWKH1'()ILOH

[ [)(

3HUPDQHQWO\ORFNWKH1'()ILOH

1. See the procedure to lock the read access ( Section 7.4: Locking an NDEF file ).

2. See the procedure to unlock the read access (

Section 7.5: Unlocking an NDEF file

3. See the procedure to permanently lock the read access.

4. Proprietary state, not defined by NFC Forum Type 4 Tag.

069

The state diagram on

Figure 3 shows how to change the write access right to an NDEF file.

Figure 3. Changing the write access right to an NDEF file

[

/RFNWKH1'()ILOH

8QORFNWKH1'()ILOH

[

3HUPDQHQWO\ORFNWKH1'()ILOH

[))

069

1. See the procedure to lock the write access.

2. See the procedure to unlock the write access.

3. See the procedure to permanently lock the write access (

Section 7.6: Reaching the read-only state for an

NDEF file ).

4. Proprietary state, not defined by NFC Forum Type 4 Tag.

DocID027776 Rev 4 15/52

ST25TA512 memory management

3.3 Access right life time

ST25TA512

The access right life time is validated while the NDEF file is selected or until the end of the

RF session. Once the read or write access right is granted, the host can send one or more

ReadBinary or UpdateBinary commands.

At the end of a session or when the host selects another file, the read and write access rights are initialized.

Note:

The NDEF file passwords protect the read or write access from an RF interface from/to an

NDEF file.

Two NDEF file passwords are available for each NDEF file:

• Read password

• Write password

The length of a password is 128 bits (16 bytes).

The delivery state for all passwords = 0x00000000000000000000000000000000.

A 20 bits counter can track the read or write events on the NDEF file.

It benefits from an anti-tearing mechanism, that ensures the consistency of the counter, even if there has been an electrical problem during its increment.

The value of the Read/Write counter can be checked by any application, by reading suitable bytes in System file (see

Section 3.1.4

If enabled, the Read/Write counter will be incremented on first event (exclusively Read or

Write) which is performed on the NDEF File, inside an RF session (an RF session is entered when ST25TA512 receives a valid "Select Application" command).

The counter is reset when it is disabled.

Apart from these procedures, there is no way to act on the value of this counter.

The Read/Write counter can be configured through a specific byte in System file (see

Section 3.1.4

This configuration byte allows to:

• Enable or disable this counter

• Define if the counter must be incremented on a read or write sequence

• Definitively lock this configuration byte

Warning: Once this configuration byte is locked, it cannot be changed anymore: the counter will behave accordingly.

16/52 DocID027776 Rev 4

ST25TA512 ST25TA512 memory management

If enabled, the Read/Write counter will have an impact on the execution time of the event which is countered: the counter increment needs some write cycles of specific EEPROM cells automatically managed by ST25TA512, which increase the total time before the response is sent to the reader.

As a consequence, an S(WTX) request can be issued on the command that will increment

the counter (see Section 5.4: S-Block format

DocID027776 Rev 4 17/52

Communication mechanism ST25TA512

4.1

This section describes the principle of communication between an RF host and the

ST25TA512 device.

Master and slave

The ST25TA512 acts as a slave device on the RF channel and therefore waits for a command from the RF host before sending its response.

The RF host shall generate the RF field and the RF commands.

18/52 DocID027776 Rev 4

ST25TA512

5 RF command sets

RF command sets

This section describes the ST25TA512 command sets that can be issued by the RF host.

There are three command families:

• the NFC Forum Type 4 Tag command set

• the ISO/IEC 7816-4 command set

• the proprietary command set

The NFC Forum Type 4 Tag command set and the ISO/IEC 7816-4 command set use the I-

Block format. For more details about the I-Block format, refer to Section 5.2: I-Block format .

Two other command formats exist:

• the commands using the R-Block format

• the commands using the S-Block format

For more details about these formats, refer to

Section 5.3: R-Block format

and to

Section 5.4: S-Block format .

This section gives a brief description of the RF host commands. The format of these command sets is the I-Block format.

Table 10 lists the RF command sets.

Family command set

Table 10. RF command sets

Command name Class byte Instruction code Brief description

NFC Forum

Type 4 Tag

NDEF Tag Application Select

CC select

NDEF select

System select

ReadBinary

UpdateBinary

Verify

ISO/IEC 7816-4

ChangeReferenceData

EnableVerificationRequirement

DisableVerificationRequirement

EnablePermanentState

ST proprietary ExtendedReadBinary

UpdateFileType

0x00

0xA2

0xA4

0xB0

0xD6

0x20

0x24

0x28

0x26

0x28

0xB0

0xD6

NDEF Tag Application Select

Selects the CC file

Selects the NDEF file

Selects the system file

Reads data from file

Writes or erases data to a

NDEF file

Checks the right access of a

NDEF file or sends a password

Changes a Read or write password

Activates the password security

Disables the password security

Enables the Read Only or

Write Only security state

Reads data from file

Sets file type to NDEF or proprietary

DocID027776 Rev 4 19/52

RF command sets

5.1 Structure of the command sets

ST25TA512

The exchange of data between the RF host and the ST25TA512 uses three kinds of data formats, called blocks:

• I-Block (Information block): to exchange the command and the response

• R-Block (Receive ready block): to exchange positive or negative acknowledgment

• S-Block (Supervisory block): to use either the Deselect command or the Frame Waiting eXtension (WTX) command or response

This section describes the structure of I-Block, R-block and S-Block. This format is used for the application command set.

The I-Block is used to exchange data between the RF host and the ST25TA512. It is composed of three fields.

Table 11

details the I-Block format.

Name

PCB

Length 1 byte

PCB field

DID field (optional)

RF host to ST25TA512: C-APDU

ST25TA512 to RF host: R-APDU

2 CRC bytes

Table 11. I-Block format

SoD Payload

DID

1 byte

1 to 251 bytes

EoD

CRC

2 bytes

20/52 DocID027776 Rev 4

ST25TA512

Note:

RF command sets b7-b6

Table 12. PCB field of the I-Block format b5 b4

0b00 0 0

I-Block

RFU

Must be set to 0

DID field is present, if bit is set

Must be set to 0

Must be set to 1

Block number (1)

1. Follow ISO 14443_4 Block numbering rules (see note) b3

X b2

0 b1

1 b0

Block numbering rules:

Reader rules:

Rule A: The Reader block number shall be initialized to 0.

Rule B: When an I-block or an R(ACK) block with a block number equal to the current block number is received, the Reader shall toggle the current block number before optionally sending a block to the

ST25TA512.

ST25TA512 rules:

Note:

Rule C: The ST25TA512 block number shall be initialized to 1 at activation.

Rule D: When an I-block is received, the ST25TA512 shall toggle its block number before sending a block.

The ST25TA512 may check if the received block number is not in compliance with Reader rules to decide neither to toggle its internal block number nor to send a response block.

Rule E: When an R(ACK) block with a block number not equal to the current

ST25TA512 block number is received, the ST25TA512 shall toggle its block number before sending a block.

There is no block number toggling when an R(NAK) block is received.

When the RF host sends a command to the ST25TA512 the format of the payload is the

C-APDU.

When the ST25TA512 sends a command to the RF host, the format of the payload is the

R-APDU.

DocID027776 Rev 4 21/52

RF command sets

5.2.1 C-APDU: payload format of a command

ST25TA512

The C-APDU format is used by the RF host to send a command to the ST25TA512.

Table 13 describes its format.

Name

CLA INS

Table 13. C-APDU format

Payload field

P1 P2 L

1 byte Length 1 byte 1 byte 1 byte

Class byte

- 0x00: standard command

- 0xA2: ST command (1)

Instruction byte

Param Byte 1

Param Byte 2

Number of bytes of the Data field

Data bytes

Number of bytes to be read in the ST25TA512 memory

1. See

Table 10

1 byte

Data

Lc byte

1 byte the ST25TA512 uses the I-Block format to reply to a command which used the I-Block format. This format is described in

Table 14 .

Name

Table 14. R-APDU format

Payload field

Data (optional)

Le byte

SW1

1 byte Length

Data

Status byte 1

Status byte 2

SW2

1 byte

22/52 DocID027776 Rev 4

ST25TA512 RF command sets

The R-Block is used to convey positive or negative acknowledgment between the RF host and the ST25TA512.

NFC frame

Table 15. R-Block format

SoD

PCB DID

Length 1 byte

R(ACK) without the DID field: 0xA2 or 0xA3

R(ACK) with the DID field: 0xAA or 0xAB

R(NAK) without the DID field: 0xB2 or 0xB3

R(NAK) with the DID field: 0xBA or 0xBB

DID field (optional)

2 CRC bytes

1 byte

Payload

0 byte

EoD

CRC

2 bytes

There are two kinds of R-Blocks:

• R(ACK): the acknowledgment block sent by the RF host or by the ST25TA512

• R( NAK ): the non-acknowledgment block sent by the RF host b7-b6

0b10

R-Block

Must be set to 1.

0: ACK

1: NAK

0: DID field is not present

1: DID field is present

Must be set to 0

Must be set to 1

Block number

Table 16. R-Block detailed format b5 b4 b3 b2

1 X X 0 b1

1 b0

DocID027776 Rev 4 23/52

RF command sets ST25TA512

The S-Block is used to exchange control information between a reader and a contactless tag.

NFC frame

Table 17. S-Block format

PCB

SoD

DID

Payload

EoD

CRC

Length 1 byte 1 byte 1 byte 2 bytes

0xC2: for S(DES) when the DID field is not present

0xCA: for S(DES) when the DID field is present

0xF2: for S(WTX) when the DID field is not present

0xFA: for S(WTX) when the DID field is present

DID field (optional)

WTX field (optional)

(1)

2 CRC bytes

1. This field is present when b5-b4 bits are set to 0b11 (S-Block is a WTX). see

Table 18: S-Block detailed format

There are two requests using the S-Block format:

• S(DES): the deselect command

• S(WTX): the Waiting Frame eXtension command or response.

A Waiting Time eXtension request occurs in RF when the operating time needed by

ST25TA512 is greater than 19.2 ms.

The WTX field indicates the increase time factor to be used in this command execution

(FDTtemp = WTX * 19.2 ms). WTX depends on FWI.

Table 18. S-Block detailed format b5-b4 b3 b2

X X 0 b1

1 b0

0 b7-b6

0b11

S-Block

0b00: Deselect

0b11: WTX

0: DID field is not present

1: DID field is present

Must be set to 0

Must be set to 1

Must be set to 0

24/52 DocID027776 Rev 4

ST25TA512

Note:

RF command sets

After receiving the deselect command, the session is released and ST25TA512 enters the

Standby power mode.

In response to a RATS command, ST25TA512 returns FWI parameter (default frame waiting time used); when ST25TA512 needs more time for a command execution, it requests a frame waiting time extension by responding 0xF2 0xWTX (Request waiting time = FWI * WTX). If the reader accepts ST25TA512 request, it acknowledges by sending the command 0xF2

0xWTX. The frame waiting time becomes FWI * WTX for the current command only.

5.5

5.6 CRC of the RF frame

The two CRC bytes check the data transmission between the RF host and the ST25TA512.

For the RF frame, the CRC is computed on all the data bits in the frame, excluding parity bits, SOF and EOF, and the CRC itself.

The CRC is as defined in ISO/IEC 13239. The initial register content shall be 0x6363 and the register content shall not be inverted after calculation.

NFC Forum Type 4 Tag protocol

5.6.2

ST25TA512 command set is built to easily support the NFC Forum Type 4 Tag protocol.

Command name

NDEF Tag Application Select

Capability Container Select

NDEF Select

System File Select

ReadBinary

UpdateBinary

Table 19. Command set overview

Brief description

Select the NDEF Tag Application

Select the capability container (CC) file using the Select command

Select the NDEF file using the Select command.

Select the system file using the Select command.

Read data from a file

Write new data to a file

Status and error codes

This section lists the status and the error code of the ST25TA512.

Value

Table 20. Status code of the ST25TA512

SW1

0x90

SW2

0x00

Comment

Command completed successfully

DocID027776 Rev 4 25/52

RF command sets

Length

Value

ST25TA512

Table 21. Error codes of the ST25TA512

SW1 SW2

1 byte 1 byte

0x62

0x63

0x65

0x67

0x69

0x6A

0x6D

0x6E

0x82

0x00

0xCX

0x81

0x00

0x81

0x82

0x84

0x80

0x82

0x84

0x86

0x00

Comment

End of file or record reached before reading Le bytes

Password is required

Password is incorrect, X further retries allowed (X can take value

0,1, 2)

Unsuccessful updating

Wrong frame length

Command is incompatible with the file structure

Security status not satisfied

Reference data not usable

Incorrect parameters Le or Lc

File or application not found

File overflow (Lc error)

Incorrect P1 or P2 values

INS field not supported

Class not supported

26/52 DocID027776 Rev 4

ST25TA512 RF command sets

5.6.3 NDEF Application Select command the RF host shall send this command to activate the NDEF Tag Application.

To activate the NDEF Tag Application, the RF host sends the Select command (see

Table 22 ) in addition to the sequence defined in the NFC Forum digital protocol.

Table 22 defines the C-APDU of the Select command to select the NDEF Tag Application

(called NDEF Tag Application Select).

Name

Table 22. C-APDU of the NDEF Tag Application Select command

CLA INS P1 P2 Lc Data

0x00 0xA4 0x04 0x00 0x07

0xD27600

00850101

Class byte

Select instruction code

P1 field

P2 field

Number of bytes of data

Application ID

Le field

0x00

Table 23 defines the R-APDU of the NDEF Tag Application Select command.

Length

Value

Table 23. R-APDU of the NDEF Tag Application Select command

Data SW1 SW2 Comment

1 byte

0x90

0x6A

0x6D

1 byte

0x00

0x82

0x00

Command completed

NDEF Tag Application not found

Class not supported

Note:

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

The RF host uses the Capability Container Select procedure to select the capability container (CC) file.

The CC file is selected when this command returns "command completed" in the R-APDU.

Table 24 defines the C-APDU of the Select command to select the CC file (called Capability

Container Select).

DocID027776 Rev 4 27/52

RF command sets

Note:

ST25TA512

Name

Table 24. C-APDU of the Capability Container Select command

CLA

Class byte

0x00

Select instruction code

P1 field

P2 field

Number of bytes of data

CC file ID

(empty field)

INS

0xA4

0x00

0x0C

0x02

Data

0xE103

Table 25 defines the R-APDU of the CC Select command.

Length

Value

Table 25. R-APDU of the Capability Container Select command

Data SW1 SW2 Comment

1 byte

0x90

0x6A

0x6D

1 byte

0x00

0x82

0x00

Command completed

File or application not found

Class not supported

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

The RF host uses the NDEF Select command to select the NDEF file.

The NDEF file is selected when this command returns "command completed" in the R-

APDU.

Table 26 defines the C-APDU of the Select command to select the NDEF file (called

NDEF Select).

Name CLA

Table 26. C-APDU of the NDEF Select command

0x00

Class byte

Select instruction code

P1 field

P2 field

Number of bytes of data

0x0001: NDEF file

(empty field)

INS

0xA4

0x00

0x0C

0x02

Data

0x0001

28/52 DocID027776 Rev 4

ST25TA512 RF command sets

Table 27 defines the R-APDU of the NDEF Select command.

Length

Value

Data

Table 27. R-APDU of the NDEF Select command

SW1 SW2 Comment

1 byte

0x90

0x6A

1 byte

0x00

0x82

Command completed

File or application not found

Note:

5.6.6

Note:

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

System File Select command

The RF host uses this command to select the system file.

The System file is selected when this command returns "command completed" in the R-

APDU.

Table 28 defines the C-APDU of the command to select the System file (called System

Select).

Name

Table 28. C-APDU of the System File Select command

CLA

Class byte

0x00

Select instruction code

P1 field

P2 field

Number of bytes of data

System file ID

(empty field)

INS

0xA4

0x00

0x0C

0x02

Data

0xE101

Table 29 defines the R-APDU of the System File Select command.

Length

Value

Table 29. R-APDU of the System File Select command

Data SW1 SW2 Comment

1 byte

0x90

0x6A

1 byte

0x00

0x82

Command completed

System file not found, no data is returned

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

DocID027776 Rev 4 29/52

RF command sets ST25TA512

Note:

On receiving the ReadBinary command, the ST25TA512 reads the requested memory field and sends back its value in the R-APDU response.

Before sending a ReadBinary command, a file shall be selected by using a Select command.

The Response of the ReadBinary command is successful when the data to be read is within the selected file

(a)

; in other words, when the sum of P1-P2 and Le fields is equal to or lower than the selected file length.

Table 30 defines the ReadBinary command.

Name

Table 30. C-APDU of the ReadBinary command

CLA INS P1 & P2

0x00

Class byte

Read instruction code

0xB0

Offset in the file selected

(empty field)

Number of bytes to read between

0x01 ≤ Le ≤ max (Selected File length, 0xFFh)

2 bytes

Data

1 byte

Table 31 defines the R-APDU of the ReadBinary command.

Length

Value

Table 31. R-APDU of the ReadBinary command

Data SW1 SW2 Comment

Content read

1 byte

0x90

0x67

0x69

0x6A

0x6E

1 byte

0x00

0x82

0x00

Command completed

Wrong length

Security status not satisfied

File or application not found

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

30/52 a. For more details about CC file, refer to

Section 3.1.2: CC file layout .

For more details about NDEF file, refer to

Section 3.1.3: NDEF file layout

For more details about System file, refer to Section 3.1.4: System file layout .

DocID027776 Rev 4

ST25TA512 RF command sets

Note:

On receiving the UpdateBinary command, the ST25TA512 writes the data field into the selected file and sends back a status in the R-APDU response. If needed, ST25TA512 will

request a timing extension (see Section 5.4: S-Block format

Before sending an UpdateBinary command, a file shall be selected by issuing a Select command.

Table 32 defines the UpdateBinary command.

Name

Table 32. C-APDU of the UpdateBinary command

CLA INS P1 & P2 Lc Data

2 bytes 1 byte Lc bytes 0x00

Class byte

Write instruction code

0xD6

Offset in the file selected

Number of bytes of data (0x01 ≤

Data to write in the ST25TA512 memory

(empty field)

Length

Value

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

Table 33 defines the R-APDU of the UpdateBinary command.

Table 33. R-APDU of the UpdateBinary command

Data SW1 SW2 Comment

1 byte

0x90

0x65

0x67

0x69

0x6A

0x6E

1 byte

0x00

0x81

0x00

0x82

0x00

Command completed

Unsuccessful updating

Security status not satisfied

File or application not found

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

DocID027776 Rev 4 31/52

RF command sets

5.7 ISO/IEC 7816-4 commands

ST25TA512

The ISO/IEC 7816-4 command set offers some extended features such as the protection of the NDEF file. This command set is used to manage the right access of the NDEF file.

The Verify command has two functions:

Check if a password is required to access to the NDEF file (the LC field = 0x00).

2. Check that the password embedded in the Verify command allows the access to the memory (the Lc field = 0x10 and the password is present).

When the Lc field if equal to 0x00, the verify command returns a success code (0x90 00) provided that the access to the NDEF file does not require a password. When the access to the NDEF file is protected, the response to the Verify command returns an error code

(0x63 00).

When the Lc field equals 0x10, on receiving the Verify command, the ST25TA512 compares the requested password with the data contained in the request and reports whether the operation has been successful in the response.

Before sending this command, an NDEF file shall be selected by issuing the NDEF Select command. Thus, this command checks the right access condition of the last NDEF file selected.

After a successful command, an access is granted for the whole NDEF file.

Table 34 defines the Verify command.

Name CLA

Table 34. Verify command format

INS P1 & P2

0x00 0x20

Class byte

Instruction code

Password identification

0x0001: Read NDEF password transmit

0x0002: Write NDEF password transmit

Other: RFU

(1)

0x00: the password is not present

0x10: the password is present in the data field

Password

(empty field)

2 bytes

1. Return ERROR code when used.

1 byte

Data

Lc bytes

32/52 DocID027776 Rev 4

ST25TA512

Note:

5.7.2

RF command sets

Table 35 defines the R-APDU of the Verify command.

Data

Table 35. R-APDU of the Verify command

SW1 SW2 Comment

Length

Value

1 byte

0x90

0x69

0x6A

0x63

1 byte

0x00

0x84

0x81

0x82

0x80

0x00

0xCX

(1)

Command completed, the password is correct

The conditions of use are not satisfied (e.g. no

NDEF file was selected, or Write access equal to

FFh (write lock), or read access equal to FEh (read lock).

Command incompatible with file structure

Security status not satisfied

Incorrect parameter in command data field

A password is required

The password transmitted is incorrect and X encodes the number of further allowed retries.

1. At each session, the RF host can check a password three times.

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

Change Reference Data command

The Change Reference Data command replaces the read or write password related to the

NDEF files previously selected. It can be performed only if the security status satisfies the security attributes for this command.

Before sending this command, the verify command with the correct NDEF write password shall be issued. Thus, this command changes the reference data of the NDEF file.

Table 36 defines the Change Reference Data command.

Name

Table 36. Change reference data command format

CLA INS P1 & P2

Class byte

Instruction code

0x00 0x24

Password identification

0x0001: Read password transmit

0x0002: Write password transmit

Other: RFU

(1)

0x10: the password is present in the data field

NDEF new file Password

(empty field)

2 bytes

1. Return ERROR code when used.

0x10

Data

Lc bytes

DocID027776 Rev 4 33/52

RF command sets ST25TA512

Table 37 defines the R-APDU of the Change Reference Data command.

Length

Value

Table 37. R-APDU of the Change Reference Data command

Data SW1 SW2 Comment

0 1 byte 1 byte

0x90

0x69

0x65

0x69

0x6A

0x00

0x81

0x82

0x80

0x82

0x86

Command completed, the access right has been changed

Command is incompatible with the file structure

Unsuccessful updating

Security status not satisfied

Incorrect parameter in file structure

File or application not found

Incorrect P1 or P2 values

Note:

5.7.3

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

Enable Verification Requirement command

The Enable Verification Requirement command activates the protection by password of the

NDEF file. When this command is successful, the read or write access to the NDEF file is protected by a 128-bit password. It can be performed only if the security status satisfies the security attributes for this command.

This command can update the right access of the NDEF file by writing into the EEPROM. In this case, the response timing will be around 5 ms.

Before sending this command, the verify command with the correct NDEF write password shall be issued. Thus, this command changes the access right of the NDEF file.

Table 38 defines the Enable Verification requirement command.

Name

Table 38. Enable Verification Requirement command format

CLA INS P1 & P2

Class byte

Instruction code

0x00 0x28 2 bytes

New security attributes

0x0001: Enable the read protection of the NDEF file

0x0002: Enable the write protection of the NDEF file

Other: RFU

(empty field)

Data

34/52 DocID027776 Rev 4

ST25TA512 RF command sets

The last five bits identify the password sent in the Verify command.

Table 39 defines the R-APDU of the Enable Verification Requirement command.

Length

Value

Table 39. R-APDU of the Enable Verification Requirement command

Data SW1 SW2 Comment

1 byte

0x90

0x69

0x6A

1 byte

0x00

0x81

0x82

0x80

0x82

0x86

Command completed, the password is correct

Command is incompatible with the file structure

Security status not satisfied

Incorrect parameter in command data field

File or application not found

Incorrect P1 or P2 values

Note:

5.7.4

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

Disable Verification Requirement command

The Disable Requirement command deactivates the protection by password of the NDEF file. When this command is successful, the read or write access to the NDEF file is granted without security requirements. It can be performed only if the security status satisfies the security attributes for this command.

Before sending this command, the verify command with the correct NDEF write password shall be issued. Thus, this command changes the access right of the NDEF file.

This command can update the right access of the NDEF file by writing into the EEPROM. In this case, the response timing will be around 6 ms.

Table 40 defines the Disable Verification Requirement command.

Name

Table 40. Disable Verification Requirement command format

CLA INS P1 & P2

Class byte

0x00 0x26 2 bytes

Instruction code

New security attributes

0x0001: Disable the read protection of the NDEF file

0x0002: Disable the write protection of the NDEF file

Other: RFU

(empty filed)

Data

DocID027776 Rev 4 35/52

RF command sets ST25TA512

Table 41 defines the R-APDU of the Disable Verification Requirement command.

Length

Value

Table 41. R-APDU of the Disable Verification Requirement command

Data SW1 SW2 Comment

1 byte

0x90

0x69

0x6A

0x65

1 byte

0x00

0x81

0x82

0x80

0x82

0x86

0x81

Command completed, the password is correct

Command is incompatible with the file structure

Security status not satisfied

CC file or System file selected

File or application not found

Incorrect P1 or P2 values

Update failed

Note:

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

36/52 DocID027776 Rev 4

ST25TA512

5.8

RF command sets

ST proprietary command set

The RF host can be issued with the command set described in this chapter.

Note:

On receiving the ExtendedReadBinary command, the ST25TA512 reads the requested memory field and sends back its value in the R-APDU response.

Before sending an ExtendedReadBinary command, a file shall be selected by issuing an

NDEF select command.

The response of the ExtendedReadBinary command will be successful even if the data to be read is beyond the NDEF message. The command returns an error code if the data to be read goes beyond the end of the file.

Name

Table 42. C-APDU of the ExtendedReadBinary command

CLA INS P1 & P2

0xA2

ST Class byte

Read instruction code

Offset in the file selected

0xB0 2 bytes

(empty field)

Number of bytes to read between 0x01 ≤ Le ≤ 0xFF

Data

1 byte

Table 43 defines the R-APDU of the read binary command.

Length

Value

Table 43. R-APDU of the ExtendedReadBinary command

Data SW1 SW2 Comment

Le bytes

Content read

1 byte

0x90

0x67

0x69

0x6A

1 byte

0x00

0x82

0x86

Command completed

Wrong length

Security status not satisfied

File or application not found

Incorrect P1 or P2 values

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

The command configures the NDEF file to the ReadOnly or to the WriteOnly State.

This command can update the right access to the NDEF file by writing into the EEPROM. In this case, the response timing will be around 6 ms.

DocID027776 Rev 4 37/52

RF command sets

Table 44 defines the EnablePermanentState requirement command.

Name

Table 44. EnablePermanentState command format

CLA INS

Class byte

0xA2 0x28

Instruction code

New security attributes

0x0001: Lock the NDEF file in read mode

0x0002: Lock the NDEF file in write mode

Other: RFU

(empty field)

P1 & P2

2 bytes

Data

ST25TA512

Table 45 defines the R-APDU of the EnablePermanentState command.

Length

Value

Table 45. R-APDU table of the EnablePermanentState command

Data SW1 SW2 Comment

1 byte

0x90

0x65

0x69

0x6A

1 byte

0x00

0x81

0x82

0x86

Command completed

Update failed

Security status not satisfied

File or application not found

Incorrect P1 or P2 values

Note:

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

This command makes it possible to modify the file type of a selected file to Proprietary file

(0x05) or NDEF file (0x04).

This command is granted only when application and file are selected and if the file length and access right have previously been set to 0X00h (message invalid, all access rights granted).

This command will update the file type located in the CC file by writing into the EEPROM. In this case, the response timing will be around 6 ms.

38/52 DocID027776 Rev 4

ST25TA512 RF command sets

Table 46 defines the UpdateFileType command.

Name CLA

Table 46. UpdateFileType command format

INS P1 P2 Lc

0xD6 0x00 0x00 0x01

Data

0x04 or

0x05

Value 0xA2

Class byte

Select instruction code

P1 field

P2 field

Number of bytes of data

File type

Table 47 describes the R-APDU of the UpdateFileType command.

Table 47. R-APDU of the UpdateFileType command

Data SW1 SW2 Comment

Length

Value

1 byte

0x90

0x69

0x6A

1 byte

0x00

0x82

0x80

0x82

0x86

Command completed

Security status not satisfied

CC file or System file selected

File or application not found

Incorrect P1 or P2 values

DocID027776 Rev 4 39/52

RF command sets ST25TA512

5.9

5.9.1

Specific RF command set

This section describes the command set that can be issued only by the RF host.

Anticollision command set

Table 48 lists the commands that can be issued only by the RF host. The format of these

commands is described in the NFC Forum Digital Protocol specification.

Table 48. Commands issued by the RF host

Family command set Command name Instruction code

NFC-A technology

ALL_REQ

SENS_REQ

SDD_REQ

SEL_REQ

SLP_REQ

0x52

(1)

0x26

(1)

0x93 or 0x95

0x50

1. Code on 7 bits.

Note:

Command

SENS_REQ or

ALL-REQ

SDD_REQ 1

In response to a SDD_REQ Command with a SEL_PAR value equal to 20h, ST25TA512 in the Operating Field transmit the requested cascade level of their NFCID1 (NFCID1 CLn, with n=1 or 2). The NFCID1 of ST25TA512 consists of 7 bytes. The length of the Response containing a complete NFCID1 cascade level (i.e., NFCID1 CL1, or NFCID1 CL2) is always

5 bytes. The coding of the Response depends on the value of the SEL_CMD byte and the size of the NFCID1.

Refer to the example below for more details.

Table 49. Example of anticollision sequence

Comment Response Code Comment Code

ATQA 42 00

93 20

NVB 20

Number Valid bit

(2 bytes Code & NVB)

CT uid1 uid2 uid3 BCC

UID double size bit frame anticollision

CT Cascade Tag

“0x88”

(UID 7bytes)

BCC Block Check

Character (XOR previous Bytes)

SEL_REQ 1

93 70 CT uid1 uid2 uid3 BBC

NVB 70

(cmd NVB Uid lower bytes)

CT Cascade Tag “0x88”

SAK & CRC 04 DAD7 UID Not complete

40/52 DocID027776 Rev 4

ST25TA512

Command

SDD_REQ 2

SEL_REQ 1

RF command sets

Table 49. Example of anticollision sequence (continued)

Code Comment Response Code

95 20

NVB 20

Number Valid bit

(2 bytes Code & NVB)

uid4 uid5 uid6 uid7

BCC

Comment

(UID 7bytes)

BCC Block Check

Character

(XOR previous Bytes)

95 70 uid4 uid5 uid6 uid7

BBC

NVB 70

(cmd NVB Uid Upper bytes)

SAK & CRC 20 FC70 UID complete

RATS command and ATS response are used for NFC Forum Type 4A Tag Platform Device

Activation (as defined in NFC Forum Digital Protocol specification).

Table 50 details the RATS command. This command shall be sent after the anticollision

process.

Name

Byte field

Bit field

Instruction code

FSDI

DID (0 ≤ DID ≤ 14)

2 CRC bytes

INS

0xE0

Table 50. RATS command

Param b7-b4

1 byte b3-b0

CRC

2 bytes

The FSDI field codes the FSD that defines the maximum size that an RF host is able to receive.

Table 51 gives the conversion from FSDI to FSD.

FSDI 0x0

FSD 16 24

Table 51. Conversion from FSDI to FSD

0x5 0x6 0x7 0x8

0x9h-

0xE

32 40 48 64 96 128 256 RFU

0xF

256

The DID (Dynamic ID, optionally affected to the ST25TA512 by the host to address

ST25TA512 in all commands) field defines the value of the addressed ST25TA512.

If DID is not ‘0’, the ST25TA512 ignores the command if it contains a DID different from the one affected to ST25TA512 during RATS.

DocID027776 Rev 4 41/52

RF command sets ST25TA512

Name TL T0

Table 52. ATS response

TA(1)

Byte field 0x05 0x75 0x80

Bit field -

Length of the ATS response

FSCI = 5 → FSC = 64 bytes

The maximum ascending data rate is 106 kbps

The maximum descending data rate is 106 kbps

FWI field (FWI = 6 → FWT = 19.2 ms)

SFGI field (SFGI = 0 → SFGT =302 µs)

The DID is supported

2 CRC bytes b8-b5

TB(1)

0x60 b4-b1

TC(1)

0x02

CRC

2 bytes

The FSCI codes the FSC which stands for the maximum frame size that the ST25TA512 is able to receive. The ST25TA512 is able to receive up to 64 bytes of command. If the RF host sends a command with more than 64 bytes, the ST25TA512 will not be able to treat the command and will not reply.

The FWI, which stands for the Frame Waiting time Integer, codes the FWT. This time corresponds to the maximum duration while an RF host shall send before sending the next command.

The SFGI which stands for the Start-up Frame Guard Time is the minimum time that the reader shall wait after receiving the response of the ST25TA512.

command and response

(b)

PPS (Protocol and Parameter Selection) command and response are defined in ISO/IEC

14443-4, in the Protocol Activation of PICC Type A.

The PPS command allows to change the data rates of the ascending (RF host to

ST25TA512) and descending (ST25TA512 to RF host) data rates. Usage of this command is optional, ST25TA512 only supports 106 Kb/s in both directions.

b. Not useful in case of ST25TA512 which only supports a Data Rate of 106 Kb/s in both directions.

42/52 DocID027776 Rev 4

ST25TA512 RF command sets

Name

Table 53. PPS command

INS (PPSS) PPS0

INS

PPS1

Byte field 0xDX 0x11

Bit field b7-b4 b3-b0

Instruction code

DID

PPS1 is present

RFU

Descending data rate (106 kb/s) = 0b00

Ascending data rate (106 kb/s) = 0b00

2 CRC bytes

0b0000

PPS1

1 byte b3-b2 b1-b0

CRC

2 bytes

The ascending and descending data rates shall be coded as described in

Table 54 .

Value

Data rate

Table 54. Ascending and descending data rate coding

0b00 0b01 0b10

106 kbps RFU RFU

0b11

RFU

When the ST25TA512 is able to change both data rates, it returns the following response.

The data rate of this response is 106 kbps; then, the ST25TA512 changes the ascending and descending data rates.

Table 55 gives the details of the PPS response.

Name

Byte field

Bit field

Response code

DID field

2 CRC bytes

Table 55. PPS response

RESPONSE (PPSS)

0xDX b8-b5 b4-b1

CRC

2 bytes

DocID027776 Rev 4 43/52

RF device operation

6 RF device operation

6.1

ST25TA512

Anticollision and Device Activation command set for the RF interface

The ST25TA512 device supports the command set defined in the NFC-A Technology and the Type 4A Tag Platform chapters of the NFC Digital Protocol V1.0 specification.

6.2 Open an RF session

Once the RF host has terminated the anticollision procedure and retrieve the ATS response, it shall send the SelectApplication command. The ST25TA512 will open an RF session. At this point, the RF host can send the applicative command set.

6.3

6.4 Close an RF session

The RF host can close the RF session by issuing one of these methods:

• send an S(DES) command

• turn off the RF field

Applicative command set

The applicative command set is composed of the following command sets:

• the NFC Forum Type 4 Tag command set

• the ISO/IEC 7816-4 command set

• the proprietary command set

44/52 DocID027776 Rev 4

ST25TA512 Functional procedures

7.1

7.2

7.3

7.4

This section describes some procedure to access the memory or manage its protection.

Selection of an NDEF message

The RF host shall use this procedure to detect the NDEF message inside an ST25TA512.

The NDEF detection procedure is as follows:

Open an RF session

2. Send the SelectNDEFTagApplication command

3. Select the CC file

4. Read the CC file

5. Select the NDEF file.

Reading of an NDEF message

The RF host executes the NDEF read procedure to read the NDEF file.

Detect successfully the NDEF file using the NDEF detection procedure

2. Check that the read access without any security is granted for the NDEF file from the information provided by the CC file

3. Select the NDEF file

4. Read the NDEF file.

Reading a locked NDEF file

The RF host executes this procedure to read an NDEF file which has been locked previously.

Select the NDEF Tag Application

2. Select the NDEF file

3. Present the Read password by using the Verify command

4. Read the data in the NDEF file.

Locking an NDEF file

The RF host executes this procedure to protect an NDEF file.

Select the NDEF Tag Application

2. Check the right access provided by the CC file

3. Select the NDEF file

4. Present the NDEF file Write password by using the Verify command

5. Lock the NDEF file by sending the Enable verification command.

DocID027776 Rev 4 45/52

Functional procedures

7.5 Unlocking an NDEF file

ST25TA512

The RF host executes this procedure to unlock an NDEF file which has been locked previously.

Select the NDEF Tag Application

2. Select the NDEF file

3. Present the NDEF file Write password by using the Verify command

4. Unlock the NDEF file by sending the Disable verification command.

7.6 Reaching the read-only state for an NDEF file

The RF host executes this procedure to permanently lock an NDEF file that has been previously locked with password.

Select the NDEF Tag Application

2. Select the NDEF file

3. Transmit the NDEF file Write password by using the Verify command

4. Send an EnablePermanentState command

7.7

7.8 Creating or Updating an NDEF file

Select the NDEF Tag Application

2. Select the NDEF file

3. Set the File Length to 0x00 using the UpdateBinary command

4. Write NDEF message content using the UpdateBinary command

5. Set the new File Length (must be always two written bytes)

Changing a File Type Procedure (applicable only on file

0x0001)

The RF host executes this procedure to change the File Type of a file for which all access rights were previously granted.

Select the NDEF Tag Application

2. Select the file 0x0001

3. Set the File Length to 0x00 using the UpdateBinary command

4. Send an UpdateFileType command with the New file Type as data

46/52 DocID027776 Rev 4

ST25TA512 UID: Unique identifier

The ST25TA512 is uniquely identified by a 7 bytes unique identifier (UID). The UID is a read-only code and comprises:

• The IC manufacturer code on 1 byte (0x02 for STMicroelectronics).

• The Product code on 1 byte.

• A device number on 5 bytes.

Table 56 describes the UID format.

Table 56. UID format

0x02 0xE5 5 bytes -

IC manufacturer code

ST25TA512 product code

Device number

DocID027776 Rev 4 47/52

Maximum ratings ST25TA512

Stressing the device above the ratings listed in

Table 57

may cause permanent damage to the device. These are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specification is not implied.

Exposure to absolute maximum rating conditions for extended periods may affect the device reliability.

Symbol

Table 57. Absolute maximum ratings

Parameter Min.

Max.

Unit

STG h

STG t

STG

Ambient operating temperature

Storage conditions

Sawn wafer on UV tape

-40

(1)

°C

°C months

Kept in its original packing form

(3)

MAX_1

(3)

STG

ESD

Storage temperature

Storage time

Sawn bumped wafer

(kept in its antistatic bag)

RF supply current AC0 - AC1

RF input voltage amplitude between

AC0 and AC1, V

SS left floating

pad

AC0

-V

AC1

(Peak to Peak)

Electrostatic discharge voltage (human body model)

(4)

AC0-AC1

(2)

100

2000 months

1. Counted from ST shipment date.

2. Counted from ST production (taping) date.

3. Based on characterization, not tested in production. Maximum absorbed power = 100 mW at 7.5 A/m.

4. AEC-Q100-002 (compliant with JEDEC Std JESD22-A114A, C1 = 100 pF, R1 = 1500 Ω , R2 = 500 Ω ).

°C mA

48/52 DocID027776 Rev 4

ST25TA512

10 RF electrical parameters

RF electrical parameters

This section summarizes the operating and measurement conditions, and the DC and AC characteristics of the device in RF mode.

The parameters in the DC and AC characteristics tables that follow are derived from tests performed under the Measurement Conditions summarized in the relevant tables.

Designers should check that the operating conditions in their circuit match the measurement conditions when relying on the quoted parameters.

Symbol

Table 58. Default operating conditions

Parameter Min.

Ambient operating temperature –40

Max.

Unit

°C

Symbol Parameter

Table 59. RF characteristics

(1)

Condition Min Typ Max Unit f

H_ISO

H_Extended

H min

CARRIER t

1 t

2 t

3 t

External RF signal frequency

Operating field according to ISO

Operating field in extended temperature range

Field detect, set-up field (1)

100% carrier modulation index

Pause A length

Pause A low time

Pause A rise time

= 0°C to 50°C

= -40°C to 85°C

MI=(A-B)/(A+B)

13.553

1500

100

28 / f

7 / f

1.5 x t

13.56

MIN CD

Pause A rise time section

Minimum time from carrier generation to first data

From H min

W t

TUN

(3) t

RF_OFF

RF write time (including internal

Verify) for one page

Internal tuning capacitor

RF OFF time

(4) f

= 13.56 MHz

Chip reset

4.468

(2)

1. All timing characterizations performed on a reference antenna with the following characteristics:

External size: 75 mm x 48 mm

Number of turns: 4

Width of conductor: 0.5 mm

Space between two conductors: 0.5 mm

Value of the tuning capacitor: 50 pF (ST25TA512)

Value of the coil: 2.5 µH

Tuning frequency: 14.2 MHz.

2. Time between command EOF and Response SOF when updating NDEF Message Length.

3. See

Capacitor value

4. Characterized only, at room temperature only, measured at V

AC0

-V

AC1

= 5 V peak to peak at 13.56 MHz.

13.567

7500

100

40.5 / f t

16 / f

6 / f

0.1

MHz mA/m mA/m mA/m

µs

µs ms ms pF ms

DocID027776 Rev 4 49/52

Ordering information ST25TA512

Device type

ST25 = RF memory

Product Type

T = Tags + RFID

Table 60. Ordering information scheme for packaged devices

ST25 T A 512 - A C 6 G 5

Protocol

A = ISO14443-A

Memory density

512 (binary)

Interface

A = None

Features

C = Counter as option

Operating temperature

6 = -40 o

C to +85 o

Package / Packing

G = Bumped 120 µm

Capacitor value

5 = 50 pF

Note: Parts marked as “ES”, “E” or accompanied by an Engineering Sample notification letter, are not yet qualified and therefore not approved for use in production. ST is not responsible for any consequences resulting from such use. In no event will ST be liable for the customer using any of these engineering samples in production. ST’s Quality department must be contacted prior to any decision to use these engineering samples to run a qualification activity.

50/52 DocID027776 Rev 4

ST25TA512 Revision history

Date

22-Apr-2015

13-Sep-2016

27-Feb-2017

05-Oct-2017

Revision

Table 61. Document revision history

Changes

Initial release.

Updated Features

and image on cover page.

Added Section 5.8.3: UpdateFileType command

and Section 7.7:

Creating or Updating an NDEF file .

Updated Section 7.8: Changing a File Type Procedure (applicable only on file 0x0001) .

Updated Figure 2: Changing the read access right to an NDEF file .

Updated Table 10: RF command sets

Table 57: Absolute maximum ratings and

Table 59: RF characteristics

Updated title of

Table 51: Conversion from FSDI to FSD and of

Section 11: Ordering information .

Updated document title and Features

Updated Table 59: RF characteristics and its footnote 4 .

Updated Features

and image caption on cover page.

Updated Table 6: Field list and

Table 16: R-Block detailed format

Updated footnote

Figure 2

and Note:

Section 11

DocID027776 Rev 4 51/52

ST25TA512

IMPORTANT NOTICE – PLEASE READ CAREFULLY

STMicroelectronics NV and its subsidiaries (“ST”) reserve the right to make changes, corrections, enhancements, modifications, and improvements to ST products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on

ST products before placing orders. ST products are sold pursuant to ST’s terms and conditions of sale in place at the time of order acknowledgement.

Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or the design of Purchasers’ products.

No license, express or implied, to any intellectual property right is granted by ST herein.

Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.

ST and the ST logo are trademarks of ST. All other product or service names are the property of their respective owners.

Information in this document supersedes and replaces information previously supplied in any prior versions of this document.

52/52 DocID027776 Rev 4

Scarica

Solo un promemoria. Puoi visualizzare il documento qui. Ma soprattutto, la nostra IA l''ha già letto. Può spiegare cose complesse in termini semplici, rispondere alle tue domande in qualsiasi lingua e aiutarti a navigare rapidamente anche nei documenti più lunghi o complicati.

No, voglio comunque cercarlo da solo

Ciao! Sono un chatbot AI specificamente addestrato per assisterti con il STMicroelectronics ST25TA512 Scheda dati. Ho esaminato attentamente il documento e posso aiutarti a individuare le informazioni di cui hai bisogno o spiegare il contenuto in termini chiari e semplici. Che tu stia cercando indicazioni su funzionalità specifiche, passaggi per la risoluzione dei problemi o l'uso generale, non esitare a fare domande. Più dettagli fornisci sulle tue esigenze o dubbi, più accuratamente e efficacemente potrò aiutarti!