macksal
commented
3 months ago EV-VSYNC-OVF is output when a VSYNC event can't be posted to the internal event queue. Events are posted by DMA and VSYNC interrupts and consumed by the camera task. The camera task is ultimately responsible for initiating DMA. The event overflow means that the CPU can't keep up with the events coming from the queue.
What's your XCLK/framerate? Remember RGB565 in particular is 2 bytes per pixel.
On the ESP32-S3, you can enable "psram mode", I think by setting xclk=16mhz. This removes the extra copy from "bounce buffers" during the frame, so the bottleneck usually becomes the memory bus rather than the CPU. Keep in mind the memory bus has a hard write limit of 80MB/s, but you're still competing with the same SPI bus used by the cpu to access psram/flash and the practical limit is much lower in non-ideal scenarios.
I haven't used RGB565 or YUV formats myself, and it is possible there's a bug. Since you're only seeing the issue at higher resolutions though, I think you are likely maxing out the bandwidth of either the CPU or memory bus.
SYPark0795
github-actions[bot]
ESP-IDF version: v6.2, v6.1.3 Board: ESP32S3 Xiao Sense Chip: ESP32-S3
Source code: https://pastebin.com/R87rAp32
When capture succeeds:
When capture fails:
I have changed Default/Maximum Log Verbosity in menuconfig to Verbose. It only increased the amount of log during the boot, but nothing more comes out around the capturing part.
As far as I can tell, multiple modules I own exhibit the same behavior.
Please give me any insights you have. Where in the source code I could take a look, where I could probe more, etc. I could look into the library itself, too. I'd be happy to hear even just "I have no idea".