I’m building TrackCheck, a small app that helps motocross riders quickly see which UK tracks are open for the weekend.
Tracks usually post updates on Facebook, so riders end up checking dozens of pages manually. I scrape recent posts and use an LLM to infer whether a track is open, closed, or unknown for the upcoming weekend.
In my use case (dirtbike anti theft tracker), it is useful to use an RTOS, not specifically for hard time constraints, as I don't have those, but more to have all the other functionality: task synchronisation mechanisms, driver abstraction, etc. That allows to better design the application. For example, having separate tasks for GPS updates, cellular communication, and motion detection with proper prioritization makes the code much cleaner than a giant main loop with interrupts. About other industries, I would say highly critical medical systems, avionics and automotive find it useful to use RTOSes because they have use cases where time constraints are really hard.
As ab71e5 said, "Real time" in the context of OSes, means the operating system is optimized for determinism. The OS guarantees that events will be handle in a particular time-window and that high priority task will always run first.
I’ve been working on a custom RTOS for Cortex-M for the past 10 years: https://github.com/raphui/rnk It started as a way to learn RTOS internals, and over time it has grown into something with lots of nice features. I’m even using it in a dirtbike anti-theft tracker I am building. Also, 2 months ago, I did a weekend challenge to build an embedded software parameter DSL and compiler. Its goal is to let firmware developers define configuration values, thresholds, constants, and other application-level parameters in a structured, human-readable format, and compile them into binary data that the firmware can directly use. https://github.com/raphui/epc
2 points by raphui 30 days ago | parent | context | prev | next [–] | on: Ask HN: What are you working on?
I’ve been working on a custom RTOS for Cortex-M for the past 10 years: https://github.com/raphui/rnk It started as a way to learn RTOS internals, and over time it has grown into something with lots of nice features. I’m even using it in a dirtbike anti-theft tracker I am building. Also, 2 months ago, I did a weekend challenge to build an embedded software parameter DSL and compiler. Its goal is to let firmware developers define configuration values, thresholds, constants, and other application-level parameters in a structured, human-readable format, and compile them into binary data that the firmware can directly use.
https://github.com/raphui/epc
I’ve been working on a custom RTOS for Cortex-M for the past 10 years: https://github.com/raphui/rnk It started as a way to learn RTOS internals, and over time it has grown into something with lots of nice features. I’m even using it in a dirtbike anti-theft tracker I am building.
Also, 2 months ago, I did a weekend challenge to build an embedded software parameter DSL and compiler. Its goal is to let firmware developers define configuration values, thresholds, constants, and other application-level parameters in a structured, human-readable format, and compile them into binary data that the firmware can directly use.
I’ve been working on a custom RTOS for Cortex-M for the past 10 years: https://github.com/raphui/rnk
It started as a way to learn RTOS internals, and over time it has grown into something with lots of nice features. I’m even using it in a dirtbike anti-theft tracker I am building.
Also, this month I did a weekend challenge to build an embedded software parameter DSL and compiler. Its goal is to let firmware developers define configuration values, thresholds, constants, and other application-level parameters in a structured, human-readable format, and compile them into binary data that the firmware can directly use.
It started as a way to learn RTOS internals, and over time it has grown into something with lots of nice features.
I’m even using it in a dirtbike anti-theft tracker I am building.
Also, this month I did a weekend challenge to build an embedded software parameter DSL and compiler.
Its goal is to let firmware developers define configuration values, thresholds, constants, and other application-level parameters in a structured,
human-readable format, and compile them into binary data that the firmware can directly use.
Tracks usually post updates on Facebook, so riders end up checking dozens of pages manually. I scrape recent posts and use an LLM to infer whether a track is open, closed, or unknown for the upcoming weekend.
Currently Android-only, with iOS in progress:
https://play.google.com/store/apps/details?id=com.lynxleap.t...