NTP53X2 datasheet(15/133 Pages) NXP

15 / 133 page

NXP Semiconductors

NTP53x2

NTAG 5 link - NFC Forum-compliant I2C bridge

NTP53x2

All information provided in this document is subject to legal disclaimers.

Product data sheet

Rev. 3.3 — 3 July 2020

COMPANY PUBLIC

544533

15 / 133

Remark: The counter can only be incremented with the C0 and C1 values defined in

Table 10. Other values than that preset the counter if a SET PASSWORD command with

the write password or a valid mutual authentication with a key with the Write privilege has

been executed before or leads to an error message.

Table 10. Increment counter data structure

Byte

Name

Value

Description

01h (LSB)

00h (MSB)

Value to increment the counter

00h

RFU

00h

RFU

8.1.3 Configuration memory

The configuration memory contains the security and configuration information. Access

to this memory area is only possible with WRITE CONFIG (see Section 8.2.3.2.2) and

READ CONFIG (see Section 8.2.3.2.1) commands depending on the initialization status.

Writing to blocks with only RFU bytes is not possible and results in error code 0Fh from

NFC perspective and NAK from I2C perspective. Reading complete RFU blocks results in

receiving all bytes 00h.

Changing RFU bytes and bits is not allowed and may result in unintended behavior.

From I2C perspective, the configuration can be accessed using READ MEMORY and

WRITE MEMORY command. Block address of configuration area from I2C perspective

starts from 1000h.

In Table 11 all NFC_KHs, NFC_KPs and AES_KEYs (all marked with an asterisk) are

only available in AES mode. NFC_KHs and NFC_KPs are not available at all and set to

RFU in plain password mode. In the area of KEY_0 and KEY_1, the plain passwords are

stored (see Section 8.1.3.9). The rest of the KEY area is RFU in plain password mode.

NOTE: AES mode is only available for NTP5332.

Different features can be configured with CONFIG bits. Similar to all other configuration

options, the effect does not take place in the current session. The effect takes place after

POR. If immediate change is expected, related session register bytes or bits need to be

used (see Section 8.1.4).

To which section each block belongs is defined in first column (Sec.). Sections might be

locked by setting related bit to 1b (see Section 8.1.3.32).

Table 11. Configuration Memory organization

Block Address

Sec.

NFC

I2C

Byte 0

Byte 1

Byte 2

Byte 3

Description

00h

1000h

...

07h

1007h

ORIGINALITY_SIGNATURE

32 byte Originality

Signature

(see Section 8.1.3.1)

08h

1008h

RFU

Configuration Header

(see Section 8.1.3.2)

NTP53X2 bảng dữ liệu(PDF) 15 Page - NXP Semiconductors

NTP53X2 bảng dữ liệu(HTML) 15 Page - NXP Semiconductors

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 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

bảng dữ liệu tải về

Link URL