Problem with NTAG protected in NFC side

[NSF]

Hello,

I am using the NXP tag NTP5332 and actually I has problems with commands that are sent via NFC using customized mobile app. On the NFC side, I am having problems writing to a password-protected memory region. To read a memory region protected against reading, I follow the sequence of commands described above, changing only the Password Identifier to 0x01 and the operation to read; in this case, the read operation is successful. If the password protection against reading and writing is removed, the read and write commands work without any problems.

Can anyone help me with these issues? Am I sending the wrong command?
Thanks for your help!

[BPrada]

Hi,

Any progress, am having the same problem writing to a password-protected memory region. 

Best Regards

[EduardoZamora]

Hello @NSF

Hope you are doing well.

Could you please confirm that is the memory region you are trying to write to (User memory or Configuration memory)?

What is the configuration of your Protection Pointer and related conditions?

Is there any chance you have perform a Lock operation to the region you are trying to write? What is the value of your NFC Lock Block Configuration blocks?

Please consider that we recommend using TapLinx SDK. This SDK provides some tools for contactless applications development in smartphones. The open API allows developers open access to all hardware features of NXP‘s NFC product portfolio. It provides a subset of features for quick and easy development of lightweight applications.

Regards,
Eduardo.

[NSF]

Hi @EduardoZamora 

Thanks for your reply!

These are the configurations that the NFC tag has:

Reg. 0x1037 (Configuration Bytes): [0]: 0x09; [1]: 0x00; [2]: 0x5f; [3]: 0x00

Reg. 0x103F (Device Security Configuration): [0]: 0x45; [1]: 0x00; [2]: 0xff; [3]: 0xff

- NFC security: plain password

- Configuration area is not read and write protected from NFC perspective

- PP_AREA_1: 0xFFFF (is pointing outside the user memory)

Reg. 0x1020 (Read Password): [0]: 0x00; [1]: 0x00; [2]: 0x00; [3]: 0x00

- Read Password is 0x00000000

Reg. 0x1021 (Write Password): [0]: 0x00; [1]: 0x00; [2]: 0x00; [3]: 0x00

- Write Password is 0x00000000

Reg. 0x1058 (NFC Protection Pointer): [0]: 0x08; [1]: 0x30; [2]: 0x00; [3]: 0x00

- NFC_PP_AREA_0H: 0x08

- NFC_PPC: 0x30 (AREA_0-H is write and read protected; AREA_0-L is not read and write protected)

Reg. 0x100C: [0]: 0x00; [1]: 0x81; [2]: 0x00; [3]: 0x00

- NFC_GCH: 0x81 (The NFC passwords can be read and written with the READ CONFIG

          and WRITE CONFIG commands)

Memory organization:

0x00 - 0x08 --> NFC_AREA_0_L (is not read and write protected)

0x08 - end of memory --> NFC_AREA_0_H (read and write protected)

Regards,

NSF

[EduardoZamora]

Hi,

Please, try performing SET PASSWORD for both Read and Write, and then try writing to the block.

Regards,
Eduardo.

[NSF]

Hi @EduardoZamora 

Thank you for your reply.
In the screenshots I sent in the ticket, you can see that in the SET PASSWORD command I used 0x01 for reading and 0x02 for writing. From the tests I ran, only the read command in a read-protected memory region worked. For writing in a write-protected memory region, I used the following commands:
- SET PASSWORD with password identifier 0x02; this command worked;
- WRITE in register 0x14, for example; this command returns 0x01 0x0F.

Based on these tests I performed and the register values I sent in my previous reply, can you replicate the same scenario on your end?
Is there any configuration error in either the register values or the commands?
Thank you for your help.

Regards,
NSF

[EduardoZamora]

Hi,

Try the following sequence:

- SELECT NTAG
- Get Random Number
- SET PASSWORD for PID 01
- SET PASSWORD for PID 02
- Write to register 0x14

Regards,
Eduardo.

[NSF]

Good morning,

Yes, we already tested it and it was resolved. 

Thank you very much,
NSF