[NCS 2.6.1] NFC T4T response timing

RE: [NCS 2.6.1] NFC T4T response timing

JONATHAN LL — Mon, 09 Mar 2026 12:59:06 GMT

Good to hear that it now works for you Jean, if there is anything else always feel free to reach out. We try to get things done in a reasonable amount of time but it can be difficult to do everything in a timely manner so sorry for the inconvenience it might have had.

Regards,
Jonathan

RE: [NCS 2.6.1] NFC T4T response timing

kartapusse — Mon, 09 Mar 2026 10:34:21 GMT

Hi Jonathan,

I have performed first tests with SDK 3.3.0-preview and the fix seems to work perfectly fine. I will soon extend my tests to ensure it fits to our needs but I am very confident now.

Thanks a lot for your support, it was worth the wait.

Jean

RE: [NCS 2.6.1] NFC T4T response timing

JONATHAN LL — Thu, 26 Feb 2026 12:22:59 GMT

[quote user="kartapusse"]Correct me if I am wrong but 3.3.0 is not yet released ?[/quote]

Correct

[quote user="kartapusse"]Is the NFC fix already present in v3.3.0-preview1 version ? [/quote]

It should be on the preview version yes, so you can test there to see if the issue still exist for you.

[quote user="kartapusse"]When 3.3.0 stable version will be released ?[/quote]

Not sure if we have a public release date, but I think you can expect it to be out before summer.

Regards,
Jonathan

RE: [NCS 2.6.1] NFC T4T response timing

kartapusse — Wed, 25 Feb 2026 13:20:44 GMT

Hi Jonathan,

Thanks for the update, I will test this soon.

Correct me if I am wrong but 3.3.0 is not yet released ? Is the NFC fix already present in v3.3.0-preview1 version ? When 3.3.0 stable version will be released ?

Regards,

Jean

RE: [NCS 2.6.1] NFC T4T response timing

JONATHAN LL — Tue, 17 Feb 2026 10:58:49 GMT

Hi Jean,

A fix is added for the NCS 3.3.0 release and this should address the issue. Sorry for this taking so long.

Regards,
Jonathan

RE: [NCS 2.6.1] NFC T4T response timing

JONATHAN LL — Fri, 26 Sep 2025 10:46:33 GMT

Hi Jean,

[quote user="kartapusse"] I am still waiting for the workaround. Do you have any info about it ?[/quote]

We are still waiting unfortunately, I am pining the developers here for you to try an push on this as we passed the 3 week timeline a few weeks back. Sorry for that.

Understand your frustration and will keep you updated with any news.

Regards,
Jonathan

RE: [NCS 2.6.1] NFC T4T response timing

kartapusse — Thu, 25 Sep 2025 15:45:18 GMT

Hi Jonathan,

Unless I missed an answer elsewhere, I am still waiting for the workaround. Do you have any info about it ?

Thanks and best regards,

Jean

RE: [NCS 2.6.1] NFC T4T response timing

JONATHAN LL — Wed, 27 Aug 2025 08:58:24 GMT

Hi Jean,

Timeline for the issue to be addressed\fixed\workarounded is ~3 weeks from last Thursday(21 Aug). So expect an update in around 2 weeks time.
Regards,
Jonathan

RE: [NCS 2.6.1] NFC T4T response timing

kartapusse — Tue, 20 May 2025 11:31:18 GMT

Hi Jonathan,

Could you at least confirm that you have the same behavior than me ?

So far I was using a custom board but to be sure, I reproduced the test on nrf5340 DK and I have the same behavior.

Is there any supplementary configuration to be done that could help ?

Jean

RE: [NCS 2.6.1] NFC T4T response timing

JONATHAN LL — Mon, 19 May 2025 20:44:47 GMT

Hi Jean, sorry for the slow response time here, but currently it is difficult for us to speed things up and I understand that that causes issues for you.

Also providing you access to the lib is not a easy task as there is a legal machinery that need to be involved and its slow.

I will try to get a more concrete timeline for you hare and follow up. Also pleas feel free to ask or push for updates if you want, fully understand that this is a timely issue for you.

Regards,
Jonathan

RE: [NCS 2.6.1] NFC T4T response timing

kartapusse — Mon, 05 May 2025 20:41:39 GMT

I am using this reader: https://www.hidglobal.com/products/omnikey-5422

I am also a bit confused about this Status Word. So far I don't know if this SW comes from the NRF chip or if this is a default SW returned by the reader.

This is also why I asked if access to NFC T4T source code library would be possible to debug this.

Jean

RE: [NCS 2.6.1] NFC T4T response timing

JONATHAN LL — Mon, 05 May 2025 20:13:59 GMT

Hi Jean,

Which NFC reader is used?

I'd like to understand what the error code (6E00) means. No response from the tag, delayed response or invalid block?

Regards,

Jonathan

RE: [NCS 2.6.1] NFC T4T response timing

kartapusse — Mon, 05 May 2025 08:27:46 GMT

Hi,

Thanks for this first answer, I am waiting for your investigation concerning WTX that seems to be not sent.

I had already tested to set FWI to the maximum (8 if I have correctly understood) but this has no effect.

I just tested to change callback processing with CONFIG_NFC_OWN_THREAD and the behavior is the same on reader side. However the errors raised by nfc_platform that I have mentioned in my initial query are not raised in this configuration case. Thus, this configuration has an impact but it is not sufficient.

Regards,

Jean

RE: [NCS 2.6.1] NFC T4T response timing

JONATHAN LL — Wed, 30 Apr 2025 17:14:14 GMT

[quote user=""]I was expecting the NFC T4T lib would send WTX to the reader until I call nfc_t4t_response_pdu_send() but it seems this is not the case. Am I missing something ?[/quote]

You are not missing something. Will investigate internally.

Proposal for possible workaround:

set different FWI (Frame Wait Time) through nfc_t4t_parameter_set() to see if the possible race condition is resolved
change the NFC callback processing: modify the IRQ priority of the callback or change the processing flow to use a dedicated thread instead of Work Queue: CONFIG_NFC_OWN_THREAD, CONFIG_NFC_THREAD_PRIORITY and maybe some others to see if it can help

Regards,
Jonathan