NFCのトピック回复： NT3H2111 Capability Container byte2, LAST_NDEF_BLOCK How should they be configured

NT3H2111 Capability Container byte2, LAST_NDEF_BLOCK How should they be configured

Tzf — Wed, 12 Mar 2025 03:07:59 GMT

1. The range of LAST_NDEF_BLOCK is from 1h to 37h, and the corresponding NFC page range is from 4h to DCh. Based on the given information, the calculated byte size is D9 * 4. This means that from the starting page to the last page corresponding to LAST_NDEF_BLOCK, the entire data area contains D9 NFC pages (each NFC page is 4 bytes)

2. According to NFC Forum Type 2 Tag specification, the value of byte 2 of the CC multiplied by 8 equals the data area byte size. the data area byte size as D9 * 4

(D9 * 4) / 8 = 217 / 2 = 108.5. As byte 2 of the CC is an 8 - bit data (1 byte), its value should be an integer. it becomes 108 in decimal, and converting it to hexadecimal gives 6C.

So, according to the specification, the CC should be set to :Byte0:0xe1 , Byte1:0x10 Byte2:0x6c Byte3:0x00 right？

回复： NT3H2111 Capability Container byte2, LAST_NDEF_BLOCK How should they be configured

Tzf — Wed, 12 Mar 2025 07:11:20 GMT

after set CC and LAST_NDEF_BLOCK

the session bytes FEh:

0~7 byte value: 0, 0x37, 0xf8, 0x48, 0x8, 0x1, 0x0, 0x0

the i2c block0 0~15 value:

0x4, 0xa9, 0x35, 0x12, 0xf0, 0x71, 0x80, 0x0, 0x44, 0x0, 0x0, 0x0, 0xe1, 0x10, 0x6c, 0x0

Not clear why the TagInfo cannot detect NDEF information

回复： NT3H2111 Capability Container byte2, LAST_NDEF_BLOCK How should they be configured

Tzf — Wed, 12 Mar 2025 11:59:23 GMT

I found out why: the NDEF data area contains data in non-NDEF format