NT3H2111 NDEF message can't be read by NXP Tag Reader

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

NT3H2111 NDEF message can't be read by NXP Tag Reader

Jump to solution
377 Views
Frzn_Solid
Contributor I

I'm using the NT3H2111 Ntag plus I2C 1k device. I've been able to write the capability container to the proper values in order to do read/writes using NFC:

CC:  0xAA, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xE1, 0x10, 0x6D, 0x00

I've also successfully written the following 32 bytes to create what I hope is a Hello World NDEF message:

0x03, 0x12, 0xD1, 0x01, 0x0E, 0x54, 0x65, 0x6E, 0x48, 0x65, 0x6C, 0x6C, 0x6F, 0x20, 0x57, 0x6F, 0x72, 0x6C, 0x64, 0x21, 0xFE, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00

I've padded the end with 0s in order to properly write the two blocks of memory. I can successfully write this but when I try reading with the NCP Tag Reader, it says that there is no NDEF message. Am I formatting it incorrectly?

 

0 Kudos
Reply
1 Solution
349 Views
Fabian_R
NXP TechSupport
NXP TechSupport

Hello sir,

It is possible that there is a small issue with the NDEF.

For a Hello world, the NDEF should be formatted as shown in the image.

Please notice that in the seventh byte, there is a 0x02 due to the NFC forum, specifically in RTD Text specifications.

Unfortunately, I can't share this document, sir.

 

Fabian_R_0-1719605163353.png

 

Best Regards,
Fabian

View solution in original post

0 Kudos
Reply
2 Replies
350 Views
Fabian_R
NXP TechSupport
NXP TechSupport

Hello sir,

It is possible that there is a small issue with the NDEF.

For a Hello world, the NDEF should be formatted as shown in the image.

Please notice that in the seventh byte, there is a 0x02 due to the NFC forum, specifically in RTD Text specifications.

Unfortunately, I can't share this document, sir.

 

Fabian_R_0-1719605163353.png

 

Best Regards,
Fabian
0 Kudos
Reply
345 Views
Frzn_Solid
Contributor I

Hello Fabian,

 

Thank you, you're correct. I added the 0x02 and the message works now.

0 Kudos
Reply