Connect and Scan
Use USB to establish a reliable host connection before configuring emulator slots or Bluetooth.
Prepare the Device
Connect a USB data cable and identify the serial port.
Install the CH343 driver if Windows does not list the device under Ports (COM & LPT).
With a display extension, select Settings → Host Interface → USB.
Close other software using the serial port.
Install the Development CLI
The emulator-export and firmware-update workflows in these guides use the PN532 CLI dev channel. Install Python 3.9 or later, then:
git clone --branch dev https://github.com/whywilson/pn532-python.git
cd pn532-python
python3 -m venv .venvActivate .venv using source .venv/bin/activate on Linux/macOS or .venv\Scripts\Activate.ps1 in Windows PowerShell, then run:
python -m pip install -r script/requirements.txt
python script/pn532_cli_main.pyPackaged beta builds are also available from the CLI releases. The development channel changes over time; inspect command help when an option differs.
Connect and Identify
Run these at the CLI prompt:
If necessary, use hw connect -p COM3 or replace COM3 with the local serial path. Confirm that the CLI identifies PN532Killer before using its extended commands.
For an ISO15693 tag:
Mobile Connections
MTools on Android uses direct USB host / OTG with Host Interface set to USB. MTools BLE requires the BLE extension and Host Interface set to BLE; scan for the device within the app. Neither app replaces the desktop firmware-update workflow.
If the interface is stuck in BLE mode, firmware supporting USB recovery allows holding Enter for about five seconds and releasing after the red LED flashes.
Continue with Reader and Emulator Operations.