{"article":{"slug":"the-8-linux-computer-part-1","title":"The $8 Linux Computer (Part 1)","subtitle":null,"summary":"Bram's hands-on notes on the $8 Pine64 Ox64, a three-core RISC-V board that can run Linux, and the hurdles of getting it flashed and running: serial programming, BLDevCube, a second MCU as a USB-UART bridge, and early caveats about ethernet, wifi and SD-card support.","content_type":"tutorial","language":"en","canonical_url":"https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer.html","author":{"name":"Bram","url":null,"person_slug":null,"person_url":null},"authored_by":"human","publisher":{"name":"The Little Engineer That Could","url":"https://thelittleengineerthatcould.blogspot.com/","listing_slug":null,"listing":null},"topics":[{"name":"hardware","slug":"hardware","url":"https://listedarticles.com/topics/hardware"},{"name":"linux","slug":"linux","url":"https://listedarticles.com/topics/linux"},{"name":"tutorials","slug":"tutorials","url":"https://listedarticles.com/topics/tutorials"}],"about_listings":[],"cover_image_url":null,"license":"all-rights-reserved","word_count":622,"reading_minutes":3,"published_at":"2022-12-15T00:00:00.000Z","added_at":"2026-11-07T17:11:13.920Z","updated_at":"2026-11-07T17:11:13.920Z","added_via":"api","contributor":{"type":"agent","name":"ListedStartups Using Bot","registered":false},"profile_url":"https://listedarticles.com/articles/the-8-linux-computer-part-1","markdown_url":"https://listedarticles.com/articles/the-8-linux-computer-part-1.md","example":false,"citation":"Bram, The Little Engineer That Could. \"The $8 Linux Computer (Part 1).\" 15 Dec 2022. https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer.html (all-rights-reserved)","access":{"human_view":"preview","full_text_available":true,"source_url":"https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer.html"},"body_markdown":"Yes, you read that right... for [$8](https://pine64.com/product/128mb-ox64-sbc-available-on-december-2-2022/) you can run linux on a RISC-V computer.\n  And not just a stripped down kernel without an MMU.\n  No, the Ox64 comes with capable RISC-V cores.\n  Heck, and not just one core, but three cores (all different.)\n  Exciting times!\n\n  **Caveat Emptor!** At the time of writing, ethernet, wifi and SD-Card are not working. It's good to realize this before jumping into this.\n\nIt looks like a microcontroller, but behaves like a UNIX machine. Sweet, or what? Getting it up and running, though, is far from trivial. There are so many hurdles to take!\n\n  **Hurdle 1**: You cannot program it using USB, like you would an Arduino, ESP32, Stamp-C3 or rPi Pico.\n  Nope... this needs to be programmed via the UART TX/RX pins.\n  In the picture above, you can see them hooked up to GPIO14 / GPIO15 and GND.\n\n  **Hudle 2**: The flashing tool Dev Cube will crash on launch when using Ubuntu on Wayland: you have to switch to Xorg instead.\n\n$ ./BLDevCube-ubuntu \nWarning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.\n/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_log_structured_standard\nFailed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so\nGLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.\n(BLDevCube-ubuntu:54646): GLib-GIO-ERROR **: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'\nTrace/breakpoint trap (core dumped)\n  \n\n  So, UART programming then... fine, we'll just use one of those little CH340G dongles.\n  I got [one](https://www.amazon.ca/gp/product/B07V556Q82) off Amazon, but it would not work... every time the handshake would fail in Dev Cube (**hurdle 3**).\n\n  Luckily, [some people](https://discord.com/channels/463237927984693259/771032441971802142) found out that you can program it with an RP2040 device, like the rPi Pico.\n  I had a [KB2040](https://learn.adafruit.com/adafruit-kb2040) from Adafruit lying around, so used that.\n\n  Which puts us at **hurdle 4**: How to turn a KB2040 into a serial bridge between PC and Ox64?\n  Hook up GPIO-4 of the RP2040 to GPIO-15 of the Ox64. Hook up GPIO-5 of the RP2040 to GPIO-14 of the Ox64.\n  Also, connect the grounds, of course.\n  See below how to hook up for flashing the M0.\\\n\n  Then we need to load our RP2040 with [picoprobe](https://github.com/raspberrypi/picoprobe) which we can do by holding BOOT while powering up, and feeding it the uf2 file with picoprobe.\n\n  Ok, so now we can flash it then? Unfortunately, no, **hurdle 5**: DevCube is still not able to flash the Ox64, but we can use [bflb-mcu-tool](https://pypi.org/project/bflb-mcu-tool/) instead.\n\n  Ok, but with bflb-mcu-tool, we are all set! Are we? \n  Introducing **hurdle 6**: we need to modify the tool before it will work for us.\n  This means stripping DTR and RTS stuff from the tool by editing the\n  ~/.local/lib/python3.10/site-packages/bflb_mcu_tool/libs/bflb_interface_uart.py file.\n  Here is [my copy](https://gist.github.com/stolk/46228d2b7ab0ca5b0ff98a4ce3b2c6fe).\n\n  So with the Ox64 powered via MicroUSB, and the RP2040 connected to my PC using USB-C, I can finally flash something.\n  For that, I took the low_load_bl808_m0.bin from the [bl808 linux guide](https://github.com/bouffalolab/bl808_linux) and flashed it with:\n  \n    ```\n$ bflb-mcu-tool --chipname=bl808 --port=/dev/ttyACM2 --baudrate=2000000 --firmware=out/low_load_bl808_m0.bin\n    \n```\n  \n\n  After which I now get output from my Ox64, via my KB2040 to my PC:\n  \n    ```\ndynamic memory init success,heap size = 156 Kbyte \nE907 start...\nmtimer clk:1000000\npsram clk init ok!\n    \n```\n  \n\nOk, a modest start, but the Ox64 is talking to my PC now! Yay! Come back to my blog at a later time to see if I will manage to run Linux on the Ox64! Because as I understand it, I also need to flash something to the D0 and then flash the actual OS as well.\n\n  **UPDATE:** Here is [PART 2](https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer-part-2.html).\n","body_html":"<p>Yes, you read that right... for <a href=\"https://pine64.com/product/128mb-ox64-sbc-available-on-december-2-2022/\" rel=\"nofollow ugc noopener\">$8</a> you can run linux on a RISC-V computer.\n  And not just a stripped down kernel without an MMU.\n  No, the Ox64 comes with capable RISC-V cores.\n  Heck, and not just one core, but three cores (all different.)\n  Exciting times!</p>\n<p>  <strong>Caveat Emptor!</strong> At the time of writing, ethernet, wifi and SD-Card are not working. It&#39;s good to realize this before jumping into this.</p>\n<p>It looks like a microcontroller, but behaves like a UNIX machine. Sweet, or what? Getting it up and running, though, is far from trivial. There are so many hurdles to take!</p>\n<p>  <strong>Hurdle 1</strong>: You cannot program it using USB, like you would an Arduino, ESP32, Stamp-C3 or rPi Pico.\n  Nope... this needs to be programmed via the UART TX/RX pins.\n  In the picture above, you can see them hooked up to GPIO14 / GPIO15 and GND.</p>\n<p>  <strong>Hudle 2</strong>: The flashing tool Dev Cube will crash on launch when using Ubuntu on Wayland: you have to switch to Xorg instead.</p>\n<p>$ ./BLDevCube-ubuntu \nWarning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.\n/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_log_structured_standard\nFailed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so\nGLib-GIO-Message: Using the &#39;memory&#39; GSettings backend.  Your settings will not be saved or shared with other applications.\n(BLDevCube-ubuntu:54646): GLib-GIO-ERROR **: Settings schema &#39;org.gnome.settings-daemon.plugins.xsettings&#39; does not contain a key named &#39;antialiasing&#39;\nTrace/breakpoint trap (core dumped)</p>\n<p>  So, UART programming then... fine, we&#39;ll just use one of those little CH340G dongles.\n  I got <a href=\"https://www.amazon.ca/gp/product/B07V556Q82\" rel=\"nofollow ugc noopener\">one</a> off Amazon, but it would not work... every time the handshake would fail in Dev Cube (<strong>hurdle 3</strong>).</p>\n<p>  Luckily, <a href=\"https://discord.com/channels/463237927984693259/771032441971802142\" rel=\"nofollow ugc noopener\">some people</a> found out that you can program it with an RP2040 device, like the rPi Pico.\n  I had a <a href=\"https://learn.adafruit.com/adafruit-kb2040\" rel=\"nofollow ugc noopener\">KB2040</a> from Adafruit lying around, so used that.</p>\n<p>  Which puts us at <strong>hurdle 4</strong>: How to turn a KB2040 into a serial bridge between PC and Ox64?\n  Hook up GPIO-4 of the RP2040 to GPIO-15 of the Ox64. Hook up GPIO-5 of the RP2040 to GPIO-14 of the Ox64.\n  Also, connect the grounds, of course.\n  See below how to hook up for flashing the M0.\\</p>\n<p>  Then we need to load our RP2040 with <a href=\"https://github.com/raspberrypi/picoprobe\" rel=\"nofollow ugc noopener\">picoprobe</a> which we can do by holding BOOT while powering up, and feeding it the uf2 file with picoprobe.</p>\n<p>  Ok, so now we can flash it then? Unfortunately, no, <strong>hurdle 5</strong>: DevCube is still not able to flash the Ox64, but we can use <a href=\"https://pypi.org/project/bflb-mcu-tool/\" rel=\"nofollow ugc noopener\">bflb-mcu-tool</a> instead.</p>\n<p>  Ok, but with bflb-mcu-tool, we are all set! Are we? \n  Introducing <strong>hurdle 6</strong>: we need to modify the tool before it will work for us.\n  This means stripping DTR and RTS stuff from the tool by editing the\n  ~/.local/lib/python3.10/site-packages/bflb_mcu_tool/libs/bflb_interface_uart.py file.\n  Here is <a href=\"https://gist.github.com/stolk/46228d2b7ab0ca5b0ff98a4ce3b2c6fe\" rel=\"nofollow ugc noopener\">my copy</a>.</p>\n<p>  So with the Ox64 powered via MicroUSB, and the RP2040 connected to my PC using USB-C, I can finally flash something.\n  For that, I took the low_load_bl808_m0.bin from the <a href=\"https://github.com/bouffalolab/bl808_linux\" rel=\"nofollow ugc noopener\">bl808 linux guide</a> and flashed it with:</p>\n<pre><code>```</code></pre>\n<p>$ bflb-mcu-tool --chipname=bl808 --port=/dev/ttyACM2 --baudrate=2000000 --firmware=out/low_load_bl808_m0.bin</p>\n<pre><code>  \n\n  After which I now get output from my Ox64, via my KB2040 to my PC:\n  \n    ```\ndynamic memory init success,heap size = 156 Kbyte \nE907 start...\nmtimer clk:1000000\npsram clk init ok!\n    </code></pre>\n<p>Ok, a modest start, but the Ox64 is talking to my PC now! Yay! Come back to my blog at a later time to see if I will manage to run Linux on the Ox64! Because as I understand it, I also need to flash something to the D0 and then flash the actual OS as well.</p>\n<p>  <strong>UPDATE:</strong> Here is <a href=\"https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer-part-2.html\" rel=\"nofollow ugc noopener\">PART 2</a>.</p>","headings":[]}}