• Registered: 2010-06-22
  • Posts: 13

Topic: Unknown SAK reply

I have a card which replies with the following
ATQA (SENS_RES): 00 04
UID (NFCID): 8E BB 32 40
SAK (SEL_RES):53 04 00 00

So it is a MIFARE CLASSIC tag but the SAK doesn't correspond to any reported here..
http://www.libnfc.org/documentation/har … s/iso14443

What one has to do in these cases?

  • rconty
  • Administrator
  • Offline
  • Registered: 2009-04-22
  • Posts: 642

Re: Unknown SAK reply

Hello,

dreddolo wrote:

So it is a MIFARE CLASSIC tag but the SAK doesn't correspond to any reported here..
http://www.libnfc.org/documentation/har … s/iso14443

What one has to do in these cases?

Is your MIFARE Classic card is manufacturered by NXP ? AFAIK, NXP have designed MIFARE family and manufactured MIFARE tags but other manufacturers can produce MIFARE tags too (with probably an NXP license), with a different SAK.

PS: Just for test, could you try to run nfc-list with the stable 1.3.4 and re-run with lastest SVN ?

Romuald Conty
  • rconty
  • Administrator
  • Offline
  • Registered: 2009-04-22
  • Posts: 642

Re: Unknown SAK reply

This document could help to know which model and modulation do use each NXP's card type.

AN10833 - MIFARE Type Identification Procedure

Romuald Conty
  • Registered: 2010-06-22
  • Posts: 13

Re: Unknown SAK reply

Well i don't really know who manufactured the card.
I am using stable 1.3.4 but i did already implement a code by myself like the one in the latest SVN and the only modulation which the card answered to was ISO14443-a..
I did already see that document however i can't find a solution anyway smile

  • rconty
  • Administrator
  • Offline
  • Registered: 2009-04-22
  • Posts: 642

Re: Unknown SAK reply

Could try to run nfc-list with trunk ? It seems SAK retrieve failed: SAK is usually 1 byte long.

Romuald Conty