As @endnode has pointed out, the NFCT peripheral on the nRF52832 can only be used as a NFC Tag (i.e. NFC Forum compliant listening device NFC-A), please see this page on our Infocenter.
As @endnode has pointed out, the NFCT peripheral on the nRF52832 can only be used as a NFC Tag (i.e. NFC Forum compliant listening device NFC-A), please see this page on our Infocenter.
My apologies - I have posted this as an answer, so posting it here as a comment
Hi guys.
Quick question, why would the Product Specification document specify TX and RX frame starts and ends, size, etc if the hardware can't do bi-directional communications? Also, from the link Bjorn posted:
"Frame assemble and disassemble for the NFC-A frames specified by the NFC Forum"
Why would it be able to disassemble frames if it can't act as a reader? From what I can understand with e-mail communications with Nordic is that bi-directional communications are possible on hardware level, but the library does not support it, which leaves the user to have to write their own library.
I have logged a ticket as suggested regarding more information about library development for two way communications. It would be interesting to hear comments and I will also give feedback on gained knowledge.
I guess there is misunderstanding of role and transport layer on NFC (or ISO14443 to be more precise). Even if you emulate card (PICC) aka slave you do bidirectional communication. And yes, you could develop your own library or HAL layer on top of well documented NFC HW peripheral block on nRF52 if you know what to do (e.g. you've ever implemented some ISO14443 card OS on dedicated HW without having this done by chip vendor). Alternatively (seems more likely given the level of your questions) you should seek some expert and subcontract the job externally.
There is indeed a lot going on 'behind the scenes' and my expertise lies not with ISO14443 as you correctly have noted. I have received a contact who I can potentially ask regarding plans for Nordic to expand their library.
