OV2640 and OV5640 compatibility

[ErMagnificoo]

Hardware Environment

AMB82-mini

Related technical area

Add library to the SDK for more sensors

Is the feature request related to an un-fixed issue?

Several users have expressed their interest in having these sensors supported, as seen in the following forum discussions:

• Help needed connecting OV5640 lens with AMB82-mini board
• Want to connect 5MP good quality camera with AMB82-mini
• Small size camera module options
• Realtek AMB82 display hibernation display

Currently, the SDK supports a variety of sensors, as listed in the sensor.h file, but the OV2640 and OV5640 are missing. Given that these sensors are widely used in similar development boards (such as ESP32-based camera modules), their support would greatly benefit the community.

Describe the ideal solution/reault/output.

The ideal solution would be to extend the SDK to include official support for the OV2640 and OV5640 sensors.

• These sensors have become industry-standard for embedded camera projects and are widely supported in other platforms, making them an accessible and affordable choice.
• The OV5640, in particular, is easily available on platforms like AliExpress at competitive prices due to its widespread adoption in ESP32-based boards.
• Additionally, the OV5640 is available in different form factors, including variations with longer flex cables, which makes it more versatile for applications where sensor placement flexibility is required (requested also in the forum threads).
• With this feature implemented, users of the AMB82-mini could take advantage of the board’s higher processing power and better streaming performance compared to ESP32-based alternatives, making it an even more attractive option for camera-based projects.

Additional remarks

• Many users are looking at the AMB82-mini as a superior alternative to ESP32-based camera boards like ESP-EYE or Xiao ESP32S3, thanks to its higher CPU speed and improved video streaming capabilities.
• However, the lack of OV2640/OV5640 support limits its adoption, as these sensors are not only affordable but also practical for a wide range of use cases.
• Supporting OV5640 would increase the price competitiveness of the AMB82-mini since users could take advantage of the cheaper sensor modules available on the market.
• If hardware limitations exist, having official documentation or guidance on how to write custom drivers for these sensors would be greatly appreciated.

I discovered the AMB82-mini through this YouTube video and found it to be a promising alternative, but the lack of support for these common sensors limits its potential in price and usability.

Thank you for considering this request!

I have checked existing/closed list of issues and the Contributing Guide.

• I confirm I have checked existing/closed list of issues and the Contributing Guide.

[github-actions]

Hello, hope this message finds you well. Congrats to your first Issue! We will review it as soon as possiable. Feel free to have a look at https://www.amebaiot.com/en/ameba-arduino-summary/ for more information

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[ErMagnificoo]

Three weeks have passed since I opened this issue, and the only “activity” it received has been automated replies from bots.
I understand this is an open-source project, but it’s still discouraging to see that no one from the team has responded at all — not even to acknowledge whether there's any interest or if support for the OV2640/OV5640 sensors is on the roadmap.

In the meantime, I’m trying to figure things out on my own — digging through past commits and attempting to understand how to extend the SDK and implement drivers for these camera modules myself.
I won’t be opening a separate issue about the lack of WebSocket support, because I’ve seen that other users have already raised this on the forum — and unfortunately, those posts also went unanswered.

That said, I find it disappointing that a board marketed for IoT applications — which inherently depend on connectivity, streaming, and real-time communication — lacks basic features like WebSocket support, which is a key component in many IoT scenarios.

I bought this board with high expectations, but so far I have to say the level of support and maintenance has been underwhelming.
I’ll keep experimenting on my own, but I really hope the team becomes more engaged with the community in the future.