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

Small typos

Browse source
This commit is contained in:
Philippe Teuwen 2010-10-14 11:53:27 +00:00
parent af88da1a9c
commit 5a5b5d681b
11 changed files with 23 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
examples/nfc-anticol.c
View file

@ -19,7 +19,7 @@
/**
* @file nfc-anticol.c
* @brief Generate one ISO14443-A anti-collision process "by-hand"
* @brief Generates one ISO14443-A anti-collision process "by-hand"
*/
#ifdef HAVE_CONFIG_H

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

@ -19,7 +19,7 @@
/**
* @file nfc-emulate-forum-tag4.c
* @brief Emulate a NFC Forum Tag Type 4 with a NDEF message
* @brief Emulates a NFC Forum Tag Type 4 with a NDEF message
*/
// Notes & differences with nfc-emulate-tag:

2
examples/nfc-emulate-tag.c
View file

@ -19,7 +19,7 @@
/**
* @file nfc-emulate-tag.c
* @brief Emulate a simple tag
* @brief Emulates a simple tag
*/
// Note that depending on the device (initiator) you'll use against, this

2
examples/nfc-emulate-uid.1
View file

@ -41,7 +41,7 @@ Nokia NFC 6212 and Pegoda readers are much too strict and won't be fooled.
.SH OPTIONS
.IR UID
8 hex digits format that represents desired UID (default is DEADBEAF).
8 hex digits format that represents desired UID (default is DEADBEEF).
.SH BUGS
Please report any bugs on the

8
examples/nfc-emulate-uid.c
View file

@ -19,7 +19,7 @@
/**
* @file nfc-emulate-uid.c
* @brief This example can be used to emulate a tag which which have a "really" custom UID
* @brief Emulates a tag which which have a "really" custom UID
*
* NFC devices are able to emulate passive tags but manufacturers restrict the
* customization of UID. With PN53x, UID is only 4-byte long and the first
@ -52,7 +52,7 @@ static nfc_device_t *pnd;
// ISO14443A Anti-Collision response
byte_t abtAtqa[2] = { 0x04, 0x00 };
byte_t abtUidBcc[5] = { 0xDE, 0xAD, 0xBE, 0xAF, 0x62 };
byte_t abtUidBcc[5] = { 0xDE, 0xAD, 0xBE, 0xEF, 0x62 };
byte_t abtSak[9] = { 0x08, 0xb6, 0xdd };
void
@ -73,7 +73,7 @@ print_usage (char *argv[])
printf ("\t-h\tHelp. Print this message.\n");
printf ("\t-q\tQuiet mode. Silent output: received and sent frames will not be shown (improves timing).\n");
printf ("\n");
printf ("\t[UID]\tUID to emulate, specified as 8 HEX digits (default is DEADBEAF).\n");
printf ("\t[UID]\tUID to emulate, specified as 8 HEX digits (default is DEADBEEF).\n");
}
int
@ -135,7 +135,7 @@ main (int argc, char *argv[])
.nm.nmt = NMT_ISO14443A,
.nm.nbr = NBR_UNDEFINED,
.nti.nai.abtAtqa = { 0x04, 0x00 },
.nti.nai.abtUid = { 0xde, 0xad, 0xbe, 0xaf },
.nti.nai.abtUid = { 0xde, 0xad, 0xbe, 0xef },
.nti.nai.btSak = 0x20,
.nti.nai.szUidLen = 4,
.nti.nai.szAtsLen = 0,

2
examples/nfc-list.c
View file

@ -19,7 +19,7 @@
/**
* @file nfc-list.c
* @brief List the first target present of each founded device
* @brief Lists the first target present of each founded device
*/
#ifdef HAVE_CONFIG_H

4
examples/pn53x-sam.1
View file

