Açıklama Yok

Ricardo Salveti 311ab1a78f freedom-u540: set UBOOT_DTB_LOADADDRESS 4 yıl önce
.github 2cf991cc31 add templates for commits and issues 5 yıl önce
conf 311ab1a78f freedom-u540: set UBOOT_DTB_LOADADDRESS 4 yıl önce
docs c3c86618f8 Added a missing word to docs 5 yıl önce
dynamic-layers b9be00d487 qtbase,qtdeclarative: Add -pthread to linker flags 5 yıl önce
recipes-bsp c23d485f94 u-boot: change overrides to be specific to freedom-u540 4 yıl önce
recipes-core 9d52dc3a2c musl: Delete riscv patches as they are upstreamed in musl >= 1.1.23 4 yıl önce
recipes-devtools 4157f3e012 gdb: Remove the RISC-V GDB 5 yıl önce
recipes-extended 551482f31e ltp: Fix build with musl 5 yıl önce
recipes-kernel 5d40902f03 linux: freedom-u540: Enable support for an INITRD 4 yıl önce
recipes-support 0aea644bb7 libunwind: Fix build for riscv64 5 yıl önce
tools 8fa69a8f27 switch to using OE-Core/bitbake instead of poky 5 yıl önce
wic 58d8b69fcb freedom-u540-opensbi.wks: Change partition order 4 yıl önce
.travis.yml b9ddd7d692 travis: Try to stop builds timing out 4 yıl önce
LICENSE c4a4f88410 Initial commit 6 yıl önce
README.md b19692e67d README: Update the README to include more detailed instructions 4 yıl önce
setup.sh bf6e63d854 Add meta-python before meta-multimedia 4 yıl önce

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 layers uptodate with upstream

cd riscv-yocto
repo sync
repo rebase

Setup Build Environment

. ./meta-riscv/setup.sh

Avaliable 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 Unleased 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 Unleased 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>