How to solve NFC PN7150 Internal Assert issue.

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

How to solve NFC PN7150 Internal Assert issue.

Jump to solution
2,024 Views
JagirMehta
Contributor II

Hello,

I am using NXP PN7150 for my project, In that, I have faced No RF field generation.
While checking it's debug logs i got CORE_RESET_NTF from PN7150 after start discovery command.
Whole notification :
NCI >> 21 03 09 04 00 01 01 01 02 01 06 01 (Start Discovery)
NCI << 60 00 06 a0 00 00 00 00 00 (Core reset notification)

As per PN7150 User manual UM10936(4.3.8) i find the core reset reason.
An assert has triggered PN7150 reset/reboot

Does it mean that PN7150 got damaged ? if not how do i recover it ?
Can i know the possible reason of this issue ?

PN7150_Issue.PNG

Labels (1)
Tags (3)
1 Solution
1,978 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @JagirMehta ,

 

Thanks for the information!  The above trace shows EEPROM memory corruption issue, confirmed then by the CORE_RESET_NTF  when starting the discovery.

See UM10936 §10.3 for more details about this EEPROM memory corruption issue.

Unfortunately there is no way to recover from this issue. Sorry for the inconvenience that has caused.

 

Have a great day,
Kan


-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

View solution in original post

4 Replies
1,998 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @JagirMehta ,

 

Is your project based on NXP NCI lib? Is it possible to share the whole NCI log with us for a review?

 

Thanks for your patience!

 

Have a great day,
Kan


-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos
1,994 Views
JagirMehta
Contributor II

Hello @Kan_Li ,

yes, My project is based on NXP NCI lib.

I have attached NCI Log for your reference

 

0 Kudos
1,979 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @JagirMehta ,

 

Thanks for the information!  The above trace shows EEPROM memory corruption issue, confirmed then by the CORE_RESET_NTF  when starting the discovery.

See UM10936 §10.3 for more details about this EEPROM memory corruption issue.

Unfortunately there is no way to recover from this issue. Sorry for the inconvenience that has caused.

 

Have a great day,
Kan


-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

1,954 Views
JagirMehta
Contributor II
Hello Kan Li,
I did go through the possible cause for the EEPROM Corruption issue.
But is it the only cause for it ?
I mean send NCI command to PN7150 for which it does some read/write in EEPROM & at that point of time if electricity cut off happens, then it will corrupt EEPROM, right ?
 
If this corruption happens for the above-mentioned scenario only then I think it's the vulnerability of the chipset only.
 
Please correct me if I wrong.
0 Kudos