MiROS VS OOP-in-C

Have you checked this one? https://www.state-machine.com/quickstart

You can check out the YouTube videos [about building your own minimal RTOS](https://www.youtube.com/playlist?list=PLPW8O6W-1chyrd_Msnn4LD6LBs2slJITs). This minimal RTOS (called MiROS) is used as a teaching aid. The project is also available on GitHub.

I've checked out C implementations like os h and (MirOS)[https://github.com/QuantumLeaps/MiROS] but when I port them to rust (even with C2Rust) they cause hard faults too.

To see "A Tiny RTOS Simply Explained" you might want to watch the RTOS video playlist on YouTube. The videos teach about the RTOS by building a "Minimal Real-Time Operating System" (MiROS) for ARM Cortex-M, which is available on GitHub.

For example, in the segment about the RTOS, you witness building a "Minimal Real-time Operating System "MiROS". The MiROS code is available on GitHub, and you can keep adding to it other features. Building a functional RTOS is a great way to learn about RTOSes.

You will build there a small "Minimal Real-time Operating System (MiROS)" for ARM Cortex-M. You will start with performing context switching manually, and then you will automate the process in assembly. Then you will build schedulers, first time-slicing round-robin and then preemptive, priority-based. You will learn about real-time and Rate Monotonic Scheduling. You will see how all this works using a logic analyzer. The RTOS code, and the examples are available on GitHub.

There is also a small OOP-in-C project (Object-Oriented Programming in C) introduced in the segment about Object-Oriented Programming. This project is also available on GitHub in the OOP-in-C repository.

> "... my coding in C++ still feels like doing C with classes and some STL containers like 2005. I want to progress from this state. ..."

What's wrong with these?:

- C++: The Core Language by Gregory Satir and Doug Brown

- https://github.com/QuantumLeaps/OOP-in-C

- C++ Concurrency in Action

- C++ Templates the Complete Guide 2e

The first is particularly geared towards C programmers, and I prefer the second one to "Inside the C++ Object Model". (There's also another popular book by a German author who covers OOP in C.)

For the time being, I will be an "opportunist" who is waiting for the right time to switch to another language[1] - Rust:

"To me using C++ means you are ready to give up a lot of time and energy in order to gain a complete control over certain aspects of your program. I was very much into that at the start of my career and gradually started drifting away to more immediate productivity while reserving the right to poke under the hood when necessary. This has led me to Rust and I find it to be the better natively compiled strongly & statically typed language, but YMMV of course."

(No, the concepts I learn in C++11 and beyond won't go into waste even when C++ becomes less and less relevant in a couple of decades.)

[1] https://news.ycombinator.com/item?id=24805717