NFC code not working

[Gordon]

Hi,

I'm trying to get NFC working on a PCA10040 dev board. Using the nfc/record_url hex file it works fine, so the hardware is obviously ok.

However, when I use the exact same code as in the record_url example from my software, it doesn't do anything. All functions execute without errors, but then log_uart_printf gets called with:

[NFC_HAL]: initialize
[NFC_HAL]: start
// ------------- put NFC device near 
[NFC_HAL]: fielddetected
[NFC_HAL]: reinitialize
[NFC_HAL]: fielddetected
[NFC_HAL]: fielddetected
[NFC_HAL]: reinitialize
[NFC_HAL]: fielddetected
[NFC_HAL]: reinitialize
[NFC_HAL]: fielddetected
[NFC_HAL]: reinitialize
[NFC_HAL]: fielddetected
[NFC_HAL]: fielddetected
[NFC_HAL]: fielddetected
[NFC_HAL]: fielddetected
[NFC_HAL]: reinitialize
[NFC_HAL]: fielddetected
[NFC_HAL]: reinitialize

Also, will the NFC code ever be distributed as something that's not a binary blob? I'm using a language interpreter (Espruino), and it expects functions to be compiled without hardware floating point (the call style is different). Currently the only way I can use NFC is to recompile with VFP, which means I'm then unable to pass floating point values into any functions!

[bjorn-spockeli]

Gordon: This might sound like a stupid question, but is the CLOCK_ENABLED define set to 1 in nrf_drv_config.h ? I had some issues with the NFC functions returning no errors and the NFC peripheral not working properly when this define was not set.

[Hung Bui]

@Gordon: I'm glad that Bjørn and you caught the issue. Most likely without the CLOCK_ENABLED defined the LFCLK will use the internal 32kHz RC and it's not good enough for the NFC.

We could have avoided the trouble if we have an explicit check in the NFC module to make sure 32kHz crystal is used.