RIOT VS zephyr

RIOT would be another alternative

https://github.com/RIOT-OS/RIOT

RIOT-OS is somewhat popular in academia, it tries to be very approachable but there are still plenty of low hanging fruits with all kinds of hardware and you can use it for software and thesis projects.

Just one example: https://github.com/RIOT-OS/RIOT

You could also take a look at RIOT-OS. http://riot-os.org

RIOT-OS has a lot of unit tests for all the boards they support. And it's written in C. https://github.com/RIOT-OS/RIOT/tree/master/tests

Another option is using RIOT-OS. But that unfortunately doesn't support PWM for the Weact. It does support PWM for the Bluepill and Blackpill STM32f103 and the Nucleo-f446 After quick search. \ https://riot-os.org

If you want to use C, I would suggest trying out RIOT-OS. It's a modern embedded operating system, written in C and focussed on IOT. It works on a lot of different boards. https://github.com/RIOT-OS/RIOT

> 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...

Now maybe this is "bad code", and "good code" could exist for this problem that still meets your requirements. But... if so that's an awfully celestial definition if it's so hard to find.

As mentioned in an earlier post on building a broadcast audio source, the Zephyr RTOS contains some awesome Bluetooth LE Audio related samples. It also contains a Bluetooth LE Audio stack with great API support available to build a functioning broadcast assistant.

The Zephyr RTOS contains some great Bluetooth LE Audio related samples. One of them is the Basic Audio Profile (BAP) Broadcast Source sample.

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...

In the Zephyr repo, there is a Broadcast Audio Source sample that was used as a starting point.

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.

Auracast was announced in June 2022. Anyone else out there struggling with expectations here? I'm really hoping the product announcement season that's right around the corner had a good number of Auracast announcements.

Side note, a ton of it is over my head but it's been so so fun tuning in every once and again to see how Zephyr's Bluetooth Audio work is going. Just wild now much has gone into this! https://github.com/zephyrproject-rtos/zephyr/commits/main/subsys/bluetooth/audio

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.

We are unsure on how to proceed further with this error. We have opened a github discussion regarding the same issue.

Then there are samples. Look through it for anything useful. RC522 uses SPI, so getting that to work would be a good first step.