All HW peripherals can be used (if you do it properly) while BLE radio is operational (through SoftDevice or custom stack). So this part is safe, you can use BLE and NFC Tag (= ISO14443 Type A Card emulation) features in parallel. However (and you will get this answer in all instances of this question on this forum as well as nRF52 Product Specification so you probably already know it) nRF52 NFC HW block isn't able to feed 13.56MHz field so there is pretty no way how it would work as "NFC reader". Sure you can purchase discrete HW which does it and communicate with nRF52 over standard wired interface (I2C, SPI, UART/ISO7816...)
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.
