PN7362 CCID Compliance? phEXNFCCID Example

[flesky]

Hello everyone,

I am currently working with the example project phEXNFCCID provided in relation to the CCID standard and have a few questions regarding its compatibility and implementation:

1. CCID Standard Compatibility:
   Is the example project fully compatible with the current CCID standard? Are there any known deviations or limitations in the implementation?

I would greatly appreciate any feedback, especially from those who have used or are familiar with the example project. If anyone has encountered issues or has suggestions for improvements, I would love to hear about them as well.

Thank you in advance for your help!

Florian

[Fabian_R · Accepted solution]

Hello, Thank you for your interest in our products

Please keep in mind that these examples are only for testing purposes. There hasn't been any deviation that may require to report or patch. Nevertheless, these are examples for starting your own implementation we only provide an API for using our hardware.

We can't recommend these as it is for end solutions. they require additional implementations from the customer side. We only provide something like a "proof of concept".

[flesky]

Hello,

I’m working with the PN7362 reader IC using the NXP phExNFCCcid reference project firmware and have encountered an issue during card removal related to the PC_to_RDR_IccPowerOff command (0x63).

Issue:
When the host sends the PowerOff command to the reader while the card is being physically removed, the reader correctly sends a NotifySlotChange with bStatus = 0x02 (Card Absent). However, the PowerOff command itself never completes, causing the CCID driver on the host to wait and eventually timeout (e.g., LIBUSB_ERROR_TIMEOUT).

As a result, the reader appears "confused" and refuses further commands, showing errors like "Slot busy." The driver never receives a proper card absent error response for the PowerOff command, only the timeout.

Observed behavior:

PC_to_RDR_IccPowerOff command sent (0x63)

NotifySlotChange with bStatus = 0x02 sent by the reader

Host CCID driver waits for command completion but hits a timeout

Reader becomes unresponsive until reset

Note:
It seems the host software must wait for the CCID driver timeout before recovery is possible.

Questions:

Is this a known behavior or firmware limitation in the phExNFCCcid project?

Are there any recommendations or firmware updates to improve handling of this race condition?

Could the firmware be modified to send a proper card absent error response before the timeout occurs?

Thank you very much for your assistance!

Best regards,