3 ms·
Lilos: A wee async RTOS for Cortex-M
- retrac 3y agoThe comments in the code are wonderful documentation. I like the applicative mutex, I may borrow the idea! https://github.com/cbiffle/lilos/blob/main/os/src/mutex.rs https://github.com/cbiffle/lilos/blob/main/os/src/mutex.rs
- dbcurtis 3y agoAwesome. When I saw it was from Cliff Biffle I got really excited. This is why I visit HN.
- sitkack 3y agoI can see why http://cliffle.com/blog/bare-metal-wasm/ http://cliffle.com/blog/bare-metal-wasm/ https://github.com/cbiffle https://github.com/cbiffle
- lulf 3y agoAsync Rust is great for embedded! Check out https://embassy.dev https://embassy.dev as well which is very similar but with support for more hardware.
- sitkack 3y agoSuper cool. A friend of mine built an event based task runner on the PIC18, but this looks even neater.
- Matthias247 3y agoIt looks pretty cool. And is actually something I tried while I was working on futures-intrusive (before I lost most interest in async Rust). But besides being possible, I'm wondering if its a *realtime* OS in the sense that the term suggests. A realtime OS requires guarantees that tasks run in certain intervals - which seems to require preemption, and thereby "real" stacks. When using a cooperative multi-tasking system it seems any task could prevent all others from running - which voids the realtime guarantees.
- bfrog 3y agoThat’s not true, higher priority interrupts could drive higher priority tasks still. That’s the premise of RTIC which also supports futures.