Forum Replies Created

  • Re: Re: Custom APDU structures for Mifare

    11. April 2014 at 13:20     in reply to: Custom APDU structures for Mifare

    Yves
    Hello,

    MIFARE DESFire EV1 supports ISO7816 file System and a basic handling of ISO7816 Standard APDUs like SELECT and READ-BINARY. You may have a look in the datasheet for details about this. Probably that would allow you to replicate your application (provided you don't use encryption or secure messaging).
    However, if you're currently using custom APDUs within your Java applet, such APDUs won't be understood by a DESFire EV1.

    Best regards
    + 0  |  - 0

    Re: Re: What type of MIFARE is?

    9. April 2014 at 18:35     in reply to: What type of MIFARE is?

    Yves
    Hello,

    you can have a look at the app note "MIFARE Type Identification Procedure" (http://www.nxp.com/products/identification_and_security/smart_card_ics/mifare_smart_card_ics/).
    For some newer products (MIFARE DESFire EV1, MIFARE Ultralight EV1), there's as well a GetVersion() command which delivers more detailled Information on the IC type.
    + 1  |  - 1

    Re: Re: Change Uid with CLRC663

    21. March 2014 at 14:45     in reply to: Change Uid with CLRC663

    Yves
    Dear Yesilkaya,

    reading the subject ("Change UID"), I have the feeling you're using a non ISO14443 PICC.

    Keep in mind that such ICs with programmable UID are not supported from NXP technical support, as those ICs are unauthorized copies of MIFARE ICs. These ICs with programmable IDs are a threat to system security and system reliability.

    Best regards
    + 0  |  - 0
  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)