# Running Linux on the Eight Dollar Ox64 RISC-V Computer

A technical deep dive into the complex setup process for the affordable Ox64 board.

- **Source:** [Hacker News](https://news.ycombinator.com)
- **Published:** 2026-11-07
- **Topic:** [technology](https://brifing.si/c/technology)
- **Original article:** <http://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer.html>
- **On Brifing:** https://brifing.si/s/ef38a2c5-950c-4568-8f92-eeb05d28b031

## The Ox64 Hardware Potential

The Ox64 is a unique development board priced at eight dollars that features RISC-V cores. Unlike basic microcontrollers, it possesses the capability to run a full Linux kernel. It utilizes three distinct cores, offering a significant performance leap for hobbyists looking to experiment with open-source instruction set architectures on extremely affordable hardware.

## Significant Initial Limitations

Potential users must be aware that the board is currently in an early state. Essential features like ethernet connectivity, wireless networking, and SD-card support are not functional at the time of writing. These hardware gaps mean the device is currently better suited for low-level experimentation rather than immediate, fully functional embedded computing projects.

## Complex Programming Requirements

Programming the Ox64 is not as straightforward as standard boards like the Arduino or ESP32. It requires a manual connection via UART TX/RX pins rather than a simple USB interface. This necessitates a serial bridge setup, as the device does not natively support direct USB flashing out of the box for most users.

## Software Environment Hurdles

The official flashing tool, Dev Cube, presents compatibility issues on modern Linux distributions using Wayland. Users must switch to an Xorg session or force the GDK backend to X11 to prevent the application from crashing. These software environment dependencies add layers of complexity to the initial setup process for new board owners.

## Serial Bridge Workarounds

Standard CH340G USB-to-serial dongles may fail during the handshake process with the Dev Cube software. A reliable workaround involves using an RP2040-based device, such as the Adafruit KB2040, configured as a serial bridge. By connecting specific GPIO pins and flashing the picoprobe firmware, users can successfully establish a stable communication link for flashing.

## Toolchain Modifications Required

Even with a functional serial bridge, the official Dev Cube tool may remain ineffective. Developers often need to switch to the bflb-mcu-tool and manually modify the Python source code. Specifically, stripping DTR and RTS signal handling from the interface script is necessary to ensure the flashing process completes without errors on the hardware.

## Successful Initial Communication

After configuring the bridge and modifying the toolchain, users can flash the low_load_bl808_m0.bin firmware. Successful execution results in serial output confirming dynamic memory initialization and PSRAM clock setup. This milestone confirms that the Ox64 is responsive and ready for subsequent stages of OS deployment, despite the arduous path to reach this point.

## Future Development Outlook

Achieving a bootable Linux environment on the Ox64 requires further steps, including flashing the D0 core and the operating system itself. While the current process is non-trivial and requires significant technical troubleshooting, the board represents a shift toward accessible RISC-V hardware. Future updates will determine the long-term viability of this platform.

## Sources covering this story

- http://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer.html — 

---

_Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._