opencv / opencv/opencv

Zephyr/RTOS port

Open
#27,751 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
C++
Stars
90.9k
Forks
57k
Avg merge
2d 15h
Merged PRs (30d)
112

Description

Describe the feature and motivation

OpenCV could work well on MCUs.

Vector acceleration, 400MHz~1000MHz CPUs, MIPI/CSI, USB webcam (host/device) support, H.264 compression harware... This closes the gap with imaging DSPs and MPU.

With all the robotics/edge/IoT development, this would bring the imaging tools embedded device need.

Challenge: sometimes very few RAM. The solution picked by libmpix is to process the data line-by-line.

-> Is the OpenCV team interested in receiving patches to make it work on MCUs upstream?
Portability changes, alternative APIs (streaming lines), support memory-constrained systems...

Thanks!

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by reviewing the linked Zephyr, libmpix, and forum discussions to determine whether the project has an agreed MCU-porting scope; done would require a defined set of portability or memory-constrained API changes and validation on a supported MCU target.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-vision, embedded-iot
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.