NFC trigger hard fault

[Roei]

Hi,

I have a problem of crash device after trying to connect my device to the PC via NFC. 

The issue is very rare.

I think that the issue occurs because of an assert in the function nrf_drv_clock_hfclk_release - ASSERT(m_clock_cb.hfclk_requests > 0).

How can I solve that?

In addition - I noticed that the functions in that file can be called form an interrupt context - isn't that unsafe to enter critical regions from an interrupt context? Maybe that can also cause some errors.

Thanks!

[Jared]

Hi,

I'm assuming that you're referring to this bug. It's scheduled to be fixed in a future release of the SDK. A workaround is also provided in the linked thread.

best regards

Jared 

[Roei]

Hi,

I think I already have this fix:

[Roei]

OK,

It's different in my version, probably because I'm using a different SDK (for example - I don't have m_nfct_cb).

So I need to fix it like that:

Am I right?

[Jared]

Which SDK version are you using? Is the issue still reproducible?

[Roei]

I'm using SDK 15, and I saw that issue 

[Jared]

The fix is correctly implemented. Have you remembered to include it on both the t2t and t4t driver?  

[Roei]

The fix was implemented by me, it wasn't there before. And now it seems OK