5.7 Software Issues
MIFARE Classic and MIFARE Plus IC memory NDEF data mapping methods
Last Updated: March 30, 2023iOS support for µFR Series hardware
Last Updated: October 10, 2023For iOS, we provide the µFR Series hardware library for iOS, the APIs, and other documentation related to hardware, as well as all the necessary technical support for your project development. As for the development tools and executable software solutions, the current iOS compliant SDK is available at our GitLab repository and the two apps at App Store. The SDK is compliant with all the µFR Series devices, while one of two available iOS apps is developed for the µFR Nano Online reader exclusively.
µFR Nano Online Reader Tools
Last Updated: October 10, 2023µFR Nano Online Reader Protocols Structure
Last Updated: October 10, 2023µFR Nano Online Reader Implementation Basics
Last Updated: October 10, 2023µFR Nano Online REST Services
Last Updated: October 10, 2023µFR Nano Online Reader settings
Last Updated: October 10, 2023How to set the µFR Card Formatter software to configure the access bits and security keys for each sector of a MIFARE 1K card
Last Updated: October 10, 2023µFR Card Formatter GUI displays the entire MIFARE Classic 1K structure with simple access to all its sectors and blocks ( 16 sectors of 4 blocks). The first block (block zero) contains the card factory UID, ad it is read-only by default.
Mifare® structure – card programming help
Last Updated: November 1, 2022Does Digital Logic offers a stand-alone open source software or software tools for working with third-party hardware?
Last Updated: November 1, 2022Can the NT4H originality be validate without configuring a random ID (nt4h_rid_read_ecc_signature_pk ECC signature)?
Last Updated: November 1, 2022Use the NDEF methods with the NT4H on µFR Nano reader (eg erase_all_ndef_records) – NDEF_UNSUPPORTED_CARD_TYPE status message
Last Updated: March 30, 2023How to use the NDEF methods with the NT4H (e.g. erase_all_ndef_records) on µFR Nano reader if you get an NDEF_UNSUPPORTED_CARD_TYPE status?
How to avoid Virtual COM port and FTDI drivers implementation on Windows OS?
Last Updated: October 10, 2023Card reading distance issue
Last Updated: November 1, 2022Windows software example cannot connect the µFR device. Missing library
Last Updated: October 10, 2023Missing library? After downloading any programming language SDK for Windows OS, if it includes the source code software example or you are about to develop your custom project, make sure that the uFCoder-x86.dll library is present in the software executable folder. If the library is not present in the .exe file folder, please check other SDK folders (it is usually stored in /lib/your_os/ folder). Otherwise, download the library from the GitLab repository https://code.d-logic.com/nfc-rfid-reader-sdk/ufr-lib, unpack the file and copy the library into your project executable folder. µFR Series libraries The µFR Series libraries support the µFR Series devices and related SDK. Libraries are available for the following platforms: Windows 32 and 64 bit (static and dynamic) Windows ARM Linux 32 and 64 bit (dynamic only) Linux ARM and ARM-HF (dynamic only) Mac OSX 32 and 64 bit (dynamic only) iOS 64 bit (static only). Implementation Download the project, select appropriate architecture, and place a library in the appropriate directory. Find more details in the µFR Series API reference. For quick insight and functions’ prototypes, check the/include/ufCoder.h header file. Requirements µFR Series device. Notice These libraries are specific to the listed hardware ONLY. There is no guarantee that they might be functional...
What is the hardware AES128 encryption?
Last Updated: June 5, 2023About encryption processes Communication with high-security cards, e.g. DESFire, which uses cryptographic protocols (DES, 3DES, AES), relies on cryptographic algorithms. This means that there are a lot of intensive calculations and repetitions. In case this is done in a library or software, the communication channel remains the security weak point. Otherwise, if this takes place in hardware, the entire cryptography is secure. Digital Logic high-security solution Given the above security weaknesses, Digital Logic has applied a special method of storing and processing keys within the hardware. All calculations, key exchange, key storage, and more are performed in the hardware (reader). This means that secret keys do not come out of the device when the reader and host communicate. For this feature, Digital Logic uses the AES128 crypto algorithm for DESFire cards/tags. The keys are securely stored in the reader and cannot be compromised. It was a logical solution because AES128 is quite fast and efficient compared to DES and 3DES which still perform processes externally by the software.