Rcore - Documentation

Just keep QEMU, GDB, and the RISCV manual close by. Have you worked through rcore? What documentation gaps or wins did you find? Let me know in the comments or on Mastodon.

The rcore documentation is not a polished, textbook-grade resource. It’s a living, sometimes messy, guide written by researchers and camp mentors who assume you’ll ask questions and read source code. If you want to understand OS dev in Rust, not just follow instructions, rcore is one of the best hands-on paths available. rcore documentation

If you’ve spent any time in systems programming, embedded development, or operating system tinkering, you’ve likely heard the name rcore whispered in enthusiast forums or GitHub repos. But what exactly is rcore, and more importantly, how do you actually use its documentation without getting lost? Just keep QEMU, GDB, and the RISCV manual close by

Let’s break it down. First, a quick definition. rcore (often styled as rCore ) is an educational operating system written in Rust. It’s designed to teach OS development from scratch—think xv6 but with Rust’s memory safety and modern tooling. The project includes multiple stages (rCore Tutorial, rCore Camp, rCore for RISCV), and its documentation is the primary gateway for anyone wanting to build their own kernel. Let me know in the comments or on Mastodon

extern "C" { fn __alltraps(); } unsafe { stvec::write(__alltraps as usize, TrapMode::Direct); }

That kind of detail lives in the community chat or old GitHub issues, not the official docs. Yes—but bring your own patience.