RIOT VS The-Open-Book

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

Alternatively, you can also write your code in an RTOS. They often have scripts that make flashing and debugging easy. One that I personally like, and also supports Arduino, is RIOT-OS.

Have you seen the "Open Book" project?

https://github.com/joeycastillo/The-Open-Book

Open book project https://github.com/joeycastillo/The-Open-Book

If you want to get all custom, you could build an e-reader https://github.com/joeycastillo/The-Open-Book https://www.tomshardware.com/news/raspberry-pi-pico-powered-open-source-ebook-reader

>I really wish I could have an e-reader, but again, I don't want to spend money on things that will lock me into a single vendor indefinitely and might just arbitrarily go away.

https://github.com/joeycastillo/The-Open-Book

This may be up your alley.

It's not a commercial off the shelf product, but the Open Book uses a 4.2" screen. There are other devices you can find on places like AliBaba that are kinda small. However, in general you won't find a name brand commercial ereader under 6" that isn't ina phone body. There were a couple at 5" back-when but the industry really settled on 6" as the common base size.

This is very useful to see examples of how people have used APIs that are either poorly documented or not at all. Or even that are well documented, really. Going from docs to code is not always straightforward.

To give you just one example, recently I've been using it to find how people have written code to interface with e-ink displays. I usually have the datasheet which lists all the commands the protocol support, but building it all into a valid startup sequence of ~20 commands to activate the display is left as an exercise for the reader.

So the docs will look like this: https://www.waveshare.com/w/upload/6/6a/4.2inch-e-paper-spec...

And what I need is a sequence like this: https://github.com/joeycastillo/The-Open-Book/blob/5c5054c58...

There is a link to the project early in the article: https://github.com/joeycastillo/The-Open-Book