Ox64 - Revision history

Tllim: /* Quick Links to the Source of OS Images Build */

2026-05-02T22:10:25Z

Quick Links to the Source of OS Images Build

← Older revision		Revision as of 22:10, 2 May 2026
Line 16:		Line 16:
	* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others		* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others
	* [https://github.com/gabearro/bl808-hal-nim NIM based HAL] Hardware abstraction layer by gabearro		* [https://github.com/gabearro/bl808-hal-nim NIM based HAL] Hardware abstraction layer by gabearro
	* [~~hhttps~~://github.com/domhathair/pine64_ox64_archlinux Arch Linux] Arch Linux build by domhathair		* [https://github.com/domhathair/pine64_ox64_archlinux Arch Linux] Arch Linux build by domhathair

Tllim: /* Quick Links to the Source of OS Images Build */

2026-05-02T22:10:06Z

Quick Links to the Source of OS Images Build

← Older revision		Revision as of 22:10, 2 May 2026
Line 16:		Line 16:
	* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others		* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others
	* [https://github.com/gabearro/bl808-hal-nim NIM based HAL] Hardware abstraction layer by gabearro		* [https://github.com/gabearro/bl808-hal-nim NIM based HAL] Hardware abstraction layer by gabearro
			* [hhttps://github.com/domhathair/pine64_ox64_archlinux Arch Linux] Arch Linux build by domhathair

Tllim: /* Quick Links to the Source of OS Images Build */

2026-05-02T16:42:13Z

Quick Links to the Source of OS Images Build

← Older revision		Revision as of 16:42, 2 May 2026
Line 15:		Line 15:
	* [https://github.com/arm000/linux-bl808/tree/linux-next/mboxic Kernel] IRQChip, SDCard, and (WIP) USB by arm000, Alexander Horner and others		* [https://github.com/arm000/linux-bl808/tree/linux-next/mboxic Kernel] IRQChip, SDCard, and (WIP) USB by arm000, Alexander Horner and others
	* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others		* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others
			* [https://github.com/gabearro/bl808-hal-nim NIM based HAL] Hardware abstraction layer by gabearro


	Original Linux Images provided by Bouffalo - Very basic '''alpha build''' which are only fit for board bring up and testing purposes.		Original Linux Images provided by Bouffalo - Very basic '''alpha build''' which are only fit for board bring up and testing purposes.

Jeffalyanak: /* Compatible UARTs when in bootloader mode */

2024-08-19T13:38:49Z

Compatible UARTs when in bootloader mode

← Older revision		Revision as of 13:38, 19 August 2024
Line 157:		Line 157:
	* Some UART adapters based on the FT232H (note that the FT232RL does not work, and neither does the Pine 64 JTAG)		* Some UART adapters based on the FT232H (note that the FT232RL does not work, and neither does the Pine 64 JTAG)
	* Some CH340G based adapters work and some don't.		* Some CH340G based adapters work and some don't.
			* Flipper Zero UART-Bridge works with baud rate set to 230400.

	== Resources and Articles ==		== Resources and Articles ==

Giorez at 15:54, 23 June 2024

2024-06-23T15:54:25Z

Giorez at 15:51, 23 June 2024

2024-06-23T15:51:54Z

Show changes

Giorez: /* Flashing */

2024-06-23T15:46:05Z

Flashing

← Older revision		Revision as of 15:46, 23 June 2024
Line 226:		Line 226:
	Buildroot will output the needed files to the `~/ox64/buildroot/output/images` directory in about 1 hour, according to your computer processing resources and internet connection speed.		Buildroot will output the needed files to the `~/ox64/buildroot/output/images` directory in about 1 hour, according to your computer processing resources and internet connection speed.

	== Flashing ~~Ox64 SBC and microSD Card~~ ==		== Flashing ==
	This page explains how to flash an Ox64 board and a microSD card to boot the system. You will need a Linux computer, a serial UART adapter, the Ox64 board, and a microSD card.		This page explains how to flash an Ox64 board and a microSD card to boot the system. You will need a Linux computer, a serial UART adapter, the Ox64 board, and a microSD card.

Line 341:		Line 341:

	[NOTE]		[NOTE]

	====		====
	The one catch is that you already need a serial adapter in order to program your Bluepill board. The good news is that you serial adapter does not have to be one from from the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. These programming instructions have been tested with a FT232RL adapter (which, notably, is listed as _not_ supported on that list).		The one catch is that you already need a serial adapter in order to program your Bluepill board. The good news is that you serial adapter does not have to be one from from the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. These programming instructions have been tested with a FT232RL adapter (which, notably, is listed as _not_ supported on that list).

Giorez: /* Building */

2024-06-23T15:45:31Z

Building

← Older revision		Revision as of 15:45, 23 June 2024
Line 186:		Line 186:
	* [https://twitter.com/thanos_engine/status/1585153938092761093 Phone Concept for BL808]		* [https://twitter.com/thanos_engine/status/1585153938092761093 Phone Concept for BL808]

	== ~~Build~~==		== Building ==
	Start the building process cloning both the upstream Buildroot repository and the Buildroot Bouffalo overlay repository:		Start the building process cloning both the upstream Buildroot repository and the Buildroot Bouffalo overlay repository:

Giorez: /* Flashing Ox64 SBC and microSD Card */

2024-06-23T15:44:23Z

Flashing Ox64 SBC and microSD Card

Show changes

Giorez: /* Build */

2024-06-23T15:37:04Z

Build

← Older revision		Revision as of 15:37, 23 June 2024
Line 189:		Line 189:
	Start the building process cloning both the upstream Buildroot repository and the Buildroot Bouffalo overlay repository:		Start the building process cloning both the upstream Buildroot repository and the Buildroot Bouffalo overlay repository:

	~~----~~
	$ mkdir -p ~/ox64		$ mkdir -p ~/ox64
	$ cd ~/ox64		$ cd ~/ox64
	$ git clone https://github.com/buildroot/buildroot		$ git clone https://github.com/buildroot/buildroot
	$ git clone https://github.com/openbouffalo/buildroot_bouffalo		$ git clone https://github.com/openbouffalo/buildroot_bouffalo
	~~----~~

	Define an environment variable for the Buildroot Bouffalo overlay path:		Define an environment variable for the Buildroot Bouffalo overlay path:

	~~----~~		$ export BR_BOUFFALO_OVERLAY_PATH=$(pwd)/buildroot_bouffalo
	$ export BR_BOUFFALO_OVERLAY_PATH=$(pwd)/buildroot_bouffalo
	~~----~~

	Change directory into the cloned Buildroot folder:		Change directory into the cloned Buildroot folder:

	~~----~~		$ cd ~/ox64/buildroot
	$ cd ~/ox64/buildroot
	~~----~~

	Apply the default configuration for Pine64 Ox64:		Apply the default configuration for Pine64 Ox64:

	~~----~~		$ make BR2_EXTERNAL=$BR_BOUFFALO_OVERLAY_PATH pine64_ox64_defconfig
	$ make BR2_EXTERNAL=$BR_BOUFFALO_OVERLAY_PATH pine64_ox64_defconfig
	~~----~~

	Use the `menuconfig` tool to adjust the build settings:		Use the `menuconfig` tool to adjust the build settings:

	~~----~~		$ make menuconfig
	$ make menuconfig
	~~----~~

	Within `menuconfig`, configure the following:		Within `menuconfig`, configure the following:
Line 232:		Line 222:
	Initiate the build process, but first make sure that your `PATH` variable contains no spaces. For Arch Linux distrubution you may also need to install extra-packages with `sudo pacman -S cpio rsync bc`.		Initiate the build process, but first make sure that your `PATH` variable contains no spaces. For Arch Linux distrubution you may also need to install extra-packages with `sudo pacman -S cpio rsync bc`.

	~~----~~		$ make
	$ make
	~~----~~

	Buildroot will output the needed files to the `~/ox64/buildroot/output/images` directory in about 1 hour, according to your computer processing resources and internet connection speed.		Buildroot will output the needed files to the `~/ox64/buildroot/output/images` directory in about 1 hour, according to your computer processing resources and internet connection speed.

← Older revision		Revision as of 15:54, 23 June 2024
Line 229:		Line 229:
	This page explains how to flash an Ox64 board and a microSD card to boot the system. You will need a Linux computer, a serial UART adapter, the Ox64 board, and a microSD card.		This page explains how to flash an Ox64 board and a microSD card to boot the system. You will need a Linux computer, a serial UART adapter, the Ox64 board, and a microSD card.

	== Prepare images for flashing ==		=== Prepare images for flashing ===

	Download the Ox64 images from the latest OpenBouffalo release. You may skip this step if you built your own images as per the instructions in the link:/documentation/Ox64/Software/Building/[Building] page.		Download the Ox64 images from the latest OpenBouffalo release. You may skip this step if you built your own images as per the instructions in the link:/documentation/Ox64/Software/Building/[Building] page.
Line 241:		Line 241:
	$ mv sdcard-pine64_ox64_full_defconfig.img sdcard.img		$ mv sdcard-pine64_ox64_full_defconfig.img sdcard.img

	=== Optional: create a combined SoC image ===		==== Optional: create a combined SoC image ====

	Use the following commands to combine _m0_lowload_bl808_m0.bin_, _d0_lowload_bl808_d0.bin_, and _bl808-firmware.bin_ into a single image. This is mainly useful for troubleshooting (e. g. when using DevCube v1.8.4 or later).		Use the following commands to combine _m0_lowload_bl808_m0.bin_, _d0_lowload_bl808_d0.bin_, and _bl808-firmware.bin_ into a single image. This is mainly useful for troubleshooting (e. g. when using DevCube v1.8.4 or later).
Line 254:		Line 254:
	$ cat bl808-firmware.bin >> bl808-combined.bin		$ cat bl808-firmware.bin >> bl808-combined.bin

	=== Check that you have the required files for flashing ===		==== Check that you have the required files for flashing ====

	$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images		$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
Line 270:		Line 270:
	* `sdcard.img` -- Kernel and root filesystem. Runs on the D0 core.		* `sdcard.img` -- Kernel and root filesystem. Runs on the D0 core.

	== Set up your UART adapter ==		=== Set up your UART adapter ===

	In this section we will configure and wire up a UART adapter in order to flash the Ox64. Choose one of the options below based on the hardware available to you; the first two are the most convenient since they minimise the number of times you will need to swap electrical connections.		In this section we will configure and wire up a UART adapter in order to flash the Ox64. Choose one of the options below based on the hardware available to you; the first two are the most convenient since they minimise the number of times you will need to swap electrical connections.

	=== Option 1: Raspberry Pi Pico ===		==== Option 1: Raspberry Pi Pico ====

	First, download the Raspberry Pi Pico firmware that allows it to act as a serial UART adapter:		First, download the Raspberry Pi Pico firmware that allows it to act as a serial UART adapter:
Line 336:		Line 336:
	* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)		* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)

	=== Option 2: STM32 Bluepill ===		==== Option 2: STM32 Bluepill ====

	The Bluepill is an affordable STM32 development board, based on the STM32F103C8T6 chip. We can program it to act as a USB serial adapter, just like we did with the Raspberry Pi Pico.		The Bluepill is an affordable STM32 development board, based on the STM32F103C8T6 chip. We can program it to act as a USB serial adapter, just like we did with the Raspberry Pi Pico.
Line 423:		Line 423:
	* `/dev/ttyACM2` (unused)		* `/dev/ttyACM2` (unused)

	=== Option 3: Generic UART adapter ===		==== Option 3: Generic UART adapter ====

	image:/documentation/Ox64/images/ox64_pinout.png[Ox64 pinout,title="Ox64 pinout", 300, float="right"]		image:/documentation/Ox64/images/ox64_pinout.png[Ox64 pinout,title="Ox64 pinout", 300, float="right"]
Line 451:		Line 451:
	Then, follow the instructions in <<booting_for_the_first_time>>, but replace all occurrences of `/dev/ttyACM0` with `/dev/tty[DEVICE]`. You should then have a working Linux system.		Then, follow the instructions in <<booting_for_the_first_time>>, but replace all occurrences of `/dev/ttyACM0` with `/dev/tty[DEVICE]`. You should then have a working Linux system.

	== Download flashing tools ==		=== Download flashing tools ===

	You have a choice of flashing software:		You have a choice of flashing software:
Line 458:		Line 458:
	* CLI (`bflb-iot-tool`): command line open source flashing tool		* CLI (`bflb-iot-tool`): command line open source flashing tool

	=== DevCube installation ===		==== DevCube installation ====

	Download the latest DevCube flashing tool from BouffaloLab's website:		Download the latest DevCube flashing tool from BouffaloLab's website:
Line 480:		Line 480:
	* SHA256: `e6e6db316359da40d29971a1889d41c9e97d5b1ff1a8636e9e6960b6ff960913`		* SHA256: `e6e6db316359da40d29971a1889d41c9e97d5b1ff1a8636e9e6960b6ff960913`

	=== CLI packages installation ===		==== CLI packages installation ====

	Install `bflb-iot-tool` using your preferred method of managing PIP packages. One option is to set up a Python virtual environment as follows:		Install `bflb-iot-tool` using your preferred method of managing PIP packages. One option is to set up a Python virtual environment as follows:
Line 497:		Line 497:
	NOTE: Each time you open a new terminal window you will need to `cd ~/ox64/` and re-run `pipenv shell` to reactivate the virtual environment.		NOTE: Each time you open a new terminal window you will need to `cd ~/ox64/` and re-run `pipenv shell` to reactivate the virtual environment.

	== Flashing the Ox64 ==		=== Flashing the Ox64 ===

	Put the Ox64 into programming mode:		Put the Ox64 into programming mode:
Line 505:		Line 505:
	* Release the BOOT button		* Release the BOOT button

	=== CLI flashing method ===		==== CLI flashing method ====

	Set up some environment variables to save typing them out later:		Set up some environment variables to save typing them out later:
Line 528:		Line 528:
	If you get permission errors when running any of the commands above, run `ls -l /dev/tty[DEVICE]`, to find out which group is allowed to talk to serial ports and add your user to that group, with `sudo usermod -a -G [GROUP] $USER` (i.e. `dialout` for Debian or `uucp` for Arch Linux). Make sure you re-login. Running the commands as `root` is not recommended since this will make `bflb-iot-tool` create root-owned files in your home directory. You can now run `exit` from virtual environment.		If you get permission errors when running any of the commands above, run `ls -l /dev/tty[DEVICE]`, to find out which group is allowed to talk to serial ports and add your user to that group, with `sudo usermod -a -G [GROUP] $USER` (i.e. `dialout` for Debian or `uucp` for Arch Linux). Make sure you re-login. Running the commands as `root` is not recommended since this will make `bflb-iot-tool` create root-owned files in your home directory. You can now run `exit` from virtual environment.

	=== BLDevCube flashing method		==== BLDevCube flashing method ====

	Open a new terminal window to run the DevCube flasher:		Open a new terminal window to run the DevCube flasher:
Line 569:		Line 569:
	* Close DevCube		* Close DevCube

	== Erasing the microSD card ==		=== Erasing the microSD card ===

	Make sure there are no signatures or partitions left, and overwrite the first sectors with zeroes. You can find the target device under `lsblk` command.		Make sure there are no signatures or partitions left, and overwrite the first sectors with zeroes. You can find the target device under `lsblk` command.
Line 581:		Line 581:
	$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=$(expr $(lsblk -bno SIZE /dev/[DEVICE] \| head -1) \/ 32768)		$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=$(expr $(lsblk -bno SIZE /dev/[DEVICE] \| head -1) \/ 32768)

	== Flashing the microSD card ==		=== Flashing the microSD card ===

	Insert the microSD card into your PC, locate its device under `lsblk` and write the image:		Insert the microSD card into your PC, locate its device under `lsblk` and write the image:
Line 591:		Line 591:
	$ sudo dd if=sdcard.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync		$ sudo dd if=sdcard.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync

	== Booting for the first time ==		=== Booting for the first time ===

	Power off your Ox64 and insert the microSD card.		Power off your Ox64 and insert the microSD card.
Line 618:		Line 618:
	Once the system is running, the "MBOX" logs will abruptly disappear and you'll be able to manage the M0 multimedia core, i.e. wifi settings, etc. When prompted, type `help` to see available commands.		Once the system is running, the "MBOX" logs will abruptly disappear and you'll be able to manage the M0 multimedia core, i.e. wifi settings, etc. When prompted, type `help` to see available commands.

	=== Connecting the Ox64 to your WiFi network ===		==== Connecting the Ox64 to your WiFi network ====

	The simplest way to connect is to run the following command from the Linux console (i.e. `/dev/ttyACM0`):		The simplest way to connect is to run the following command from the Linux console (i.e. `/dev/ttyACM0`):
Line 632:		Line 632:
	For more information on using the `blctl` command, see https://github.com/bouffalolab/blwnet_xram[here].		For more information on using the `blctl` command, see https://github.com/bouffalolab/blwnet_xram[here].

	== Appendix ==		=== Appendix ===

	=== Adding Nuttx RTOS ===		==== Adding Nuttx RTOS ====

	In this section, we will set up our Ox64 to dual-boot both Linux and the NuttX real-time operating system. For more information see the https://nuttx.apache.org/docs/latest/platforms/risc-v/bl808/boards/ox64/index.html[official documentation].		In this section, we will set up our Ox64 to dual-boot both Linux and the NuttX real-time operating system. For more information see the https://nuttx.apache.org/docs/latest/platforms/risc-v/bl808/boards/ox64/index.html[official documentation].