It seems we are talking different use case. If you are using UART interface of nRF52 to talk with an IC card, there should have another device is used to connect nRF52 and IC card, one side by UART connection with nRF52, the other side by ISO7816 to talk with IC card. If this is your case, nRF52 only take are the UART package, no relationship with ISO7816.
What I've said is that nRF52 is working as full functional card reader, the IC card contactors have directly electrical connection with nRF52 GPIO.
Yes, ISO7816 has no relationship with BLE. In our case, the application program take care the time events form BLE and ISO7816. For example, since Softdevice use the highest interrupt of nRF52, so the ISO7816 packets may be corrupted by BLE events, a sanity check is used for each ISO7816 packet. But if you are using UART of nRF52, there is no such issue, since nRF52 take care UART and BLE.
It seems we are talking different use case. If you are using UART interface of nRF52 to talk with an IC card, there should have another device is used to connect nRF52 and IC card, one side by UART connection with nRF52, the other side by ISO7816 to talk with IC card. If this is your case, nRF52 only take are the UART package, no relationship with ISO7816.
What I've said is that nRF52 is working as full functional card reader, the IC card contactors have directly electrical connection with nRF52 GPIO.
Yes, ISO7816 has no relationship with BLE. In our case, the application program take care the time events form BLE and ISO7816. For example, since Softdevice use the highest interrupt of nRF52, so the ISO7816 packets may be corrupted by BLE events, a sanity check is used for each ISO7816 packet. But if you are using UART of nRF52, there is no such issue, since nRF52 take care UART and BLE.
