[TapLinx Support]

Hello Jesse,

Currently TapLinx iOS only supports MIFARE DESFire EV2. NTAG424DNA/NTAGDNATT card support will be available in the next release of TapLinx iOS. We suggest you to use native CoreNFC iOS APIs. Use NFCTagReaderSession and then NFCISO7816Tag protocol. You’ll be able to send any ISO7816 type command aka NTAGs APDUs.

https://developer.apple.com/documentation/corenfc/nfciso7816tag
https://developer.apple.com/documentation/corenfc/nfciso7816apdu

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Dear AppDev Luxone,

The permission denied exception is a result of missing authentication in the internal call of the isT4T() API within writeNDEf() API during Native communication.
However, API functions as expected when using ISO communication using the isoSelectFile command internally for execution.

This issue is being addressed and will be fixed in the upcoming release.

As a workaround would be to utilize the ISO command set for the T4T NDEF APIs.

desFireEV1.setCommandSet(IDESFireEV1.CommandSet.ISO);

Furthermore, please take note of a specific detail regarding the formatT4T function. The size parameter for the formatT4T function should be the length of the NDEF data to be written, plus an additional 2 bytes or more.

For example:
desFireEV1.formatT4T(nDef.getByteArrayLength() +2);
desFireEV1.writeNDEF(nDef);

This ensures the proper functioning of the writeNDEF API. In the event that the format is executed for an exact number of bytes or lesser to be written, Boundary Error (BE) Exception will be thrown from the writeNDEF API.

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Hello,

Please check latest Application Notes on
https://www.mifare.net/developer/home/

Best regards,
TapLinx

---

+ 0  |  - 0

[TapLinx Support]

Hello,

TapLinx SDK offers open API only for so called Reader/Writer mode. Host Card Emulation (HCE) which enables emulating a Smart Card/Tag is not supported. NXP supports HCE within reach NFC reader ICs portfolio in form of reader library. You can continue your journey here:
https://www.nxp.com/products/rfid-nfc/nfc-hf/nfc-readers:NFC-READER

For any additional query please contact NXP Support team on nxp.com.

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Dear Rob, TapLinx community.

We have found out that there is a bug with Inspire Portal URL in the latest Taplinx iOS release. We are planning for a bug fix release asap.

Please excuse inconvenience caused.

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Dear Oliver,

As of today all links are working. Please try again.


Best regards,
TapLinx

---

+ 0  |  - 0

[TapLinx Support]

Hello David,

Please note that Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Within IDE you can create an application and after, you can import TapLinx SDK into your application.

NTAG 424 DNA can be configured as Read-Only with help of SDK. Please check APPLICATION NOTE - NTAG 424 DNA and NTAG 424 DNA TagTamper features and hints, chapter "6.15 Write to CC - using Cmd.WriteData, CommMode.PLAIN". Two things to do to transition into Read-only life-cycle:

• Write read-only byte into CC file (E103)*
• Set WRITE access rights of NDEF file to 0xN (N = number of any key from 0 to 4, so write access for the ones knowing that key) or 0xF (no WRITE access for anyone)

* In order to write/change data to CC File, you need to Authenticate before with key 0x00.

Method to use to change access rights:
changeFileSettings(int fileNumber, NTAG424DNAFileSettings fileSettings)


Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Dear Parthsaradhi,

For the case when you already successfully executed the transition with Pegoda reader:
With help of RFIDDiscover SW tool and Pegoda, you can check APDU exchange in Log window and apply similar exchange to your firmware. Most probably you will need to insert ISO14443 communication APDUs into Host -> Reader APDUs. For that a reader shall include such instructions.

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Dear Varun,

This forum is intended for TapLinx SDK only. We would suggest to read 3rd party documentation. Maybe https://learn.microsoft.com/en-us/samples/xamarin/monodroid-samples/cardreader/.

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Dear Manish,

Example application shall be found under "Sample Application:" on TapLinx webpage https://www.mifare.net/developer/. After opening and finished synchronizing of Gradle scripts, Build shall be possible. Please search the web for similar topics on Android applications development in Android Studio IDE.

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Dear users,

Please check "Release Notes" for your chosen platform of TapLinx https://www.mifare.net/developer/.

MF Plus is currently supported in:
TapLinx Android
TapLinx Java

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Hello dear users,

Please check for mentioned .a file in .zip:

.zip -> \TapLinx-v1.0.0\TapLinx-v1.0.0\TapLinxiOSSDK.zip\TapLinx iOS SDK 1.0.0\libTapLinxLibrary.a

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Dear David,

Please note that this is purely TapLinx related forum. Question is going a bit beyond our reach. Please contact local NXP Sales representative and will guide to answers for your application. In short Key ownership is each project / application specific. It is usually one party. So application owner has knowledge of the keys, online and the ones on chip.

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Dear Robert,

in the library .zip file there are .jar files which you can include into your project. We encourage you to use latest one (as of today) 3.0.0.

Best regards,
TapLinx team

---

+ 0  |  - 0

[TapLinx Support]

Dear David,

For the start we would encourage you to go through Datasheet, Application Notes and search web for Cryptography articles.

Errors are described in Datasheet, page 48. 0x91AE: Current authentication status does not allow the requested command. Probably, you are not using the valid key for Authentication. Or you did not select NDEF Application upfront.

Best regards,
TapLinx team

---

+ 0  |  - 0

[Author]

Posts