Forum Replies Created

  • Re: Re: Desifre card = Mifare 1K emulation

    22. June 2014 at 13:59     in reply to: Desifre card = Mifare 1K emulation

    Adnan
    Hi Paul,
    You probably meant MIFARE DESFire EV2. Classic emulation on DESFire EV2 will be available in future release (Not in the first release).
    regarding your business case: You can realize the same with DESFire EV1. You can have a file inside an application. The file will have free read access and no write access.
    By the way, what do you mean, no keys are used to lock down the card? in MIFARE Classic 1K, you got to authenticate with KeyA or KeyB (depending on access control).
    BR
    Adnan
    + 0  |  - 0

    Re: Re: DESFire EV2 ATQ bytes

    17. June 2014 at 15:48     in reply to: DESFire EV2 ATQ bytes

    Adnan
    Hi
    May i ask, why that is important? I have both Datasheet and DESFire EV2 card.
    You can drop me an email at adnan.abdulhai@nxp.com
    BR
    Adnan
    + 0  |  - 0

    Re: Re: DESFire EV2 ATQ bytes

    17. June 2014 at 15:31     in reply to: DESFire EV2 ATQ bytes

    Adnan
    Same as MIFARE DESFire EV1
    + 0  |  - 0

    Re: Re: Configure Mifare Plus SL3

    28. April 2014 at 11:01     in reply to: Configure Mifare Plus SL3

    Adnan
    Hi Stephane,
    MIFARE Plus X offers Proximity Check features in SL3. By default it is optional, but you can make it mandatory using Field Configuration Block.
    How to work with PC activated or how PC works are described in Datasheet (page 34 and page 76).
    You can get the Datasheet from our docstore.
    Regards
    Adnan
    + 0  |  - 0

    Re: Re: Ultralight?

    14. January 2014 at 14:59     in reply to: Ultralight?

    Adnan
    Ultralight EV1 offers FAST_Read command to read multiple pages in one single command/response
    + 0  |  - 0

    Re: Re: MIFARE DesFire EV1 Work Flow — Authentication Method and Date

    18. December 2013 at 18:52     in reply to: MIFARE DesFire EV1 Work Flow — Authentication Method and Date

    Adnan
    Possible. Please refer to datasheet.
    + 0  |  - 0

    Re: Re: MIFARE DesFire EV1 Work Flow — Authentication Method and Date

    3. December 2013 at 18:36     in reply to: MIFARE DesFire EV1 Work Flow — Authentication Method and Date

    Adnan
    Hi,
    MIFARE Classic and DESFire EV1 are two different sort of cards. Classic is sectors-blocks oriented where as DESFire Ev1 is applications-files oriented.
    Authentication in EV1 is based on challenge - Response. Please refer to datasheet.
    There are also DESFire Application note describing the authentication procedure.
    The datasheet and Application notes are available at our docstore(http://docstore.nxp.com/).
    Br
    Adnan
    + 0  |  - 0

    Re: Re: SAK response on the Classic next generation tags.

    17. October 2013 at 22:16     in reply to: SAK response on the Classic next generation tags.

    Adnan
    Hi Aitor,
    Thanks for your question.


    SAK response of MIFARE Classic is 0x08 (final response, i.e. CL2).

    SAK response for Double size UID in CL1 is 0x04 (Without MIFARE Desfire). Which means UID is not finished yet.

    Now if you use NUID mapping enabled, you have only CL1 and and the SAK will be 0x08.

    Page 10 of AN10833 is talking about SAK in CL1 for double size UID (thats why 0x04).

    Hope its clear now.
    BR
    Adnan
    + 0  |  - 0
  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)