NT3H2211W0FHKH Datasheet, PDF (19/77 Pages) NXP Semiconductors – NTAG I2C plus, NFC Forum Type 2 Tag compliant IC with I2C interface

NXP Semiconductors
NT3H2111/NT3H2211
NFC Forum Type 2 Tag compliant IC with I²C interface
8.3.7 Dynamic Lock Bytes
To lock the pages of NTAG I²C plus starting at page address 16 and onwards, the
dynamic lock bytes are used. The dynamic lock bytes are located in Sector 0 at page E2h.
The three lock bytes cover the memory area of 840 data bytes (NTAG I²C plus 1k) or 1864
data bytes (NTAG I²C plus 2k). The granularity is 16 pages for NTAG I²C plus 1k (see
Figure 9) and 32 pages for NTAG I²C plus 2k (see Figure 10) compared to a single page
for the first 48 bytes (see Figure 8).
NTAG I²C plus needs a Lock Control TLV as specified in NFC Forum Type 2 Tag
specification to ensure NFC Forum Type 2 Tag compliancy.
When NFC Forum Type 2 Tag transition to READ ONLY state is intended, all bits marked
as RFUI and dynamic lock bits related to the protected area shall be set to 0b when
writing to the dynamic lock bytes.
The default value of the dynamic lock bytes is 000000h. The value of Byte 3 is always 00h
when read.
Like for the static lock bytes, this process of modifying the dynamic lock bits is irreversible
from NFC perspective. If a bit is set to logic 1b, it cannot be changed back to logic 0b.
From I²C interface, these bits can be set to 0b again.
MSB
LSB
MSB
LSB
bit 7 6
5
4
3
2
1
0
bit 7 6
5
4
3
2
1
0
page 226 (E2h) 0
1
2
3
Sector 0
MSB
LSB
Block Locking (BL) bits
bit 7 6
5
4
3
2
1
0
aaa-008092
Fig 9. NTAG I²C plus 1k Dynamic lock bytes 0, 1 and 2
NT3H2111/NT3H2211
Product data sheet
COMPANY PUBLIC
All information provided in this document is subject to legal disclaimers.
Rev. 3.0 — 3 February 2016
359930
© NXP Semiconductors N.V. 2016. All rights reserved.
19 of 77