You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue arrises, in my case, when requesting a file greater than 256 bytes in size. I have executed a GET_DATA command, and the response sent back from the card is 6100
From my understanding, 6100 does not mean 0 bytes left to read, as your library seems to interpret it as. Instead, it means there are more than 256 bytes left, just read a full 256.
Instead, your program sends the proper request but, appears to improperly setup the buffer, as I receive the following error: Error: SCardTransmit error: Insufficient buffer.(0x80100008)
The text was updated successfully, but these errors were encountered:
I think I've figured out what causes the issue. And that is that my interpretation of the 0xFF above was just including the response information and not the status code (sw1 and sw2). So, therefore, when 0xFF bytes of data are returned, the status code 6100 or whatever, actually makes the number of returned bytes 0x102. Hence, my issue can be resolved by increasing that number to 0x102
I'll close this issue now, as I think this is more an interpretation issue on my part but, perhaps a note in the docs could be helpful here, if anyone has this issue in the future.
This issue arrises, in my case, when requesting a file greater than 256 bytes in size. I have executed a GET_DATA command, and the response sent back from the card is
6100
From my understanding,
6100
does not mean 0 bytes left to read, as your library seems to interpret it as. Instead, it means there are more than 256 bytes left, just read a full 256.An example exchange would be as follows:
Instead, your program sends the proper request but, appears to improperly setup the buffer, as I receive the following error:
Error: SCardTransmit error: Insufficient buffer.(0x80100008)
The text was updated successfully, but these errors were encountered: