Home | History | Annotate | Download | only in tech

Lines Matching full:ultralight

28 //TOOD: Ultralight C 3-DES authentication, one-way counter
31 * Provides access to MIFARE Ultralight properties and I/O operations on a {@link Tag}.
35 * <p>MIFARE Ultralight compatible tags have 4 byte pages {@link #PAGE_SIZE}.
36 * The primary operations on an Ultralight tag are {@link #readPages} and
39 * <p>The original MIFARE Ultralight consists of a 64 byte EEPROM. The first
44 * <p>The MIFARE Ultralight C consists of a 192 byte EEPROM. The first 4 pages
56 * because all MIFARE Ultralight tags are also {@link NfcA} tags.
64 /** A MIFARE Ultralight compatible tag of unknown type */
66 /** A MIFARE Ultralight tag */
68 /** A MIFARE Ultralight C tag */
71 /** Size of a MIFARE Ultralight page in bytes */
86 * Ultralight compatible, or that this Android
87 * device does not implement MIFARE Ultralight.
90 * @param tag an MIFARE Ultralight compatible tag
91 * @return MIFARE Ultralight object
122 * Return the MIFARE Ultralight type of the tag.
126 * to accurately classify between original MIFARE Ultralight and
127 * Ultralight C. So treat this method as a hint.
139 * <p>The MIFARE Ultralight protocol always reads 4 pages at a time, to
143 * Ultralight tags have readable blocks 0x00 through 0x0F. So a read to
145 * Ultralight C tags have readable blocks 0x00 through 0x2B. So a read to
170 * <p>The MIFARE Ultralight protocol always writes 1 page at a time, to