NTP53X2 datasheet(31/133 Pages) NXP

31 / 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

31 / 133

Bit

Name

Value Description

AREA_0-L is not read protected

READ_AREA_L

AREA_0-L is read protected

8.1.3.12 I2C Authentication Limit Counter

The I2C Authentication Limit Counter is a feature to limit the maximum number of failed

authentications from I2C perspective. The counter is incremented for failed password

write to block 1096h to 1099h. The counter resets on positive authentication.

The NFC interface can access this block with READ CONFIG and WRITE CONFIG

commands if not locked by NFC section lock.

Table 35. I2C Authentication Limit Counter (I2C_AUTH_LIMIT) location

Block Address

NFC

I2C

Byte 0

Byte 1

Byte 2

Byte 3

32h

1032h

I2C_AUTH_

LIMIT (LSB)

I2C_AUTH_

LIMT (MSB)

RFU

Byte 0 of Block 32h is LSB and Byte 1 is MSB of the I2C Authentication Limit counter

value. Default value of I2C_AUTH_LIMIT is 00h.

The start value for the Authentication Limit can be preset with an I2C WRITE command if

• I2C Key header is not locked or Not active

• I2C Key header is Active then after valid authentication with a write key.

The Authentication limit is enabled with the most significant bit of Byte 1 is set to 1b. The

remaining 15 bit of I2C_AUTH_LIMIT are defining the preset value.

Example:

• 8000h enables and presets the authentication limit to 0, which means the maximum

number of failed authentications before a successful is required again is 32767.

Remark: The absolute maximum authentication limit value is FFFEh before a positive

authentication is required, otherwise the authentication is irreversibly locked (no longer

available).

As soon as the value of the Authentication limit reaches

• FFFFh: no further authentication possible any longer. This status is irreversible.

8.1.3.13 Configuration

Different features can be configured with CONFIG bits. The effect does not take place

in the current session. The effect takes place after POR. All config bits can be read and

written from both interfaces.

Table 36. Configuration Bytes Location (CONFIG)

Block Address

NFC

I2C

Byte 0

Byte 1

Byte 2

Byte 3

37h

1037h

CONFIG_0

CONFIG_1

CONFIG_2

RFU

On POR, all CONFIG bits are copied to CONFIG_REG (see Section 8.1.4.2).

NTP53X2 датащи(PDF) 31 Page - NXP Semiconductors

NTP53X2 датащи(HTML) 31 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

датащи скачать

ссылки URL