Issue using NFC in nRF52832

RE: Issue using NFC in nRF52832

Hieu — Tue, 04 Feb 2025 07:23:57 GMT

Hi Arthur,

Could you please gather log from a run of the peripheral_nfc_pairing sample with the following Kconfig enabled.

CONFIG_LOG_MODE_DEFERRED=y
CONFIG_LOG_BUFFER_SIZE=8192
CONFIG_LOG_BACKEND_UART_BUFFER_SIZE=8192 # Or RTT if you are logging via RTT.

CONFIG_NFC_PLATFORM_LOG_LEVEL_DBG=y
CONFIG_NFC_NDEF_CH_REC_PARSER_LOG_LEVEL_DBG=y
CONFIG_NFC_NDEF_LE_OOB_REC_PARSER_LOG_LEVEL_DBG=y
CONFIG_NFC_NDEF_PARSER_LOG_LEVEL_DBG=y
CONFIG_NFC_TNEP_CH_LOG_LEVEL_DBG=y
CONFIG_NFC_TNEP_TAG_LOG_LEVEL_DBG=y

I am unsure what could be the issue here, so I just want to enable logging for all NFC-related modules to be safe.

Are you against having a hardware review done by us? It's confidential, and it's helpful to have another pair of eyes checking things over. It's often hard to see a spot in something we have worked on over many days.

Have you checked with only one unit, or multiple units?

RE: Issue using NFC in nRF52832

Arthur J Sary — Fri, 31 Jan 2025 11:56:23 GMT

Hi Hieu,

Thank you for the previous suggestions. I followed your advice and tested the peripheral_nfc_pairing sample across multiple nRF Connect SDK and toolchain versions (ensuring they match). Specifically, I tested versions 2.5.2, 2.6.0, and 2.9.0, and the issue remains the same in all cases:

I can read the NFC tag information using a smartphone (with an app such as “NFC Tools”), so the tag is recognized and read properly.
However, the NFC callback never gets triggered, meaning the BLE advertising does not start (it seems the interrupt is never generated).

I have double-checked the hardware setup to ensure there are no pin or antenna issues, but so far I haven’t identified anything that would prevent normal operation. If you have any additional troubleshooting steps or configuration changes you recommend, please let me know.

RE: Issue using NFC in nRF52832

Hieu — Wed, 22 Jan 2025 07:52:18 GMT

Hi Arthur,

Both the record_launch_app and record_text samples use callback in a similar manner and doesn't have any special setup for the nRF52832 targets. I believe no special configuration is necessary.

Could you try flashing those samples and see if they work as intended first? Of course, make any change in pin configuration to adapt to your custom board.

You mentioned using nRF Connect SDK (NCS) v2.6.0, but with toolchain from v2.7.0. I don't think that is the problem here, but just to be sure, could you please try with toolchain v2.6.0?

Also likely not the issue, but I recommend moving to at least NCS v2.6.1.

If the setup still fails after that, could you please have a private case for a hardware design review?

I also recommend getting a nRF52 DK to test with the most similar environment.

Hieu