0xcf is the first byte of the *encrypted* image format, but it looks like it's written via function calls that expect the *decrypted* image.

I think that code would crash: you're calling a blocking function in a critical section. In general: That sleep mode is not intended to manually call, to be honest; it's ideal for a RTOS idle scenario as the way it sleeps makes it trivial to implement, with the downside being that the savings are no...

If the JSON is a single key/value store, you'd probably best off using the NVS (or specifically for Arduino, the 'preferences' library) rather than a spiffs. Just take the keys that you would put into the JSON file and feed them into the Preferences lib instead.

Glad to hear it works. No need to mark the answer as accepted, the forum doesn't have functionality for that.

All of them do. FreeRTOS detects when there's nothing better to do and runs the 'idle' task. This will put the core to sleep until the next tick interrupt or any other configured interrupt happens. Note that the core is only clockgated, not powered down, and all peripherals including the radios stil...

Dependent on what configuration you need, nvs could also be a good place to store it.

If you need OTA, you need two OTA partitions, ideally of the same size. (The factory partition is not required for OTA, though, so unless you know you need a factory partition, you can convert that into an OTA partition, giving you two 1.5MiB-sized OTA partitions.) Do you need to store files into in...

Have you looked at the example that comes with esp-idf? Probably easier to just copy/paste that.

Why would you need wifi.h in the first place? The 'normal' way to include wifi functions is by including esp_wifi.h.

Likely the module was subjected to something not good (overvoltage, power spike, static electricity, ...) that fried the flash chip inside the package. The ESP32 is trying to boot from that but fails. Normally the ESP32 itself doesn't get hot in that state; it's more likely that the flash broke in s...