Question 1

ESP32: Cannot connect: esptool waits for a reply that never comes — what does it mean?

Accepted Answer

The serial port exists, but the chip is not in download mode at that moment. This is the single most common ESP32 error and the chip is almost never broken. Hit upload, and the moment Connecting... appears, hold BOOT until the percentage starts climbing. Test the USB cable on a phone — no "file transfer" prompt means it is charge-only. Replace it. Close every Serial Monitor and extra IDE window; only one program can own the port. Use a rear motherboard USB port (not a front panel or unpowered hub), or drop to 115200 baud. Disconnect all peripherals and expansion boards and retry with the bare minimum.

Question 2

ESP32: Wrong boot mode detected — what does it mean?

Accepted Answer

The strapping pins were sampled at a level combination that is not download mode — GPIO0 was not held low during reset. Manual sequence: hold BOOT (GPIO0 to GND) → tap EN (reset) → release EN → release BOOT. Measure GPIO0 to ground with a multimeter; in download mode it should read near 0 V. Remove everything wired to GPIO0 (LEDs, relay modules, sensors) and retry. On classic ESP32, also confirm GPIO2 is low at power-up.

Question 3

ESP32: Cannot open the serial port — what does it mean?

Accepted Answer

This fails at the OS level, before the chip is involved. On Windows it is usually driver or port contention, on Linux permissions, on macOS driver conflicts. Windows: Device Manager → Ports (COM & LPT), look for a yellow exclamation. Install the WCH driver for CH340 or the Silicon Labs driver for CP210x — never both. Close every Serial Monitor and IDE window except one. Linux: run sudo usermod -aG dialout $USER, then log out and back in. Unplug and replug; if the COM number keeps jumping, suspect power or contact problems.

Question 4

ESP32: Connected but writing to flash fails — what does it mean?

Accepted Answer

Handshake succeeded but the actual write failed. Flash writing draws peak current — this is nearly always power or cable quality. Drop the baud rate to 115200 and retry — reliability over speed. Use a short, thick cable on a rear motherboard port, or a powered hub. Add a 10–100 µF electrolytic capacitor across 3V3 and GND to absorb current spikes. If you soldered the module yourself, reflow the pins around the flash chip.

Question 5

ESP32: Flash verify failed (MD5 mismatch) — what does it mean?

Accepted Answer

After writing, the read-back does not match. Either the write was disturbed, or the flash address / mode is wrong. Retry at 115200 baud first. Check the flash mode: most modules use DIO, WROVER-class parts often QIO. When unsure, DIO is the safe choice. Verify each binary offset: bootloader 0x1000, partition table 0x8000, app 0x10000 (classic ESP32). If it keeps failing with correct offsets and mode, the flash chip is probably dead.

Question 6

ESP32: Firmware does not fit in flash — what does it mean?

Accepted Answer

The binary is bigger than the app partition. Very common with OTA enabled — two app slots cut usable space almost in half. Arduino IDE: Tools → Partition Scheme, pick a larger layout (e.g. "16M with spiffs" or "Minimal SPIFFS"). Disabling OTA (choose a non-OTA scheme) frees almost double the space. Lower the log level to Warning / Error — that alone saves tens of KB. ESP-IDF: run idf.py size-files to see which component dominates.

Question 7

ESP32: Brownout detector was triggered — what does it mean?

Accepted Answer

The chip saw its own supply drop below the threshold and reset itself. Wi-Fi transmit bursts draw the most current. Your code is not the problem. Use an external 5 V supply of at least 1 A — not a computer USB port, especially not a front panel or unpowered hub. Add 100 µF electrolytic plus 0.1 µF ceramic across 3V3 and GND, as close to the module as possible. Try reducing Wi-Fi TX power: WiFi.setTxPower(WIFI_POWER_8_5dBm). As a stopgap you can lower or disable the brownout threshold in menuconfig, but that only hides the problem — fix the power.

Question 8

ESP32: Watchdog reset (rst:0x10 / 0x7 / 0x8) — what does it mean?

Accepted Answer

The chip decided the firmware was stuck and rebooted. 0x10 means it hung during boot (bootloader watchdog); 0x7/0x8 mean a FreeRTOS task stopped feeding the task watchdog. Look at the task name in parentheses after Task watchdog got triggered — that is the stuck task. Every loop needs a vTaskDelay() / delay(), even 1 ms, so the scheduler can run. Check for unthrottled printf / Serial.println in a loop — serial is line-buffered and will stall the system. For rst:0x10, verify PSRAM and flash mode settings first, then initialisation code before app_main.

