mirror of
https://github.com/Fishwaldo/meta-riscv.git
synced 2025-03-15 19:41:42 +00:00
OpenEmbedded/Yocto layer for RISC-V Architecture
They result in linking errors, -fstack-protector-strong wants libssp libdrm errors when using -fstack-protector-strong drm@sha/xf86drmSL.c.o: relocation R_RISCV_HI20 against `__stack_chk_guard@@GLIBC_2.27' can not be used when making a shared object; recompile with -fPIC libdrm errors when using fortify options rm@sha/xf86drm.c.o(.text+0x3ce2): unresolvable R_RISCV_CALL relocation against symbol `strdup@@GLIBC_2.27' For now just disable the whole shebang Signed-off-by: Khem Raj <raj.khem@gmail.com> |
||
---|---|---|
conf | ||
recipes-core | ||
recipes-devtools | ||
recipes-extended/ghostscript | ||
recipes-kernel/linux | ||
recipes-support | ||
tools/manifests | ||
wic | ||
.travis.yml | ||
LICENSE | ||
README.md | ||
setup.sh |
meta-riscv
RISC-V Architecture Layer for OpenEmbedded/Yocto
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 (main focus of testing).
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
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
Build Image
bitbake core-image-full-cmdline
Run in QEMU
runqemu nographic
Running wic.gz image on hardware
The output of the 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>