Forum Replies Created

  • Re: Reply To: SAM Master key change to PICC type after switch to AV2 mode

    17. July 2017 at 12:16
    in reply to: SAM Master key change to PICC type after switch to AV2 mode
    Hi,

    I know what you say. My problem os that the only key enable is the SAM Master key, and now that key is PICC type, and the autentications with SAM Master key return 6985.
    What is the solution?

    Thanks in advanced.
    + 0  |  - 0

    Re: Reply To: Meaning of expression

    10. July 2017 at 15:27
    in reply to: Meaning of expression
    Hi,

    Sorry but there was a problem with html processor. The expression I don't understand it's a part of that expression, that the html explorer deleted.

    The expression is \, that is inside the expression to calculate SV1.


    + 0  |  - 0

    Re: Reply To: DESFireEV1 WriteData error:"Boundary Error"

    6. February 2017 at 16:09
    in reply to: DESFireEV1 WriteData error:"Boundary Error"
    Hi,

    Yes I know that situation. The problem is that the WriteData command launchs the exception.
    + 0  |  - 0

    Re: Reply To: DESFireEV1 Authentication error

    4. January 2017 at 12:19
    in reply to: DESFireEV1 Authentication error
    Hi,

    Error Description: Setting the Access Rights of a Backup Data File to require the key number 1, the response to the ReadData command is Auhtnetication Error, although that the Authentication command with key number 1 was successfull.

    Android version: 5.1.1 API 22
    Phone model: Samsung Galaxy Core Prime

    Thanks in advanced

    Regards


    + 0  |  - 0

    Re: Reply To: DESFireEV1 Authentication error

    2. January 2017 at 15:40
    in reply to: DESFireEV1 Authentication error
    Hi,

    Sorry, but I don´t understand your response. I think you are confused with my problem. I'll try to explain in other words the bug.

    If I set the Access Rights of my file to require the key 1, The response to the read command is Auhtnetication Error, although that the Authentication command with key number 1 was successfull.
    We think there's an error in your library when we try to use key number different from 0.

    We have another library, in C++, to use MIFARE DESFire EV1/EV2 cards, and we are able to use all key numbers.

    Thanks in advance.
    + 0  |  - 0

    Re: Reply To: MIFARE DESFire EV1/EV2 not recognised

    30. November 2016 at 13:02
    in reply to: MIFARE DESFire EV1/EV2 not recognised
    Hi,

    I'm waiting for the new release, Is it released yet? If not, when will it be released?

    Thanks in advanced
    + 0  |  - 0

    Re: Reply To: MIFARE DESFire EV1/EV2 not recognised

    15. November 2016 at 9:40
    in reply to: MIFARE DESFire EV1/EV2 not recognised
    How do you announce the publication of the new release?

    Thanks
    + 0  |  - 0

    Re: Reply To: MIFARE DESFire EV1/EV2 not recognised

    3. November 2016 at 12:58
    in reply to: MIFARE DESFire EV1/EV2 not recognised
    HI,

    Do you have any notice about the bug?

    Thanks in advanced
    + 0  |  - 0

    Re: Reply To: MIFARE DESFire EV1/EV2 not recognised

    21. October 2016 at 11:49
    in reply to: MIFARE DESFire EV1/EV2 not recognised
    Hi,

    the manufacturer is Itos, and the phone model is IC-50SG.

    Thanks!
    + 0  |  - 0

    Re: Reply To: MIfare SDK Lite classes supported

    10. June 2016 at 10:21
    in reply to: MIfare SDK Lite classes supported
    Hi,

    I really appreciate your sincerity. it is important for me to know if the SDK Lite support the methods to use Backup Data Files and the commitTransaction() method from class com.nxp.nfclib.desfire.DESFireEV1.
    please, Could you answer this question?

    Thanks in advanced
    + 0  |  - 0
Viewing 10 posts - 1 through 10 (of 10 total)