GitPlanet

Cheap and reliable Node.js hosting starts at $3/month, and $1/month static HTML hosting

Created with love in Canada, visit hostnodejs.com today

Feel like to post an Ad? Learn Details
All Projects → riscv → Meta Riscv

riscv / Meta Riscv

Licence: other
OpenEmbedded/Yocto layer for RISC-V Architecture

Labels

risc-vriscv

Projects that are alternatives of or similar to Meta Riscv

Cores Swerv El2
SweRV EL2 Core
Stars: ✭ 79 (-30.7%)
Mutual labels:  risc-v, riscv
Ustc Rvsoc
FPGA-based RISC-V CPU+SoC.
Stars: ✭ 77 (-32.46%)
Mutual labels:  risc-v, riscv
Maxine Vm
Maxine VM: A meta-circular research VM
Stars: ✭ 274 (+140.35%)
Mutual labels:  risc-v, riscv
bx-docker
Tutorial on how to build Docker Images for the IAR Build Tools on Linux hosts. The IAR Build Tools on Linux are available for Arm, RISC-V and Renesas (RH850, RL78 and RX).
Stars: ✭ 28 (-75.44%)
Mutual labels:  riscv, risc-v
Cores Swerv
SweRV EH1 core
Stars: ✭ 406 (+256.14%)
Mutual labels:  risc-v, riscv
NMSIS
Nuclei Microcontroller Software Interface Standard Development Repo
Stars: ✭ 24 (-78.95%)
Mutual labels:  riscv, risc-v
Darkriscv
opensouce RISC-V cpu core implemented in Verilog from scratch in one night!
Stars: ✭ 1,062 (+831.58%)
Mutual labels:  risc-v, riscv
rv32emu
RISC-V RV32I[MAC] emulator with ELF support
Stars: ✭ 61 (-46.49%)
Mutual labels:  riscv, risc-v
Scr1
SCR1 is a high-quality open-source RISC-V MCU core in Verilog
Stars: ✭ 393 (+244.74%)
Mutual labels:  risc-v, riscv
Jupiter
RISC-V Assembler and Runtime Simulator
Stars: ✭ 326 (+185.96%)
Mutual labels:  risc-v, riscv
hero-sdk
⛔ DEPRECATED ⛔ HERO Software Development Kit
Stars: ✭ 21 (-81.58%)
Mutual labels:  riscv, risc-v
Chipyard
An Agile RISC-V SoC Design Framework with in-order cores, out-of-order cores, accelerators, and more
Stars: ✭ 436 (+282.46%)
Mutual labels:  risc-v, riscv
arv
ARV: Asynchronous RISC-V Go High-level Functional Model
Stars: ✭ 18 (-84.21%)
Mutual labels:  riscv, risc-v
Riscv Rust
RISC-V processor emulator written in Rust+WASM
Stars: ✭ 253 (+121.93%)
Mutual labels:  risc-v, riscv
mdepx
MDEPX — A BSD-style RTOS
Stars: ✭ 17 (-85.09%)
Mutual labels:  riscv, risc-v
Shecc
A self-hosting and educational C compiler
Stars: ✭ 286 (+150.88%)
Mutual labels:  risc-v, riscv
KyogenRV
The Simple 5-staged pipeline RISC-V written in chisel3 for intel FPGA.
Stars: ✭ 37 (-67.54%)
Mutual labels:  riscv, risc-v
riscv em
Simple risc-v emulator, able to run linux, written in C.
Stars: ✭ 51 (-55.26%)
Mutual labels:  riscv, risc-v
Lbforth
Self-hosting metacompiled Forth, bootstrapping from a few lines of C; targets Linux, Windows, ARM, RISC-V, 68000, PDP-11, asm.js.
Stars: ✭ 293 (+157.02%)
Mutual labels:  risc-v, riscv
Rars
RARS -- RISC-V Assembler and Runtime Simulator
Stars: ✭ 413 (+262.28%)
Mutual labels:  risc-v, riscv
View All Similar Projects ➔

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).
  • Yoe Distro.
  • 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 different machines you can build for are:

  • freedom-u540: The SiFive HiFive Unleashed board

Note that this layer also provides improvements and features for the upstream qemuriscv32 and qemuriscv64 machines.

Build Images

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

MACHINE=qemuriscv64 bitbake core-image-full-cmdline

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

MACHINE=freedom-u540 bitbake core-image-weston

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>
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].