Mastering ESP32 HTTPUpdate: Fixing OTA Errors and Flashing Firmware

The Verdict: Which ESP32 OTA Method to Choose

When deploying ESP32 firmware over the air, you have three primary paths. Choosing the wrong one leads to bricked devices or impossible maintenance cycles. Here is the decision matrix to lock in your architecture.

Hardware & Parts List: ESP32 HTTPUpdate Setup

While HTTPUpdate is a software library, a robust physical build requires visual feedback and a manual override trigger. This parts list targets the most common development board on the market.

Pin Mapping Table

Complete ESP32 HTTPUpdate Code (Arduino Core 3.x)

This code targets the ESP32 Dev Module board definition. It connects to WiFi, checks for a forced update via the GPIO 0 button, and executes the HTTP update with full error handling. It explicitly disables auto-reboot so you can execute cleanup tasks (like saving state to NVS) before restarting.

#include <WiFi.h>
#include <HTTPUpdate.h>

// --- PIN DEFINITIONS ---
#define STATUS_LED      2
#define FORCE_UPDATE_BTN 0

// --- NETWORK & SERVER CONFIG ---
const char* ssid     = "YOUR_WIFI_SSID";
const char* password = "YOUR_WIFI_PASSWORD";
const char* fw_url   = "http://192.168.1.100/firmware/v2.bin";

// Update check interval (1 hour)
const unsigned long updateInterval = 3600000; 
unsigned long lastUpdateCheck = 0;

void setup() {
  Serial.begin(115200);
  pinMode(STATUS_LED, OUTPUT);
  pinMode(FORCE_UPDATE_BTN, INPUT_PULLUP);
  
  digitalWrite(STATUS_LED, LOW);
  
  WiFi.begin(ssid, password);
  Serial.print("Connecting to WiFi");
  while (WiFi.status() != WL_CONNECTED) {
    delay(500);
    Serial.print(".");
  }
  Serial.println("\nConnected. IP: " + WiFi.localIP().toString());
}

void loop() {
  // Check for forced button press OR scheduled interval
  bool buttonPressed = (digitalRead(FORCE_UPDATE_BTN) == LOW);
  bool timeElapsed = (millis() - lastUpdateCheck > updateInterval);
  
  if (buttonPressed || timeElapsed) {
    lastUpdateCheck = millis();
    performOTAUpdate();
  }
  
  delay(100); // Yield to WiFi task
}

void performOTAUpdate() {
  Serial.println("[OTA] Starting HTTPUpdate...");
  digitalWrite(STATUS_LED, HIGH); // LED ON during update
  
  WiFiClient client;
  HTTPUpdate httpUpdate;
  
  // Configure HTTPUpdate behavior
  httpUpdate.setLedPin(-1); // We handle LED manually
  httpUpdate.rebootOnUpdate(false); // CRITICAL: Manual reboot for safety
  httpUpdate.setFollowRedirects(HTTPC_FORCE_FOLLOW_REDIRECTS);
  
  t_httpUpdate_return ret = httpUpdate.update(client, fw_url);
  
  switch(ret) {
    case HTTP_UPDATE_FAILED:
      Serial.printf("[OTA] Error (%d): %s\n", 
                    httpUpdate.getLastError(), 
                    httpUpdate.getLastErrorString().c_str());
      break;
      
    case HTTP_UPDATE_NO_UPDATES:
      Serial.println("[OTA] Server returned 304 Not Modified.");
      break;
      
    case HTTP_UPDATE_OK:
      Serial.println("[OTA] Success. Rebooting...");
      // Blink LED to indicate success before reboot
      for(int i=0; i<5; i++) {
        digitalWrite(STATUS_LED, !digitalRead(STATUS_LED));
        delay(100);
      }
      ESP.restart();
      break;
  }
  
  digitalWrite(STATUS_LED, LOW); // LED OFF on failure/no-update
}

Troubleshooting: Exact Error Strings and Ranked Causes

When HTTP_UPDATE_FAILED triggers, the getLastErrorString() method returns specific strings. Here is the exact translation of those strings and how to fix them.

1. Error String: "HTTP_UPDATE_NO_SPACE"

• Rank 1 (95%): Incorrect Partition Table. You are using the "Default 4MB with spiffs" scheme, which allocates one massive 3MB app partition. OTA requires two app partitions (Active and Standby).
• Fix: In the Arduino IDE, go to Tools > Partition Scheme and select "Default 4MB with OTA (1.2MB APP/1.5MB SPIFFS)" or "Minimal OTA (1.9MB APP/190KB SPIFFS)".

2. Error String: "Connection refused" or "Connect failed"

• Rank 1 (60%): The web server is down, or the IP address in fw_url is incorrect.
• Rank 2 (30%): Your router's AP Isolation (Guest Network) is blocking the ESP32 from talking to your local server.
• Rank 3 (10%): The ESP32 hasn't fully obtained an IP address before the update function fires (always check WiFi.status() == WL_CONNECTED first).

3. Error String: "Write to flash failed" or "Failed to write chunk"

• Rank 1 (80%): Insufficient contiguous heap memory. The ESP32 needs a large, unfragmented block of RAM to buffer the incoming binary chunks before writing to flash.
• Fix: Call ESP.getFreeHeap() and heap_caps_get_largest_free_block(MALLOC_CAP_8BIT) before triggering the update. If the largest block is under 100KB, close open files, disconnect MQTT, or free dynamically allocated buffers before calling httpUpdate.update().
• Rank 2 (20%): Flash chip degradation or a counterfeit ESP32 module with mismatched flash size.

The First Three Things to Check When OTA Fails

If your serial monitor just spits out a generic failure and you are stuck, run through this mandatory three-point checklist before rewriting your code.

Extending the Build: HTTPS and Rollbacks

Once you have basic HTTP updates working, production environments demand two upgrades: encrypted transport and safe rollbacks.

Upgrading to HTTPS

To use HTTPS, swap WiFiClient for WiFiClientSecure. You must provide the root CA certificate of your server. In Arduino Core 3.x, you can skip strict verification for internal servers using client.setInsecure(), but for public servers, embed the PEM certificate:

WiFiClientSecure client;
client.setCACert(root_ca_pem); // Your const char* PEM string
httpUpdate.update(client, "https://secure-server.com/fw.bin");

Note: TLS handshakes consume roughly 50KB-80KB of additional heap memory. Ensure you are using an ESP32 with PSRAM (like the ESP32-WROVER) if your application is already memory-heavy.

Implementing Safe Rollbacks

If your new firmware has a bug that prevents WiFi connection, the device will be bricked. The ESP32's native OTA API supports automatic rollbacks. To enable this, you must mark the new firmware as "valid" only after it successfully connects to the cloud.

According to the Espressif OTA Documentation, if you do not call esp_ota_mark_app_valid(), the bootloader will automatically revert to the previous partition on the next hard reset. Add this to your setup() function:

#include <esp_ota_ops.h>

void setup() {
  // ... WiFi connection code ...
  if (WiFi.status() == WL_CONNECTED) {
    // Mark this firmware as good. If we crash before this, 
    // the bootloader rolls back to the old firmware next boot.
    esp_ota_mark_app_valid();
  }
}

For deeper integration and advanced HTTP client configurations, always refer to the official Arduino ESP32 HTTPUpdate examples repository to ensure compatibility with the latest Core releases.

Final Recommendation: Start with plain HTTP on a local Nginx server to validate your partition scheme and memory management. Once the HTTP_UPDATE_OK path is proven, migrate to HTTPS with esp_ota_mark_app_valid() rollback protection before deploying to the field.