NFC trigger hard fault

RE: NFC trigger hard fault

Roei — Mon, 22 Jun 2020 07:56:03 GMT

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

RE: NFC trigger hard fault

Jared — Mon, 22 Jun 2020 07:54:04 GMT

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

RE: NFC trigger hard fault

Roei — Mon, 22 Jun 2020 06:37:52 GMT

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

RE: NFC trigger hard fault

Jared — Mon, 22 Jun 2020 06:25:17 GMT

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

RE: NFC trigger hard fault

Roei — Wed, 17 Jun 2020 09:01:09 GMT

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?

RE: NFC trigger hard fault

Jared — Wed, 17 Jun 2020 08:48:16 GMT

Not quite, the fix is the added if clause that checks if there is already a field on. The idea is to only release the clock if it has already been request earlier, avoiding decrementing the semaphore twice. Workaround provided in the previous linked thread:

        case NRFX_NFC_FIELD_STATE_OFF:
            if (m_nfct_cb.field_on)     //This added if clause is the workaround
            {
                nrfx_nfct_state_force(NRFX_NFCT_STATE_SENSING);
#ifdef NRF52840_XXAA
                /* Begin: Bugfix for FTPAN-116 (IC-12886) */
                if (m_nrf52840.eng_a)
                {
                    *(volatile uint32_t *)0x40005010 = 1;
                }
                /* END: Bugfix for FTPAN-116 (IC-12886) */
#endif // NRF52840_XXAA
                nrf_nfct_int_disable(NRFX_NFCT_RX_INT_MASK | NRFX_NFCT_TX_INT_MASK);
                m_nfct_cb.field_on = false;
                nfct_evt.evt_id    = NRFX_NFCT_EVT_FIELD_LOST;
    
                NRFX_NFCT_CB_HANDLE(m_nfct_cb.config.cb, nfct_evt);
            }                       //The if statement ends here
            break;

RE: NFC trigger hard fault

Roei — Wed, 17 Jun 2020 05:37:07 GMT

Is that the correct fix?

RE: NFC trigger hard fault

Roei — Tue, 16 Jun 2020 09:01:54 GMT

Hi,

I think I already have this fix:

RE: NFC trigger hard fault

Jared — Tue, 16 Jun 2020 08:43:12 GMT

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