PN5190 EnBootNormalMode Error

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

PN5190 EnBootNormalMode Error

1,854 Views
rayjoel
Contributor I

Hi, supporters!

    We are developing a reader with the PN5190.

    Some readers are failed to initialize the PN5190 when it calls the function phhalHw_Pn5190_EnBootNormalMode, it returns error.

Normally when the PN5190 works well, the initial SPI datas are:

Host Send:4
7F 20 01 00

Host Recv:4
FF 80 00 08

Host Recv:9
FF 01 00 00 00 01 00 00 00

------------------------------------------------

But some PN5190 are always failed to work , the initial SPI datas are:

Host Send:4
7F 20 01 00

Host Recv:4
FF 80 00 0C

Host Recv:13
FF 03 00 00 00 01 00 00 00 03 00 00 00

-----------------------------------------------

How can we fix the problems ?

       

0 Kudos
Reply
6 Replies

1,142 Views
renkebienert
NXP Employee
NXP Employee

Hi all,

sorry for late reply!

We investigated and found some rare issues with fast crystals. These issues can be fixed with these new PN5190 EEPROM settings:

adr. 0x4BD -> 0x94

adr. 0x4BE -> 0x7F

BTW: this applies for every FW.

BR,

Renke

901 Views
dx1
Contributor II

Dear @renkebienert ,

I read the default configuration, the FW is v2.7. It is shown below:

adr. 0x4BD -> 0x7F

adr. 0x4BE -> 0x94

The configuration is just the opposite. Maybe it's written incorrectly, or maybe it's just about to swap the values?

0 Kudos
Reply

1,558 Views
renkebienert
NXP Employee
NXP Employee

Event: FF 80 00 0C 03 00 00 00 01 00 00 00 03 00 00 00

Refer to Instruction layer (nxp.com)

Event Status 0x00 00 00 03:

1) BOOT_EVENT -> OK, to be expected

2) GENERAL_ERROR_EVENT -> not OK, so let us check the 

 

GENERAL_ERROR_STATUS_DATA 0x 00 00 00 03:

CLOCK_ERROR and GPADC_ERROR

This looks like the x-tal does not start properly or fast enough.

For debugging the XTAL_CHECK_DELAY (address 0013h) EEPROM configuration, can be increased:

0xFF instead of 0xF6 (default) increase the interval and releases the start-up time.

However, it might make sense to change the x-tal (design), if it is too slow...

0 Kudos
Reply

1,548 Views
dx1
Contributor II

Hi @renkebienert 

The Firmware versions upgrade to V2.F6 from V2.01,The problem is solved。

But we have a large number of products, Upgrade all is a lot of work, is there a way to fix this problem without upgrading the firmware

0 Kudos
Reply

1,555 Views
dx1
Contributor II

Hi rekebientert,

Thanks for your reply!

We tried the following, but it still doesn't work:

1、XTAL_CHECK_DELAY:0xFF instead of 0xF6

2、Increase reset timing time PHHAL_HW_PN5190_RESET_DELAY_MILLI_SECS:10 ms  instead of 0xF6

The Firmware versions we used is V2.01,could it be because of this?

But we can't update the firmware right now because EnBootNormalMode Error,Is there any way to factory reset?

 

0 Kudos
Reply

1,583 Views
dx1
Contributor II

Hi,I have the same problem, can you solve it?

0 Kudos
Reply