No Description

tienhock.loh e003b1104c Merge branch 'starfive-kirkstone-dubhe-uboot' into 'starfive-kirkstone' 1 month ago
conf 495d539898 dubhe: starfive-dubhe.conf: Update machine config 1 month ago
dynamic-layers 973fcf0a8e jh8100: openocd: Update recipe for jh8100 support 3 months ago
recipes-benchmark d95d9bdb0e dubhe: dhrystone: Edit compiler flags 2 months ago
recipes-bsp 5d0826ebb9 dubhe: Change SRC_URI to Github 1 month ago
recipes-connectivity 7a8e42d781 dhcp: Remove files for dhcp-dev 3 months ago
recipes-core ae8bdc4fc5 dubhe: qspi-image: Update image generation method 1 month ago
recipes-devtools 4f3f4187d9 dubhe: llvm: Set llvm PV to 16.0.5 2 months ago
recipes-extended d5f37d375d lua-cjson: Add recipe and ptest support 3 months ago
recipes-graphics 6e12d580da visionfive2: xserver-xorg: Fix warning due to missing patches 1 month ago
recipes-httpd 768e9d8773 nginx: Add nginx-upload-module 3 months ago
recipes-kernel 5e852d4be5 dubhe: linux-starfive-dev: Update Linux kernel 1 month ago
recipes-multimedia ae2bfebccc visionfive2: ffmpeg: Add ffmpeg recipe 5 months ago
recipes-support 8b9845d005 dubhe: isl: Move isl recipe to recipes-support. 10 months ago
tools 096909ba2b dubhe: manifests: Use openembedded-core & bitbake layer provided by poky 7 months ago
wic c110cffeaa jh8100: starfive-jh8100: Added machine config 3 months ago 3434ec4a17 Update meta-starfive branch 1 month ago c48f6580c8 dubhe: Update image choices 1 month ago

StarFive Linux Software Development Kit (SDK)

The StarFive Dubhe Linux SDK is based on Yocto Project. It enables the creation of Linux distributions for any embedded project, as well as easy migration from a different architecture platform. The meta-starfive layer is built on top of meta-riscv to provide additional modifications such as Linux Kernel, and toolchains like GCC and LLVM.

Supported Features

  • FPGA Image Generation
    • Able to generate an image to boot up on FPGA directly

  • Yocto extensible-SDK (eSDK)
    • Shell-script installer
    • Shrink-wrapped distro maintainer environment
    • Updateable and Extensible

Setting up meta-starfive

Guide to use meta-starfive using Yocto


First, you need to download the essential Yocto dependencies, which can also be found on their official Yocto Guide:

$ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev pylint3 xterm python3-subunit mesa-common-dev zstd liblz4-tool

Installing Repo

Next, you will need to install the repo command from Google.


Create a workspace

Now, we will be creating a workspace and retrieve the latest layers needed for our image creation.

$ mkdir starfive-yocto && cd starfive-yocto
$ repo init -u -b starfive-kirkstone -m tools/manifests/starfive.xml
$ repo sync
$ repo start work --all

Setup Bitbake Environment

After having all the layers required, you can now source into the build environment by running the script in the meta-starfive layer. You should run the script in the starfive-yocto folder directory.

$ . ./meta-starfive/

Available Machines

In meta-starfive, there is currently only one buildable machine that you can build for:

  • starfive-dubhe: The StarFive Dubhe machine

Build Images

To build a initramfs image with QSPI-Image binary:

$ MACHINE=starfive-dubhe bitbake qspi-image

For the bitbake command, you can control the number of parallel tasks and the number of cores that Bitbake will use. You can either add the variables in the <build_directory>/conf/local.conf file, or add it in your shell environment command, for example:

$ PARALLEL_MAKE="-j 6" BB_NUMBER_THREADS=4 MACHINE=starfive-dubhe bitbake qspi-image

To populate the extensible eSDK shell script, you can use the -c populate_sdk_ext command:

$ MACHINE=starfive-dubhe bitbake qspi-image -c populate_sdk_ext

NOTE: For your first build, it may take several hours to build the image.

Running in QEMU

Run the 64-bit machine in QEMU using the following command:

MACHINE=starfive-dubhe runqemu nographic dubhe-image-initramfs

Tip: Once QEMU starts, in nographic mode, the terminal is ‘controlled’ by the Linux console. Thus, to kill QEMU and get back to the terminal, you can:

  • CTRL-a x to kill QEMU and exit

Running on FPGA

You will find image components such as openSBI (fwpayload.bin) and the Linux kernel in the bitbake build directory (/build/tmp-glibc/deploy/images/starfive-dubhe/_) after your bitbake process is done. You can also find the full QSPI binary image generated (QSPI-Image.bin), which includes the boot codes, openSBI and kernel in a single binary.

You can flash the QSPI binary into the FPGA via openOCD or other FPGA flashing tools.

Modifying the Kernel

To modify the kernel, you can use the devtool command line:

$ MACHINE=starfive-dubhe devtool modify virtual/kernel

The devtool command will fetch the source code and unpack them in the _‘build/workspace/sources/‘_ directory.

Now you can make your changes in your source code in the workspace directory.

Building the Kernel

After you had done your changes, you can build only the kernel by:

$ MACHINE=starfive-dubhe devtool build <kernel_name>


$ MACHINE=starfive-dubhe bitbake virtual/kernel

You can obtain the image generated in the images folder _build/tmp-glibc/deploy/images/starfive-dubhe/_

Saving the Modification

Once you are happy with the changes, you can go to the source folder and commit your changes:

  • Go to _workspace/sources/_:
    • $ git status
    • $ git add .
    • $ git commit -m "Changes added"
  • Create a bbappend and patch file:
    • $ devtool finish <kernel_name> <layer_path>
  • Rebuilding the Image

    To rebuild your image, the steps include:

    $ MACHINE=starfive-dubhe bitbake qspi-image

    Rebuilding will take less time as the sstate-cache is saved during your first build.


    In case you accidentally deleted files in the build/tmp/deploy/images/ directory and some of the files are not automatically re-created when you build the image again, you can rebuild and recreate the kernel files by:

    $ MACHINE=starfive-dubhe bitbake -c clean virtual/kernel
    $ MACHINE=starfive-dubhe bitbake virtual/kernel