Clarification of LOCKDETECT flag of NFCT peripheral

RE: Clarification of LOCKDETECT flag of NFCT peripheral

Andreas — Wed, 27 Mar 2019 11:51:30 GMT

Hi,

EVENTS_FIELDDETECTED sets FIELDPRESENT.FIELDPRESENT. If there is lock, FIELDPRESENT.LOCKDETECT will be set.

Best regards,

Andreas

RE: Clarification of LOCKDETECT flag of NFCT peripheral

Remo — Wed, 27 Mar 2019 07:28:30 GMT

Hi Andreas

I've one last question. Is the FIELDDETECTED event generated due to the FIELDPRESENT flag or the LOCKDETECT flag?

RE: Clarification of LOCKDETECT flag of NFCT peripheral

Andreas — Tue, 26 Mar 2019 08:16:57 GMT

Hi,

Our NFC stack should check this, if you are using that you should not need to pay any attention to it. If you are making your own stack you might want to check it, it will probably only be interesting if you risk entering the Active state if a non-valid field is present.

Best regards,

Andreas

RE: Clarification of LOCKDETECT flag of NFCT peripheral

Remo — Mon, 25 Mar 2019 14:29:24 GMT

Thank you for the fast answer.

Do I have to respect this flag in my application? Is this flag still of importance when I've received the SELECTED event (NFC Auto collision resolution successfully completed)?

Best regards

Remo

RE: Clarification of LOCKDETECT flag of NFCT peripheral

Andreas — Mon, 25 Mar 2019 12:00:10 GMT

Hi,

This indicates that the carrier frequency is correct and stable, it can e.g. be used to verify if a detected field is a valid NFC field or not. 1 = Locked means the field is valid.

Best regards,

Andreas