zephyr
embox
Our great sponsors
zephyr | embox | |
---|---|---|
57 | 34 | |
9,402 | 1,083 | |
3.4% | 2.9% | |
10.0 | 9.9 | |
3 days ago | 7 days ago | |
C | C | |
Apache License 2.0 | BSD 2-clause "Simplified" License |
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.
embox
-
Release v0.5.9.10 ยท embox/embox
Embox is a configurable RTOS designed for resource constrained and embedded systems. Embox main idea is using Linux software without Linux. (https://embox.github.io/ ) If you want use complex Linux Software and Linux is huge for your goals. Embox is the best idea, as I think. For example Embox is the only RTOS that allows to use OpenCV on Cortex-m MCUs https://www.embedded.com/benchmarking-opencv-on-stm32-mcus/
-
Query: Alternatives to Zephyr?
Look at Embox (https://github.com/embox/embox). It can run on EFM32ZG with 32kB ROM 4kB RAM
-
Can you share some open source projects we can contribute to?
Take a look at Embox - https://github.com/embox/embox
-
Open source projects
Embox (https://github.com/embox/embox) open-source RTOS for embedded systems. It was born as a student project and a lot of students took part in it.
-
Embedded software testing
In Embox (https://github.com/embox/embox ) we use several testing levels to check different parts including hardware. We designed unit test framework on C and can use it to check hardware (https://github.com/embox/embox/blob/master/src/tests/spi/imx6_spi.c). We also try to develop peripheral independent code. We created libraries and use files for access to peripherals that allows using a command-line interface to test hardware. And finally, we have a regression testing framework. It bases on 'telnet' and 'expect' (https://github.com/embox/embox/tree/master/scripts/autotest). I'm sure that UART can be used instead of telnet
-
which modbus c library do you use?
Embox (https://github.com/embox/embox) is a configurable open-source RTOS. Its main idea is to use Linux software everywhere including MCU or develop software in a convenient environment. In other words, you can use wished Linux software without "heavy" Linux kernel therefore you need small resources. In the article, libmodbus is used on STM32F4-discovery. Embox allows using of such complex Linux software as OpenCV on STM32 (https://www.embedded.com/benchmarking-opencv-on-stm32-mcus/ ) or Qt (https://youtu.be/9rA\_sHrQjjE)
-
Choosing an RTOS
Yes, it is a very fast development speed especially if you need rather complex functionality. As for other questions, the project is more than 10 years and more than 100 contributors (https://github.com/embox/embox/graphs/contributors ). I think it will actively develop.
You should look at Embox (https://github.com/embox/embox). Its main idea is to use Linux software everywhere including MCU. It looks like an embedded Linux distributive where you can choose necessary modules, but unlike Linux Embox's kernel, standard C library, TCP/IP stack and so on also configure while compilation. It allows on the one hand run on EFM32 with 32kB flash 4 kB RAM (https://anton-bondarev.medium.com/embox-on-efm32zg-stk3200-board-how-to-run-rtos-on-mcu-with-4kb-ram-26a82dc7b9d9) and on the other hand you can use TONs Linux software for example OpenCV (https://youtu.be/7QjfgEPCLiw )
-
What are some good USB libraries for STM32?
Take a look at Embox (https://github.com/embox/embox/wiki/USB-gadget-on-STM32 )
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
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
littlefs - A little fail-safe filesystem designed for microcontrollers
stm32-bootloader - Customizable Bootloader for STM32 microcontrollers. This example demonstrates how to perform in-application-programming of a firmware located on an external SD card with FAT32 file system.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
opencv_contrib - Repository for OpenCV's extra modules