There is an example of specifying custom MAC addresses in ESP-IDF: https://github.com/espressif/esp-idf/blob/master/examples/system/base_mac_address/main/base_mac_address_example_main.c. Basically, you need to call esp_base_mac_addr_set before starting WiFi. To get the default address, you can use e...

No, that's an internal structure which contains the handle: https://github.com/espressif/esp-idf/bl ... read.c#L51

When ULP is running constantly, current consumption will be closer to 1.4mA. It takes about 4 cycles for the ULP to wake up and go to sleep, the rest is determined by the program being run. For simple programs which only check GPIOs you can expect around 15uA current consumption. Above mentioned ulp...

Depending on duty cycle of your ULP program, ULP might be an option. Based on your description, duty cycle can be made very low — it would be sufficient to let ULP wake up every, say, 100ms and keep working for a few 100us. This would result in average current consumption little over the deep sleep ...

Sorry, this is a regression in latest master. Will be fixed shortly.

C++ threading is implemented on top of pthreads (that's the standard implentation in libstdc++v3) which in turn is implemented on top of FreeRTOS in ESP-IDF. So all threads (pthreads, c++11 threads) are actually FreeRTOS threads, just wrapped with some levels of indirection. Same applies to mutexes....

Perhaps something like

Such crash typically indicates memory corruption, when something overwrites a member of the semaphore (queue) structure. Can you please try to set heap checking level to "comprehensive" in menuconfig?

That's going to be =now*1000

What kind of file system is that, FAT or SPIFFS, and what is the storage, SD card (SDMMC or SPI?) or flash? Corruption by 2 bytes would have pointed to a potential DMA issue (such as when one attempts to use an unaligned DMA buffer) but 4 byte shift means that this is likely something else. Can you ...