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