Change to NFC library

RE: Change to NFC library

Simonr — Fri, 06 Mar 2026 07:34:33 GMT

And this is on NCS v2.0.0, correct? Is it also reproducible on an nRF development kit so we can reproduce this on our end with one of the sample projects? Does it seem to be happening at random, or is it seemingly random whether you get a hardfault or not?

Best regards,

Simon

RE: Change to NFC library

skajam66 — Thu, 05 Mar 2026 12:16:14 GMT

[quote userid="75734" url="~/f/nordic-q-a/127200/change-to-nfc-library/562610"]What exactly is the issue you're seeing with NFC on your end?[/quote]

I'm getting hard fault 50% of the time. If I breakpoint on nrfx_nfct.c::nrfx_nfct_parameter_set(...) and look at the p_param parameter being passed in, it is sometimes good and NFC runs just fine. At other times, the values are garbage and I get an immediate hard fault. The first attached image (fdt=4096) is an example where NFC runs fine. The second is an example where I get a hard fault. These two images were from back-to-back runs.

RE: Change to NFC library

Simonr — Thu, 05 Mar 2026 07:32:44 GMT

There were some issues with the nrfx NFC driver that was fixed in nrfx 4.0.0 (NCS v3.2.0). I attached the patch files here so you can add those on your end. But this was mainly a current consumption issue, so if you have issues with the NFC data itself it might be something else than this issue. What exactly is the issue you're seeing with NFC on your end?

devzone.nordicsemi.com/.../nrf_5F00_nfc_5F00_patch.zip

Best regards,

Simon

RE: Change to NFC library

skajam66 — Tue, 03 Mar 2026 15:23:19 GMT

Are there any known issues with libnfc_t2t.a delivered with NCS 2.0.0? I ask because I cannot get NFC working for a pure NCS 2.0.0 build (that is, libnfc_t2t.a and all supporting files). I can get a build using libnfc_t2t.a plus supporting files from NCS 3.1.0 together with nrfx_nfct.c from NCS 2.0.0 working. For both cases, the program flow and the NFC data records are identical so it points to an issue with libnfc_t2t.a.

RE: Change to NFC library

skajam66 — Tue, 03 Mar 2026 10:47:01 GMT

[quote userid="75734" url="~/f/nordic-q-a/127200/change-to-nfc-library/562400"]For new SDK versions we recommend using the SoftDevice and Zephyr controller for LE Audio applications[/quote]

We have had discussions with Nordic about porting over from Packetcraft but, unfortunately, the controller is not provided as source code so we cannot implement some of the customisations that we have made with Packetcraft...

RE: Change to NFC library

skajam66 — Tue, 03 Mar 2026 10:44:28 GMT

Hi Simonr,

>> AFAIK the Packetcraft controller was provided as a bin file, and not with specific libraries.

Packetcraft controller is provided as source code. The Nordic drivers are also source code - basically a copy of what you find in NCS_vxxx/modules/hal/nordic/nrfx...

Regards,

Andrew Coad

RE: Change to NFC library

Simonr — Tue, 03 Mar 2026 09:44:49 GMT

Hi again Andrew

Okay. Packetcraft is not the LE audio controller we recommend for new designs, as the last controller was certfified for NCS 2.0.0, but should be valid up to 2.7.0. What are these libraries shipped with the vendor stack exactly? AFAIK the Packetcraft controller was provided as a bin file, and not with specific libraries.

For new SDK versions we recommend using the SoftDevice and Zephyr controller for LE Audio applications. https://docs.nordicsemi.com/bundle/comp_matrix_nrf5340/page/COMP/nrf5340/nrf5340_audio_qdid.html

We can not recommend moving the Packetcraft controller to NCS versions beyond v2.7.0 as that would violate the QDID.

Best regards,

Simon

RE: Change to NFC library

skajam66 — Fri, 27 Feb 2026 14:51:08 GMT

Hi Simonr,

Thank you for your response.

The Bluetooth stack is from Packetcraft. NFC is quite separate from Bluetooth but it still links in to the same NRFX libraries...

I can confirm that NCS 2.0.0 has the older enum declaration; NCS 2.1.0 has the newer declaration. I do not see a NCS 2.0.1 to download (using VS Code).

I guess my options are 1) to use libnfc_t2t.a and libnfc_t4t.a from NCS 2.0.0 or 2) find a way to build the NFC part using libraries from NCS 3.1.0 while building the Bluetooth part using the provided NRFX libraries.

Kind regards,

Andrew Coad

RE: Change to NFC library

Simonr — Fri, 27 Feb 2026 13:58:26 GMT

Hi Andrew

The

NRFX_NFCT_PARAM_ID_FDT_MIN configuration parameter was added as part of nrfx v2.9.0 back in July of 2022, so the libraries or Bluetooth stack you have been sent is rather old at this point. What Bluetooth stack is this exactly? From what I can see, the release this NFCT library was viable was in NCS v2.0.1.

Best regards,

Simon