TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
A December 2022 blog post documented an attempt to bring up Linux on the $8 Ox64, a RISC-V board built around the BL808 chip. The author got a firmware loader to run and received serial output, but the post did not confirm a working Linux system; it also listed Ethernet, Wi-Fi and SD-card support as unavailable at the time.
A December 2022 hands-on report about the $8 Ox64 RISC-V computer documented a first step toward running Linux: its author flashed firmware and received startup messages over a serial connection. The post did not show Linux booting, and warned that Ethernet, Wi-Fi and SD-card support were not working at the time, making the low-cost board an experimental project rather than a ready-to-use Linux computer.
The Ox64 is based on Bouffalo Lab’s BL808 chip, which the report describes as having three different RISC-V cores. The author presented the board as capable of running Linux, including a system using a memory-management unit, rather than merely a stripped-down kernel for a microcontroller. Those are descriptions of the hardware and its potential; the post’s demonstrated result was more limited.
Getting firmware onto the board required a UART serial connection, not the USB programming approach familiar from some other hobbyist boards. The author reported that Bouffalo Lab’s Dev Cube flashing application crashed in an Ubuntu Wayland session. A USB-to-serial adapter also failed to complete its handshake, so the author used an Adafruit KB2040, an RP2040-based board, as a serial bridge to the Ox64.
Even with that connection, Dev Cube did not work for the author. They switched to the bflb-mcu-tool and said they had to edit its UART interface code, removing DTR and RTS handling. After flashing a low-load BL808 M0 binary, the board returned messages including “dynamic memory init success” and “E907 start.” The post described this as evidence that the Ox64 was communicating with the computer—not as proof that Linux had started.
A Low-Cost Board, Not a Finished PC
The report captures both the appeal and the practical limits of an inexpensive RISC-V development board. At $8, the Ox64 offered hobbyists a low-cost way to experiment with a multi-core RISC-V chip and Linux bring-up. But the price alone did not make it a plug-and-play computer: programming required serial wiring, compatible tools and troubleshooting at the software level.
That distinction matters to buyers comparing small Linux-capable boards. The report’s successful serial output was a limited milestone, while missing network and storage support could constrain what users could do even if they reached a Linux prompt. Readers should treat the post as a record of one person’s setup in December 2022, not as a current compatibility guide or a guarantee that every board will behave the same way.
Popular right now
Ninja Espresso and Coffee Maker with Built-In Frother, CFN601
Bose QuietComfort Wireless Noise Cancelling Headphones, Twilight Blue
Roborock Q7 M5+ Robot Vacuum and Mop with Self-Emptying Dock
As an affiliate, we earn on qualifying purchases.
The Steps Before a Linux Boot
The report’s central subject was not a completed Linux installation but the process of getting the Ox64 to accept firmware. The author described several separate obstacles: Dev Cube’s crash under their Ubuntu Wayland setup, a failed handshake with a CH340G adapter, and a need to use an RP2040 board as the serial bridge. The author also said the alternative flashing tool needed a local code change.
After flashing the M0 low-load binary, the author wrote that further work remained: flashing something to the D0 core and then installing or flashing the operating system. The post ended by directing readers to a planned follow-up, identified as Part 2. The source material supplied here does not include that follow-up’s results, so it cannot establish whether the author later booted Linux.
““Caveat Emptor!””
— The Ox64 report’s author
Linux Boot Remained Unconfirmed
The supplied report does not show a successful Linux boot, identify a completed operating-system installation, or provide benchmark results. It says the author still needed to flash the D0 core and the operating system after the initial M0 firmware step. The author’s expectation that these steps could lead to Linux is not evidence that they were completed.
The report also does not establish whether the listed Ethernet, Wi-Fi and SD-card limitations were later resolved, whether the same flashing problems affected other users, or whether the later Part 2 changed the outcome. Its findings are specific to the author’s hardware, operating-system environment and tools in December 2022.
The Follow-Up Was the Next Test
The author pointed readers to a planned Part 2 for further progress. Based on the first post, the next reported milestones would be flashing the D0 core, loading the operating system and checking whether the board could boot into Linux. The supplied source material does not include those results, so the status beyond the serial-output demonstration remains unverified here.
For readers evaluating the board, the practical next step is to consult later documentation or reports for the exact hardware revision, supported firmware and current tool instructions. The 2022 account remains useful as a record of the initial setup hurdles, but it should not be read as confirmation of present-day software support.
Key Questions
Did the report show Linux running on the Ox64?
No. It showed the board returning serial startup messages after firmware was flashed. The author said additional steps, including flashing the D0 core and the operating system, remained.
What is the Ox64?
In the report, the Ox64 is an $8 RISC-V board based on the BL808 chip, which the author described as having three different RISC-V cores. The post discussed its potential for Linux, not a completed, ready-to-use computer.
What did the author use to connect to the board?
The author used an Adafruit KB2040, an RP2040-based board, as a serial bridge between the computer and Ox64 after a CH340G adapter failed to handshake. The post describes connections through UART TX/RX pins.
Which features were reported as unavailable?
The author said Ethernet, Wi-Fi and SD-card support were not working at the time of writing. The supplied material does not confirm whether those limitations were later resolved.
Was the flashing process straightforward?
No. The author reported a crash with Dev Cube under Ubuntu Wayland, a failed adapter handshake and a need to modify the bflb-mcu-tool UART code. These are the author’s experiences in that setup, not proof that every user will encounter the same issues.
