Fix ESP8266 WDT Reset After ESP.wdtDisable(): Hardware vs. Software Watchdog

Error Code: MCU_ERR_0061

title: "Fix ESP8266 WDT Reset After ESP.wdtDisable(): Hardware vs. Software Watchdog" slug: fix-esp8266-wdt-reset-after-esp-wdtdisable-hardware-watchdog metadescription: "ESP8266 still rebooting with 'wdt reset' after calling ESP.wdtDisable()? Learn why the 6-8s Hardware Watchdog cannot be disabled and how to yield properly." excerpt: "Disabled the watchdog with ESP.wdtDisable() but your ESP8266 still crashes with 'wdt reset' after 6 seconds? Discover the unstoppable Hardware Watchdog and how to feed it." primarykeywords: - "esp8266 wdt reset after esp wdtdisable" - "esp wdtdisable not working esp8266" - "esp8266 hardware vs software watchdog timer" secondarykeywords: - "esp8266 rst cause 4 hardware wdt reset" - "esp wdtfeed yield delay 0 esp8266" - "esp8266 long math calculation wdt reset" - "how to disable hardware watchdog esp8266" canonicalurl: "https://mentora.school/blog/fix-esp8266-wdt-reset-after-esp-wdtdisable-hardware-watchdog" author: "Mentora Hardware Troubleshooting Bench" date: "2026-10-24"

Article Publishing & SEO / AEO Metadata

Metadata Field

Specification

Article Title

Fix ESP8266 WDT Reset After ESP.wdtDisable(): Hardware vs. Software Watchdog

Target Slug

fix-esp8266-wdt-reset-after-esp-wdtdisable-hardware-watchdog

Canonical URL

https://mentora.school/blog/fix-esp8266-wdt-reset-after-esp-wdtdisable-hardware-watchdog

Meta Description (157 chars)

ESP8266 still rebooting with 'wdt reset' after calling ESP.wdtDisable()? Learn why the 6-8s Hardware Watchdog cannot be disabled and how to yield properly.

Post Excerpt

Disabled the watchdog with ESP.wdtDisable() but your ESP8266 still crashes with 'wdt reset' after 6 seconds? Discover the unstoppable Hardware Watchdog and how to feed it.

Primary Keywords

esp8266 wdt reset after esp wdtdisable, esp wdtdisable not working esp8266, esp8266 hardware vs software watchdog timer

Secondary Keywords

esp8266 rst cause 4 hardware wdt reset, esp wdtfeed yield delay 0 esp8266, esp8266 long math calculation wdt reset, how to disable hardware watchdog esp8266

Author & Date

Mentora Hardware Troubleshooting Bench | October 24, 2026

DELIVERABLE 1: The Mentora School Blog Post

Fix ESP8266 WDT Reset After ESP.wdtDisable(): Hardware vs. Software Watchdog

Quick Answer (AEO / 60-Second Summary)

Symptom: You have a long-running calculation, cryptographic loop, or blocking sensor routine on an ESP8266 that takes 6 to 10 seconds. To prevent a Watchdog Timer (WDT) reset, you call ESP.wdtDisable(); before the loop. However, after approximately 6 to 8 seconds, the ESP8266 still crashes and reboots with: ets Jan 8 2013,rst cause:4, boot mode:(3,6) wdt reset

Root Cause (Dual Watchdog Architecture): The ESP8266 possesses two completely independent watchdog timers:

The Software Watchdog Timer (SW WDT - ~3.2s timeout): Managed by the Espressif Non-OS SDK. Calling ESP.wdtDisable() disables only the Software Watchdog.

The Hardware Watchdog Timer (HW WDT - ~6.0s to 8.4s timeout): Built directly into the silicon peripheral registers (0x60000900). The Hardware Watchdog CANNOT be permanently disabled by ESP.wdtDisable()! If your code blocks for more than ~6 seconds without feeding the watchdog or yielding to the background Wi-Fi stack, the Hardware WDT forces a hard silicon reset (rst cause:4).

The Solution:

Leave the Software WDT Enabled and Call yield() / ESP.wdtFeed(): Remove ESP.wdtDisable() and place yield(); (or ESP.wdtFeed(); if interrupts/scheduler cannot run) inside your compute loop so it executes at least once every 500–1000 milliseconds.

Refactor Blocking Loops into Non-Blocking State Machines: Break multi-second calculations into incremental steps across loop() iterations so the ESP8266 Wi-Fi MAC and TCP/IP stack never starve.

Technical Deep-Dive: The Dual-Watchdog Architecture of the ESP8266

Unlike an 8-bit Arduino Uno (where your sketch owns 100% of the CPU and can stay inside a while loop for days), the ESP8266 is a single-core 32-bit Tensilica Xtensa LX106 microcontroller that shares its single CPU between your Arduino sketch and the Espressif 802.11 Wi-Fi / lwIP TCP/IP protocol stack.

