Change to NFC library

[skajam66]

Hi,

In ncs/v3.1.0/modules/hal/nordic/nrfx/drivers/include/nrfx_nfct.h, the enum 'nrfx_nfct_param_id_t' is defined as:

/** @brief NFCT driver parameter types. */
typedef enum
{
    NRFX_NFCT_PARAM_ID_FDT,     ///< NFC-A Frame Delay Time parameter.
    NRFX_NFCT_PARAM_ID_FDT_MIN, ///< NFC-A Frame Delay Time Min parameter.
    NRFX_NFCT_PARAM_ID_SEL_RES, ///< Value of the 'Protocol' field in the NFC-A SEL_RES frame.
    NRFX_NFCT_PARAM_ID_NFCID1,  ///< NFC-A NFCID1 setting (NFC tag identifier).
} nrfx_nfct_param_id_t;

In the nrfx support libraries shipped to us with a vendor Bluetooth stack, the enum is defined as:

/** @brief NFCT driver parameter types. */
typedef enum
{
    NRFX_NFCT_PARAM_ID_FDT,     ///< NFC-A Frame Delay Time parameter.
    NRFX_NFCT_PARAM_ID_SEL_RES, ///< Value of the 'Protocol' field in the NFC-A SEL_RES frame.
    NRFX_NFCT_PARAM_ID_NFCID1,  ///< NFC-A NFCID1 setting (NFC tag identifier).
} nrfx_nfct_param_id_t;

We are using the NFC libraries (libnfc_t2t.a and libnfc_t4t.a) from SDK v3.1.0 so it appears that v3.1.0 libraries are incompatible with the nrfx support libraries shipped with the Bluetooth stack.

Can you advise in which SDK version the above enum was changed? I'm thinking that I should use the libnfc_t2t.a and libnfc_t4t.a libraries from an SDK version prior to the change.

Kind regards,

Andrew Coad

[Simonr]

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

[skajam66]

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

[skajam66]

Simonr said:

For new SDK versions we recommend using the SoftDevice and Zephyr controller for LE Audio applications

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...

[skajam66]

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.