• State Verified Answer
  • Replies 31 replies
  • Subscribers 72 subscribers
  • Views 8866 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 115255
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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!

Parents
  • 0

    Hi Gordon,

    Attached is an example to use record_url in other example (ble_app_hrm). I don't see any issue. Could you try ?

    ble_app_hrs_URL_nfc - Copy.zip

  • 0 in reply to Hung Bui

    Hi Gordon,

    Thanks for making the repo, I had some issue with the dependencies and path I need to fix but I will try to compile it here.

    In the mean time could you try to help debugging the code by checking if the NFC peripheral is actually activated with the call NRF_NFCT->TASKS_ACTIVATE = 1; in nrf_nfct_clock_event_handler(). This only executed if the HFCLK is started (in function nrf_nfct_field_event_handler()).

    From your log, we can spot that the SELECTED event supposed to come after "fielddetected" but it didn't come. We suspect for some reason it's not activated. If the NRF_NFCT->TASKS_ACTIVATE = 1; is called but "selected" is not arrived, you can try to turn on interrupt on READY event and AUTOCOLRESST and COLLISION event. These are the events supposed to come before we get the SELECTED event.

    SELECTED event tells that the tag has been selected by the reader and the communication between them are fine.

Reply
  • 0 in reply to Hung Bui

    Hi Gordon,

    Thanks for making the repo, I had some issue with the dependencies and path I need to fix but I will try to compile it here.

    In the mean time could you try to help debugging the code by checking if the NFC peripheral is actually activated with the call NRF_NFCT->TASKS_ACTIVATE = 1; in nrf_nfct_clock_event_handler(). This only executed if the HFCLK is started (in function nrf_nfct_field_event_handler()).

    From your log, we can spot that the SELECTED event supposed to come after "fielddetected" but it didn't come. We suspect for some reason it's not activated. If the NRF_NFCT->TASKS_ACTIVATE = 1; is called but "selected" is not arrived, you can try to turn on interrupt on READY event and AUTOCOLRESST and COLLISION event. These are the events supposed to come before we get the SELECTED event.

    SELECTED event tells that the tag has been selected by the reader and the communication between them are fine.

Children
No Data
Related
Terms of service