NFC EEPROM sample application

NFC EEPROM Application based on X-NUCLEO-NFC04A1 expansion board

The application will write an URL to the EEPROM of the NFC tag on your board. This will be able to be read by any NFC device capable of reading NFC tags.

The example uses the EEPROM driver provided for the X-NUCLEO-NFC04A1 expansion board based on the ST25DV04K dynamic NFC/RFID tag.

README.md

Committer:
apalmieri
Date:
22 months ago
Revision:
3:3b37cd0a18e4
Parent:
0:f3d7ca3d45de

File content as of revision 3:3b37cd0a18e4:

# NFC EEPROM usage example for X-NUCLEO-NFC04A1

Demonstration of possible usage of the NFC EEPROM class. 

The application will write an URL to the EEPROM of the NFC tag on your board. This will be able to be read by any NFC device capable of reading NFC tags.

The example needs to supply a driver for the EEPROM. The `ST25DV` EEPROM driver is provided for the `NUCLEO_F401RE` target. You may wish to update the configuration if you're using a different target.

# Running the application

## Requirements

Verification of the sample application can be seen on any smartphone with a NFC reader. After running you will be able to read the tag with a NFC tag reader application running on the smartphone.

Information about activity is also printed on the serial interface. See the [official documentation website](https://os.mbed.com/docs/mbed-os/v5.15/tutorials/serial-comm.html#using-terminal-applications) for more informartion about using serial terminals.

As mentioned above, this example is known to work on the `NUCLEO_F401RE` target which uses the [`ST25DV`](./source/target/TARGET_ST25DV) driver.

If your are not using a `NUCLEO_F401RE` you should indicate in the application configuration file ([`mbed_app.json`](./mbed_app.json)) which driver should be selected by the build system as follows:

```json
    "<TARGET_NAME>": {
        "target.extra_labels_add": ["ST25DV"]
    }
```