Question 9

ESP32: Garbled serial output — usually just the wrong baud rate — what does it mean?

Accepted Answer

The ESP32 bootloader prints its banner at 74880 baud. If your monitor is set to 9600 or 115200 you will see garbage — this is normal, not a broken board. Set the serial monitor to 115200 (the default for almost all firmware). Use 74880 if you want to read the bootloader banner. Arduino users: the value in Serial.begin(115200) must match the monitor.

Question 10

ESP32: LoadProhibited — reading memory it should not — what does it mean?

Accepted Answer

The code read from an invalid address — usually a NULL pointer, a wild pointer, or an object used after free. Check EXCVADDR: 0x00000000 almost always means dereferencing NULL. Read EXCVADDR: zero means NULL, a small value means a struct member, garbage means an uninitialised pointer. Convert backtrace addresses with addr2line -e build/xxx.elf 0x400dxxxx. ESP-IDF users: idf.py monitor decodes the backtrace into function names and line numbers automatically. Null-check every call that can return NULL: malloc, calloc, container lookups, hardware init.

Question 11

ESP32: StoreProhibited — writing memory it should not — what does it mean?

Accepted Answer

A write to an invalid address — a read-only region, a NULL struct member, or past the end of an array. Use EXCVADDR to find the address being written, then match it against the backtrace. Replace strcpy with strncpy or snprintf — always bound string writes. Check array index limits, especially where the index is a variable. Make sure the target buffer is still valid when written (not a local that went out of scope).

Question 12

ESP32: IllegalInstruction — the CPU executed something that is not code — what does it mean?

Accepted Answer

The program counter jumped somewhere invalid. Usually a corrupted function pointer, a smashed stack, or flash pins reconfigured as GPIO so instructions cannot be fetched. Check whether your code touches GPIO6–11 (classic ESP32) — those are wired to the flash and must stay free. Release any reconfigured flash pins back to their default function. Verify every function pointer is initialised before it is called. Turn on compiler warnings and add the missing return statements in non-void functions.

Question 13

ESP32: InstrFetchProhibited — cannot fetch an instruction — what does it mean?

Accepted Answer

The CPU tried to execute code from an address outside valid instruction memory. If PC is 0 or garbage, a function pointer is broken. Check PC: anything not starting with 0x4xxxxxxx is an invalid jump target. Verify every callback registration succeeded before invoking it. Increase the stack size of suspect tasks to rule out overflow.

Question 14

ESP32: Stack overflow — task stack too small — what does it mean?

Accepted Answer

The task used more stack than allocated and stomped on the canary. Compared with a mystery crash this is good news: it names the task. Bump the stack size for that task one notch (2048 → 4096 → 8192). Move large arrays to static or allocate them on the heap. Use uxTaskGetStackHighWaterMark() to see actual usage and size it properly. The printf family is stack-hungry, especially with JSON or long strings — trim it.

Question 15

ESP32: Task watchdog got triggered — what does it mean?

Accepted Answer

The idle task has not run for too long, meaning some task is hogging the CPU. The log usually names the offending task. Find the task named in the log and add vTaskDelay(1) / delay(1) inside its loop. In an ISR only set a flag or push to a queue; do the real work in a task. Review mutex locking order to avoid circular waits. For genuinely long computations, pin the task to another core or call vTaskDelay periodically.

Question 16

ESP32: abort() / assert failed — what does it mean?

Accepted Answer

Not a hardware fault — the code or a library called abort deliberately. The assert line names the file, line and condition, which makes this the easiest crash to fix. Note the file and line from the assert line and read that condition directly. Scroll up to the last E (...) line before the abort — that is usually the real cause. Make sure the peripheral was initialised (begin() / init()) before use. If it points inside a library, it is likely a version mismatch — upgrade or downgrade.

Question 17

ESP32: Cache disabled but cached memory region accessed — what does it mean?

Accepted Answer

During flash erase/write the cache is temporarily disabled, so calling a function that lives in flash — or taking an interrupt — crashes. ESP-IDF solves this with IRAM_ATTR. Add IRAM_ATTR to the ISR and DRAM_ATTR to the constants it uses. Disable the relevant interrupts around flash writes, or use spi_flash_disable_interrupts_caches_and_other_cpu(). Guard NVS access with a mutex when several tasks are involved.

Question 18

