Fix PN532 transport and NFC tag handling.

Tighten PN532 framing and NFC access locking so scan, read, write, and raw operations behave reliably on hardware, and correct Classic versus Type 2 tag classification so common cards hit the right code paths. Refresh the embedded web assets and launcher files to match the corrected firmware behavior.

Made-with: Cursor
This commit is contained in:
drjones
2026-04-02 18:32:06 -07:00
parent 8968560565
commit 3be2d3f936
19 changed files with 1162 additions and 287 deletions

View File

@@ -67,6 +67,26 @@ On init the PN532 is configured for **high passive-activation retries** (`RFConf
## Build
### One-command local run
```bash
./start-firmware.sh
```
What it does:
- bootstraps ESP-IDF locally if needed
- builds the web UI into `firmware/data`
- configures target `esp32s3`
- auto-detects the serial port
- builds and flashes the device
Useful options:
- `./start-firmware.sh --build-only`
- `./start-firmware.sh --monitor`
- `./start-firmware.sh --port /dev/cu.usbmodemXXXX`
### Web UI → flash image
```bash