21–30 of 47 posts
Hi HN, I’ve been working on a tiny RTOS as a personal project to better understand how operating systems and schedulers work internally. This project includes: - Basic task scheduler - Context switching - Simple memory management - Runs on (your target hardware or environment) Motivation: I wanted to learn OS internals by building everything from scratch rather than relying on existing frameworks. Challenges: - Imple…
Others (well, two people really) have also noted the lack of a linker script, start-up code, and that the project doesn't even build.
82 points at the time of writing, which is 4 hours from the post's submission. Already on the main page. The only previous activity of the author? Two other vibe-coded projects of similar quality and a few comments with broken list formatting, suggesting that they were never even reviewed by a human prior to posting.
Does anybody read past the headline these days? Had my hopes higher for this site.
[0] https://github.com/cmc-labo/tinyos-rtos/blob/2a47496047fdb45...
[1] https://github.com/cmc-labo/tinyos-rtos/blob/2a47496047fdb45...
[2] https://github.com/cmc-labo/tinyos-rtos/blob/2a47496047fdb45...
Hi HN, I’ve been working on a tiny RTOS as a personal project to better understand how operating systems and schedulers work internally. This project includes: - Basic task scheduler - Context switching - Simple memory management - Runs on (your target hardware or environment) Motivation: I wanted to learn OS internals by building everything from scratch rather than relying on existing frameworks. Challenges: - Imple…
Nice try, OpenClaw
I have no practical insight on RTOS in general, if anyone bothers to give me a hint, please. From all what I've looked into, RTOS does mean to create software systems that are almost perfectly predictable and safe to execute. Predictable latency, runtime and memory usage, plus maybe side channels to do the unpredictable stuff in between. It's actual rocket science, as no systemic mistakes are allowed. The confusion i…
You're probably thinking of a hard real-time RTOS with time slices and WCET constraints. For soft real-time, you basically only need low latency. Threads with priorities, synchronization primitives and some way of handling interrupts is generally considered good enough. From the description, this sounds like the kind of RTOS that runs most embedded RT applications currently if perhaps a bit heavier in features than t…
Why would someone make a context switch HIGH latency? That defeats the purpose.
Earlier quoted context omitted.
You're probably thinking of a hard real-time RTOS with time slices and WCET constraints. For soft real-time, you basically only need low latency. Threads with priorities, synchronization primitives and some way of handling interrupts is generally considered good enough. From the description, this sounds like the kind of RTOS that runs most embedded RT applications currently if perhaps a bit heavier in features than t…
Can someone explain this whole boondoggle with RTOS and latency means in practice? Why would someone make a context switch HIGH latency? That defeats the purpose.
How much of this was by AI?
It doesn't even compile, the whole thing is evidently built on vibes.
The README mentions ARMv7-M, RISC-V, and AVR, but no actual SoCs or boards, and the source code contains unconditional inline assembly for Arm. Similarly, there are measurements of context switch time on RISC-V, while the scheduler is one big stub that doesn't even enter a task, only returns from itself using Arm-specific assembly [0]. The examples rely on this scheduler never returning, so there's no way any of them…
The README mentions ARMv7-M, RISC-V, and AVR, but no actual SoCs or boards, and the source code contains unconditional inline assembly for Arm. Similarly, there are measurements of context switch time on RISC-V, while the scheduler is one big stub that doesn't even enter a task, only returns from itself using Arm-specific assembly [0]. The examples rely on this scheduler never returning, so there's no way any of them…