Forum › MIFARE SDK › Mifare Plus SE 1K card Personalization › Reply To: Mifare Plus SE 1K card Personalization
Hi Fajar,
“Stupid” means here that you have full control over the NFC interface (for instance with a PC/SC interface). In an Android device you have not full control over the NFC Interface! The middleware controls the interface and try to find out, which card type is in the field. If the middleware decides, you cannot change it afterwards. In your case it detects an ISO14443-3 card (MIFARE Classic or MIFARE Plus in SL1) for which you get an NFC adapter object for operating. You cannot force it to get another type of object, for instance an ISO14443-4 for a MIFARE Plus in SL3.
All what you can do is to prepare the SL switch by writing the required keys and to execute a CommitPerso. If you remove the card from the field and tap again, it should be in SL3. Either the middleware accepts the card in the field as ISO14443-4 or not. But you have no way to control this by software for security reasons.
The TapLinx team
“Stupid” means here that you have full control over the NFC interface (for instance with a PC/SC interface). In an Android device you have not full control over the NFC Interface! The middleware controls the interface and try to find out, which card type is in the field. If the middleware decides, you cannot change it afterwards. In your case it detects an ISO14443-3 card (MIFARE Classic or MIFARE Plus in SL1) for which you get an NFC adapter object for operating. You cannot force it to get another type of object, for instance an ISO14443-4 for a MIFARE Plus in SL3.
All what you can do is to prepare the SL switch by writing the required keys and to execute a CommitPerso. If you remove the card from the field and tap again, it should be in SL3. Either the middleware accepts the card in the field as ISO14443-4 or not. But you have no way to control this by software for security reasons.
The TapLinx team
+ 0
|
- 0