NFC reader chip selection for public door application

[hernan26]

Hi.

We are selecting a NFC chip for a public door application and need some help for deciding.

My requirements:

- We will be using our own MCU.

- NFC Low Power detection since my Door reader is a battery-powered device.

- Need to support NFC passive tags, Android phones and Apple Phones.

My questions:

- Is ECP mandatory for interfacing Apple Phones? or is it only required  for using Apple wallet?

- Which is the base strategy in my NFC chip for interfacing mobile phones? HCE or P2P? other?

- I would like to avoid integrating NfcRdLib in my MCU. Is this possible to do this by using PN7462 with standard FW pre-programmed provided by NXP? we do not want to programm the PN7462.

- If I use the PN5190 along with NfcRdLib integrated in my own MCU, is it possible to interface Apple devices (either via wallet or via custom App).

Any assistance will be appreciated.

Regards, Ramon.

[Habib_MS]

Hello @hernan26,
Answering your questions.
- Is ECP mandatory for interfacing Apple Phones? or is it only required for using Apple wallet?
Yes, is required to interfacing in apple phones. ECP is development by Apple, so you need permission from Apple to use ECP in your design. With Apple's permission, you need to integrate the ECP into your system.

- Which is the base strategy in my NFC chip for interfacing mobile phones? HCE or P2P? other?
We recommend use the HCE interface, since P2P is slowly removed from the market. You can use the NFC library to implement HCE, which offers some examples demonstrating this functionality.

- I would like to avoid integrating NfcRdLib in my MCU. Is this possible to do this by using PN7462 with standard FW pre-programmed provided by NXP? we do not want to programm the PN7462.

In order to support you better, could you clarify me if this phrase "we do not want to program" refers to only program the device or develop your own code?

Software we offer for PN7462 is only for demonstration purposes, therefore, the PN7462 needs to be programed to implement the functionality your application/project requires.

If you are looking for an end product or solution, you can explore the Partner Marketplace | NXP Semiconductors, which offers solutions that can be integrated into your system.

- If I use the PN5190 along with NfcRdLib integrated in my own MCU, is it possible to interface Apple devices (either via wallet or via custom App).

There is a software package ready to showcase ECP and its functionality. However, this software can only be handed out on request (through your local Distributor or NXP Sales representative) and if you are approved by Apple.

BR
Habib

[hernan26]

Thanks for your kind response. Let me confirm some details in blue below.

Answering your questions.
- Is ECP mandatory for interfacing Apple Phones? or is it only required for using Apple wallet?
Yes, is required to interfacing in apple phones. ECP is development by Apple, so you need permission from Apple to use ECP in your design. With Apple's permission, you need to integrate the ECP into your system.

I am aware P2P mode is outphased and not recommended to be used, but are you sure it is not possible to use P2P in order to connect my NFC chip (e.g. PN5190) with an app running in iOS.

- Which is the base strategy in my NFC chip for interfacing mobile phones? HCE or P2P? other?
We recommend use the HCE interface, since P2P is slowly removed from the market. You can use the NFC library to implement HCE, which offers some examples demonstrating this functionality.

- I would like to avoid integrating NfcRdLib in my MCU. Is this possible to do this by using PN7462 with standard FW pre-programmed provided by NXP? we do not want to programm the PN7462.

In order to support you better, could you clarify me if this phrase "we do not want to program" refers to only program the device or develop your own code?

Software we offer for PN7462 is only for demonstration purposes, therefore, the PN7462 needs to be programed to implement the functionality your application/project requires.

If you are looking for an end product or solution, you can explore the Partner Marketplace | NXP Semiconductors, which offers solutions that can be integrated into your system.

- If I use the PN5190 along with NfcRdLib integrated in my own MCU, is it possible to interface Apple devices (either via wallet or via custom App).

There is a software package ready to showcase ECP and its functionality. However, this software can only be handed out on request (through your local Distributor or NXP Sales representative) and if you are approved by Apple.

If PN5190 supports ECP i do not understand why it is not specified in DS just as it is specified in other parts such as PN7220/1 or others.

Is there any reason for that I am not seeing?

Regards, Ramon.

[Habib_MS]

Hello @hernan26,
Unfortunately peer-to-peer functionality has never supported by iOS devices. Moreover, since Android 12, P2P functionality is not included by default in the main package. For these reasons, P2P is not recommended for new designs.
On the other hand, some devices have variants with dedicated hardware designed for support ECP, for example PN7221 or PN7161. Because of this, some devices mentioned specifically ECP support.

BR
Habib