Closed SYPark0795 closed 2 months ago
This issue appears to be stale. Please close it if its no longer valid.
I'm still waiting for an answer.
Try to raise the JPEG quality to 10 first and then slowly lower it. Also the board you are using is known to overheat very quickly and to refuse then to work properly (I have it also). Some sort of radiator and airflow is a must for it. NO-EOI means that the sensor triggered VSYNC for new frame, but JPEG End Of Image marker was not found for the last frame
What I want to achieve is to capture a picture with high quality, so setting the quality to a higher value is not the point for me.
When I set the quality to 3 or 2, it does capture a picture when I point the camera at something visually simple, so that the JPEG picture size goes lower. AFAICT, it's never the problem of the heat. It often captures a picture after several consecutive failed attempts, and it always fails to capture when the image goes complicated.
I have also tried ESP32-CAM and it's giving the same error.
If the sensor is not providing the proper bytes, there is no way for the ESP to verify the image. There is nothing wrong on our end, OV2640 and JPEG quality of 1 seems to not work correctly in the sensor itself. Have you tried getting RGB or YUYV image? Can't go higher quality than that
Yes I have. #643 is the problem I'm having with that.
This issue appears to be stale. Please close it if its no longer valid.
ESP-IDF version: v6.2, v6.1.3 Board: ESP32S3 Xiao Sense Chip: ESP32-S3
Source code: https://pastebin.com/yyXjRYbj
When capture succeeds:
When capture fails:
I have played around with these lines to allocate more bytes to the framebuffer. It didn't help with the problem. https://github.com/espressif/esp32-camera/blob/f0bb42917cddcfba2c32c2e2fb2875b4fea11b7a/driver/cam_hal.c#L376-L379
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".