SaaSHub helps you find the best software and product alternatives Learn more →
Zephyr Alternatives
Similar projects and alternatives to zephyr
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
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
-
zig
General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
-
-
TinyGo
Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
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.
-
-
-
-
zephyr-visionfive2
Discontinued Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
-
-
-
-
microk8s
MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge.
-
-
flex
The Fast Lexical Analyzer - scanner generator for lexing in C and C++ (by westes)
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
zephyr reviews and mentions
-
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.
-
A note from our sponsor - SaaSHub
www.saashub.com | 28 Mar 2024
Stats
zephyrproject-rtos/zephyr is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of zephyr is C.