@ -11,8 +11,8 @@ Module) in several modes.
To run this utility you must have a SAM (like the NXP's P5CN072 chip)
successfully connected to your PN53x chip.
Warning: the SAM inside the Touchatag is \fInot\fP hooked to the PN532
but to the intermediate controller so \fBpn53x-sam\fP won't work with a Touchatag.
Warning: the SAM inside a Touchatag/ACR122U is \fInot\fP hooked to the PN532
but to the intermediate controller so \fBpn53x-sam\fP won't work with a Touchatag/ACR122U.
.SH BUGS
Please report any bugs on the

6
examples/pn53x-sam.c
View file

@ -19,7 +19,7 @@
/**
* @file pn53x-sam.c
* @brief Configure the NFC device to comunicate with a SAM (Secure Access Module).
* @brief Configures the NFC device to communicate with a SAM (Secure Access Module).
*/
#ifdef HAVE_CONFIG_H
@ -132,7 +132,7 @@ main (int argc, const char *argv[])
printf ("Connected to NFC device: %s\n", pnd->acName);
// Print the example's menu
printf ("\nSelect the comunication mode:\n");
printf ("\nSelect the communication mode:\n");
printf ("[1] Virtual card mode.\n");
printf ("[2] Wired card mode.\n");
printf ("[3] Dual card mode.\n");
@ -205,7 +205,7 @@ main (int argc, const char *argv[])
.nm.nmt = NMT_ISO14443A,
.nm.nbr = NBR_UNDEFINED,
.nti.nai.abtAtqa = { 0x04, 0x00 },
.nti.nai.abtUid = { 0x08, 0xad, 0xbe, 0xaf },
.nti.nai.abtUid = { 0x08, 0xad, 0xbe, 0xef },
.nti.nai.btSak = 0x20,
.nti.nai.szUidLen = 4,
.nti.nai.szAtsLen = 0,

6
examples/pn53x-tamashell.c
View file

@ -17,6 +17,12 @@ You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
/**
* @file pn53x-tamashell.c
* @brief Configures the NFC device to communicate with a SAM (Secure Access Module).
*/
#ifdef HAVE_CONFIG_H
# include "config.h"
#endif // HAVE_CONFIG_H

4
libnfc/drivers/pn532_uart.c
View file

@ -104,7 +104,7 @@ pn532_uart_list_devices (nfc_device_desc_t pnddDevices[], size_t szDevices, size
pn532_uart_ack ((nfc_device_spec_t) sp);
// PN532 could be powered down, we need to wake it up before line testing.
pn532_uart_wakeup ((nfc_device_spec_t) sp);
// Check communication using "Diagnose" command, with "Comunication test" (0x00)
// Check communication using "Diagnose" command, with "Communication test" (0x00)
if (!pn532_uart_check_communication ((nfc_device_spec_t) sp, &bComOk))
return false;
if (!bComOk)
@ -158,7 +158,7 @@ pn532_uart_connect (const nfc_device_desc_t * pndd)
pn532_uart_ack ((nfc_device_spec_t) sp);
// PN532 could be powered down, we need to wake it up before line testing.
pn532_uart_wakeup ((nfc_device_spec_t) sp);
// Check communication using "Diagnose" command, with "Comunication test" (0x00)
// Check communication using "Diagnose" command, with "Communication test" (0x00)
if (!pn532_uart_check_communication ((nfc_device_spec_t) sp, &bComOk))
return NULL;
if (!bComOk)

2
libnfc/nfc.c
View file

@ -498,7 +498,7 @@ nfc_initiator_transceive_bytes (nfc_device_t * pnd, const byte_t * pbtTx, const
* nfc_initiator_transceive_bytes(). With that function you can only
* communicate frames that consist of full bytes. When you send a full byte (8
* bits + 1 parity) with the value of REQA (0x26), a tag will simply not
* respond. More information about this can be found in the anti-colision
* respond. More information about this can be found in the anti-collision
* example (\e nfc-anticol).
*
* @param pbtTxPar parameter contains a byte array of the corresponding parity bits needed to send per byte.