ESP32: Out of memory — what does it mean?

Accepted Answer

The heap ran out. Classic ESP32 has roughly 300 KB of usable DRAM, and Wi-Fi + TLS + camera eats through it fast. Print esp_get_free_heap_size() periodically to tell a slow leak from a one-off shortfall. On ESP32-S3 / WROVER: enable PSRAM in menuconfig and allocate big buffers with MALLOC_CAP_SPIRAM. Always cJSON_Delete() after parsing and esp_camera_fb_return() after each camera frame. Fewer concurrent TLS connections and less string concatenation — stream or chunk instead.

Question 19

ESP32: PSRAM initialisation failed — what does it mean?

Accepted Answer

The chip cannot find external PSRAM. Either the module has none, or the setting is on but the hardware (or pinout) does not support it. Confirm the module: ESP32-WROOM has no PSRAM, ESP32-WROVER does. Read the marking on the module. Arduino: Tools → PSRAM, set Disabled, or pick OPI PSRAM on the S3. ESP-IDF: menuconfig → Component config → ESP PSRAM, disable or choose the right type. If the module really has PSRAM but the ID read fails, check whether GPIO16/17 (classic ESP32) are in use.

Question 20

ESP32: DRAM region overflowed — what does it mean?

Accepted Answer

This fails at link time: your globals and statics together exceed usable DRAM. Failing at build time is much easier than crashing at runtime. Allocate large arrays dynamically, or mark them EXT_RAM_BSS_ATTR to place them in PSRAM. ESP-IDF: run idf.py size-components to see who uses the DRAM. Lower the log level and disable unneeded debug options.

Question 21

ESP32: Wi-Fi network not found or refused — what does it mean?

Accepted Answer

ESP32 is 2.4 GHz only — no 5 GHz support. If your router uses band steering or you share a 5 GHz phone hotspot, the ESP32 simply cannot see the network. Make sure the router broadcasts 2.4 GHz. For a phone hotspot, explicitly select 2.4 GHz in settings. Disable band steering / "smart connect" so 2.4 G and 5 G show as separate networks. Retype the SSID and password — case matters. Write a minimal sketch that only calls WiFi.begin() and prints WiFi.status() to rule out other code.

Question 22

ESP32: Wi-Fi authentication failed — what does it mean?

Accepted Answer

The password is right but the handshake fails. Common with WPA2/WPA3 mixed mode, incompatible encryption, or poor signal causing handshake timeouts. Temporarily set the router to plain WPA2-PSK (AES) and retry. Test within two metres of the router to rule out signal issues. Escape backslashes and quotes correctly in C/C++ string literals. Update ESP-IDF or the Arduino-ESP32 core for WPA3 support.

Question 23

ESP32: MQTT connection failing or looping — what does it mean?

Accepted Answer

The network works but the MQTT handshake fails. Read the return code: -2 means timeout (network layer), 4/5 bad credentials, 2 rejected client ID. Generate a unique client ID per device (the last bytes of the MAC work well). Connect once from a desktop client such as MQTTX with the same parameters to rule out the broker. Set keepalive to 60 seconds or less. With TLS, check the root certificate and sync the clock via NTP — a wrong time breaks certificate validation.

Question 24

ESP32: TLS / HTTPS handshake failed — what does it mean?

Accepted Answer

HTTPS cannot be established. The most common cause is a wrong device clock making the certificate "not yet valid", followed by a missing or expired root certificate. Sync the clock via NTP before making HTTPS requests. Make sure the correct root certificate PEM is embedded in the firmware. Set SNI (the hostname field of esp_http_client_config_t in ESP-IDF). Print esp_get_free_heap_size() — a TLS handshake needs well over 40 KB contiguous.

Question 25

ESP32: Camera probe failed — what does it mean?

Accepted Answer

The ESP32 could not handshake with the camera over SCCB. The number one cause is always the ribbon cable; number two is the wrong board model in code. Reseat the ribbon cable fully and lock the connector — this alone fixes half of all cases. Keep exactly one #define CAMERA_MODEL_AI_THINKER uncommented; comment out the rest. Power from a separate 5 V / 2 A supply — not a computer USB port, and never the 3.3 V pin. Run the official CameraWebServer example first to prove the hardware before touching your own code.

Question 26

ESP32: Frame buffer failure or corrupted image — what does it mean?

Accepted Answer

