-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
espcamera ESPIDF Generic Failure and Memory Error on ESP32S2 #8942
Comments
I am trying to make a build for the feather esp32s2 with imagecapture instead of esp32camera, but it is not building. It appears the imagecapture has been removed from the common-hal for espressif builds ...
|
That code has been removed. Scott removed part of it in 3b15931 while I removed the rest in efed3c9. So you could travel back in time to efed3c9 with git to have that module possible to build, maybe -- it hadn't been used in a long time (not since the idf5 update), so I don't even know whether it would build before the related files were removed. |
I think the real question is whether there is a bug causing the problems with espcamera on the esp32s2 or if esp32s2 simply can’t handle espcamera. If that is the case, do we just document that and move on or is it worth trying to revert to something lime imagecapture. There does not appear to have been a great demand for it so I expect there are more important issues to resolve at this time. |
I don't think it would work before I removed it. It was relying on other stuff I also removed. |
I'm not super interested in getting things going on the S2 if we don't have a project that uses it. The S3 is much better. |
I have used the espcamera on an esp32-s2 without problems a while back, so I'm confident it's possible: https://hackaday.io/project/182342-camera-shield-for-s2-mini |
That is fine with me. I have migrated my camera projects to esp32s3 boards and I am happy to put the "kaluga" back on the shelf. |
Have you tried this with espcamera and CP9? I'm just curious if you will have the same issues with memory. |
Sorry for the delay, I didn't see your comment. I just tried with 9.1.0-beta on a Lolin S2 Mini, with this code: import busio
import espcamera
import board
i2c = busio.I2C(scl=board.IO35, sda=board.IO33)
data_pins = (
board.IO21, board.IO17, board.IO16, board.IO18,
board.IO37, board.IO34, board.IO36, board.IO39,
)
c = espcamera.Camera(
data_pins=data_pins,
external_clock_pin=board.IO11,
pixel_clock_pin=board.IO12,
vsync_pin=board.IO40,
href_pin=board.IO38,
pixel_format=espcamera.PixelFormat.RGB565,
frame_size=espcamera.FrameSize.QVGA,
i2c=i2c,
)
c.take() and I'm getting |
CircuitPython version
Code/REPL
Behavior
Description
This is being run on a feather esp32s2 with an OV5460 breakout.
See the additional example below that fails with a Memory error when adafruit_requests is also used.
I suspect these failures are both due to memory issues on the esp32s2 so I am reporting both here.
Additional information
switching to PixelFormat = JPEG runs normally
Both examples run as espected on an esp32s3 (memento or metro_esp32s3)
I suspect this is a memory issue and not really related to the Pixel Format.
If I extend the working code (JPEG format) to try to use the requests library to access AIO, then it fails with a Memory Error.
code:
fails:
line 65 is:
These may be unrelated issues, let me know if you would prefer them to be separated.
It may be of little general interest since the ESP32S3 support works well and it is not trivial to attach a camera to any esp32s2 board other than the Kaluga (The same issues are present on the Kaluga)
I wanted to report the issue others are aware of potential limitations of using espcamera with esp32s2 boards.
If this is just a "fact of life" for the esp32s2, perhaps it should be noted in the espcamera docs.
I have not tried using the adafruit_OV5640 library instead of espcamera. I will try that.
The text was updated successfully, but these errors were encountered: