ISO/IEC 14443 Type A support of nRF52832

[MJ Ma]

Hi ,

I am working on a NFC project which has below requirements , could you please help check if we have any existed example I can test ?

1. Support standarded ISO/IEC 14443 Type A.

2. All memory section is readable(full scanned) and writable by proper reader device.

I tested two example in SDK15.3, record_text and writable_ndef_msg , it turns out that all memory content of record_text can be scanned ,  but I cannot see any memory content of writable_ndef_msg ? could anyone tell me how to do full scan of writable_ndef_msg ?

[Kenneth]

Not sure if I understand, but from the description of the writable NDEF message example it seems you can both read and update the NDEF message, is that not the case?
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/nfc_writable_ndef_msg.html?cp=5_5_0_4_7_6 

[MJ Ma]

Hi Kenneth,

My question is how can I scan all memory content of writable_ndef_msg. You can see the different behavior of record_text example (pic1) and writable_ndef_msg(pic2) from below screenshots  . I can see all memory content of record_text, but none of writable_nedf_msg.

.

[Kenneth]

I have spoken with the expert, and it is probably app limitation. The record_text has its data organized according to the Type 2 Tag specification, whereas the writable_ndef_msg uses the Type 4 Tag specification. T2T data is a continuous data piece  (1024 byte buffer or so) and the NFC poller usually reads it from the beginning to the end. T4T data is organized in a more complex way and the protocol to access it is also a bit more sophisticated. At first, the poller reaads metadata containing tag attributes & file ids. Then it may decide to choose specific file id (like NDEF File ID) to get the file content.

Kenneth