Hi everyone. I’m using a GOOUUU ESP32-S3-CAM board with an OV2640 camera for an object recognition project, but I’m running into issues. I’m certain that the sensor, pinout, and esp32-camera driver are working perfectly.
The initial symptom was a “Panic handler entered multiple times” crash—a freeze involving memory corruption, followed by a reboot.
Attempts made so far, in order:
Wrong destination buffer size (96x96 while the camera was capturing in QQVGA)—fixed, but the crash persisted due to other causes.
Direct capture at 96x96 (JPEG and then RGB565)—both failed with known driver errors (FB-OVF/NO-EOI for JPEG; FB-SIZE mismatch for RGB565).
Capture at QQVGA (160x120) with RGB565 + software resizing—same FB-SIZE error (insufficient lines captured).
XCLK adjustment (10MHz and 80MHz)—didn’t solve it; 10MHz even caused an actual brownout (confirmed by the BOD log), ruling out the power supply as the root cause.
Capture at 240x240 with RGB565—same FB-SIZE mismatch pattern, confirming the issue wasn’t specific to small resolutions but rather the RGB565 (raw) format itself on this driver/board.
Capture at 240x240 with JPEG (the driver’s more mature format)—reverted to the double panic with heap corruption, occurring inconsistently between runs.
Increasing the loop task stack (16KB → 32KB) and removing run_classifier()—no change in behavior, ruling out stack overflow and the classifier as causes.
Minimal test: raw capture only, without any of our own processing—ran cleanly and stably over multiple iterations. I don’t know if the image format is incorrect or if I should have selected the custom board instead of the Espressif ESP-EYE.
If anyone has any information that might help, I would appreciate it.
The project ID is 1051194.
I am using Windows 11