This README file contains information on the contents of the meta-cva6-yocto layer.

This layer is compatible with honister.

This layer depends on:

• URI: https://github.com/openembedded/openembedded-core
  • branch: master
  • revision: HEAD
• URI: https://github.com/openembedded/bitbake
  • branch: master
  • revision: HEAD
• URI: https://github.com/riscv/meta-riscv
  • branch: master
  • revision: HEAD

The system requirements for yocto are described here.

First install the repo tool

mkdir ${HOME}/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ${HOME}/bin/repo
chmod a+x ${HOME}/bin/repo
PATH=${PATH}:~/bin

mkdir cva6-yocto && cd cva6-yocto
repo init -u https://github.com/openhwgroup/meta-cva6-yocto -b main -m tools/manifests/cva6-yocto.xml
repo sync
repo start work --all

. ./meta-cva6-yocto/setup.sh

This layer is available for:

• cv64a6-genesys2: The Digilent FPGA board with the bitstream generated from the cva6 corev-apu with target default target cv64a6_imafdc_sv39.
• cv32a6-genesys2: Same board with the bitstream generated from the cva6 corev-apu with target cv32a6_ima_sv32_fpga.

To generate a console-only image for the cv32a6-genesys2:

MACHINE=cv32a6-genesys2 bitbake core-image-minimal

Image files will be located in build/tmp-glibc/deploy/images/cv32a6-genesys2.

Warning, you need to find the correct device image and fill it in the dd's of= parameter:

gunzip -c build/tmp-glibc/deploy/images/cv32a6-genesys2/core-image-minimal-cv32a6-genesys2.wic.gz | sudo dd of=/dev/sd$ bs=1M iflag=fullblock oflag=direct conv=fsync status=progress

The login is "root", no password is needed.

To produce the SDK for your target, you need to launch the following command :

MACHINE=cv32a6-genesys2 bitbake core-image-minimal -c populate_sdk_ext

This will create the SDK Installer in build/tmp-glibc/deploy/sdk/oecore-x86_64-riscv32nf-toolchain-ext-nodistro.0.sh file.

To install it, simply run

./build/tmp-glibc/deploy/sdk/oecore-x86_64-riscv32nf-toolchain-ext-nodistro.0.sh

You can install the SDK anywhere you want as long as you have writing rights.

To use the SDK, you need to source the environment-setup file in the SDK install path :

source $(SDK_INSTALL_PATH)/environment-setup-riscv32nf-oe-linux

Your environment variables should have changed (e.g. PATH, CC, LD and more). This allow you to manually build software. The devtool command is also available. It will allow build, test, package an integrate software in the Yocto build system.

The core-image-minimal has been tested for the 32 and 64bits version of corev-apu with release 3ddf797.

TFTP boot from u-boot is working.