From b5322316aa4e9a604b1d969cc6013fee65070dec Mon Sep 17 00:00:00 2001 From: Kiara Navarro Date: Thu, 25 Sep 2014 01:27:39 -0500 Subject: [PATCH 1/2] Generate the new README.md --- README.md | 35 ++++++++++++++++++++++++++++------- 1 file changed, 28 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index e21e533..2cf4daa 100644 --- a/README.md +++ b/README.md @@ -1,20 +1,41 @@ -rfid -==== +rduino RFID Library for MFRC522 +======================================================= +This library is use to read RFID Cards through MIFARE RC522 reader using SPI interface on Arduino Board. -Arduino RFID Library for MFRC522 -Read a card using a mfrc522 reader on your SPI interface on your Arduino -* Pin layout should be as follows (on Arduino Uno): + +Pin Layout for Arduino UNO +------------ * MOSI: Pin 11 / ICSP-4 * MISO: Pin 12 / ICSP-1 * SCK : Pin 13 / ISCP-3 * SS : Pin 10 (Configurable) * RST : Pin 9 (Configurable) -* -* Pin layout should be as follows (on Arduino Mega): +Pin Layout for Arduino Mega +------------ * MOSI: Pin 51 / ICSP-4 * MISO: Pin 50 / ICSP-1 * SCK : Pin 52 / ISCP-3 * SS : Pin 53 (Configurable) * RST : Pin 5 (Configurable) + +Installation +------------ +Clone the repository with: + +```bash +git clone https://github.com/sophiekovalevsky/rfid.git +``` +And place the repo into the your arduino libraries folder. + +Credits +----- +This library was created by [Miguel Balboa.][1] + +More comming soon. +----- +We need to document a lot. + +[1]: https://github.com/miguelbalboa + From e13cfd59a745d438c9adb00b504ca297d72ced88 Mon Sep 17 00:00:00 2001 From: Kiara Navarro Date: Fri, 25 Dec 2015 01:58:27 -0500 Subject: [PATCH 2/2] Fix datasheet urls in 1k and 4k cards. --- MFRC522.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/MFRC522.h b/MFRC522.h index bbe1963..36102e7 100644 --- a/MFRC522.h +++ b/MFRC522.h @@ -25,8 +25,8 @@ * If only the PICC UID is wanted, the above documents has all the needed information. * To read and write from MIFARE PICCs, the MIFARE protocol is used after the PICC has been selected. * The MIFARE Classic chips and protocol is described in the datasheets: - * 1K: http://www.nxp.com/documents/data_sheet/MF1S503x.pdf - * 4K: http://www.nxp.com/documents/data_sheet/MF1S703x.pdf + * 1K: http://www.mouser.com/ds/2/302/MF1S503x-89574.pdf + * 4K: http://datasheet.octopart.com/MF1S7035DA4,118-NXP-Semiconductors-datasheet-11046188.pdf * Mini: http://www.idcardmarket.com/download/mifare_S20_datasheet.pdf * The MIFARE Ultralight chip and protocol is described in the datasheets: * Ultralight: http://www.nxp.com/documents/data_sheet/MF0ICU1.pdf @@ -35,7 +35,7 @@ * MIFARE Classic 1K (MF1S503x): * Has 16 sectors * 4 blocks/sector * 16 bytes/block = 1024 bytes. * The blocks are numbered 0-63. - * Block 3 in each sector is the Sector Trailer. See http://www.nxp.com/documents/data_sheet/MF1S503x.pdf sections 8.6 and 8.7: + * Block 3 in each sector is the Sector Trailer. See http://www.mouser.com/ds/2/302/MF1S503x-89574.pdf sections 8.6 and 8.7: * Bytes 0-5: Key A * Bytes 6-8: Access Bits * Bytes 9: User data @@ -249,7 +249,7 @@ public: PICC_CMD_SEL_CL2 = 0x95, // Anti collision/Select, Cascade Level 2 PICC_CMD_SEL_CL3 = 0x97, // Anti collision/Select, Cascade Level 3 PICC_CMD_HLTA = 0x50, // HaLT command, Type A. Instructs an ACTIVE PICC to go to state HALT. - // The commands used for MIFARE Classic (from http://www.nxp.com/documents/data_sheet/MF1S503x.pdf, Section 9) + // The commands used for MIFARE Classic (from http://www.mouser.com/ds/2/302/MF1S503x-89574.pdf, Section 9) // Use PCD_MFAuthent to authenticate access to a sector, then use these commands to read/write/modify the blocks on the sector. // The read/write commands can also be used for MIFARE Ultralight. PICC_CMD_MF_AUTH_KEY_A = 0x60, // Perform authentication with Key A