The frame buffer could not be allocated, or DMA could not keep up so data is misaligned. Green or garbled images almost always mean PSRAM is off or the resolution is too high. Arduino: Tools → PSRAM → Enabled, and pick a Wrover-class partition scheme. Check that psramFound() returns true; if not, it is not active. Drop to QVGA (320×240) or VGA first, then raise resolution gradually. Always call esp_camera_fb_return(fb) after esp_camera_fb_get().

Question 27

ESP32: OTA update failed or rolled back — what does it mean?

Accepted Answer

The new firmware was written but validation failed, or the app never confirmed it booted successfully — so the chip rolled back. That is a safety feature, not a bug. Make sure the partition table has two app slots (ota_0 / ota_1). Check that the firmware fits inside one app partition. After the new firmware boots and self-checks (for example, once MQTT connects), call esp_ota_mark_app_valid_cancel_rollback() immediately. Verify MD5/SHA after download and add retries for flaky networks.

Question 28

ESP32: ADC2 conflict with Wi-Fi — what does it mean?

Accepted Answer

On classic ESP32 the ADC2 channels are used by the Wi-Fi driver, so readings are unreliable whenever Wi-Fi is on. That is architecture, not a bug. Move to ADC1: GPIO32–39 on classic ESP32 — the only reliable choice. If ADC2 is unavoidable, read it only while Wi-Fi is off, then bring Wi-Fi back up. For battery monitoring always use ADC1, plus a 100 nF bypass capacitor and averaging.

Question 29

ESP32: I²C communication failure — what does it mean?

Accepted Answer

The host sent an address but no device pulled SDA low. Usually a wrong address, missing pull-ups, or an unpowered device. Add a 4.7 kΩ pull-up to 3.3 V on SDA and SCL (2.2 kΩ for long runs or many devices). Run an I²C scanner and print the real addresses — do not guess. Confirm the slave is powered and shares ground with the ESP32. Never use GPIO34–39 (input-only, no internal pull-up) for I²C.

Question 30

ESP32: Strapping pin at the wrong level — what does it mean?

Accepted Answer

The strapping pins (GPIO0/2/5/12/15) decide how the chip boots. If external circuitry pulls them the wrong way you get bizarre symptoms — the classic one is GPIO12 held high, feeding the flash 1.8 V and bricking the board. Measure each strapping pin at power-up with a multimeter and compare against the datasheet requirements. GPIO12: must be low (or left floating with the internal pull-down) at boot. Never attach anything that drives it high. GPIO0: 10 kΩ pull-up plus a button to ground; do not connect circuitry that holds it low. GPIO15: 10 kΩ pull-down; do not leave it floating or pull it high.

Question 31

ESP32: Deep sleep will not wake or wakes immediately — what does it mean?

Accepted Answer

Either it never wakes, or it wakes instantly. The first is a misconfigured wake source; the second means the wake pin is already at the trigger level. Make sure the wake pin is an RTC GPIO (on ESP32 the RTC subset of GPIO0/2/4/12–15/25–27/32–39). Fit external pull-up/down so the wake pin sits at the non-triggering level. ext0 supports one pin only; ext1 supports several and you must choose "any" or "all". Re-initialise every peripheral (Wire, SPI, serial, Wi-Fi) after waking.

Question 32

ESP32: Header not found — missing library — what does it mean?

Accepted Answer

The compiler cannot find an #include. In Arduino the library is missing; in ESP-IDF the component was not added to CMakeLists. Arduino: Project → Load Library → Manage Libraries, search and install, then restart the IDE. Watch the version — many samples state "requires x.y.z", so do not grab the latest. ESP-IDF: add set(EXTRA_COMPONENT_DIRS ...) to CMakeLists.txt. When dropping libraries into ~/Arduino/libraries/, the folder name must match the .h file name.

Question 33

ESP32: API changed — sample code vs newer library — what does it mean?

Accepted Answer

The most common reason copied sample code will not compile. The ESP32 Arduino core changed many APIs between 2.x and 3.x, breaking older examples. Pin the core version the sample requires (e.g. 2.0.17 or a specific 3.x) in the Arduino boards manager. Take the function name from the error and compare against the current example in the library's examples folder. ESP8266 code does not run on ESP32 unchanged — especially Wi-Fi and filesystem parts. Or use PlatformIO and pin versions in platformio.ini for a reproducible environment.

Question 34

ESP32: ESP-IDF toolchain not set up — what does it mean?

Accepted Answer

