Sequences, as all the RF frontend and synchronization firmware is already compiled.
That way the user does not need to worry if the code compiles correctly and respects critical timing Provided in form of object file "main.o". the "main" code, implementing the RF modem, has been isolated from the source code, compiled separately, and If you are one of such users, then the SDK is definitely for you! LimitationsĪs with any commercial product, there exists a part of code closely related to hardware and which requires careful tuning, as opposed to simple Position, while still emulating security features of Ultralight), add custom backdoor commands, and even change the UID length to either 4 or 10īytes. to make the Emulator always read the same content as long as the lock switch is in the locked Multi-purpose, add data auto-reload capabilities (e.g. The SDK has been created following requests of multiple EMUTAG Emulator users and candidates for purchasing. The user can also program own functionality into the hardware lock switch. Provided with access to the receive buffer and the reply function, where the message processing code can be created from scratch or modified from the provided examples of already implemented NFC tag processing routines.
Now instead of simply being a functional clone ofĥ NFC tags, it can be converted by user to a custom ISO 14443-A message processor based on NFC Forum Generic Type 2 Tag protocol.
The main purpose of the SDK is to open the high-level part of message processing to the user. *** New in version 3 *** : added example code for NTAG213 and Ultralight EV1 emulation NFC Shell was created prior to testing firmwares for NTAG213 and EV1, because they have lots of features (commands) other than READ and WRITE.ĭevelopment of another more convenient application to manage special memory locations of NTAG213 and EV1 (counters, signature, etc.) is planned. MIFARE++ Ultralight was originally created from an existing application ofīy adding NFC functions and buttons on top of it.