PApantalaimon·Jul 5, 2024
RIOT would be another alternative
https://github.com/RIOT-OS/RIOT
In Moving to a RTOS on the RP2040RIOT-OS
RIOT
C2015–2024
RIOT-OS / RIOT
RIOT
RIOT - The friendly OS for IoT
8Distinct people
20Mentions
0Explicit recommenders
5.8KGitHub stars
What to know before exploring
What it is
RIOT - The friendly OS for IoT
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year20 dated mentions
Observed mentions: 2015-08-26 13:55:40 UTC to 2024-07-05 13:02:10 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 10 | 2 | 8 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
20 sourcesSounds a lot like what RIOT is doing, but there support for 64 bit `native` was just merged recently, so you can also build for the virtual `native64` board and run your code as a 64 bit Linux executable.
(Support for macOS was removed a few years ago due to a lack of maintenance and no active developers with access to a macOS machine)
It also comes with a mesh simulator: https://github.com/RIOT-OS/RIOT/tree/master/dist/tools/zep_d...
In Future of 32-bit platform support in FreeBSD> With hindsight, we've never really tried to use that flexibility in the real world, but the capability is there if we need it.
Maybe not in public networks, but if you run your own network you can easily make use of auto-subnetting.
e.g. see [0], [1]
[0] https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_ne...
[1] https://summit.riot-os.org/2021/wp-content/uploads/sites/16/...
In Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]Riot-OS 2021.10 released with initial support for GD32VF103, RP2040
3 points · Open discussionActually you can do that with RIOT-OS (and probably Zephyr too) if you attach an SPI radio or Ethernet module.
https://github.com/RIOT-OS/RIOT/tree/master/examples/suit_up...
In Updating STM32 Over-The-Air using ESP32The clones even tend to have more memory.
But I was thinking of those boards: https://aliexpress.com/item/4000103610226.html
(also supported by RIOT btw https://github.com/RIOT-OS/RIOT/pull/12778)
In Riot OS – Real-Time, MMU optional and threadsYou can use lwip instead of the default GNRC stack for IPv4.
But there is also a PR for IPv4 in GNRC: https://github.com/RIOT-OS/RIOT/pull/12988
In Riot OS – Real-Time, MMU optional and threadsI would read the extensive list of features and look at the code first before hurling content-free FUD. It even supports Arduino too.
https://github.com/RIOT-OS/RIOT/tree/master/cpu
In Riot OS – Real-Time, MMU optional and threadsLooks like it can save a good chunk of memory compared to newlib: https://github.com/RIOT-OS/RIOT/pull/12305
In Picolibc – Libc for Embedded SystemsHow's your experience with writing device drivers for NuttX? Is it easy to attach manufacture's device libraries? The biggest reason that I stick to FreeRTOS is the fear of writing device drivers from scratch for a big RTOS like NuttX.
I did some contributions to RIOT-OS [1]. Honestly it was nightmare to me because they have strict policies not allowing manufacturer drivers so I should write peripheral registers directly, which leads to a lot of bugs that is hard to debug.
[1]: https://github.com/RIOT-OS/RIOT
In NuttX – A POSIX-compliant RTOS for embedded platformsProbably it's still possible to use ipv4 with this OS, but not with "gnrc" framework.
- IPv4 is mentioned in docs: http://doc.riot-os.org/group__net__ipv4.html
- lwip config has ipv4 enabled: https://github.com/RIOT-OS/RIOT/blob/3091cd85bd6df0bce1fcf60...
In RIOT: Operating System for the Internet of Things> Yes, I think they are. Nordic 832’s SPI has an 8bit for remaining count in its hardware register meaning a transfer has a max of 255chars. Atmel’s SPI is all event based. STM32 F3 SPI has an entirely different setup procedure than those two and that has a difference I can’t remeber the F0 and F7 are different.
How does this prevent you from hiding all those implementation details behind an API like spi_transfer(spi_t dev, const void* buffer_tx, void* buffer_rx, size_t size)?
RIOT manages to get by with that - granted, most implementations there rely on polling, it's not a conceptual problem.
https://github.com/RIOT-OS/RIOT/blob/master/cpu/stm32_common...
https://github.com/RIOT-OS/RIOT/blob/master/cpu/atmega_commo...
https://github.com/RIOT-OS/RIOT/blob/master/cpu/nrf5x_common...
In RIOT: Operating System for the Internet of ThingsNo IPv4 support?
https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_ne...
In RIOT: Operating System for the Internet of ThingsShowing the 15 most recent of 20 sources. Enable JavaScript to search and browse every indexed mention.