Mifare Classic Authentication Error – Taplinx & Native Android NFC

Forum / MIFARE and NFC Reader IC`s / Mifare Classic Authentication Error – Taplinx & Native Android NFC

  • 10. September 2019 at 6:31
    Hey Folks,

    Re-opening a thread as the old one got hi-jacked but we've been seeing a continual issue with NXP548 chip and the android OS when it comes to authenticating mifare classic 1K cards, we don't see the same issue when the 547 chip is used in the same phone (older model).

    The following is returned from the android logs when attempting to authenticate with a the chip - this can be worked around by adding a loop and attempting to authenticate over and over again however my concern is that if we're seeing failures during the authentication step we'd possibly also see degraded performance in other operations when dealing with the chip.

    We've tried it on numerous devices with the 548 chip and ruled out the chip AND a singular device as being defective (as it spans multiple manufacturers).


    2019-09-10 14:05:02.353 1791-1878/? I/BrcmNfcNfa: nfa_dm_disc_sm_execute (): new state: W4_HOST_SELECT (3), disc_flags: 0x1
    2019-09-10 14:05:02.356 1791-1888/? D/NxpTml: PN54X - I2C Read successful.....
    2019-09-10 14:05:02.356 1791-1888/? D/NxpNciR: len = 23 > 61051401808000FF01090400043D343159010800000000
    2019-09-10 14:05:02.356 1791-1888/? D/NxpTml: PN54X - Posting read message.....
    2019-09-10 14:05:02.356 1791-1891/? D/NxpHal: read successful status = 0x0
    2019-09-10 14:05:02.356 1791-1891/? D/NxpHal: NxpNci: RF Interface = MIFARE
    2019-09-10 14:05:02.356 1791-1891/? D/NxpHal: NxpNci: Protocol = MIFARE
    2019-09-10 14:05:02.356 1791-1891/? D/NxpHal: NxpNci: Mode = A Passive Poll
    2019-09-10 14:05:02.356 1791-1891/? D/NfcAdaptation: NfcAdaptation::HalDeviceContextDataCallback: len=23
    2019-09-10 14:05:02.356 1791-1888/? D/NxpTml: PN54X - Read requested.....
    2019-09-10 14:05:02.356 1791-1888/? D/NxpTml: PN54X - Invoking I2C Read.....
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: NFC received ntf gid:1
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: returning from nfa_dm_p2p_prio_logic Disable p2p_prio_logic
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfc_set_state 4 (IDLE)->5 (OPEN)
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfc_ncif_proc_activate:20 0, mode:0x00
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfa_dm_disc_discovery_cback (): event:0x4004
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfa_dm_disc_sm_execute (): state: W4_HOST_SELECT (3), event: ACTIVATED_NTF(5) disc_flags: 0x1
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfa_dm_disc_new_state (): old_state: W4_HOST_SELECT (3), new_state: POLL_ACTIVE (4) disc_flags: 0x1
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfa_dm_disc_notify_activation (): tech_n_mode:0x0, proto:0x80
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfa_dm_disc_get_disc_mask (): tech_n_mode:0x0, protocol:0x80, disc_mask:0x2000
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: activated_protocol:0x80, activated_handle: 0x1
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfa_dm_poll_disc_cback (): event:0x01
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfa_rw_handle_event event: NFA_RW_ACTIVATE_NTF_EVT (0x601), flags: 00000001
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfa_rw_activate_ntf
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfa_dm_notify_activation_status (): status:0x0
    2019-09-10 14:05:02.356 1791-1878/? D/BrcmNfcJni: nfaConnectionCallback: event= 5
    2019-09-10 14:05:02.356 1791-1878/? D/BrcmNfcJni: nfaConnectionCallback: NFA_ACTIVATED_EVT: gIsSelectingRfInterface=1, sIsDisabling=0
    2019-09-10 14:05:02.356 1791-1878/? D/BrcmNfcJni: checkforTranscation: enter; event=0x5 transaction_data.current_transcation_state = 0x0
    2019-09-10 14:05:02.356 1791-1878/? D/BrcmNfcJni: checkforTranscation: exit; event=0x5 transaction_data.current_transcation_state = 0x0
    2019-09-10 14:05:02.356 1791-1878/? D/BrcmNfcJni: NfcTag::setActivationState: state=2
    2019-09-10 14:05:02.356 1791-1878/? I/BrcmNfcNfa: nfa_dm_disc_sm_execute (): new state: POLL_ACTIVE (4), disc_flags: 0x1
    2019-09-10 14:05:02.357 1791-1945/? D/BrcmNfcJni: reSelect: select completed; sConnectOk=1
    2019-09-10 14:05:02.357 1791-1945/? D/BrcmNfcJni: setReconnectState = 0x0
    2019-09-10 14:05:02.357 1791-1945/? I/BrcmNfcNfa: NFA_SetReconnectState = 0x0
    2019-09-10 14:05:02.357 1791-1945/? D/BrcmNfcJni: reSelect: exit; status=0
    2019-09-10 14:05:02.357 1791-1945/? D/BrcmNfcJni: nativeNfcTag_doReconnect: exit 0x0
    2019-09-10 14:05:02.357 1791-1945/? D/BrcmNfcJni: nativeNfcTag_doTransceive: exit
    2019-09-10 14:05:02.358 4344-4590/au.com.ticketbooth.rfid.android E/Authentication Failed: error
    com.nxp.nfclib.exceptions.SecurityException: Authentication Failed
    at com.nxp.nfclib.classic.MFClassic.authenticateSectorWithKeyA(:330)
    at au.com.ticketbooth.rfid.android.cardsOperations.ClassicCardOperations.authenticate(ClassicCardOperations.java:42)

    + 0  |  - 0

    Re: Mifare Classic Authentication Error – Taplinx & Native Android NFC

    10. September 2019 at 9:51
    Hi Matthew,

    The PN547 and PN548 are mobile chips. Please contact the team under this link:

    TIC Support

    The TapLinx team

    + 0  |  - 0
Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.