Environment variables or the Python virtualenv are not active, so idf.py / cmake / python cannot be found. Run . $IDF_PATH/export.sh (export.bat on Windows) in every new terminal. On Windows, prefer the official ESP-IDF installer — it handles paths and dependencies for you. Keep project paths free of spaces and non-ASCII characters. Re-run install.sh to repair missing Python packages.

ESP32 error decoder

Why this exists

Full error index

⬇ Flashing

⚡ Power & reset

💥 Runtime crash

📶 Wi-Fi & network

📷 Camera

🧠 Memory & PSRAM

🔄 OTA update

🔌 Hardware & I/O

🛠 Build & toolchain

Cannot connect: esptool waits for a reply that never comes	The serial port exists, but the chip is not in download mode at that moment. This is the…
Wrong boot mode detected	The strapping pins were sampled at a level combination that is not download mode — GPIO0…
Cannot open the serial port	This fails at the OS level, before the chip is involved. On Windows it is usually driver…
Connected but writing to flash fails	Handshake succeeded but the actual write failed. Flash writing draws peak current — this…
Flash verify failed (MD5 mismatch)	After writing, the read-back does not match. Either the write was disturbed, or the flas…
Firmware does not fit in flash	The binary is bigger than the app partition. Very common with OTA enabled — two app slot…

Brownout detector was triggered	The chip saw its own supply drop below the threshold and reset itself. Wi-Fi transmit bu…
Watchdog reset (rst:0x10 / 0x7 / 0x8)	The chip decided the firmware was stuck and rebooted. 0x10 means it hung during boot (bo…
Garbled serial output — usually just the wrong baud rate	The ESP32 bootloader prints its banner at 74880 baud. If your monitor is set to 9600 or …

LoadProhibited — reading memory it should not	The code read from an invalid address — usually a NULL pointer, a wild pointer, or an ob…
StoreProhibited — writing memory it should not	A write to an invalid address — a read-only region, a NULL struct member, or past the en…
IllegalInstruction — the CPU executed something that is not code	The program counter jumped somewhere invalid. Usually a corrupted function pointer, a sm…
InstrFetchProhibited — cannot fetch an instruction	The CPU tried to execute code from an address outside valid instruction memory. If PC is…
Stack overflow — task stack too small	The task used more stack than allocated and stomped on the canary. Compared with a myste…
Task watchdog got triggered	The idle task has not run for too long, meaning some task is hogging the CPU. The log us…
abort() / assert failed	Not a hardware fault — the code or a library called abort deliberately. The assert line …
Cache disabled but cached memory region accessed	During flash erase/write the cache is temporarily disabled, so calling a function that l…

Wi-Fi network not found or refused	ESP32 is 2.4 GHz only — no 5 GHz support. If your router uses band steering or you share…
Wi-Fi authentication failed	The password is right but the handshake fails. Common with WPA2/WPA3 mixed mode, incompa…
MQTT connection failing or looping	The network works but the MQTT handshake fails. Read the return code: -2 means timeout (…
TLS / HTTPS handshake failed	HTTPS cannot be established. The most common cause is a wrong device clock making the ce…

Camera probe failed	The ESP32 could not handshake with the camera over SCCB. The number one cause is always …
Frame buffer failure or corrupted image	The frame buffer could not be allocated, or DMA could not keep up so data is misaligned.…

Out of memory	The heap ran out. Classic ESP32 has roughly 300 KB of usable DRAM, and Wi-Fi + TLS + cam…
PSRAM initialisation failed	The chip cannot find external PSRAM. Either the module has none, or the setting is on bu…
DRAM region overflowed	This fails at link time: your globals and statics together exceed usable DRAM. Failing a…

ADC2 conflict with Wi-Fi	On classic ESP32 the ADC2 channels are used by the Wi-Fi driver, so readings are unrelia…
I²C communication failure	The host sent an address but no device pulled SDA low. Usually a wrong address, missing …
Strapping pin at the wrong level	The strapping pins (GPIO0/2/5/12/15) decide how the chip boots. If external circuitry pu…
Deep sleep will not wake or wakes immediately	Either it never wakes, or it wakes instantly. The first is a misconfigured wake source; …

Header not found — missing library	The compiler cannot find an #include. In Arduino the library is missing; in ESP-IDF the …
API changed — sample code vs newer library	The most common reason copied sample code will not compile. The ESP32 Arduino core chang…
ESP-IDF toolchain not set up	Environment variables or the Python virtualenv are not active, so idf.py / cmake / pytho…