zephyr

Why ZephyrOS? ZephyrOS: https://github.com/zephyrproject-rtos/zephyr Would there be value in modeling this system with TLA+? Why build another open product? There are a few GitHub topics for solar electricity: solar: https://github.com/topics/solar photovoltaic: https://github.com/topics/photovoltaic pv: https://github.com/topics/pv battery-management: https://github.com/topics/battery-management ups-management: https://github.com/topics/ups-management inverter: https://github.com/topics/inverter Photovoltaic system: https://en.wikipedia.org/wiki/Photovoltaic_system

> I meant the goal of your function needs to be grasped within a reasonable amount of time. This works for every codebase. It really doesn't though. Here's a function of mine. It's maybe 40 lines of logic, so medium-scale. It's part of an intrusive red/black tree implementation for Zephyr. I'm fairly proud of how it turned out, and think that this code is awfully readable given its constraints. No human being is going to understand fix_extra_red() without having already read and understood the rest of the file, and coming to it with an understanding of the underlying algorithm. Certainly I can't. I can't even get started on maintaining this code that I originally wrote within a five minute time frame, it's an hour at least every time, just to remind myself how it works: https://github.com/zephyrproject-rtos/zephyr/blob/main/lib/u...

the pi pico is 100% supported in Zephyr. https://github.com/zephyrproject-rtos/zephyr/tree/main/board... Did the author not check the docs? https://docs.zephyrproject.org/latest/boards/raspberrypi/rpi... Additionally, you aren't intended (for many situations) to use a single "main" Zephyr install, but to include what external modules you need in your project's west.yml. If you have a number of projects sharing the same Zephyr install that's a separate discussion but installing every possible toolchain/HAL is not the only way to do things.

Hey folks. Anyone out there waiting for BT Auracast? It was announced June 2022, and immediately struck me as must have. I lost my earbuds, but it seems ridiculous to get a replacement without Auracast, seems like surely if I'm going to make a decent sized purchase like that it needs to support group playing. I want to tune into the radios of other people on the metro or on the bus, want to be able to watch a movie on the plane with someone. Having been announced so far back now, I've been struggling with expectations. I keep assuming this has to be happening someday soon! I'm really hoping the product announcement season that's right around the corner had a good number of Auracast announcements. Has anyone else been struggling with expectations here? Side note, a ton of it is over my head but it's been so so fun tuning in every once and

Related: https://docs.zephyrproject.org/latest/introduction/index.htm... https://github.com/zephyrproject-rtos/zephyr

Zephyr has a lot of good points, but I really wish it didn't use Kconfig. Getting a working config seems to be mostly a matter of copying an already working example. It might be okay for hardware side of things, but it's a really bad at software/feature dependency. Set https://docs.zephyrproject.org/latest/build/kconfig/tips.htm... and the issue: https://github.com/zephyrproject-rtos/zephyr/issues/52575. And don't even get me started on trying anything to group options together.

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

I'm going to sound old and very uncool but ... Use C! I'm in the process of doing my first "serious" project in 'straight' C (I'm a C++ guy from long ago) and it's taken me a while to get into it properly, but I'm starting to get its philosophy and it's becoming easy. But also, in the embedded space, it clearly has all the support you could ever want. I'm also gradually falling for Zephyr (https://www.zephyrproject.org) that has all the support for (eg) callbacks, all sorts of low level stuff. And one more ... the way you'd solve this in Zephyr is to use the scary simple API (https://docs.zephyrproject.org/latest/reference/peripherals/...). https://github.com/zephyrproject-rtos/zephyr/blob/master/sam...

Thank you for writing this so that I don't have to. :) This would probably be a good time to mention https://github.com/zephyrproject-rtos/zephyr.

So far I've been having a lot of success with Zephyr OS https://github.com/zephyrproject-rtos/zephyr It's quite easy to set up and writing drivers for it isn't really so much of a pain. I don't know if one should state it as a pain point or a good point but they do use CMake for the build system. So it's reasonably quick at least they are using a newer version of CMake than most projects I've had the joy of testing out. Their APIs are quite linux/posix inspired in my opinion but with their own zephyr flavor on top. But I would say NuttX is probably a more mature project and Zephyr has been reworked quite heavily lately so a lot has changed but at least they'll have an LTS release soon.

Hi author, nice hacking and writeup!. Nordic employee here. Note that if instead of the SoftDevice and the SDK you would've used Zephyr then you'd be able to do the same you did but with a fully open source software stack, including all layers of the BLE protocol stack. More here https://github.com/zephyrproject-rtos/zephyr