ESP32 board
ESP32-WROOM-32 or ESP32-S3 with 4 MB flash. The release reserves two 1.875 MB application slots.
03 / FIRST TEST
Flash it. Watch it. Measure it.
The v0.3 release is a beta hardware build. This page turns the long bench-test notes into a quick path from a blank ESP32 to a useful boot log.
REQUIREMENTS
What you need.
USB data cable
A cable capable of data transfer. Nothing needs to be connected to the lock output for the first boot.
v0.3 firmware
Use the release factory image for a clean install or the application image for an existing installation.
FLASH
Factory image first.
The factory image contains the bootloader, partition table and application. It belongs at offset 0x0.
esptool.py --chip esp32 --port /dev/tty.usbserial-0001 --baud 460800 write_flash 0x0 esp32.firmware.factory.bin
Do not use the factory image for OTA. The application image belongs in an OTA slot. The firmware validates the image header and chip ID before accepting an OTA upload.
BOOT
A healthy development boot.
Connect at 115200 baud. The important thing is that the firmware starts, initializes the reader, configures networking and serves its UI. The exact log changes with configuration and build options.
I aliro/app : Aliro HomeKey starting I aliro/access : credential registered I aliro/reader : reader running I aliro/web : configuration UI listening I aliro/net : network / setup portal ready
WHAT THE TEST PROVES
Separate boot success from tap success.
| Result | Meaning |
|---|---|
| Build passes | Firmware compiles for the target and fits the application slot. |
| Board boots | Startup, configuration, identity handling and core tasks are alive. |
| Web UI works | Networking and configuration paths are operational. |
| PN532 sees a device | The physical frontend is working. |
| Aliro transaction completes | The protocol path is working against the test credential or supported ecosystem. |
| Phone unlocks a real lock | A much stronger end-to-end milestone that requires the full credential and certification ecosystem. |