Hi Chris! I'd like to elaborate what we currently have. We have a "Linux target" that you can switch on like any other ESP chip target. But this for now is only good for very isolated unit testing. E.g., you can test all the code of a potential sensor driver for an I2C sensor that uses the IDF I2C d...

I think we won't really have a solution for that. I'm afraid changing the build system to output the preprocessed header files to feed them into CMock would be quite complicated to maintain. However, we have the same problem in IDF and to solve this, two possibilities come to my mind: 1. If it's jus...

For the power consumption of the ESP32 chip, you can refer to the chip's datasheet: https://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf. For the power consumption of any of the modules, you can refer to their respective datasheets from here: https://www.espressif.com/e...

Not sure but the warning might be from the task watchdog timer (task WDT). You're using a big while loop inside your main function which never waits long enough to give the idle task a chance to run and feed the WDT. You can read more about watchdogs in the watchdog documentation: https://docs.espre...

FreeRTOS is the operating system, esp_event is a mechanism for synchronisation or message sending, hence you can't compare these in this sense. As already mentioned, esp_event is built on FreeRTOS, in particular the FreeRTOS queue. If you use the default esp_event loop, it will create a task in the ...

Hi Jonas, the NVS functions are all blocking. There is no background thread going on. Since NVS may re-order data if one page is full, there's a potential erasure of flash which takes a "long" time, blocking the current thread. If you want to do something during the time of writing, then please use ...

I think the pulse counter peripheral may be more suited for your application.

Documentation and example code can be found here: https://docs.espressif.com/projects/esp ... /pcnt.html.

Best,
Jakob

Hi wijnsema,

did you flash all the new partitions to your board? Or have you tried to do a full erase of the flash? If one of the mentioned actions fixes the problem, probably something went wrong during the switch to the new partition table. But let's first see whether that's the case.

Best,
Jakob

Hi! Several things to consider here. First, printf functions may consume quite some memory. I heard that 1 to 1.5k can be considered usual. Please not that the high water mark API reports the minimum available stack space: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/sys...

Hi jmcornil,

we had some issues with re-using the I2C commands. I personally don't know the details but for now, please create a new I2C command for every transaction.

Best,
Jakob