bluespec / mcu-release Goto Github PK

After the fix to #5 , now the documented toolchain does not contain Verilator, but the demo instructions use Verilator.

Users will probably have to build a recent version of verilator from source: https://github.com/verilator/verilator

The version of verilator packaged in Debian Buster does NOT work; it is too old.

I opened a pull request

#2

in releases/mcu_20220508/README.adoc are instructions to get riscvachronix-1.202105.0.1.1.1centos7-2.x86_64.rpm.

However, the gcc in this toolchain only supports rv32i, but it looks like this release supports rv32imc.

For reference, the build log log that toolchain is at /raid/tools/riscvachronix/.install/riscvachronix-1.202105.0.1.1.1centos7/build/toolchain/build.log

releases/mcu_20220508/demo/run/program_fpga
releases/mcu_20220508/demo/scripts/program_fpga

The contents are identical.

The documentation in releases/mcu_20220508/README.adoc refers to the one in /scripts.

The "riscvachronix" for Centos 7 toolchain given in the documentation does NOT contain openocd. The example gdb scripts require it.

I have never successfully built openocd for Centos 7. According to my notes, the problems are
riscv-software-src/riscv-tools#134
and
mummer4/mummer#12

Around September 2021, after some discussion, we decided to punt on the issue, so I did not try harder to build openocd for Centos 7.