Chipyard BOOM环境搭建

link

Chipyard BOOM环境搭建

安装流程

安装依赖

安装依赖可以避免后续的很多问题。
Docs » 1. Chipyard Basics » 1.4. Initial Repository Setup
查看对应版本需要安装的依赖，本文使用的环境是ubuntu 18.04：

#!/bin/bash
set -ex
sudo apt-get install -y build-essential bison flex software-properties-common curl
sudo apt-get install -y libgmp-dev libmpfr-dev libmpc-dev zlib1g-dev vim default-jdk default-jre
# install sbt: https://www.scala-sbt.org/release/docs/Installing-sbt-on-Linux.html#Ubuntu+and+other+Debian-based+distributions
echo "deb https://repo.scala-sbt.org/scalasbt/debian /" | sudo tee -a /etc/apt/sources.list.d/sbt.list
curl -sL "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x2EE0EA64E40A89B84B2DF73499E82A75642AC823" | sudo apt-key add
sudo apt-get update
sudo apt-get install -y sbt
sudo apt-get install -y texinfo gengetopt
sudo apt-get install -y libexpat1-dev libusb-dev libncurses5-dev cmake
# deps for poky
sudo apt-get install -y python3.8 patch diffstat texi2html texinfo subversion chrpath wget
# deps for qemu
sudo apt-get install -y libgtk-3-dev gettext
# deps for firemarshal
sudo apt-get install -y python3-pip python3.8-dev rsync libguestfs-tools expat ctags
# install DTC
sudo apt-get install -y device-tree-compiler
sudo apt-get install -y python
# install git >= 2.17
sudo add-apt-repository ppa:git-core/ppa -y
# sudo apt-get update
sudo apt-get install git -y
# install verilator
sudo apt-get install -y autoconf
git clone http://git.veripool.org/git/verilator
cd verilator
git checkout v4.034
autoconf && ./configure && make -j$(nproc) && sudo make install

下载chipyard并配置BOOM

参考Welcome to RISCV-BOOM’s documentation!

# Download the template and setup environment
git clone https://github.com/ucb-bar/chipyard.git
cd chipyard
./scripts/init-submodules-no-riscv-tools.sh

# build the toolchain
./scripts/build-toolchains.sh riscv-tools

# add RISCV to env, update PATH and LD_LIBRARY_PATH env vars
# note: env.sh generated by build-toolchains.sh
source env.sh

cd sims/verilator
make CONFIG=SmallBoomConfig

./scripts/build-toolchains.sh riscv-tools执行成功：
在这里插入图片描述
make CONFIG=SmallBoomConfig执行成功：
在这里插入图片描述

使用BOOM进行Dhrystone测试：

# 对SmallBoom运行dhrystone程序
./simulator-chipyard-SmallBoomConfig $RISCV/riscv64-unknown-elf/share/riscv-tests/benchmarks/dhrystone.riscv

 
 
  • 1
  • 2

./simulator-chipyard-LargeBoomConfig $RISCV/riscv64-unknown-elf/share/riscv-tests/benchmarks/dhrystone.riscv执行成功：
在这里插入图片描述
如果想要切换BOOM CONGIF，重新执行make步骤即可：

# 切换BOOM CONFIG：如选择LargeBoomConfig进行编译
make CONFIG=LargeBoomConfig
# 然后运行dhrystone程序
./simulator-chipyard-LargeBoomConfig $RISCV/riscv64-unknown-elf/share/riscv-tests/benchmarks/dhrystone.riscv

 
 
  • 1
  • 2
  • 3
  • 4

在这里插入图片描述

BOOM的配置文件在generators/chipyard/src/main/scala/config/BoomConfigs.scala中，也可自行编写Boom的其它配置项。
在这里插入图片描述

使用BOOM核仿真自己编写的C程序

编译C程序生成可执行文件：

riscv64-unknown-elf-gcc -fno-common -fno-builtin-printf -specs=htif_nano.specs -c test.c
riscv64-unknown-elf-gcc -static -specs=htif_nano.specs test.o -o test.riscv
spike test.riscv

 
 
  • 1
  • 2
  • 3

BOOM核仿真运行：

./simulator-chipyard-SmallBoomConfig ./test.riscv

 
 
  • 1

