Index is out of range when connect PN5190 with NFC Cockpit v7.2.0

[jeff_ho]

Hi NXP Team,

After I updated the DPC values and RF protocol configuration for Type A/B in the EEPROM, I found the RF power can't be measured when I execute the RF Field On. So I try to redownload the firmware 2.F6 to overwrite the EEPROM. 

But after I download the 2.F6 firmware, the cockpit always replies an Error: 

[2024.01.04 18:25:11]:ERROR:BoardConnectionViewModel:Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

May you please let me know what kind of error it is and how to fix it?

Thank you.

Best Regards,

Jeff

[jeff_ho]

Dear Eduardo,

Thank you for your reply. I use a normal board to connect the Nxp NFC cockpit v7.4.0 first and then connect the failed board to update the firmware to 2.F7. 

After successfully updating the firmware, I close and open the port. The NXP NFC cockpit shows the fail message below,

The detail log Monitor:

[2024.01.05 10:41:16]:INFO:BoardDetect:Enforcing board selection for PN5190
[2024.01.05 10:41:18]:INFO:ServiceFactory:Generating Services for VCOM_PN5190 @COM1
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:TX [009]: 7F 02 00 05 03 FE FF FF FF
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 02 00 01 00 FF FF FF FF
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:TX [006]: 7F 0D 00 02 00 80
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 0D 00 01 00 FF FF FF FF
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:TX [009]: 7F 00 00 05 32 7F 08 00 00
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 00 00 01 00 FF FF FF FF
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:TX [009]: 7F 00 00 05 11 7F 09 00 00
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 00 00 01 00 FF FF FF FF
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:TX [004]: 7F 27 00 00
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 27 00 05 00 52 02 F7 02
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:TX [004]: 7F 27 00 00
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 27 00 05 00 52 02 F7 02
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:TX [008]: 7F 07 00 04 00 00 01 00
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 07 00 02 00 E4 FF FF FF
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:TX [008]: 7F 07 00 04 3E 01 80 00
[2024.01.05 10:41:18]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 07 00 81 00 50 C2 20 82
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:RX [125]: FF 2A 80 15 80 34 81 7F 40 7F 00 30 00 20 00 1A 00 7F 40 7F 00 40 00 20 00 1A 00 7F 40 7F 00 40 00 20 00 1A 00 50 40 40 00 30 00 20 00 1A 00 7F 40 50 00 40 00 20 00 1A 00 7F 40 50 00 40 00 20 00 1A 00 7F 40 50 00 40 00 20 00 1A 00 7F 40 7F 00 40 00 20 00 1A 00 7F 40 7F 00 40 00 20 00 1A 00 0A 40 0A 00 0A 00 0A 00 0A 00 2F 40 2F 00 2F 00 0A 00 0A 00 1F 41 1F 01 1F 01 0A 01
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:TX [008]: 7F 07 00 04 BE 01 48 00
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 07 00 49 00 0A 01 2F 40
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:RX [069]: FF 2F 00 2F 00 0A 00 0A 00 2F 40 2F 00 2F 00 0A 00 0A 00 1F 40 1F 00 1F 01 1F 01 14 01 4F 40 4F 00 3F 00 1F 00 14 00 1F 40 1F 00 1F 01 1F 01 14 01 4F 40 4F 00 3F 00 1F 00 14 00 0A 40 0A 00 0A 00 0A 00 0A 00
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:TX [008]: 7F 07 00 04 9D 0C 0A 00
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 07 00 0B 00 50 C0 50 80
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:RX [007]: FF 50 80 50 80 2A 81
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:TX [008]: 7F 07 00 04 76 00 01 00
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 07 00 02 00 77 FF FF FF
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:TX [005]: 7F 04 00 01 56
[2024.01.05 10:41:19]:DEBUG:UcBalVComBalDelegate:RX [009]: FF 04 00 05 00 7F 1E 00 00
[2024.01.05 10:41:19]:ERROR:BoardConnectionViewModel:Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

Best Regards,

Jeff

[Fabian_R]

Hello sir,
This is Fabian, could you please clarify if is possible to access your board through NFC Cockpit? I'm interested in the values of the E2PROM with a Dump EEPROM button.
I also would like to know if after flashing the NFC Reader Library you were able to use your PN5190 correctly.

[jeff_ho]

Dear Fabian_R,

I just realized the Dump EEPROM button can't dump all EEPROM from the PN5190. After I manually fill each EEPROM value from the address 0x77 to 0x8A, my board can connect the Nxp NFC cockpit again.

The NFC Reader Library works fine on my board. But the RF power is very low. Just a few millivolts. 

The data sheet does not clarify every address of EEPROM. Is it possible that the tx/rx circuit was over-current and damaged?

Best Regards,

Jeff

[Fabian_R · Accepted solution]

Hello sir,
I wanted to check this with the E2PROM values. It is possible to damage the transmitter drivers by disabling the DPC and activating the RF field. Please take a look at the precautionary notes of RN00013. This applies to B1 and B2 IC versions.

https://www.nxp.com/docs/en/release-note/RN00013.pdf

[EduardoZamora]

Hello @jeff_ho,

Hope you are doing well.

Please, try flashing any example project from the NFC Reader Library to your device, this is only to confirm that it is working as expected and to restore any possible configuration to a known working state. After this, load the firmware binary for the usage with Cockpit according to the NFC Cockpit User Guide.

Also, there should be a newer version of the NFC Cockpit (7.4.0), could you please try using the latest version available?

Once you have flashed the NFC Cockpit binary into your device again, if it is not working, could you please share the complete log from the Log Monitor?

If you are still having issues, please do not hesitate to contact us.

Regards,
Eduardo.