SpacemiT K1 / Banana Pi F3 Android BSP

Multi-repo manifests for the BayLibre Android 16 BSP targeting the SpacemiT K1 (RISC-V) on the Banana Pi F3 board.

Manifests in this repo

File	Tree	Base
default.xml	AOSP	android16-qpr2-release (Google)
kernel.xml	Android Common Kernel	main-kernel (Google), kernel/common branch android-mainline-riscv64

Both inherit the upstream Google manifests and apply BayLibre overrides at the bottom of the file. See Overrides below.

Expected layout

spacemit/
  aosp/      AOSP tree              (default.xml, required)
  kernel/    Android Common Kernel  (kernel.xml, optional — only to rebuild the kernel)
  mesa/      Mesa source            (BayLibre/mesa, optional — only to rebuild Mesa)
  gpu/       Mesa build helper      (build-mesa-powervr.sh, optional)

The AOSP tree already carries:

• Mesa userspace prebuilts under device/spacemit/k1/mesa/lib64/
• kernel prebuilts under device/spacemit/k1-kernel/mainline/

so a plain m from aosp/ produces flashable images on its own. Cloning kernel/, mesa/ and gpu/ is only required when you have local changes to rebuild.

Prerequisites

Standard AOSP host setup (repo, git, JDK, ~300 GB free disk).

If you plan to rebuild Mesa locally, also install:

• meson, ninja, cmake
• llvm-config-15 or newer (with C++ libs)
• patchelf
• Python 3

Sync the source

Required — AOSP tree:

mkdir -p spacemit && cd spacemit
mkdir aosp && (cd aosp && repo init -u git@github.com:BayLibre/android_manifest.git -b android-16-spacemit -m default.xml && repo sync -j$(nproc))

Optional — only if you plan to rebuild the kernel locally:

mkdir kernel && (cd kernel && repo init -u git@github.com:BayLibre/android_manifest.git -b android-16-spacemit -m kernel.xml && repo sync -j$(nproc))

Optional — only if you plan to rebuild Mesa locally:

git clone -b android-pvr-support git@github.com:BayLibre/mesa.git mesa

The gpu/ helper directory (Mesa cross-build script) is currently shipped out-of-band; copy build-mesa-powervr.sh and the android-riscv64 meson cross file into a gpu/ directory at the top level next to aosp/ and mesa/.

Build

AOSP (required)

cd aosp && source build/envsetup.sh && lunch aosp_bananapi_f3-trunk_staging-userdebug && m

Output images land in out/target/product/k1/.

Rebuild Mesa (optional)

Cross-builds Mesa for Android RISC-V and overwrites the prebuilts in aosp/device/spacemit/k1/mesa/lib64/. Includes a patchelf --set-soname libgbm_mesa.so step so the Soong wrapper finds the prebuilt at runtime.

cd gpu && ./build-mesa-powervr.sh

The first run builds the native helpers mesa_clc and pco_clc under /tmp/mesa-compiler (a few minutes). Subsequent runs can skip them with --skip-native. Re-run m from aosp/ afterwards to repackage the images.

Rebuild the kernel (optional)

Builds the GKI kernel, the SpacemiT K1 modules and the Banana Pi F3 device tree blob, and overwrites the kernel prebuilts in aosp/device/spacemit/k1-kernel/mainline/.

cd kernel && tools/bazel run --config=fast //devices/spacemit/bananapi_f3:spacemit_k1x_dist -- --destdir=../aosp/device/spacemit/k1-kernel/mainline/

Re-run m from aosp/ afterwards to repackage the images.

Flash the board

After m, the AOSP build deposits flash_bpi_f3.sh, the bootloader prebuilts (FSBL.bin, fw_dynamic.itb, u-boot.itb, env.bin, partition_android.json) and the Android images (boot.img, super.img, vbmeta*.img, …) all together into out/target/product/k1/. Run the script from there:

cd aosp/out/target/product/k1

Putting the board in DFU mode (first-time setup)

The board exposes the SpacemiT BROM USB download interface (USB ID 361c:1001) when in DFU mode. This is required for the first-time flash on a fresh eMMC, and to recover from a bricked bootloader.

1. Disconnect all power and USB cables from the board.
2. Connect a USB-C data cable from the host to the F3 OTG / USB-data port.
3. Press and hold the BOOT button on the board (sometimes labelled U-BOOT or KEY).
4. Apply power while holding the button — second USB-C / barrel jack, or a powered USB-C host port.
5. Release the BOOT button after about 2 seconds.
6. Verify on the host that the board is in BROM mode:

lsusb | grep 361c:1001

The line Bus xxx Device xxx: ID 361c:1001 ... confirms DFU mode.

Flash modes

From out/target/product/k1/:

./flash_bpi_f3.sh                # default: bootloader + Android via fastboot (board in U-Boot)
./flash_bpi_f3.sh --bootloader   # bootloader only
./flash_bpi_f3.sh --android      # Android images only
./flash_bpi_f3.sh --dfu          # full DFU flash from BROM (first-time setup)
./flash_bpi_f3.sh --dfu --wipe   # first-time DFU + clean userdata
./flash_bpi_f3.sh --no-avb       # disable AVB verification (bringup/development)

For the fastboot modes, run fastboot usb 0 on the U-Boot console first so the board exposes its fastboot interface to the host.

Overrides

Compared to the upstream Google manifests, this BSP overrides:

Manifest	Project	Source	Notes
default.xml	external/minigbm	BayLibre/android_external_minigbm @ android-16	gbm_mesa backend + dma_heap driver + runtime backend selection on top of upstream cros_gralloc
default.xml	device/spacemit/common	BayLibre/android_device_spacemit_common @ android-16	board-agnostic SpacemiT bits (added)
default.xml	device/spacemit/k1	BayLibre/android_device_spacemit_k1 @ android-16	K1 SoC + Banana Pi F3 board overlay, Mesa userspace prebuilts, audio/Bluetooth/Wi-Fi HAL configs, SELinux vendor policy (added)
default.xml	device/spacemit/k1-kernel	BayLibre/android_device_spacemit_k1_kernel @ android-16	Kleaf-built kernel prebuilts (Image, .ko modules, .dtb) consumed by the AOSP build (added)
kernel.xml	devices/spacemit	BayLibre/android_kernel_device_spacemit @ android-mainline-riscv64	Banana Pi F3 Kleaf kernel_build target (replaces the Pixel raviole device tree)