移植到FPGA上

由于软件仿真效率太低，考虑将BOOM核移植到FPGA上。参考：10.1. General Setup and Usage
在chipyard/fpga/src/main/scala/arty/Configs.scala下添加如下配置：

class BoomArtyConfig extends Config(
  new WithFPGAFrequency(50) ++
  new WithArtyTweaks ++
  new chipyard.SmallBoomConfig)

class WithFPGAFrequency(fMHz: Double) extends Config(
new chipyard.config.WithPeripheryBusFrequency(fMHz) ++ // assumes using PBUS as default freq.
new chipyard.config.WithMemoryBusFrequency(fMHz)
)
class WithFPGAFreq25MHz extends WithFPGAFrequency(25)
class WithFPGAFreq50MHz extends WithFPGAFrequency(50)
class WithFPGAFreq75MHz extends WithFPGAFrequency(75)
class WithFPGAFreq100MHz extends WithFPGAFrequency(100)

安装vivado后配置路径，返回chipyard目录：

# in the chipyard top level folder
source ./env.sh
# 配置vivado路径，如果which vivado有返回可以忽略
# source ../../vivado/Vivado/2019.1/settings64.sh
./scripts/init-fpga.sh
cd fpga
# 查看vivado是否配置
which vivado
make SUB_PROJECT=arty CONFIG=BoomArtyConfig bitstream

踩的一些坑

build the toolchain时遇到的问题以及解决措施

问题1：虚拟机磁盘空间不足，对磁盘扩容

//查看磁盘使用率
df -hl

 
 
  • 1
  • 2

在这里插入图片描述

解决：VMware虚拟机 Linux系统 Ubuntu 16.04 硬盘/磁盘扩容

问题2：ubuntu编译qemu报错：‘ERROR: pixman >= 0.21.8 not present.’

在这里插入图片描述
解决：ubuntu编译qemu报错：‘ERROR: pixman >= 0.21.8 not present.’ 解决方案

apt-cache search pixman
apt-get install libpixman-1-dev

 
 
  • 1
  • 2

问题3：提示“Failed to connect to boringssl.googlesource.com port 443: Connection timed out”

在这里插入图片描述
解决：
参考：OPTEE repo更新提示“Failed to connect to boringssl.googlesource.com port 443: Connection timed out”的解决方案
qemu-v8分支会自动下载edk2，而edk2的Openssl在下载boringssl时访问boringssl.googlesource.com，而GFW屏蔽了googlesouce，所以会导致链接超时。

使用git config --global url.A.insteadOf B命令将boringssl.googlesource.com替换为谷歌的github镜像库https://github.com/google/boringssl.git

git config --global url."https://github.com/google/boringssl.git".insteadOf "https://boringssl.googlesource.com/boringssl"
git config --global url."https://hub.fastgit.org/google/boringssl.git".insteadOf "https://boringssl.googlesource.com/boringssl"
repo sync

 
 
  • 1
  • 2
  • 3

问题4：dromajo没有那个文件或目录。停止。

在这里插入图片描述
解决：
在GitHub chipyard项目找到对应位置，手动下载dromajo-secrect文件，注意文件夹名称与chipyard中一致。

git clone git://github.com/riscv-boom/dromajo.git

 
 
  • 1

make CONFIG时遇到的问题以及解决措施

问题5：bash：java：未找到命令

在这里插入图片描述
解决：安装java，参考Ubuntu配置JAVA环境

