Thanks for the reply. I'm also having some trouble with it, although I'm only trying to build IDF examples and my own projects at the moment. I've written a bit about my troubles here: viewtopic.php?f=13&t=11280

Looks like I'm getting the same behaviour on my Linux system - IDF_PATH must be set in both the command line (as -DIDF_PATH=...) and in the Environment table. If it's in neither or only one, I get an error from the IDF .cmake functions as per above. I naively assume that anything in the Environment ...

Hmm, a breakthrough! I was using the Environment "table" under Build, Execution, Deployment > CMake. I clicked the little rectangle symbol on the right and was adding IDF_PATH and PYTHON variables there: Capto_Capture 2019-07-03_15-03-48_.png However it turns out that this doesn't work on its own fo...

@ESP_cermak, thanks for your reply. I thought I'd try setting it up "from scratch" on my Mac (Mojave, 10.14.5) which I already have ESP IDF v3.2 installed on. I have cmake 3.14.0 installed. I did a fresh install of CLion 2019.1.4 and opened the CMakeLists.txt file from a freshly copied (from IDF v3....

I realise that this may be a bit tricky to convey as I'm running into a few different problems. One issue I have is that the docs here don't exist: https://docs.espressif.com/projects/esp-idf/en/v3.3-beta3/get-started-cmake/index.html - so I'm using a mixture of 3.2 and master to get by. In my origi...

What's the current status of this? I'm keen to test out the state-of-the-art and help if i can...

(Moderator's note: Moved to a new thread.) I've spent a bit of time this morning trying out the new CMake build system. I had a few issues with changes between 3.2.2, 3.3-beta3 and master but I was able to resolve those and get a non-trivial ESP32 project, written in C (not C++), with custom compone...

I've hit this problem with the example code too - and this thread is a bit confusing because it's not clear to me which changes apply to which other fixes. Does anyone have a working version of this example, for ESP-IDF v3.2, that correctly handles client disconnect/reconnects? ESP guys - it would b...

Ok, never mind, turns out I was passing a uint8_t as the length parameter. Embarrassing.

Sorry for the noise. ESP-IDF happily reads (much) more than 255 bytes per I2C transaction. If you read this far, I apologise for wasting your time.

I'm reading blocks of data from an IC device's internal FIFO over I2C. The device implements special FIFO read registers that "loop around" so that the master can continue to read over and over, allowing large amounts of data to be read in a single I2C transaction. I'm having a problem with IDF v3.2...