Replies: 3 comments 1 reply
-
|
Turns out I don't have an OV5640, not sure what's up, but it's not this. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
You would have to have an OV3660 (OV3660_PID = 0x3660) camera, but the support for it is deactivated. AI-on-the-edge-device/code/sdkconfig.defaults Line 161 in 73afc07 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have the same board, here is my serial stream FWIW (No, mine is also not working, doesn't give me an image): |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The Problem
The ESP32-CAM device with an OV5640 camera fails to initialize with the official v16.0.0 firmware release, even though the release notes state that the camera is supported. The logs indicate a PID mismatch, where the firmware detects the OV5640 but then expects an OV3660.
This appears to be a bug in the pre-compiled firmware bundle for this hardware and camera combination. There is no user-configurable option in the config.ini file to manually set the camera model.
Hardware and Firmware
Device: Inland ESP32-CAM (Micro Center product 632692)
Camera: OV5640
Firmware Version: v16.0.0
PSRAM: Found 8MB PSRAM
Steps to Reproduce
Flash the v16.0.0 release firmware onto the Inland ESP32-CAM.
Power on the device.
Monitor the serial port log for startup messages.
Actual Behavior
The camera initialization fails. The device continuously attempts to initialize the camera before reverting to a reduced web interface. The following error messages are observed in the serial log:
I (2658) ov5640: Mismatch PID=0x3660
E (2658) camera: Detected camera not supported.
E (2658) camera: Camera probe failed with error 0x106(UNKNOWN ERROR)
Workaround
The issue does not appear in more recent nightly builds from the GitHub Actions page. Flashing a successful nightly build resolves the problem. This suggests a bug was present in the v16.0.0 official release firmware that was later patched in subsequent commits.
Version
16.0.0
Logfile
Expected Behavior
The camera should be detected and initialized successfully, allowing the device to begin the main workflow.
Screenshots
No response
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions