Hallo Saurabh, > You mean page 12 , section *5.3 Reading Binary Block*. I didn't find any "section *5.3 Reading Binary Block*" on that page. In fact, I mean have you tried the whole command sequence described for "Card Access -- How to access MIFARE Classic Tags?" on that page.
You have to do the polling using these commands to access the card. The standard PC/SC commands will not work. I just looked through my code and found that I also explicitly disabled ISO 14443-4 activation (before polling) using this command: FF00000003D41224 > Can you tell me the name of card reader where we cant see > this behavior (reader automatically performed protocol selection up to > ISO 14443-4 / APDU layer) The ACR 122U was the only reader with which I successfully accessed the MIFARE area of the SmartMX so far. br, Michael > On Thu, Jan 19, 2012 at 6:14 PM, Michael Roland <mi.rol...@gmail.com > <mailto:mi.rol...@gmail.com>> wrote: > > Hallo Saurabh, > > > I am getting This ATR now : *3B 8A 80 01 00 31 C1 73 C8 40 00 00 90 00 > > 90* , which I have read in this group that it is for SmartMX. > > Correct, that's the PC/SC ATR for the SmartMX. > > > I am looking into writing onto it but so far I am getting 63 00 > > response(which means error) > > I am trying to load., authenticate the keys and then read -write and > > then read back from the SmartMX (Secure Element). > > > > *_Here is my list of commands : _* > > > > FF82006006FFFFFFFFFFFF// load keys > > FF860000050100026000// authenticate > > FFB0000210//read sector 2 > > FFD600021022222222222222222222222222222222// write sector 2 > > FFB0000210 // read sector 2 again > > > > I followed this -- > http://www.nfc-reader.com/ > > NFC-smart-card-reader/ACR122-API-Manual/API_ACR122.pdf > > I would guess, that the reader automatically performed protocol > selection up to ISO 14443-4 / APDU layer. In that state it is not > possible to access the MIFARE part of the chip with reader-side MIFARE > emulation. You could try the example on page 12ff of this document. > > br, > Michael > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to > android-developers@googlegroups.com > <mailto:android-developers@googlegroups.com> > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > <mailto:android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
