zephyr
opencv_contrib
Our great sponsors
zephyr | opencv_contrib | |
---|---|---|
57 | 19 | |
9,402 | 9,013 | |
3.4% | 1.2% | |
10.0 | 8.3 | |
3 days ago | 6 days ago | |
C | C++ | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zephyr
-
VisionFive 2 ROM addresses for Zephyr RTOS
I am working on adding support for VisionFive 2 in Zephyr RTOS. I have created a device tree by referencing the starfive linux, patches of hifive_unmatched FU740 SoC and patches of BeagleV Starlight.
-
Adding support for visionfive2 in zephyr rtos
We are unsure on how to proceed further with this error. We have opened a github discussion regarding the same issue.
-
Learning to write device drivers using C/C++ in Zephyr OS
Then there are samples. Look through it for anything useful. RC522 uses SPI, so getting that to work would be a good first step.
-
PlatformIO and Zephyr is a bad idea
In this thread u/ikravets explained that there hasn't been much demand for Zephyr, which is why they aren't doing anything with it, and in this pull request Zephyr decided to no longer recommend PlatformIO in their documentation.
-
Libraries for Zephyr (Nordic SDK 2.3)
I'd start out with another IMU example like this one: https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/sensor/lsm6dso
This is exactly the library you're looking for. You just need to create an application and instantiate it. The samples for other drivers can show you how to do that. https://github.com/zephyrproject-rtos/zephyr/tree/main/drivers/sensor/ism330dhcx
- Examples of excellently-written projects.
-
Sensor FIFO interrupt implementation in Zephyr
2) There's nothing better I guess. Just look through the samples and try to understand what they're doing. In the MAX30101 example they only enabled the sensor itself. So the configuration was already done in the .dts file. If you look into that file, you'll see how exactly it was configured. I'd urge you to go through the samples/sensor directory and look at as many overlay files as possible to see how they can be configured.
The Zephyr driver for MAX30101 does not have much functionality, it lacks sensor triggering support for example https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/sensor/max30101/max30101.c so you need to implement it yourself, maybe you could contribute to the driver itself.
-
Git archive generation meets Hyrum's law
I think that's uncharitable. Almost no one realized these things were being generated. We all assumed that links to github's "releases" were just links to files because they look like links to files! Here's one to Zephyr 3.2.0: https://github.com/zephyrproject-rtos/zephyr/archive/refs/ta...
You pull that and get a tarball that is presented to the world as an "official release". Looks like a file. Acts like a file. It's a file.
So now your package manager or reproducible build engine or whatever needs a reference to the "official source code release", and what do you point it to? That file, obviously. It's right there on the "release" page for the download. And of course you checksum it for security, because duh.
Then last week all of a sudden that file changed! Sure, it has the same contents. But the checksum that you computed in good faith based on the official release tarball doesn't match!
If there's a misunderstanding here, it's on github and not the users. They can't be providing official release tarballs if they won't guarantee consistency. "As documented", this feature was a huge footgun. That's bad.
opencv_contrib
- I was Trying to install Opencv with Cuda in my TX2 NX- but facing this issue....., also i tried to install it through Nvidia SDK but got multimedia error.
-
how to fix failed to fetch error when installing OpenCV on raspberry pi?
wget -O opencv_contrib.zip https://github.com/opencv/opencv_contrib/archive/4.1.0.zip
- TrackerCSRT source code
-
Docker multi-architecture, .NET 6.0 and OpenCVSharp
FROM debian:bullseye-slim AS build-native-env ARG TARGETPLATFORM ENV DEBIAN_FRONTEND=noninteractive # 4.5.5: released 25 Dec 2021 ENV OPENCV_VERSION=4.5.5 # 4.5.3.20211228: released 28 Dec 2021 ENV OPENCVSHARP_VERSION=4.5.3.20211228 WORKDIR / # install dependencies required for building OpenCV and OpenCvSharpExtern RUN apt-get update && apt-get -y install --no-install-recommends \ # details omitted \ libgdiplus # Get OpenCV and opencv-contrib sources using the specified release. RUN wget https://github.com/opencv/opencv/archive/${OPENCV_VERSION}.zip && \ unzip ${OPENCV_VERSION}.zip && \ rm ${OPENCV_VERSION}.zip && \ mv opencv-${OPENCV_VERSION} opencv RUN wget https://github.com/opencv/opencv_contrib/archive/${OPENCV_VERSION}.zip && \ unzip ${OPENCV_VERSION}.zip && \ rm ${OPENCV_VERSION}.zip && \ mv opencv_contrib-${OPENCV_VERSION} opencv_contrib # configure and build OpenCV optionally specifying architecture related cmake options. RUN if [ "$TARGETPLATFORM" = "linux/amd64" ]; then \ ADDITIONAL_FLAGS='' ; \ elif [ "$TARGETPLATFORM" = "linux/arm64" ]; then \ ADDITIONAL_FLAGS='-D ENABLE_NEON=ON -D CPU_BASELINE=NEON ' ; \ elif [ "$TARGETPLATFORM" = "linux/arm/v7" ]; then \ ADDITIONAL_FLAGS='-D CPU_BASELINE=NEON -D ENABLE_NEON=ON ' ; \ fi && cd opencv && mkdir build && cd build && \ cmake $ADDITIONAL_FLAGS \ # additional flags omitted for clarity \ && make -j$(nproc) \ && make install \ && ldconfig # Download OpenCvSharp to build OpenCvSharpExtern native library RUN git clone https://github.com/shimat/opencvsharp.git RUN cd opencvsharp && git fetch --all --tags --prune && git checkout ${OPENCVSHARP_VERSION} WORKDIR /opencvsharp/src RUN mkdir /opencvsharp/make \ && cd /opencvsharp/make \ && cmake -D CMAKE_INSTALL_PREFIX=/opencvsharp/make /opencvsharp/src \ && make -j$(nproc) \ && make install \ && cp /opencvsharp/make/OpenCvSharpExtern/libOpenCvSharpExtern.so /usr/lib/ \ && ldconfig # Copy the library and dependencies to /artifacts (to be used by images consuming this build) # cpld.sh will copy the library we specify (./libOpenCvSharpExtern.so) and any dependencies # to the /artifacts directory. This is useful for sharing the library with other images # consuming this build. # credits: Hemanth.HM -> https://h3manth.com/content/copying-shared-library-dependencies WORKDIR /opencvsharp/make/OpenCvSharpExtern COPY cpld.sh . RUN chmod +x cpld.sh && \ mkdir /artifacts && \ ./cpld.sh ./libOpenCvSharpExtern.so /artifacts/ RUN cp ./libOpenCvSharpExtern.so /artifacts/ # Publish the artefacts using a clean image FROM debian:bullseye-slim AS final RUN mkdir /artifacts COPY --from=build-native-env /artifacts/ /artifacts WORKDIR /artifacts
-
HOWTO: Install OpenCV in Raspberry Pi OS (Buster)
git clone https://github.com/opencv/opencv.git git clone https://github.com/opencv/opencv_contrib.git mkdir ~/opencv/build cd ~/opencv/build
-
OpenCV + Raspberry Pi: Como configurar o ambiente?
wget -O opencv_contrib.zip https://github.com/opencv/opencv_contrib/archive/4.0.0.zip
- OpenCV Kurulum Kılavuzu
-
Please help: Making SDHC work for the use of a filesystem on the NXP MIMXRT1020 EVK
My problem is pretty simple. I would like to add a C/C++ program to the NXP MIMXRT1020 EVK that classifies some traffic signs. The issue here is that for a neural network to work, I need some files containg the model and some other stuff. The need of files raises the issue of needing a filesystem which Zephyr does not support on the MIMXRT1020 EVK. So I've tought of writing my own SDHC "driver" to help me with this issue and maybe also help the community for that matter. I've tought of embedding the model in the program, but many of the functions of the library I tried to use (opencv cnn classifier and Shark) use functions that require opening files, so it was either modifying those or Zephyr.
What are some alternatives?
FreeRTOS-Kernel - FreeRTOS kernel files only, submoduled into https://github.com/FreeRTOS/FreeRTOS and various other repos.
mbed-os - Arm Mbed OS is a platform operating system designed for the internet of things
RIOT - RIOT - The friendly OS for IoT
nuttx - Apache NuttX is a mature, real-time embedded operating system (RTOS)
wasm-micro-runtime - WebAssembly Micro Runtime (WAMR)
mongoose-os - Mongoose OS - an IoT Firmware Development Framework. Supported microcontrollers: ESP32, ESP8266, CC3220, CC3200, STM32F4, STM32L4, STM32F7. Amazon AWS IoT, Microsoft Azure, Google IoT Core integrated. Code in C or JavaScript.
FreeRTOS-rust - Rust crate for FreeRTOS
littlefs - A little fail-safe filesystem designed for microcontrollers
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
OpenCV - Open Source Computer Vision Library
embox - Modular and configurable OS for embedded applications