I did implement a logging facility, but it was more elaborate than I first thought it would be (source file was almost 1200 lines).

No side effects that I'm aware of. Still works just fine.

Well, you could use the return from the call.

I realize this thread is ancient, but today I got bitten by the long execution time of esp_ota_begin(). In looking at the source code, I discovered the OTA_WITH_SEQUENTIAL_WRITES macro which can be used as the 2nd argument. It changed the execution time of esp_ota_begin() from about 3 seconds to ...

Hi Chegewara -

I'm not really sure what you mean - can you please give me a little more detail as to what I'm supposed to do?

Thanks...

Hi Chegewara - so, does this mean I need to pull GPIO12 low prior to calling esp_restart()?

Thanks...

Hi all -

My app issues an esp_restart() command, and I get these messages:

I (348163) wifi:state: run -> init (0)
I (348173) wifi:pm stop, total sleep time: 203864605 us / 343318182 us

W (348173) wifi:<ba-del>idx
W (348173) wifi:<ba-del>idx
I (348183) wi��ets Jun 8 2016 00:22:57

waiting for ...

Hi ESP_Mahavir -

This does eliminate the compile time errors. It appears, however, that I'm using a routine found in the openthread component, instead of the mbedtls component: Am I correctly interpreting this window?

Thanks...

Hi all -

I'm porting a program to the ESP32. I just enabled the portion of code that uses md5 (it supplies its own files for this) and now I can't link. When I try to use the files in my project folder, this code passage:
mbedtls_md5_init(&Zctx);
mbedtls_md5_starts(&Zctx);
results in this error ...

There's something about the build process I still don't understand. If I do a clean, I get build errors when I try to build from within the IDE. Running idf.py build fixes that, but it also wipes out my compile_commands.json file, and replaces it with about 4800 lines including a ton of files from ...