More details on featuring your application can be found from Feature Element. To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK. You can check if a devrice supports the related features for this API by using System Information, thereby controlling the procedure of your application. It is recommended to design feature related codes in your application for reliability. This API is related with the following features: There are two keys per sector, and ACL bits determine what I/O operations are allowed on that sector after authenticating with a key MIFARE Classic tags require authentication on a per-sector basis before any other I/O operations on that sector can be performed. The first 32 sectors contain 4 blocks and the last 8 sectors contain 16 blocks. MIFARE Classic 4k are 4096 bytes (SIZE_4K). MIFARE Classic 2k are 2048 bytes (SIZE_2K), with 32 sectors each of 4 blocks. MIFARE Classic 1k are 1024 bytes (SIZE_1K), with 16 sectors each of 4 blocks. ![]() ![]() ![]() MIFARE Classic Mini are 320 bytes (SIZE_MINI), with 5 sectors each of 4 blocks. MIFARE Classic tags are divided into sectors, and each sector is sub-divided into blocks. MIFARE Classic is also known as MIFARE Standard. API provides access to MIFARE specific I/O operations on a Tag.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |