Google Git
Sign in
opensecura / 3p / lowrisc / opentitan / ac5c79b544762d9a793bb4928b8e086fff3cc3ea / . / hw / vendor / pulp_riscv_dbg / tb
tree: 53a3e91de4e81ce269e243bb612289161cf300cc [path history] [tgz]
  1. prog/
  2. remote_bitbang/
  3. unused/
  4. .gitignore
  5. boot_rom.sv
  6. dm_compliance_test.cfg
  7. dm_debug.cfg
  8. dm_tb_pkg.sv
  9. dp_ram.sv
  10. LICENSE.Berkeley
  11. LICENSE.SiFive
  12. Makefile
  13. mm_ram.sv
  14. README.md
  15. SimJTAG.sv
  16. tb_test_env.sv
  17. tb_top.sv
  18. tb_top_verilator.cpp
  19. tb_top_verilator.sv
  20. vsim_batch.tcl
  21. vsim_gui.tcl
  22. waves.tcl
hw/vendor/pulp_riscv_dbg/tb/README.md

Debug Unit plus RI5CY Testbench

This testbench tests RI5CY together with a v0.13.1 compliant debug unit. There are several tests that can be run, but for now it is just riscv test_compliance of riscv-openocd (see in pulpissimo.cfg) and a not yet scripted run of gdb connecting to openocd, loading and running a hello world program (see prog/test.c).

You need riscv-openocd.

Running the testbench with vsim

Point you environment variable RISCV to your RISC-V toolchain. Call make vsim-run to build the testbench and the program, and run it with vsim. Use VSIM_FLAGS to configure the simulator e.g. make vsim-run VSIM_FLAGS="-gui -debugdb".

Running the testbench with vcs

Point you environment variable RISCV to your RISC-V toolchain. Call make vcs-run. Use VCS_FLAGS and SIMV_FLAGS to configure vcs e.g. make vcs-run VCS_FLAGS="-debug_all".

Running the testbench with verilator

Point you environment variable RISCV to your RISC-V toolchain. Call make veri-run. Use VERI_FLAGS to configure verilator e.g. make firmware-veri-run VERI_FLAGS="+firmware=path_to_firmware +vcd" to use a custom firmware and dump to a vcd file.

Options

A few plusarg options are supported.

  • +verbose to show all memory read and writes and other miscellaneous information.

  • +vcd to produce a vcd file called riscy_tb.vcd. Verilator always produces a vcd file called verilator_tb.vcd.

  • +firmware=path_to_firmware to load a specific firmware. It is a bit tricky to build and link your own program. Look into the prog folder for an example.

Example Run

  1. make veri-run
  2. (in new terminal) export JTAG_VPI_PORT=port_name_from 1.
  3. (in new terminal) openocd -f dm_compliance_test.cfg
  4. Now you can connect with gdb and interact with the testbench