Modifications

== Using Mifare Classic Cards as an NDEF Tag ==

== Using Mifare Classic Cards as an NDEF Tag ==

Mifare Classic 1K and 4K cards can be configured as NFC Forum compatible NDEF tags, but they must be organised in a certain manner to do so. The requirements to make a Mifare Classic card "NFC Forum compliant" are described in the following App Note from NXP:

Mifare Classic 1K and 4K cards can be configured as NFC Forum compatible NDEF tags, but they must be organised in a certain manner to do so. The requirements to make a Mifare Classic card "NFC Forum compliant" are described in the following App Note from NXP:

While the App Note above is the authoritative source on the matter, the following notes may also offer a quick overview of the key concepts involved in using Mifare Classic cards as NFC Forum compatible 'NDEF' tags:

While the App Note above is the authoritative source on the matter, the following notes may also offer a quick overview of the key concepts involved in using Mifare Classic cards as NFC Forum compatible 'NDEF' tags:

== Mifare Application Directory (MAD)

== Mifare Application Directory (MAD) ==

In order to form a relationship between the sector-based memory of a Mifare Classic card and the individual NDEF records, the '''Mifare Application Directory''' (MAD) structure is used. The MAD indicates which sector(s) contains which NDEF record. The definitive source of information on the Mifare Application Directory is the following application note:

In order to form a relationship between the sector-based memory of a Mifare Classic card and the individual NDEF records, the '''Mifare Application Directory''' (MAD) structure is used. The MAD indicates which sector(s) contains which NDEF record. The definitive source of information on the Mifare Application Directory is the following application note: