← Back to the chapter · Previous detail
Technical detail · NFC Tag Programming
NTAG21x memory and inspection
For the protection decision, take the common NTAG21x family as the concrete example. NTAG213, NTAG215, and NTAG216 provide roughly 144, 504, and 888 bytes of user memory, respectively. Their memory model gives you two different write controls, and confusing them creates deployment bugs.
Static and dynamic lock bits make selected pages permanently read-only. Password protection uses the 32-bit PWD and the 16-bit PACK acknowledgement to control access while permitting authorized updates.
NTAG21x also exposes a one-way NFC counter and a Capability Container that a reader checks first to learn the memory size and whether the tag is already read-only. The Capability Container is why a careful writer inspects the tag before writing instead of blasting records at every UID it sees.
The quoted user-memory sizes are not a promise that every byte is available to a chosen NDEF message. Compare the writer’s usable NDEF capacity with the actual encoded message before writing.