PN5190 FW2.3 How to breke the EEPROM

[nori]

Regarding PN5190 FW2.5, we got this information.

"NXP discovered a minor issue with the PN5190, if the VEN (=N_RESET) is toggling while some internal startup sequence is running. This can cause a corrupted EEPROM."

Therefore

I would like to test and confirm that EEPROM is broken by actually putting togging in VEN.

Please tell me how timing and how toggle should I use to destroy it.

[danielchen]

Hi NORI:

First of all:  there is no bug known in the PN5190 FW2.3.  All updates from 2.3 to 2.5 are improvements in functionality or new features.

The PN5190 might detect a violation of the Startup timing (as described in the datasheet) as a potential “attack”.

With FW2.3 or lower, the PN5190 writes the resulting error into EEPROM, which then might cause a failure during booting, since the boot sequence checks the EEPROM consistency. Then the PN5190 starts and stays in Download mode, and only a secure FW flash can recover from that.

With FW2.5 or higher, the PN5190 uses an Event status after booting to indicate such an error to the host after booting. That is all.

In neither case the EEPROM is broken.

Regards

NXP technical support.