There is a branch in the arduino repository for IDF4.0 that you can try, but to answer your question, wee will skip 4.0 and go directly to 4.2 (current IDF master) because of support for ESP32-S2. If you want to try that, there is an "esp32s2" branch that you can checkout

It's already added, just not in the master branch. Check the arduino repo for "esp32s2" branch and give it a go. Be warn that it's a work in progress so some things might be broken.

OK So I see two issues.

1. You should use SDMMC on Wrover-Kit
2. If you want to use SPI and use the LCD as well, you need to init first a new SPI port (HSPI) and then init the SD card to use that port.

LCD and SD do not share pins and the SPI port is going to the device initialised last.

You are not sending a response to the request in the alarm handler You must request->send(response) in every handler.

The exposure settings on those sensors is actually measured in lines. So for max res of 1600x1200 you can expose for the whole duration of 1200 lines. Not sure if that makes any sense :). For smaller resolutions you get less lines and less exposure. There are 3 main resolutions from which all others...

Hi Lucas, As far as I can understand, you want to collect all frames in the loop and give the latest to the web server. Am I correct? I will continue based on that assumption :) You should not use busy loops inside threads, instead you should use one of the FreeRTOS objects that allow for threads to...

please try to diagnose the problem a bit more. Just stop working does not give any clues I have ESP32 cams running for days without issues. What is the XCLK that you are using? What is in the logs when they stop? Which example are you running?

Can you swap the sensor on that board and try again? Put one from the other working cams and see if it's the board or the sensor that is faulty (I will bet on the sensor here). Error means that the ESP was not able to communicate over I2C with the camera, but the line before that means that the came...

I don't agree that things are not well documented. The camera driver is rather a basic thing. You setup the camera and start grabbing frame buffers from it. Structure of the frame buffer is in the header. Frame buffer in every case that I have seen contains an array of pixels in the form of (width *...

I'm really sorry you find this so frustrating. I had no idea that "GRAYSCALE", "RGB565" or any other of the formats need explanation. 1. GRAYSCALE means values from 0 to 255 for each pixel 2. RGB565 means that a 16 bit value is per pixel and is comprised from 5 bits red, 6 bits green and 5 bits blue...