embox VS The-Open-Book

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/

Look at Embox (https://github.com/embox/embox). It can run on EFM32ZG with 32kB ROM 4kB RAM

Take a look at Embox - https://github.com/embox/embox

As for Linux, it allows easy and fast creating a device with reach features, but it requires more powerful and expensive hardware platforms, it has some questions with hard real-time, and it is less secure after all it is a general-purpose OS. We try to solve these cons of Linux in Embox. It combines prop RTOSes and Linux and allows run Linux software everywhere including MCUs

We try to solve these Linux disadvantages in our way in Embox project. The project allows run Linux software everywhere including MCUs.

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