Fixed FAST_READ command and handling of dynamic and static locks for … #314
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
You are welcome to add an entry to the CHANGELOG.md as well |
Built artifacts for commit 11bafacFirmwareClient |
dogty
force-pushed
the
main
branch
2 times, most recently
from
13d51a5 to
bbef641
Compare
… lock bits (only for NTAG213, NTAG215 and NTA216)
…ritable even if a password is set (only for NTAG215, NTAG216 and NTAG213)
…NTAG215, NTAG213 and NTAG216)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixed an issue with the FAST_READ command, it didn't take into account the last bloc.
Recoded the handling of dynamic and static locks based on https://www.nxp.com/docs/en/data-sheet/NTAG213_215_216.pdf. It took into account bl lock bits when you shouldn't to check if a page needs to be locked or not
Note that I've only looked for these specific tags : NTAG213, NTAG215 and NTAG216 and I kept the old algorithm for the other tags. I have no idea if those tags are compatible with the new handling would gladly want some feedback on that.