To guarantee that a bug in user code never permanently freezes the Wi-Fi radio, Espressif implemented a two-tier safety net:

ESP8266 TWO-TIER WATCHDOG ARCHITECTURE: [ User Sketch Loop ] │ ├──► Tier 1: Software Watchdog (SW WDT) │ • Timeout: ~1.5s to 3.2 seconds │ • Can be disabled by ESP.wdtDisable()? YES │ • Crash output: "Soft WDT reset" + Stack Trace │ └──► Tier 2: Hardware Watchdog (HW WDT - Register 0x60000900) • Timeout: ~6.0s to 8.4 seconds • Can be disabled by ESP.wdtDisable()? NO! (Silicon-enforced) • Crash output: "wdt reset" + "rst cause:4"

Watchdog Type

Timeout Window

Reset Cause Code

Serial Monitor Output

Affected by ESP.wdtDisable()?

Software WDT

∼3.2seconds

rst cause:2 or 4

Soft WDT reset + >>>stack>>>

Yes (Disabled by ESP.wdtDisable())

Hardware WDT

∼6.0--8.4seconds

rst cause:4

wdt reset (Boot ROM at 74880 baud)

No (Continues ticking and resets CPU!)

When you call ESP.wdtDisable(), the Software WDT steps aside, allowing your blocking loop to pass the 3.2-second mark. However, the Hardware WDT timer continues counting down in silicon. At ~6.5 seconds, the Hardware WDT expires and yanks the internal CPU reset line!

2 Proven Fixes to Prevent Hardware WDT Resets

Fix 1: Call yield() or ESP.wdtFeed() Inside Long Compute Loops

Instead of disabling the watchdog, keep both watchdogs enabled and feed them periodically inside your inner loop:

void performHeavyCalculation() { // DO NOT call ESP.wdtDisable()! for (uint32_t i = 0; i < 5000000; i++) { // Perform math step... // Every 10,000 iterations (~50ms), service the watchdog and Wi-Fi stack: if (i % 10000 == 0) { yield(); // Feeds both SW WDT and HW WDT, and services Wi-Fi! // Or use ESP.wdtFeed(); if you only want to reset the WDT counter } }}

Fix 2: Refactor Multi-Second Loops into Non-Blocking Chunks

If you are computing a large lookup table, cryptographic hash, or image buffer, process a small chunk on each pass of void loop():

uint32t currentStep = 0;const uint32t TOTALSTEPS = 1000000;bool calculationDone = false;void loop() { if (!calculationDone) { // Process 5,000 steps per loop() pass (~25ms), then let loop() return! for (int k = 0; k < 5000 && currentStep < TOTALSTEPS; k++) { computeStep(currentStep++); } if (currentStep >= TOTAL_STEPS) { calculationDone = true; Serial.println("Calculation complete with zero WDT resets!"); } }}

Frequently Asked Questions

What is the difference between yield(), delay(0), and ESP.wdtFeed()?

yield() and delay(0) are identical on ESP8266: they feed the watchdog and switch context to the Non-OS SDK background task so incoming Wi-Fi and TCP packets are processed.

ESP.wdtFeed() resets the watchdog timer counter directly without switching context to the Wi-Fi stack. Note that if you only call ESP.wdtFeed() for more than 5–10 seconds without calling yield(), the Wi-Fi connection will drop even though the CPU doesn't reset!

For more bare-metal embedded tutorials, register-level debugging guides, and ESP8266 RTOS/watchdog workflows, explore Mentora School.

DELIVERABLE 2: The Community Forum Reply Message

Target Thread: GitHub Issues: esp8266/Arduino #7344

Recipient: Anonymous / GitHub esp8266 Community

The reason your ESP8266 still reboots after 6 seconds—even after calling ESP.wdtDisable()—is that the ESP8266 has two separate watchdog timers:

Software Watchdog (~3.2 seconds): Managed by the software SDK. Calling ESP.wdtDisable() disables only this software watchdog.

Hardware Watchdog (~6.0 to 8.4 seconds): Built into the physical silicon timer registers (0x60000900). The Hardware Watchdog cannot be disabled by ESP.wdtDisable()! When your math calculation blocks for 8 seconds without feeding the watchdog, the Hardware WDT forces a hard reset (rst cause:4 / wdt reset).

How to Fix Your 8-Second Calculation

Remove ESP.wdtDisable() and instead call yield() (or ESP.wdtFeed()) periodically inside your calculation loop:

// Every ~100ms worth of iterations, feed the watchdog & Wi-Fi stack:if (i % 5000 == 0) {    yield(); // Resets both SW and HW watchdogs and keeps Wi-Fi alive!}
} ```
I wrote a full breakdown of the ESP8266 dual-watchdog architecture (Software vs. Hardware WDT) on Mentora: https://mentora.school/blog/fix-esp8266-wdt-reset-after-esp-wdtdisable-hardware-watchdog