//安装jdk
sudo apt install openjdk-8-jdk-headless
//编辑环境变量
sudo gedit /etc/profile
//添加：
//export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
//export JRE_HOME=$JAVA_HOME/jre
//export CLASSPATH=$JAVA_HOME/lib:$JRE_HOME/lib:$CLASSPATH
//export PATH=$JAVA_HOME/bin:$JRE_HOME/bin:$PATH
//使其生效
source /etc/profile
//查看是否安装成功
java -version

    “source [file join $scriptdir “prologue.tcl”]”
    (file “/home/hansi/BOOM/chipyard/fpga/fpga-shells/xilinx/common/tcl/vivado.tcl” line 7)
    INFO: [Common 17-206] Exiting Vivado at Wed Apr 6 14:42:43 2022….
    Makefile:115: recipe for target ‘/home/hansi/BOOM/chipyard/fpga/generated-src/chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig/obj/ArtyFPGATestHarness.bit’ failed
    make: *** [/home/hansi/BOOM/chipyard/fpga/generated-src/chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig/obj/ArtyFPGATestHarness.bit] Error 1

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8

    解决方案：
    Swap two arguments to resolve bug #941
    Merge pull request #941 from zslwyuan/patch-3
    查看chipyard/fpga/Makefile，对应位置的代码是merge后的代码，但还是报了一样的错，bug中提到这是针对2020版本的vivado报错进行的修改，本文使用的是2019.1版本的vivado，所以尝试修改回之前的版本试试看。
    成功解决了这个报错，但是出现了新的问题。

    问题10：vivado安装文件中没有对应的板子的文件

    ERROR: [Board 49-71] The board_part definition was not found for digilentinc.com:arty:part0:1.1. The project's board_part property was not set, but the project's part property was set to xc7a35ticsg324-1L. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command. Check if board.repoPaths parameter is set and the board_part is installed from the tcl app store.
