ESP32
The default target and the board used for the v0.3 hardware validation. ESP32-S3 and other targets remain part of the build matrix.
4 MB flashWi-FiBluetooth02 / HARDWARE
The bench.
The project uses accessible embedded hardware while leaving the NFC frontend behind a replaceable interface. v0.3 makes that interface real with a PN532 driver.
PN532
The first real NFC frontend. v0.3 adds SPI and I2C support as an isolated component.
ISO 14443SPII2CLock / LED
The access-control layer drives a configurable output. On a development board this can simply be the onboard LED.
GPIOrelayNFC OPTIONS
Why PN532, and what comes next?
The architecture keeps the frontend replaceable. PN532 is inexpensive and widely available. ST25R3916 is the path used in Espressif's NFC example. PN7160 is a more modern NCI option.
| Frontend | Status | Notes |
|---|---|---|
| PN532 | v0.3 | First real frontend; SPI/I2C component with the transport seam. |
| ST25R3916 | exploring | Known-good reference path from Espressif's example hardware. |
| PN7160 | exploring | Modern NCI part; likely more driver work. |
SECURITY
Bench hardware is not production hardware.
Development identities are generated for testing. A production reader needs protected key storage, appropriate certificates and an ecosystem certification path. The current project treats plaintext development keys as a deliberate shortcut, not a security recommendation.
Important: the project is research and interoperability work. Do not treat the current firmware as a production door controller without a proper threat model, secure key storage, authentication and certification.