Hi,
I am having some trouble to make NFC Tag emulation working with "ble_app_hrs_rscs_relay" example application in the nRF5 SDK v11.0 on a PCA10040 board. Actually I did not modify anything, except adding some NFC related code snippets, found in the "launchapp" example for the NFC usage.
It seems that suddenly after a fielddetected event the nfc module is reinitialized while, when trying the "hrs_pairing_nfc" example (on the same hardware, not "together") everything is working fine. In the example mentioned before the nfc radio had never got to the "selected" state...
At first I thought that simply because of the Central-Periheral slots, the scheduling is much more strict, so I tried changing the "field_state_cnt" upper limit (in "hal_nfc_t2t.c"), giving more time to the nfc tag getting selected. Unfortunately that did not help at all.
Update #1: I digged myself a bit into the issue and found out that the HFCLK is enabled around 4-5 "fieldcheck cycles" later, than when using the "hrs_pairing_nfc" example. But if it was the only problem, pushing the "field_state_cnt" limit upper should help the nfc tag to get locked and selected...which is not, what I experienced. So the following questions are still opened:
Is the hfclock actually blocked (or drawn away somehow) by the softdevice when ble radio activity is about to happen? I tried with much greater advertising, scan, and connection interval, and the result was the same. No effect...
If not, what could cause such anomaly, and is there any kind of workaround for that?
Any help would be appreciated.
Thanks in advance.
Best Regards,
András Balogh
