How to Read an RFID Tag with Raspberry Pi: MFRC522 SPI Wiring & Python Code

If you want to read an RFID tag with a Raspberry Pi, the 13.56 MHz MFRC522 module communicating over SPI is the most reliable and cost-effective path. Unlike 5V Arduino boards that require a BSS138 logic level shifter to prevent frying the MFRC522's 3.3V logic pins, the Raspberry Pi natively operates at 3.3V on its GPIO header. This means you can wire the reader directly to the Pi without intermediary buffers.

This guide targets the Raspberry Pi 4 Model B (BCM2711) running Raspberry Pi OS (Bookworm or later), though the SPI pinout remains identical for the Pi 3B+ and Pi 5. We will cover the exact hardware spec sheet, step-by-step SPI configuration, a production-ready Python script with strict GPIO cleanup, and a debugging matrix for the most common read failures.

Hardware Spec Sheet & Pin Mapping

Before stripping jumper wires, verify your exact hardware variants. The MFRC522 market is flooded with clones; ensure your breakout board has a 3.3V voltage regulator (usually an AMS1117-3.3) if you plan to power it from the Pi's 5V pin, though powering it directly from the Pi's 3.3V pin is safer and preferred.

Required Parts List

• Microcontroller: Raspberry Pi 4 Model B (4GB or 8GB variant)
• RFID Module: MFRC522 Breakout Board (13.56 MHz, SPI/I2C/UART capable)
• RFID Tags: Mifare Classic 1K (S50) or NTAG215 cards/fobs
• Wiring: 8x Female-to-Female Dupont jumper wires (minimum 24 AWG)
• Storage: 32GB MicroSD card (Class 10, A1 rated minimum)

Module Specifications

GPIO Pin Mapping (BCM Numbering)

The mfrc522 Python library defaults to specific BCM pins. Do not use BOARD (physical pin) numbering in your code unless you explicitly remap the library initialization. The mapping below uses standard BCM numbering.

Step-by-Step Wiring & SPI Configuration

Hardware is only half the battle; the Linux kernel must be instructed to load the SPI device tree overlays before Python can access /dev/spidev0.0.

1. De-energize the Pi: Always unplug the USB-C power supply before connecting jumper wires to the GPIO header to prevent accidental shorting of the 5V rail to the MISO line.
2. Wire the SPI Bus: Connect SDA to GPIO 8, SCK to GPIO 11, MOSI to GPIO 10, MISO to GPIO 9, RST to GPIO 25, 3.3V to 3V3, and GND to GND. Leave IRQ disconnected.
3. Boot and Enable SPI: Power on the Pi. Open a terminal and run sudo raspi-config. Navigate to Interface Options > SPI and select Yes to enable the SPI kernel module.
4. Verify Device Tree (Bookworm OS): If using the latest Raspberry Pi OS, verify SPI is active by running ls -l /dev/spi*. You should see /dev/spidev0.0 and /dev/spidev0.1. If missing, add dtparam=spi=on manually to /boot/firmware/config.txt and reboot.
5. Install Python Dependencies: Create a virtual environment (highly recommended for Bookworm) and install the required libraries:

   python3 -m venv rfid_env
   source rfid_env/bin/activate
   pip install spidev RPi.GPIO mfrc522

   Note: If you are on a Raspberry Pi 5, the legacy RPi.GPIO library may throw architecture errors. Install the drop-in replacement via pip install rpi-lgpio before installing mfrc522.

Complete Python Implementation

The following script targets the Pi 4 Model B using BCM numbering. It initializes the SPI bus, polls for a tag, extracts the 4-byte or 7-byte UID, and enforces strict GPIO.cleanup() in a finally block to prevent the GPIO lock-up issues notorious in long-running RFID scripts.

#!/usr/bin/env python3
import sys
import time
import signal
import RPi.GPIO as GPIO
from mfrc522 import SimpleMFRC522

# --- PIN DEFINITIONS (BCM) ---
# The SimpleMFRC522 class hardcodes these internally:
# CE0 (SDA) = 8, SCLK = 11, MOSI = 10, MISO = 9, RST = 25

def signal_handler(sig, frame):
    print('\n[INFO] Interrupt received. Cleaning up GPIO...')
    GPIO.cleanup()
    sys.exit(0)

# Register signal handler for clean Ctrl+C exits
signal.signal(signal.SIGINT, signal_handler)

def main():
    reader = None
    try:
        # Initialize the reader (sets up SPI and GPIO)
        reader = SimpleMFRC522()
        print('[SYSTEM] MFRC522 initialized. Hold an RFID tag near the antenna...')
        print('[SYSTEM] Press Ctrl+C to exit.\n')
        
        while True:
            try:
                # read_no_block() returns (id, text) or (None, None)
                tag_id, text = reader.read_no_block()
                
                if tag_id:
                    print(f'[SUCCESS] Tag Detected!')
                    print(f'  UID (Decimal): {tag_id}')
                    print(f'  UID (Hex):     {hex(tag_id)}')
                    print(f'  Data Block:    {repr(text.strip())}')
                    print('-' * 40)
                    
                    # Debounce: prevent reading the same tag 50 times a second
                    time.sleep(1.5) 
                    
            except Exception as read_err:
                print(f'[WARN] Transient read error: {read_err}')
                time.sleep(0.5)
                
    except OSError as e:
        print(f'[FATAL] SPI Bus Error: {e}')
        print('Action: Ensure SPI is enabled in raspi-config and /dev/spidev0.0 exists.')
        sys.exit(1)
        
    except RuntimeError as e:
        print(f'[FATAL] GPIO/Hardware Error: {e}')
        print('Action: Check BCM pin mappings and ensure you are running on a Pi.')
        sys.exit(1)
        
    finally:
        # CRITICAL: Always cleanup GPIO to release hardware locks
        print('[SYSTEM] Executing GPIO cleanup...')
        GPIO.cleanup()

