tock VS rust-raspberrypi-OS-tutorials

Hi! This is Daniel from OxidOS Automotive (stating this for disclaimer purposes).

Yes, our OS is based on TockOS, and our CEO (Alex Radovici) is #7 in the contributors list (https://github.com/tock/tock/graphs/contributors), with other colleagues contributing in the past years.

I'm definitely not the best person to answer this, but honestly it's not bad. Here's an example of a moderately complex peripheral, the cortex-m MPU, and how one rust OS handles it:

https://github.com/tock/tock/blob/3a0527d586702b8ae8cb242391...

Reads and writes turn into volatile reads, so everything works out under the hood. You get the benefits of everything having good names, declared sizes, and proper typing on your register accesses. You can extend that to bit accesses as well.

Rust still has a few areas it isn't competitive in, like your hyper limited or obscure chips (e.g. 8051s, XAP), mature tooling around formal methods, and a certification story for safety critical code. People are working on these latter two issues (e.g. ferrocene) and supposedly very close to public delivery, but you know how slow the industry is to adopt new things even then.

There's Tock (https://www.tockos.org/), which is written in Rust (with sprinkles of assembly).

Yeah, and I like I mentioned in the earlier comment, omitting the frame pointer reduces code size by 10% on RISC-V targets, which is huge when dealing with embedded flash: https://github.com/tock/tock/pull/1660

Tock is an excellent embedded OS written in Rust and has some good industrial support. I think Tock gets a lot of stuff right and I highly recommend some of the talks the developers gave on it.

Unfortunately, it increases the code size by 10%. I was looking into this just last week, and can confirm that it's still a problem on the latest version of Rust nightly: https://github.com/tock/tock/pull/1660

I wish we could have frame pointers, because they would make working in embedded land so much easier and more reliable, but a 10% increase in code size just isn't worth it.

I am very interested in this tutorial for building an OS for the Raspberry Pi in Rust: https://github.com/rust-embedded/rust-raspberrypi-OS-tutoria...

I'd love to try it out when (if ever) I have the time.

I like rust, low level and embedded hacking so I programmed a simple "kernel", based on this: https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials

So every week, I basically followed along these tutorials. I didn't even made an effort to fully understand the code I was copying, as I just didn't want to waste mental energy on it as I wanted that energy and time wasted on my focus at the time (C++ and JS). I did that for like a year, doing 1-3 tutorials/week from that site. Over the course of it, I got to build web apps, several compilers, several games mostly board games/3d shooters/2d multiplayer games, raytracers, peer to peer apps, building a networking stack, bots, blockchain apps, servers, PGP encryption, E2E encryption apps such as for messaging, built a NES emulator, virtual machines, simulators and graphics programming, etc. I'd say the longest one was learning to build a tiny OS on raspberry pi

Hello everyone, I'm not sure if this is possible, but I'll give it a shot. I have a raspberry PI zero and a linux host pc. I am trying to run stuff on the raspberry on bare metal, no OS below it (using this tutorial https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials/). Now in the tutorial 4 there is a step "flash the kernel onto SD card and insert the SD card into the raspberry". Now, given my lack of SD card adapter (I'm also curious) I wanted to ask if it is possible to deliver this kernel onto the raspberry without the SD card using USB.