Forum Replies Created

  • Re: Reply To: NTAG 424 DNA: writing NDEF throws `6985` error

    27. June 2019 at 19:24
    in reply to: NTAG 424 DNA: writing NDEF throws `6985` error
    Dear colleagues,

    Please let me know if any other info is needed for investigation.
    I would appreciate any advice from your side.

    Best regards,
    Dmitry Solgalov
    + 0  |  - 0

    Re: Reply To: NTAG 424 DNA: writing NDEF throws `6985` error

    24. June 2019 at 11:11
    in reply to: NTAG 424 DNA: writing NDEF throws `6985` error
    Dear colleagues,

    do you have any news on the matter of this topic?
    + 0  |  - 0

    Re: Reply To: NTAG 424 DNA: writing NDEF throws `6985` error

    19. June 2019 at 12:06
    in reply to: NTAG 424 DNA: writing NDEF throws `6985` error
    I've also tried a code from the SDK's sample and it caused another error:
    com.nxp.nfclib.exceptions.PICCException: Error : 91AE
    at com.nxp.nfclib.desfire.ᐝ.ˏ(:11068)
    at com.nxp.nfclib.desfire.י.ˎ(:5223)
    at com.nxp.nfclib.desfire.ᵋ.ˋ(:12050)
    at com.nxp.nfclib.desfire.ᵗ.writeData(:344)
    at com.nxp.nfclib.desfire.ᵗ.writeData(:331)
    at com.nxp.nfclib.desfire.ᵗ.writeData(:313)

    The code snippet:

    if (nfcTag instanceof INTAG424DNA) {
    INTAG424DNA ntag424DNA = (INTAG424DNA)nfcTag;
    ntag424DNA.isoSelectApplicationByDFName(NTAG424DNA_APP_NAME);
    KeyData aesKeyData = new KeyData();
    Key keyDefault = new SecretKeySpec(KEY_AES128_DEFAULT, "AES");
    aesKeyData.setKey(keyDefault);
    ntag424DNA.authenticateEV2First(0, aesKeyData, null);
    ntag424DNA.getReader().setTimeout(2000);
    ntag424DNA.writeData(03, 0, data);
    }

    + 0  |  - 0

    Re: Reply To: NTAG 424 DNA: writing NDEF throws `6985` error

    18. June 2019 at 19:18
    in reply to: NTAG 424 DNA: writing NDEF throws `6985` error
    Dear TapLinx Support team!

    Please find a code that causes the error below:

    byte[] payload = Utilities.append(
    NDEF_VERSION,
    MIRROR_PLACEHOLDER.getBytes(),
    //our business info
    );

    ICard mTag;
    if (CardType.NTAG424DNA.equals(cardType)) {
    mTag = DESFireFactory.getInstance().getNTAG424DNA(customModules);
    } else if (CardType.NTAG424DNATagTamper.equals(cardType)) {
    mTag = DESFireFactory.getInstance().getNTAG424DNATT(customModules);
    }

    NdefRecordWrapper ndefRecordWrapper = NdefRecordWrapper.createMime(CUSTOM_MIME_TYPE, payload);
    NdefMessageWrapper ndef = new NdefMessageWrapper(ndefRecordWrapper);
    ((INdefOperations) nfcTag).writeNDEF(ndef);

    + 0  |  - 0

    Re: Reply To: makeCardReadOnly() doesn't lock all pages

    18. January 2019 at 15:23
    in reply to: makeCardReadOnly() doesn't lock all pages
    Thank you for the clarification!

    Could you please advise something regarding my second question: "Is it possible to lock the pages 0x28--0x2A via TapLinx SDK?" ?


    + 0  |  - 0

    Re: Reply To: makeCardReadOnly() doesn't lock all pages

    15. January 2019 at 16:15
    in reply to: makeCardReadOnly() doesn't lock all pages
    Dear TapLinx team, thank you for the response.

    Could you please clarify which pages is in scope of makeCardReadOnly() method? Why does 0x03 (CC) page stay intact?
    Is it possible to lock the pages 0x28--0x2A via TapLinx SDK? I saw NTAGs with these pages locked, so I conclude that it is possible from the technical point of view.

    Best regards,
    Dmitry Solgalov
    + 0  |  - 0

    Re: Reply To: makeCardReadOnly() doesn't lock all pages

    10. January 2019 at 18:40
    in reply to: makeCardReadOnly() doesn't lock all pages
    BTW, I tried to fulfill "Lock tag" function from the NXP TagWriter app and got the same results. Is it a bug or a feature?
    + 0  |  - 0
Viewing 7 posts - 1 through 7 (of 7 total)