GitHub

A RISC-V system-on-a-chip and an operating system, designed as one machine.

Zeitlos is a work-in-progress SOC and OS built in tandem, giving FPGA computers a responsive graphical environment for running and writing timeless applications.

rv32im @ 48 MHz 640 × 480 × 1bpp pre-emptive multitasking hardware graphics acceleration work in progress

The desktop as it boots — 640 × 480, one bit per pixel. The hardware renders that single bit as white, amber, green or paper, and the switch at the top of this page follows the same four.

The project

A whole computer, small enough to read

zeitlos — German, adj. — timeless

Most computers are a stack of things nobody has read end to end: a CPU you cannot see inside, firmware you cannot change, an OS too large to hold in your head. Zeitlos is an attempt at the opposite — a system where the gateware and the operating system live in one repository and are designed together. When the OS needs something the hardware can grow it, and when the hardware offers something the OS can use it immediately.

It runs on Machdyne FPGA computers and other FPGA development boards. Every release ships a prebuilt image per supported board: write one to flash and the board comes up in a graphical desktop with a dock, movable windows and a terminal. Nothing to build, and an sdcard is optional.

The core applications turn the system into an extensible multi-window network terminal with scripting and graphics.

Goals

What we aim for

  • Timeless applications Software written against a small, stable system. The target is useful timeless applications that still build and still run decades from now.
  • Hardware and software as one design The SOC and OS are designed and developed together, so each is built to what the other actually needs. The OS gets exactly the hardware it needs and the SOC remains as simple as possible.
  • Complete on its own Flash a board once and it boots to a desktop. Storage and networking are optional.
  • Legible from the gate up Verilog for the machine, C for the system, Scheme for scripting it — each layer small enough to follow. The documentation is being written as a book, Timeless Computing, to be shipped with the system.
  • Open, and open to work on Open-source, developed in the open, and buildable with an open toolchain on ordinary hardware.
  • Responsive Responds quickly and predictably to what you want to do.

Hardware

The SOC

Written in Verilog, targeting ECP5, Artix-7 and GateMate FPGAs.

System-on-chip
CPU32-bit RISC-V (PicoRV32 or Zeitlos32) at 48 MHz, rv32im with hardware multiply and divide
GPULine rasterizer and blitter
MTUVirtual addressing through a Memory Translation Unit
MPUMemory protection unit with crash reporting
CacheOptional instruction cache, or a unified instruction and data cache with write buffer
Bus32-bit Wishbone
MemorySDRAM, DDR3, PSRAM or SRAM, 1 MB minimum
Framebuffer640×480, 1 bit per pixel — monochrome in white, amber, green or paper
VideoVGA, DVI, DVI over HDMI, composite NTSC and PAL
Audio8 channel 16-bit hardware mixer with stereo output
StorageMicroSD
NetworkEthernet over SPI or USB, an Ethernet MAC for RMII PHYs, or an ESP32 link
CryptoRing-oscillator TRNG, with optional SHA-256, Keccak and Montgomery multiplier blocks behind TLS and SSH
USBDual-port host controller — keyboard, mouse, gamepad, storage and serial — plus a USB serial console
I/OGPIO on PMOD ports with I2C and SPI, hardware SPI, 16550 UART

System

The OS

Written in C, with a Scheme interpreter for scripting.

  • Pre-emptive multitasking
  • Flat memory model, with a virtual address space for each application
  • Core applications stored in flash, so a flashed board boots to a desktop with no sdcard
  • Object-based interprocess messaging, streaming and ports
  • FAT filesystem on MicroSD, with long filenames
  • TCP/IP networking with TLS 1.3 and SSH, and servers to match
  • UTF-8 throughout, with 22 keyboard layouts
  • Speech and system-wide captions, for blind and headless use

Memory translation

Zeitlos has no MMU. Instead there is a single virtual address space that is remapped during context switches. The kernel sits at the start of main memory and applications are loaded immediately after it — but every application executes at the same fixed address, 0x8000_0000, which mirrors wherever it actually lives.

The translation base register is set on each context switch, so an application only ever sees its own memory through one address. No need for position-independent code or relocation.

Main memory — physical

Kernel0x4000_0000running
App 1running
App 2running
App 3running

Executing at

Kernel0x4000_0000

The kernel is scheduled as task 0 alongside the applications. Only addresses in the 0x8 region are translated, so each application is mirrored to 0x8000_0000 while the kernel runs untranslated where it sits.

Software

Core applications

Written to flash alongside the kernel and started at boot.

Shipped in flash
kernelKernel and kernel shell (serial console)
wmWindow manager and dock, with ten workspaces
netNetworking service
termTerminal emulator (VT100, UTF-8) that connects to shells and services
consoleConsole service
cronRuns programs on a schedule

Anything on an sdcard shadows the copy in flash, so a single application can be replaced during development without reflashing the rest.

The card carries the rest: the shells — a Lisp interpreter and a POSIX layer — alongside an editor, a spreadsheet, a web browser, a file browser, image and document viewers, network servers, games, and a C compiler and FPGA toolchain that run on the machine itself. The repository has the full list.

Contributing

Get involved

Zeitlos is early and moving quickly — the SOC, the kernel, the window manager and the applications are all still being shaped, and there is plenty left to do. Development happens entirely on GitHub.

Porting to a new board, filling in the drivers, writing applications, and especially testing the system is extremely helpful. If you have an unsupported FPGA board and want to run Zeitlos on it, please open an issue.

Build instructions, the current list of supported boards and the documentation all live in the repository, where they stay up to date with the code.