MD5 error on ESP32-WROOM

[jmuellers]

Hello!

I am working with the board "ESP-32 Dev Kit C V4" from AZ-delivery, which contains ESP-WROOM-32.
My project are working fine, and I made some progress with the library IRremote (V4.0.0). I changed to IRremoteESP8266, since I am trying to decode signals from a Hisense AC.

Below a snippet from my code. As soon as I add irrecv.enableIRIn(); I will receive MD5 errors at the end of programming:

Wrote 834064 bytes (521893 compressed) at 0x00010000 in 7.4 seconds (effective 904.1 kbit/s)...
File md5: d7f7efc6335b5c5b43b660b709e22bb7
Flash md5: 38a7f4af5a64a87e5cca7df47fca2ded
MD5 of 0xFF is 4df52851ea707acc381e9bdec8c1eeb2

A fatal error occurred: MD5 of file does not match data in flash!
Failed uploading: uploading error: exit status 2

Pin 34 is a digital input port. To my knowledge it is not a strapping pin. I also tried pin 39.
See pinout.
In any case it was working fine on the same pin using IRremote V4.0.0.

Is this library not ESP32 compatible? Does anyone have an idea what could be going wrong?

#include <IRremoteESP8266.h>
#include <IRrecv.h>
#include <IRutils.h>

// [...]

#define IR_IN    34
IRrecv irrecv(IR_IN);
decode_results irResults;

// [...]

void setup() {
   irrecv.enableIRIn();
   // [...]
}

[NiKiZe]

Does it change with default pin? Does it error out with any of the examples (unmodified) ?

We might need a minimal reproducible sample.

[crankyoldgit]

An MD5 hash is an integrity check. Its failing is telling you that the two pieces of data (program(s)) are different some how.
If I'm reading what you're saying correctly, that output is telling you the data (program) you've uploaded to the ESP32 is not the same as what the ESP is reporting it has loaded. i.e. There is corruption somehow. Perhaps bad flash memory on the ESP32.
I am fairly confident this is not an IRremoteESP8266 library problem, but it is either a problem in your build/upload tool chain, or more likely, something is wrong with that particulare ESP32 module.
My guess is adding the library to your sketch/program has increased the size of the flash data binary, and it's now overlapping some corrupt (damaged) flash memory on your ESP32 module. Or, less likely, your usb serial connection is being corrupted somehow.

In short, the MD5 error is telling you there is corruption in the uploading process. This library has no influence what so ever on that processes. Your problem is not with the library, but elsewhere.

[crankyoldgit]

FYI, A quick google of your error message yields:
https://forum.arduino.cc/t/esp32-cam-md5-programming-error/1040371/7

Other possiblities listed in other search results are your 5V powersupply may not be good/strong enough etc causing the upload to fail.

[jmuellers]

Hello David,
thank you for your reply. I also suspected it has to do with the increased size of the image.
I am sure it has nothing to do with the cable, it reproducibly works every time I do comment the line in question. It is not impossible that it is an edge case where due to the size of the image being written to flash, a power drop occurs, who knows.

I will work on a minimum example as suggested by NiKiZe to further track it down.