NFC

[HadarMiz]

Hi,

I'm using the nRF52832 with SDK version 17.0.1, and I'm experiencing an issue with NFC handling.

Sometimes, the NFC interrupt triggers two FIELD_OFF or two FIELD_ON events in a row.

After investigating the code, I found that instead of being called from the interrupt handler, the FIELD_OFF event is triggered from another function. I've attached all the relevant functions for reference.

In particular, one function only triggers the FIELD_ON event, while the FIELD_OFF call appears to be disabled.
Is there a specific reason for this behavior?

 

In this function, I see that there's protection preventing 'filed_off' from being called without 'filed_on', and vice versa. However, in this state, we don't call 'filed_off' at all.

After debugging, we found that 'filed_off' is called from this function. There's no protection in place, and sometimes the device gets stuck while executing it.

I’d like to know if you see anything wrong with this function and how I can fix it.
Thanks,

[Simonr]

Hi

I'm not sure I understand what exactly the issue is. Do you see that the field_off function is called when it's not supposed to and that causes the device to get stuck? Can you explain what kind of "stuck" the device is? Does the device return an error code when stuck or what? Have you based your function off of an example project or have you made the project yourself.

Best regards,

Simon