nfc - PN532 Tag Emulation - Understanding initial response and APDU data field -


i have pn532 i'd present reader passive nfc tag ndef record url on it.

following pn532's user manual can put device target mode, , read first adpu command phone. can use iso-14443-4 pdf 2005 see command a4, read file, , 2 parameter bytes indicate "select df name, first occurrence". past though, don't know how interpret data field, should the name of file being requested reading.

furthermore, don't know how interpret initial command [e080] phone.

the program's output: (comments #'s)

usart init.  i2c init.  pn532 init.  firmware: 1.6  sam config done.  gen status:      err code: 0x00      field: 0x00      number of tags: 0x00  initiating target. # here pn532 waits reader.  tginitastarget. length: 5 # callback function once pn532 detects reader , retrieves first command it.      mode:       baud: 106kbps, 14443-4: yes, dep: no, framing type: mifare.   initiator command:   0xe0  0x80  entering tg loop.  callback: tggetdata. # tggetdata command sent without doing initial instructions.      status: 0x00      0x00 0xa4 0x04 0x00 0x07 0xd2 0x76 0x00 0x00 0x85 0x01 0x01 0x00       cla: 0x00 # single command, no sm, channel 0.      ins: 0xa4 # select.      p1:  0x04 # select df name.      p2:  0x00 # first/only occurrence, return fci template.      lc:  0x07 # 7 data bytes.      data: 0xd2 0x76 0x00 0x00 0x85 0x01 0x01 #???      le:  0x00 # length response. 


Comments

Popular posts from this blog

javascript - Thinglink image not visible until browser resize -

firebird - Error "invalid transaction handle (expecting explicit transaction start)" executing script from Delphi -

mongodb - How to keep track of users making Stripe Payments -