INFO: [Common 17-17] undo 'set_property'

    <span class="token keyword">while</span> executing

    “rdi::add_properties -dict {BOARD_PART digilentinc.com:arty:part0:1.1 TARGET_LANGUAGE Verilog DEFAULT_LIB xil_defaultlib IP_REPO_PATHS /home/hansi/BOOM…”
    invoked from within
    “set_property -dict [list
    BOARD_PART KaTeX parse error: Undefined control sequence: \ at position 19: …t_board</span> \̲ ̲ TARGET_LANGUAG…ipdir
    ] [current_…”
    (file “/home/hansi/BOOM/chipyard/fpga/fpga-shells/xilinx/common/tcl/prologue.tcl” line 78)

    <span class="token keyword">while</span> executing

    “source [file join $scriptdir “prologue.tcl”]”
    (file “/home/hansi/BOOM/chipyard/fpga/fpga-shells/xilinx/common/tcl/vivado.tcl” line 7)
    INFO: [Common 17-206] Exiting Vivado at Wed Apr 6 20:01:41 2022….
    Makefile:115: recipe for target ‘/home/hansi/BOOM/chipyard/fpga/generated-src/chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig/obj/ArtyFPGATestHarness.bit’ failed
    make: *** [/home/hansi/BOOM/chipyard/fpga/generated-src/chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig/obj/ArtyFPGATestHarness.bit] Error 1

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16
    • 17
    • 18
    • 19
    • 20

    解决：Missing Board Files for ARTY-A7-35T
    下载并提取文件：Vivado Version 2015.1 and Later Board File Installation (Legacy)
    将所需的board复制到vivado/Vivado/2019.1/data/boards/board_files路径下即可。

    问题11：error: [synth 8-2715] syntax error near "dpi-c

    连续很多行报错都是SimSRAM.v存在syntax error。

    解决：Errors while generating bitstream for Rocket Chip core verilogs using vivado 2016.1
    回答中说明SimSRAM.v文件在综合过程中不是必须的，可以使用空文件代替。syntax error是因为这是sv的语法，vivado 2016.1不支持，需要2018.1以后的版本。（但是这里2019.1也存在问题
    所以这里删除SimSRAM.v文件中的全部内容即可。

    问题12：chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig.harness.v中找不到module 'SimDRAM'

    ERROR: [Synth 8-439] module 'SimDRAM' not found [/home/hansi/BOOM/chipyard/fpga/generated-src/chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig/chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig.harness.v:335]
	Parameter LINE_SIZE bound to: 32'sb00000000000000000000000001000000 
	Parameter CLOCK_HZ bound to: 32'sb00000010111110101111000010000000 
	Parameter ID_BITS bound to: 32'sb00000000000000000000000000000100 
	Parameter ADDR_BITS bound to: 32'sb00000000000000000000000000100000 
	Parameter MEM_SIZE bound to: 32'sb00010000000000000000000000000000 
	Parameter DATA_BITS bound to: 32'sb00000000000000000000000001000000 
ERROR: [Synth 8-6156] failed synthesizing module 'ArtyFPGATestHarness' [/home/hansi/BOOM/chipyard/fpga/generated-src/chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig/chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig.harness.v:1]

 
 
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8

    解决：找到报错的部分，删除整个module SimDRAM即可。

    问题13：报错vivado/Vivado/2019.1/bin/loader: 行 267: 23806 已杀死 "$RDI_PROG" "$@"

    Start Technology Mapping
---------------------------------------------------------------------------------
/home/hansi/vivado/Vivado/2019.1/bin/loader: 行 267: 23806 已杀死               "$RDI_PROG" "$@"
Makefile:115: recipe for target '/home/hansi/BOOM/chipyard/fpga/generated-src/chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig/obj/ArtyFPGATestHarness.bit' failed
make: *** [/home/hansi/BOOM/chipyard/fpga/generated-src/chipyard.fpga.arty.ArtyFPGATestHarness.BoomArtyConfig/obj/ArtyFPGATestHarness.bit] Error 137
Parent process (pid 23806) has died. This helper process will now exit

 
 
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6

    解决：
    /tools/Xilinx/Vivado/2019.1/bin/loader: line 267: 18166 Killed “$ RDI_PROG” " $@" Vivado build interruption
    64434 - Vivado Synthesis - getting a Segmentation fault after using up a lot of memory.

    在Makefile文件中添加vivado -stack 2000参数
    在这里插入图片描述
    还是不行，看到有解决方法提示RAM太小，把虚拟机内存大小从原本8GB调整到16GB，问题解决。

    问题14：place_design failed

    报错：

    Phase 1.2 IO Placement/ Clock Placement/ Build Placer Device
ERROR: [Place 30-640] Place Check : This design requires more Register as Flip Flop cells than are available in the target device. This design requires 51080 of such cell types but only 41600 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device.
ERROR: [Place 30-640] Place Check : This design requires more Slice Registers cells than are available in the target device. This design requires 51081 of such cell types but only 41600 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device.
ERROR: [Place 30-640] Place Check : This design requires more Slice LUTs cells than are available in the target device. This design requires 191762 of such cell types but only 20800 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device. Please set tcl parameter "drc.disableLUTOverUtilError" to 1 to change this error to warning.
ERROR: [Place 30-640] Place Check : This design requires more LUT as Logic cells than are available in the target device. This design requires 111786 of such cell types but only 20800 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device. Please set tcl parameter "drc.disableLUTOverUtilError" to 1 to change this error to warning.
ERROR: [Place 30-640] Place Check : This design requires more LUT as Memory cells than are available in the target device. This design requires 79976 of such cell types but only 9600 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device. Please set tcl parameter "drc.disableLUTOverUtilError" to 1 to change this error to warning.
ERROR: [Place 30-640] Place Check : This design requires more LUT as Distributed RAM cells than are available in the target device. This design requires 79938 of such cell types but only 9600 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device. Please set tcl parameter "drc.disableLUTOverUtilError" to 1 to change this error to warning.
ERROR: [Place 30-640] Place Check : This design requires more LUT6 cells than are available in the target device. This design requires 77493 of such cell types but only 32600 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device.
ERROR: [Place 30-640] Place Check : This design requires more RAMD64E cells than are available in the target device. This design requires 78176 of such cell types but only 9600 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device.
INFO: [Timing 38-35] Done setting XDC timing constraints.
Phase 1.2 IO Placement/ Clock Placement/ Build Placer Device | Checksum: bf3f60f9

    Time (s): cpu = 00:01:00 ; elapsed = 00:00:50 . Memory (MB): peak = 7312.086 ; gain = 0.000 ; free physical = 9339 ; free virtual = 14080
    Phase 1 Placer Initialization | Checksum: bf3f60f9

    Time (s): cpu = 00:01:00 ; elapsed = 00:00:50 . Memory (MB): peak = 7312.086 ; gain = 0.000 ; free physical = 9339 ; free virtual = 14080
    ERROR: [Place 30-99] Placer failed with error: ‘Implementation Feasibility check failed, Please see the previously displayed individual error or warning messages for more details.’
    Please review all ERROR, CRITICAL WARNING, and WARNING messages during placement to understand the cause for failure.
    Ending Placer Task | Checksum: bf3f60f9

    Time (s): cpu = 00:01:00 ; elapsed = 00:00:50 . Memory (MB): peak = 7312.086 ; gain = 0.000 ; free physical = 9339 ; free virtual = 14080
    INFO: [Common 17-83] Releasing license: Implementation
    11 Infos, 0 Warnings, 0 Critical Warnings and 10 Errors encountered.
    place_design failed
    ERROR: [Common 17-69] Command failed: Placer could not place all instances

    <span class="token keyword">while</span> executing

    “source [file join $scriptdir “place.tcl”]”
    (file “/home/hansi/BOOM/chipyard/fpga/fpga-shells/xilinx/common/tcl/vivado.tcl” line 29)

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16
    • 17
    • 18
    • 19
    • 20
    • 21
    • 22
    • 23
    • 24
    • 25
    • 26
    • 27
    • 28
    • 29

    板子资源不足，卒。。。。arty7 35T资源支撑不了BOOM。
    尝试了下用arty7 35T生成tinyrocket的bitstream，很快就完成了并且没有报错。

    make SUB_PROJECT=arty CONFIG=TinyRocketConfig bitstream

 
 
    • 1

    对比了一下所需资源，差了十几倍。
    在这里插入图片描述
    生成BOOM的bitstream只能考虑换一个板子了。

    参考

    [1] Docs » 1. Chipyard Basics » 1.4. Initial Repository Setup
    [2] Welcome to RISCV-BOOM’s documentation!
    [3] VMware虚拟机 Linux系统 Ubuntu 16.04 硬盘/磁盘扩容
    [4] ubuntu编译qemu报错：‘ERROR: pixman >= 0.21.8 not present.’ 解决方案
    [5] OPTEE repo更新提示“Failed to connect to boringssl.googlesource.com port 443: Connection timed out”的解决方案
    [6] Ubuntu配置JAVA环境
    [7] Failed to build verilator · Issue #72 · nvdla/hw · GitHub
    [8] Installation——Verilator 4.221 documentation
    [9] How do I compile a c program such that the binary can be run/simulated by an RTL config?
    [10] 7.3. Baremetal RISC-V Programs

    附录

    RISC-V toolchain编译指令

    // complie 64-bit file
riscv64-unknown-elf-gcc -o file file.c
// complie 32-bit file
riscv64-unknown-elf-gcc -march=rv32imac -mabi=ilp32 -o file file.c

    // pretreatment
    riscv64-unknown-elf-gcc -march=rv32imac -mabi=ilp32 -E -o file.i file.c
    // compile
    riscv64-unknown-elf-gcc -march=rv32imac -mabi=ilp32 -S -o file.s/file.S file.i
    // assembler
    riscv64-unknown-elf-gcc -march=rv32imac -mabi=ilp32 -c -o file.o file.s/file.S
    // link
    riscv64-unknown-elf-gcc -march=rv32imac -mabi=ilp32 -o file file.o
    // get ELF-file
    riscv64-unknown-elf-gcc -march=rv32imac -mabi=ilp32 -o file file.c
    // ELF to bin
    riscv32-unknown-elf-objcopy -O binary file file.bin
    // ELF to HEX
    riscv64-unknown-elf-objcopy -O ihex file file.hex
    // disassembler ELF to get ASM
    riscv64-unknown-elf-objdump -d file.elf > file.asm

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16
    • 17
    • 18
    • 19
    • 20
    • 21

    Linux查看CPU信息

    //查看物理 cpu 数：
cat /proc/cpuinfo| grep "physical id"| sort| uniq| wc -l
//查看每个物理 cpu 中 核心数(core 数)：
cat /proc/cpuinfo | grep "cpu cores" | uniq
//查看总的逻辑 cpu 数（processor 数）：
cat /proc/cpuinfo| grep "processor"| wc -l
//查看 cpu 型号：
cat /proc/cpuinfo | grep name | cut -f2 -d: | uniq -c
//lscpu 命令可以同时看到上述信息：
lscpu

 
 
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    posted @ 2022-08-19 22:44  luoganttcc  阅读(323)  评论(0)  编辑  收藏  举报