How to rewrite an EEPROM configeration when the crystal oscillator is abnormal

[Fanfei]

Hello NXP expert.

I'm working on the PN5190B1.

I try to modify the EEPROM configuration "XTAL_CHECK_DELAY" to 0xE1, and then the  IC seems not work now.

But what's more troublesome is that I can't modify this configuration back.

Is there any way to fix this problem?

[EduardoZamora]

Hello @Fanfei

Hope you are doing well.

When you mention that the IC seems not to work, could you please describe the issue you are seeing?

Is there any chance you could provide a capture with an oscilloscope of the XTAL to try to check if it is working properly? Example of measurement of these signals is described in Crystal Oscillator Design Guide, Annex 2.

What is the procedure you are following to try to modify this EEPROM configuration? By any chance, are you using the recommended tool NFC Cockpit?

Perhaps you can try using the Load EEPROM feature of NFC Cockpit. This feature loads a previous saved file, and stores is into the user area of EEPROM; you could "Dump" a known-good EEPROM configuration from a working device.

Also, even though they are many, EEPROM has limited write cycles. Is it possible that you have a exceeded them?

Regards,
Eduardo.

[Fanfei]

Hello @EduardoZamora
Thanks for you reply.
There is no signal neither XTAL1 or XTAL2.
I use the "NFC Reader Library" in my project, and I can't use NFC Cockpit.
After successfully calling the "phNfcLib_Init", a program for modifying the configuration of EERPOM was added. And the "phNfcLib_Init" return fail after modify the "XTAL_CHECK_DELAY" to 0xE1.
If the initialization error is ignored and write the EEPROM is directly, errors will also occur because there is no interrupt signal during SPI interaction.

[EduardoZamora]

Hi,

Just to confirm, was the device working properly before making the modification to XTAL_CHECK_DELAY in EEPROM?

Could you please describe the procedure you are following in your code to try to modify this EEPROM configuration? Is there any specific error code returned or log/output you could share?

The device performs some internal checks at startup, perhaps XTAL is not starting due to a bad component. Is it possible for you to replace the XTAL circuitry in your HW and test the functioning after this?

Regards,
Eduardo.

[Fanfei]

Hello,
The device works well before.
I found that "phNfcLib_Init" return error in stage of switch to normal mode, and the EEPROM can be configure if Ignore this error.
It seems working properly now.
Thanks for your help.

[EduardoZamora]

Hi,

Thank you for the update, it is good to know that it is working properly.

If you have any further questions, please let us know.

Regards,
Eduardo.