sometimes PN7150 failed to read tag until reboot app

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

sometimes PN7150 failed to read tag until reboot app

561 Views
dx1
Contributor II

we develop NFC apps with PN7150 ,The Android version is 10.0

Sometimes the tag reading will fail, you can restart the app, plug and unplug the USB, and wake up the screen to read it again。

The exception log is attached in the attachment。

Generally, what are the reasons for this phenomenon and what are the solutions。

0 Kudos
2 Replies

491 Views
danielchen
NXP TechSupport
NXP TechSupport

Hi Ethan:

 

I would suggest you check whether you can reproduce this issue with Taginfo App?

 

Regards

Daniel

0 Kudos

481 Views
dx1
Contributor II

Hi danielchen,

    Thanks for your reply!This problem also occurs with the TagInfo app,The information for scanning the card is as follows:

```
** TagInfo scan (version 4.25.3) 2023-01-12 10:17:59 **
Report Type: -- IC INFO ------------------------------

# IC manufacturer:
NXP Semiconductors

# IC type:
MIFARE Ultralight EV1 (MF0UL11)

-- NDEF ------------------------------

# No NDEF data storage populated:

-- EXTRA ------------------------------

# Memory size:
48 bytes user memory
* 12 pages, with 4 bytes per page

# IC information:
Full product name: MF0UL1101DUx

# Version information:
Vendor ID: NXP
Type: MIFARE Ultralight
Subtype: 17 pF
Major version: 1
Minor version: V0
Storage size: 48 bytes
Protocol: ISO/IEC 14443-3


# Originality Check (asymmetric):
Signature verified with NXP public key

# TagInfo Version:
Version :4.25.3

# Device Info:
Device Model :QUALCOMM ( qcm2150_32 )
Android OS Version :10

-- FULL SCAN ------------------------------

# Technologies supported:
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible

# Android technology information:
Tag description:
* TAG: Tech [android.nfc.tech.NfcA, android.nfc.tech.MifareUltralight]
* Maximum transceive length: 253 bytes
* Default maximum transceive time-out: 618 ms


# Detailed protocol information:
ID: 04:4C:7C:BA:5F:67:81
ATQA: 0x0F00
SAK: 0x00

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

 

There are system logs attached to the property,The watchdog triggered a reboot (line num:206306)

Tags (1)
0 Kudos