PN532 Tag emulation NFC Tools showing NULL all the data

[Vignesh_Kumar_M]

Currently am using the PN532 (UM0701-02 ) module interface interface with the STM32WL micro controller via SPI comminication with IRQ based state model. i will explain me statemachine how am handling step by step

step 1:
SPI configuartion - clock 2Mhz and 8 bit mode

Step 2 :
after trun the PN532 Module i have send the SMA Configuration After that am waiting for the Frist IRQ for the ACK and after that i will wait for the second IRQ for the SMA Configuration response. this is happing proper am not getting any errors. please note the bellow configuaration which i have using

     pn532_packetbuffer[0] = PN532_COMMAND_SAMCONFIGURATION;

    pn532_packetbuffer[1] = 0x01; // normal mode;

    pn532_packetbuffer[2] = 0x14; // timeout 50ms * 20 = 1 second

    pn532_packetbuffer[3] = 0x01; // use IRQ pin!

step 3: 
after once i received the SMA configuration Reponse.  i have start to send the TgTarget init command. for this command i only get the ACK. the reponse when the phone is comming near to the module that time i have received.

  uint8_t command[] = {

      PN532_COMMAND_TGINITASTARGET,

      5, // MODE: PICC only, Passive only

      0x04, 0x00,       // SENS_RES

      0x00, 0x00, 0x00, // NFCID1

      0x20,             // SEL_RES

      0, 0, 0, 0, 0, 0, 0, 0,

      0, 0, 0, 0, 0, 0, 0, 0, // FeliCaParams

      0, 0,

      0, 0, 0, 0, 0, 0, 0, 0, 0, 0, // NFCID3t

      0, // length of general bytes

      0  // length of historical bytes

  };

if (uidPtr != 0)

  { // if uid is set copy 3 bytes to nfcid1

    memcpy(command + 4, uidPtr, 3);

  }

This command also am getting the success reponse.

So now i have the Phone NFC information like NFC supporting class

Note : till this am getting proper IRQ Assert, ACK and reponse for the commands.

step 4:
 After the reponse i will start to send the TgGetTarget Command(0x86). the 1 frist time like when ever am take the phone closer to PN532 am getting the response as 0x87 with error code 0x13. like RF released. after this i have try the two ways to reinit the communication. the frist way is send the Inrelease command 0x52, 0x00 then am getting the IRQ and am getting 53 with 0x00 reponse. then again am sending the TgTartget Command Initi command like follow the step3 again. Note here some time after this am getting proper response for 0x86. 

Now i have onemore issue after i send the Inrelease or TgTarget command the NFC Tools Mobile its showing the all the Data like Serial Number and other information is showing zero. and showing felica technology. but am using the ISO1884A Type A card enumation.

Now my qustion why this is happening. any sequence if i missed here. please guide us ASAP. we are in the end of project phase.

already some one refer the forms i did' nt get the anwser

[jimmychan]

It is because there is no memory to store the data.

Please refer to Chapter 3.3.7.2 in  Application Note

[Vignesh_Kumar_M]

I am not trying to store any data. First, I send the 0x8C (TgInitAsTarget) command with the required parameters, and I wait for the 0x8D response. I receive the 0x8D response correctly. After that, I send the TgGetData (0x86) command and expect to receive 0x87 with status 0x00, but most of the time I receive 0x87 with status 0x13 instead. When this happens, I send the TgInitAsTarget (0x8C) command again, and again I receive a proper 0x8D response. This time, when I send 0x86, I receive 0x87 with status 0x00 along with the APDU data. This behavior works correctly on newer phones like Motorola and Realme, but on older Samsung models I always get 0x87 with status 0x13 after 0x86, even after multiple intervals. After receiving 0x8D, I tried sending 0x86 at different time intervals such as 1 ms, 10 ms, 20 ms, 50 ms, 80 ms, 100 ms, 120 ms, and 140 ms, but I still get 0x13 on older Samsung devices. Please guide me if I am missing anything. Note one more thing when if i get the 0x87, 0x13 i tried the polling also that time am getting 0x29.

[Vignesh_Kumar_M]

please any one support for this issue

[Vignesh_Kumar_M]

Still we are facing this issue please any one support this issue fix. i have no idea we are getting issue.