NFCLIB init issues with PN7642 folowing a failed flash

[glev]

Hello,

A board for a ISO 15693 tag reader worked perfectly for two days of testing.

While working on another project I clicked on the wrong probe to flash the board, I accidently selected the probe my PN7642 board was connected to instead of the one for the other project.

The J-Link driver indicated "CPU not found" but the board reseted and started to reset every few seconds.

I can flash and run a program that doesn't require the NFC but if I try to run any program that uses the NFC the following message shows up and the program crashes.

"Line: 154 Error - (0x001E) has occurred in NFCLIB"

Did I damage something and is there a way to fix it ?

Thank you, have a nice day.

[KaiLi]

Hello @glev 

Is your board an NXP demo board? Are you running the NXP application routine? If so, which routine is it? I may need to run trace on my side.

BR

kelly

[glev]

Hello @KaiLi,

Thank you for your response.

This board is not an NXP demo board, but it's based on the same module as the PNEV7642A and the design is heavily inspired by the demo board. All the proper antenna matching has been done.

The two boards we have worked perfectly before this incident and the other one still does work with no issues.

I run a custom firmware based on the NfcrdlibEx5_ISO15693 example running freeRTOS, but I also tried running the NfcrdlibEx5_ISO15693 example directly with the same result.

"Line: 154 Error - (0x001E) has occurred in NFCLIB" at startup

The same programs work perfectly on the other board and the demo board. 

I'm using a J-LINK plus probe with IAR to program the device, I have added the proper JLINKscript. I also the direct storage method to program, with the same result.

Best Regards

Gwendal

[KaiLi]

Hello @glev 

So when you debug, can you locate which API the error occurred?

BR

Kelly

[glev]

Hello @KaiLi 

It seems to me that the error comes from the PN76_Sys_Clif_Init() function, returning 0x001E.

BR

Gwendal

[KaiLi · Accepted solution]

Hello @glev 

Could you try to update FW and test again?

[glev]

Hello,
It solved the problem, thank you !
However I had to use IAR to flash the firmware update project because mcuexpresso couldn't do it.
Thank you again for your help.
Gwendal