No Description

Vijai Kumar K 98708e9065 Fix some minor typos in documentation 4 years ago
.github 2cf991cc31 add templates for commits and issues 5 years ago
conf 99cdf8d0cf machine/qemuriscv32: Remove device loader 4 years ago
docs 98708e9065 Fix some minor typos in documentation 4 years ago
dynamic-layers b9be00d487 qtbase,qtdeclarative: Add -pthread to linker flags 5 years ago
recipes-bsp 90b51bb980 u-boot: Fix the mabc probing with 5.3 device tree 4 years ago
recipes-connectivity 55a188ec70 openssl: Update the RV32 append to 1.1.1d 4 years ago
recipes-core b5443214a2 busybox: Fix y2038 64-bit time_t build failures 4 years ago
recipes-devtools 4157f3e012 gdb: Remove the RISC-V GDB 5 years ago
recipes-extended 1b726bf8bb ltp: Remove RISC-V Patches 4 years ago
recipes-kernel 270c8cb7c1 linux-mainline: Move some configs into the include file 4 years ago
recipes-support 11504e23cf libffi: Remove from meta-riscv 4 years ago
tools 8fa69a8f27 switch to using OE-Core/bitbake instead of poky 5 years ago
wic fa8c8584c4 wic: add freedom-u540 wic for sota/ostree 4 years ago
.travis.yml b9ddd7d692 travis: Try to stop builds timing out 4 years ago
LICENSE c4a4f88410 Initial commit 6 years ago
README.md 98708e9065 Fix some minor typos in documentation 4 years ago
setup.sh 0ec98278a9 setup.sh: Do not delete build dir 4 years ago

README.md

meta-riscv

RISC-V Architecture Layer for OpenEmbedded/Yocto

license Build Status

Description

This is the general hardware-specific BSP overlay for the RISC-V based devices.

More information can be found at: https://riscv.org/ (Official Site)

The core BSP part of meta-riscv should work with different OpenEmbedded/Yocto distributions and layer stacks, such as:

  • Distro-less (only with OE-Core).
  • Angstrom.
  • Yocto/Poky.

Dependencies

This layer depends on:

  • URI: git://github.com/openembedded/openembedded-core
    • branch: master
    • revision: HEAD
  • URI: git://github.com/openembedded/bitbake
    • branch: master
    • revision: HEAD

Quick Start

Note: You only need this if you do not have an existing Yocto Project build environment.

Make sure to install the repo command by Google first.

Create workspace

mkdir riscv-yocto && cd riscv-yocto
repo init -u git://github.com/riscv/meta-riscv  -b master -m tools/manifests/riscv-yocto.xml
repo sync
repo start work --all

Update existing workspace

In order to bring all the layers up to date with upstream

cd riscv-yocto
repo sync
repo rebase

Setup Build Environment

. ./meta-riscv/setup.sh

Available Machines

The three different machines you can build for are:

  • qemuriscv64: The 64-bit RISC-V machine
  • qemuriscv32: The 32-bit RISC-V machine
  • freedom-u540: The SiFive HiFive Unleashed board

Build Images

A console-only image for the 64-bit QEMU machine

MACHINE=qemuriscv64 bitbake core-image-full-cmdline

Basic image without X support suitable for Linux Standard Base (LSB) implementations. It includes the full meta-toolchain, plus development headers and libraries to form a standalone (on device) SDK for the 32-bit QEMU machine

MACHINE=qemuriscv32 bitbake core-image-lsb-sdk

To build an image to run on the HiFive Unleashed using Wayland run the following

MACHINE=freedom-u540 bitbake core-image-wayland

To build a full GUI equipped image running Plasma Mobile see the in-tree documentation here.

Running in QEMU

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

MACHINE=qemuriscv64 runqemu nographic

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

MACHINE=qemuriscv32 runqemu nographic

Running on hardware

Setting up a TFTP server

If you would like to boot the images from a TFTP server (optional) you should set your TFTP server address in your local.conf with the following line. Change 127.0.0.1 to the IP address of your TFTP server and copy the uImage to the server.

TFTP_SERVER_IP = "127.0.0.1"

Running with the Microsemi Expansion board

To use the Microsemi expansion board with your HiFive Unleased add the following line to your local.conf. This tells the Unleashed to use a device tree with the PCIe device described:

RISCV_SBI_FDT_freedom-u540 = "hifive-unleashed-a00-microsemi.dtb"

Sparse Image Creation

The output of the build can also be written to an SD card using bmaptool, the steps to do this are below:

$ MACHINE=freedom-u540 wic create freedom-u540-opensbi -e core-image-minimal
$ bmaptool create ./freedom-u540-opensbi-201812181337-mmcblk.direct > image.bmap
$ sudo bmaptool copy --bmap image.bmap ./freedom-u540-opensbi-201812181337-mmcblk.direct /dev/sdX

dding wic.gz

The output of a freedom-u540 build will be a <image>.wic.gz file. You can write this file to an sd card using:

$ zcat <image>-<machine>.wic.gz | sudo dd of=/dev/sdX bs=4M iflag=fullblock oflag=direct conv=fsync status=progress

Maintainer(s)

  • Khem Raj <raj dot khem at gmail.com>