NPC100(P1003) will be blocked when it detect a MIFARE nfc card

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

NPC100(P1003) will be blocked when it detect a MIFARE nfc card

1,003 Views
bert_li
Contributor I

Our devices have build a nfc reader with NPC100 module, When we update the android version to 7.1.1 from 5.1.1

NFC reader can not detect the MIFARE nfc card:

Log message:

05-14 08:50:54.690 1513 1744 D NxpTml : PN54X - I2C Read successful.....
05-14 08:50:54.690 1513 1744 D NxpNciR : len = 23 > 61051401808000FF010904000440A64DCD010800000000
05-14 08:50:54.690 1513 1744 D NxpTml : PN54X - Posting read message.....
05-14 08:50:54.690 1513 1747 D NxpHal : read successful status = 0x0
05-14 08:50:54.690 1513 1747 D NxpHal : NxpNci: RF Interface = MIFARE
05-14 08:50:54.690 1513 1747 D NxpHal : NxpNci: Protocol = MIFARE
05-14 08:50:54.690 1513 1747 D NxpHal : NxpNci: Mode = A Passive Poll
05-14 08:50:54.690 1513 1747 D NfcAdaptation: NfcAdaptation::HalDeviceContextDataCallback: len=23
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: NFC received ntf gid:1
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: p2p priority is running under bail out mode ONLY.
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: nfc_set_state 4 (IDLE)->5 (OPEN)
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: nfc_ncif_proc_activate:20 0, mode:0x00
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: nfa_dm_disc_discovery_cback (): event:0x4004
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: nfa_dm_disc_sm_execute (): state: DISCOVERY (1), event: ACTIVATED_NTF(5) disc_flags: 0x1
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: nfa_dm_disc_new_state (): old_state: DISCOVERY (1), new_state: POLL_ACTIVE (4) disc_flags: 0x1
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: nfa_dm_disc_notify_activation (): tech_n_mode:0x0, proto:0x5
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: nfa_dm_disc_get_disc_mask (): tech_n_mode:0x0, protocol:0x5, disc_mask:0x8
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: activated_protocol:0x5, activated_handle: 0x1
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: nfa_dm_poll_disc_cback (): event:0x01
05-14 08:50:54.690 1513 1715 I BrcmNfcNfa: nfa_dm_notify_activation_status (): status:0x0
05-14 08:50:54.690 1513 1715 D BrcmNfcJni: nfaConnectionCallback: event= 5
05-14 08:50:54.690 1513 1715 D BrcmNfcJni: nfaConnectionCallback: NFA_ACTIVATED_EVT: gIsSelectingRfInterface=0, sIsDisabling=0
05-14 08:50:54.690 1513 1715 D BrcmNfcJni: NfcTag::setActivationState: state=2
05-14 08:50:54.690 1513 1715 D BrcmNfcJni: nfaConnectionCallback: NFA_ACTIVATED_EVT; is p2p
05-14 08:50:54.690 1513 1715 D BrcmNfcJni: nfaConnectionCallback: Disabling RF field events
05-14 08:50:54.691 1513 1715 I BrcmNfcNfa: NFA_SetConfig (): param_id:0x80
05-14 08:50:54.691 1513 1715 D BrcmNfcJni: nfaConnectionCallback: Disabled RF field events
05-14 08:50:54.691 1513 1715 I BrcmNfcNfa: nfa_dm_disc_sm_execute (): new state: POLL_ACTIVE (4), disc_flags: 0x1
05-14 08:50:54.691 1513 1715 I BrcmNfcNfa: NFA got event 0x0102
05-14 08:50:54.691 1513 1715 I BrcmNfcNfa: nfa_dm_evt_hdlr event: NFA_DM_API_SET_CONFIG_EVT (0x02)
05-14 08:50:54.691 1513 1715 I BrcmNfcNfa: nfa_dm_check_set_config ()
05-14 08:50:54.691 1513 1715 D NfcAdaptation: NfcAdaptation::HalWrite
05-14 08:50:54.691 1513 1715 D NxpExtns: const CNfcParam *CNfcConfig::find(const char *) const found MIFARE_READER_ENABLE=
05-14 08:50:54.691 1513 1745 D NxpTml : PN54X - Write requested.....
05-14 08:50:54.691 1513 1745 D NxpTml : PN54X - Invoking I2C Write.....
05-14 08:50:54.691 1513 1744 D NxpTml : PN54X - Read requested.....
05-14 08:50:54.691 1513 1744 D NxpTml : PN54X - Invoking I2C Read.....
05-14 08:50:54.693 1513 1745 D NxpNciX : len = 7 > 20020401800100
05-14 08:50:54.693 1513 1745 D NxpTml : PN54X - I2C Write successful.....
05-14 08:50:54.693 1513 1745 D NxpTml : PN54X - Posting Fresh Write message.....
05-14 08:50:54.693 1513 1745 D NxpTml : PN54X - Tml Writer Thread Running................
05-14 08:50:54.693 1513 1747 D NxpHal : write successful status = 0x0
05-14 08:50:54.696 1513 1744 D NxpTml : PN54X - I2C Read successful.....
05-14 08:50:54.696 1513 1744 D NxpNciR : len = 4 > 40020106
05-14 08:50:54.696 1513 1744 D NxpTml : PN54X - Posting read message.....
05-14 08:50:54.696 1513 1747 D NxpHal : read successful status = 0x0
05-14 08:50:54.696 1513 1747 D NxpHal : > Deinit workaround for LLCP set_config 0x0 0x0 0x0
05-14 08:50:54.696 1513 1747 D NxpHal : phNxpNciHal_print_res_status: response status =STATUS_OK
05-14 08:50:54.696 1513 1747 D NfcAdaptation: NfcAdaptation::HalDeviceContextDataCallback: len=5
05-14 08:50:54.696 1513 1744 D NxpTml : PN54X - Read requested.....
05-14 08:50:54.696 1513 1715 I BrcmNfcNfa: NFC received rsp gid:0
05-14 08:50:54.696 1513 1744 D NxpTml : PN54X - Invoking I2C Read.....
05-14 08:50:54.696 1513 1715 I BrcmNfcNfa: nci_proc_core_rsp opcode:0x2
05-14 08:50:54.696 1513 1715 I BrcmNfcNfa: nfa_dm_nfc_response_cback () NFC_SET_CONFIG_REVT(0x5002)
05-14 08:50:54.696 1513 1715 D BrcmNfcJni: nfaDeviceManagementCallback: enter; event=0x2
05-14 08:50:54.696 1513 1715 D BrcmNfcJni: nfaDeviceManagementCallback: NFA_DM_SET_CONFIG_EVT

Labels (1)
0 Kudos
1 Reply

740 Views
Jonathan_Iglesias
NXP TechSupport
NXP TechSupport

the NPC100 is listed in our system as customer specific this means that all the documentation is confidential so  my recommendation to get a solution for your issue please contact your closest distributor or your closest NXP site so they get you in touch with  the sales team. my apologies for the inconvenience this means.

Have a great day !

BR

 

Jonathan

0 Kudos