This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NFC nfc_t4t_setup returns NRF_ERROR_INVALID_STATE on nRF5 SDK v17.0.0 (worked on 14)

Hello,

I'm running into an issue after upgrading my SDK from nRF5 SDK v14.2.0 to nRF5 SDK v17.0.0 .

We are using NFC periodically, where emulation is started and stopped.

Every time Emulation is started the following sequence is called:

err_code          =  nfc_t4t_setup(nfc_callback, NULL);
APP_ERROR_CHECK(err_code);
nfc_t4t_emulation_start();
d_nfcEmuStarted++;

Every time Emulation is stopped the following sequence is called:

d_nfcEmuStarted--;
nfc_t4t_emulation_stop();
nfc_t4t_done();

If NFC is started, and stopped once, subsequent calls to "nfc_t4t_setup(...)" return NRF_ERROR_INVALID_STATE . I've ensured "d_nfcEmuStarted" is 0, and with an NFC reader that Emulation is indeed stopped.

Is there an extra step I'm missing? It doesn't look like emulation is ever stopped in any of the Nordic Demos, so I don't have anything to compare to. This worked correctly with SDK 14

0 briz over 5 years ago

Edit: Ignoring the APP_ERROR_CHECK after nfc_t4t_setup(...) allows the program to work fine... not ideal
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jørgen Holmefjord over 5 years ago

Hi,

Please make sure to also check return codes from the other API calls (nfc_t4t_emulation_start()/nfc_t4t_emulation_stop()/nfc_t4t_done()). Do all these return NRF_SUCCESS?

Best regards,
Jørgen
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 briz over 5 years ago in reply to Jørgen Holmefjord
Hello, Thank you for your help.

I added the following:

err_code = nfc_t4t_setup(nfc_callback, NULL); APP_ERROR_CHECK(err_code); err_code = nfc_t4t_emulation_start(); APP_ERROR_CHECK(err_code);

and

err_code = nfc_t4t_emulation_stop(); APP_ERROR_CHECK(err_code); err_code = nfc_t4t_done(); APP_ERROR_CHECK(err_code);

The first time through all return "NRF_SUCCESS", the 2nd call "nfc_t4t_setup(...)" is still "NRF_ERROR_INVALID_STATE "

If I remove APP_ERROR_CHECK(..) after "nfc_t4t_setup(...)" the firmware functions normally (as it did with SDK 14).

I can verify emulation has stopped with a PCD in both cases.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jørgen Holmefjord over 5 years ago in reply to Jørgen Holmefjord

I reproduced this behavior with the SDK example. I'm checking with the developers if there are any changes between the releases that can cause this behavior.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jørgen Holmefjord over 5 years ago in reply to Jørgen Holmefjord

Sorry for the slow response on this topic.

It seems like the NFCT driver is not uninitialized inside the nfc_t4t_done() call. You can do this yourself in the application, by calling nrfx_nfct_uninit() after nfc_t4t_done() if you need to re-initialize the NFCT completely.

What is the purpose of doing a full re-initialization? There is no configuration-passing to the library through this API. If you want to change the configuration parameters, you can use nfc_t4t_paramter_set() API when the emulation is stopped (just calling nfc_t4t_emulation_stop() and nfc_t4t_emulation_start() should be enough) - no need to call nfc_t4t_done() and nfc_t4t_setup().

Best regards,
Jørgen
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel