Troubleshooting & FAQ

When something doesn't work, it's almost always one of a handful of causes. This page lists the common ones by symptom, with the fix, plus answers to frequently asked questions.

Flashing & Serial

SymptomLikely cause & fix
Port doesn't appear in the web flasher or terminalCharge-only USB cable — swap to a known data cable. Close any other program holding the port (only one owner at a time).
Web flasher won't connect at allUse Chrome or Edge on desktop; Web Serial isn't available in Safari, Firefox, or on mobile.
Flash fails or stallsPut the board in download mode: hold BOOT, tap RESET, release BOOT, then retry.
Flashes fine but won't boot / crashesWrong target. Rebuild for the consumer chip: idf.py set-target esp32c5.
Console shows nothing after connectPress RESET to see boot logs; confirm the terminal is on the POOM port at 115200 baud.

SD Card & Captures

SymptomLikely cause & fix
SD not detected / FILES emptyReseat the card; format as FAT32; the mount point is /sdcard (SPI mode).
Capture starts but no file is writtenNo SD present — the sniffer falls back to UART streaming. Insert a card for a .pcap file.
Lua script "not found"Scripts must be under /sdcard with an absolute path (e.g. /sdcard/main.lua).
Portal doesn't appear in CAPTIVEPut a root.html under /portals on the SD card before starting.

Wireless, BLE & NFC

SymptomLikely cause & fix
CLI: "Command not found"Typo, or the command isn't in this build. Run help to list what's actually available.
cfg-154-* says "not supported"The 802.15.4 radio is only on esp32c5. Confirm your target.
Zigbee capture is emptyWrong channel. Use cfg-154-hop-start to find activity, then pin it with cfg-154-ch.
BLE device won't pairRemove/forget POOM on the host first, then re-pair. Only one host connects at a time.
NFC won't scan a tagRun nfc-start first, select the right technology (nfc-tech/nfc-a), and hold the tag steady on the antenna. Try nfc-tune-auto.
IR replay doesn't trigger the deviceIR is line-of-sight — aim directly and get closer. Only NEC is decoded currently.

Frequently Asked Questions

Do I need the cable after the first flash? No — use the wireless updater. See OTA / DFU Updates.

Which board target do I have? If unsure, check the silkscreen/marketing for ESP32-C5, and match idf.py set-target accordingly. A wrong target simply won't boot.

Where do captures, dumps and scripts live? On the SD card: PCAP captures, NFC dumps, CAPTIVE portals (/portals), captured portal data (/captive_data), and Lua scripts (/sdcard/*.lua).

Is any of this legal to use? The tools are for authorized testing, controlled labs, and defensive research only. Use them exclusively on devices and networks you own or are explicitly permitted to assess.

Can I add features without rebuilding firmware? Yes — write a Lua script for small automations, or drive the device from the CLI.

How do I reset stored settings? Credentials and config live in the nvs partition; a full USB re-flash that erases NVS clears them (otherwise they persist across app updates).