crewID/libnfc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix typos

Browse source
This commit is contained in:
Philippe Teuwen 2012-05-14 19:44:03 +00:00
parent e9b2f5729c
commit 7597055f26
6 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
examples/nfc-emulate-forum-tag2.c
View file

@ -35,7 +35,7 @@
* It have been developed using PN533 USB hardware as target and Google Nexus S phone as initiator. * It have been developed using PN533 USB hardware as target and Google Nexus S phone as initiator.
* *
* This is know to NOT work with Nokia 6212 Classic and could not work with * This is know to NOT work with Nokia 6212 Classic and could not work with
* several NFC Forum compiliant devices due to these reasons: * several NFC Forum compliant devices due to these reasons:
* - The emulated target only have a 4 bytes UID where 7 bytes UID (as a real * - The emulated target only have a 4 bytes UID where 7 bytes UID (as a real
* Mifare Ultralight tag) are usually attempted; * Mifare Ultralight tag) are usually attempted;
* - The chip is emulating a ISO/IEC 14443-3 tag, without any hardware helper. * - The chip is emulating a ISO/IEC 14443-3 tag, without any hardware helper.

2
include/nfc/nfc-types.h
View file

@ -111,7 +111,7 @@ typedef enum {
* In initiator mode, it means that NFC chip will send RATS automatically when * In initiator mode, it means that NFC chip will send RATS automatically when
* select and it will automatically poll for ISO14443-4 card when ISO14443A is * select and it will automatically poll for ISO14443-4 card when ISO14443A is
* requested. * requested.
* In target mode, with a NFC chip compiliant (ie. PN532), the chip will * In target mode, with a NFC chip compliant (ie. PN532), the chip will
* emulate a 14443-4 PICC using hardware capability */ * emulate a 14443-4 PICC using hardware capability */
NP_AUTO_ISO14443_4, NP_AUTO_ISO14443_4,
/** Use automatic frames encapsulation and chaining. */ /** Use automatic frames encapsulation and chaining. */

2
utils/nfc-emulate-forum-tag2.1
View file

@ -9,7 +9,7 @@ is a demonstration tool that emulates a NFC Forum tag type 2 that contains a rea
.SH NOTES .SH NOTES
It have been developed using PN533 USB hardware as target and Google Nexus S phone as initiator. It have been developed using PN533 USB hardware as target and Google Nexus S phone as initiator.
This is know to NOT work with Nokia 6212 Classic and could not work with several NFC Forum compiliant devices due to these reasons: This is know to NOT work with Nokia 6212 Classic and could not work with several NFC Forum compliant devices due to these reasons:
- The emulated target only have a 4 bytes UID where 7 bytes UID (as a real Mifare Ultralight tag) are usually attempted; - The emulated target only have a 4 bytes UID where 7 bytes UID (as a real Mifare Ultralight tag) are usually attempted;
- The chip is emulating a ISO/IEC 14443-3 tag, without any hardware helper. - The chip is emulating a ISO/IEC 14443-3 tag, without any hardware helper.

6
utils/nfc-emulate-forum-tag4.1
View file

@ -8,11 +8,11 @@
.Op infile Op outfile .Op infile Op outfile
.Sh DESCRIPTION .Sh DESCRIPTION
.Nm .Nm
is a demonstration tool that emulates a NFC Forum tag type 4 with NDEF content. is a demonstration tool that emulates a NFC Forum tag type 4 v1.0 with NDEF content.
.Pp .Pp
.Ar infile .Ar infile
is the file which contains NDEF message you want to share with the NFC-Forum is the file which contains NDEF message you want to share with the NFC-Forum
compiliant initiator device (e.g. Nokia 6212 Classic) compliant initiator device (e.g. Nokia 6212 Classic)
.Pp .Pp
If you want to save a shared content by the initiator device, we have to give If you want to save a shared content by the initiator device, we have to give
.Ar outfile .Ar outfile
@ -21,7 +21,7 @@ argument to point where the NDEF message will be saved.
This example uses the hardware capability of PN532 to handle ISO/IEC 14443-4 This example uses the hardware capability of PN532 to handle ISO/IEC 14443-4
low-level frames like RATS/ATS, WTX, etc. low-level frames like RATS/ATS, WTX, etc.
.Pp .Pp
All devices compiliant with NFC-Forum Tag Type 4 (Version 1.0) can be used with All devices compliant with NFC-Forum Tag Type 4 (Version 1.0) can be used with
this example in read-write mode. this example in read-write mode.
.Pp .Pp
If no argument is given, a default NDEF file is available. If no argument is given, a default NDEF file is available.

2
utils/nfc-emulate-forum-tag4.c
View file

@ -30,7 +30,7 @@
/** /**
* @file nfc-emulate-forum-tag4.c * @file nfc-emulate-forum-tag4.c
* @brief Emulates a NFC Forum Tag Type 4 with a NDEF message * @brief Emulates a NFC Forum Tag Type 4 v1.0 with a NDEF message
*/ */
/* /*

2
utils/nfc-read-forum-tag3.c
View file

@ -240,7 +240,7 @@ main(int argc, char *argv[])
} }
// Check again if System Code equals 0x12fc // Check again if System Code equals 0x12fc
if (0 != memcmp (nt.nti.nfi.abtSysCode, abtNfcForumSysCode, 2)) { if (0 != memcmp (nt.nti.nfi.abtSysCode, abtNfcForumSysCode, 2)) {
fprintf (stderr, "Tag is not NFC Forum Tag Type 3 compiliant.\n"); fprintf (stderr, "Tag is not NFC Forum Tag Type 3 compliant.\n");
error = EXIT_FAILURE; error = EXIT_FAILURE;
goto error; goto error;
} }