Increase PN532_PACKBUFFSIZ
to 128 bytes
#132
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change is in response to a bug in this library found when working with NFC YubiKeys, which contain an NDEF record that is returned as 71 bytes (6 bytes of header, 63 bytes of payload, 2 bytes of status words).
It was found that when read using
inDataExchange()
, the last 15 bytes (13 bytes of payload and 2 bytes of status words) are being read as00
rather than their actual value:However the reading function still returns true as though it succeeded.
This has been documented here, and a suggested solution is to increase the size of
PN532_PACKBUFFSIZ
.Although I'm not sure what the optimal size is, upping it to 128 solved my problem but is not wildly larger (given this is obviously meant for an embedded system).