NTP5312: How to change NFC Protection Pointer Configuration register

[kiku541]

Hello,

I want to enable the AREA_0_H read & write protection by writing 0x30 to NFC Protection Pointer Configuration (NFC_PPC) using I2C. 

The I2C write returns a success but when the NFC_PPC register is read again, it still keeps at 0x00. The read write protection is still not enable.

How can I modify the NFC_PPC register?

FYI, similar problem also happens to SRAM and Configuration Protection (SRAM_CONF_PROT) register.

Thank you for your kind attention.

[Fabian_R]

Hello, Thank you for your interest in our products

In order to protect a specific are of the NTAG 5 it is required to first use a secure mode for authenticating into the Tag, is possible that the protection isn't enabling due to this.

For further information, please take a look at section 8.2.4.3.6 PROTECT PAGE below Table 145. Memory organization where the access conditions are listed.

In case the conditions are listed and, the tag's NFC_PPC is still disabled, please share the log of the NTAG 5 Boost configuration for a closer look.

[kiku541]

Hello Fabian,

Here are the configuration memory of my NTP5312. I haven't activated the password authentication or locked any memory. Most register values are coming out of box.

Configuration Header
1008h: 81 00 00 00

NFC Global Crypto Header
100Ch: 00 81 00 00

NFC Crypto Configuration Header
100Dh: 00 81 00 00

KEY_0 to 3
1020h: 00 00 00 00
1021h: 00 00 00 00
1022h: 0F 0F 0F 0F
1023h: 0F 0F 0F 0F
1024h: 00 00 00 00
1025h: 00 00 00 00
1026h: 00 00 00 00
1027h: 00 00 00 00
1028h: 00 00 00 00
1029h: 00 00 00 00
102Ah: 00 00 00 00
102Bh: 00 00 00 00
102Ch: 00 00 00 00
102Dh: 00 00 00 00
102Eh: 00 00 00 00
102Fh: 00 00 00 00

I2C Key Header
1030h: 81 00 00 00

I2C Protection Pointer
1031h: FF 00 00 00

Feature Configuration
1037h: 08 02 FF 00

Device Security Configuration
103Fh: 45 00 FF FF

NFC Protection Pointer
1058h: FF 00 00 00

NFC Section Lock
1092h: 00 00 00 00
1093h: 00 00 00 00

I2C Section Lock
1094h: 00 00 00 00
1095h: 00 00 00 00

I2C PWD_AUTH
1096h: 00 00 00 00
1097h: 00 00 00 00
1098h: 00 00 00 00
1099h: 00 00 00 00

I don't understand why the NFC_PPC (byte 1 of NFC Protection Pointer 1058h) cannot be modified by I2C under this condition.

Thank you for your kind attention.

[Fabian_R · Accepted solution]

Hello sir,

It is required to first set a password for the Tag before protecting a page of the tag. If there isn't a password and authentication for accessing the tag, it won't be possible to enable the page protection.

Please explore the possibility of using RFIDDiscover for performing this configuration and test. This will help you speed up the process.