This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Question related to [218] NFCT: Frame Delay timing is too short after SLP_REQ.

I have a custom board using nrf 52382 with NFC.  While Developing application I have checked  nRF52832 Revision 2 Errata.

I have a question related [218] NFCT: Frame Delay timing is too short after SLP_REQ.

I want to ensure that FRAMEDELAYMAX is set to the default value when the NFCT is in states IDLE or SLEEP_A. I searched in the project but I have not ensured it.

kindly suggest a way to confirm it

Thanks in advance.

Parents Reply
  • You need to somehow ensure that FRAMEDELAYMAX is set to the default value when the NFCT is in states IDLE or SLEEP_A. There are several major changes in NFC drivers/libraries since SDK 15.2. E.g. in SDK 15.3 we have this section in the release notes:

    - The NFC libraries (nfc_t2t_lib and nfc_t4t_lib) now use the NFCT driver instead of the NFC HAL modules (hal_nfc_t2t and hal_nfc_t4t). 
      The NFCT driver is a part of nrfx repository.
    - Replaced hal_nfc_t2t and hal_nfc_t4t components with the nrfx_nfct driver.
    - Added the NFC platform module (nfc_platform) to abstract runtime environment specific implementation from the driver.
      HFCLK activation, required for NFC to operate correctly, is managed in this module.
    - Removed the nfc_fixes.h file with NFC workaround description. The content of this file was moved to nrfx_nfct.h.

    So backporting the workaround shown in SDK 16 to SDK 15.2 is actually not straight forward after all. If you are having difficulties with implementing the workaround in SDK 15.2, it might be easier to migrate your code to use SDK 16 instead.

Children
No Data
Related