RE: NFC lib restart bug

TSonono — Thu, 25 Mar 2021 11:32:42 GMT

Hi Simon,

Thanks for the swift reply!

In my code, I was checking the returns with APP_ERROR_CHECK but I did not include it in the code I attached to my question. Regarding calling emulation_stop before done, I've tried that too.

However, calling nrfx_nfct_uninit() did the trick! Thanks for that. FYI, it seems like this problem is still present in SDK 17.0.2 (which is what I'm using).

Thanks,

Tofik

RE: NFC lib restart bug

Simonr — Thu, 25 Mar 2021 11:24:24 GMT

Hi Tofik

At a first glance, I see that you call the done(); call before emulation_stop(); This should be the other way around, as you should stop the emulation before you release the reference to the application callback. Please make sure that both these return NRF_SUCCESS as well.

Next, it was discovered in this ticket, that the NFCT driver isn't uninitialized inside nfc_t4t_done(); in SDK 17.0.0, so you're correct that it is a bug. You will have to do this yourself in the application by calling nrfx_nfct_uninit() after nfc_t4t_done().

Best regards,

Simon