smoltcp VS embassy

There is also the Rust TCP/IP stack https://github.com/smoltcp-rs/smoltcp which is not mentioned as reference (and it's probably more useful to have a look there than querying ChatGPT).

Trying to dig out a link for you, will edit when I find it; TCP and Layer 4 raw sockets do not play nicely together on many platforms. You’ll probably have to send at the datalink layer and/or use something like https://github.com/smoltcp-rs/smoltcp

This seems close to what you're asking for: https://github.com/smoltcp-rs/smoltcp

A small-ish tcp/ip stack, in rust.

You can look into smoltcp

smoltcp

This here is a kernel including a memory-safe TCP/IP stack (https://github.com/smoltcp-rs/smoltcp/), and not having it crash or be full of security vulnerabilities due to preventable memory corruption is a quality beyond personal language preferences.

Oh, and you also probably want to check out smoltcp, a userspace/"no operating system required" networking stack that we often use in embedded rust.

Embassy got _some_ support for rp2350 for quite some time now

https://github.com/embassy-rs/embassy

TL;DR: No. Maybe? Depends.

It's probably reasonable to make a distinction between "Real Time" desktop/server OS (on CPUs) vs "Real Time" embedded hardware OS (on MCUs).

(Even aside from any hard-/soft- real time distinction.)

On the embedded side, in addition to FreeRTOS (upon which Pebble OS is built), I'm aware of others with reasonably high profile such as:

* Zephyr (Linux Foundation, C): https://en.wikipedia.org/wiki/Zephyr_(operating_system)

* NuttX (Apache Software Foundation, C & C++): https://en.wikipedia.org/wiki/NuttX

In addition, there's also some "up & coming" Rust language projects which fall somewhere along the "framework" to "OS" spectrum (in part, via https://arewertosyet.com):

* Tock: https://github.com/tock/tock

* Embassy: https://github.com/embassy-rs/embassy

* Hubris: https://hubris.oxide.computer

On the desktop side, I seem to recall in the past, OS such as BeOS & QNX have been presented as a possible future for real time desktop OS that hasn't arrived.

As someone else already mentioned, PREEMPT_RT being merged for Linux is a recent development somewhat in this space which could have impact on both desktop & "embedded" situations but suitability varies dependent on, say, whether you're wanting to use it for audio production versus controlling some 10 tonne robot operating next to humans.

Hope this at least goes some way to answering your question. :)

The other comment implied it but I think it's worth pointing out that:

> embedded applications that can't have asynchronous execution

Is most definitely not the case.

They can't have the same type of async runtime that would be optimal for a web server or the likes (and I'm not sure all desktop applications and web servers are going to always benefit from the same runtime in the same way), but that's a point in favour of Rust's model imho

If you're interested this is an embedded async runtime that's expected to run in no-std and no-alloc environments

https://embassy.dev/

In this article, I will guide you through creating a Snake game in embedded Rust on the BBC Micro:bit using the asynchronous framework Embassy.

Rust solved this by autogenning code from mfgr published device xml descriptors. Eg https://embassy.dev/

Better than any C(++) embedded hal I've used