topic Re: Problem with PN5180 firmware 4.0 and DPC enabled. in NFC

Problem with PN5180 firmware 4.0 and DPC enabled.

marcinbaliniak — Wed, 05 Jan 2022 11:48:52 GMT

Hi,

Recently we did some soak test on our products.

Basically, procedure looks like this:
11:58:28.630 - Get tag count req...
11:58:28.725 - TAG is found: 04DA044A5C6684
11:58:28.725 - Writing random value to page 5 - this is phalMful_Write()
11:58:28.949 - Reading test page - this is phalMful_Read()
11:58:28.965 - Read page OK
11:58:28.965 - Write test passed
11:58:28.981 - HALT done

This is repeated 3000 times.

And this procedure on the PN5180 firmware 3.5 is fine - 0 errors. But when we use the same procedure on board with PN5180 running firmware 4.0 we have some errors when writing or reading - mostly 0x0203 (PH_COMP_PAL_ISO14443P3A + PH_ERR_COLLISION_ERROR) or 0x0201 (PH_COMP_PAL_ISO14443P3A + PH_ERR_IO_TIMEOUT) - about 30 errors for 3000 cycles of test above.

What we found already when changing EEPROM settings to disable DPC (writing value 0x00 to register 0x59, other EEPROM values left as default) the problem disappears.

NPXLib we are using is 5.12. We know that we can upgrade NXPLib but I don't know if something related to this problem was reported or fixed.

Can you suggest any other than DPC solution to this problem? DPC is a nice feature and we want to keep it on our products.

Marcin.

Re: Problem with PN5180 firmware 4.0 and DPC enabled.

danielchen — Fri, 21 Jan 2022 02:28:46 GMT

Hi Marcin:

I would suggest you check the differences between version 3.5 and version 4.0.

The differences are listed on PN5180 datasheet.

If some parameters modified , and you can use cockpit to adjust the relevant settings.

Here is an application note about dynamic power control.

https://www.nxp.com/docs/en/application-note/AN11742.pdf

Regards

Daniel

Re: Problem with PN5180 firmware 4.0 and DPC enabled.

marcinbaliniak — Wed, 23 Mar 2022 09:02:06 GMT

But we are running the same tests with the chips already received with firmware 4.0 not upgraded by us to 4.0 so I believe all DPC settings are already adopted to this firmware.

Anything else to check ?