if __name__ == '__main__':
    main()

Debugging: 'No RFID Reader Found' & Read Failures

When an RFID tag Raspberry Pi build fails, it rarely fails silently. The Linux kernel and Python GPIO libraries will throw specific exceptions. If your script crashes or fails to read, check these first three things:

1. Verify the SPI Device Node: Run ls /dev/spidev*. If it returns 'No such file', the kernel overlay failed to load.
2. Check Logic Power: Use a multimeter to measure voltage between the MFRC522 VCC and GND pins. It must read between 3.1V and 3.4V. If it reads 0V, your Pi's 3.3V polyfuse may have tripped, or your jumper wire is broken.
3. Validate the Tag Frequency: Hold a known-good 13.56 MHz Mifare tag to the reader. If you are using a 125kHz EM4100 fob (common in cheap apartment keychains), the MFRC522 physically cannot excite its coil.

Common Error Strings & Ranked Causes

Error 1: OSError: [Errno 2] No such file or directory: '/dev/spidev0.0'

• Cause A (Most Likely): SPI interface is disabled in raspi-config.
• Cause B: You are running the script outside your virtual environment where spidev was installed.
• Cause C: On Raspberry Pi 5, the device tree naming convention shifted; ensure your OS is fully updated via sudo apt update && sudo apt full-upgrade.

Error 2: RuntimeError: Failed to add edge detection or ValueError: The channel sent is invalid on a Raspberry Pi

• Cause A (Most Likely): A previous script crashed without running GPIO.cleanup(), leaving the GPIO pins locked in an active state. Reboot the Pi to clear the hardware latch.
• Cause B: You are accidentally using BOARD (physical) pin numbering in a secondary script while the mfrc522 library strictly demands BCM numbering.

Error 3: Script runs, but read_no_block() always returns (None, None) even with a tag present.

• Cause A (Most Likely): MISO and MOSI wires are swapped. SPI requires Master-Out to connect to Slave-In. Double-check the pin mapping table.
• Cause B: The MFRC522 antenna coil is cracked or the tuning capacitor (usually 100pF or 150pF surface mount) is damaged, preventing the 13.56 MHz electromagnetic field from generating.

Extending and Simplifying the Build

Depending on your end goal, you may need to pivot your hardware choices. Here is how to adapt the build.

How to Simplify the Build

If you are already using the SPI bus for an ILI9341 TFT display or an MCP3008 ADC, you will run into chip-select (CE) conflicts. To simplify wiring and free up the SPI bus, switch to an I2C-based PN532 RFID module. The PN532 requires only four wires (VCC, GND, SDA, SCL), uses the adafruit-circuitpython-pn532 library, and supports both 13.56 MHz tag reading and NFC peer-to-peer emulation.

How to Extend the Build

To turn this reader into an access control system, you need to drive a 12V magnetic door lock. Never wire a 12V relay coil directly to the Pi's 3.3V GPIO. Instead, extend the circuit using a PC817 optocoupler or a logic-level MOSFET (like the IRLZ44N) to isolate the Pi from the inductive kickback of the relay coil. Add a flyback diode (1N4007) across the relay coil pins to protect the MOSFET. For software extension, wrap the UID validation logic in an MQTT publisher (using paho-mqtt) to log entry attempts to a Home Assistant dashboard over your local network.

Frequently Asked Questions

Can I read a 125kHz RFID tag with a Raspberry Pi using the MFRC522?

No. The MFRC522 silicon is an ASIC specifically tuned to generate and decode the 13.56 MHz ISO/IEC 14443 Type A protocol. A 125kHz tag (like the EM4100 or HID ProxCard) relies on a completely different low-frequency inductive coupling mechanism. To read 125kHz tags with a Raspberry Pi, you must purchase a dedicated 125kHz USB RFID reader (which acts as a serial keyboard wedge) or an RDM6300 module wired to the Pi's UART RX pin.

Why does my Raspberry Pi RFID reader only work once and then freeze?

This is almost always caused by poor exception handling in Python. When a read operation times out or encounters SPI bus noise, the underlying C-extension of the GPIO library can leave the hardware state machine locked. If your script crashes and you restart it without a proper GPIO.cleanup() execution in a finally block, the new instance cannot claim the SPI bus. Always use the try...finally structure provided in the code block above, and if the Pi freezes entirely, add a hardware watchdog timer via systemd to auto-reboot the board on kernel panics.

How do I connect multiple RFID readers to one Raspberry Pi?

The Raspberry Pi's primary SPI bus (spidev0) natively supports two Chip Enable lines: CE0 (GPIO 8) and CE1 (GPIO 7). You can wire two MFRC522 modules to the same SCK, MOSI, and MISO lines, but connect the first module's SDA to GPIO 8 and the second module's SDA to GPIO 7. You will need to initialize two separate instances of the spidev bus in Python (spi.open(0, 0) and spi.open(0, 1)). If you need three or more readers, you must either use a software-SPI (bit-banging) library on standard GPIO pins—which drastically reduces read speed—or use an I2C multiplexer like the TCA9548A with I2C-capable PN532 readers.