MIFARE CLASSIC 1k CARD

[SLianksnc]

Hello, I would like to ask how to read your company's M1 card with ST's NFC reader ST25R3920B. ST card readers support the communication of mifare-classic cards, but they don't support the encryption part of M card. Is there demo code to provide it?

你好，我想问一下如何使用ST的NFC读卡器ST25R3920B读取贵公司的M1卡？ST读卡器支持mifare-classic类型卡片的通讯，但是他们不支持M卡的加密部分，是否有demo code提供？

[SLianksnc]

Hi Daniel

Thank you for your reply.

I still have a question. In the process of learning and certification of M card,What do M cards usually learn when studying? Is it a UID or a custom value? Then, the content of this study needs to be used for authentication when authenticating.

BR

SLian

[SLianksnc]

The process of learning is to bind the card to the card reader, such as writing the card ID into the EEPROM of the card reader.

After binding, every time a card is identified, it needs to be authenticated. The content of authentication is the content in the EEPROM of the card reader, and only the bound card can be authenticated successfully.

My main doubt is, is the general binding content a card UID or a user-defined value?

[Daniel_Gutierrez]

Hello @SLianksnc, Good Day!

The UID of the card is used for performing the selection of the card before any memory operations. Once the card has been selected the 3 pass authentication has to take place in order to be able to perform memory operations.

This procedure is described in detail in section 12.1 of the MIFARE Classic EV1 1K Data Sheet. For the authentication, one of the two secret keys (for each block) stored in the EEPROM of the card is used.  The value of these keys is set to FFFF FFFF FFFFh at chip delivery.

Please consider that for being able to perform memory operations with a MIFARE Classic card, an NFC reader IC for MIFARE products is required. Please have a look at our recommended NFC Readers Portfolio in order to find a suitable option for your application.

My best regards,
Daniel

[SLianksnc]

Hi Daniel:

Thanks for your reply, I still have a problem.Do the SELECT part and 3 PASS AUTHENTICATION part belong to ISO 14443-4? Does MIFARE Classic card support ISO14443-4?

BR

SLian

[Daniel_Gutierrez]

Hello @SLianksnc, Good Day!

Communication with the MIFARE Classic card is compliant with the ISO/IEC 14443 Type A standard, including the selection and anticollision sequence.

The mutual three pass authentication procedure is implemented according to the ISO/IEC DIS 9798 standard which focuses on entity authentication.

My best regards,
Daniel

[SLianksnc]

Hi Daniel

Thank you for your answer to help me solve this problem. Thank you.

BR

SLian

[RajPadmani]

Hello

I am using st25r200 reader to detect the mifare classic 4k card and perform read/write operations. but st25r200 does not support the auth function unlike mfrc522 reader for auth of the sector.
i tried to handle the auth process as per the card datasheet but it return the timeout, crc or frame formatting error of the [auth cmd + block].
if you have any reference please share.

thank you

[Daniel_Gutierrez · Accepted solution]

Hello @SLianksnc, Good Day!

Thank you very much for your interest in our products.

Communication with MIFARE Classic EV1 1K - 4K takes place according to the ISO/IEC 14443A protocol. Please refer to ISO/IEC 14443A documentation for further details regarding the construction of the communication frame.

You may also take a look at section 8 of the MIFARE Classic EV1 1K  Data Sheet in order to get an overview of the process followed to be able to perform memory operations such as reading blocks of the card. As well as section 9 which offers a command overview.

You may also find useful the MIFARE ISO/IEC 14443 PICC selection document which offers a detailed description of the process for selecting the right card and application.

Access to additional information as well as supporting software for this product requires an approved NDA as it is part of NXP's secure resources. Please refer to Non-Disclosure Agreement FAQs in order to find out more about the process of requesting an NDA.

My best regards,
Daniel