PN7160 design works but PN7161 doesn't work

[ELECHOUSE]

I designed PN7160 and PN7161 boards, with I2C port. I tested them with this library: GitHub - NXPNFCLinux/linux_libnfc-nci: Linux NFC stack for NCI based NXP NFC Controllers

I got the following result:

1. All PN7160 boards are working well.

2. All PN7161 boards are not working, failing at initiate.

PN7160 and PN7161 boards share the same design. I have no authorization from Apple for the ECP.

My questions:

1. W/o Apple authorization for the ECP, Will PN7161 work as PN7160, or never work at all?

2. Except the ECP, any other difference between PN7161 and PN7160?

Thanks

[ELECHOUSE]

Not sure if I could paste the link here: https://www.elechouse.com/product/pn7160-nfc-rfid-module/

We already solved all problems of PN7160 and PN7161 modules

[Omar_ahmed1234]

Can you help me please, 

I design nfc board with Pn7161 ic and have the problem in initiating. 

[Tomas_Parizek]

Hello ELECHOUSE,

Can you share what was the root cause of your issue,please ?

Thanks !
BR
Tomas

[mattiadorigo]

Hi Elechouse, I love your products! When do you think the PN7160 will be ready?

[danielchen]

Hi

The PN7161 has the same features as PN7160 with Apple Enhanced Contactless Polling (ECP ) feature supported.

All of the standard design principals used in the generic PN7160, also apply to the PN7161 includes additional contents but is form, fit and functionality identical to the PN7160.

PN7161 needs authorization from Apple

Regards

Daniel

[ELECHOUSE]

Thanks very much for your reply.

Do you mean without Apple's authoritarian, we could not use any function of PN7161? Even reading a normal tag (such as Mifare)?

[danielchen]

Hi

The PN7161 responds identically, as the PN7160, unless special ECP enablement is activated, then it just has more functionality. 

Regards

Daniel

[ELECHOUSE]

We made another 2pcs new PN7160 boards and 5pcs new PN7161 boards. Along with those 5pcs PN7160 boards we made last time, we have:

• PN7160 boards: 7pcs
• PN7161 boards: 5pcs

They have the same PCBA design. The testing result is:

• 7pcs PN7160 boards: all were working
• 5pcs PN7161 boards: none ever worked. All failed at initiating....

Testing tool: Rapberry Pi

Software: git clone https://github.com/NXPNFCLinux/linux_libnfc-nci.git -b NCI2.0_PN7160

Any suggestion would be appreciated!

Thanks

[nko]

Hi,

In an application we use the SPI version of the PN7161.
We do not use the apple ECP feature.
3 out of 5 PCBs produced in the same batch do not generate an RF signal, while there is communication via SPI.
Electronically there seem to be no connection problems.

Did you ever find out what the problem was?

Thank you in advance.

[nko]

Just an update on the above for future references:

Our problem is gone by applying the same solution mentioned in the following thread:
PN7160 TXLDO stays at 0V if VBAT is connected to 3V3 

In our case, the RF drive was controlled by 3V3, which apparently does not pass the TXLDO-Check in all cases. Disabling the TXLDO-Check generated the RF signal.

It is not clear why some PCBs pass the test and others do not.